Arch Linux

snoxu

Member

Registered: 2010-01-24

Posts: 141

[Solved] Gparted won't start; libgiomm-2.4.so

I just did a clean install of my system and I'm not able to start gparted for some reason:

/usr/sbin/gpartedbin: symbol lookup error: /usr/lib/libgiomm-2.4.so.1: undefined symbol: g_dbus_action_group_get_type

From a ubuntuforums thread discussing a similar problem I get that there is some kind of incompatibility with glibmm versions:
http://ubuntuforums.org/showthread.php?t=1836597&page=3

Any help is appreciated

Last edited by snoxu (2012-04-24 12:58:22)

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,362

Website

Re: [Solved] Gparted won't start; libgiomm-2.4.so

Is dbus running and do you have a dbus-session for your X session?

If the latter half is unclear, please describe your wm/de and how you start x and I can describe that more.

Edit: this is following a suspicion that it is a problem with dbus not the lib, but this could just be me being an idiot.

Last edited by Trilby (2012-04-24 03:00:07)

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

snoxu

Member

Registered: 2010-01-24

Posts: 141

Re: [Solved] Gparted won't start; libgiomm-2.4.so

deleted

Last edited by snoxu (2012-04-24 12:57:29)

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: [Solved] Gparted won't start; libgiomm-2.4.so

is all about his packages. He is not up to date or he replaced stock packages with some from aur.

---

Give what you have. To someone, it may be better than you dare to think.

snoxu

Member

Registered: 2010-01-24

Posts: 141

Re: [Solved] Gparted won't start; libgiomm-2.4.so

I did a system update and gparted now opens without errors.
I suspect a related package was updated and resolved whatever issue was going on.
Marking this as solved

Last edited by snoxu (2012-04-24 12:59:49)

snoxu

Member

Registered: 2010-01-24

Posts: 141

Re: [Solved] Gparted won't start; libgiomm-2.4.so

I checked pacman log and discovered glib2 was updated. And apparently it was updated yesterday in the official core repos.

I suspect this package had something to do with it. So maybe update timing is what originated the issue for me.

Last edited by snoxu (2012-04-24 13:08:55)