Shutdown issue - Keyring-Daemon still running

[AZgl1800]

Kernel: 4.10.0-38-generic x86_64 (64 bit)
Desktop: Cinnamon 3.6.6 Distro: Linux Mint 18.3 Sylvia


This became an issue a few days ago, but didn't have time to investigate.

When I want to run Chromium I am asked to supply a password.

Have no idea if that is related to the Keyring-Daemon or not, but when I select 'Shutdown' the Keyring is still running and I am asked if I want to "Shutdown anyway"


.

[Cosmo.]

Read here. The problem exists since 18.2 and increased in 18.3. The devs say, that they cannot reproduce it.

[AZgl1800]

Read here. The problem exists since 18.2 and increased in 18.3. The devs say, that they cannot reproduce it.

Well, 2 things happened on the way to the forum.

1) the shutdown issue is gone, and the laptop is now powering off in about 10 seconds versus a minute or so.

2) I had 2 older kernels that I was reserving for testing purposes "Just in Case" they might be needed.

without giving it too much thought, I followed thru on the 2nd command and Poof!
no more kernels to worry about

[Solved]

thanks guys

[AZgl1800]

Kernel: 4.13.0-26-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.6.6 (Gtk 3.18.9-1ubuntu3.3)
Distro: Linux Mint 18.3 Sylvia

_______________________________________

It was gone for a while, now it has come back again.

Is there any permanent solution to getting rid of that Keyring Daemon at shutdown?

it is very aggravating.

[AZgl1800]

I remembered reading somewhere, someone said they could Log Out, and then Log back in.
Problem Solved at least temporarily.

I just now tried that, logged out, back in, shutdown, and no daemon.

[Cosmo.]

The only thing, which can be said reliably is, that this behaves very unreliable. The problem does sometimes go and later it reappears. It seems, that there is a race condition problem, triggered since Cinnamon 3.4 by whatever.

Most likely this is at now the only working workaround.

[frankt]

I also have this issue.

I created a bash shell file, named 'down' (without the quote marks), in my ~/bin directory with the following:

Code: Select all

#!bin/bash

gnome-keyring-daemon -r -d

shutdown -P now

Also issue the following in a terminal window in the bin directory:

Code: Select all

chmod 777 down

If you want to limit execution permission, change the 777 to 770, or 774.

This shell file will cause a power-off immediately on your machine when you command

Code: Select all

 
. down

in a terminal window.

Your bin directory should also be in your $PATH. You can check with:

Code: Select all

echo $PATH

The first entry should be /home/$USER/bin: .

[AZgl1800]

I also have this issue.

I created a bash shell file, named 'down' (without the quote marks), in my ~/bin directory with the following:

Code: Select all

#!bin/bash

gnome-keyring-daemon -r -d

shutdown -P now

Also issue the following in a terminal window in the bin directory:

Code: Select all

chmod 777 down

If you want to limit execution permission, change the 777 to 770, or 774.

This shell file will cause a power-off immediately on your machine when you command

Code: Select all

 
. down

in a terminal window.

Your bin directory should also be in your $PATH. You can check with:

Code: Select all

echo $PATH

The first entry should be /home/$USER/bin: .

I tried that and got an error when I issued the $ down command

Code: Select all

sudo chmod 777 down

john@john-TP500LA /bin $ down
bash: /bin/down: bin/bash: bad interpreter: No such file or directory
john@john-TP500LA /bin $ down
bash: /bin/down: bin/bash: bad interpreter: No such file or directory

john@john-TP500LA /bin $ echo $PATH
/home/john/bin:/home/john/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
john@john-TP500LA /bin $ 

.

[CastleMan]

Re: Keyring-Daemon still running
Apologies if I've entered this in the wrong place!
I’ve no solutions, just observations and questions!
Like several other Mint users, I have the ‘Keyring-Daemon still running’ problem when trying to shut down. I have Mint 18.3 Cinnamon, Kernel 4.13.0 running on two older machines, different hardware, ‘Keyring’ problem occurs on both. I am the ONLY user on both machines.
a) Several suggestions in the Mint Forum that the problem occurs only with systems using ‘Automatic Login’ . Has anyone encountered the problem on a system that does require password entry to login ?
b) How can an ‘Automatic Login’ Mint 18.3 system be changed to require the password to be entered on login? I have the impression that if I logout of the system immediately after logging in, before doing anything else, and then login again (which requires password entry), I don’t seem to encounter the problem, but I’m not totally sure about this.
c) It would appear that the problem happens ONLY on Mint Cinnamon machines. Is this true?
d) While I have the utmost respect for the software developers, I have to believe that there’s a bug in the Cinnamon software, or at the very least it is not ‘bullet-proof’.
e) I’m not running anything exotic on either of my machines. I use only Firefox and Thunderbird; no other browsers or email programmes installed. (I’m still doing my routine work on a – apologies! - Windows 10 machine until I have more confidence in the Linux installations.)
f) When the ‘ Keyring-Daemon still running’ message occurs when I’m shutting down, I tell the system to logout anyhow and have not encountered any problems, other than a delay of about 30 seconds or so.

Sorry about rambling, but I’ve often found that by asking ‘dumb questions’ I often get intelligent answers.

[AZgl1800]

this thread shows how to turn OFF auto login
viewtopic.php?t=252967

you have to edit a file.
should have been a menu item....


Here is a pix of before and after, note in the pix that I used a # sign, then noticing they showed a " * " symbol, I changed the file to use the * symbol instead.

then I shut down, powered back up, and it asked me for my password... since I use a Single Character password, it is not problem for me at all.....


.

Auto Login ON.png

.

Auto Login OFF.png

[Cosmo.]

@CastleMan:

b) you can chenge this with the settings for the login screen - reachable via the menu. Details depend, if this is a fresh install of Mint 18.3 or if it has been upgraded from an older version of Mint, which in this case?

c) As far as we can see here: yes. Since Mint 18.2, increasing in 18.3.

[frankt]

To AZgl1500:

To execute the bash script you use a period and a space before the name:

Code: Select all

. down

Just typing in the name does not execute the file. That's why you got those error messages.

[AZgl1800]

To AZgl1500:

To execute the bash script you use a period and a space before the name:

Code: Select all

. down

Just typing in the name does not execute the file. That's why you got those error messages.

Thank you, was not aware of that.... still a newbie

[cogsncogs]

Re: Keyring-Daemon still running
Apologies if I've entered this in the wrong place!
I’ve no solutions, just observations and questions!
Like several other Mint users, I have the ‘Keyring-Daemon still running’ problem when trying to shut down. I have Mint 18.3 Cinnamon, Kernel 4.13.0 running on two older machines, different hardware, ‘Keyring’ problem occurs on both. I am the ONLY user on both machines.
a) Several suggestions in the Mint Forum that the problem occurs only with systems using ‘Automatic Login’ . Has anyone encountered the problem on a system that does require password entry to login ?
/snip

Me, on LM 18.3 Cinnamon. Only user, no automatic login.

[AZgl1800]

To AZgl1500:

To execute the bash script you use a period and a space before the name:

Code: Select all

. down

Just typing in the name does not execute the file. That's why you got those error messages.

Just got back to the thread, exited all applications to be sure nothing gets lost.
issued the 'Down' command in Terminal and wow!
Instant black screen, and power off.

Now a question. As this will allow me to get out of a locked computer easier, does it have the same negative ramifications as just turning off the power thru the BIOS hold down power button?

I have scrambled this laptop a couple of times, and had to reinstall the OS to clean it up because I used the Power Off button in the early days of my Linux experience.

Lately the REISUB and REISUO have been working, but I remember a time or two that those did not work, so if I can access Terminal is this safer?

[Boca]

Re: Keyring-Daemon still running

Like several other Mint users, I have the ‘Keyring-Daemon still running’ problem when trying to shut down. I have Mint 18.3 Cinnamon, Kernel 4.13.0 running on two older machines, different hardware, ‘Keyring’ problem occurs on both. I am the ONLY user on both machines.
a) Several suggestions in the Mint Forum that the problem occurs only with systems using ‘Automatic Login’ . Has anyone encountered the problem on a system that does require password entry to login ?
....
c) It would appear that the problem happens ONLY on Mint Cinnamon machines. Is this true?

Hi,
I have 2 machine running 18.3 ; neither have auto-login and there is only a single user.
The problem only occurs on the Cinnamon machine.

In addition to the respective inxi -Fxz shown below, if there is specific info required from one/both machines to assist on this issue.... please let me know.

Tony

Code: Select all

tony@tony-Latitude-E6430 ~ $ inxi -Fxz
System:    Host: tony-Latitude-E6430 Kernel: 4.4.0-116-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: MATE 1.18.0 (Gtk 3.18.9-1ubuntu3.3) Distro: Linux Mint 18.3 Sylvia
Machine:   System: Dell (portable) product: Latitude E6430 v: 01
           Mobo: Dell model: 0CPWYR v: A00 Bios: Dell v: A07 date: 10/08/2012
CPU:       Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9966
           clock speeds: max: 3100 MHz 1: 2946 MHz 2: 2900 MHz 3: 2899 MHz 4: 2196 MHz
Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1366x768@60.01hz, 1024x768@60.00hz
           GLX Renderer: Mesa DRI Intel Ivybridge Mobile GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes
Audio:     Card Intel 7 Series/C210 Series Family High Definition Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.4.0-116-generic
Network:   Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e v: 3.2.6-k port: f080 bus-ID: 00:19.0
           IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
           Card-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi bus-ID: 02:00.0
           IF: wlp2s0 state: down mac: <filter>
Drives:    HDD Total Size: 1320.2GB (78.6% used) ID-1: /dev/sda model: TOSHIBA_MK3261GS size: 320.1GB
           ID-2: USB /dev/sdb model: My_Passport_07A8 size: 1000.2GB
Partition: ID-1: / size: 282G used: 252G (95%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 12.75GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 61.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 195 Uptime: 7 min Memory: 2758.5/11889.2MB Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35 

Code: Select all

tony@tony-ThinkPad-SL510 ~ $ inxi -Fxz
System:    Host: tony-ThinkPad-SL510 Kernel: 4.4.0-116-generic x86_64 (64 bit gcc: 5.4.0)
           Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3)
           Distro: Linux Mint 18.3 Sylvia
Machine:   System: LENOVO product: 2847CQG v: ThinkPad SL510
           Mobo: LENOVO model: 2847CQG
           Bios: LENOVO v: 6JET83WW (1.41 ) date: 09/21/2010
CPU:       Dual core Intel Core2 Duo T6670 (-MCP-) cache: 2048 KB
           flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 8777
           clock speeds: max: 2201 MHz 1: 1600 MHz 2: 2201 MHz
Graphics:  Card: Intel Mobile 4 Series Integrated Graphics Controller
           bus-ID: 00:02.0
           Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1366x768@59.64hz
           GLX Renderer: Mesa DRI Mobile Intel GM45 Express
           GLX Version: 2.1 Mesa 11.2.0 Direct Rendering: Yes
Audio:      Card Intel 82801I (ICH9 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture v: k4.4.0-116-generic
Network:   Card-1: Realtek RTL8191SEvB Wireless LAN Controller
           driver: rtl8192se port: 2000 bus-ID: 05:00.0
           IF: wlp5s0 state: down mac: <filter>
           Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 4000 bus-ID: 08:00.0
           IF: enp8s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 2250.4GB (67.4% used)
           ID-1: /dev/sda model: HITACHI_HTS54502 size: 250.1GB
           ID-2: USB /dev/sdb model: Elements_25A2 size: 2000.4GB
Partition: ID-1: / size: 228G used: 28G (13%) fs: ext4 dev: /dev/sda1
           ID-2: swap-1 size: 2.00GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 48.0C mobo: 0.0C
           Fan Speeds (in rpm): cpu: N/A fan-1: 653
Info:      Processes: 203 Uptime: 2 min Memory: 616.4/1867.4MB
           Init: systemd runlevel: 5 Gcc sys: 5.4.0
           Client: Shell (bash 4.3.481) inxi: 2.2.35

[Boca]

Re: Keyring-Daemon still running

c) It would appear that the problem happens ONLY on Mint Cinnamon machines. Is this true?

Hi,
I have 2 machine running 18.3 ; neither have auto-login and there is only a single user.
The problem only occurs on the Cinnamon machine.
.....
Tony

I have just "up"-graded the CInnamon machine to Mate and it now shuts down without the keyring issue.

Rgds, Tony

[Cosmo.]

Yes, this is a workaround - but it does not throw a good light at the latest versions of Cinnamon, the so called flagship of Mint. I do understand, that such regressions happen. I do not understand, that this bug, which has been often enough reported here, cannot get reproduced and solved by 11 Cinnamon developers. (This number is given by Clem in the January blog.) What do they use? Only a live system (there the problem does not appear to my knowledge)?

[AZgl1800]

Sometimes when I shutdown for the night, everything works perfect.

Other times, it hangs with that keyring daemon.... and when it does, and you click "shutdown anyway' it seems to take a weekend for the PC to finally power off.

I changed from AutoLogin to requiring a password, did not change a thing.
the keyring daemon still gets in the way, and I don't have a clue what is different from one time to the next.

One thing I can say though, that the script above these posts for the "Down command" works every time, it has never failed.

" . down " and poof! computer is off.


Oh, when I started this thread, my PC had the following:


Kernel: 4.10.0-38-generic Cinnamon 3.6.6 Distro: Linux Mint 18.3 Sylvia


a couple of days ago, I upgraded the kernel to 4.13.0-36-generic and that did not have any effect on the keyring daemon issue.

[lsemmens]

Just got back to the thread, exited all applications to be sure nothing gets lost.
issued the 'Down' command in Terminal and wow!
Instant black screen, and power off.

Now a question. As this will allow me to get out of a locked computer easier, does it have the same negative ramifications as just turning off the power thru the BIOS hold down power button?

I have scrambled this laptop a couple of times, and had to reinstall the OS to clean it up because I used the Power Off button in the early days of my Linux experience.

Lately the REISUB and REISUO have been working, but I remember a time or two that those did not work, so if I can access Terminal is this safer?

Interesting questions that seem to have been missed in the follow ups. I'd love it if all I had to do was hit the power button. (Anyone remember the old days of DOS? A power refresh solved all sorts of problems.