Created attachment 493496 [details] log file Description of problem: X Crashes.
Lovely backtrace, indeed! Backtrace: [ 916.713] 0: X (xorg_backtrace+0x2f) [0x45e17f] [ 916.713] 1: X (0x400000+0x62b96) [0x462b96] [ 916.714] 2: /lib64/libpthread.so.0 (0x3ed0c00000+0xf3c0) [0x3ed0c0f3c0] [ 916.714] 3: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f22308b7000+0xeab9) [0x7f22308c5ab9] [ 916.714] 4: X (AddScreen+0x17f) [0x42ee1f] [ 916.714] 5: X (InitOutput+0x282) [0x471ca2] [ 916.714] 6: X (0x400000+0x22a39) [0x422a39] [ 916.714] 7: /lib64/libc.so.6 (__libc_start_main+0xed) [0x3ed082143d] [ 916.714] 8: X (0x400000+0x22ee1) [0x422ee1] [ 916.715] Segmentation fault at address 0xffffffffffecca4c [ 916.715] Fatal server error: [ 916.715] Caught signal 11 (Segmentation fault). Server aborting [ 916.715] Could we have versions of xorg-x11-server and xorg-x11-drv-intel, please? Thank you
If you back down to xorg-x11-server-Xorg-1.10.1-9.fc15.x86_64 it works.
With these versions: xorg-x11-drv-intel-2.15.0-2.fc16.x86_64 xorg-x11-server-1.10.99.1-3.20110418.fc16 It blows up.
(In reply to comment #2) > If you back down to xorg-x11-server-Xorg-1.10.1-9.fc15.x86_64 it works. Yes, you're right and from the fedora-devel post by ajax (http://article.gmane.org/gmane.linux.redhat.fedora.devel/147699) it looks like a known bug. We are sorry.
*** Bug 698227 has been marked as a duplicate of this bug. ***
*** Bug 698334 has been marked as a duplicate of this bug. ***
*** Bug 699177 has been marked as a duplicate of this bug. ***
*** Bug 699277 has been marked as a duplicate of this bug. ***
*** Bug 702182 has been marked as a duplicate of this bug. ***
*** Bug 701623 has been marked as a duplicate of this bug. ***
(In reply to comment #4) > (In reply to comment #2) > > If you back down to xorg-x11-server-Xorg-1.10.1-9.fc15.x86_64 it works. > > Yes, you're right and from the fedora-devel post by ajax > (http://article.gmane.org/gmane.linux.redhat.fedora.devel/147699) it looks like > a known bug. We are sorry. That thread just says "Rawhide's X is going to be like that for a while."
I have run into this with both my NVidia and AMD drivers and getting back down to a previous version of X is a manual process. Shouldn't there be dependencies set within the RPMs to indicate a specific version of X is required and not allow you to drive off the cliff if that version isn't available? Isn't that why we use RPM and Yum?
The main drivers are rebuilt, this should hopefully fix the issues. Intel build: http://koji.fedoraproject.org/koji/taskinfo?taskID=3062113 ATI build: http://koji.fedoraproject.org/koji/taskinfo?taskID=3062122 Nouveau build: http://koji.fedoraproject.org/koji/taskinfo?taskID=3062143 I'll rebuild the other less-used drivers too, but please let us know if this fixes the issue.
*** Bug 702956 has been marked as a duplicate of this bug. ***
I have tried it on my NVidia powered laptop with the nouveau driver and it works nicely. Thank you. I can't test my AMD powered machine until tomorrow but will post the results when I do.
Please redo the nvr to be > F15 versions xorg-x11-drv-ati-6.14.0-9.20110316gitcdfc007ec.fc16 xorg-x11-drv-ati-6.14.1-1.20110504gita6d2dba6.fc15
With these packages: [andy@timelock ~]$ rpm -qa | egrep "(server-common|intel)" xorg-x11-server-common-1.10.99.1-5.20110510.fc16.i686 xorg-x11-drv-intel-2.15.0-4.fc16.i686 [andy@timelock ~]$ My X Window system works fine. Thank you. [andy@timelock ~]$ dmesg | grep -i chipset [ 1.478614] agpgart-intel 0000:00:00.0: Intel G41 Chipset [andy@timelock ~]$
Solved for me as well, [stijn@pounce] <~/Documents/Fedora/Bugs/698237> rpm -qa | egrep "(server-common|intel)" xorg-x11-drv-intel-2.15.0-4.fc16.x86_64 xorg-x11-server-common-1.10.99.1-5.20110510.fc16.x86_64 [stijn@pounce] <~/Documents/Fedora/Bugs/698237> sudo grep -i chipset /var/log/messages May 1 15:01:49 pounce kernel: [ 0.976223] agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset
All drivers are rebuilt now and should have found their way into the rawhide compose. Reports so far are positive, so I'm closing this bug. Thanks for testing, sorry about this bug, it shouldn't have happened.