Comment 6 for bug 1837071

Revision history for this message
In , Dmitry Katsubo (dma-k) wrote :

In my case xfsettingsd results segfault during the session startup:

[Tue Oct 8 11:14:22 2019] xfsettingsd[2538]: segfault at 18 ip 00007fc318301f2d sp 00007ffdcfc9f2d0 error 4 in libxklavier.so.16.4.0[7fc3182f7000+d000]
[Tue Oct 8 11:14:22 2019] Code: 48 89 45 28 48 c1 e2 03 4a 8d 7c e0 08 e8 eb 51 ff ff e9 1e fe ff ff e8 11 5a ff ff 90 41 54 48 89 d1 49 89 fc 55 48 89 f5 53 <48> 8b 42 18 48 89 d3 48 89 fa 48 89 ef 48 8b b0 28 01 00 00 e8 0a
[Tue Oct 8 11:14:22 2019] traps: light-locker[2510] trap int3 ip:7f017b666c75 sp:7fff462b5400 error:0 in libglib-2.0.so.0.5800.3[7f017b62e000+7e000]

When I start xfsettingsd afterwards from xterm, it starts and functions correctly. I have difficulty capturing the backtrace with gdb unless somebody can give a hint how to do it. I have added

export XFSETTINGSD_DEBUG=1
ulimit -c unlimited
/etc/X11/Xsession

to ./.vnc/xstartup but it does not generate a core dump :(

Additional info:

* Debian Buster, uname: 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux
* xfce4-settings:amd64 v4.12.4-1
* libxklavier16:amd64 v5.4-4
* Xfce is running under tightvncserver.