Bug#820944: libcanberra-gtk3-0: segfault after call to ca_gtk_proplist_set_for_widget when running under wayland
Diane Trout
diane at ghic.org
Wed Apr 13 20:33:07 UTC 2016
Package: libcanberra-gtk3-0
Version: 0.30-2.1
Severity: important
Dear Maintainer,
While running applications that use libcanberra-gtk3-0 under wayland I
get
segfaults when trying to touch settings.
I first experienced this in empathy-chat when receving a new message
tringgering a sound notification. It also happens when adjusting the
Output
Device volume slider in pavucontrol.
Both stack traces lead into the same functions:
end of gdb backtrace from empathy-chat:
#0 0x00007fffec72fa1d in ?? () from /usr/lib/x86_64-linux-
gnu/libX11.so.6
#1 0x00007fffec72feda in XInternAtom () from /usr/lib/x86_64-linux-
gnu/libX11.so.6
#2 0x00007fffee408c2c in gdk_x11_atom_to_xatom_for_display ()
from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#3 0x00007ffff64f02cd in window_get_desktop (d=0x68a000, w=0x68a5c0)
at
canberra-gtk.c:188
#4 0x00007ffff64f0795 in ca_gtk_proplist_set_for_widget (p=0x1c1de00,
widget=0xa38570)
at canberra-gtk.c:271
#5 0x00007ffff7873833 in empathy_sound_play_internal (widget=0xa38570,
sound_id=sound_id at entry=EMPATHY_SOUND_MESSAGE_INCOMING,
callback=callback at entry=0x0,
user_data=user_data at entry=0x0) at empathy-sound-manager.c:298
#6 0x00007ffff7873d6f in empathy_sound_manager_play_full
(self=<optimized
out>, widget=<optimized out>,
sound_id=sound_id at entry=EMPATHY_SOUND_MESSAGE_INCOMING,
callback=callback at entry=0x0,
user_data=user_data at entry=0x0) at empathy-sound-manager.c:357
#7 0x00007ffff7873e1e in empathy_sound_manager_play (self=<optimized
out>,
widget=<optimized out>,
sound_id=sound_id at entry=EMPATHY_SOUND_MESSAGE_INCOMING) at empathy-
sound-
manager.c:379
#8 0x00000000004107fb in chat_window_new_message_cb (chat=0x8925f0,
message=0x1bf36a0, pending=0,
should_highlight=0, self=0xa38570) at empathy-chat-window.c:1764
Gdb backtrace from pavucontrol:
#0 0x00007ffff604ceba in XInternAtom () from /usr/lib/x86_64-linux-
gnu/libX11.so.6
#1 0x00007ffff526fc2c in gdk_x11_atom_to_xatom_for_display ()
from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#2 0x00007ffff63642cd in window_get_desktop (d=0x6c9000, w=0x6c9450)
at
canberra-gtk.c:188
#3 0x00007ffff6364795 in ca_gtk_proplist_set_for_widget (p=0xc62140,
widget=0xb104f0)
at canberra-gtk.c:271
#4 0x00007ffff6365145 in ca_gtk_play_for_widget (w=0xb104f0, id=2) at
canberra-gtk.c:445
#5 0x0000000000416282 in ?? ()
#6 0x000000000041050e in ?? ()
#7 0x00007ffff69ea7a2 in sigc::slot0<bool>::operator()
(this=<optimized out>)
at /usr/include/sigc++-2.0/sigc++/functors/slot.h:440
#8 (anonymous namespace)::glibmm_main_context_invoke_callback
(data=<optimized
out>) at main.cc:329
#9 0x00007ffff3bb1a53 in ?? () from /lib/x86_64-linux-gnu/libglib-
2.0.so.0
#10 0x00007ffff3bb0fea in g_main_context_dispatch () from /lib/x86_64-
linux-
gnu/libglib-2.0.so.0
#11 0x00007ffff3bb1390 in ?? () from /lib/x86_64-linux-gnu/libglib-
2.0.so.0
#12 0x00007ffff3bb16b2 in g_main_loop_run () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#13 0x00007ffff56efed5 in gtk_main () from /usr/lib/x86_64-linux-
gnu/libgtk-3.so.0
#14 0x00007ffff79d6bdf in Gtk::Main::run(Gtk::Window&) ()
from /usr/lib/x86_64-linux-gnu/libgtkmm-3.0.so.1
#15 0x000000000040c2dd in main ()
(pavucontrol was a lot shorter so was easier to include the whole
thing.)
Both end up going through the same few functions leading to an X11
call, so I
think the problem is with the library and not the applications.
I tried this with libcanberra-gtk0-3 which I built from an unreleased
debcheckout because it includes the gtk_dont_assume_x11.patch which is
an
upstream fix for (apparently some other) calls that assume GDK is X11.
Diane
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libcanberra-gtk3-0 depends on:
ii libatk1.0-0 2.20.0-1
ii libc6 2.22-6
ii libcairo-gobject2 1.14.6-1+b1
ii libcairo2 1.14.6-1+b1
ii libcanberra0 0.30-2.1
ii libgdk-pixbuf2.0-0 2.32.3-2
ii libglib2.0-0 2.48.0-1
ii libgtk-3-0 3.18.9-1
ii libpango-1.0-0 1.38.1-1
ii libpangocairo-1.0-0 1.38.1-1
ii libx11-6 2:1.6.3-1
ii multiarch-support 2.22-6
Versions of packages libcanberra-gtk3-0 recommends:
ii libcanberra-gtk3-module 0.30-3
libcanberra-gtk3-0 suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list