I experience the same problem on Manjaro Linux with gnome-keyring 3.20.0+57+g9db67ef6 and skypeforlinux. So it seems to be a bug in gnome- keyring, not in Ubuntu's package.
Some observations (citing my post on the Manjaro forums https://forum.manjaro.org/t/skypeforlinux-weird-and-inconsistent- authentification-behaviour/26076): I read that the old Skype client will stop working on Juli 1st, that is in less than two weeks, so I switched to the new client on several machines. However, the new client behaves in a weird way on starting up: 1. On some machines the user gets logged in without being asked for his password 2. On some machines the user gets a gnome-keyring password dialogue 3. On some machines the user has to enter the complete Skype user name and password into the Skype client itself In the ideal world I would like to have all machines behave as in 1. But how to do so? Does anybody else experience the same problem? I have digged deeper into this issue. It turned out that the gnome- keyring-daemon is running with different command lines in the three cases. Case 1: gnome-keyring-daemon --start --foreground --components=secrets (on my Manjaro laptop) gnome-keyring-daemon --start (on my old Arch install) Case2: gnome-keyring-daemon is not running at all. It is then launched when skypeforlinux is started and needs a password to unlock the keyring. Case3: gnome-keyring-daemon --daemonize --login So there seem to be two problems: First, the problem that gnome-keyring- daemon is not launched at login at all, second, if it is launched, it is launched with a bad command line. I looked in the Xfce session settings and there is an entry for gnome- keyring-daemon with the correct (Case 1) command line, but it is not activated. I activated it, but it seems to have changed nothing, gnome- keyring is still launched with the wrong command line. It looks like it is started by some system wide service and then the Xfce session settings entry collides with the already running instance. But what is this system wide service and why does it use the wrong command line on some machines but the right command line on others? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : email@example.com Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp