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

Bug#185658: marked as done (xserver-xfree86: [core server] should queue up fatal errors and report them last(?))

Your message dated Sun, 22 Jul 2007 02:34:22 +0200
with message-id <20070722003413.GA7307@patate.is-a-geek.org>
and subject line Bug#185658: xserver-xfree86: if fail, say something on the console
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xserver-xfree86
Version: 4.2.1-5
Severity: minor

Let's say there is some minor problem with the XF86Config-4 file.
Well, upon power up, x windows doesn't start, and the user is baffled.
The answer lies at the bottom of syslog file.
I say the answer should be right there at the bottom of all those
dmesg messages, which you must admit are less important.
Reproduce by changing the /dev listing of your mouse and typing "init 1".
so say also to the console, e.g.
xf86OpenSerial: Cannot open device /dev...
-- Package-specific info:
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux debian 2.4.20-k7 #1 Tue Jan 14 00:29:06 EST 2003 i686
Locale: LANG=zh_TW.Big5, LC_CTYPE=zh_TW.Big5

Versions of packages xserver-xfree86 depends on:
ii  debconf                       1.2.22     Debian configuration management sy
ii  libc6                         2.3.1-10   GNU C Library: Shared libraries an
ii  xserver-common                4.2.1-5    files and utilities common to all 
ii  zlib1g                        1:1.1.4-9  compression library - runtime

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
On Fri, Mar 21, 2003 at 03:18:44 +0800, Dan Jacobson wrote:

> Let's say there is some minor problem with the XF86Config-4 file.
> Well, upon power up, x windows doesn't start, and the user is baffled.
> The answer lies at the bottom of syslog file.
> I say the answer should be right there at the bottom of all those
> dmesg messages, which you must admit are less important.
> Reproduce by changing the /dev listing of your mouse and typing "init 1".
> so say also to the console, e.g.
> xf86OpenSerial: Cannot open device /dev...

This bugreport doesn't make sense, so I'm closing it.  The format of
messages is explained right there at the top of the X log, and if people
can't read there's nothing we can do to help them anyway.

Cheers,
Julien

--- End Message ---
Reply to: