Description of problem: After performing a yum update on 08-Mar-2010, and receiving a number of xorg-x11 components, I found that X11 would hang as soon as I started it and tried to open any application, change to a different virtual desktop or open any desktop control windows. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.7.1-7.fc12 How reproducible: 100%. Update to this RPM and X will hang on the first operation you attempt after it starts. Steps to Reproduce: 1. yum update xorg-x11-server-Xorg 2. startx 3. click on desktop #2 in ICEWM Actual results: X hangs with no crash dump or any other clues. Am unable to launch applications, switch desktops, or perform any other X operations. The only way out is <ctrl><alt><backspace> Expected results: Expected X to continue working after yum update Additional info: System runs ICEWM as desktop manager. ICEWM comes from Fedora provided RPM. System has ATI RV535 [Radeon X1650 Series] (rev 9e) video. Same yum update provided new ATI driver and firmware but those do not seem to be causing this issue as they have been updated and the system continues to work as long as I do not update xorg-x11-server-Xorg I see other bugs reporting X11 crashes and those appear to leave a crash dump or other clues as to what happened. This case is different because there are no clues, no crash dump, X just becomes unresponsive.
correcting version number of failing RPM, When I update to: xorg-x11-server-Xorg.1.7.5.901-1.fc12.i686 from: xorg-x11-server-Xorg-1.7.1-7.fc12.i686 this failure/hang occurs.
I have the same behavior. I upgraded to xorg-x11-server-Xorg.1.7.5.901-4.fc12.i686 in testing and the problem persists.
As an additional note, there are additional reports showing up on fedoraforum.org.
As a follow up, I can confirm that downgrading to xorg-x11-server-Xorg-1.7.1-7.fc12.i686 doesn't help, so I would suspect the problem could be in gdm or a gdm/xorg interaction.
I cannot confirm that downgrading is not an improvement. In fact, it is quite the opposite here. When I upgrade to 1.7.5, the problem appears and when I downgrade to 1.7.1, the problem goes away. I spent considerable time isolating the failure to just this RPM and I do not run gdm here at all.
(In reply to comment #5) > I cannot confirm that downgrading is not an improvement. In fact, it is > quite the opposite here. When I upgrade to 1.7.5, the problem appears > and when I downgrade to 1.7.1, the problem goes away. I spent considerable > time isolating the failure to just this RPM and I do not run gdm here > at all. Strange. In my case I can confirm that it is something to do with gdm. I switched to xdm and no problems.
Just a further followup. Moved back to xorg-x11-server-Xorg.1.7.5.901-1.fc12.i686 and with gdm disabled (xdm enabled) no problems.
hmm... curious. I do not use xdm either. Pretty bare bones... I use 'startx' to launch X from a dumb vt. So, perhaps the bug relates to something common in the way gdm and ICEWM use the X server.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.