New kernel 4.4.1-1 solves the issue!
for me the problem still exists and I continue using linux-lts 4.1.17-1
]]>If shutdown (whether it be to reboot or power-off) of your system gets stuck, first test if the kernel itself is able to reboot or power-off the machine forcedly using one of these commands
sync && reboot -f sync && poweroff -f
If either one of the commands does not work, it is a kernel bug, not systemd.
But we are mentioned already that shutdown/reboot works fine when launched from tty2 or another tty and only fails when run somehow via desktop environment. So it's not a kernel bug...
PS: commands work but after boot I've met unclean disk partitions and fsck...
PPS: filed a bug
EDIT: the problem is solved with the 4.1.16-1-lts kernel
If shutdown (whether it be to reboot or power-off) of your system gets stuck, first test if the kernel itself is able to reboot or power-off the machine forcedly using one of these commands
sync && reboot -f sync && poweroff -f
If either one of the commands does not work, it is a kernel bug, not systemd.
But we are mentioned already that shutdown/reboot works fine when launched from tty2 or another tty and only fails when run somehow via desktop environment. So it's not a kernel bug...
PS: commands work but after boot I've met unclean disk partitions and fsck...
PPS: filed a bug
EDIT: the problem is solved with the 4.1.16-1-lts kernel
]]>sync && reboot -f
sync && poweroff -f
dviktor wrote:Has the problem gone permanently after this combination or only for single reboot?
this problem gone permanently.
acutally it is not really solve it.
I mean it works this moring, I reboot 3 times.
however, it does not work now, laptop still canot be rebooted
]]>Has the problem gone permanently after this combination or only for single reboot?
this problem gone permanently.
]]>The dirty work-around is to log out from DE, log in to the tty2 (or anything else without starting X again) and then manually
shutdown now
or
reboot
thank you very much!
it is working.
systemctl isolate multi-users.target
reboot
then this problem was gone.
I still have a question, why it works?
]]>shutdown now
or
reboot
seems like I'm experiencing the same problem!
you are right, so what is the solution?
]]>I am facing with the same problem since few days: "A stop job is running for Login Service" when I try to poweroff or reboot (from command line, I do not use any GUI to poweroff/reboot)
here is the output for loginctl session-status
c1 - troncy_l (1000)
Since: Sun 2016-01-10 23:15:57 UTC; 8min ago
Leader: 289 (login)
Seat: seat0; vc1
TTY: tty1
Service: login; type tty; class user
State: active
Unit: session-c1.scope
├─ 289 login -- troncy_l
├─ 507 /bin/sh /usr/bin/startx
├─ 545 xinit /home/troncy_l/.xinitrc -- /etc/X11/xinit/xserverrc :0 vt1 -auth /tmp/serverauth.qkxuqjMFCH
├─ 546 /usr/lib/xorg-server/Xorg -nolisten tcp :0 vt1 -auth /tmp/serverauth.qkxuqjMFCH
├─ 552 i3
├─ 561 i3bar --bar_id=bar-0 --socket=/run/user/1000/i3/ipc-socket.552
├─ 562 i3status
├─ 577 urxvt
├─ 578 zsh
├─ 602 /usr/bin/zsh
├─ 605 /opt/google/chrome/chrome
├─ 612 cat
├─ 613 cat
├─ 618 /opt/google/chrome/chrome-sandbox /opt/google/chrome/chrome --type=zygote
├─ 619 /opt/google/chrome/chrome --type=zygote
├─ 621 /opt/google/chrome/chrome-sandbox /opt/google/chrome/nacl_helper
├─ 622 /opt/google/chrome/nacl_helper
├─ 624 /opt/google/chrome/chrome --type=zygote
├─ 748 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AffiliationBasedMatching/EnabledThroughFieldTrial/AppBannerTriggering/Aggressive/CaptiveP$
├─ 753 /proc/self/exe --type=gpu-process --channel=605.2.1035391618 --supports-dual-gpus=false --gpu-driver-bug-workarounds=2,3,18,25,33,47,51,63 --disable-accelerated-vid$
├─ 756 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AffiliationBasedMatching/EnabledThroughFieldTrial/AppBannerTriggering/Aggressive/CaptiveP$
├─ 808 /proc/self/exe --type=gpu-process --channel=605.2.1035391618 --supports-dual-gpus=false --gpu-driver-bug-workarounds=2,3,18,25,33,47,51,63 --disable-accelerated-vid$
├─ 972 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AffiliationBasedMatching/EnabledThroughFieldTrial/AppBannerTriggering/Aggressive/CaptiveP$
├─1000 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AffiliationBasedMatching/EnabledThroughFieldTrial/AppBannerTriggering/Aggressive/CaptiveP$
├─1235 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=AffiliationBasedMatching/EnabledThroughFieldTrial/AppBannerTriggering/Aggressive/CaptiveP$
├─1489 loginctl session-status
└─1490 most
I use i3wm.
Thank you.