Bug 2576 - glib update to 2.29.18 breaks inkscape due to glibmm missing symbol problem
Summary: glib update to 2.29.18 breaks inkscape due to glibmm missing symbol problem
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-31 13:22 CEST by Jari S
Modified: 2011-08-31 18:32 CEST (History)
2 users (show)

See Also:
Source RPM: glibmm2.4-2.29.10-2.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Jari S 2011-08-31 13:22:14 CEST
Description of problem:
Inkscape does not start if glib has been updated to 2.29.18 since there is missing symbols "inkscape: symbol lookup error: /usr/lib64/libgiomm-2.4.so.1: undefined symbol: g_time_zone_monitor_get_type". Inskscape just shows the problem, it is not the actual source of the problem.

Version-Release number of selected component (if applicable):
lib64glib2.0_0-2.29.18-1.mga2
lib64glibmm2.4_1-2.29.10-2.mga2


How reproducible:
Always.

Steps to Reproduce:
1. Update to lib64glib2.0_0-2.29.18-1.mga2
2. Start inkscape from command line
3. See the resulting missing symbol message

Information of the problem can be found at https://mail.gnome.org/archives/commits-list/2011-August/msg09009.html. The source of the problem is that "TimeZoneMonitor" has been removed in glib (http://osdir.com/ml/commits.gnome/2011-08/msg05626.html) causing missing symbol message. The situation is fixed in "TimeZoneMonitor: Remove as was done in glib." patch for glibmm version 2.29.12 available from http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.29/. Inkscape starts without warning after installing the new version.
Manuel Hiebel 2011-08-31 13:51:44 CEST

CC: (none) => fundawang

Comment 1 Jani Välimaa 2011-08-31 18:32:52 CEST
Funda pushed 2.29.12, should be available on mirrors anytime soon.

Status: NEW => RESOLVED
CC: (none) => jani.valimaa
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.