Description of problem: When starting some GL programs (like ppracer for example), then the X server seems to crash and send me back to the login prompt. I tried to update all relevant components to the latest updates-testing, but it remains. Version-Release number of selected component (if applicable): see attachments How reproducible: always Steps to Reproduce: 1. log in 2. start ppracer, supertux or similar 3. ...you're sent back the login prompt Actual results: Expected results: Additional info:
Created attachment 305993 [details] all packages, output of lspci and the xorg.conf
Created attachment 305994 [details] output of glxinfo
are you running with desktop effects enabled?
This happens both with and without the desktop effects enabled. I have used a fresh F9 install.
(In reply to comment #3) > are you running with desktop effects enabled? This happens both with and without the desktop effects enabled. I have used a fresh F9 install.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 307245 [details] the xorg.conf file I use
Created attachment 307246 [details] logfile for X The Xorg logfiles after I made the server crash starting tuxpaint.
Created attachment 307247 [details] logfile for X same as previous
Created attachment 307250 [details] Case 2, restart with no xorg.conf file, start tuxpaint again
Created attachment 307251 [details] Case 2, restart with no xorg.conf file, start tuxpaint again
Created attachment 307252 [details] Case 2, restart with no xorg.conf file, start tuxpaint again
Created attachment 307255 [details] Case 3: new xorg.conf file produced with system-config-display Then I make a new xorg.conf file using system-config-display. Suddenly I get the correct resolution of my screen: 1600x1200, this I did not get after install and even after running system-config-display.
Created attachment 307256 [details] Case 3: the log file now the server does not crash.
One crash: Backtrace: 0: /usr/bin/Xorg(xf86SigHandler+0x79) [0x80d60c9] 1: [0x110400] 2: /usr/bin/Xorg(VidModeGetFirstModeline+0x7d) [0x80c62ad] 3: /usr/bin/Xorg(VidModeGetNumOfModes+0x40) [0x80c6360] 4: /usr/lib/xorg/modules/extensions//libextmod.so [0x22249f] 5: /usr/bin/Xorg(Dispatch+0x34f) [0x8085a3f] 6: /usr/bin/Xorg(main+0x47d) [0x806b3bd] 7: /lib/libc.so.6(__libc_start_main+0xe6) [0xa005d6] 8: /usr/bin/Xorg(FontFileCompleteXLFD+0x22d) [0x806a7a1]
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.