Arch Linux

jdmac

Member

Registered: 2015-07-14

Posts: 13

GDM + open-vm-tools seems to hang on shutdown/restart

Hi All,

I've noticed a problem that doesn't seem to be specific to Arch (seen it in Fedora 24 also).

The problem I've noticed is that when shutting down or restarting GDM, systemd gets stuck waiting for a stop job on c1 and User Manager for one minute and thirty seconds until timeout.

I've been working around this by using lightdm for a while (2-3 months maybe), figuring the issue may have been a temporary bug introduced by a recent patch and would be resolved as quickly as it came.
However, going back to GDM, it's still present. I can't see much talk about the issue so I'm hoping it's just me but I do seem to be able to reproduce it on a fresh install.

If I completely remove open-vm-tools, the issue doesn't occur anymore.
It doesn't matter whether open-vm-tools services are enabled, just as long as it's installed and modules loaded to kernel.

I'm running arch inside VMWare Workstation 12.5 Pro.

Everything is up to date, so versions are:
open-vm-tools 10.0.7-5
gdm 3.20.1-2
systemd 231-3

Here's the logs of what happens.

Oct 09 19:01:42 arch systemd[1]: Stopped Session c2 of user xxxxx.
Oct 09 19:01:42 arch systemd[608]: Received SIGRTMIN+24 from PID 1096 (kill).
Oct 09 19:01:42 arch systemd[1]: Stopped User Manager for UID 1000.
Oct 09 19:01:42 arch systemd[1]: Removed slice User Slice of xxxxx.
Oct 09 19:01:42 arch systemd-logind[441]: Removed session c2.
Oct 09 19:01:42 arch systemd[1]: Unmounted /run/user/1000.
Oct 09 19:03:12 arch systemd[498]: at-spi-dbus-bus.service: State 'stop-sigterm' timed out. Killing.
Oct 09 19:03:12 arch systemd[498]: at-spi-dbus-bus.service: Killing process 554 (at-spi-bus-laun) with signal SIGKILL.
Oct 09 19:03:12 arch systemd[1]: user@120.service: State 'stop-sigterm' timed out. Killing.
Oct 09 19:03:12 arch systemd[1]: user@120.service: Killing process 498 (systemd) with signal SIGKILL.
Oct 09 19:03:12 arch systemd[1]: user@120.service: Killing process 554 (at-spi-bus-laun) with signal SIGKILL.
Oct 09 19:03:12 arch systemd[1]: session-c1.scope: Stopping timed out. Killing.
Oct 09 19:03:12 arch systemd[1]: session-c1.scope: Killing process 550 (Xwayland) with signal SIGKILL.
Oct 09 19:03:12 arch systemd[1]: Stopped Session c1 of user gdm.
Oct 09 19:03:12 arch systemd[1]: session-c1.scope: Unit entered failed state.
Oct 09 19:03:12 arch systemd[1]: Stopped User Manager for UID 120.
Oct 09 19:03:12 arch systemd[1]: user@120.service: Unit entered failed state.
Oct 09 19:03:12 arch systemd[1]: user@120.service: Failed with result 'timeout'.

Any ideas what is blocking/causing?

Many thanks,

jdmac

jdmac

Member

Registered: 2015-07-14

Posts: 13

Re: GDM + open-vm-tools seems to hang on shutdown/restart

Is anybody else experiencing this?

4ronie4

Member

Registered: 2015-09-24

Posts: 20

Re: GDM + open-vm-tools seems to hang on shutdown/restart

I have experienced this today and I'm not running a virtual machine, it's running on my laptop. I think it's a bug of GDM, also have this problem on the previus version of Gnome.

Last edited by 4ronie4 (2017-01-13 11:12:05)

jf25

Member

From: Germany

Registered: 2015-07-11

Posts: 35

Re: GDM + open-vm-tools seems to hang on shutdown/restart

Same issue here since about yesterday (might also be 3 days ago, not sure). It doesn't always happen, only sometimes. It could  be related to a systemd update (232-7), but that's hard to say, since it's not reliably reproducible.

Glinx

Member

Registered: 2010-10-12

Posts: 34

Re: GDM + open-vm-tools seems to hang on shutdown/restart

WaylandEnable=false Worked very well for getting rid of the reboot/shutdown "GDM a stop service is running..."
https://wiki.archlinux.org/index.php/GD … _on_logout

I'm using a nvidia card that doesn't support wayland yet.

After a few more reboots it came back
back to xinit to auto login..

Last edited by Glinx (2017-02-01 09:26:32)

4ronie4

Member

Registered: 2015-09-24

Posts: 20

Re: GDM + open-vm-tools seems to hang on shutdown/restart

it seems to be reported on Arch
https://bugs.archlinux.org/task/47734