Unexpected shutdown

3 réponses [Dernière contribution]
Avron
Hors ligne
A rejoint: 08/18/2020

As I was working with another computer, not doing anything actively besides sharing mouse and keyboard using barrier, my desktop unexpectedly initiated shutdown.

In syslog, these are the very first messages of the time:

Jun  7 20:10:42 albert mate-session[22164]: WARNING: Unable to find desktop file 'keepassxc.desktop': Impossible de trouver un fichier de clés valide dans les répertoires de recherche
Jun  7 20:10:42 albert mate-session[22164]: WARNING: Unable to find desktop file 'mate-keepassxc.desktop': Impossible de trouver un fichier de clés valide dans les répertoires de recherche
Jun  7 20:10:43 albert systemd[1]: Stopped Unattended Upgrades Shutdown.
Jun  7 20:10:43 albert systemd[1]: Stopped QEMU KVM preparation - module, ksm, hugepages.
Jun  7 20:10:43 albert systemd[1]: session-c2.scope: Killing process 2036 (pulseaudio) with signal SIGTERM.
Jun  7 20:10:43 albert systemd[1]: session-c2.scope: Killing process 2054 (deja-dup-monito) with signal SIGTERM.

Then I have a lot of messages for the ongoing shutdown.

In auth.log, I see

Jun  7 20:10:42 albert polkitd(authority=local): Unregistered Authentication Agent for unix-session:c4 (system bus name :1.3119, object path /org/mate/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus)
Jun  7 20:10:43 albert lightdm: pam_unix(lightdm:session): session closed for user david
Jun  7 20:10:43 albert systemd-logind[893]: System is powering down.

I did not press the power button ad did not ask to log out.

From syslog, it looks a bit like mate-session could be responsible for the shutdown. The message in French says something like "Unable to find a valid key file in in search directories", the "key file" might refer to the gnome keyring rather than keepassxc, but I don't know.

I welcome any clue.

Besides, my desktop was fully stable for several weeks, until yesterday, since then I lost control of the mate session at least three times, I managed to close it via ssh either by restarting lightdm or using mate-session-save.

Cyberhawk

I am a translator!

Hors ligne
A rejoint: 07/27/2010

It does say something about unattended upgrades in your log. Did you initiate a software update in the background?

Avron
Hors ligne
A rejoint: 08/18/2020

> It does say something about unattended upgrades in your log. Did you initiate a software update in the background?

Indeed, I wondered about this message but I did not initiate anything, at least not on purpose and not at that moment. I suspect the message might be related to preventing unattending upgrades from running due to the initiation of shutdown, but I am not sure. Besides, I thought these unattended upgrades were a cron job and I see logs elsewhere indicated they are run by cron.

Cyberhawk

I am a translator!

Hors ligne
A rejoint: 07/27/2010

If I read the message correctly, it means, it is preventing shutdown caused by unattended updates. So maybe it's trying to prevent a shutdown but it still somehow happens?

Not sure what is causing this sudden shutdown, never had anything like that happen on my systems... Is there some way of configuring these upgrades from the system settings in main menu?