libX11 segfault

Nubsy · 2011-12-03 02:26:34

I have arch running on a Thinkpad t510.

It has an Nvidia3100M graphics card. Somewhat recently, I can't quite remember when, it started randomly crashing to the login screen. As you can imagine, this is incredibly frustrating, especially when doing something. At first I thought it may have been the Nvidia drivers, so I switched to Nouveau (which actually seems slower), but it still persisted. I thought maybe it was a glitch in Gnome3, so I installed XFCE. No change. Checking the Xorg log, it tells me there was a segmentation fault and the server aborted.
The last time it crashed (about 10 minutes ago), the log shows this:

Backtrace:
[ 15377.756] 0: /usr/bin/Xorg (xorg_backtrace+0x37) [0x81c0057]
[ 15377.756] 1: /usr/bin/Xorg (0x8048000+0x4800d) [0x809000d]
[ 15377.756] 2: /usr/bin/Xorg (0x8048000+0x156757) [0x819e757]
[ 15377.756] 3: /usr/bin/Xorg (mieqProcessDeviceEvent+0x93) [0x819e8a3]
[ 15377.756] 4: /usr/bin/Xorg (mieqProcessInputEvents+0x48) [0x819ea78]
[ 15377.756] 5: /usr/bin/Xorg (ProcessInputEvents+0x14) [0x80b3654]
[ 15377.756] 6: /usr/bin/Xorg (0x8048000+0x2e441) [0x8076441]
[ 15377.756] 7: /usr/bin/Xorg (0x8048000+0x1c37a) [0x806437a]
[ 15377.756] 8: /lib/libc.so.6 (__libc_start_main+0xf3) [0xb753e243]
[ 15377.756] 9: /usr/bin/Xorg (0x8048000+0x1c6a9) [0x80646a9]
[ 15377.756] 
Fatal server error:
[ 15377.756] Wrong event type 0. Aborting server
[ 15377.756] 
[ 15377.756]

However, sometimes it gives an error 11.

Checking Dmesg and piping in grep to look for 'seg', I get:

[matt@matt-laptop ~]$ dmesg | grep seg
[  177.594483] chromium[1534]: segfault at 0 ip b396af95 sp bfc9e090 error 4 in libX11.so.6.3.0[b3931000+132000]
[  217.393616] chromium[1620]: segfault at 0 ip b388ef95 sp bf8ab2d0 error 4 in libX11.so.6.3.0[b3855000+132000]
[  260.902507] chromium[1626]: segfault at 730036 ip b14631ba sp bff2e8e0 error 4 in nouveau_dri.so[b12c2000+cb5000]
[  261.307867] chromium[1524]: segfault at 9 ip b511b550 sp bfda0670 error 4 in chromium[b3a5a000+3dda000]
[  277.847890] chromium[1646]: segfault at 0 ip b396cf95 sp bfc37d70 error 4 in libX11.so.6.3.0[b3933000+132000]
[  281.862182] chromium[1654]: segfault at 0 ip b380bf95 sp bfb94530 error 4 in libX11.so.6.3.0[b37d2000+132000]
[  304.374679] chromium[1661]: segfault at 730036 ip b14d71ba sp bfe76a80 error 4 in nouveau_dri.so[b1336000+cb5000]
[  681.326174] chromium[1741]: segfault at 0 ip b3802f95 sp bfe7b090 error 4 in libX11.so.6.3.0[b37c9000+132000]
[  882.222275] chromium[1750]: segfault at 4 ip b13b31ba sp bfd4a370 error 4 in nouveau_dri.so[b1212000+cb5000]
[  891.985357] chromium[1757]: segfault at 0 ip b3959f95 sp bfd0db10 error 4 in libX11.so.6.3.0[b3920000+132000]
[  892.353693] chromium[1761]: segfault at 0 ip b39d2f95 sp bfb202b0 error 4 in libX11.so.6.3.0[b3999000+132000]
[  892.650085] chromium[1765]: segfault at 0 ip b37fbf95 sp bf9b6f00 error 4 in libX11.so.6.3.0[b37c2000+132000]
[  892.799934] chromium[1769]: segfault at 0 ip b387ef95 sp bfccae00 error 4 in libX11.so.6.3.0[b3845000+132000]
[ 1997.844240] chromium[2256]: segfault at 0 ip b3842f95 sp bf9d46e0 error 4 in libX11.so.6.3.0[b3809000+132000]
[ 4467.343024] chromium[3223]: segfault at 0 ip b384df95 sp bf8d2bb0 error 4 in libX11.so.6.3.0[b3814000+132000]
[ 4468.465762] chromium[3227]: segfault at 0 ip b3845f95 sp bf821230 error 4 in libX11.so.6.3.0[b380c000+132000]
[ 6666.722529] chromium[4100]: segfault at 0 ip b39def95 sp bfd75780 error 4 in libX11.so.6.3.0[b39a5000+132000]
[ 8405.657373] chromium[1633]: segfault at 40680075 ip b4bc9070 sp bfda0690 error 6 in chromium[b3a5a000+3dda000]
[ 8408.892328] chromium[4963]: segfault at 0 ip b395af95 sp bfd3f620 error 4 in libX11.so.6.3.0[b3921000+132000]
[ 9154.110340] chromium[5067]: segfault at 0 ip b3911f95 sp bfdcbfc0 error 4 in libX11.so.6.3.0[b38d8000+132000]
[ 9175.114782] chromium[5078]: segfault at 0 ip b3969f95 sp bfb45380 error 4 in libX11.so.6.3.0[b3930000+132000]
[11216.689290] chromium[5253]: segfault at 0 ip b37f2f95 sp bfbcac20 error 4 in libX11.so.6.3.0[b37b9000+132000]
[12399.493768] chromium[5360]: segfault at 74 ip b145f406 sp bfb5b2b0 error 4 in nouveau_dri.so[b12be000+cb5000]
[14925.876646] gnome-shell[1256]: segfault at 1c ip b442d243 sp bfc6d010 error 4 in nouveau_dri.so[b42c6000+cb5000]
[14993.043247] chromium[1538]: segfault at 8107119f ip b0986d53 sp bfff028c error 4 in libflashplayer.so[b07b2000+fc8000]
[15007.149943] chromium[4955]: segfault at 8d4c4198 ip b474cc19 sp bfd9f610 error 4 in chromium[b3a5a000+3dda000]
[15012.590773] chromium[7712]: segfault at d2214e00 ip b083dd53 sp bfcbcfac error 5 in libflashplayer.so[b0669000+fc8000]
[15029.908502] chromium[7748]: segfault at 0 ip b38c2f95 sp bfc793b0 error 4 in libX11.so.6.3.0[b3889000+132000]
[15068.172591] chromium[7788]: segfault at 10 ip b4c48602 sp bfda10d0 error 4 in chromium[b3a5a000+3dda000]
[15108.182255] chromium[7952]: segfault at 0 ip b398cf95 sp bfe15890 error 4 in libX11.so.6.3.0[b3953000+132000]
[15192.366900] chromium[8100]: segfault at 0 ip b398ff95 sp bfa405c0 error 4 in libX11.so.6.3.0[b3956000+132000]
[15197.070312] chromium[8106]: segfault at b0c2464 ip 44ef6f92 sp bf85f304 error 6
[15221.086428] chromium[8142]: segfault at 0 ip b3989f95 sp bfc55860 error 4 in libX11.so.6.3.0[b3950000+132000]
[15253.186948] chromium[8284]: segfault at 0 ip b3848f95 sp bff858b0 error 4 in libX11.so.6.3.0[b380f000+132000]
[15367.798876] chromium[8461]: segfault at 0 ip b3934f95 sp bfa9ad50 error 4 in libX11.so.6.3.0[b38fb000+132000]

I've googled up and down and cannot find anything that pertains to my problem. The other major problem is that flashplugin crashes almost immediately. Now, I know that it's asked that we keep one problem per thread, but I get a sneaking feeling the two may be somehow linked.

If anyone has any idea, I'd really appreciate it. My sanity rests in your hands.

kanja · 2012-01-07 18:51:51

I'm having the exact same problem on a thinkpad 410s - flash crashing, chromium/crome segfaults, x crashing.

I was getting really bad crashing with flashplugin-beta - I also got a less descriptive error message from the x server's crash. Switching to plain flashplugin improved stability a little and changed the error message to match yours. Are you also getting your mouse cursor stuck in the upper left corner?

bovis · 2012-01-15 20:07:59

I am receiving a similar error. I can't find any segfault, but my system is crashing and it always happens when I'm in a web browser. I thought, at first, that it was Firefox. But I have since switched to uzbl, which uses a completely different stucture, and I continue to have problems.

The browser will crash, then I'm booted out of X, and then the command line refuses to accept commands, forcing me to cold shut down my tower. I am unable to replicate the crash by going to any specific website; I have not seen a correlation between the crashing and usage of Flash.

My graphics card is an NVIDIA GeForce FX5200.

This is the output I was able to capture when I was booted out of X. Uzbl is my browser, /dev/sd5 is my slash partition.

OSError: [Errno 30] Read-only file system: '~/.local/share/uzbl'
Traceback (most recent last call):
File "/usr/bin/uzbl-tabbed", line 1018, in tab_closed
File "/usr/bin/uzbl-tabbed", line 1237, in quit
File "/usr/bin/uzbl-tabbed", line 802, in close_socket
OSError: [Errno 30] Read-only file system: '/tmp/usbl-tabbed_1093.socket'
** (uzbl-core: 1550): WARNING **: Error reading: Connection reset by peer
** (uzbl-core: 1095): WARNING **: Error flushing: Broken pipe
fluxbox: No such file or directory
fluxbox: No such file or directory
xinit: Connection to X server lost
XIO: Fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 27800 requests (27795 known processed) with 0 events remaining
[1922.448608] EXT3-fs error (device sda5): ext3_find_entry: reading directory #390913 offset 0
[1923.121798\ EXT3-fs (sda5): IO error while writing superblock

Any help is appreciated. Thanks in advance.

XenGi · 2016-12-22 17:44:40

I have the same error on my Thinkpad X250. The crash happens only when I exit a youtube video in fullscreen mode but not everytime. Haven't tested chromium or firefox yet. Using google-chrome-stable atm.

in dmesg I see:

[31515.372076] chrome[8496]: segfault at 968 ip 00007fe8ba4bd3a3 sp 00007ffe89de0e60 error 4 in libX11.so.6.3.0[7fe8ba490000+139000]
[32015.260262] chrome[14593]: segfault at 968 ip 00007f98f42893a3 sp 00007ffdf1526fd0 error 4 in libX11.so.6.3.0[7f98f425c000+139000]
[61790.991757] chrome[10670]: segfault at 968 ip 00007f1333e563a3 sp 00007ffe8df3bc90 error 4 in libX11.so.6.3.0[7f1333e29000+139000]
[71486.810054] chrome[19337]: segfault at 968 ip 00007fbc4e93f3a3 sp 00007ffce48d9460 error 4 in libX11.so.6.3.0[7fbc4e912000+139000]

Are there any news on this? This is very annoying.

R00KIE · 2016-12-22 18:09:07

This is quite an old thread, necro-bumping is one of the things you should not do[1].

You should open a new thread as most probably your problem is different. Closing.

[1] https://wiki.archlinux.org/index.php/Co … bumping.22

Arch Linux

#1 2011-12-03 02:26:34

libX11 segfault

#2 2012-01-07 18:51:51

Re: libX11 segfault

#3 2012-01-15 20:07:59

Re: libX11 segfault

#4 2016-12-22 17:44:40

Re: libX11 segfault

#5 2016-12-22 18:09:07

Re: libX11 segfault

Board footer