Bug#925483: tilda: does not start (segfault) (under Wayland)

[Vlad Orlov]

Hi,

Upstream has a workaround for this crash at [1], you might want to use it as a 
patch.
Also this report can be probably merged with [2].


[1] 
https://github.com/lanoxx/tilda/commit/daa64f579b4d544cb7da614612f1d35c461b43be
[2] https://bugs.debian.org/904309

Bug#925483: tilda: does not start (segfault)

[Gunter Grodotzki]

Thanks Bernhard for the help!

You are right, I am running Gnome/Wayland, and this seems to be
unsupported.

Bug#925483: tilda: does not start (segfault)

[Bernhard Übelacker]

Hello Guenter Grodotzki,
I am not the maintainer for tilda, just got here and
tried to collect some more information.

For some reason your upstream report contains one
(interesting) lines more than made it into the debian report.

Just as a hint: the real important information has to be
queried from gdb by the "bt" or backtrace command.
For bug reports sometimes "bt full" might be helpful too.

Adding the debug symbol packages [1] would be even more helpful.


I have tried to reproduce in a minimal amd64 buster VM.
Tilda just run fine within a openbox or plasma X11 session.

I just received a crash when running within a gnome session:

(gdb) bt
#0  0x7fcc0191c4bb in require_socket (dpy=0x563f2b027810) at 
../../src/xcb_io.c:68
#1  0x7fcc0191cd05 in require_socket (dpy=0x563f2b027810) at 
../../src/xcb_io.c:518
#2  _XFlush (dpy=0x563f2b027810) at ../../src/xcb_io.c:515
#3  0x7fcc0191f7f5 in _XGetRequest (dpy=dpy@entry=0x563f2b027810, 
type=type@entry=119 'w', len=len@entry=4) at ../../src/XlibInt.c:1717
#4  0x7fcc0190b7dd in XGetModifierMapping (dpy=0x563f2b027810) at 
../../src/ModMap.c:42
#5  0x563f2ad6660a in reload_modmap (modmap=0x563f2b745cd0, 
keymap=0x563f2b046840) at src/eggaccelerators.c:82
#6  egg_keymap_get_modmap (keymap=0x563f2b046840) at 
src/eggaccelerators.c:173
#7  0x563f2ad66850 in egg_keymap_resolve_virtual_modifiers 
(keymap=0x563f2b046840, virtual_mods=EGG_VIRTUAL_LOCK_MASK, 
concrete_mods=0x563f2af81b44 ) at src/eggaccelerators.c:56
#8  0x563f2ad6c64a in lookup_ignorable_modifiers 
(keymap=0x563f2b046840) at src/tomboykeybinder.c:88
#9  0x563f2ad6cc1e in tomboy_keybinder_init () at 
src/tomboykeybinder.c:319
#10 0x563f2ad65635 in main (argc=, argv=) 
at src/tilda.c:842

At least the address offset from my frame 0 and your frame 0
is equal, therefore I guess you are running also
a gnome/wayland session?

This issue are describing in more detail
upstream issues [2] and [3].

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
[2] https://github.com/lanoxx/tilda/issues/150
[3] https://github.com/lanoxx/tilda/issues/314

# Buster amd64 qemu VM 2019-03-25

apt update
apt dist-upgrade

#

apt install systemd-coredump xserver-xorg lightdm openbox tilda

systemctl start lightdm

export DISPLAY=:0
tilda

-> no segfault

#

apt install systemd-coredump xserver-xorg sddm plasma-desktop dbus-x11 tilda

systemctl start sddm

export DISPLAY=:0
tilda

-> no segfault

#

apt install systemd-coredump gdb weston gdm3 gnome-session tilda

systemctl start gdm3

export DISPLAY=:0
tilda

-> segfaults

#


apt install dpkg-dev devscripts systemd-coredump gdb weston gdm3 gnome-session 
tilda tilda-dbgsym libx11-6-dbgsym



mkdir /tmp/source/libx11-6/orig -p
cd/tmp/source/libx11-6/orig
apt source libx11-6
cd


set width 0
set pagination off
directory /tmp/source/libx11-6/orig/libx11-1.6.7/debian/patches
bt


#

benutzer@debian:~$ tilda
Unable to open lock directory: /home/benutzer/.cache/tilda/locks
Erstelle Verzeichnis: '/home/benutzer/.config/tilda'
Speicherzugriffsfehler (Speicherabzug geschrieben)


dmesg
[  273.20] tilda[14800]: segfault at 40 ip 7fcc0191c4bb sp 
7ffc7815cce0 error 4 in libX11.so.6.3.0[7fcc018f5000+8a000]
[  273.208894] Code: 31 c9 48 89 fb 48 8d 35 f3 05 00 00 48 83 ec 10 64 48 8b 
04 25 28 00 00 00 48 89 44 24 08 31 c0 48 8b 87 30 0a 00 00 49 89 e0 <8b> 50 40 
85 d2 48 89 fa 48 8b 38 0f 95 c1 e8 32 a9 fd ff 85 c0 74


root@debian:~# coredumpctl list
TIMEPID   UID   GID SIG COREFILE  EXE
Mon 2019-03-25 22:29:54 CET   14800  1000  1000  11 present   /usr/bin/tilda


root@debian:~# coredumpctl gdb 14800
   PID: 14800 (tilda)
   UID: 1000 (benutzer)
   GID: 1000 (benutzer)
Signal: 11 (SEGV)
 Timestamp: Mon 2019-03-25 22:29:54 CET (1min 37s ago)
  Command Line: tilda
Executable: /usr/bin/tilda
 Control Group: /user.slice/user-1000.slice/session-5.scope
  Unit: session-5.scope
 Slice: user-1000.slice
   Session: 5
 Owner UID: 1000 (benutzer)
   Boot ID: 889af76e9cd9473da884a4f59630c55b
Machine ID: 32f43b50ac8c4b21941bc0b02f8e7811
  Hostname: debian
   Storage: 
/var/lib/systemd/coredump/core.tilda.1000.889af76e9cd9473da884a4f59630c55b.14800.155354939400.lz4
   Message: Process 14800 (tilda) of user 1000 dumped core.

Stack trace of thread 14800:
#0  0x7fcc0191c4bb n/a (libX11.so.6)
#1  0x7fcc0191cd05 _XFlush (libX11.so.6)
#2  0x7fcc0191f7f5 _XGetRequest (libX11.so.6)
#3  0x7fcc0190b7dd XGetModifierMapping (libX11.so.6)
#4  0x563f2ad6660a n/a (tilda)
#5  0x563f2ad66850 n/a (tilda)
#6  0x563f2ad6c64a 

Bug#925483: tilda: does not start (segfault)

[Guenter Grodotzki]

Package: tilda
Version: 1.4.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

starting tilda (either via menu or terminal)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

was not able to get it to run

   * What was the outcome of this action?

"Segmentation fault"

   * What outcome did you expect instead?

Running application (tilda)


Upstream bug report:
https://github.com/lanoxx/tilda/issues/360#issuecomment-476309441


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_ZA:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tilda depends on:
ii  libc6   2.28-8
ii  libconfuse2 3.2.2+dfsg-1
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-1
ii  libgtk-3-0  3.24.5-1
ii  libpango-1.0-0  1.42.4-6
ii  libvte-2.91-0   0.54.2-2
ii  libx11-62:1.6.7-1

tilda recommends no packages.

tilda suggests no packages.

-- no debconf information

*** /home/guenter/gdp-tilda.txt
~  gdb tilda
GNU gdb (Debian 8.2.1-2) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from tilda...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/tilda
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Detaching after fork from child process 3404]
[New Thread 0x7427b700 (LWP 3406)]
[New Thread 0x73a7a700 (LWP 3407)]
[New Thread 0x73247700 (LWP 3408)]
[New Thread 0x72a3f700 (LWP 3409)]
[New Thread 0x71f58700 (LWP 3411)]
[New Thread 0x7170a700 (LWP 3412)]
[New Thread 0x70f09700 (LWP 3413)]
[New Thread 0x7fffdbfff700 (LWP 3414)]
[New Thread 0x7fffdb7fe700 (LWP 3415)]
[New Thread 0x7fffdaffd700 (LWP 3416)]
[New Thread 0x7fffda7fc700 (LWP 3417)]
[Detaching after fork from child process 3418]

Thread 1 "tilda" received signal SIGSEGV, Segmentation fault.