[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#561764: marked as done (boot warnings fly off screen and are not logged to any file)



Your message dated Wed, 10 Jul 2013 20:09:13 +0200
with message-id <20130710180913.GB6890@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #561764,
regarding boot warnings fly off screen and are not logged to any file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
561764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561764
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-2
Severity: wishlist
X-debbugs-cc: linux-kernel@vger.kernel.org

There is some warning about SYS... being DEPRECATED or something like
that. I can't tell as it flies off the screen at boot and is not kept in
any /var/log file.

I don't even know what to google for, as I can't read the message fast enough.

How is one supposed to know what it says if it files off the screen, and
even SHIFT PAGE UP can't reach it.

How many other warnings fly away and aren't in dmesg etc.?



--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---

Reply to: