Shutdown problems - Failed to wait for process: Protocol error

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
ZFR
Level 2
Level 2
Posts: 77
Joined: Sat Jan 11, 2020 8:23 am

Shutdown problems - Failed to wait for process: Protocol error

Post by ZFR »

Recently, when I shutdown I get the following error repeated 5 or 6 times.

[XXX.XXXXXX] shutdown[1]: Failed to wait for process: Protocol error

X are numbers that change every time.

I haven't installed anything new recently, but I did all the updates the Update Manager shows.

Here is my inxi output

Code: Select all

System:
  Host: D Kernel: 5.3.0-28-generic x86_64 bits: 64 compiler: gcc 
  v: 7.4.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 
  Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic 
Machine:
  Type: Desktop Mobo: Gigabyte model: Z97X-Gaming GT v: x.x serial: <filter> 
  BIOS: American Megatrends v: F7 date: 09/19/2015 
CPU:
  Topology: Quad Core model: Intel Core i7-4790K bits: 64 type: MT MCP 
  arch: Haswell rev: 3 L2 cache: 8192 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 64002 
  Speed: 4000 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 4000 2: 4000 
  3: 4000 4: 4000 5: 4000 6: 4000 7: 4000 8: 4000 
Graphics:
  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: Gigabyte driver: nvidia 
  v: 435.21 bus ID: 04:00.0 chip ID: 10de:13c2 
  Display: x11 server: X.Org 1.20.5 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1200~60Hz 
  OpenGL: renderer: GeForce GTX 970/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 
  direct render: Yes 
Audio:
  Device-1: Intel 9 Series Family HD Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8ca0 
  Device-2: NVIDIA GM204 High Definition Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip ID: 10de:0fbb 
  Sound Server: ALSA v: k5.3.0-28-generic 
Network:
  Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet vendor: Gigabyte 
  driver: alx v: kernel port: d000 bus ID: 06:00.0 chip ID: 1969:e091 
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 2.29 TiB used: 969.52 GiB (41.4%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 850 PRO 512GB size: 476.94 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 1B6Q scheme: MBR 
  ID-2: /dev/sdb vendor: Seagate model: ST2000NM0053-1C1175 size: 1.82 TiB 
  speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: SS04 scheme: MBR 
Partition:
  ID-1: / size: 42.77 GiB used: 15.96 GiB (37.3%) fs: ext4 dev: /dev/sda2 
  ID-2: /home size: 124.46 GiB used: 13.13 GiB (10.5%) fs: ext4 
  dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 74.0 C mobo: N/A gpu: nvidia temp: 36 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 49% 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/home:stevenpusser.list 
  1: deb http://download.opensuse.org/repositories/home:/stevenpusser/xUbuntu_18.04/ /
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com tricia main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ bionic partner
Info:
  Processes: 260 Uptime: N/A Memory: 31.22 GiB used: 1.59 GiB (5.1%) 
  Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.4.0 alt: 7 Shell: bash 
  v: 4.4.20 running in: gnome-terminal inxi: 3.0.32 
Centauri39
Level 4
Level 4
Posts: 296
Joined: Sun Mar 23, 2014 2:20 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by Centauri39 »

Same here!

Another kernel doesn't help, neither does:

Code: Select all

sudo apt update && sudo apt dist-upgrade
Does anybody know a solution, please?

EDIT:
According to another forum, we all just have to wait for a patch to be released.
User avatar
LanceM
Level 10
Level 10
Posts: 3271
Joined: Sun Jul 08, 2018 11:50 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by LanceM »

What does this do?

Code: Select all

sudo shutdown -P now
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php
Centauri39
Level 4
Level 4
Posts: 296
Joined: Sun Mar 23, 2014 2:20 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by Centauri39 »

I tried that command without the -P switch and I got the same wrong behaviour.
User avatar
Jeronimo17
Level 2
Level 2
Posts: 82
Joined: Fri Jun 08, 2018 6:48 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by Jeronimo17 »

It's happening to me too recently, I think.
The shutdown does not take anything but the message appears several times last

Code: Select all

Kernel: 4.15.0-76-generic x86_64 bits: 64 
Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia
ZFR
Level 2
Level 2
Posts: 77
Joined: Sat Jan 11, 2020 8:23 am

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by ZFR »

OK, so it's not just me... guess we just wait for a patch.
User avatar
karlchen
Level 21
Level 21
Posts: 13499
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by karlchen »

Hi, folks.

You are aware that you can investigate in more detail, what precisely disturbed the last shutdown, by executing the following commandline, after you have started up the system again:
journalctl -b -1 (the options are "minus b" "minus 1" (minus one))
The shutdown steps and disturbencies will be near the end of the previous OS session journal.
(journalctl gives many more details than the file /var/log/syslog)

Would be interesting to know what precisely is not working as it should during shutdown.

Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 9.51 64-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)
Centauri39
Level 4
Level 4
Posts: 296
Joined: Sun Mar 23, 2014 2:20 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by Centauri39 »

Meanwhile, I restored a snapshot of Timeshift to get rid of this issue and so,
I found out that it began after updating the following packages:

Code: Select all

webkit2gtk from 2.26.2-0ubuntu0.18.04.1 to 2.26.3-0ubuntu0.18.04.1
casper from 1.394.2 to 1.394.3
ubuntu-meta from 1.417.3 to 1.417.4
ubuntu-release-upgrader from 1:18.04.36 to 1:18.04.37
I will now install them one-by-one and after each one I will check the shutdown behaviour.

I will report my results afterwards.
Please wait...

EDIT:
Ok, so, after installing the casper update, the issue appeared again.
Unfortunately, I don't know what's causing it, because casper required
the installation of another package called finalrd,
but obviously one of these must be responsible for the issue.
User avatar
Kadaitcha Man
Level 11
Level 11
Posts: 3597
Joined: Mon Aug 27, 2012 10:17 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by Kadaitcha Man »

Centauri39 wrote:
Fri Jan 31, 2020 7:41 am
the installation of another package called finalrd,
but obviously one of these must be responsible for the issue.
Possibly that one.

http://manpages.ubuntu.com/manpages/cos ... lrd.1.html

You may have to raise a bug report on it with ubuntu.
Coming to a thread near you: Lots of bragging about my AMD 5950X. Currently delayed due to high demand.
It's pronounced kad-eye-cha, not kada-itcha.
Centauri39
Level 4
Level 4
Posts: 296
Joined: Sun Mar 23, 2014 2:20 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by Centauri39 »

I just looked up that package within synaptic and there is no older version available there where I could go back to.
and since the installed version is from Thu, 23 May 2019, I wonder, do I need that package anyway,
because it looks like prior to the last updates it wasn't present on my system anyway.

On the other hand, I don't dare to uninstall that package (as a test), because I've got no idea, what will happen afterwards.
User avatar
LanceM
Level 10
Level 10
Posts: 3271
Joined: Sun Jul 08, 2018 11:50 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by LanceM »

Centauri39 wrote:
Fri Jan 31, 2020 8:37 am
I just looked up that package within synaptic and there is no older version available there where I could go back to.
and since the installed version is from Thu, 23 May 2019, I wonder, do I need that package anyway,
because it looks like prior to the last updates it wasn't present on my system anyway.

On the other hand, I don't dare to uninstall that package (as a test), because I've got no idea, what will happen afterwards.
Can't you just rollback and then backlist the Casper update?
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php
GeeGee47
Level 1
Level 1
Posts: 5
Joined: Sat Dec 01, 2018 10:40 am

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by GeeGee47 »

Also had exactly the same issues but on 19.2.

Can confirm that rolling back the kernel, on it's own, does not make a difference, for me anyway.

However if you have Timeshift in use then roll back to before the Casper update (thanks to poster for the heads-up) and that worked for me.

As this appears to be an update "Bug/Issue" would also agree with the suggestion that this is posted as something to be sorted.

Regards to all.
GeeGee
User avatar
Jeronimo17
Level 2
Level 2
Posts: 82
Joined: Fri Jun 08, 2018 6:48 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by Jeronimo17 »

Centauri39 wrote:
Fri Jan 31, 2020 7:41 am
Meanwhile, I restored a snapshot of Timeshift to get rid of this issue and so,
I found out that it began after updating the following packages:

Code: Select all

webkit2gtk from 2.26.2-0ubuntu0.18.04.1 to 2.26.3-0ubuntu0.18.04.1
casper from 1.394.2 to 1.394.3
ubuntu-meta from 1.417.3 to 1.417.4
ubuntu-release-upgrader from 1:18.04.36 to 1:18.04.37
I confirm that these updates on another PC have given the same problem
GeeGee47
Level 1
Level 1
Posts: 5
Joined: Sat Dec 01, 2018 10:40 am

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by GeeGee47 »

Was half expecting to see a load of me-too posts, as indeed I began.
But, no, is it really only affecting us few?
Or is there a broader issue that I'm missing?

Anyone any thoughts?
GeeGee
User avatar
karlchen
Level 21
Level 21
Posts: 13499
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by karlchen »

Well, so far no-one, who experiences this specific shutdown problem, has bothered to look up in the journalctl output what systemd tells who is the one to cause shutdown trouble:
karlchen wrote:
Fri Jan 31, 2020 7:24 am
You are aware that you can investigate in more detail, what precisely disturbed the last shutdown, by executing the following commandline, after you have started up the system again:
journalctl -b -1 (the options are "minus b" "minus 1" (minus one))
The shutdown steps and disturbencies will be near the end of the previous OS session journal.
(journalctl gives many more details than the file /var/log/syslog)
Note:
The most relevant lines from the journalctl -b -1 output will be the last 250 to 300 lines very likely, because they document the shutdown steps.
This would be a way of catching the last 300 lines e.g.:

Code: Select all

journalctl -b -1 --no-pager | tail -300 > $HOME/journalctl.$USER.txt
(catch the last 300 lines from journalctl and write it in your $HOME directory to a file named journalctl.$USER.txt, where $USER will be your loginname.)
Making this file available here for inspection might really help identify the source of trouble.

Up to those, who experience the problem, to help analyze or not to do so.
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 9.51 64-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)
GeeGee47
Level 1
Level 1
Posts: 5
Joined: Sat Dec 01, 2018 10:40 am

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by GeeGee47 »

Hi Karlchen

Thanks for your response.
Having seen the output of the file that you are asking for, as an ignorant newbie of both Linux and indeed the use of forums - I am uncomfortable in publishing such in the wild, so to speak. Containing as it does IP addresses and names, etc, etc.

At this time I can only repeat that, for me, reverting the kernel made no discernible difference.
But "Timeshifting" back and then blocking the "Casper" update, which does indeed also require a supplementary download of "finalrd" to be installed as well seems to cure the issue.

I realise that this may well be tying your hands behind your back, so I apologise for wasting your time.
Kind Regards
GeeGee
User avatar
karlchen
Level 21
Level 21
Posts: 13499
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by karlchen »

Hi, GeeGee.

No need to apologize for wasting my time. Absolutely not.
First of all my posts had not been addressed to you specifically, but to all, who experience the reported problem.
Second, I am totally free to spend time on this thread or not. So I cannot blame anybody else for doing so.

Third, everyone, who experiences the problem, is free to post the suggested journalctl ouput or not to do so.
Some users may be able to interpret the output themselves and will therefore not post it here.
Some users may need help by other forum users in interpreting the journalctl output, which they can get only in case they post it here.
I do understand that some users will not post the journalctl output, because it will hold their Linux Mint login name e.g. and maybe some other details, which they consider private.
This is perfectly all right.
By posting logfiles you will frequently reveal details, which you would normally not post.
On the one hand.
On the other hand, without inspecting journalctl output it will be much more difficult, if possible at all, to identify what causes the shutdown problems.
Yet, everyone has to decide form himself, what in this situation is more important, getting to the bottom of it and solve the problem or keeping the journalctl log details private.

In case the reported problem had occurred on my Mint 19.3 systems, I would have the journalctl output. But so far the problem has not occurred here.

Anyway, I will not blame anybody for not posting the suggested output.

Best regards,
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 9.51 64-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)
User avatar
karlchen
Level 21
Level 21
Posts: 13499
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by karlchen »

OK. folks.
I ran my own commandline

Code: Select all

journalctl -b -1 --no-pager | tail -300 > $HOME/journalctl.$USER.txt
Before uploading the content of the resulting text file journalctl.karl.txt into the forum, the following cleanup operations have been applied to the file:
  • lines 1 to 50 have been removed, because they had been logged before the system got the command to reboot
  • in 4 lines IP nad Mac addresses have been detected and replaced by "<filtered>"
If someone should come across other sensitive pieces of information, which have slipped my attention, bad luck for me.

Note:
The LM 19.3 xfce system, where the journalctl output has been collected, does not exhibit any problems, when shutting down.
Hence my journalctl output is unlikely to help identify the root cause of the shutdown problems reported by others.
My journalctl output only serves to give an idea what kind of output to expect and which sensitive data might be found in journalctl output.

Code: Select all

[... lines 1 to 50 removed because they were not about the reboot (see below), yet. ...]
Feb 01 20:14:15 unimatrix3 systemd-logind[809]: System is rebooting.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Authorization Manager...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping User Manager for UID 1000...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Save/Restore Sound Card State...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped target Default.
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping Virtual filesystem service - disk device monitor...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping Accessibility services bus...
Feb 01 20:14:15 unimatrix3 rsyslogd[829]:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="829" x-info="http://www.rsyslog.com"] exiting on signal 15.
Feb 01 20:14:15 unimatrix3 gpg-agent[1597]: SIGTERM received - shutting down ...
Feb 01 20:14:15 unimatrix3 gpg-agent[1597]: gpg-agent (GnuPG) 2.2.4 angehalten
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping D-Bus User Message Bus...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping GnuPG cryptographic agent and passphrase cache...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping Virtual filesystem service...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping Virtual filesystem service - digital camera monitor...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping XFCE notifications service...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopping Virtual filesystem metadata service...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Create final runtime dir for shutdown pivot root...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping PackageKit Daemon...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Daemon for power management...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped target Timers.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Message of the Day.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped target Graphical Interface.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped target Multi-User System.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Ubuntu system adjustments...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Dispatcher daemon for systemd-networkd...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Initialize hardware monitoring sensors.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Postfix Mail Transport Agent.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping System Logging Service...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped Accessibility services bus.
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped GnuPG cryptographic agent and passphrase cache.
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped Virtual filesystem service - disk device monitor.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Make remote CUPS printers available locally...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Regular background program processing daemon...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped Virtual filesystem service - digital camera monitor.
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping LSB: Speech Dispatcher...
Feb 01 20:14:15 unimatrix3 systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Daily apt upgrade and clean activities.
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped Virtual filesystem metadata service.
Feb 01 20:14:15 unimatrix3 dbus-daemon[813]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.12' (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Postfix Mail Transport Agent (instance -)...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping LSB: Record successful boot for GRUB...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Trigger anacron every hour.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Tool to automatically collect and submit kernel crash signatures...
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped Virtual filesystem service.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Session c2 of user karl.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping LSB: automatic crash report generation...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping LSB: disk temperature monitoring daemon...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped target Login Prompts.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Getty on tty1...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Disk Manager...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped OpenVPN service.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Discard unused blocks once a week.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Light Display Manager...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Modem Manager...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped target Sound Card.
Feb 01 20:14:15 unimatrix3 ModemManager[801]: <info>  Caught signal, shutting down...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping ACPI event daemon...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Availability of block devices...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping irqbalance daemon...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Daily apt download activities.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Accounts Service...
Feb 01 20:14:15 unimatrix3 NetworkManager[820]: <info>  [1580584455.7490] modem-manager: ModemManager no longer available
Feb 01 20:14:15 unimatrix3 ModemManager[801]: <info>  ModemManager is shut down
Feb 01 20:14:15 unimatrix3 systemd[1]: Unmounted /run/user/1000/gvfs.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Regular background program processing daemon.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Accounts Service.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Dispatcher daemon for systemd-networkd.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped irqbalance daemon.
Feb 01 20:14:15 unimatrix3 udisksd[824]: udisks daemon version 2.7.6 exiting
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Authorization Manager.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Manage, Install and Generate Color Profiles.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Getty on tty1.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Daemon for power management.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Make remote CUPS printers available locally.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped PackageKit Daemon.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Disk Manager.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Tool to automatically collect and submit kernel crash signatures.
Feb 01 20:14:15 unimatrix3 dbus-daemon[813]: [system] Activation via systemd failed for unit 'polkit.service': Refusing activation, D-Bus is shutting down.
Feb 01 20:14:15 unimatrix3 postfix/postfix-script[25431]: stopping the Postfix mail system
Feb 01 20:14:15 unimatrix3 postfix/master[1150]: terminating on signal 15
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Postfix Mail Transport Agent (instance -).
Feb 01 20:14:16 unimatrix3 apport[25411]:  * Stopping automatic crash report generation: apport
Feb 01 20:14:16 unimatrix3 apport[25411]:    ...done.
Feb 01 20:14:16 unimatrix3 blkdeactivate[25417]: Deactivating block devices:
Feb 01 20:14:16 unimatrix3 speech-dispatcher[25404]:  * speech-dispatcher disabled; edit /etc/default/speech-dispatcher
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Modem Manager.
Feb 01 20:14:15 unimatrix3 avahi-daemon[808]: Got SIGTERM, quitting.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped LSB: Record successful boot for GRUB.
Feb 01 20:14:15 unimatrix3 avahi-daemon[808]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address <ipv6 address filtered>.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped LSB: Speech Dispatcher.
Feb 01 20:14:15 unimatrix3 avahi-daemon[808]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address <ipv4 address filtered>.
Feb 01 20:14:15 unimatrix3 NetworkManager[820]: <warn>  [1580584455.8852] error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: Authorization check failed: Refusing activation, D-Bus is shutting down.
Feb 01 20:14:15 unimatrix3 avahi-daemon[808]: Leaving mDNS multicast group on interface lo.IPv6 address with ::1.
Feb 01 20:14:15 unimatrix3 NetworkManager[820]: <warn>  [1580584455.8853] error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: Authorization check failed: Refusing activation, D-Bus is shutting down.
Feb 01 20:14:15 unimatrix3 avahi-daemon[808]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Feb 01 20:14:15 unimatrix3 NetworkManager[820]: <info>  [1580584455.8863] device (wlp3s0): state change: activated -> deactivating (reason 'connection-removed', sys-iface-state: 'managed')
Feb 01 20:14:15 unimatrix3 avahi-daemon[808]: avahi-daemon 0.7 exiting.
Feb 01 20:14:15 unimatrix3 NetworkManager[820]: <info>  [1580584455.8869] manager: NetworkManager state is now DISCONNECTING
Feb 01 20:14:15 unimatrix3 systemd[1]: Removed slice system-postfix.slice.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped target Host and Network Name Lookups.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped target System Time Synchronized.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopping CUPS Scheduler...
Feb 01 20:14:15 unimatrix3 systemd[1]: Removed slice system-getty.slice.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped LSB: disk temperature monitoring daemon.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped target Network is Online.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Network Manager Wait Online.
Feb 01 20:14:15 unimatrix3 systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Feb 01 20:14:15 unimatrix3 systemd[1268]: Stopped XFCE notifications service.
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopped ACPI event daemon.
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopped LSB: automatic crash report generation.
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopped Session c2 of user karl.
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopped Save/Restore Sound Card State.
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopped System Logging Service.
Feb 01 20:14:16 unimatrix3 systemd-logind[809]: Removed session c2.
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopped Availability of block devices.
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopped Ubuntu system adjustments.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Stopped D-Bus User Message Bus.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Stopped target Basic System.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Stopped target Sockets.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Feb 01 20:14:16 unimatrix3 systemd[1268]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Feb 01 20:14:16 unimatrix3 systemd[1268]: Closed GnuPG network certificate management daemon.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Feb 01 20:14:16 unimatrix3 systemd[1268]: Closed GnuPG cryptographic agent and passphrase cache.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Stopped target Paths.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Stopped target Timers.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Closed D-Bus User Message Bus Socket.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Reached target Shutdown.
Feb 01 20:14:16 unimatrix3 systemd[1268]: Starting Exit the Session...
Feb 01 20:14:16 unimatrix3 systemd[1268]: Received SIGRTMIN+24 from PID 25785 (kill).
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopped Create final runtime dir for shutdown pivot root.
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopped User Manager for UID 1000.
Feb 01 20:14:16 unimatrix3 systemd[1]: Removed slice User Slice of karl.
Feb 01 20:14:16 unimatrix3 systemd[1]: Stopping Login Service...
Feb 01 20:14:16 unimatrix3 dbus-daemon[813]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Feb 01 20:14:16 unimatrix3 dbus-daemon[813]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
Feb 01 20:14:16 unimatrix3 NetworkManager[820]: <info>  [1580584456.9135] device (wlp3s0): state change: deactivating -> disconnected (reason 'connection-removed', sys-iface-state: 'managed')
Feb 01 20:14:16 unimatrix3 NetworkManager[820]: <info>  [1580584456.9464] dhcp4 (wlp3s0): canceled DHCP transaction, DHCP client pid 1301
Feb 01 20:14:16 unimatrix3 NetworkManager[820]: <info>  [1580584456.9465] dhcp4 (wlp3s0): state changed bound -> done
Feb 01 20:14:17 unimatrix3 wpa_supplicant[819]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=<IPv4 address filtered> reason=3 locally_generated=1
Feb 01 20:14:17 unimatrix3 wpa_supplicant[819]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Feb 01 20:14:17 unimatrix3 NetworkManager[820]: <info>  [1580584457.1660] manager: NetworkManager state is now DISCONNECTED
Feb 01 20:14:17 unimatrix3 dbus-daemon[813]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=820 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Feb 01 20:14:17 unimatrix3 NetworkManager[820]: <warn>  [1580584457.1673] sup-iface[0x561893aa0a40,wlp3s0]: connection disconnected (reason -3)
Feb 01 20:14:17 unimatrix3 dbus-daemon[813]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
Feb 01 20:14:17 unimatrix3 NetworkManager[820]: <info>  [1580584457.1675] device (wlp3s0): supplicant interface state: completed -> disconnected
Feb 01 20:14:17 unimatrix3 systemd[1]: Stopped CUPS Scheduler.
Feb 01 20:14:18 unimatrix3 wpa_supplicant[819]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb 01 20:14:21 unimatrix3 kernel: wlp3s0: deauthenticating from <IPv4 address filtered> by local choice (Reason: 3=DEAUTH_LEAVING)
Feb 01 20:14:21 unimatrix3 systemd[1]: Stopped Login Service.
Feb 01 20:14:25 unimatrix3 systemd[1]: Stopped Light Display Manager.
Feb 01 20:14:25 unimatrix3 systemd[1]: Starting Show Plymouth Reboot Screen...
Feb 01 20:14:25 unimatrix3 systemd[1]: Stopping Permit User Sessions...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Permit User Sessions.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Network.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping Network Manager...
Feb 01 20:14:26 unimatrix3 NetworkManager[820]: <info>  [1580584466.0056] caught SIGTERM, shutting down normally.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping Raise network interfaces...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping Network Name Resolution...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping WPA supplicant...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target User and Group Name Lookups.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Remote File Systems.
Feb 01 20:14:26 unimatrix3 NetworkManager[820]: <info>  [1580584466.0105] device (wlp3s0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed')
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Network Name Resolution.
Feb 01 20:14:26 unimatrix3 wpa_supplicant[819]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Feb 01 20:14:26 unimatrix3 wpa_supplicant[819]: wlp3s0: CTRL-EVENT-TERMINATING
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped WPA supplicant.
Feb 01 20:14:26 unimatrix3 systemd[1]: Received SIGRTMIN+20 from PID 25793 (plymouthd).
Feb 01 20:14:26 unimatrix3 systemd[1]: Started Show Plymouth Reboot Screen.
Feb 01 20:14:26 unimatrix3 NetworkManager[820]: <info>  [1580584466.2065] exiting (success)
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Raise network interfaces.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Network Manager.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping D-Bus System Message Bus...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped D-Bus System Message Bus.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Basic System.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Sockets.
Feb 01 20:14:26 unimatrix3 systemd[1]: Closed CUPS Scheduler.
Feb 01 20:14:26 unimatrix3 systemd[1]: Closed UUID daemon activation socket.
Feb 01 20:14:26 unimatrix3 systemd[1]: Closed ACPID Listen Socket.
Feb 01 20:14:26 unimatrix3 systemd[1]: Closed Syslog Socket.
Feb 01 20:14:26 unimatrix3 systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Slices.
Feb 01 20:14:26 unimatrix3 systemd[1]: Removed slice User and Session Slice.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Paths.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped ACPI Events Check.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped CUPS Scheduler.
Feb 01 20:14:26 unimatrix3 systemd[1]: Closed D-Bus System Message Bus Socket.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target System Initialization.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping Load/Save Random Seed...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping Network Time Synchronization...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Local Encrypted Volumes.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Apply Kernel Variables.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Load Kernel Modules.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:acpi_video0...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:radeon_bl0...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Load/Save Random Seed.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:radeon_bl0.
Feb 01 20:14:26 unimatrix3 systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Network Time Synchronization.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Create Volatile Files and Directories.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Local File Systems.
Feb 01 20:14:26 unimatrix3 systemd[1]: Unmounting /run/user/1000...
Feb 01 20:14:26 unimatrix3 systemd[1]: Unmounting /boot...
Feb 01 20:14:26 unimatrix3 systemd[1]: Unmounted /run/user/1000.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Swap.
Feb 01 20:14:26 unimatrix3 systemd[1]: Deactivating swap /dev/disk/by-uuid/9eb5e38a-d7f5-4e83-bb06-3ee6445a1111...
Feb 01 20:14:26 unimatrix3 systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:1f.2-ata-1-part6.
Feb 01 20:14:26 unimatrix3 systemd[1]: Deactivated swap /dev/disk/by-partuuid/b0ffe0c4-06.
Feb 01 20:14:26 unimatrix3 systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5000cca5edca76a0-part6.
Feb 01 20:14:26 unimatrix3 systemd[1]: Deactivated swap /dev/disk/by-id/ata-Hitachi_HTS545032B9A300_100107PBN3061TGS0K8R-part6.
Feb 01 20:14:26 unimatrix3 systemd[1]: Deactivated swap /dev/sda6.
Feb 01 20:14:26 unimatrix3 systemd[1]: Deactivated swap /dev/disk/by-uuid/9eb5e38a-d7f5-4e83-bb06-3ee6445a1111.
Feb 01 20:14:26 unimatrix3 systemd[1]: Unmounted /boot.
Feb 01 20:14:26 unimatrix3 systemd[1]: Reached target Unmount All Filesystems.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/3143c685-9eff-4c79-8216-f6389324a50d.
Feb 01 20:14:26 unimatrix3 systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped target Local File Systems (Pre).
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Create Static Device Nodes in /dev.
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Remount Root and Kernel File Systems.
Feb 01 20:14:26 unimatrix3 systemd[1]: Reached target Shutdown.
Feb 01 20:14:26 unimatrix3 systemd[1]: Starting Shuts down the "live" preinstalled system cleanly...
Feb 01 20:14:26 unimatrix3 systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Feb 01 20:14:31 unimatrix3 systemd[1]: Stopping LVM2 metadata daemon...
Feb 01 20:14:31 unimatrix3 systemd[1]: Stopped LVM2 metadata daemon.
Feb 01 20:14:35 unimatrix3 systemd[1]: Started Shuts down the "live" preinstalled system cleanly.
Feb 01 20:14:35 unimatrix3 systemd[1]: Reached target Final Step.
Feb 01 20:14:35 unimatrix3 systemd[1]: Starting Reboot...
Feb 01 20:14:35 unimatrix3 systemd[1]: Shutting down.
Feb 01 20:14:36 unimatrix3 kernel: systemd-shutdow: 33 output lines suppressed due to ratelimiting
Feb 01 20:14:36 unimatrix3 systemd-shutdown[1]: Syncing filesystems and block devices.
Feb 01 20:14:36 unimatrix3 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Feb 01 20:14:36 unimatrix3 systemd-journald[391]: Journal stopped
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 9.51 64-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)
Centauri39
Level 4
Level 4
Posts: 296
Joined: Sun Mar 23, 2014 2:20 pm

Re: Shutdown problems - Failed to wait for process: Protocol error

Post by Centauri39 »

That command is giving me a huuuuuge amount of data.
Got no idea, what's the relevant section of that output.
caz
Level 4
Level 4
Posts: 275
Joined: Mon Dec 31, 2012 6:48 am
Location: England

Odd message during shutdown: "Failed to wait for process: Protocol error"

Post by caz »

IMG_.JPG
Hi all. A couple of days ago this message started to flash up during shutdown. It's only there for a second and then my machine switches off. I haven't noticed any new problems when running Mint so I'm not sure what's going on.

Any help with fixing this or identifying the cause will be much appreciated.

Linux Mint Mate 19.3.
Some stuff I made using FOSS http://caz747.deviantart.com/
Post Reply

Return to “Installation & Boot”