Comment 2 for bug 1592008

Revision history for this message
IBBoard (ibboard) wrote :

Same on openSUSE Tumbleweed. Crash and backtrace with debug symbols is:

Thread 1 "synapse" received signal SIGSEGV, Segmentation fault.
_XkbGetGetMapReq (dpy=dpy@entry=0x71aa60, xkb=<optimized out>) at XKBGetMap.c:477
477 XKBGetMap.c: No such file or directory.
(gdb) backtrace
#0 _XkbGetGetMapReq (dpy=dpy@entry=0x71aa60, xkb=<optimized out>) at XKBGetMap.c:477
#1 0x00007ffff463a114 in XkbGetUpdatedMap (dpy=0x71aa60, which=7, xkb=0x9a5320) at XKBGetMap.c:582
#2 0x00007ffff463a1dd in XkbGetMap (dpy=0x71aa60, which=which@entry=7, deviceSpec=deviceSpec@entry=256) at XKBGetMap.c:603
#3 0x00007ffff76e3747 in grab_ungrab (rootwin=rootwin@entry=0x732010, keyval=32, modifiers=4, grab=grab@entry=1) at bind.c:203
#4 0x00007ffff76e3885 in do_grab_key (binding=binding@entry=0x90ae50) at bind.c:326
#5 0x00007ffff76e3c60 in keybinder_bind_full (keystring=0xa4ef50 "<Control>space",
    handler=handler@entry=0x4158c0 <_synapse_ui_launcher_handle_shortcut_keybinder_handler>, user_data=user_data@entry=0x7a26e0,
    notify=notify@entry=0x0) at bind.c:586
#6 0x00007ffff76e3cb7 in keybinder_bind (keystring=<optimized out>,
    handler=handler@entry=0x4158c0 <_synapse_ui_launcher_handle_shortcut_keybinder_handler>, user_data=user_data@entry=0x7a26e0) at bind.c:551
#7 0x0000000000415423 in synapse_ui_launcher_bind_keyboard_shortcut (self=0x7a26e0)
    at /usr/src/debug/synapse-0.2.99.2/src/ui/synapse-main.vala:210
#8 synapse_ui_launcher_construct (object_type=<optimized out>) at /usr/src/debug/synapse-0.2.99.2/src/ui/synapse-main.vala:63
#9 0x0000000000415c7c in synapse_ui_launcher_new () at /usr/src/debug/synapse-0.2.99.2/src/ui/synapse-main.vala:51
#10 synapse_ui_launcher_main (argv=<optimized out>, argv_length1=<optimized out>) at /usr/src/debug/synapse-0.2.99.2/src/ui/synapse-main.vala:293
#11 0x00007ffff4907291 in __libc_start_main () from /lib64/libc.so.6
#12 0x0000000000414d0a in _start () at ../sysdeps/x86_64/start.S:120

Apparently this is because of Synapse assuming it'll be an X11 GDK display, when that is just one implementation (since now there's Wayland)