Gnome 3.4 gnome-keyring problem

hey,
just upgraded to gnome 3.4.
First thanks for the hard work over the weekend besides your jobs and private life :-) to bring gnome 3.4.1 to extra.
i had a problem after log in, that the desktop didn`t come up.
Found a solution with downgrading gnome-keyring to the version 3.2.2.
In .xsession-errors there are two lines, which could explain the behaviour:
/usr/bin/gnome-keyring-daemon: error while loading shared libraries: libgck-1.so.0: cannot open shared object file: No such file or directory
/usr/bin/gnome-shell: error while loading shared libraries: libgcr-3.so.1: cannot open shared object file: No such file or directory
Any ideas to get theses libraries?
Or are there old dependencies, that were not completely deleted?
regards

I had a problem with evolution and network manager with the gnome-keyring 3.4.1 update. A downgrade to 3.2.2-3 worked, but I have since re-installed (pacman -S) gnome-keyring followed by gcr. That works. Fyi, resintalling gcr then gnome-keyring did not work for me .

Similar Messages

Gnome-keyring-daemon crashes when blank passwords are entered.

Steps to reproduce:
Install fresh Arch Linux
Install chromium, gnome, xorg-server, and xorg-xinit
Put "exec gnome-session" in ~/.xinitrc
Launch startx
Open chromium
On prompt for new keyring creation, leave password fields blank and press OK.
Witness gnome-shell crashing.
What's supposed to happen:
It's supposed to prompt the user asking if it's OK to have unencrypted keys.
What happens:
The gnome-shell crashes, and no keyrings or passwords were set or created.
journalctl output:
Sep 04 21:11:04 Winston gnome-session[1417]: Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Sep 04 21:11:04 Winston gnome-session[1417]: Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
Sep 04 21:11:14 Winston gnome-session[1417]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600029 (New Tab - )
Sep 04 21:11:14 Winston gnome-session[1417]: Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Sep 04 21:11:18 Winston gnome-keyring-daemon[1478]: keyring alias directory: /home/naelstrof/.local/share/keyrings
Sep 04 21:11:31 Winston gnome-session[1417]: ** Message: init gpgme version 1.4.3
Sep 04 21:11:31 Winston gnome-session[1417]: ** Message: DNS-SD initialization failed: Daemon not running
Sep 04 21:11:38 Winston gnome-session[1417]: (gnome-shell:1494): Clutter-CRITICAL **: clutter_text_set_color: assertion `CLUTTER_IS_TEXT (self)' failed
Sep 04 21:11:38 Winston gnome-session[1417]: (gnome-shell:1494): Clutter-CRITICAL **: clutter_text_set_cursor_size: assertion `CLUTTER_IS_TEXT (self)' failed
Sep 04 21:11:38 Winston gnome-session[1417]: (gnome-shell:1494): Clutter-CRITICAL **: clutter_text_set_cursor_color: assertion `CLUTTER_IS_TEXT (self)' failed
Sep 04 21:11:38 Winston gnome-session[1417]: (gnome-shell:1494): Clutter-CRITICAL **: clutter_text_set_selected_text_color: assertion `CLUTTER_IS_TEXT (self)' failed
Sep 04 21:11:38 Winston gnome-session[1417]: (gnome-shell:1494): Clutter-CRITICAL **: clutter_text_get_font_name: assertion `CLUTTER_IS_TEXT (text)' failed
Sep 04 21:11:38 Winston gnome-session[1417]: (gnome-shell:1494): Clutter-CRITICAL **: clutter_text_set_font_name: assertion `CLUTTER_IS_TEXT (self)' failed
Sep 04 21:11:38 Winston gnome-session[1417]: (gnome-shell:1494): Clutter-CRITICAL **: clutter_text_get_font_name: assertion `CLUTTER_IS_TEXT (text)' failed
Sep 04 21:11:38 Winston gnome-keyring-daemon[1478]: prompting failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Sep 04 21:11:38 Winston gnome-session[1417]: WARNING: Application 'gnome-shell.desktop' killed by signal 11
Sep 04 21:11:38 Winston gnome-session[1417]: gnome-session[1417]: WARNING: Application 'gnome-shell.desktop' killed by signal 11
Sep 04 21:11:38 Winston gnome-session[1417]: ** Message: applet now removed from the notification area
Sep 04 21:11:39 Winston gnome-session[1417]: JS LOG: GNOME Shell started at Wed Sep 04 2013 21:11:39 GMT-0600 (MDT)
Anyone got any tips to what could be wrong? It's infuriating to have it ask to create a new key, while it won't let me set a blank key.
Giving the prompt an actual password works as intended, it's impossible to set it as a blank password, even using seahorse.
It's acting as if something is wrong with DBus, but journalctl -u dbus shows no problems. as well as systemctl status dbus.
Thanks for any help.
Oh yeah and attempting to use gdm causes the gnome-session not to launch at all. Since gdm created a key, I'm guessing the problems are related.
Last edited by naelstrof (2013-09-05 03:27:50)

I found an acceptable workaround:
Create a keychain with the same password as your account named "Login" using the keychain utility seahorse.
Follow the autologin instructions for console based login here: https://wiki.archlinux.org/index.php/GN … at_Startup
Restart X.
gdm still fails to start x though, despite the startx command working fine.
Uninstalling gnome-keychain works just as well though :u.
Last edited by naelstrof (2013-09-05 05:39:09)

[solved] gnome 3.2.1-1/gdm 3.2.1.1-1 - gnome-keyring password!

Hi guys,
I have some trouble using the 'Online Accounts' feature of Gnome Shell.
When I log into my Google account, I'm asked to grant access to my contacts, docs and so on for Gnome. The problem is that I'm prompted to type my Gnome Keyring password (I thought it was automatically unlocked when logging through GDM) but my user password doesn't work! I even tried to enter my root password but it doesn't work either.
Am I missing something here?
Thanks
Last edited by sclarckone (2011-12-29 16:29:00)

wonder wrote:try to change the keyring password to match the system one from seahorse
I've already tried but I have the same problem: since I don't know the current password, I can't change it.

[SOLVED] Subversion will not use gnome-keyring

Hi,
Anyone know how to use gnome-keyring with subversion? When I run svn up, I get the following warning every time:
ATTENTION! Your password for authentication realm:
<https://123.456.789.012:443> Subversion Repository
can only be stored to disk unencrypted! You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible. See the documentation for details.
You can avoid future appearances of this warning by setting the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'/home/david/.subversion/servers'.
Store password unencrypted (yes/no)?
I googled a bit and found that you can use gnome-keyring to store passwords encrypted. I tried setting "password-stores = gnome-keyring" in ~/.subversion/config, but this had no effect.
I have the package 'extra/gnome-keyring' installed. From what I can see Subversion is always compiled with gnome-keyring support. I also tried starting the gnome-keyring-daemon, since it's not started by default (I don't use GNOME as my WM). I started it from the command line using 'gnome-keyring-daemon' command. But this had no effect - subversion acts like it doesn't know gnome-keyring even exists.
Any idea?
Cheers,
David
Last edited by david00 (2010-03-22 09:45:32)

I had the same problem.
When the daemon gets started it prints some environment variables with values to stdout. I think other programs like subversion read these to connect to the daemon.
Starting the daemon like this:
export `gnome-keyring-daemon`
in your .xinitrc or at a comparable place should solve your problem.
Of course, this only applies if you're not using the gnome desktop environment.

SVN over SSH won't interface with gnome-keyring

The title about says it all. I log into my box at home and try to pull down the latest revision from an SVN server and get the following message.
ATTENTION! Your password for authentication realm:
<https://*************> Subversion repository
can only be stored to disk unencrypted! You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible. See the documentation for details.
You can avoid future appearances of this warning by setting the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'/home/om/.subversion/servers'.
Is there anyway to have it store password encrypted? I found another topic which recommended running
export `gnome-keyring-daemon`
but that didn't solve the problem. In my subversion config I have specified gnome-keyring as a password store and it is installed on the system.

Will a simple reboot help? (But how, without ssh )
It might. You can issue a restart command through Server Monitor if you configured LOM properly, as I don't believe that it (Server Monitor) relies on ssh to issue commands.
-Doug

Gnome-keyring-daemon will not save my passphrase

I use Slim to log in to my Openbox session on my dear EeePC 901. What I cannot seem to do is set up my environment so that gnome-keyring-daemon not only pops up and asks for my ssh passphrases but also save them for future use. Ideally I would like gnome-keyring to unlock the keyring automatically on login. I have the pop up and ask for passphrase part figured out, but now I'm basically lost when trying to get it to remember my passphrase.
Set up: slim-plus, logging in using my .xinitrc (below):
~/.xinitrc:
source /etc/X11/xinit/xinitrc.d/30-dbus
# gnome-keyring stuff, which almost works
eval $(gnome-keyring-daemon)
export GNOME_KEYRING_PID
export GNOME_KEYRING_SOCKET
export SSH_AUTH_SOCK
# desktop
eval $(cat ~/.fehbg) &
wicd-client &
syndaemon -i 0.7 -t -k &
tint2 &
# finally, launch openbox
exec ck-launch-session openbox
/etc/pam.d/slim (if it even matters?):
#%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
session required pam_env.so readenv=1 envfile=/etc/profile.d/locale.sh
session optional pam_gnome_keyring.so auto_start
password required pam_unix.so
Any hints on this? I had it running quite some time ago on another computer (no, not using GDM then either) and I didn't have this much trouble setting it all up.

Same problem here.

Gnome-keyring + networkmanager: Not prompting for password

I recently shifted from wicd to networkmanager & I want it to be that way. There is one problem that's troubling me. As a non-root user, if I connect to a new network, the nm-applet doesn't ask for passwords.
The logs say:
2014-07-19T08:29:45.217385+05:30 archlinux NetworkManager[20784]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
2014-07-19T08:29:45.217385+05:30 archlinux NetworkManager[20784]: <info> Activation (wlan0/wireless): access point 'my access point name' has security, but secrets are required.
I run "awesome wm" and I've configured gnome-keyring via the "pam" method & I believe that it works.
➜ 0 /home/shadyabhi [ 9:09AM] % echo $SSH_AUTH_SOCK
/run/user/1000/keyring/ssh
➜ 0 /home/shadyabhi [ 9:09AM] % echo $GPG_AGENT_INFO
/run/user/1000/keyring/gpg:0:1
➜ 0 /home/shadyabhi [ 9:09AM] % ss -xl | grep -o '/run/user/1000/keyring/ssh'
/run/user/1000/keyring/ssh
➜ 0 /home/shadyabhi [ 9:09AM] %
Running "sudo nm-applet" from terminal recognizes gnome-keyring.
➜ 2 /home/shadyabhi [ 8:38AM] % sudo nm-applet
(nm-applet:21840): libnotify-WARNING **: Failed to connect to proxy
(nm-applet:21840): nm-applet-WARNING **: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .servi
ce files
nm-applet-Message: No keyring secrets found for "my access point name"/802-11-wireless-security; asking user.
Can anyone help me in finding out what might be wrong? Thanks.

I had the same issue. Turns out I was using SLiM with auto_login enabled, which doesn't unlock the GNOME keyring on login (see this post). Changing auto_login to false solved the issue.

[Solved] Why couldn't Python3 handle GNOME Keyring?

Hello, everyone!
I'm using Awesome WM as desktop,as well as SLiM as login manager , and python-keyring 4.0-2. The GNOME packages I've installed are as follow:
gnome-icon-theme
gnome-icon-theme-symbolic
gnome-keyring
libgnome-keyring
libsoup
python-gobject
seahorse
What's more, I've followed the instruction from Arch Wiki and set up the PAM config files and .xinitrc(My .xinitrc).
When I finish logging in with SLiM, I open htop immediately, and find the process gnome-keyring-daemon running. Then I open seahorse (GUI front-end of GNOME Keyring), the default keyring 'Login' is unlocked.
Hence, I think that GNOME Keyring is unlocked automatically at login in my system. Refer to https://wiki.gnome.org/Projects/GnomeKeyring/Pam
Now, I open the terminal and execute the following command:
$ python
Python 3.4.2 (default, Oct 8 2014, 13:44:52)
[GCC 4.9.1 20140903 (prerelease)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import keyring
>>> print(keyring)
<module 'keyring' from '/usr/lib/python3.4/site-packages/keyring/__init__.py'>
>>> print(keyring.get_keyring())
<keyring.backends.file.EncryptedKeyring object at 0x7ff0189e83c8>
>>> keyring.set_password('test_server', 'test_user', 'test_password')
Please set a password for your new keyring:
Please confirm the password:
After that I open seahorse, and find no item added. What's more, there is an item added in ~/.local/share/python_keyring/crypted_pass.cfg :
[test_5Fserver]
test_5fuser = (Some encrypted code)
This means, Python3 fails to handle GNOME Keyring with Python Keyring.
=========================================
The expected response is as follow：
>>> print(keyring.get_keyring())
<keyring.backends.Gnome.Keyring object at xxxxxxxx>
>>> keyring.set_password('test_server', 'test_user', 'test_password')
>>>
Then open seahorse, there should have been a new item added in the keyring 'Login' like the picture below:
==========================================
So What's the problem? Is it a PEBKAC? How can I fix it?
Yours sincerely
Last edited by firef0x (2014-11-22 02:45:05)

Hi firef0x,
in the past python-keyring had some problem in the detection of the default keyring backend but I thought that this problem was solved a long ago (at least it detects my kwallet backend correctly). However, you can try to set your default backend manually by creating the file ~/.local/share/python_keyring/keyringrc.cfg with the following content
[backend]
default-keyring=keyring.backends.Gnome.Keyring

[solved] gnome-keyring won't save the passphrase for ssh-keys

Hello,
I'm trying to use the gnome-keyring to store the passphrases for my ssh-keys in gnome-terminal.
I started to generate my ssh-keys as described in this article.
After that I transfered the key via "ssh-copy-id" to my other computer.
Then I connected to that computer via nautilus and stored the passphrase. Now it is no problem to connect without typing in the passphrase again.
When I try to connect to that computer via a gnome-terminal ssh asks every time for the passphrase.
I tried a lot of things, but I can't solve this issue.
Does anybody got an idea how to tell the gnome-keyring that it should store the passphrase for connections via terminals?
Any help is appreciated Maybe I just don't see the solution, but I'm still new to ssh.
Thanks in advance!
David
Last edited by senior_spielbergo (2011-08-02 15:01:04)

Hi alexcriss,
I tried to open the terminal from the application menu, but it didn't help.
I searched the forum for "GDM keyring" and I found a few topics dealing with similar problems, but I couldn't find a solution.
I have forgotten to tell, that when I enter
ssh-add -L
it returns
The agent has no identities.
Typing
ssh-add ~/.ssh/id_ecdsa
returns:
Enter passphrase for /home/david/.ssh/id_ecdsa:
Error reading response length from authentication socket.
Could not add identity: /home/david/.ssh/id_ecdsa
Maybe this helps to find the error.
Thanks again,
David

Gnome-keyring-daemon and ssh outside gnome

I had gnome-keyring set up so that on login it unlocks the keyring and reads ssh keys (so that it acts as a ssh-agent), as described here: http://live.gnome.org/GnomeKeyring/Ssh and here http://live.gnome.org/GnomeKeyring/Pam
This was working great also outside gnome (for instance in xmonad and openbox), up to version 2.24.1. However, after update to 2.26.0-1 this stopped working. It is still OK in gnome, but in other environments (where the only gnome thing that is loaded is gnome-keyring-manager) it doesn't work correctly - it loads, but instead of creating both /tmp/keyring-<sth>/socket and /tmp/keyring-<sth>/socket.ssh it only created the first one, so no ssh support.
Can anyone help a bit with what has changed, or what could have gone wrong?
Thanks.

bender02 wrote:
abarilla wrote:I had the same problem with openbox. Using gdm fixed it.
Well if this is the only way to fix this then it sucks big time, since I don't want to run a huge login manager just to unlock the passwords
adding the content of /etc/X11/xinit/xinitrc.d/30-dbus to the ~/.xinitrc works for me.
# launches a session dbus instance
dbuslaunch="`which dbus-launch 2>/dev/null`"
if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
eval `$dbuslaunch --sh-syntax --exit-with-session`
fi
or sourcing the 30-dbus file in the ~/.xinitrc
source /etc/X11/xinit/xinitrc.d/30-dbus
or for all files in /etc/X11/xinit/xinitrc.d/
source /etc/X11/xinit/xinitrc.d/*
That's what GDM and KDM do.
Thanks to Jan de Groot for the hint.
Last edited by SiD (2009-04-14 09:58:46)

Freenx crash with gnome-keyring-daemon

I have gnome 2.26 installed with nxserver 3.2.0-73 and nxnode 3.2.0-73 installed.
When I log into the computer locally, everything works fine.
Logging into gnome via nx, when the gnome-keyring-daemon is running, anytime after I open
either gnome-appearance-properties, gnome-keyboard-properties or any of the other gnome programs,
launching programs causes NX to terminate.
With logging on, it just says nx session terminated.
nothing showes up in the main message log.
using "exec dbus-launch --exit-with-session /usr/bin/gnome-session" as my command.
I have fonts installed and everything.
Both XFCE and KDE 4.2 work fine in NX.
I have all the font packages installed also.
I have set up older versions of gnome with nx on other machines and never had this problem.
Anyone have any ideas?

I just also noticed that opening .jpg files crashes NX.

Unable to get Gnome-Keyring working with nm-applet

Hi guys
I've installed openbox and using NetworkManager/nm-applet to manage my network connections.
I prefer it over other utils as it has good support for mobile connections etc.
I'm using qingy as my login manager.
I have added the following to /etc/pam.d/qingy
auth optional /lib/security/pam_gnome_keyring.so
session optional /lib/security/pam_gnome_keyring.so auto_start
and the following to /etc/pam.d/passwd
password optional pam_gnome_keyring.so
as per the network manager wiki http://wiki.archlinux.org/index.php/Net … fter_login
I have the following in my session login script:
nm-applet --sm-disable &
I think if I remember correctly, the Gnome keyring dialog popped up once or twice in the beginning, but now it never happens. nm applet now always requests my WPA key upon login.
My intention is to have the key stored in gnome-keyring so that I don't have to enter it every time I log in.
Any help would be greatly appreciated.

Hi dieghen89
Nice to know I'm not the only one pulling out hair over here
I was playing around and did the following:
1. Exit nm-applet completely
2. $ gnome-keyring-daemon --start //I know that the daemon is running. --help states that it starts or initialize an already running daemon
3. Run nm-applet again
And the keyring dialog actually did pop up asking for the password to unlock it.
Now I thought a quick-fix would be to add gnome-keyring-daemon --start to my startup script before nmapplet &
But alas. doesn't work

[Solved] SDDM does not unlock gnome-keyring

Hi everyone!
I did some searching but didn't find the answer to my issue yet.
I'm using SDDM to log in to i3. The issue is that my keyring doesn't get unlocked after login and it asks for the password on first access (owncloud client).
Now I want to have the gnome-keyring automatically unlocked after logging in. My user and keyring password are identical. I've also followed the instructions and added the suggested parts to my pam files:
cat /etc/pam.d/sddm
#%PAM-1.0
auth include system-login
auth optional pam_gnome_keyring.so
account include system-login
password include system-login
password optional pam_gnome_keyring.so use_authtok
session include system-login
session optional pam_gnome_keyring.so auto_start
ps aux | grep keyring
xxx 788 0.0 0.0 428836 6228 ? SLl Apr25 0:04 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
sudo find / -name "pam_gnome_keyring.so"
/usr/lib/security/pam_gnome_keyring.so
Nevertheless the keyring is not unlocked automatically and asks for a password on first access.
Any suggestions? Thanks in advance.
(It began with the ownCloud client, which asked for the password after every login. I installed gnome-keyring and added a "login" password group with seahorse, which solved the issue, so it appears gnome-keyring is working.)
Last edited by one1 (2014-04-27 11:01:21)

Thanks, it actually appears that's the case I tried the various available versions and with the git ones, unlocking is working, but it's not possible to log out of i3 without the whole X session breaking down, forcing a reboot.
So I think I'll enter the password or give gdm another shot.

[SOLVED] Chromium with Gnome Keyring as password store?

Hi there.
I'm trying to use gnome keyring as default password store for google chromium. I read all over the web about starting chromium using options '--password-store=detect' (to detect gnome evnironment) or even '--password-store=gnome' (force gnome). None of these options work for me, as I get the same result: chromium will store password in its own keyring.
$ pacman -Q chromium gnome-keyring
chromium 18.0.1025.162-1
gnome-keyring 3.2.2-3
Any idea how I can make it work as planned?
Thanks in advance!
Last edited by josephg (2012-06-12 17:56:48)

sl1pkn07 wrote:makedepends=('python2' 'perl' 'gperf' 'yasm' 'mesa' 'libgnome-keyring'
chromium use by default libgnome-keyring
I don't think so, that's a makedepends; it means it's needed for building the package, not for using it.
On my system (not running any desktop environment), I need to run chromium with --password-store=gnome for it to use the gnome keyring.

"The GNOME keyring manager hijacked the GnuPG agent"

I've run gpg from the command line and suddenly a dialog box appeared asking for my password: it even asked if I wanted to remember it.
Meanwhile, in my bash terminal gpg had this to say:
gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent.
gpg: WARNING: GnuPG will not work proberly - please configure that tool to not interfere with the GnuPG system!
Googling didn't help much, seems to be a new "feature"...
Any idea how can I configure the keyring manager to stay away when I'm working in bash?

I had similar situation and decided to disable gnome-keyring's ssh and gpg agents. https://wiki.archlinux.org/index.php/GN … ing_daemon
The reason is that gnome keyring is active only when you have a GUI session active, thus it does not work for headless machines or when one SSH to the machine. It is just easier for me to use "default" agents.
PS The ssh-agent and gpg-agent is a mess from usability/configuration point of view (without those ugly environment variables). I wish there was a systemd friendly implementation of these agents.
PPS The latest gnupg use "use-standard-socket' config option by default, it means one does not need to start gpg-agent and configure GPG_AGENT_INFO envvar manually. gpg will start agent for you transparently.

Gnome 3.4 gnome-keyring problem

Similar Messages

Maybe you are looking for