Created attachment 373790 [details] Xorg log from crashed session Description of problem: When attempting to view a certain web page (http://kar3ning.livejournal.com/545639.html) in a maximised Firefox window, the X server crashes (segfault) and restarts I can view the page when the browser window is not maximised. When the window is maximised, the crash happens. I can load the page in a background tab without issue. When I switch to the tab, the crash happens. I can view the page in Opera without issues. I have tested with a fresh Firefox profile as well as my usual profile. Version-Release number of selected component (if applicable): Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.5) Gecko/20091105 Fedora/3.5.5-1.fc12 Firefox/3.5.5 xorg-x11-server-Xorg-1.7.1-7.fc12.x86_64 xorg-x11-drv-ati-6.13.0-0.10.20091006git457646d73.fc12.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a fresh Firefox profile (firefox -p) 2. Browse to http://kar3ning.livejournal.com/545639.html 3. Maximise Firefox window Actual results: My X session is lost. The server restarts instantly, showing me the GDM login screen. Expected results: I can view the page just like any other on the web, without losing my session and potentially losing data in applications unrelated to my web browser. Additional info: Possibly a radeon driver issue? I have a RV530 [Radeon X1600] I will post any other urls I find that cause this issue.
Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49e8d8] 1: /usr/bin/Xorg (0x400000+0x619c9) [0x4619c9] 2: /lib64/libpthread.so.0 (0x3567200000+0xefa0) [0x356720efa0] 3: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f84e9c3b000+0xd507f) [0x7f84e9d1007f] 4: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f84e9c3b000+0x9f5b5) [0x7f84e9cda5b5] 5: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f84e9c3b000+0xa1b35) [0x7f84e9cdcb35] 6: /usr/lib64/xorg/modules/libexa.so (0x7f84e904c000+0xd1b9) [0x7f84e90591b9] 7: /usr/lib64/xorg/modules/libexa.so (0x7f84e904c000+0xe697) [0x7f84e905a697] 8: /usr/bin/Xorg (0x400000+0xd1c80) [0x4d1c80] 9: /usr/bin/Xorg (0x400000+0xcb80e) [0x4cb80e] 10: /usr/bin/Xorg (0x400000+0x2c69c) [0x42c69c] 11: /usr/bin/Xorg (0x400000+0x21cfa) [0x421cfa] 12: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3566a1eb1d] 13: /usr/bin/Xorg (0x400000+0x218a9) [0x4218a9] Segmentation fault at address 0x20 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting
Attempting to Preview (not post) a comment on scienceblogs.com also triggers the crash. From Xorg.log: Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49e8d8] 1: /usr/bin/Xorg (0x400000+0x619c9) [0x4619c9] 2: /lib64/libpthread.so.0 (0x3567200000+0xefa0) [0x356720efa0] 3: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f2e0ed32000+0xd507f) [0x7f2 e0ee0707f] 4: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f2e0ed32000+0x9f5b5) [0x7f2 e0edd15b5] 5: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f2e0ed32000+0xa1b35) [0x7f2 e0edd3b35] 6: /usr/lib64/xorg/modules/libexa.so (0x7f2e0e143000+0xd1b9) [0x7f2e0e1501b9] 7: /usr/lib64/xorg/modules/libexa.so (0x7f2e0e143000+0xe697) [0x7f2e0e151697] 8: /usr/bin/Xorg (0x400000+0xd1c80) [0x4d1c80] 9: /usr/bin/Xorg (0x400000+0xcb80e) [0x4cb80e] 10: /usr/bin/Xorg (0x400000+0x2c69c) [0x42c69c] 11: /usr/bin/Xorg (0x400000+0x21cfa) [0x421cfa] 12: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3566a1eb1d] 13: /usr/bin/Xorg (0x400000+0x218a9) [0x4218a9] Segmentation fault at address 0x20 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting
I'm having similar problems with my system as well. I'm running F12 x86_64 on a Phenom II with a Radeon 1950 pro. My system worked fine when I first installed it earlier this month. The system is configured to automatically install updates each night. An updated package of some sort was installed 2 or 3 days ago and this behavior emerged. The work around that I've found is to use X -configure to create an xorg.conf file and then specify the "vesa" driver. X no longer crashes, but the performance is obviously limited.
*** This bug has been marked as a duplicate of bug 528390 ***