Gnome Keyring Daemon not responding
 

This problem has plagued me for some time, basically when I shutdown the computer I will get a message saying "A program is still running" Gnome Keyring Daemon Not Responding.
It only seems to happen every now & then but I have no idea why this happens.

I have searched the Internet for help, there are lots of people with the same problem but few answers. Some have said disabling auto login, rebooting & re enabling it may work, I tried this & thought it was the answer but some time time later it came back again.

I can get the computer to close by typing "shutdown now" in a terminal but I don't know if that may cause any other problems that I'm not aware of.

A permanent fix would be great if anyone has one.

Thanks

gnome-keyring daemon not responding
 

I'm also having this problem and have had it since my first install on Linux mint 17.3. Totals of 3 years. I have always selected shutdown anyway and have seen no problems. The question is why this has not been fixed and what is the cause. Unfortunately I am just a regular user who is using this system because my boss gave it to me and said use it. I use a single program all day long and then shutdown. We are a small 5 person business with no IT support. If any solutions become available I would be willing to try them.

I see quiet a lot of people have read the post but no one seems to have an answer which is surprising. I will continue to look for an answer & post here if I am lucky. I know there's plenty of others out there with the same problem.

ho develops gnome keyring?
 

It would be nice to get hold of the development team and find out if they are even aware of this issue. Considering this has been going on for at least three year I suspect that this issue is not being bug tracked properly leaving them totally in-aware of this issue. Someone who has enough background should hunt down this issue and see if it is on the bug track list and what its priority is.

I've seen more suggestions, one said if you have updated your kernel removing old kernels may help. I have no idea if this is correct but I did have a few old kernels after updating so I have removed the old ones, (I would not recommend this unless you are happy that the kernel you are using has no issues).
I've down a few shutdowns & reboots today & the issue has not shown itself, although as I said in my original post it didn't happen every time anyway so I will continue to monitor the situation & see what happens.
In the meantime it would be great if someone with superior Linux knowledge could give their views.

I am running the latest kernel. My machine is an old old old IBM T61 with 4GB ram and an 80Gb HD. My boss never met a refurbished computer he wasn't willing to give to his employees. I also found out that I am actually running Linux under Virtualbox on this machine. Its been carefully hidden behind a start-up screen but discovered it when I was poking around some places I am not supposed to go.

You can try to remove it

what is issuing the message?
is it on the console (white text on black background) or is it while the graphical env is still active?
what is the verbatim full message?

I've not seen the issue since I removed an old kernel & I can't remember exactly what the message box looked like, if it surfaces again I will post details. Thanks.
AwsomeMachine, I'm a little worried to remove Gnome keyring as I don't really understand what it is & if I need it, I'm always loathe to do something that might end up with something worse than I had to start with. I'm not suggesting that there is anything wrong with your suggestion, rather that I don't understand it.

Well, still no shutdown issues since I took the action of removing old kernels, was that the answer? I don't know but for now I'm marking this post as solved.
It seems to have worked for me, will it work for others? I can't say, it could be coincidence but in the absence of any other suggestions there's not much else I can do & I'm left wondering like pwingert are the developers aware of the issue & how come no one seems to have the definitive answer.

Removing gnome-keyring will only prevent you being asked for passwords in certain programs, like email.

Problem occurs 100% of the time on two Mint Cinnamon 64 bit machines after the latest round of updates (3/6/18) 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 all the recent 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 most recent batch of updates for Cinnamon that is causing this problem.

I am reporting this info at https://bugs.launchpad.net/ubuntu/+s...ng/+bug/608162. I suggest everyone else do the same, providing as much troubleshooting info as possible.

Just switched from Linux Lite to Mint Cinnamon 18.3 64 bit and have the same problem on shutdown. Message reads, "A program is still running... gnome-keyring-daemon not responding." The previous post on this issue before mine was dated 03-07-18. Has anyone discovered a solution in the past three months?

Thanks in advance for any/all replies!

look at post #10.

Thanks, ondoho.

I'm still a bit of a Linux lightweight... so do I need to remove ALL old kernels or must I determine which one is problematic?

i'm sure you can remove all but the currently working kernel.

After deleting the only other active kernel, shutdown worked perfect... no message about the gnome-keyring. Unfortunately, the message reappeared the next time I shut down the laptop (sigh).

I always leave two active kernels, that would be the latest one & the previous one, any others can go, this way if your current kernel has issues you can revert to the previous one which presumably worked without issues.
Removing kernels is easiest in the update manager "View" "Linux Kernels" "Right click" "Remove"

Hoping this makes sense...

My active kernel is 4.13.0-45. In the update manager > view > kernels, the left column shows 4.4, 4.8, 4.10, 4.11, 4.13 and 4.15. Clicking on any one of those series of kernels then displays the individual kernels in the right column. None of the other kernels with any series is active except 4.13.0.45. I can't delete the others (even if I right-click), the only choice is to install them.

I'll need to read up on kernels because I'm not sure why the most recent kernel (4.15.0-13) isn't the active one (or the one I should be using).

Thanks for your guidance/patience with this "newbie!"

post output of please.

4.13.0-45-generic #50~16.04.1-Ubuntu SMP Wed May 30 11:18:27 UTC 2018

do you want the newest kernel?
assuming yes:
have you installed it?
have you rebooted?

https://askubuntu.com/questions/2793...-the-boot-menu

Success! Thanks for all the help!

and now please give back to the community and tell us (or others who might stumble upon this thread in search of answers) how you did it.
thanks.

Turns out this was the second false fix. Originally, there were two kernels installed: 4.13.0-45 and an older one (can't remember which). First, I removed the older kernel and kept 4.13.0-45 active. Upon shutdown, I did not get a "gnome-keyring-daemon not responding" notification and thought the problem was solved. Next time I shut down the system, the notification returned.

On the next attempt to fix, I installed the most recent kernel, 4.15.0-13, and removed 4.13.0-45. When I rebooted, the "gnome-keyring-daemon not responding" notification did not appear. I was hopeful yet again, but the notification returned during the next shutdown.

This leaves me wondering if it is, in fact, a kernel issue.

i suspected that the purging of old kernels is just some voodoo snake oil.

so, back to post #1.
here's a few search results, please tell us if you find something useful:
https://www.startpage.com/do/dsearch...nding+shutdown

also look at post #11:
do you really need gnome-keyring?
i don't use any such software and my system works just fine.

I reviewed some of trouble-shooting suggestions in other forums from the link provided by ondoho in post # 26; nothing I read provided a resolution.

For good measure, I tried the kernel approach one more time by downloading and installing the most recent kernel update (4.15.0-23). As anticipated, that did not correct the problem.

What I DID do is remove "gnome-keyring 3.18.3-Oubuntu2" from the Synaptic Package Manager. I'm not sure how this will affect other aspects of the system, but after a handful of shutdowns and restarts, the message has not returned.

If anyone else attempts this solution, please reply with results. Thanks!

This issue just came up for me. I'm new to linux. Dabbled with it till took the plunge and wiped all my hard drive and went to linux Mint Cinnamon 18.3 All was going well with no flags till I installed and set up the Timeshift backup as the final step now all is set up as I like it. Now I get the notice on shutdown (so I didn't shut it down as wanted to read results). I consider myself to know enough computer stuff to do damage (learned much by trial and error) so try to proceed with clear steps. Could it be with the backup set up that is keeping the keyring open? I have all login stuff turned off except for where I make changes in my hard drive. I'm thankful ahead for any and all help!

welcome to LQ!

it could be all sorts of things, but switching OFF autologin might help.
apart from that, did you read this complete thread in all its gory glory?
if that doesn't help you, you might want to start a new, dedicated thread with a valid problem description.

Thank you! Yes, I did read the whole thread. The removing kernels seemed like something I'd really mess up but I did go and see how to do it. I don't have a list of old ones sitting there since I've just put all on here. My autologin was already switched off so I switched it back on then restarted (took two restarts before I did not see the open keyring - had read someone else got that too). Then went back and switched it off again and all is going great. I'm very appreciative for all the helps!

gnome-keyring probably does not use kernel built-in encryption nor cpu special security features

i glanced through the source code: they are pulling your d**ck

also i don't think it's a gnome problem. it's likely your linux distro admins that broke something. your next question is if it was a mistake. (it works for them, why not for you?)

---------------------------------------

gnome-keyring does not use kernel encryption nor cpu encryption and has no obvious ties to kernel. if it did: then gnome wouldn't run on freeBSD

it's possibly a "packaging problem that ubuntu created": but it's not kernel related.

i don't think it's secure though it's "useful and convenient", many like it

but really if it doesn't work. you should wonder if it's your job to fix everything broken that comes you way. how much is coming your way that is broken? if you cannot do simple things like passwords what else is broken? (not the kernel, the kernel at least is "stable" and not needy for fixing)

there are things you should fix but there are things that, if they are hacked and broken, you have to wonder if who broke it. it's your time.

From https://bugs.launchpad.net/linuxmint/+bug/1745573 post #14

I had this since updating to 18.3,(newbie)I went to software manager & installed monodoc gnome-keyring-manuel-after 2 restarts-problem solved!

I performed this on my 18.3 and the shutdown went normally. It prompts to modify a couple of libmono components and I said yes. So I think manual here mean not automated rather then an instruction manual as is implied in the documents for this package.

I just hate that a self-described newbie dropped this solution down without a pedigree as though it had been given to him by an angel engraved on golden plates. Anyone have any authoratative commentary on this solution?