Bug#182976: marked as done (xserver-xfree86: [core server] hack server to tell people 'no screens found' can be due to 'UseFBDev' option)
Your message dated Tue, 24 Jul 2007 14:20:32 +0200
with message-id <20070724122030.GA1575@patate.is-a-geek.org>
and subject line Bug#182976: xserver-xfree86: more information in debconf about possible problems with framebuffer
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 ---
- To: Debian Bug Tracking System <maintonly@bugs.debian.org>
- Subject: xserver-xfree86: more information in debconf about possible problems with framebuffer
- From: Marco Herrn <herrn@gmx.net>
- Date: Sat, 01 Mar 2003 13:10:36 +0100
- Message-id: <E18p5p7-0002bC-00@lurkabove.darkstar>
Package: xserver-xfree86
Version: 4.2.1-3
Severity: minor
Sometimes using the framebuffer device can lead to problems (for example
when using nvidia drivers). The error message from the X server is not
very verbose:
EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
Nobody can know that this can be the result of using framebuffer.
It would be good, if debconf displays an extra warning to the question
of whether using the framebuffer device, like:
If you get the error message "no screens found" and
/var/log/XFree86.0.log contains the line
"EE) Screen(s) found, but none have a usable configuration.",
then this is possibly the result of using the framebuffer
device. Try turning this option off, by running
"dpkg-reconfigure xserver-xfree86" and see if the error goes
away.
I would say this is more a bug of the actual X server, but this message
could help newbies a lot by showing them a frequent cause of problems.
Maybe this problem is the one of bug #157924:
"xserver-xfree86: [nv] no screens found on GeForce2 MX DDR rev 178"
(I do not send the content of my /var/log/XFree86.0.log, because it
wouldn't help here.)
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux lurkabove.darkstar 2.4.19 #1 Sam Sep 7 18:28:31 CEST 2002 i686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro
Versions of packages xserver-xfree86 depends on:
ii debconf 1.2.21 Debian configuration management sy
ii libc6 2.2.5-14.3 GNU C Library: Shared libraries an
ii xserver-common 4.2.1-3 files and utilities common to all
ii zlib1g 1:1.1.4-6 compression library - runtime
--- End Message ---
--- Begin Message ---
- To: 182976-done@bugs.debian.org
- Subject: Re: Bug#182976: xserver-xfree86: more information in debconf about possible problems with framebuffer
- From: Julien Cristau <jcristau@debian.org>
- Date: Tue, 24 Jul 2007 14:20:32 +0200
- Message-id: <20070724122030.GA1575@patate.is-a-geek.org>
- In-reply-to: <1046527719.2886.15.camel@thor>
- References: <E18p5p7-0002bC-00@lurkabove.darkstar> <1046527719.2886.15.camel@thor>
On Sat, Mar 1, 2003 at 15:08:40 +0100, Michel Dänzer wrote:
> On Sam, 2003-03-01 at 13:10, Marco Herrn wrote:
> > The error message from the X server is not
> > very verbose:
> >
> > EE) Screen(s) found, but none have a usable configuration.
> >
> > Fatal server error:
> > no screens found
> >
> > Nobody can know that this can be the result of using framebuffer.
>
> Indeed, because it's a very generic error message which can be caused by
> a lot of things. If Option "UseFBDev" is a problem, the usual symptom is
> the driver aborting right after loading the fbdevhw module.
>
I don't think we can do much to improve that error message, so I'll just
close this bug. If someone disagrees, please reopen and reassign to
xserver-xorg-core.
Cheers,
Julien
--- End Message ---
Reply to: