GNOME Keyring Daemon stops panel's shutdown

[seanlano]

Binary package hint: gnome-keyring

Almost every time I click "Shut Down" from the panel's menu for it, I get an error that says: "GNOME-Keyring-Daemon is not responding." Then I can choose "Shut Down anyway" and the computer usually turns off after that, but sometimes I need to use a sudo shutdown command.
Also, sometimes when I select "Shut Down" from the panel, nothing happens at all. Again, I need to use a sudo shutdown command to turn off the computer.
This happens for all of the users on this computer (a Thinkpad laptop).
This issue is particularly annoying for non-administrator users, because if selecting "Shut Down" from the panel doesn't work they cannot issue a sudo shutdown command - which means I need to assist them in changing to a tty terminal, logging in as me, and then giving the sudo shutdown command.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-keyring 2.92.92.is.2.30.3-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Wed Jul 21 20:17:15 2010
ExecutablePath: /usr/bin/gnome-keyring-daemon
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcEnviron:
 LANG=en_AU.utf8
 SHELL=/bin/bash
SourcePackage: gnome-keyring

[Sebastien Bacher (seb128)]

Thank you for your bug report, not sure what create the issue but setting to low since you are the first to report a such issue, could you try if that happens with another user account on the same installation or if it's due to some configuration you use?

[seanlano (seanlano)]

Since Lucid Final release I have not encountered this problem, so it may be closed.

Thanks.

[AJ (aj-johnson11)]

I get got the same issue in Solaris 11.

[Juan (zheive)]

Same problem in Mint 18.2

[John Stephens (g1vvu)]

Same problem Mint 18.2

[Thomas Hartley (thomasarlohartley)]

Same problem running Cinnamon 3.4 desktop on Ubuntu 16.04. Different models show the error more than others. Travelmate B117 only happens on low battery. Otherwise pretty random. Not on every shutdown, but at least 70% of the time.

[Jim Oakley (jim1440)]

This same problem just popped up in the last few days after updating to Mint 18.2

[John Stephens (g1vvu)]

in Mint Cinnamon 18.2 i have noticed if i list running daemons e.g. ps -e | grep -e d$ -e daemon
there are 2 copies of the gnome-keyring-daemon active.
does anyone know if this should be so?
(I am running as a single user)

[ALinuxUser (buntulongername-new)]

I'll bump this, if I may. I too am affected - on Mint 18.3 Cinnamon.

[Jeff Jones (jeffjones)]

I've just started getting this on my laptop with a current version of Linux Mint Cinnamon with all the updates. Also if I close my laptop (so it sleeps) when I open it, sometimes the screen just goes blank and even REISUB or REISUO will not work. I've also had to run fschk to fix issues which I think are cause by forcing the shutdown while the screen is blank. Not sure if the blank screen is related to the gnome-keyring-daemon or not, but they both started at the same time. There have been a lot of updates recently with the Intel chip problem, so I have no idea which (if any) have caused the problem.

[Pete (brvcf)]

Problem occurs 100% of the time on two Mint Cinnamon 64 bit machines after the latest round of updates when shutting down or restarting from whisker menu. 'shutdown (-r) now' works without an error.

The most commonly reported 'fix' for this problem is purging old kernels. I just reinstalled 18.3 Cinnamon 64 from scratch on one and then installed all the updates. There were only 2 kernels. I removed 4.10 4.13.0-36 is the only one installed. It did not fix the problem. I did not have the problem before the last round of updates.

Also on another computer with 18.2 which has not been turned on for a while I never had the problem until I just installed updates. It is using 4.10.0-33 kernel. 4.8.0.53, 4.10.0-33, and 4.13.0-36 are installed.

I had no problem with on two 18.3 XFCE 64 bit machines. One I last used/updated Sunday 3/4 or another I just updated (including latest kernel) as of 3/8/18 0245Z.

All computers are set for autologin. I tried turning autologin off on one Cinnamon but that had no effect.

It appears there is something in the recent updates for Cinnamon that is causing this problem.

[Rick (rwba13572)]

Same issue in Mint 18.3 Cinnamon with all updates

[John Kerr (jack543)]

I have the same error, only when I click on the shutdown icon. A command line shutdown does not get this error. I am running Mint 18.3 on oracle virtualbox.

[gunarto (gn82)]

I Have same Problem on LinuxMint 18.3 Cinnamon lates update..please help me to fix it..thanx U

[gunarto (gn82)]

I Have same Problem on LinuxMint 18.3 Cinnamon x64 lates update..please help me to fix it..thanx U

[ewan (ewanlawrie)]

Same problem LinuxMint 18.3 Cinnamonx64 latest update

SYS info

-Computer-
Processor : 2x Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz
Memory : 3936MB (1329MB used)
Operating System : Linux Mint 18.3 Sylvia
User Name : ewan (Ewan)
Date/Time : Mon 26 Mar 2018 12:57:43 CEST
-Display-
Resolution : 1280x1024 pixels
OpenGL Renderer : Mesa DRI Intel(R) G41
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA Intel
Audio Adapter : USB-Audio - USB Device 0x46d
-Input Devices-
 Power Button
 Power Button
 Logitech USB Receiver
 Logitech USB Receiver
 Dell Dell USB Keyboard
 HDA Intel Rear Mic
 HDA Intel Front Mic
 HDA Intel Line Out
 HDA Intel Front Headphone
 Dell WMI hotkeys
 gspca_zc3xx
-Printers (CUPS)-
MP230-series : <i>Default</i>
-SCSI Disks-
ATA WDC WD2500AAJS-7
TSSTcorp DVD+-RW TS-L633J
SanDisk Ultra USB 3.0

[Simon Quigley (tsimonq2)]

This problem was long-solved in Ubuntu and we don't support Mint. Please ask them why their packages are outdated (years old at this point) and still contain this bug.

[Richard Moore (richard-darton-moore)]

I have this problem too. It is very irritating, as I frequently return to find that my laptop has run out of battery overnight because shutdown doesn't complete. It's been such a long standing issue. I'm also running Mint 18.3