Bug#669883: notification-daemon crashes in gdk_pixbuf_scale_simple

anomie at users.sourceforge.net anomie at users.sourceforge.net
Sat Apr 28 15:54:26 UTC 2012


Ok, I think I have this worked out. GTK is throwing a critical warning,
and since notification-daemon calls
g_log_set_always_fatal (G_LOG_LEVEL_ERROR | G_LOG_LEVEL_CRITICAL) it
results in SIGTRAP where most GTK-using programs will just output a
message to stderr.

The problem seems to be that GtkStatusIcon defaults to a size of 4
somewhere, and then rounds this down to 0, and so tries to make a
zero-sized icon. If the critical warning doesn't terminate the program,
GtkStatusIcon will later on get a larger size and create an
appropriately-sized icon. As far as I can tell, older versions of GTK
didn't do this because they used a minimum size of GTK_ICON_SIZE_MENU
rather than 0 for GtkStatusIcons. I think this changed in
http://git.gnome.org/browse/gtk+/commit/gtk/gtkstatusicon.c?id=2e01dc1b7a134a6482f39ae7b3b6c840442c93db
in the block @@ -1364,9 +1327,9 @@.

This bug should probably be reassigned to gtk+3.0, since it has little
to do with notification-daemon. I've attached a small test program to
illustrate the problem. As a workaround, the g_log_set_always_fatal call
could be commented out in daemon.c.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug.c
Type: text/x-csrc
Size: 611 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20120428/bd8d3078/attachment.c>


More information about the pkg-gnome-maintainers mailing list