[CALUG] Sudden logout

Howard how0909 at freeshell.org
Sat Dec 9 12:05:54 EST 2017



On 12/09/2017 12:21 AM, Bernard Karmilowicz wrote:
> Good morning, Howard;
>
>
>> I have had this laptop suddenly logout
>> How can I track down what is happening?
>> This is Fedora 25 on a 7yr old ASUS laptop.
>
> If you are using the X Window server (xorg) then:
>
> 1. Examining the X Window server log files may provide a clue where to 
> direct further attention:
>
>     /var/log/Xorg.0.log
>     /var/log/Xorg.0.log.old
>
> The Xorg.0.old file will likely have more useful information than the 
> log for your current session (Xorg.0.log). I would start reading from 
> the bottom of the Xorg.0.old file upward. The last line in the file 
> should be something to the effect of when the session terminates 
> normally:
>
>     "Server terminated successfully (0). Closing log file."
>
Well not what I'm seeing:)

tail  -n30 /var/log/Xorg.0.log.old
...
[ 28259.027] (II) input device 'Logitech USB-PS/2 Optical Mouse', 
/dev/input/event5 is a pointer caps
[ 39968.568] (EE)
[ 39968.568] (EE) Backtrace:
[ 39968.655] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59ea19]
[ 39968.658] (EE) 1: /lib64/libpthread.so.0 (funlockfile+0x50) 
[0x7f4cfaf0f61f]
[ 39968.660] (EE) 2: /lib64/libdrm_radeon.so.1 (_init+0x6c8) 
[0x7f4cf725e358]
[ 39968.662] (EE) 3: /lib64/libdrm_radeon.so.1 
(radeon_cs_space_reset_bos+0x2f) [0x7f4cf725ef6f]
[ 39968.663] (EE) 4: /usr/lib64/xorg/modules/drivers/radeon_drv.so 
(_init+0x1db2d) [0x7f4cf74b03dd]
[ 39968.664] (EE) 5: /usr/lib64/xorg/modules/drivers/radeon_drv.so 
(_init+0x2b498) [0x7f4cf74cb608]
[ 39968.665] (EE) 6: /usr/lib64/xorg/modules/libexa.so 
(exaMoveOutPixmap+0x43f2) [0x7f4cf6605a72]
[ 39968.665] (EE) 7: /usr/libexec/Xorg (DamageRegionAppend+0x36c3) 
[0x5272b3]
[ 39968.666] (EE) 8: /usr/libexec/Xorg (SendGraphicsExpose+0xfc8) [0x4348c8]
[ 39968.666] (EE) 9: /usr/libexec/Xorg (SendErrorToClient+0x405) [0x437175]
[ 39968.666] (EE) 10: /usr/libexec/Xorg (InitFonts+0x428) [0x43b0b8]
[ 39968.680] (EE) 11: /lib64/libc.so.6 (__libc_start_main+0xf1) 
[0x7f4cfab58431]
[ 39968.681] (EE) 12: /usr/libexec/Xorg (_start+0x2a) [0x424d5a]
[ 39968.681] (EE)
[ 39968.681] (EE) Illegal instruction at address 0x7f4cf725dc90
[ 39968.681] (EE)
Fatal server error:
[ 39968.681] (EE) Caught signal 4 (Illegal instruction). Server aborting
[ 39968.681] (EE)
[ 39968.681] (EE)
Please consult the Fedora Project support
          at http://wiki.x.org
  for help.
[ 39968.681] (EE) Please also check the log file at 
"/var/log/Xorg.0.log" for additional information.
[ 39968.681] (EE)
[ 39968.683] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 39968.692] (EE) Server terminated with error (1). Closing log file.

So I searched on wikki.x.org and saw one thread with same "Caught signal 
4 (Illegal instruction)." error produced when this guy started kde on 
ubuntu on vmware on win7. Not quite similar.


>
> 2. Regarding Ken Jackson's keyboard-shortcut note; The X Server kill 
> ("Zap") keyboard shortcut can be disabled within the X Server 
> configuration file (xorg.conf). Instructions/information regarding 
> that configuration file and the "DontZap" configuration option are at:
>
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/4/html/Reference_Guide/s1-x-server-configuration.html 
>
> https://www.x.org/releases/X11R7.7/doc/man/man5/xorg.conf.5.xhtml
>

Ken's keypress idea seems reasonable to me and my bumbling fingers.
First, I have no xorg.conf.
I do have a /etc/X11/xorg.conf.d/00-keyboard.conf but nothing of 
interest in there.

I am running lxde so I also have ~/.config/openbox/lxde-rc.xml but 
nothing of interest in there.

Looking at s1-x-server-configuration.html I see that ctrl-alt-Backspace 
is the zap combo but that has no effect when I try it.


> 3. The Fedora 25 Installation Guide includes a page on X Server 
> crashes which may be useful as well:
>
> https://docs-old.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/ch07s04s06.html 
>
>

That talks about low disk space which I have plenty of in all partitions.

So the only clue so far has been  that signal 4.
I don't understand the events leading up to that there so...
Any ideas?

I'll have to see what happens going forward.
Thanks for all the help.

Howard();



More information about the CALUG mailing list