Bug#675608: notification-daemon immediately coredumps when receiving notifications

Michael Prokop mika at debian.org
Sat Jun 2 13:07:10 UTC 2012


Package: notification-daemon
Version: 0.7.4-1
Severity: important


System is fully updated Debian/sid as of today with libnotify-bin
0.7.5-1, using openbox window manager (no gnome involved).

Executing:

  % /usr/lib/notification-daemon/notification-daemon

and then sending a notification via e.g.:

  % notify-send abc abc

causes the notification-daemon process to immediately coredump (no
notification is visible):

  | (notification-daemon:17244): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed
  | [1]  + 17244 trace trap (core dumped)  /usr/lib/notification-daemon/notification-daemon

When running notification-daemon under strace or gdb I can't
reproduce the problem. I can reproduce the problem also with
versions notification-daemon versions 0.7.3-1, 0.7.2-1 and 0.7.1-1.

The problem does NOT exist with libnotify1 0.5.0-2 +
notification-daemon 0.5.0-3.

As I couldn't find a debug package for notification-daemon the
backtrace isn't that useful, but adding it as reference anyway:

(gdb) bt
#0  0x00007ff03b472341 in g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007ff03b4724d2 in g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff03bc6eee4 in gdk_pixbuf_scale_simple () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0
#3  0x00007ff03c7d0f6b in gtk_icon_theme_lookup_by_gicon () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#4  0x00007ff03c7d1099 in gtk_icon_theme_lookup_by_gicon () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#5  0x00007ff03c7cb7bb in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#6  0x00007ff03c876cf2 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#7  0x000000000040bea1 in ?? ()
#8  0x00007ff03b46b205 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007ff03b46b538 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007ff03b46b932 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ff03c7f72d5 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x000000000040738a in ?? ()
#13 0x00007ff03ab60ead in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#14 0x00000000004073f5 in ?? ()
#15 0x00007fff6b4cf078 in ?? ()
#16 0x000000000000001c in ?? ()
#17 0x0000000000000001 in ?? ()
#18 0x00007fff6b4d138e in ?? ()
#19 0x0000000000000000 in ?? ()
(gdb) 

If you need any further information please let me know.

I tend to call this an RC bug, but as not everyone seems to be
affected I chose severity important, leaving the decision to the
maintainer.

regards,
-mika-





More information about the pkg-gnome-maintainers mailing list