You are not logged in.

#1 2016-01-06 14:28:35

dviktor
Member
From: Moscow
Registered: 2015-10-18
Posts: 155

[SOLVED] problems with Login Service on reboot or shutdown

Hi everyone. Recently after some update (couldn't remember exactly what, but I also installed Steam) I've noticed that when I want to reboot or shutdown my laptop via XFCE menu system hangs after killing X with next message on display:

A stop job is running for Login Service...
followed by some timestamps. I tried to wait but with no luck - only hard-shutdown via button on my laptop helped. Interesting thing: if first I logout via XFCE menu and then manually shutdown or reboot laptop via tty2 (I have no login managers like GDM - X starting after login on tty1) all is ok.

So, guys, what the hell is this?

Kernel 4.3.3-2, XFCE 4.12, Xorg 1.18.0-3

Last edited by dviktor (2016-02-02 08:50:31)

Offline

#2 2016-01-07 16:39:27

dviktor
Member
From: Moscow
Registered: 2015-10-18
Posts: 155

Re: [SOLVED] problems with Login Service on reboot or shutdown

anyone? It's very annoying problem!

Offline

#3 2016-01-07 16:58:43

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 17,277

Re: [SOLVED] problems with Login Service on reboot or shutdown

Rather than bumping your thread, try to provide us with more information.  These are active forums, if someone had enough information to help you, they would.  As, we are sure, you are continuing to work the problem. share with us what you have read, what you have learned, learned, what you have tried. what wokred, what didn't.

The updates are available in you pacman log.  Post that part of the log starting before your problem started.
How do you start Xfce4?  You don;t use a Display manager (good smile ), but do you use startx or xinit?  What are the contents of ~/.xinitrc or what do you pass on the command line to xinit?
When you start to log out, does Xorg terminate? any interesting messages on the screen?  Anything interesting in the Xorg log?  Anything interesting in the Journal?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#4 2016-01-07 19:27:13

dviktor
Member
From: Moscow
Registered: 2015-10-18
Posts: 155

Re: [SOLVED] problems with Login Service on reboot or shutdown

here is the full list of any package changes from when the problem appeared

I start XFCE through .xinitrc, here it's:

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then
    xrdb -merge "$userresources"
fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

#twm &
#xclock -geometry 50x50-1+1 &
#xterm -geometry 80x50+494+51 &
#xterm -geometry 80x20+494-0 &
#exec xterm -geometry 80x66+0+0 -name login
exec startxfce4

During the log out X server stops, at the very bottom of screen some message appears but vanishes too quick. I can't found any clues in Xorg.0.log or Xorg.0.log.old. After that I see blank screen with blinking underline-symbol cursor at left top corner of the screen and "A stop job is running..." message some seconds later.

Found something interesting in systemd journal:

янв 05 19:41:29 freesky-laptop org.a11y.atspi.Registry[695]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0
янв 05 19:41:29 freesky-laptop systemd[573]: Stopped Virtual filesystem service - disk device monitor.
янв 05 19:41:29 freesky-laptop systemd[573]: Stopping Virtual filesystem service...
янв 05 19:41:29 freesky-laptop systemd[573]: Stopping Virtual filesystem metadata service...
янв 05 19:41:29 freesky-laptop systemd[573]: Stopped target Default.
янв 05 19:41:29 freesky-laptop systemd[573]: Stopping Sound Service...
янв 05 19:41:29 freesky-laptop systemd[573]: Stopping D-Bus User Message Bus...
янв 05 19:41:29 freesky-laptop systemd[573]: Stopped Sound Service.
янв 05 19:41:29 freesky-laptop systemd[573]: Stopped Virtual filesystem metadata service.
янв 05 19:41:29 freesky-laptop systemd[573]: Stopped Virtual filesystem service.
янв 05 19:41:29 freesky-laptop org.a11y.atspi.Registry[695]: after 13197 requests (13197 known processed) with 0 events remaining.
янв 05 19:41:29 freesky-laptop gvfsd[653]: ** (process:1509): WARNING **: Error initializing Avahi: Неожиданная ошибка D-Bus
янв 05 19:41:30 freesky-laptop systemd[573]: Stopped D-Bus User Message Bus.
янв 05 19:41:30 freesky-laptop systemd[573]: Stopped target Basic System.
янв 05 19:41:30 freesky-laptop systemd[573]: Stopped target Sockets.
янв 05 19:41:30 freesky-laptop systemd[573]: Closed Sound System.
янв 05 19:41:30 freesky-laptop systemd[573]: Stopped target Timers.
янв 05 19:41:30 freesky-laptop systemd[573]: Stopped target Paths.
янв 05 19:41:30 freesky-laptop systemd[573]: Closed D-Bus User Message Bus Socket.
янв 05 19:41:30 freesky-laptop systemd[573]: Reached target Shutdown.
янв 05 19:41:30 freesky-laptop systemd[573]: Starting Exit the Session...
янв 05 19:41:30 freesky-laptop systemd[573]: Received SIGRTMIN+24 from PID 3717 (kill).
янв 05 19:41:30 freesky-laptop systemd[575]: pam_unix(systemd-user:session): session closed for user viktor

Offline

#5 2016-01-07 21:44:17

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,297

Re: [SOLVED] problems with Login Service on reboot or shutdown

systemd[573] is systemd user process.

systemd system is systemd[1].

Post all the journal entries from the time of the shutdown command to the forced powering off.
You can get these entries after a reboot and with the command:

journalctl -b -1 -e

Offline

#6 2016-01-08 15:12:25

dviktor
Member
From: Moscow
Registered: 2015-10-18
Posts: 155

Re: [SOLVED] problems with Login Service on reboot or shutdown

Here it's:

-- Logs begin at Вс 2015-09-27 21:50:59 MSK, end at Пт 2016-01-08 18:08:40 MSK. --
янв 08 18:03:33 freesky-laptop systemd[581]: Reached target Paths.
янв 08 18:03:33 freesky-laptop systemd[581]: Starting D-Bus User Message Bus Socket.
янв 08 18:03:33 freesky-laptop systemd[581]: Reached target Timers.
янв 08 18:03:33 freesky-laptop systemd[581]: Listening on Sound System.
янв 08 18:03:33 freesky-laptop systemd[581]: Listening on D-Bus User Message Bus Socket.
янв 08 18:03:33 freesky-laptop systemd[581]: Reached target Sockets.
янв 08 18:03:33 freesky-laptop systemd[581]: Reached target Basic System.
янв 08 18:03:33 freesky-laptop systemd[581]: Reached target Default.
янв 08 18:03:33 freesky-laptop systemd[581]: Startup finished in 163ms.
янв 08 18:03:38 freesky-laptop systemd[581]: Started D-Bus User Message Bus.
янв 08 18:03:40 freesky-laptop dbus-daemon[627]: Activating service name='org.xfce.Xfconf'
янв 08 18:03:40 freesky-laptop dbus-daemon[627]: Successfully activated service 'org.xfce.Xfconf'
янв 08 18:03:41 freesky-laptop systemd[581]: Time has been changed
янв 08 18:03:42 freesky-laptop dbus-daemon[627]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
янв 08 18:03:42 freesky-laptop systemd[581]: Starting Virtual filesystem service...
янв 08 18:03:42 freesky-laptop systemd[581]: Starting Sound Service...
янв 08 18:03:43 freesky-laptop dbus-daemon[627]: Activating service name='org.freedesktop.Notifications'
янв 08 18:03:43 freesky-laptop dbus-daemon[627]: Successfully activated service 'org.freedesktop.Notifications'
янв 08 18:03:43 freesky-laptop dbus-daemon[627]: Successfully activated service 'org.gtk.vfs.Daemon'
янв 08 18:03:43 freesky-laptop systemd[581]: Started Virtual filesystem service.
янв 08 18:03:43 freesky-laptop dbus-daemon[627]: Activating service name='org.freedesktop.thumbnails.Thumbnailer1'
янв 08 18:03:44 freesky-laptop org.freedesktop.thumbnails.Thumbnailer1[627]: (tumblerd:684): tumbler-WARNING **: Failed to load plugin 
янв 08 18:03:44 freesky-laptop dbus-daemon[627]: Activating service name='org.a11y.Bus'
янв 08 18:03:44 freesky-laptop dbus-daemon[627]: Successfully activated service 'org.a11y.Bus'
янв 08 18:03:44 freesky-laptop org.a11y.Bus[627]: Activating service name='org.a11y.atspi.Registry'
янв 08 18:03:45 freesky-laptop org.a11y.Bus[627]: Successfully activated service 'org.a11y.atspi.Registry'
янв 08 18:03:45 freesky-laptop org.a11y.atspi.Registry[710]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Regist
янв 08 18:03:45 freesky-laptop org.freedesktop.thumbnails.Thumbnailer1[627]: (tumblerd:684): tumbler-WARNING **: Failed to load plugin 
янв 08 18:03:47 freesky-laptop dbus-daemon[627]: Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udi
янв 08 18:03:47 freesky-laptop systemd[581]: Starting Virtual filesystem service - disk device monitor...
янв 08 18:03:48 freesky-laptop dbus-daemon[627]: Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
янв 08 18:03:48 freesky-laptop systemd[581]: Started Virtual filesystem service - disk device monitor.
янв 08 18:03:49 freesky-laptop dbus-daemon[627]: Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
янв 08 18:03:50 freesky-laptop dbus-daemon[627]: Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.servic
янв 08 18:03:50 freesky-laptop systemd[581]: Starting Virtual filesystem metadata service...
янв 08 18:03:50 freesky-laptop dbus-daemon[627]: Successfully activated service 'org.gtk.vfs.Metadata'
янв 08 18:03:50 freesky-laptop systemd[581]: Started Virtual filesystem metadata service.
янв 08 18:03:51 freesky-laptop systemd[581]: Started Sound Service.
янв 08 18:04:48 freesky-laptop dbus-daemon[627]: Activating service name='org.gnome.GConf'
янв 08 18:04:48 freesky-laptop dbus-daemon[627]: Successfully activated service 'org.gnome.GConf'
янв 08 18:06:52 freesky-laptop org.freedesktop.thumbnails.Thumbnailer1[627]: (tumblerd:684): GVFS-RemoteVolumeMonitor-WARNING **: Owner
янв 08 18:06:52 freesky-laptop org.a11y.atspi.Registry[710]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0
янв 08 18:06:52 freesky-laptop org.a11y.atspi.Registry[710]: after 221 requests (221 known processed) with 0 events remaining.
янв 08 18:06:52 freesky-laptop org.freedesktop.Notifications[627]: xfce4-notifyd: Fatal IO error 11 (Ресурс временно недоступен) on X s
янв 08 18:06:52 freesky-laptop systemd[581]: Stopped target Default.
янв 08 18:06:52 freesky-laptop systemd[581]: Stopping D-Bus User Message Bus...
янв 08 18:06:52 freesky-laptop systemd[581]: Stopping Virtual filesystem metadata service...
янв 08 18:06:52 freesky-laptop systemd[581]: Stopping Virtual filesystem service...
янв 08 18:06:52 freesky-laptop systemd[581]: Stopping Sound Service...
янв 08 18:06:52 freesky-laptop systemd[581]: Stopped Virtual filesystem metadata service.
янв 08 18:06:52 freesky-laptop systemd[581]: Stopped Sound Service.
янв 08 18:06:52 freesky-laptop systemd[581]: Stopped Virtual filesystem service.
янв 08 18:06:53 freesky-laptop systemd[581]: Stopped D-Bus User Message Bus.
янв 08 18:06:53 freesky-laptop systemd[581]: Stopped target Basic System.
янв 08 18:06:53 freesky-laptop systemd[581]: Stopped target Timers.
янв 08 18:06:53 freesky-laptop systemd[581]: Stopped target Paths.
янв 08 18:06:53 freesky-laptop systemd[581]: Stopped target Sockets.
янв 08 18:06:53 freesky-laptop systemd[581]: Closed Sound System.
янв 08 18:06:53 freesky-laptop systemd[581]: Closed D-Bus User Message Bus Socket.
янв 08 18:06:53 freesky-laptop systemd[581]: Reached target Shutdown.
янв 08 18:06:53 freesky-laptop systemd[581]: Starting Exit the Session...
янв 08 18:06:53 freesky-laptop systemd[581]: Received SIGRTMIN+24 from PID 1130 (kill).
янв 08 18:06:53 freesky-laptop systemd[583]: pam_unix(systemd-user:session): session closed for user viktor

PS. After each forced-shutdown my /dev/sda2 partition (which corresponds to the / directory) gets corrupted and fsck checks it during the next boot-up

Offline

#7 2016-01-08 22:14:49

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,297

Re: [SOLVED] problems with Login Service on reboot or shutdown

@dviktor
Run the command as root to get the systemd system messages.

What you posted concerns only the systemd user manager.
But what imports is the systemd[1] lines of the system manager.

# journalctl -b -1 -e

or add the user to the systemd-journal group:

# gpasswd --add <user name> systemd-journal

After that, the user will see all the journal entries, not only the user journal.

Offline

#8 2016-01-09 01:08:43

dviktor
Member
From: Moscow
Registered: 2015-10-18
Posts: 155

Re: [SOLVED] problems with Login Service on reboot or shutdown

Now I'm in systemd-journal group. Log after forced-shutdown:

-- Logs begin at Вс 2015-09-27 21:50:59 MSK, end at Сб 2016-01-09 04:07:16 MSK. --
янв 09 04:03:02 freesky-laptop systemd[584]: Starting D-Bus User Message Bus Socket.
янв 09 04:03:02 freesky-laptop systemd[584]: Reached target Paths.
янв 09 04:03:02 freesky-laptop systemd[584]: Listening on Sound System.
янв 09 04:03:02 freesky-laptop systemd[584]: Reached target Timers.
янв 09 04:03:02 freesky-laptop systemd[584]: Listening on D-Bus User Message Bus Socket.
янв 09 04:03:02 freesky-laptop systemd[584]: Reached target Sockets.
янв 09 04:03:02 freesky-laptop systemd[584]: Reached target Basic System.
янв 09 04:03:02 freesky-laptop systemd[584]: Reached target Default.
янв 09 04:03:02 freesky-laptop systemd[584]: Startup finished in 160ms.
янв 09 04:03:07 freesky-laptop systemd[584]: Started D-Bus User Message Bus.
янв 09 04:03:07 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.freedesktop.systemd1'
янв 09 04:03:08 freesky-laptop dbus-daemon[629]: Activating service name='org.xfce.Xfconf'
янв 09 04:03:08 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.xfce.Xfconf'
янв 09 04:03:11 freesky-laptop dbus-daemon[629]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service'
янв 09 04:03:11 freesky-laptop systemd[584]: Starting Virtual filesystem service...
янв 09 04:03:12 freesky-laptop systemd[584]: Starting Sound Service...
янв 09 04:03:12 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.gtk.vfs.Daemon'
янв 09 04:03:12 freesky-laptop systemd[584]: Started Virtual filesystem service.
янв 09 04:03:13 freesky-laptop dbus-daemon[629]: Activating service name='org.a11y.Bus'
янв 09 04:03:13 freesky-laptop dbus-daemon[629]: Activating service name='org.freedesktop.Notifications'
янв 09 04:03:13 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.freedesktop.Notifications'
янв 09 04:03:13 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.a11y.Bus'
янв 09 04:03:13 freesky-laptop dbus-daemon[629]: Activating service name='org.freedesktop.thumbnails.Thumbnailer1'
янв 09 04:03:13 freesky-laptop org.a11y.Bus[629]: Activating service name='org.a11y.atspi.Registry'
янв 09 04:03:13 freesky-laptop org.freedesktop.thumbnails.Thumbnailer1[629]: (tumblerd:711): tumbler-WARNING **: Failed to load plugin "tumbler-raw-thumbnailer.so": libopenrawgnome.so.1: cannot open shared object file: No such file or directory
янв 09 04:03:14 freesky-laptop org.a11y.Bus[629]: Successfully activated service 'org.a11y.atspi.Registry'
янв 09 04:03:14 freesky-laptop org.a11y.atspi.Registry[709]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
янв 09 04:03:14 freesky-laptop org.freedesktop.thumbnails.Thumbnailer1[629]: (tumblerd:711): tumbler-WARNING **: Failed to load plugin "tumbler-ffmpeg-thumbnailer.so": libffmpegthumbnailer.so.4: cannot open shared object file: No such file or directory
янв 09 04:03:15 freesky-laptop dbus-daemon[629]: Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service'
янв 09 04:03:16 freesky-laptop systemd[584]: Starting Virtual filesystem service - disk device monitor...
янв 09 04:03:17 freesky-laptop systemd[584]: Started Virtual filesystem service - disk device monitor.
янв 09 04:03:17 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
янв 09 04:03:17 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
янв 09 04:03:19 freesky-laptop dbus-daemon[629]: Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service'
янв 09 04:03:19 freesky-laptop systemd[584]: Started Sound Service.
янв 09 04:03:19 freesky-laptop systemd[584]: Starting Virtual filesystem metadata service...
янв 09 04:03:19 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.gtk.vfs.Metadata'
янв 09 04:03:19 freesky-laptop systemd[584]: Started Virtual filesystem metadata service.
янв 09 04:03:40 freesky-laptop dbus-daemon[629]: Activating service name='org.gnome.GConf'
янв 09 04:03:40 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.gnome.GConf'
янв 09 04:04:29 freesky-laptop org.a11y.atspi.Registry[709]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
янв 09 04:04:29 freesky-laptop org.a11y.atspi.Registry[709]: after 201 requests (201 known processed) with 0 events remaining.
янв 09 04:04:29 freesky-laptop org.freedesktop.Notifications[629]: xfce4-notifyd: Fatal IO error 2 (Нет такого файла или каталога) on X server :0.
янв 09 04:04:34 freesky-laptop dbus-daemon[629]: Activating service name='org.freedesktop.Notifications'
янв 09 04:04:35 freesky-laptop dbus-daemon[629]: Successfully activated service 'org.freedesktop.Notifications'
янв 09 04:04:35 freesky-laptop org.a11y.Bus[629]: Activating service name='org.a11y.atspi.Registry'
янв 09 04:04:35 freesky-laptop org.a11y.Bus[629]: Successfully activated service 'org.a11y.atspi.Registry'
янв 09 04:04:35 freesky-laptop org.a11y.atspi.Registry[709]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
янв 09 04:05:25 freesky-laptop dbus-daemon[629]: Activating service name='ca.desrt.dconf'
янв 09 04:05:25 freesky-laptop dbus-daemon[629]: Successfully activated service 'ca.desrt.dconf'
янв 09 04:05:57 freesky-laptop org.a11y.atspi.Registry[709]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"

Offline

#9 2016-01-09 10:05:09

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,297

Re: [SOLVED] problems with Login Service on reboot or shutdown

This can't be the real shutdown sequence from the journal...

Systemd system messages are lines with systemd[1] ie process ID 1 (init process).
These lines should be in the journal.

It's the third times I mention the systemd[1] term in my answers;
so this will be the last times I try to help you on this matter, if you don't show the real content of the journal. Sorry.

Offline

#10 2016-01-09 19:39:09

dviktor
Member
From: Moscow
Registered: 2015-10-18
Posts: 155

Re: [SOLVED] problems with Login Service on reboot or shutdown

excuse me, there was a problem with corrupted journals on my laptop. I've cleaned all old journals. Now I have this.
The only thing with systemd[1] which related to the shutdown process is:

янв 09 22:27:32 freesky-laptop systemd-logind[461]: System is powering down.
янв 09 22:27:32 freesky-laptop systemd[1]: Stopping Authorization Manager...
-- Reboot --

Offline

#11 2016-01-09 22:42:44

berbae
Member
From: France
Registered: 2007-02-12
Posts: 1,297

Re: [SOLVED] problems with Login Service on reboot or shutdown

What command exactly did you run to shutdown?

I have much more lines in my journal describing the shutdown sequence.
Here is just the beginning and the end of it:

janv. 08 23:33:22 arch64 systemd-logind[269]: System is powering down.
janv. 08 23:33:22 arch64 systemd[1]: Deactivating swap /dev/sda2...
janv. 08 23:33:22 arch64 systemd[1]: Stopped target Multi-User System.
janv. 08 23:33:22 arch64 systemd[1]: Stopped target Sound Card.
janv. 08 23:33:22 arch64 systemd[1]: Stopped target Timers.
janv. 08 23:33:22 arch64 systemd[1]: Stopped Daily man-db cache update.
janv. 08 23:33:22 arch64 systemd[1]: Stopping Save/Restore Sound Card State...
janv. 08 23:33:22 arch64 systemd[1]: Stopping Daemon for power management...
janv. 08 23:33:22 arch64 systemd[1]: Starting Generate shutdown-ramfs...
janv. 08 23:33:22 arch64 systemd[1]: Stopping Initialize hardware monitoring sensors...
janv. 08 23:33:22 arch64 systemd[1]: Stopped Daily verification of password and group files.
janv. 08 23:33:22 arch64 systemd[1]: Stopped Daily Cleanup of Temporary Directories.
janv. 08 23:33:22 arch64 systemd[1]: Stopping Session c1 of user berbae.
janv. 08 23:33:22 arch64 systemd[1]: Stopped Daily locate database update.
janv. 08 23:33:22 arch64 systemd[1]: Stopping Authorization Manager...
janv. 08 23:33:22 arch64 systemd[1]: Stopping User Manager for UID 1000...
janv. 08 23:33:22 arch64 systemd[1]: Stopping Disk Manager...
janv. 08 23:33:22 arch64 systemd[1]: Stopping Network Name Resolution...
janv. 08 23:33:22 arch64 systemd[1]: Stopped Timer for Restore Again Sound Card State.
janv. 08 23:33:22 arch64 systemd[1]: Stopped target Login Prompts.
janv. 08 23:33:22 arch64 systemd[1]: Stopping Getty on tty1...
janv. 08 23:33:22 arch64 systemd[1]: Stopping Shorewall IPv4 firewall...
janv. 08 23:33:22 arch64 systemd[1]: Stopped Daily rotation of log files.
janv. 08 23:33:22 arch64 systemd[1]: Stopped target System Time Synchronized.
janv. 08 23:33:22 arch64 systemd[1]: Stopped Network Name Resolution.
janv. 08 23:33:22 arch64 systemd[1]: Stopped Disk Manager.
janv. 08 23:33:22 arch64 systemd[1]: Stopped Authorization Manager.
janv. 08 23:33:22 arch64 systemd[1]: Stopped Daemon for power management.
janv. 08 23:33:22 arch64 systemd[1]: Stopped Save/Restore Sound Card State.
...
many other entries which I cut
...
janv. 08 23:33:23 arch64 systemd[1]: Unmounting /home...
janv. 08 23:33:23 arch64 systemd[1]: Unmounting /opt...
janv. 08 23:33:23 arch64 systemd[1]: Unmounting /run/user/1000...
janv. 08 23:33:23 arch64 systemd[1]: Unmounting /boot...
janv. 08 23:33:23 arch64 systemd[1]: Unmounting Temporary Directory...
janv. 08 23:33:23 arch64 systemd[1]: Unmounted /run/user/1000.
janv. 08 23:33:23 arch64 systemd[1]: Unmounted Temporary Directory.
janv. 08 23:33:23 arch64 systemd[1]: Unmounted /boot.
janv. 08 23:33:23 arch64 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/d267dfa5-9544-4e3d-981f-0f7e0e8053fc.
janv. 08 23:33:23 arch64 systemd[1]: Unmounted /opt.
janv. 08 23:33:23 arch64 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/ccb81b06-8bbe-4c3e-bd3c-10203298e5f7.
janv. 08 23:33:23 arch64 systemd[1]: Unmounted /home.
janv. 08 23:33:23 arch64 systemd[1]: Reached target Unmount All Filesystems.
janv. 08 23:33:23 arch64 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/1b9df96b-c0a6-4b4d-9f50-f843d2152a3e.
janv. 08 23:33:23 arch64 systemd[1]: Removed slice system-systemd\x2dfsck.slice.
janv. 08 23:33:23 arch64 systemd[1]: Stopped target Local File Systems (Pre).
janv. 08 23:33:23 arch64 systemd[1]: Stopped Create Static Device Nodes in /dev.
janv. 08 23:33:23 arch64 systemd[1]: Stopped Remount Root and Kernel File Systems.
janv. 08 23:33:23 arch64 systemd[1]: Reached target Shutdown.
janv. 08 23:33:23 arch64 systemd[1]: Reached target Final Step.
janv. 08 23:33:23 arch64 systemd[1]: Starting Power-Off...
janv. 08 23:33:23 arch64 systemd[1]: Shutting down.
janv. 08 23:33:23 arch64 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
janv. 08 23:33:23 arch64 systemd-journald[163]: Journal stopped

Can you describe exactly what you did at these points:

янв 09 22:27:32 freesky-laptop systemd[1]: Stopping Authorization Manager...
-- Reboot --
янв 09 22:28:18 freesky-laptop systemd-journald[213]: Runtime journal (/run/log/journal/) is currently using 8.0M.

There are only 46 seconds before the next reboot...
Did you forced power off the machine too quickly, and immediately rebooted it?
This doesn't seem good for your system.

Offline

#12 2016-01-10 00:22:37

dviktor
Member
From: Moscow
Registered: 2015-10-18
Posts: 155

Re: [SOLVED] problems with Login Service on reboot or shutdown

Usually I click shutdown button in XFCE menu (but I've checked - shutdown command invoked in the xfce4-terminal leads to the same effect) to power off my laptop. After that X stops, screen blanks and annoying message with "A stop job..." appears at the top left corner of the screen. I tried to wait but even after 5 mins laptop hasn't became shut down. Then I press power button and hold it until laptop becomes power off state. I think that "Stopping Authorization Manager..." is reffered to the processes I've described above.

If I first log out from xfce session then log in at tty2 and finally hit shutdown command all works like a charm.

I have no idea why my journal has so little messages from systemd[1] process. I've completely stuck on this.

PS: reboot works fine both ways (XFCE menu and tty2)

PPS: Breaking news. Previously boot always worked fine but now I'm experiencing the same problems as with shutdown. Now I decided to wait a bit more while "A stop job is running...". After some timeout periods this message disappeared and a log of shutdown was shown on the screen. Some messages were related to the ata but reboot didn't happened. So I manually powered down laptop. After reboot /dev/sda2 (which is correspond to the / mount point) was marked clean! (usually after forced-shutdown /dev/sda2 is always unclean and fsck check runs). Some logs are here

PPPS: I've captured some messages that are not present in journal (they appears after "A stop job..." message):

shutdown[1] failed to finalize file systems
--here strings with ata3.00 keyword--
ata3.00: revalidation failed errno=-5

PPPPS: filed a bug

Last edited by dviktor (2016-01-13 06:34:50)

Offline

#13 2016-01-13 12:40:21

archpen
Member
From: wuhan-China
Registered: 2015-12-31
Posts: 4
Website

Re: [SOLVED] problems with Login Service on reboot or shutdown

Are you sloved it? I meet the same before this days .
My way is  sudo vim the ~/.xinitrc ,and keep it become this:
export LANG=zh_CN.UTF-8
export LC_ALL=”zh_CN.UTF-8″
export GTK_IM_MODULE=fcitx
export QT_IM_MODULE=fcitx
export XMODIFIERS=”@im=fcitx”
exec startxfce4
then it reboot ,and xfce4 become run successful !
but you can only add exec startxfce4,  because I use Chinese .
it maybe run ,you try ,


One man's meat is another man's poison.                            ----From my laptop:Dell inspiron15-3542.,1.4Ghz,  win8.1+archlinux

Offline

#14 2016-01-13 16:35:37

dviktor
Member
From: Moscow
Registered: 2015-10-18
Posts: 155

Re: [SOLVED] problems with Login Service on reboot or shutdown

my .xinitrc

I think the problem isn't related to the .xinitrc. Moreover as I noticed this bug appeared after kernel update to 4.3.3-2 version...
Now I have only dirty workaround, not real solution:

1) log out from xfce session
2) log in to the tty2 or any other without starting X
3) manually shutdown or reboot

Offline

#15 2016-01-14 17:24:34

Vyre
Member
Registered: 2011-06-18
Posts: 16

Re: [SOLVED] problems with Login Service on reboot or shutdown

I want to avoid a new thread if possible, and I think I may be having the same or a similar issue, though it manifests a bit differently.

When I leave my computer idle for a while, I've noticed recently that it frequently closes and logs out of my LXDM/XFCE session.  This is really frustrating, as I lose my desktop state.  When I check journalctl I get messages similar to the following:

Jan 13 22:19:21 siona org.a11y.atspi.Registry[545]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jan 13 22:19:21 siona org.a11y.atspi.Registry[545]: after 1645 requests (1645 known processed) with 0 events remaining.
Jan 13 22:19:21 siona polkitd[474]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.11, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Jan 13 22:19:21 siona lxdm-session[450]: pam_unix(lxdm:session): session closed for user ajacobs
Jan 13 22:19:21 siona kernel: traps: xfsettingsd[2208] trap int3 ip:7fcf0d9b464b sp:7ffc9b034c90 error:0
Jan 13 22:19:21 siona systemd-coredump[2209]: Process 2208 (xfsettingsd) of user 1000 dumped core.
                                             
                                              Stack trace of thread 2208:
                                              #0  0x00007fcf0d9b464b g_logv (libglib-2.0.so.0)
                                              #1  0x00007fcf0d9b47bf g_log (libglib-2.0.so.0)
                                              #2  0x0000000000406f1c n/a (xfsettingsd)
                                              #3  0x00007fcf0cc7b610 __libc_start_main (libc.so.6)
                                              #4  0x0000000000407259 n/a (xfsettingsd)
Jan 13 22:19:21 siona systemd-logind[234]: Removed session c1.
Jan 13 22:19:21 siona systemd[1]: Stopping User Manager for UID 1000...
Jan 13 22:19:21 siona systemd[451]: Stopping D-Bus User Message Bus...
Jan 13 22:19:21 siona systemd[451]: Stopped target Default.
Jan 13 22:19:21 siona systemd[451]: Stopped D-Bus User Message Bus.
Jan 13 22:19:21 siona systemd[451]: Stopped target Basic System.
Jan 13 22:19:21 siona systemd[451]: Stopped target Paths.
Jan 13 22:19:21 siona systemd[451]: Stopped target Timers.
Jan 13 22:19:21 siona systemd[451]: Stopped target Sockets.
Jan 13 22:19:21 siona systemd[451]: Closed D-Bus User Message Bus Socket.
Jan 13 22:19:21 siona systemd[451]: Reached target Shutdown.
Jan 13 22:19:21 siona systemd[451]: Starting Exit the Session...
Jan 13 22:19:21 siona systemd[451]: Received SIGRTMIN+24 from PID 2216 (kill).
Jan 13 22:19:21 siona systemd[452]: pam_unix(systemd-user:session): session closed for user ajacobs
Jan 13 22:19:21 siona systemd[1]: Stopped User Manager for UID 1000.
Jan 13 22:19:21 siona systemd[1]: Removed slice User Slice of ajacobs.

Any ideas of what's going on here?  Initially, this seemed to always coincide with a pulseaudio error, but I removed pulseaudio and still have it happen, so I think it's something deeper.

Offline

#16 2016-02-02 08:50:07

dviktor
Member
From: Moscow
Registered: 2015-10-18
Posts: 155

Re: [SOLVED] problems with Login Service on reboot or shutdown

The problem is solved with the 4.1.16-1-lts kernel. I'll mark thread as solved
EDIT: kernel 4.4.1-1 also solves this problem

Last edited by dviktor (2016-02-03 10:15:09)

Offline

Board footer

Powered by FluxBB