Thank you, @leftyfb.
I'm seeing some strange behavior when deleting the files in
~/.config/autostart/
I can delete the file. If I open the GUI for startup Applications it
has a line for gnome-keyring-daemon --start --components=ssh which seems
unrelated to the text file in ~/.config/autostart. If I delete both the
GUI entry and the text file and reboot, I get the same behaviour and
have to run gnome-keyring-daemon --replace and enter my password. I
also have to open the HUD to get the password prompt to show itself
otherwise nothing happens.
Also after reboot, the entry in the startup applications gui shows up
again even though the text file is not there. Upon closing the GUI, the
text file appears again.
As for the rest of the system,
In /etc/xdg/autostart I have three gnome-keyring-daemon files for secrets, ssh,
and pkcs11. These files have been here since November 2015.
They contain:
Exec=/usr/bin/gnome-keyring-daemon --start --components={{one of
secrets, ssh, or pkcs11}}
the rest of these three files are the same and contain the following
lines:
OnlyShowIn=GNOME;Unity;MATE;
X-GNOME-Autostart-Phase=Initialization
X-GNOME-AutoRestart=false
X-GNOME-Autostart-Notify=true
X-GNOME-Bugzilla-Bugzilla=GNOME
X-GNOME-Bugzilla-Product=gnome-keyring
X-GNOME-Bugzilla-Component=general
X-GNOME-Bugzilla-Version=3.18.3
NoDisplay=true
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
Status in D-Bus:
New
Status in chromium-browser package in Ubuntu:
Invalid
Status in flatpak package in Ubuntu:
Confirmed
Status in gdm package in Ubuntu:
Confirmed
Status in gnome-keyring package in Ubuntu:
Confirmed
Status in libgnome-keyring package in Ubuntu:
Confirmed
Status in lightdm 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/dbus/+bug/1689825/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
