Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 274148 - media-gfx/inkscape-0.46-r5 - inkscape: Symbol `_ZTIN3Gtk6WidgetE' has different size in shared object, consider re-linking
Summary: media-gfx/inkscape-0.46-r5 - inkscape: Symbol `_ZTIN3Gtk6WidgetE' has differe...
Status: RESOLVED CANTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-14 18:10 UTC by Michael P. Soulier
Modified: 2009-06-25 14:14 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 Michael P. Soulier 2009-06-14 18:10:17 UTC
After picking up recent upgrades, I noticed suddenly that inkscape won't start.

msoulier@anton:~$ inkscape: Symbol `_ZTIN3Gtk6WidgetE' has different size in
shared object, consider re-linking

(inkscape:24474): glibmm-CRITICAL **: Glib::Interface::Interface(const
Glib::Interface_Class&): assertion `gobject_ != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

(inkscape:24474): gtkmm-CRITICAL **:
void<unnamed>::container_foreach_callback(GtkWidget*, void*): assertion
`widget != 0' failed

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix


Reproducible: Always

Steps to Reproduce:
I'm not sure exactly which upgrades resulted in this situation, but revdep-rebuild showed that everything was fine. 



Expected Results:  
I expected inkscape to start normally.

Rebuilding inkscape solved the issue.
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2009-06-15 01:00:59 UTC
Um, have you ever used the revdep-rebuild tool from the app-portage/gentoolkit package?
Comment 2 Michael P. Soulier 2009-06-15 01:25:02 UTC
(In reply to comment #1)
> Um, have you ever used the revdep-rebuild tool from the app-portage/gentoolkit
> package?

Yes, if you look at the description, you'll see that I ran it and it reported that nothing needed rebuilding. It apparently missed this problem.
Comment 3 anomen 2009-06-15 10:20:37 UTC
see bug 200130, it might the same problem

> Now rebuilding gtkmm and glibmm (2.14.2) ...
> OK, recompiling boths libs _and_ Inkscape makes this programs works again