shutdown: gnome-keyring-daemon still running

[AZgl1800]

if gdm file not exist, then find the /lightdm or /mdm file (it is either or)
take a look here -> http://i.prntscr.com/BnJZfck1QNiMq_hzjp1rxA.png

/lightdm file was there and I applied the change suggested.

I will save the last hint in my notes IF the keyring pops up again.
so far, doing well, if I never see it again, I will be happy.

[Mike_Ham]

This just started happening yesterday after the system had been OK for 3 days after installation. What I want to know is what the definitive solution to this issue is - after reading through the thread I can't really understand which is the correct solution, especially after people say this or that didn't work. I don't want to muck up the system.

I haven't done much of anything complex with the OS other than become familiar with it and install the updates and a package called BOINC for distributed computing so I can run Seti@home. Is it a developer issue that will be corrected in a coming release? What exactly is gnome-keyring-daemon and why would it be in this state?

But again - what is the definitive solution at this time?

Thanks.

[Cosmo.]

A definitive solution can only get provided by the developers. Until this happens (for Mint 18.x most likely never) we can offer only a workaround.

[Mike_Ham]

A definitive solution can only get provided by the developers. Until this happens (for Mint 18.x most likely never) we can offer only a workaround.

OK.

I've been trying other Linux distros for the past few days and I still like this one best. I reinstalled it this evening and if the issue crops up again I guess I'll just deal with it.

Thanks.

[Sinnis250]

I don't know if this is the definitive solution but, this worked for me running Mint 18.3 Cinnamon 64bit.

The message came up after installing a 4.13 kernel, so I installed 4.4.0116 (same thing happened again) but a further update of 4.4.0-122 came up in the manager.

I simply updated the kernel from 4.4.0-116 to a fresh kernel 4.4.0-122 and removed the 4.13 kernel completely.

So far, after several shutdowns and reboots, there has been no re-occurrence of the nag "gnome-keyring-daemon still running".

Seems good to go now.

[AZgl1800]

I don't know if this is the definitive solution but, this worked for me running Mint 18.3 Cinnamon 64bit.

The message came up after installing a 4.13 kernel, so I installed 4.4.0116 (same thing happened again) but a further update of 4.4.0-122 came up in the manager.

I simply updated the kernel from 4.4.0-116 to a fresh kernel 4.4.0-122 and removed the 4.13 kernel completely.

So far, after several shutdowns and reboots, there has been no re-occurrence of the nag "gnome-keyring-daemon still running".

Seems good to go now.

I have a question concerning this very post:

Recently the 4.4.x kernel came up as a suggested upgrade to my 4.13.0.39 system.
The idea of jumping "ship" to a different kernel series kind of shocked me, so I rejected it.

Is this a "suggested" upgrade that I should consider?
I thought the 4.13 series of kernels were LTS

As a "General Practice" I have been rejecting all upgrades for Developers.

[Cosmo.]

I thought the 4.13 series of kernels were LTS

No. In August support will end and you have to switch to another kernel.

Besides that: What you show is not a kernel, but a kind of library. You will not find any 4.4 kernel after this update. (IIRC you use TimeShift, so you can do it without risk).

[AZgl1800]

I thought the 4.13 series of kernels were LTS

No. In August support will end and you have to switch to another kernel.

Besides that: What you show is not a kernel, but a kind of library. You will not find any 4.4 kernel after this update. (IIRC you use TimeShift, so you can do it without risk).

I will just stay with my Daily Driver, don't want to mess it up.
TimeShift is a mainstay for me, for every change that is made.

[Cosmo.]

Nothing gets messed up. I have this update already since a week. Note, that the update includes security fixes.

[jakebob]

I reviewed some of trouble-shooting suggestions in this and other forums but nothing I read/tried provided a resolution.

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 during shutdown, "a program is still running... gnome-keyring-daemon not responding," has not returned.

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

[Flemur]

I uninstalled gnome-keyring(-daemon) ages ago. No apparent change in anything, though you might actually be using for something.

[venommin]

this is because of your chrome browser ,nothing to do just uninstall chrome once and force shutdown after that tern it on and try to restart and this time it will not ask for that , and if you want to install chrome again then you have to clean browser data and history .

[AZgl1800]

I uninstalled gnome-keyring(-daemon) ages ago. No apparent change in anything, though you might actually be using for something.

thanks for that little tidbit, that damn thing irritates me to no end............
it is long gone now, I had to install Chrome browser yesterday, just so I could talk a forum user thru how to get rid of his old passwords............
and that crappy POS daemon came up and asked me for my root password

[Flemur]

thanks for that little tidbit, that damn thing irritates me to no end............

Here's a better gnome keyring:
https://www.etsy.com/listing/263797277/ ... -gardening

[FenderGuy]

Yep. Me, too. Running Mint 18.3.

[tyebillion]

I'm getting this almost all of the time when shutting down Linux Mint 18.3. Note I've got a NVIDIA card and I'm using the proprietary driver.