On 09/21/2010 03:43 PM, Kevin Martin wrote: > > On 09/21/2010 03:24 PM, Kevin Martin wrote: >> So I'm using the latest unstable version of Chrome browser, updated my kernel today, and BAM, when I try to view a video on cnn.com >> Xorg crashes. This just started happening today (I've been running this version of the chrome browser for a solid week or more). >> Here's the backtrace from the Xorg.0.log.old for anybody who's interested: >> >> Backtrace: >> [ 9854.608] 0: /usr/bin/X (xorg_backtrace+0x3c) [0x80ddfac] >> [ 9854.608] 1: /usr/bin/X (0x8047000+0x60826) [0x80a7826] >> [ 9854.608] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb6040c] >> [ 9854.608] 3: /usr/bin/X (miModifyPixmapHeader+0x2b) [0x81b8bfb] >> [ 9854.608] 4: /usr/lib/xorg/modules/libexa.so (0x21d000+0x5fa1) [0x222fa1] >> [ 9854.608] 5: /usr/lib/xorg/modules/libexa.so (0x21d000+0x6368) [0x223368] >> [ 9854.608] 6: /usr/bin/X (0x8047000+0x4dbd1) [0x8094bd1] >> [ 9854.608] 7: /usr/bin/X (0x8047000+0x51ab7) [0x8098ab7] >> [ 9854.608] 8: /usr/bin/X (0x8047000+0x1b595) [0x8062595] >> [ 9854.608] 9: /lib/libc.so.6 (__libc_start_main+0xe6) [0x2b6cc6] >> [ 9854.608] 10: /usr/bin/X (0x8047000+0x1b181) [0x8062181] >> [ 9854.608] Segmentation fault at address (nil) >> [ 9854.608] >> Fatal server error: >> [ 9854.608] Caught signal 11 (Segmentation fault). Server aborting >> [ 9854.608] >> [ 9854.608] >> Please consult the Fedora Project support >> at http://bodhi.fedoraproject.org/ >> for help. >> [ 9854.608] Please also check the log file at "/var/log/Xorg.0.log" for additional information. >> [ 9854.608] >> [ 9854.613] (II) Power Button: Close >> [ 9854.613] (II) UnloadModule: "evdev" >> [ 9854.617] (II) Power Button: Close >> [ 9854.617] (II) UnloadModule: "evdev" >> [ 9854.621] (II) Sleep Button: Close >> [ 9854.621] (II) UnloadModule: "evdev" >> [ 9854.629] (II) Logitech USB Optical Mouse: Close >> [ 9854.629] (II) UnloadModule: "evdev" >> [ 9854.633] (II) AT Translated Set 2 keyboard: Close >> [ 9854.633] (II) UnloadModule: "evdev" >> [ 9854.644] (II) UnloadModule: "synaptics" >> [ 9854.644] (II) AIGLX: Suspending AIGLX clients for VT switch >> >> Problem is, I don't think that abrtd is reporting the crash, but I'm not sure. How can I tell? >> >> Thanks >> >> Kevin Martin >> >> >> > Actually, it turns out it looks like *any* video causes the crash. Was watching a video from ebaumsworld and it crashed too. > Backtrace appears to be the same as before. > > Backtrace: > [ 10537.325] 0: /usr/bin/X (xorg_backtrace+0x3c) [0x80ddfac] > [ 10537.325] 1: /usr/bin/X (0x8047000+0x60826) [0x80a7826] > [ 10537.325] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x2d840c] > [ 10537.325] 3: /usr/bin/X (miModifyPixmapHeader+0x2b) [0x81b8bfb] > [ 10537.325] 4: /usr/lib/xorg/modules/libexa.so (0x1b3000+0x5fa1) [0x1b8fa1] > [ 10537.325] 5: /usr/lib/xorg/modules/libexa.so (0x1b3000+0x6368) [0x1b9368] > [ 10537.326] 6: /usr/bin/X (0x8047000+0x4dbd1) [0x8094bd1] > [ 10537.326] 7: /usr/bin/X (0x8047000+0x51ab7) [0x8098ab7] > [ 10537.326] 8: /usr/bin/X (0x8047000+0x1b595) [0x8062595] > [ 10537.326] 9: /lib/libc.so.6 (__libc_start_main+0xe6) [0x662cc6] > [ 10537.326] 10: /usr/bin/X (0x8047000+0x1b181) [0x8062181] > [ 10537.326] Segmentation fault at address (nil) > [ 10537.326] > Fatal server error: > [ 10537.326] Caught signal 11 (Segmentation fault). Server aborting > [ 10537.326] > [ 10537.326] > > > Kevin So good news and bad (kind of). It's not strictly related to Chrome. I've also just had this blow up when watching the cnn.com video in FireFox4 Beta (although it didn't cause X to crash when watching the video on ebaumsworld). Same crash as above. Kevin -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines