I can now confirm that these instructions have worked for me. Thank you
all. I did change my password as suggested in comment #74 by
bytecommander.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
I added a bad command line into the GUI and .config/autostart file to be
sure that it could not run the command to start the daemon.
upon reboot I still see two daemons running, one with my username as owner and
one with lightdm as owner.
I'm still getting the same behavior of slow launch of
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.
Removing flatpak/dbus-user-session did not change anything for me on
16.04.2. dbus-user-session was first installed on May 8th 2017 in
conjunction with an upgrade of flatpak (and other software) as can be
seen in attached apt history log entry.
flatpak list
org.pitivi.Pitivi/x86_64/stable
I'm also seeing slow response to taking a screenshot with shortcut keys.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To
I'm also seeing slow startup in chrome/chromium, and gnome-terminal
using keyboard shortcut.
When launching chromium-browser from command line I see the following
messages:
Using PPAPI flash.
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so
--ppapi-flash-version=
@chenzero Thank you. I found the LTS Hardware Enablement Stack wiki and
I installed the Quantal stack that updated me to kernel
3.5.0-27-generic. This resolved the error.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-nettool
same problem started after kernel update
uname -r
3.2.0-40-generic
dmesg -k |grep GEN6_RP
[186612.716928] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy:
GEN6_RP_INTERRUPT_LIMITS expected 1600, was 1206
lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core
