[Bug 1689825] Re: gnome-keyring not unlocked on boot
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. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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 terminal and extremely long load of chrome if I don't run the workaround command gnome-keyring-daemon --replace and enter my password. After logging in for the second time, the daemon owned by lightdm exits leaving only one daemon running owned by my user. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not unlocked on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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 org.gnome.Platform/x86_64/3.22 user,runtime flatpak --user uninstall org.pitivi.Pitivi flatpak --user uninstall org.gnome.Platform apt-get purge flatpak autoremoved libostree-1-1 xdg-desktop-portal xdg-desktop-portal-gtk apt-get purge dbus-user-session reboot and check for running gnome-keyring-daemon $ psa | grep gnome-keyring-daemon antonios 4592 0.0 0.0 14524 980 pts/17 S+ 13:58 0:00 | \_ grep gnome-keyring-daemon lightdm 1589 0.0 0.0 123296 3148 ?Sl 13:56 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login antonios 2652 0.1 0.2 232048 34776 ?SLl 13:57 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login the lightdm owned process stopped running after a few minutes. to workaround, I still have to run `gnome-keyring-daemon --replace' ** Attachment added: "I think the issue started after this upgrade" https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+attachment/4914766/+files/upgrade-issue-begin.txt -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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= [3823:3823:0513/140354.928952:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool) 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. [3909:3909:0513/140445.076144:ERROR:interface_registry.cc(210)] Failed to locate a binder for interface: chrome::mojom::ResourceUsageReporter requested by: exposed by: via InterfaceProviderSpec "service_manager:connector". 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. [3823:3823:0513/140510.780378:ERROR:display_info_provider_aura.cc(31)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const display::Display&, extensions::api::system_display::DisplayUnitInfo*) Starting [1:1:0513/140539.638655:ERROR:interface_registry.cc(210)] Failed to locate a binder for interface: chrome::mojom::ResourceUsageReporter requested by: exposed by: via InterfaceProviderSpec "service_manager:connector". -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168467] Re: phy0 - rt2800pci_mcu_status: Error AND [drm:gen6_sanitize_pm] *ERROR*
@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 in Ubuntu. https://bugs.launchpad.net/bugs/1168467 Title: phy0 - rt2800pci_mcu_status: Error AND [drm:gen6_sanitize_pm] *ERROR* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/1168467/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1168467] Re: phy0 - rt2800pci_mcu_status: Error AND [drm:gen6_sanitize_pm] *ERROR*
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 Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation Panther Point USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation Panther Point MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation Panther Point High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 1 (rev c4) 00:1c.5 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 6 (rev c4) 00:1c.6 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 7 (rev c4) 00:1c.7 PCI bridge: Intel Corporation Panther Point PCI Express Root Port 8 (rev c4) 00:1d.0 USB controller: Intel Corporation Panther Point USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Panther Point LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation Panther Point 6 port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation Panther Point SMBus Controller (rev 04) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 09) 04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller 05:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-nettool in Ubuntu. https://bugs.launchpad.net/bugs/1168467 Title: phy0 - rt2800pci_mcu_status: Error AND [drm:gen6_sanitize_pm] *ERROR* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/1168467/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
