Bug 208619 - xorg backtrace after logging into GNOME
Summary: xorg backtrace after logging into GNOME
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-29 18:27 UTC by Matthias Saou
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-11-13 14:34:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.log with backtrace (51.52 KB, text/plain)
2006-09-29 18:27 UTC, Matthias Saou
no flags Details

Description Matthias Saou 2006-09-29 18:27:48 UTC
Reproducible on a 20060929 x86_64 Rawhide system :

- Boot the computer (rhgb is disabled, FWIW)
- Log in through gdm
- The GNOME desktop starts to appear... but then X crashes and back to gdm
- Log in through gdm again, this time it works

Attached is my Xorg log. The next log (when X still works) is identical up until
the backtrace, which doesn't occur.

My graphics card is an nVidia Quadro FX 3450 of which I'm using the DVI port and
the free nv driver. I didn't ever touch the xorg.conf file (FC6t3 DVD install).

Comment 1 Matthias Saou 2006-09-29 18:27:48 UTC
Created attachment 137415 [details]
Xorg.log with backtrace

Comment 2 Matthias Saou 2006-09-29 18:30:08 UTC
Oh, one last possibly important detail : I pass vga=0x317 to the kernel in order
to get a nice framebuffer console.

Comment 3 Matthias Saou 2006-10-04 14:05:55 UTC
Still 100% reproducible. I get the crash and backtrace after each boot upon the
first login, and the second login attempt works fine. I'm really confused. Today
I just checked the /var/log/Xorg.0.log.old file, but it only has this as the
last line :

Backtrace:

And doesn't contain the actual backtrace below anymore. Weird. Please let me
know if there is any more testing I can do.

Comment 4 Matthias Saou 2006-11-13 14:34:49 UTC
The system is now FC6 + all updates, and the problem doesn't happen anymore, so
closing this bug.


Note You need to log in before you can comment on or make changes to this bug.