Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 486006 - x11-libs/gtk+-2.24.20: printing crashes gtk based apps (firefox, chromium, gimp, ...)
Summary: x11-libs/gtk+-2.24.20: printing crashes gtk based apps (firefox, chromium, gi...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-25 18:54 UTC by Thomas Bettler
Modified: 2013-09-26 21:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Bettler 2013-09-25 18:54:09 UTC
After updating to x11-libs/gtk+-2.24.20 firefox & co crash right after the print dialog has disappeared (print or even cancel).

Problem:
After a bisect I can tell the problem is related to upstream commit a057ed26dc623dff0fc0c62ef287f6583b2710d0 which introduces the use of function g_clear_pointer() (https://git.gnome.org/browse/gtk+/commit/modules/printbackends/cups/gtkprintbackendcups.c?h=gtk-2-24&id=a057ed26dc623dff0fc0c62ef287f6583b2710d0 )

This very function has been introduced by >=dev-libs/glib-2.34. Compiling with glib-2.32.4-r1 works although it gives a warning: "implicit declaration of function ‘g_clear_pointer’ [-Wimplicit-function-declaration]"
However firefox crashes on printing operations (and even page settings) with the output: "symbol lookup error: /usr/lib64/gtk-2.0/2.10.0/printbackends/libprintbackend-cups.so: undefined symbol: g_clear_pointer"

Solution:
Depend x11-libs/gtk+-2.24.20 on >=dev-libs/glib-2.34:2
Comment 1 Alexandre Rostovtsev (RETIRED) gentoo-dev 2013-09-26 02:00:42 UTC
Thanks. I've fixed the dependency and alerted upstream to the issue.

+  26 Sep 2013; Alexandre Rostovtsev <tetromino@gentoo.org> gtk+-2.24.20.ebuild:
+  Require glib-2.34 due to g_clear_pointer (bug #486006, thanks to Thomas
+  Bettler).