> Please, no need to confirm this anymore, we know it's broken and are
trying to find the cure.

> The bug is not in the driver, since Herd5 didn't have that. I've now
put new xserver-xorg-core which has debugging symbols in it. so no need
to install a -dbg too, so go grab these and get a backtrace:

There is a back trace in my last post ....
Regardless... i've installed those 2 packages and restarted gdm...
heres the latest backtrace

------------------ Snippet from log ------------
(WW) VESA(0): No valid modes left.  Trying less strict filter...

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x81) [0x80da8f1]
1: [0xffffe420]
2: /usr/X11R6/bin/X(InitOutput+0x9aa) [0x80a5b9a]
3: /usr/X11R6/bin/X(main+0x27b) [0x807456b]
4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d24ebc]
5: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]

Fatal server error:
Caught signal 11.  Server aborting


** Attachment added: "xorg log file with backtrace"
   http://librarian.launchpad.net/7360639/Xorg.0.log

-- 
[regression] 7.2 broke vesa: "No matching modes found"
https://bugs.launchpad.net/bugs/89853
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to