Solved LXDE crash

balanga

Son of Beastie

Reaction score: 137
Messages: 3,059

Further to my previous Thread 70744 I started a new one as the problem seems to be more specific to LXDE. After installing XFCE the system is stable and the previous crashes do not appear.

I've been using LXDE for quite a while now and it has proved to be fairly stable on systems which had it installed some time ago, however it seems unstable on systems on which it has been installed recently, which makes me wonder if there is an underlying problem in a recent release of one of the dependent programs of which there are fifteen x11/lxde-meta one of which - x11-wm/lxsession is fairly recent.

Is it possible to identify this program as the cause of a crash?
 
OP
OP
B

balanga

Son of Beastie

Reaction score: 137
Messages: 3,059

Do you see your error logs in the log folder?
Do you mean /var/log/Xorg.0.log ?

Here is part of it:- (means nothing to me)...

Code:
[   667.421] (II) sysmouse: SetupAuto: protocol is SysMouse
[   667.421] (II) config/devd: device /dev/ums0 already opened
[   741.603] (EE).
[   741.604] (EE) Backtrace:
[   741.606] (EE) 0: ? (?+0x111ea08) [0x80151e428]
[   741.608] (EE) 1: /lib/libthr.so.3 (pthread_sigmask+0x544) [0x800ae9924]
[   741.609] (EE) 2: /lib/libthr.so.3 (pthread_getspecific+0xe12) [0x800ae96f2]
[   741.611] (EE) 3: ? (?+0xe12) [0x7ffffffffe15]
[   741.614] (EE) 4: /lib/libc.so.7 (memcpy+0x88) [0x800cb8820]
[   741.617] (EE) 5: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x80274dac8]
[   741.619] (EE) 6: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x802487a68]
[   741.620] (EE) 7: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x802486d18]
[   741.621] (EE) 8: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x80248e0b8]
[   741.623] (EE) 9: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x802187608]
[   741.624] (EE) 10: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x8021879f8]
[   741.625] (EE) 11: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x80248f778]
[   741.626] (EE) 12: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x80248ea38]
[   741.627] (EE) 13: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x802179ad8]
[   741.629] (EE) 14: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x802173158]
[   741.630] (EE) 15: /usr/local/lib/dri/i965_dri.so (?+0x88) [0x802173368]
[   741.631] (EE) 16: /usr/local/lib/xorg/modules/libglamoregl.so (?+0x88) [0x801af98d8]
[   741.633] (EE) 17: /usr/local/lib/xorg/modules/libglamoregl.so (?+0x88) [0x801af9c48]
[   741.634] (EE) 18: /usr/local/lib/xorg/modules/libglamoregl.so (?+0x88) [0x801aedd48]
[   741.635] (EE) 19: /usr/local/bin/X (?+0x88) [0x378f88]
[   741.637] (EE) 20: /usr/local/bin/X (?+0x88) [0x2879d8]
[   741.638] (EE) 21: /usr/local/bin/X (?+0x88) [0x284908]
[   741.639] (EE) 22: /usr/local/bin/X (?+0x88) [0x28e1b8]
[   741.640] (EE) 23: /usr/local/bin/X (?+0x88) [0x278088]
[   741.641] (EE) 24: ? (?+0x88) [0x800438088]
[   741.641] (EE).
[   741.641] (EE) Segmentation fault at address 0x3c6db8
[   741.641] (EE).
Fatal server error:
[   741.641] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   741.641] (EE).
[   741.641] (EE).
Please consult the The X.Org Foundation support.
<------> at http://wiki.x.org
 for help..
[   741.641] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   741.641] (EE).
[   741.642] (II) AIGLX: Suspending AIGLX clients for VT switch
[   741.983] (EE) Server terminated with error (1). Closing log file.
I'm using the supplied configuration - no customisation.
 

Zirias

Aspiring Daemon

Reaction score: 218
Messages: 602

I guess he meant ~/.xsession-errors ... but your /var/log/Xorg.0.log shows it is actually your X server crashing, not the desktop running on it. It might trigger the crash by using some direct drawing or video decoding functionality.

So the first thing I'd look into: Are you using the up-to-date drm drivers from graphics/drm-kmod? The kernel still includes drm drivers (unfortunately), but they are out of date, don't use them. This also means for now that you need the full path (/boot/modules/xxxxxx.ko) in /etc/rc.conf for loading the drm driver.

If you can't find the issue, you can still use your system without DRM, of course with the typical implications on features and performance.
 
OP
OP
B

balanga

Son of Beastie

Reaction score: 137
Messages: 3,059

Installing the updated drivers solved the problem. Many thanks.
 
Top