skippy triggers systemd-coredump

[gazeto]

I have no clue what's going on here and didn't have problems in the past. But lately I found skippy got killed repeatedly and now I'm reading in the systemlog:

Jan 12 08:58:39 opaque systemd-coredump[3223]: Process 727 (skippy-xd) of user 1000 dumped core.

                                               Stack trace of thread 727:
                                               #0  0x00007f46ae38304f raise (libc.so.6)
                                               #1  0x00007f46ae38447a abort (libc.so.6)
                                               #2  0x00007f46ae37bea7 __assert_fail_base (libc.so.6)
                                               #3  0x00007f46ae37bf52 __assert_fail (libc.so.6)
                                               #4  0x0000000000405a5c n/a (skippy-xd)
                                               #5  0x00000000004070fe n/a (skippy-xd)
                                               #6  0x00007f46ae370291 __libc_start_main (libc.so.6)
                                               #7  0x0000000000407329 n/a (skippy-xd)

And for reference:

[gazeto@opaque ~]$ uname -a
Linux opaque 4.9.0-1-MANJARO #1 SMP PREEMPT Fri Dec 23 10:47:01 UTC 2016 x86_64 GNU/Linux
[gazeto@opaque ~]$ skippy-xd --help
skippy-xd (2015.12.21)
Usage: skippy-xd [command]

The available commands are:
  --config                    - Read the specified configuration file.
  --start-daemon              - starts the daemon running.
  --stop-daemon               - stops the daemon running.
  --activate-window-picker    - tells the daemon to show the window picker.
  --deactivate-window-picker  - tells the daemon to hide the window picker.
  --toggle-window-picker      - tells the daemon to toggle the window picker.

  --help                      - show this message.
  -S                          - Synchronize X operation (debugging).
PNG support: Yes
  Compiled with libpng 1.6.21, using 1.6.27.
  Compiled with zlib 1.2.8, using 1.2.8.

Cheers & happy 2017 to everybody!

[FHFS]

Same here, actually happend a few times. A few more recently, I changed the multi-monitor setup, from next to eachother to above.

dec 26 21:23:48 fhfs-ArchLabs-Laptop systemd-coredump[8019]: Process 626 (skippy-xd) of user 1000 dumped core.
jan 04 10:05:42 fhfs-ArchLabs-Laptop systemd-coredump[8415]: Process 675 (skippy-xd) of user 1000 dumped core.
jan 28 16:22:35 fhfs-ArchLabs-Laptop systemd-coredump[6232]: Process 668 (skippy-xd) of user 1000 dumped core.
jan 31 10:29:38 fhfs-ArchLabs-Laptop systemd-coredump[8783]: Process 654 (skippy-xd) of user 1000 dumped core.
feb 19 11:15:00 fhfs-ArchLabs-Laptop systemd-coredump[1922]: Process 941 (skippy-xd) of user 1000 dumped core.
feb 25 13:02:29 fhfs-ArchLabs-Laptop systemd-coredump[10086]: Process 1010 (skippy-xd) of user 1000 dumped core.
feb 26 17:34:57 fhfs-ArchLabs-Laptop systemd-coredump[27707]: Process 978 (skippy-xd) of user 1000 dumped core.
feb 27 15:01:25 fhfs-ArchLabs-Laptop systemd-coredump[11600]: Process 698 (skippy-xd) of user 1000 dumped core.
mrt 02 12:41:10 fhfs-ArchLabs-Laptop systemd-coredump[13239]: Process 727 (skippy-xd) of user 1000 dumped core.
mrt 02 12:41:10 fhfs-ArchLabs-Laptop systemd-coredump[13239]: Process 727 (skippy-xd) of user 1000 dumped core.
mrt 02 12:41:10 fhfs-ArchLabs-Laptop systemd-coredump[13239]: Process 727 (skippy-xd) of user 1000 dumped core.

Stack trace of thread 727:
#0  0x00007f68445bf860 raise (libc.so.6)
#1  0x00007f68445c0ec9 abort (libc.so.6)
#2  0x00007f68445b80bc __assert_fail_base (libc.so.6)
#3  0x00007f68445b8133 __assert_fail (libc.so.6)
#4  0x000055b4e1ceea73 n/a (skippy-xd)
#5  0x000055b4e1cf041a n/a (skippy-xd)
#6  0x00007f68445abf4a __libc_start_main (libc.so.6)
#7  0x000055b4e1cf058a n/a (skippy-xd)

uname -a
Linux fhfs-ArchLabs-Laptop 4.14.22-1-lts #1 SMP Sun Feb 25 15:13:49 CET 2018 x86_64 GNU/Linux

[FHFS]

This is actually Quite troublesome, this crash shuts down my whole laptop. I've lost hours of work on several occasions. On the upside this makes me save more regularly...