Comment 41 for bug 1689825

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?