Bug#367260: marked as done (xorg-server: server fails to start at 2048x1536 but starts at 1920x1440 (then crashes))
Your message dated Sun, 11 Jun 2006 18:49:41 -0400
with message-id <20060611224941.GH11101@localdomain>
and subject line Bug#367260: bug appears to be fixed
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 <submit@bugs.debian.org>
- Subject: xorg-server: server fails to start at 2048x1536 but starts at 1920x1440 (then crashes)
- From: Jeff Abrahamson <jeff@purple.com>
- Date: Sun, 14 May 2006 14:52:12 -0400
- Message-id: <20060514185212.9045.71205.reportbug@astra.purple.com>
Package: xorg-server
Severity: normal
If I request 2048x1536 resolution in xorg.conf, X fails on startup
with a backtrace that is not output to Xorg.log for reporting here.
If I request 1920x1440, X runs, but leaves the display in an unusable
state (a version of a blank screen) when X exits. The machine is
still usable via ssh, but I can't get the display to work again
without rebooting.
This might be related to bug #365654.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
On Sun, Jun 11, 2006 at 05:54:03PM -0400, Jeff Abrahamson wrote:
> This bug appears to have been fixed with the xserver-xorg 7.0.20.
Great! Thank you for following up! Closing per submitter.
- David Nusinow
--- End Message ---
Reply to: