Shutdown/Reboot infinite hanging

SeaIsland · 2016-01-04 04:40:31

Hello.

Recently i have been getting hangs when rebooting/shutting down.

I have just reinstalled Arch, but the problem is still happening.

When i poweroff or reboot, units seem to shutdown as normal until it hangs on.

A stop job is running for logind.service

This hangs forever unless i ctrl+d/ctrl+c. That makes it wait for about a minute or so, and then says that it failed. After that, all of the remaining units shutdown normally, but when it gets to the end it says something along the lines of:

Shutdown failed. Ignored

That is not the exact error, but it is something similar to that.

After that happens, it still hangs, nothing i do can get me out of it other than manually holding the power button for 5 seconds.

Some errors in my log that seem related are:

Jan 03 21:37:49 sea systemd[1]: systemd-logind.service: Processes still around after SIGKILL. Ignoring.
Jan 03 21:39:19 sea systemd[1]: systemd-logind.service: State 'stop-final-sigterm' timed out. Killing.
Jan 03 21:39:40 sea kernel: INFO: task systemd-logind:352 blocked for more than 120 seconds.
Jan 03 21:39:40 sea kernel:       Not tainted 4.3.3-2-ARCH #1
Jan 03 21:39:40 sea kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

This problem is really making things hard for me, and I am unsure of what i should do. I would seriously appreciate anyone's help. If any more information could be useful, please let me know.

likeahundredninjas · 2016-01-04 05:05:54

sounds like maybe your shell?

SeaIsland · 2016-01-04 05:20:47

likeahundredninjas wrote:

sounds like maybe your shell?

Sorry, I'm not entirely sure what you mean by that.

I use zsh, but i don't know what about it could be causing this.

topquark · 2016-01-05 04:15:52

I'm having the same issue, systemd-logind seems to be causing my system to hang when shutting down or rebooting. After doing a little testing, it seems the issue only occurs when I log into a standard gnome-shell session from gdm. Disabling gdm and booting into a TTY allows the system to shut down properly. In addition, logging into a Wayland gnome-shell session also allows the system to shut down properly.

SeaIsland · 2016-01-05 15:45:05

topquark wrote:

I'm having the same issue, systemd-logind seems to be causing my system to hang when shutting down or rebooting. After doing a little testing, it seems the issue only occurs when I log into a standard gnome-shell session from gdm. Disabling gdm and booting into a TTY allows the system to shut down properly. In addition, logging into a Wayland gnome-shell session also allows the system to shut down properly.

I don't use Gnome, although that is strange how that fix worked out for you.

I'm kind of losing hope, this is still happening, and i just don't know how to fix it.

dude42 · 2016-01-05 22:28:32

I'm having the same issue. I use gnome without GDM. I log into a TTY and type startx. The strange thing is: It only happens on my laptop, not my desktop, and the two installations are nearly identical.

SeaIsland · 2016-01-05 23:58:18

dude42 wrote:

I'm having the same issue. I use gnome without GDM. I log into a TTY and type startx. The strange thing is: It only happens on my laptop, not my desktop, and the two installations are nearly identical.

I'm on a laptop too.

One thing i should clarify is that I'm just running a minimal installation, both of the times i reinstalled. I3wm, zsh, and around 500 packages.

I really wonder what in particular could be making the shutdown fail. I'm looking at some older threads to see the problems they have in common, but so far I'm not seeing much.

I saw in another thread someone mentioned they thought it could be video card related. I don't know how, but here is my output of lspci

00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)

dude42 · 2016-01-06 10:20:12

I have 2:

00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff)

My journalctl shows the following for the previous boot, although the radeon errors - VCE init error (-110) - have been there since I can remember:

kernel: ACPI: RSDP 0x00000000C8FD3000 000024 (v02 DELL  )
kernel: ACPI: XSDT 0x00000000C8FD3098 0000AC (v01 DELL   CBX3     01072009
kernel: ACPI: FACP 0x00000000C8FE4AE0 00010C (v05 DELL   CBX3     01072009
kernel: ACPI: DSDT 0x00000000C8FD31D0 01190D (v02 DELL   CBX3     00000014
kernel: ACPI: FACS 0x00000000CA7FE080 000040
kernel: ACPI: APIC 0x00000000C8FE4BF0 000092 (v03 DELL   CBX3     01072009
kernel: ACPI: FPDT 0x00000000C8FE4C88 000044 (v01 DELL   CBX3     01072009
kernel: ACPI: SLIC 0x00000000C8FE4CD0 000176 (v03 DELL   CBX3     01072009
kernel: ACPI: LPIT 0x00000000C8FE4E48 00005C (v01 DELL   CBX3     00000000
kernel: ACPI: SSDT 0x00000000C8FE4EA8 000228 (v01 INTEL  sensrhub 00000000 INTL 20120711)
kernel: ACPI: SSDT 0x00000000C8FE50D0 000160 (v01 Intel  zpodd    00001000 INTL 20120711)
kernel: ACPI: SSDT 0x00000000C8FE5230 00051F (v01 PmRef  Cpu0Ist  00003000 INTL 20120711)
kernel: ACPI: SSDT 0x00000000C8FE5750 000AD8 (v01 PmRef  CpuPm    00003000 INTL 20120711)
kernel: ACPI: HPET 0x00000000C8FE6228 000038 (v01 DELL   CBX3     01072009
kernel: ACPI: SSDT 0x00000000C8FE6260 0003D2 (v01 SataRe SataTabl 00001000 INTL 20120711)
kernel: ACPI: MCFG 0x00000000C8FE6638 00003C (v01 DELL   CBX3     01072009
kernel: ACPI: SSDT 0x00000000C8FE6678 001044 (v01 SgRef  SgPeg    00001000 INTL 20120711)
kernel: ACPI: ASF! 0x00000000C8FE76C0 0000A5 (v32 INTEL   HCG     00000001
kernel: [81B blob data]
kernel: ACPI: DMAR 0x00000000C8FE77A0 0000B8 (v01 INTEL  HSW      00000001
kernel: ACPI: SSDT 0x00000000C8FE7858 001093 (v01 AmdRef AmdTabl  00001000 INTL 20120711)
kernel: ACPI: 8 ACPI AML tables successfully acquired and loaded
kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
kernel: Ignoring BGRT: invalid status 0 (expected 1)
kernel:  #2 #3 #4 #5 #6 #7
kernel: pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
kernel: ACPI: Executed 2 blocks of module-level executable AML code
kernel: ACPI: Dynamic OEM Table Load:
kernel: ACPI: SSDT 0xFFFF88041BE5BC00 0003D3 (v01 PmRef  Cpu0Cst  00003001 INTL 20120711)
kernel: ACPI: Dynamic OEM Table Load:
kernel: ACPI: SSDT 0xFFFF88041BE62800 0005AA (v01 PmRef  ApIst    00003000 INTL 20120711)
kernel: ACPI: Dynamic OEM Table Load:
kernel: ACPI: SSDT 0xFFFF88041BEC1C00 000119 (v01 PmRef  ApCst    00003000 INTL 20120711)
kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150818/hwxface-580)
kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150818/hwxface-580)
kernel: ACPI: Enabled 2 GPEs in block 00 to 3F
kernel: i8042: Warning: Keylock active
kernel: mmc0: Unknown controller version (3). You may experience problems.
kernel: usb 3-10: config 1 has an invalid interface number: 8 but max is 3
kernel: usb 3-10: config 1 has no interface number 1
systemd[1]: display-manager.service: Cannot add dependency job, ignoring: Unit display-manager.service failed to load: No such file
kernel: VBoxNetAdp: Successfully started.
kernel: VBoxNetFlt: Successfully started.
kernel: VBoxPciLinuxInit
kernel: ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB_.PCI0.SBUS.SMBI) (20150818/utaddress-254)
kernel: CRAT table not found
kernel: [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
kernel: ATPX version 1, functions 0x00000033
systemd-udevd[385]: Error calling EVIOCSKEYCODE on device node '/dev/input/event15' (scan code 0x150, key code 190): Invalid
systemd-udevd[359]: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
systemd-udevd[360]: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
kernel: radeon 0000:01:00.0: VCE init error (-110).
avahi-daemon[680]: socket() failed: Address family not supported by protocol
avahi-daemon[680]: socket() failed: Address family not supported by protocol
NetworkManager[678]: <error> [1452073802.347399] [devices/nm-device.c:4905] addrconf6_start(): (wlp3s0): failed to start router discovery (wlp3s0)
kernel: radeon 0000:01:00.0: VCE init error (-110).
org.a11y.Bus[871]: Activating service name='org.a11y.atspi.Registry'
org.a11y.Bus[871]: Successfully activated service 'org.a11y.atspi.Registry'
org.gnome.OnlineAccounts[871]: goa-daemon-Message: goa-daemon version 3.18.2.1 starting
org.gnome.zeitgeist.Engine[871]: ** (zeitgeist-datahub:1107): WARNING **: zeitgeist-datahub.vala:226: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
gnome-session-binary[867]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gnome-session-binary[867]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gnome-session-binary[867]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gnome-session-binary[867]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gnome-session-binary[867]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gnome-session-binary[867]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gnome-session-binary[867]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gnome-session-binary[867]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
gnome-session-binary[867]: WARNING: Lost name on bus: org.gnome.SessionManager
avahi-daemon[680]: Disconnected from D-Bus, exiting.
NetworkManager[678]: <warn>  error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (0) Authorization check failed: The connection is
NetworkManager[678]: <warn>  error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (0) Authorization check failed: The connection is
systemd[824]: ssh-agent.service: Failed with result 'exit-code'.
systemd-logind[681]: Failed to abandon session scope: Connection reset by peer
systemd[1]: upower.service: Failed with result 'exit-code'.
org.gnome.zeitgeist.SimpleIndexer[871]: (zeitgeist-fts:1105): GLib-GIO-WARNING **: Error releasing name org.gnome.zeitgeist.SimpleIndexer: The connection is closed
org.gnome.zeitgeist.SimpleIndexer[871]: ** (zeitgeist-fts:1105): WARNING **: zeitgeist-fts.vala:252: The connection is closed
org.gnome.zeitgeist.Engine[871]: (zeitgeist-daemon:1063): GLib-GObject-CRITICAL **: g_object_unref: assertion 'object->ref_count > 0' failed
org.gnome.zeitgeist.Engine[871]: [09:50:33.225661 WARNING] zeitgeist-daemon.vala:449: The connection is closed
systemd[1]: session-c1.scope: Stopping timed out. Killing.
kernel: radeon 0000:01:00.0: VCE init error (-110).
systemd[1]: systemd-logind.service: State 'stop-sigterm' timed out. Killing.
systemd[1]: systemd-logind.service: Processes still around after SIGKILL. Ignoring.
kernel: INFO: task systemd-logind:681 blocked for more than 120 seconds.
kernel:       Tainted: G      
kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kernel:  ffff8804128e37b8 0000000000000046 ffffffff81812500 ffff88041b24a940
kernel:  ffff8804128e4000 ffff88041bd4e20c ffff88041b24a940 00000000ffffffff
kernel:  ffff88041bd4e210 ffff8804128e37d0 ffffffff8158028a ffff88041bd4e208
kernel: Call Trace:
kernel:  [<ffffffff8158028a>] schedule+0x3a/0x90
kernel:  [<ffffffff81580675>] schedule_preempt_disabled+0x15/0x20
kernel:  [<ffffffff81581abe>] __mutex_lock_slowpath+0xce/0x140
kernel:  [<ffffffff81581b47>] mutex_lock+0x17/0x30
kernel:  [<ffffffffa0702e8e>] drm_kms_helper_poll_enable+0x1e/0x40 [drm_kms_helper]
kernel:  [<ffffffffa0ae1911>] radeon_resume_kms+0x211/0x3c0 [radeon]
kernel:  [<ffffffffa0adf13f>] radeon_pmops_runtime_resume+0x6f/0xa0 [radeon]
kernel:  [<ffffffff81305deb>] pci_pm_runtime_resume+0x7b/0xa0
kernel:  [<ffffffff813d7bf0>] ? vga_switcheroo_runtime_suspend+0x50/0x50
kernel:  [<ffffffff813d7c25>] vga_switcheroo_runtime_resume+0x35/0x40
kernel:  [<ffffffff813e96d2>] __rpm_callback+0x32/0x70
kernel:  [<ffffffff813d7bf0>] ? vga_switcheroo_runtime_suspend+0x50/0x50
kernel:  [<ffffffff813e9734>] rpm_callback+0x24/0x80
kernel:  [<ffffffff813d7bf0>] ? vga_switcheroo_runtime_suspend+0x50/0x50
kernel:  [<ffffffff813eaa40>] rpm_resume+0x490/0x690
kernel:  [<ffffffff811bba97>] ? kfree+0x147/0x150
kernel:  [<ffffffff813eac7f>] __pm_runtime_resume+0x3f/0x60
kernel:  [<ffffffffa0b091f8>] radeon_crtc_set_config+0x38/0x110 [radeon]
kernel:  [<ffffffffa059a642>] drm_mode_set_config_internal+0x62/0x100 [drm]
kernel:  [<ffffffffa070ca23>] restore_fbdev_mode+0xb3/0x110 [drm_kms_helper]
kernel:  [<ffffffffa070e9b5>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
kernel:  [<ffffffffa0b1109a>] radeon_fbdev_restore_mode+0x1a/0x40 [radeon]
kernel:  [<ffffffffa0ae3a92>] radeon_driver_lastclose_kms+0x12/0x20 [radeon]
kernel:  [<ffffffffa058ea2e>] drm_lastclose+0x2e/0x140 [drm]
kernel:  [<ffffffffa058ee56>] drm_release+0x316/0x500 [drm]
kernel:  [<ffffffff811db2fc>] __fput+0x9c/0x1f0
kernel:  [<ffffffff811db48e>] ____fput+0xe/0x10
kernel:  [<ffffffff81091173>] task_work_run+0x73/0x90
kernel:  [<ffffffff81077c85>] do_exit+0x395/0xb40
kernel:  [<ffffffff810b5c90>] ? __wake_up_sync_key+0x50/0x60
kernel:  [<ffffffff810784ab>] do_group_exit+0x3b/0xb0
kernel:  [<ffffffff8108340c>] get_signal+0x23c/0x630
kernel:  [<ffffffff81016297>] do_signal+0x37/0x6a0
kernel:  [<ffffffff810aa735>] ? put_prev_entity+0x35/0x7f0
kernel:  [<ffffffff8101fd79>] ? sched_clock+0x9/0x10
kernel:  [<ffffffff81221632>] ? signalfd_poll+0xb2/0xc0
kernel:  [<ffffffff8121f080>] ? ep_send_events_proc+0xb0/0x1c0
kernel:  [<ffffffff8121efd0>] ? ep_read_events_proc+0xd0/0xd0
kernel:  [<ffffffff8121f898>] ? ep_scan_ready_list+0x1c8/0x1d0
kernel:  [<ffffffff810039dd>] prepare_exit_to_usermode+0xbd/0x100
kernel:  [<ffffffff81003aed>] syscall_return_slowpath+0xcd/0x1d0
kernel:  [<ffffffff8109e150>] ? wake_up_q+0x60/0x60
kernel:  [<ffffffff81221075>] ? SyS_epoll_wait+0xb5/0xd0
kernel:  [<ffffffff81583e8c>] int_ret_from_sys_call+0x25/0x8f
systemd[1]: systemd-logind.service: State 'stop-final-sigterm' timed out. Killing.
kernel: INFO: task systemd-logind:681 blocked for more than 120 seconds.
kernel:       Tainted: G      
kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kernel:  ffff8804128e37b8 0000000000000046 ffffffff81812500 ffff88041b24a940
kernel:  ffff8804128e4000 ffff88041bd4e20c ffff88041b24a940 00000000ffffffff
kernel:  ffff88041bd4e210 ffff8804128e37d0 ffffffff8158028a ffff88041bd4e208
kernel: Call Trace:
kernel:  [<ffffffff8158028a>] schedule+0x3a/0x90
kernel:  [<ffffffff81580675>] schedule_preempt_disabled+0x15/0x20
kernel:  [<ffffffff81581abe>] __mutex_lock_slowpath+0xce/0x140
kernel:  [<ffffffff81581b47>] mutex_lock+0x17/0x30
kernel:  [<ffffffffa0702e8e>] drm_kms_helper_poll_enable+0x1e/0x40 [drm_kms_helper]
kernel:  [<ffffffffa0ae1911>] radeon_resume_kms+0x211/0x3c0 [radeon]
kernel:  [<ffffffffa0adf13f>] radeon_pmops_runtime_resume+0x6f/0xa0 [radeon]
kernel:  [<ffffffff81305deb>] pci_pm_runtime_resume+0x7b/0xa0
kernel:  [<ffffffff813d7bf0>] ? vga_switcheroo_runtime_suspend+0x50/0x50
kernel:  [<ffffffff813d7c25>] vga_switcheroo_runtime_resume+0x35/0x40
kernel:  [<ffffffff813e96d2>] __rpm_callback+0x32/0x70
kernel:  [<ffffffff813d7bf0>] ? vga_switcheroo_runtime_suspend+0x50/0x50
kernel:  [<ffffffff813e9734>] rpm_callback+0x24/0x80
kernel:  [<ffffffff813d7bf0>] ? vga_switcheroo_runtime_suspend+0x50/0x50
kernel:  [<ffffffff813eaa40>] rpm_resume+0x490/0x690
kernel:  [<ffffffff811bba97>] ? kfree+0x147/0x150
kernel:  [<ffffffff813eac7f>] __pm_runtime_resume+0x3f/0x60
kernel:  [<ffffffffa0b091f8>] radeon_crtc_set_config+0x38/0x110 [radeon]
kernel:  [<ffffffffa059a642>] drm_mode_set_config_internal+0x62/0x100 [drm]
kernel:  [<ffffffffa070ca23>] restore_fbdev_mode+0xb3/0x110 [drm_kms_helper]
kernel:  [<ffffffffa070e9b5>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
kernel:  [<ffffffffa0b1109a>] radeon_fbdev_restore_mode+0x1a/0x40 [radeon]
kernel:  [<ffffffffa0ae3a92>] radeon_driver_lastclose_kms+0x12/0x20 [radeon]
kernel:  [<ffffffffa058ea2e>] drm_lastclose+0x2e/0x140 [drm]
kernel:  [<ffffffffa058ee56>] drm_release+0x316/0x500 [drm]
kernel:  [<ffffffff811db2fc>] __fput+0x9c/0x1f0
kernel:  [<ffffffff811db48e>] ____fput+0xe/0x10
kernel:  [<ffffffff81091173>] task_work_run+0x73/0x90
kernel:  [<ffffffff81077c85>] do_exit+0x395/0xb40
kernel:  [<ffffffff810b5c90>] ? __wake_up_sync_key+0x50/0x60
kernel:  [<ffffffff810784ab>] do_group_exit+0x3b/0xb0
kernel:  [<ffffffff8108340c>] get_signal+0x23c/0x630
kernel:  [<ffffffff81016297>] do_signal+0x37/0x6a0
kernel:  [<ffffffff810aa735>] ? put_prev_entity+0x35/0x7f0
kernel:  [<ffffffff8101fd79>] ? sched_clock+0x9/0x10
kernel:  [<ffffffff81221632>] ? signalfd_poll+0xb2/0xc0
kernel:  [<ffffffff8121f080>] ? ep_send_events_proc+0xb0/0x1c0
kernel:  [<ffffffff8121efd0>] ? ep_read_events_proc+0xd0/0xd0
kernel:  [<ffffffff8121f898>] ? ep_scan_ready_list+0x1c8/0x1d0
kernel:  [<ffffffff810039dd>] prepare_exit_to_usermode+0xbd/0x100
kernel:  [<ffffffff81003aed>] syscall_return_slowpath+0xcd/0x1d0
kernel:  [<ffffffff8109e150>] ? wake_up_q+0x60/0x60
kernel:  [<ffffffff81221075>] ? SyS_epoll_wait+0xb5/0xd0
kernel:  [<ffffffff81583e8c>] int_ret_from_sys_call+0x25/0x8f
systemd[1]: systemd-logind.service: Processes still around after final SIGKILL. Entering failed mode.
systemd[1]: systemd-logind.service: Failed with result 'timeout'.
systemd[1]: Failed unmounting /var.

When I don't start X, it shuts down without problems.

Last edited by dude42 (2016-01-06 10:23:51)

dviktor · 2016-01-07 16:49:10

Seems like I'm experiencing the same problem: when I'm trying to shutdown or reboot laptop from XFCE menu "A stop job is running for Login Service..." appears. If I first log out XFCE session and then manually shutdown all seems good

Kernel 4.3.3-2

mekitron · 2016-01-09 08:45:03

This seems hot issue of Jan.2016. I am also encountering same problem and trying to solve it. I have no problem while booting the OS but when it comes to shutdown. All same errors appear and nothing works at all.

mgmillani · 2016-01-09 19:41:56

The best "solution" I could find was logging out, then logging in as root and calling `poweroff -f` (suggested here).

I'm using a laptop with one AMD and one Intel video card, but the AMD card should be deactivated.

kavinga · 2016-01-10 07:53:34

It is working for both Gnome on Wayland and Cinnamon on LightDM. Not working for Gnome on GDM or Cinnamon on GDM. Probably the issue is with GDM and Xserver. So I have switched to LightDM from GDM and now it is working fine.

rhoit · 2016-01-11 06:57:38

kinda strange but I'm also having problem, I don't use any loginDM. use xfce4 with compiz, only way I could shutdown properly is to logoff xfce then $ shutdown now

dviktor · 2016-01-11 07:15:32

The same issue here
I don't use any login managers, X started after logging in through tty1 and XFCE runs. As I understood, the problem is related to the unmount process

I have Intel + AMD configuration but IMHO this is not an issue because it appeared after update (package list from unholy update)

PS:

mgmillani wrote:

The best "solution" I could find was logging out, then logging in as root and calling `poweroff -f`.

Logging in as root is a bad idea. Better way to manually shutdown/reboot from tty2, for example.

Last edited by dviktor (2016-01-11 07:19:08)

ganlu · 2016-01-12 11:48:03

Same here, but I can't swithc to tty2 or tty any, I have to shut down my laptop by mannually pressing the power button for a while.

dviktor · 2016-01-12 12:56:38

Are you using some login manager or starting DE via .xinitrc?

judd1 · 2016-01-12 14:32:18

I also got it with my gnome 3.18 and starting with GDM, the only way to turn off the pc is with sudo poweroff -f as stated by here, and no way to restart if there is not a tty with shutdown - r now

In addition to the above kernel 4.2.5-1 there was no problem shutdown and restart.-

dviktor · 2016-01-12 18:13:52

I think this is a bug introduced with 4.3.3-2 kernel. Has anybody filed a bugreport already?

NahUndFern · 2016-01-12 22:28:04

I'm experiencing this problem.

They way i normally shutdown or reboot is just typing

poweroff

or

reboot

No desktop environment or login manager, just running x and i3 window manager.

mgmillani wrote:

The best "solution" I could find was logging out, then logging in as root and calling `poweroff -f` (suggested here).
I'm using a laptop with one AMD and one Intel video card, but the AMD card should be deactivated.

A workaround that works for me most of the time is terminating X (usually by exiting through the window manager) and then powering off from the TTY. However, there have been times where i receive the output

Xorg refused to die

, which will make powering off from TTY impossible, and i receive the same logind.service stop job problem as i would with powering off in X.

I also have Hybrid graphics Intel/AMD. I doubt it's relevant to the problem, i just found it strange that quite a few people experiencing the problem in the thread also have Intel/AMD.

Last edited by NahUndFern (2016-01-12 22:31:13)

dviktor · 2016-01-13 06:37:24

filed a bug

NahUndFern · 2016-01-13 07:39:41

dviktor wrote:

filed a bug

I don't think it is necessarily a DE or XFCE problem. There's a few people reporting that they are experiencing it from gnome, and others reporting that they experience it from just window managers.

I would have thought it could happen to anyone in X, especially considering a couple of earlier posts in the the thread saying that the problem went away for them when using Wayland. I lack knowledge when it comes to Wayland so i might be mistaken, but i think it's mostly used without X server?

Also, when you experience the problem, does your error specify login service or logind service?

dviktor · 2016-01-13 08:18:09

I think that this bug is related to the kernel 4.3.3-2 so I've filed corresponding report. It's worth for everyone who experiencing this bug to confirm it on bugzilla

Personally I have error message with Login Service string

mekitron · 2016-01-13 18:09:11

dviktor wrote:

I've filed corresponding report.

I think, it is systemd problem because we can turn off laptops using sync && shutdown -f

adventurer · 2016-01-14 10:51:36

dviktor wrote:

I think that this bug is related to the kernel 4.3.3-2

I don't think so as I'm having this problem with the LTS kernel 4.1.15-1.

dviktor · 2016-01-14 11:11:45

here is the full list of package changes. As I noticed the problem appeared after this updates/removals. The only suspicious package is p11-kit.

Arch Linux

#1 2016-01-04 04:40:31

Shutdown/Reboot infinite hanging

#2 2016-01-04 05:05:54

Re: Shutdown/Reboot infinite hanging

#3 2016-01-04 05:20:47

Re: Shutdown/Reboot infinite hanging

#4 2016-01-05 04:15:52

Re: Shutdown/Reboot infinite hanging

#5 2016-01-05 15:45:05

Re: Shutdown/Reboot infinite hanging

#6 2016-01-05 22:28:32

Re: Shutdown/Reboot infinite hanging

#7 2016-01-05 23:58:18

Re: Shutdown/Reboot infinite hanging

#8 2016-01-06 10:20:12

Re: Shutdown/Reboot infinite hanging

#9 2016-01-07 16:49:10

Re: Shutdown/Reboot infinite hanging

#10 2016-01-09 08:45:03

Re: Shutdown/Reboot infinite hanging

#11 2016-01-09 19:41:56

Re: Shutdown/Reboot infinite hanging

#12 2016-01-10 07:53:34

Re: Shutdown/Reboot infinite hanging

#13 2016-01-11 06:57:38

Re: Shutdown/Reboot infinite hanging

#14 2016-01-11 07:15:32

Re: Shutdown/Reboot infinite hanging

#15 2016-01-12 11:48:03

Re: Shutdown/Reboot infinite hanging

#16 2016-01-12 12:56:38

Re: Shutdown/Reboot infinite hanging

#17 2016-01-12 14:32:18

Re: Shutdown/Reboot infinite hanging

#18 2016-01-12 18:13:52

Re: Shutdown/Reboot infinite hanging

#19 2016-01-12 22:28:04

Re: Shutdown/Reboot infinite hanging

#20 2016-01-13 06:37:24

Re: Shutdown/Reboot infinite hanging

#21 2016-01-13 07:39:41

Re: Shutdown/Reboot infinite hanging

#22 2016-01-13 08:18:09

Re: Shutdown/Reboot infinite hanging

#23 2016-01-13 18:09:11

Re: Shutdown/Reboot infinite hanging

#24 2016-01-14 10:51:36

Re: Shutdown/Reboot infinite hanging

#25 2016-01-14 11:11:45

Re: Shutdown/Reboot infinite hanging

Board footer