Arch Linux

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

System doesn't reboot/shutdown (cgroup : option or name mismatch....)

Hi all.

I can't reboot or shutdown my computer by command (reboot/shutdown) or by desktop enviroment (Gnome). After 'everything' is done to shutdown I got the "error message"

cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"

I already searched on forum and I found this, but I think people there is only concerning about message but the system reboots after a while. In my case it doesn't happen. My system stop working when this message is shown and I can only end it if I turn it off (by remove power energy).

I want to know if I can do anything to search for the cause of this "crash". Do you guys have any idea?

OBS: a weird thing is happing after I turn my PC on and off because of this issue. After that, my system boots without recognizing my icon themes, even if it's set and I change the icons (by Gnome Tweaking Tool), so when I have to reboot, I have to turn the PC on and off twices. I don't know if these problems are related.

Thanks in advance.

runical

Member

From: The Netherlands

Registered: 2012-03-03

Posts: 896

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

Looking at post #4 of that forum threat, it seems that the cgroup message is not relevant in this case. Is there anything in the logs?

---

For all your makepkg signature checking troubles

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

I have read  everything in that thred, but my problem is a little diferent, I can't reboot/shutdown my system. I have looked for somehing in logs file but I don't know if I have looked in the right log file.

clfarron4

Member

From: London, UK

Registered: 2013-06-28

Posts: 2,163

Website

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

OK, the next time you have to "pull-the-plug" on the machine, can you start it back up and post the contents of the following command:

journalctl -b -1

That should be a good starting point.

---

Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

Well, I just tried to reboot, the system was hanged, so I turn it off and on. First thing I did was running "journalctl -b -1"
Well, the text is too big so I have cutted it in the last minutes. I don't know if it works

Jan 23 19:33:22 MALIBU smbd[4638]: [2015/01/23 19:33:22.341664,  0] ../source3/printing/print_cups.c:151(cups_connect)
Jan 23 19:33:22 MALIBU smbd[4638]: Unable to connect to CUPS server /run/cups/cups.sock:631 - Descritor de arquivo inválido
Jan 23 19:33:22 MALIBU smbd[524]: [2015/01/23 19:33:22.341949,  0] ../source3/printing/print_cups.c:528(cups_async_callback)
Jan 23 19:33:22 MALIBU smbd[524]: failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL
Jan 23 19:34:42 MALIBU gnome-session[589]: K_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: Showing the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_STICKY | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 40
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: hiding the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_WITHDRAWN | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 33
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: Showing the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_STICKY | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 40
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: hiding the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_WITHDRAWN | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 33
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: Showing the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_STICKY | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 40
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: hiding the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_WITHDRAWN | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 33
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: Showing the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_STICKY | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 40
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: hiding the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_WITHDRAWN | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 33
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: Showing the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_STICKY | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 40
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: hiding the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_WITHDRAWN | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 33
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: Showing the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_STICKY | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 40
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: hiding the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_WITHDRAWN | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 33
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: Showing the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_STICKY | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 40
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE? True
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: hiding the terminal
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG Window display
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = <flags GDK_WINDOW_STATE_WITHDRAWN | GDK_WINDOW_STATE_ABOVE of type GdkWindowState>
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: gtk.gdk.WindowState = 33
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_STICKY? False
Jan 23 19:34:42 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_WITHDRAWN? True
Jan 23 19:34:47 MALIBU sudo[4519]: pam_unix(sudo:session): session closed for user root
Jan 23 19:34:50 MALIBU polkitd[338]: Registered Authentication Agent for unix-process:4647:16711533 (system bus name :1.88 [/usr/bin/pkttyagent --notify-fd 5 --fallback], objec
Jan 23 19:34:50 MALIBU systemd-logind[316]: System is rebooting.
Jan 23 19:34:50 MALIBU polkitd[338]: Unregistered Authentication Agent for unix-process:4647:16711533 (system bus name :1.88, object path /org/freedesktop/PolicyKit1/Authentica
Jan 23 19:34:50 MALIBU systemd[1]: Deactivating swap /dev/sda2...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Sound Card.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped target Sound Card.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Daemon for power management...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Accounts Service...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Jan 23 19:34:50 MALIBU systemd[1]: Starting Store Sound Card State...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping system-systemd\x2dfsck.slice.
Jan 23 19:34:50 MALIBU systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping User Manager for UID 1000...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Jan 23 19:34:50 MALIBU systemd[1]: Deactivating swap /dev/sda2...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Session c2 of user janilson.
Jan 23 19:34:50 MALIBU avahi-daemon[527]: Got SIGTERM, quitting.
Jan 23 19:34:50 MALIBU avahi-daemon[527]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 192.168.0.100.
Jan 23 19:34:50 MALIBU avahi-daemon[527]: avahi-daemon 0.6.31 exiting.
Jan 23 19:34:50 MALIBU dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Jan 23 19:34:50 MALIBU polkitd[338]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.45, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, 
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Session c2 of user janilson.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Graphical Interface.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped target Graphical Interface.
Jan 23 19:34:50 MALIBU systemd[578]: Starting Shutdown.
Jan 23 19:34:50 MALIBU systemd[578]: Reached target Shutdown.
Jan 23 19:34:50 MALIBU systemd[578]: Starting Exit the Session...
Jan 23 19:34:50 MALIBU systemd[578]: Stopping Default.
Jan 23 19:34:50 MALIBU systemd[578]: Stopped target Default.
Jan 23 19:34:50 MALIBU systemd[578]: Stopping Basic System.
Jan 23 19:34:50 MALIBU systemd[578]: Stopped target Basic System.
Jan 23 19:34:50 MALIBU systemd[578]: Stopping Sockets.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping GNOME Display Manager...
Jan 23 19:34:50 MALIBU systemd[578]: Stopped target Sockets.
Jan 23 19:34:50 MALIBU systemd[578]: Stopping Timers.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Multi-User System.
Jan 23 19:34:50 MALIBU systemd[578]: Stopped target Timers.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped target Multi-User System.
Jan 23 19:34:50 MALIBU systemd[578]: Stopping Paths.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Samba SMB/CIFS server...
Jan 23 19:34:50 MALIBU systemd[578]: Stopped target Paths.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Login Service...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Entropy Harvesting Daemon...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping D-Bus System Message Bus...
Jan 23 19:34:50 MALIBU systemd[1]: Deactivating swap /dev/sda2...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping WPA supplicant...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Authorization Manager...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping system-getty.slice.
Jan 23 19:34:50 MALIBU NetworkManager[319]: <warn> disconnected by the system bus.
Jan 23 19:34:50 MALIBU polkitd[338]: Lost the name org.freedesktop.PolicyKit1 - exiting
Jan 23 19:34:50 MALIBU gnome-session[589]: DBG: GDK_WINDOW_STATE_ABOVE?
Jan 23 19:34:50 MALIBU gnome-session[589]: Received signal:15->'Terminado'
Jan 23 19:34:50 MALIBU systemd[1]: Removed slice system-getty.slice.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Login Prompts.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped target Login Prompts.
Jan 23 19:34:50 MALIBU systemd[1]: Starting Generate shutdown-ramfs...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Bluetooth.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped target Bluetooth.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Timers.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped target Timers.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Daily man-db cache update.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Daily man-db cache update.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Daily verification of password and group files.
Jan 23 19:34:50 MALIBU systemd[1]: Deactivating swap /dev/sda2...
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Disk Manager...
Jan 23 19:34:50 MALIBU haveged[318]: haveged: Stopping due to signal 15
Jan 23 19:34:50 MALIBU haveged[318]: haveged starting up
Jan 23 19:34:50 MALIBU NetworkManager[319]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-q
Jan 23 19:34:50 MALIBU wpa_supplicant[539]: Successfully initialized wpa_supplicant
Jan 23 19:34:50 MALIBU gnome-session[589]: Received signal:15->'Terminado'
Jan 23 19:34:50 MALIBU org.freedesktop.Tracker1[606]: Received signal:15->'Terminado'
Jan 23 19:34:50 MALIBU gnome-session[589]: Received signal:15->'Terminado'
Jan 23 19:34:50 MALIBU gnome-session[589]: Received signal:15->'Terminado'
Jan 23 19:34:50 MALIBU systemd[1]: Stopped D-Bus System Message Bus.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Entropy Harvesting Daemon.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Accounts Service.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Authorization Manager.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Manage, Install and Generate Color Profiles.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped WPA supplicant.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Disk Manager.
Jan 23 19:34:50 MALIBU systemd[1]: Started Store Sound Card State.
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Login Service.
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) evdev: AT Translated Set 2 keyboard: Close
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) UnloadModule: "evdev"
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) UnloadModule: "joystick"
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) UnloadModule: "joystick"
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Close
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) UnloadModule: "evdev"
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) evdev: Microsoft Microsoft® Nano Transceiver v2.0: Close
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) UnloadModule: "evdev"
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) evdev: Power Button: Close
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) UnloadModule: "evdev"
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) evdev: Power Button: Close
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (II) UnloadModule: "evdev"
Jan 23 19:34:50 MALIBU gdm-Xorg-:0[327]: (EE) Server terminated successfully (0). Closing log file.
Jan 23 19:34:50 MALIBU smbd[523]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsFailed to delete pidfile /var/run/smbd.pid. Error was Arquivo ou diret
Jan 23 19:34:50 MALIBU systemd[1]: Stopped Samba SMB/CIFS server.
Jan 23 19:34:50 MALIBU systemd[1]: Stopping Samba Winbind daemon...
Jan 23 19:34:50 MALIBU winbindd[521]: STATUS=daemon 'winbindd' finished starting up and ready to serve connectionsGot sig[15] terminate (is_parent=1)
Jan 23 19:34:50 MALIBU winbindd[526]: STATUS=daemon 'winbindd' finished starting up and ready to serve connectionsGot sig[15] terminate (is_parent=0)
Jan 23 19:34:50 MALIBU gdm[322]: Freeing conversation 'gdm-password' with active job
Jan 23 19:34:50 MALIBU systemd[1]: Stopped GNOME Display Manager.
Jan 23 19:34:51 MALIBU systemd[1]: Deactivated swap /dev/disk/by-uuid/021a6afe-b4b1-421e-b58a-2b5edf7cfa1d.
Jan 23 19:34:51 MALIBU systemd[1]: Deactivated swap /dev/disk/by-label/swap.
Jan 23 19:34:51 MALIBU systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5000c5006cb25b00-part2.
Jan 23 19:34:51 MALIBU systemd[1]: Deactivated swap /dev/disk/by-id/ata-ST1000DM003-1CH162_S1DFB3WZ-part2.
Jan 23 19:34:51 MALIBU systemd[1]: Deactivated swap /dev/sda2.
Jan 23 19:34:51 MALIBU systemd[578]: Received SIGRTMIN+24 from PID 4664 (kill).
Jan 23 19:34:51 MALIBU systemd[579]: pam_unix(systemd-user:session): session closed for user janilson
Jan 23 19:34:51 MALIBU systemd[1]: Stopped User Manager for UID 1000.
Jan 23 19:34:51 MALIBU systemd[1]: Stopping Permit User Sessions...
Jan 23 19:34:51 MALIBU systemd[1]: Stopping user-1000.slice.
Jan 23 19:34:51 MALIBU systemd[1]: Removed slice user-1000.slice.
Jan 23 19:34:51 MALIBU systemd[1]: Stopped Permit User Sessions.
Jan 23 19:34:51 MALIBU systemd[1]: Stopping Remote File Systems.
Jan 23 19:34:51 MALIBU systemd[1]: Stopped target Remote File Systems.
Jan 23 19:34:51 MALIBU mkinitcpio[4667]: ==> Starting build: none
Jan 23 19:34:51 MALIBU systemd[1]: Stopped Samba Winbind daemon.
Jan 23 19:34:51 MALIBU systemd[1]: Stopping Samba NetBIOS name server...
Jan 23 19:34:51 MALIBU nmbd[519]: STATUS=daemon 'nmbd' finished starting up and ready to serve connectionsGot SIGTERM: going down...
Jan 23 19:34:51 MALIBU mkinitcpio[4667]: -> Running build hook: [sd-shutdown]
Jan 23 19:34:51 MALIBU systemd[1]: Stopped Samba NetBIOS name server.
Jan 23 19:34:51 MALIBU systemd[1]: Stopping Network.
Jan 23 19:34:51 MALIBU systemd[1]: Stopped target Network.
Jan 23 19:34:51 MALIBU systemd[1]: Stopping Network Manager...
Jan 23 19:34:51 MALIBU NetworkManager[319]: <info> caught signal 15, shutting down normally.
Jan 23 19:34:51 MALIBU NetworkManager[319]: (NetworkManager:319): GLib-CRITICAL **: Source ID 20 was not found when attempting to remove it
Jan 23 19:34:51 MALIBU NetworkManager[319]: <info> exiting (success)
Jan 23 19:34:51 MALIBU systemd[1]: Stopped Network Manager.
Jan 23 19:34:51 MALIBU mkinitcpio[4667]: ==> Build complete.
Jan 23 19:34:51 MALIBU systemd[1]: Started Generate shutdown-ramfs.
Jan 23 19:34:55 MALIBU systemd-udevd[171]: error opening USB device 'descriptors' file
Jan 23 19:34:55 MALIBU kernel: usb 4-1.2: USB disconnect, device number 6

pgoetz

Member

From: Austin, Texas

Registered: 2014-02-21

Posts: 341

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

You might also try running

# systemctl --failed

to see if any services failed to load.

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

I've tried this and

[janilson@MALIBU ~]$ systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

After  see for a long period (30min ) the message

cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"
shutdown[1]: Failed to finalize  file systems, ignoring

I have taken a photograph
http://i.imgur.com/fB7zlTZ.jpg

I got this message many times until I gave up and turn the PC off
OBS: this message was repeating after a while. But it was always the same message

Thanks in advance

Last edited by Janilson (2015-01-28 21:34:55)

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

After try sometimes now I'm getting this error

A stop job is running for Daemon for power management (20s/1min 30s)

It doesn't matter how much I wait, this timer always increases so my PC hangs and does nothing to shutdown.

I still can't shutdown my PC

runical

Member

From: The Netherlands

Registered: 2012-03-03

Posts: 896

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

Sorry, I don't have any idea what might be going on (which is why I didn't reply earlier). Is it possible that this is a hardware issue? Or maybe a problem with unmounting external drives?

See if the same thing happens with different distros if you are able to. Try disabling non-critical services and see if it helps. In the ultimate "I don't know", try a fresh arch install and see what the differences are when compared to the current install if the problems are absent (Or just move to the new install if all else fails and the problem is fixed).

---

For all your makepkg signature checking troubles

gregorylock

Member

Registered: 2015-01-29

Posts: 10

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

I have a computer that I think has the same problem described.  It is a complete Intel machine.  I tried several different Distros on it, and they all seem to have the same shutdown symptoms.  Some of them Turn off the machine sometimes and others won't turn it off at all.  When it won't shut down it gives me this exact same message, and then freezes up.

cgroup : option or name mismatch, new: 0x0"", old: 0x4 "systemd"
shutdown[1]: Failed to finalize  file systems, ignoring

I began my research with google searches.  It seems that some people experience a shutdown problem.  Then I moved to the LinuxDistroCommunity forums and a person told me He started having problems after the Kernel got updated.  I tested  Manjaro on my Machine since you can switch Kernels easy.  But I have the same problem with all the Kernels. Some people thought it could be the Bios.  I flashed the Bios, and for a while it seemed to be helping.  But after 5 successful shutdowns the machine went back it's old habit.   Now in some forums people think it is a problem with systemd.  Anyways I've been researching this for a year now, and this is as far I've gotten.  I know it is not hardware failure because Windows manages to turn the machine off every time, where as Linux turns the machine off, only when it 'feels' like it. 

Since this seems to effect every Linux distro I tried on this machine.  My guess is there must be something in common with all of them.  Logically I think it's the Systemd, not being fully compatible with Mainboard or Bios Firmware.  I think we need  to look more into systemd, and try to figure out if there could be anything in it that could be causing this bug.  One suggestion made to me is.  "Try a distro that doesn't use systemd"

Last edited by gregorylock (2015-02-02 21:05:58)

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

o.O
Gregory, you made me sad with your comments.
I was thinking about asking in Arch mail list, maybe some arch gurus can have a clue. It's not hard for me to believe that systemd is the problem.
I really don't know what to do, I can't go back to windows, and the only distro I would like to move to is gentoo, but I really want to stay with Arch.

@Gregory, so your machine still has the same problem for a year? Or did you move to another distro without systemd?

Thanks for your comments.

runical

Member

From: The Netherlands

Registered: 2012-03-03

Posts: 896

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

I was thinking about asking in Arch mail list, maybe some arch gurus can have a clue.

Asking there increases the likelihood of a developer reading the question, so that is not a bad idea.

If systemd seems to be the problem, try something like void linux or debian stable to see if the problem persists. Alternatively, you can set up arch to boot with openRC (although that will not be as easy to maintain).

Last edited by runical (2015-02-03 13:52:07)

---

For all your makepkg signature checking troubles

gregorylock

Member

Registered: 2015-01-29

Posts: 10

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

o.O
Gregory, you made me sad with your comments.
I was thinking about asking in Arch mail list, maybe some arch gurus can have a clue. It's not hard for me to believe that systemd is the problem.
I really don't know what to do, I can't go back to windows, and the only distro I would like to move to is gentoo, but I really want to stay with Arch.

@Gregory, so your machine still has the same problem for a year? Or did you move to another distro without systemd?

Thanks for your comments.

Testing a none Systemd OS is still on my "To Try" list.  But in the mean time I've been looking around to find out if anyone knows how I could try changing the configuration.

Alad

Wiki Admin/IRC Op

From: Bagelstan

Registered: 2014-05-04

Posts: 2,412

Website

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

After try sometimes now I'm getting this error

A stop job is running for Daemon for power management (20s/1min 30s)

It doesn't matter how much I wait, this timer always increases so my PC hangs and does nothing to shutdown.

I still can't shutdown my PC

Try

# systemctl mask upower.service
# systemctl stop upower.service

For the finalize thing, maybe this gives some ideas:

https://bugs.debian.org/cgi-bin/bugrepo … bug=688985
https://ask.fedoraproject.org/en/questi … e-effects/

You can also try an LTS kernel (3.14 from the repos, 3.10 from the AUR or ArchAudio).

PS: switching inits doesn't take long, provided you don't use GNOME.

Last edited by Alad (2015-02-03 17:15:34)

---

Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

I just tried to use KDE and there the "reboot" button works. In KDE menu Settings/Autentication Screen/Shutdown tab I found this command

/sbin/shutdown -r now

It's really differente than the one I was running (reboot).

I Will try your option @Alad and I willl see if it works.

As far as I know, it's true that I can't use Gnome without systemd

Soukyuu

Member

Registered: 2014-04-08

Posts: 854

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

I'm getting the same error message about cgroup mismatch for systemd, also on a full Intel (+nvidia GPU) machine. However, it shuts down right after it anyway...

Last edited by Soukyuu (2015-02-05 12:10:39)

---

[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]

gregorylock

Member

Registered: 2015-01-29

Posts: 10

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

I'm getting the same error message about cgroup mismatch for systemd, also on a full Intel (+nvidia GPU) machine. However, it shuts down right after it anyway...

I think it is entirely possible that the error message may have nothing to do with what is actually happening to Janilson and I.  But it is the only lead we have so far....

Last edited by gregorylock (2015-02-05 16:13:27)

runical

Member

From: The Netherlands

Registered: 2012-03-03

Posts: 896

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

Could it be that this is filesystem related? My desktop sometimes does not shutdown when I have my external disk with NTFS mounted. It never happens when the disk is not mounted.

---

For all your makepkg signature checking troubles

gregorylock

Member

Registered: 2015-01-29

Posts: 10

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

Could it be that this is filesystem related? My desktop sometimes does not shutdown when I have my external disk with NTFS mounted. It never happens when the disk is not mounted.

I think  in my case it could be filesystem related because some people have suggested that as a possibility to me in this thread.  @Janilson I think you should also take a look at this thread. 

http://www.cupoflinux.com/SBB/index.php … l#msg16802

However I don't think Janilson has windows on his machine. 

In my experience, a lot of Linux users hold onto a Windows partition.  When I first tried Ubuntu I installed it along side of Windows.  Then when I tried LXLE (based off of Lubuntu)  I installed it along side of Windows.  I experienced shut down problems under LXLE, but I can't remember what happened with Ubuntu because it's been about 4 years ago....   This time I did things differently.  Not only is Manjaro Distro Built on Arch but it's also installed on it's own independent hard drive.  That includes the grub too. 

* What I'm trying to make it clear here is this bug is not just in Arch. 

Method of Install used:

Windows Hard Drive unplugged. 
Linux Installed
Windows Hard Drive plugged back in
Linux updated and Grub added Windows Boot Loader to the List.
(The system knows the windows drive is there, but does not mount it until I tell it too.  I can't remember the last time I mounted the windows drive under Linux   I just know that the OS always shows me it isn't mounted.)

*I hope we can find a solution for this because I'm sure others are suffering too.

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

I've done what @lad told me to, it seems it works now (I have tried several times and in most of them I can reboot my computer).
Since now I'm using KDE (I thought it was the problem) when I start the KDE I get a notification message that the Power Management is not set. Is that what the command

# systemctl mask upower.service
# systemctl stop upower.service

After I run this command I've tried to reboot with no success, but then I can reboot, so I think this command has made something.

@runical I don't have any other filesystem, I only use ArchLinux+Ext4

@gregorylock it's true that not only arch users are experiencing problems with it, many people is blaming the systemd :S

Well, since I did had problem sometimes after I issued the command above, I will try to reboot my PC every day, if it always work, I will set this thread as solved. But in a strange way I think.
Of course I do thank you all, because it seems I finally can reboot my PC again, but maybe we can figure out how to fix this (I think it's a problem)

Obs: by "we can figure out" I'm refering to you more than me

Thanks again

gregorylock

Member

Registered: 2015-01-29

Posts: 10

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

I've done what @lad told me to, it seems it works now (I have tried several times and in most of them I can reboot my computer).
Since now I'm using KDE (I thought it was the problem) when I start the KDE I get a notification message that the Power Management is not set. Is that what the command

# systemctl mask upower.service
# systemctl stop upower.service

After I run this command I've tried to reboot with no success, but then I can reboot, so I think this command has made something.

@runical I don't have any other filesystem, I only use ArchLinux+Ext4

@gregorylock it's true that not only arch users are experiencing problems with it, many people is blaming the systemd :S

Well, since I did had problem sometimes after I issued the command above, I will try to reboot my PC every day, if it always work, I will set this thread as solved. But in a strange way I think.
Of course I do thank you all, because it seems I finally can reboot my PC again, but maybe we can figure out how to fix this (I think it's a problem)

Obs: by "we can figure out" I'm refering to you more than me

Thanks again

I also tried running those two commands and it didn't seem to change anything on my system.

I'm running XFCe

Last edited by gregorylock (2015-02-09 00:18:41)

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

Things are very strange to me. After few more reboot it stopped work again. So I switched to Gnome (it worked only after I umask and start upower service).

Now the reboot works "when it want to". Sometimes it works sometimes it doesn't. It's is freaking me out, I can't understand that.

@Gregorylock, I didn't try with XFCE, only with KDE and Gnome, but as you see, something is really weird with this stuff.

gregorylock

Member

Registered: 2015-01-29

Posts: 10

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

Things are very strange to me. After few more reboot it stopped work again. So I switched to Gnome (it worked only after I umask and start upower service).

Now the reboot works "when it want to". Sometimes it works sometimes it doesn't. It's is freaking me out, I can't understand that.

@Gregorylock, I didn't try with XFCE, only with KDE and Gnome, but as you see, something is really weird with this stuff.

I don't have any trouble with rebooting.  But I have trouble with shutting down.  Sometimes it will turn the power off and sometimes it will just freeze up.  It doesn't seem to be an issue with what I have mounted and what I don't have mounted.  Generally speaking I unmount all my USB drives and unplug them before shutting down.  The shut down messages are usually the same but their have been times when it even reads something different.  But as long as it works I don't care. 

My current theory is we have a compatiblity issue between something in Systemd and our BIOS firmware.  I say this because I've tried different Kernels and they don't seem to make any difference.  Except I know that I won't be using Kernel 3.10 because when I install that one things mess up really bad.  I'm talking panels that don't load, and mouse and keyboard issues.  But the day I flashed my BIOS with the Current version that it already has (Intel is not making any firmware for this mainboard)  My shut down problems went away for about 5 shutdowns before the computer returned to it's bad habbit. 

Listening to the computer:

During a bad shutdown, It sounds like the hard drives turn off before it kicks the powersupply off.  Does yours sound like that?

Janilson

Member

From: Recife-PE/Brazil

Registered: 2013-03-05

Posts: 55

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

it's so weird the fact you have problems only with shutdowns;

Well, it seems the hard drive does turns off. I have tested things with or without mounted filesystem (android device) and sometimes it works and sometimes it doesn't, just like you.
I don't know what to do, but I'm trying to avoid rebooting/shutting down my computer.

gregorylock

Member

Registered: 2015-01-29

Posts: 10

Re: System doesn't reboot/shutdown (cgroup : option or name mismatch....)

it's so weird the fact you have problems only with shutdowns;

Well, it seems the hard drive does turns off. I have tested things with or without mounted filesystem (android device) and sometimes it works and sometimes it doesn't, just like you.
I don't know what to do, but I'm trying to avoid rebooting/shutting down my computer.

I don't know for sure... But when It comes to manually turning off your machine, I think Linux is more forgiving than Windows.  Anyways I think this is a good question for this forum.  When one needs to do a force shutdown does it hurt the Linux OS like it can Hurt the Windows OS?