Description of problem: after update my system, i can't start X server Version-Release number of selected component (if applicable): [root@timelock ~]# cat /etc/redhat-release Fedora release 16 (Rawhide) [root@timelock ~]# uname -a Linux timelock.rtcomm.ru 2.6.39-0.rc3.git2.0.fc16.i686 #1 SMP Wed Apr 13 17:53:18 UTC 2011 i686 i686 i386 GNU/Linux xorg-x11-server-Xorg-1.10.99.1-2.20110418.fc16.i686 xorg-x11-drv-intel-2.15.0-2.fc16.i686 How reproducible: update system and try to load X server Steps to Reproduce: 1. 2. 3. Actual results: i can't load my lxde :( Expected results: in runlevel 5, i can work, surf web, and so on :) Additional info: Backtrace: [ 137.931] 0: /usr/bin/X (xorg_backtrace+0x3c) [0x80a38ec] [ 137.931] 1: /usr/bin/X (0x8048000+0x600e6) [0x80a80e6] [ 137.931] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x3d240c] [ 137.931] 3: /usr/lib/libdrm_intel.so.1 (0x606000+0x43c7) [0x60a3c7] [ 137.931] 4: /usr/lib/libdrm_intel.so.1 (drm_intel_bufmgr_check_aperture_space+0x1b) [0x6077fb] [ 137.931] 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x110000+0x1ea25) [0x12ea25] [ 137.931] 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x110000+0x1fdd2) [0x12fdd2] [ 137.931] 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x110000+0x2a8e2) [0x13a8e2] [ 137.932] 8: /usr/bin/X (0x8048000+0xde0bf) [0x81260bf] [ 137.932] 9: /usr/bin/X (CompositeGlyphs+0xb1) [0x81b68d1] [ 137.932] 10: /usr/bin/X (0x8048000+0xd89c8) [0x81209c8] [ 137.932] 11: /usr/bin/X (0x8048000+0xd22d4) [0x811a2d4] [ 137.932] 12: /usr/bin/X (0x8048000+0x29227) [0x8071227] [ 137.932] 13: /usr/bin/X (0x8048000+0x1c1cc) [0x80641cc] [ 137.932] 14: /lib/libc.so.6 (__libc_start_main+0xf3) [0x4d4b7513] [ 137.932] 15: /usr/bin/X (0x8048000+0x1c4f1) [0x80644f1] [ 137.933] Segmentation fault at address 0x4064 [ 137.933] Fatal server error: [ 137.933] Caught signal 11 (Segmentation fault). Server aborting [ 137.933] [ 137.933] Please consult the Fedora Project support at http://wiki.x.org for help. [ 137.933] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
*** This bug has been marked as a duplicate of bug 698237 ***