Red Hat Bugzilla – Bug 475485
Gnome screensaver crash locks up X windows
Last modified: 2015-01-14 18:22:14 EST
Created attachment 326309 [details]
Description of problem:
X is locking up when the gnome screensaver starts. The only way I can work around this is to restart X (<ctrl><alt><backspace>)
It also crashes when I try to edit the screensaver settings, but X doesn't lock up.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Leave pc unattended. Wait to screensaver starts.
2. PC locked up. Crash report visible but unreachable. Reboot X to recover.
3. Also, using the following menu sequence: system, preferences, Look and Feel, Screensaver. Crash report appears but no lock up.
1. The bug reporter is on the screen, but can't be accessed because X is locked.
2. Via menus: can save the crash report. (Attached)
No X lockup.
Crash report attached.
I've found the problem.
There seems to be a conflict with the old fglrx driver that was used in F9 before I upgraded the box.
After removing the module, which is not used in F10, the problem went away.
I have the same exact problem though I am using a fresh install of fedora 10. I am using the rpmfusion's akmod-fglrx driver. I can not find any other fglrx driver installed that might be conflicting using yum.
Created attachment 331470 [details]
Ok so the problem comes from having xinerama enabled in xorg.conf file. After resetting my xorg file using system-config-display --reconfig. Making sure that the utility picked the fglrx driver and restarting the xserver the screensaver stopped crashing. Since xrandr doesn't detect my two monitors as seperate i used the command xrandr --output default --mode 2560x1024 to enable dual monitors.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.