Upgrade to gnome-keyring broke network-manager-applet?

gabe_ · 2010-04-01 13:41:54

Greetings. I don't use Gnome, but I do use Network Manager.

After updating this morning, nm-applet fails to launch with the following message:

nm-applet: error while loading shared libraries: libgnome-keyring.so.0: cannot open shared object file: No such file or directory

I suspect this is due to the upgrade of gnome-keyring to 2.30.0-1.

Anyone else experiencing this problem? Any solutions?

The relevant lines from pacman.log, just in case:

[2010-04-01 08:11] synchronizing package lists
[2010-04-01 08:11] starting full system upgrade
[2010-04-01 08:16] upgraded glib2 (2.22.5-1 -> 2.24.0-1)
[2010-04-01 08:16] upgraded atk (1.28.0-1 -> 1.30.0-1)
[2010-04-01 08:16] upgraded bison (2.4.1-1 -> 2.4.2-1)
[2010-04-01 08:16] upgraded device-mapper (2.02.60-3 -> 2.02.61-1)
[2010-04-01 08:16] upgraded pango (1.26.2-1 -> 1.28.0-1)
[2010-04-01 08:16] upgraded libcups (1.4.2-5 -> 1.4.3-1)
[2010-04-01 08:16] upgraded gtk2 (2.18.9-2 -> 2.20.0-1)
[2010-04-01 08:16] upgraded libidl2 (0.8.13-1 -> 0.8.14-1)
[2010-04-01 08:16] upgraded orbit2 (2.14.17-1 -> 2.14.18-1)
[2010-04-01 08:16] upgraded gconf (2.28.0-1 -> 2.28.1-1)
[2010-04-01 08:16] upgraded gnome-icon-theme (2.28.0-1 -> 2.30.0-1)
[2010-04-01 08:16] upgraded gnome-keyring (2.28.2-1 -> 2.30.0-1)
[2010-04-01 08:16] upgraded libgl (7.7-1 -> 7.7.1-0.1)
[2010-04-01 08:16] upgraded intel-dri (7.7-1 -> 7.7.1-0.1)
[2010-04-01 08:16] upgraded librsvg (2.26.0-2 -> 2.26.2-1)
[2010-04-01 08:16] upgraded libwnck (2.28.0-1 -> 2.30.0-1)
[2010-04-01 08:16] upgraded lvm2 (2.02.60-3 -> 2.02.61-1)
[2010-04-01 08:16] upgraded mesa (7.7-1 -> 7.7.1-0.1)
[2010-04-01 08:16] when you use a non-reparenting window manager
[2010-04-01 08:16] set _JAVA_AWT_WM_NONREPARENTING=1 in
[2010-04-01 08:16] /etc/profile.d/openjdk6.sh
[2010-04-01 08:16] upgraded openjdk6 (6.b17_1.7.1-1 -> 6.b17_1.7.2-1)
[2010-04-01 08:16] installed libffi (3.0.9-1)
[2010-04-01 08:16] upgraded pygobject (2.20.0-1 -> 2.21.1-1)
[2010-04-01 08:16] upgraded pygtk (2.16.0-2 -> 2.17.0-1)
[2010-04-01 08:16] upgraded xterm (255-1 -> 256-1)
[2010-04-01 08:16] upgraded zenity (2.28.0-1 -> 2.30.0-1)

Gigaplex · 2010-04-02 02:53:46

I just ran into the same problem. I worked around the issue by reverting to the older version, luckily I still had it in my package cache.

sudo pacman -U --asdeps /var/cache/pacman/pkg/gnome-keyring-2.28.2-1-x86_64.pkg.tar.gz

Allan · 2010-04-02 03:05:28

That file is in the libgnome-keyring package.

barzam · 2010-04-02 06:20:46

I had the same problem and installing libgnome-keyring makes nm-applet start. However my passwords are not saved, like they used to be.

How can I fix this? Running Xmonad with some Gnome programs installed.

Same problem here: http://bbs.archlinux.org/viewtopic.php?id=94334
http://bbs.archlinux.org/viewtopic.php?id=85357

Last edited by barzam (2010-04-02 06:21:48)

gabe_ · 2010-04-02 12:55:07

Allan wrote:

That file is in the libgnome-keyring package.

Thanks. This solved it for me.

barzam wrote:

I had the same problem and installing libgnome-keyring makes nm-applet start. However my passwords are not saved, like they used to be.
How can I fix this? Running Xmonad with some Gnome programs installed.

I can't comment on this, as I don't save any passwords for any networks that I regularly connect to. I can confirm that the rest of my network settings were saved (SSID's, DNS Servers, etc).

enrique · 2010-04-02 13:40:56

Changing /usr/share/dbus-1/services/org.gnome.keyring.service to:

[D-BUS Service]
Name=org.freedesktop.secrets

Fixed it for me.

I found the fix here: https://bugzilla.redhat.com/show_bug.cgi?id=572137 maybe I should create a bugreport?

alphazo · 2010-04-02 14:53:53

Gigaplex wrote:

I just ran into the same problem. I worked around the issue by reverting to the older version, luckily I still had it in my package cache.
sudo pacman -U --asdeps /var/cache/pacman/pkg/gnome-keyring-2.28.2-1-x86_64.pkg.tar.gz

When trying this I get:

:: libgnome-keyring: requires gnome-keyring>=2.30.0

And I can't find any earlier version of this libgnome-keyring!

This is part of my emergency downgrade as recent GTK2 broke Thunar and other things.
http://bbs.archlinux.org/viewtopic.php?id=94272

wonder · 2010-04-02 15:50:17

http://bugs.archlinux.org/task/18930

in comments is the solution

@alphazo this is the first release of libgnome-keyring.

Last edited by wonder (2010-04-02 15:51:02)

alphazo · 2010-04-03 06:12:59

This bug report gives a different solution. http://bugs.archlinux.org/task/18930

Adding this line to ~/.xinitrc fixes the problem and is probably the most correct solution:

eval $(gnome-keyring-daemon -s --components=pkcs11,secrets,ssh)

So what is the preferred solution versus the one described above:

Changing /usr/share/dbus-1/services/org.gnome.keyring.service to:
[D-BUS Service]
Name=org.freedesktop.secrets

Got an answer from project manager regarding the /usr/share/dbus-1/services/org.gnome.keyring.service way, apparently this is not the preferred way.

messing with this file is not the proper way. this change would be good only if upstream is changing that.

[EDIT] I tried to use the recommended fix but it doesn't work. I've added:

eval $(gnome-keyring-daemon -s --components=pkcs11,secrets,ssh)

to ~/.xinitrc (before the exec command)

and also

auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start

to /etc/pam.d/slim as suggested in the bug report

This fix doesn't work for me. At that point I'm going back to the un-preferred way.

Last edited by alphazo (2010-04-03 09:04:52)

wonder · 2010-04-03 09:32:37

better post your .xinitrc

alphazo · 2010-04-03 09:41:31

I use both Slim and XfCE4

~/.xinitrc

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)

# exec gnome-session
# exec startkde
#exec startxfce4
# ...or the Window Manager of your choice
eval $(gnome-keyring-daemon -s --components=pkcs11,secrets,ssh)
exec ck-launch-session startxfce4

I also added two lines at the end of my /etc/pam.d/slim

#%PAM-1.0
auth            requisite       pam_nologin.so
auth            required       pam_env.so
auth            required       pam_unix.so
account       required       pam_unix.so
session        required       pam_limits.so
session        required       pam_unix.so
password     required       pam_unix.so
auth            optional        pam_gnome_keyring.so
session        optional        pam_gnome_keyring.so      auto_start

Allan · 2010-04-03 09:51:57

I have the same setup (slim + xfce) and can confirm that adding that line to .xinitrc does not work. Currently I have to manually run gnome-keyring-daemon to start the keyring and have to type the keyring password.

barzam · 2010-04-03 09:59:41

Same here, running Slim + XMonad.

I wanna punch Networkmanager in its virtual face after every update when stuff starts breaking.. it's nice when it works though

alphazo · 2010-04-03 10:01:50

The other fix, even if not recommended works though. BTW, I also have wicd handy in case things break too badly (too bad it doesn't support wireless broadband and VPN)

wonder · 2010-04-03 11:25:07

i don't get it. what does it need to run this at login? the older version only had gnome-keyring-daemon.desktop with gnome-keyring-daemon --start

gnome-keyring /etc/xdg/autostart/gnome-keyring-pkcs11.desktop
gnome-keyring /etc/xdg/autostart/gnome-keyring-secrets.desktop
gnome-keyring /etc/xdg/autostart/gnome-keyring-ssh.desktop

Allan · 2010-04-03 12:13:50

I added gnome-keyring-daemon to my autostarted applications in XFCE. I still have to type my keyring password, but at least it starts now.

sistematico · 2012-01-23 15:29:45

Any progress?

Arch Linux

#1 2010-04-01 13:41:54

Upgrade to gnome-keyring broke network-manager-applet?

#2 2010-04-02 02:53:46

Re: Upgrade to gnome-keyring broke network-manager-applet?

#3 2010-04-02 03:05:28

Re: Upgrade to gnome-keyring broke network-manager-applet?

#4 2010-04-02 06:20:46

Re: Upgrade to gnome-keyring broke network-manager-applet?

#5 2010-04-02 12:55:07

Re: Upgrade to gnome-keyring broke network-manager-applet?

#6 2010-04-02 13:40:56

Re: Upgrade to gnome-keyring broke network-manager-applet?

#7 2010-04-02 14:53:53

Re: Upgrade to gnome-keyring broke network-manager-applet?

#8 2010-04-02 15:50:17

Re: Upgrade to gnome-keyring broke network-manager-applet?

#9 2010-04-03 06:12:59

Re: Upgrade to gnome-keyring broke network-manager-applet?

#10 2010-04-03 09:32:37

Re: Upgrade to gnome-keyring broke network-manager-applet?

#11 2010-04-03 09:41:31

Re: Upgrade to gnome-keyring broke network-manager-applet?

#12 2010-04-03 09:51:57

Re: Upgrade to gnome-keyring broke network-manager-applet?

#13 2010-04-03 09:59:41

Re: Upgrade to gnome-keyring broke network-manager-applet?

#14 2010-04-03 10:01:50

Re: Upgrade to gnome-keyring broke network-manager-applet?

#15 2010-04-03 11:25:07

Re: Upgrade to gnome-keyring broke network-manager-applet?

#16 2010-04-03 12:13:50

Re: Upgrade to gnome-keyring broke network-manager-applet?

#17 2012-01-23 15:29:45

Re: Upgrade to gnome-keyring broke network-manager-applet?

Board footer