systemd-coredump

Patch2 · 2018-07-22 22:41:00

Alright, I think I'm posting this in the right place. For an unknown to me reason, my Xorg server keeps crashing. This usually occurs when I hit the key combo Alt+l (lowercase L), which is bound to snap the window to the right half of the screen.

Since I've been unable to locate any logs related to Xorg/X11, the most information I was able to find came from journalctl. A bit more information about my setup:

Using:

Mate without a desktop manager.
Compiz 0.9.

This is the output of `journalctl`:

systemd-coredump[6781]: Process 1261 (Xorg) of user 1001 dumped core.
                                                 
                                                 Stack trace of thread 1261:
                                                 #0  0x00007fe4fec2786b raise (libc.so.6)
                                                 #1  0x00007fe4fec1240e abort (libc.so.6)
                                                 #2  0x0000559336e7160a OsAbort (Xorg)
                                                 #3  0x0000559336e716ff FatalError (Xorg)
                                                 #4  0x0000559336fa7dae n/a (Xorg)
                                                 #5  0x00007fe4fec278f0 __restore_rt (libc.so.6)
                                                 #6  0x0000559336f11897 ChangeWindowDeviceCursor (Xorg)
                                                 #7  0x0000559336ead655 n/a (Xorg)
                                                 #8  0x0000559336e55f08 n/a (Xorg)
                                                 #9  0x00007fe4fec1406b __libc_start_main (libc.so.6)
                                                 #10 0x0000559336e5622a _start (Xorg)
                                                 
                                                 Stack trace of thread 1262:
                                                 #0  0x00007fe4fcc66ffc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                 #1  0x00007fe4f685b124 n/a (i965_dri.so)
                                                 #2  0x00007fe4f685ae18 n/a (i965_dri.so)
                                                 #3  0x00007fe4fcc61075 start_thread (libpthread.so.0)
                                                 #4  0x00007fe4fece953f __clone (libc.so.6)
                                                 
                                                 Stack trace of thread 1263:
                                                 #0  0x00007fe4fcc66ffc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
                                                 #1  0x00007fe4f685b124 n/a (i965_dri.so)
                                                 #2  0x00007fe4f685ae18 n/a (i965_dri.so)
                                                 #3  0x00007fe4fcc61075 start_thread (libpthread.so.0)
                                                 #4  0x00007fe4fece953f __clone (libc.so.6)

Please let me know what further information I can provide or where to do more research. So far the best I've come up with is Xorg's gdb tutorial, which is beyond the depth of my X programming skill.

Thank you!

jasonwryan · 2018-07-22 22:45:39

Patch2 wrote:

I've been unable to locate any logs related to Xorg/X11

Why? Where have you looked?

Patch2 · 2018-07-22 23:58:59

I looked in /var/log/ which contained nothing related to X11.

▶ ls /var/log                         
127.0.0.1.log      archserver.log  clamav   glusterfs  keybase  mongodb   openvas     samba              swtpm         teamviewer13      vnetlib
192.168.1.189.log  btmp            cups     httpd      lastlog  nmbd.log  pacman.log  smbd.log           tallylog      vmware            wtmp
ansible.log        btmp.1          faillog  journal    libvirt  old       private     speech-dispatcher  teamviewer12  vmware-installer

I checked

journal
archserver.log
private
lastlog
and
the IP address logs

Historically, I've had limited success with appending 2>&1 >> ~/out.log to my `exec startx`, but that hasn't yielded anything of merit in this case.

I should also mention that I realize journal and private are directories. Journal of course contained my journalctl information, while private was completely empty.
archserver.log was also empty and lastlog contained: (rZtty1U[tty1%

Last edited by Patch2 (2018-07-23 00:02:05)

2ManyDogs · 2018-07-23 00:03:18

Patch2 wrote:

I looked in /var/log/ which contained nothing related to X11.

Look in ~/.local/share/xorg.

https://wiki.archlinux.org/index.php/Xorg#General

Patch2 · 2018-07-23 00:23:47

Ah, well that certainly helps on the log file front. Thank you lots. I'll report back next time it crashes and see what information I can glean from it. If I encounter the resolution, hopefully, this will help someone else with the same issue.

seth · 2018-07-23 06:33:37

How are you running

Mate without a desktop manager.
Compiz 0.9.

?

How do you start X and the session itfp?
Try to "startx xterm", run compiz from there and see what happens when you trigger the crash (whether only compiz or all of X11 dies)

Patch2 · 2018-07-23 13:42:35

seth:

After login, xinit executes startx from ~/.zprofile as seen here:
Autostart_X_at_login

Then ~/.xinitrc gets executed as seen here:
xinitrc config

.xinitrc runs

exec mate-session

loqs · 2018-07-23 14:02:26

Patch2 wrote:

.xinitrc runs
exec mate-session

Is that the full contents of ~/.xinitrc ?

Patch2 · 2018-07-23 16:06:56

Negative, here's a link to the full contents:
Gist of my .xinitrc

seth · 2018-07-23 17:23:42

Either mate-session or actually the X11 server crashes (the X11 abort could also be a follow-up from a thread calling into the dying server)
Are there traces of other coredumps in the journal?

Patch2 · 2018-07-25 02:21:12

That's a good point, I was just thinking the same thing regarding mate-session. It recently occurred when I was resizing a chrome window that was still under the 'wobbly windows' effect and loading a page.
Of course, I failed to get the logs from Xorg.0.log at that time. (I will do this though!)

I tried adding `&2>1 >> ~/out.log` to the end of mate-session, but then the GUI wouldn't boot. I'm going to do some more research on that particular issue, but I do think it's related to mate and not X11.

I'm not seeing any other coredumps. I'm searching through it with `journal -x -r`. If there's a better way to hunt, I'm open to suggestions.

seth · 2018-07-25 07:41:53

It's rather

>> ~/out.log 2>&1

(First redirect stdout into the file, then stderr into stdout)

Patch2 · 2018-11-17 17:51:57

As an update for anyone else having this issue:

I noticed a correlation with opening Chromium and then immediately using a shortcut mapped to Compiz' Grid plugin which puts the window in the desired location on the screen. During the time that Chromium was 'initiating' (identified by two Chromium windows on the bottom panel), if the shortcut was activated it would initiate a crash of the X Window Server.

Thanks to everyone for helping me nail down the source of this.

Arch Linux

#1 2018-07-22 22:41:00

systemd-coredump

#2 2018-07-22 22:45:39

Re: systemd-coredump

#3 2018-07-22 23:58:59

Re: systemd-coredump

#4 2018-07-23 00:03:18

Re: systemd-coredump

#5 2018-07-23 00:23:47

Re: systemd-coredump

#6 2018-07-23 06:33:37

Re: systemd-coredump

#7 2018-07-23 13:42:35

Re: systemd-coredump

#8 2018-07-23 14:02:26

Re: systemd-coredump

#9 2018-07-23 16:06:56

Re: systemd-coredump

#10 2018-07-23 17:23:42

Re: systemd-coredump

#11 2018-07-25 02:21:12

Re: systemd-coredump

#12 2018-07-25 07:41:53

Re: systemd-coredump

#13 2018-11-17 17:51:57

Re: systemd-coredump

Board footer