Created attachment 367815 [details]
The rawhide from 5th November introduced a crash in X server. The back trace is in the xorg log files. I had to revert back to the following to get a working X
Machine is a Dell D630C laptop with the following card
[root@neo ~]# lspci |grep VGA
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 135M (rev a1)
looks like bug 533236. perhaps try 1.7.1-7 from koji
Similar but in this case there's 3 main differences. Graphics card is Nvidia not ATI, I didn't have a second monitor attached (although when in the office I do have one) and I'm already running with the nomodeset option due to RHBZ bug 529883
I'm not an X-pert, but I seem to recall someone also hitting bug#533236 who was using nouveau with a single monitor (see https://bugzilla.redhat.com/show_bug.cgi?id=533236#c11). I've confirmed that my dual-monitor ATI issue is resolved using the latest kernel (http://koji.fedoraproject.org/koji/buildinfo?buildID=139823) and xorg-x11-server (http://koji.fedoraproject.org/koji/buildinfo?buildID=140035). I believe you'll also want the latest nouveau (http://koji.fedoraproject.org/koji/buildinfo?buildID=139811).
Can you please retest with those packages and provide feedback?
Thanks James, I'll need to investigate this tomorrow as today I need a working machine.
Please do try a later version; 1.7.1-3 is known bad.
Known bad in what way? I seem to have a US keyboard back again but at least I have what otherwise seems to be a working system. The others wouldn't give me X and I need a stable system tonight for work.
that actually makes sense, because the thing that broke it for you was introduced in 1.7.1-5. (as a fix for a different bug introduced by 1.7.1-3).
this is 99.99% certainly a duplicate of 533236, the traceback is identical and the bug was somewhat unpredictable, i.e., it's not certain you needed KMS or dual displays to hit it, it depended on your exact circumstances.
Please test 1.7.1-7, I am sure it will work for you, and since this was placed on the blocker list we need to be sure.
Fedora Bugzappers volunteer triage team
I can confirm now that 1.7.1-7 fixes the problem
*** This bug has been marked as a duplicate of bug 533236 ***