Arch Linux

tbhartman

Member

Registered: 2011-01-25

Posts: 5

GNOME becomes unresponsive "randomly"

I've been using Arch for ~2 months and am having an issue with GNOME becoming unresponsive and am not sure how to diagnose the problem.

I've looked at the following post: https://bbs.archlinux.org/viewtopic.php?id=100843
but not sure if it relates.  As far as I can tell, the times it happens most are when I have a web browser open (google-chrome 9.0.597.94-1 from AUR) or when I try to run KeePass (keepass 2.14-2 from the AUR).  I can still move the cursor around the screen, but cannot manipulate anything and the clock in my panel does not update.  Sometimes I can CTRL-ALT-1 to get to a terminal, though other times even that seems unresponsive.

Until recently I've not noticed anything in a log file that is helpful to me, but today while working (web browser open, but working with different app) I got this at the end of my Xorg.0.log after starting into a terminal:

Fatal server error:
[ 72998.009] Caught signal 11 (Segmentation fault). Server aborting
[ 72998.009] 
[ 72998.009] 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
[ 72998.009] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 72998.009] 
[ 73001.888] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[ 73001.888] 

Later, when I went to open KeePass, I got this from Xorg.0.log:

Backtrace:
[   531.595] 0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49f718]
[   531.595] 1: /usr/bin/Xorg (0x400000+0x60349) [0x460349]
[   531.595] 2: /lib/libpthread.so.0 (0x7f45ae62a000+0xf150) [0x7f45ae639150]
[   531.595] 3: /lib/libc.so.6 (0x7f45ad58c000+0x742ae) [0x7f45ad6002ae]
[   531.595] 4: /lib/libc.so.6 (__libc_malloc+0x70) [0x7f45ad602460]
[   531.595] 5: /usr/lib/xorg/modules/libexa.so (0x7f45aaeb6000+0x8ca4) [0x7f45aaebeca4]
[   531.595] 6: /usr/lib/xorg/modules/libexa.so (0x7f45aaeb6000+0x13151) [0x7f45aaec9151]
[   531.595] 7: /usr/lib/xorg/modules/libexa.so (0x7f45aaeb6000+0xea6c) [0x7f45aaec4a6c]
[   531.595] 8: /usr/lib/xorg/modules/libexa.so (0x7f45aaeb6000+0x1132a) [0x7f45aaec732a]
[   531.595] 9: /usr/bin/Xorg (0x400000+0xd2b41) [0x4d2b41]
[   531.595] 10: /usr/bin/Xorg (0x400000+0x2d201) [0x42d201]
[   531.595] 11: /usr/bin/Xorg (0x400000+0x2131e) [0x42131e]
[   531.595] 12: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f45ad5aadcd]
[   531.595] 13: /usr/bin/Xorg (0x400000+0x20ec9) [0x420ec9]
[   531.595] Segmentation fault at address (nil)
[   531.595] 
Fatal server error:
[   531.595] Caught signal 11 (Segmentation fault). Server aborting
[   531.595] 
[   531.595] 
Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
[   531.595] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   531.595] 

System info:
uname -a gives:

Linux eleutheroi 2.6.37-ARCH #1 SMP PREEMPT Tue Mar 8 08:34:35 CET 2011 x86_64 Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz GenuineIntel GNU/Linux

I'm running on a ThinkPad R60 with an ATI Mobility Radeon X1400.

Thoughts or suggestions?  Thanks!

kett

Member

Registered: 2008-04-21

Posts: 104

Re: GNOME becomes unresponsive "randomly"

Same problem here.  I've got an ATI card running GNOME as well.

lives2evil

Member

From: GMT+7

Registered: 2010-03-21

Posts: 244

Re: GNOME becomes unresponsive "randomly"

Perhaps a ati driver errors. Try using vesa instead.

---

tsujeruplive, tnarongisi... ... ... ... ɥsılƃuǝ sı sıɥʇ

tbhartman

Member

Registered: 2011-01-25

Posts: 5

Re: GNOME becomes unresponsive "randomly"

Perhaps a ati driver errors. Try using vesa instead.

I am currently using:  xf86-video-vesa 2.3.0-3

kett

Member

Registered: 2008-04-21

Posts: 104

Re: GNOME becomes unresponsive "randomly"

I actually get the problems on GNOME, XFCE4 and OpenBox.  I was having others issues with KDE4, and I'm not sure if they are related.

thegritche

Member

Registered: 2010-08-23

Posts: 2

Re: GNOME becomes unresponsive "randomly"

I also have this problem, using latest kernel. It appears while launching firefox or rekonq, and disappeared when I killed firefox. Have you been able to solve this problem ?

Thanks.