Shutdown did seem too slow with 13.1, but not with 13.2.
Okay, one exception. On my box with Nvidia graphics, I did have a slow shutdown yesterday. I normally don’t see that, but it did happen yesterday.
I had just run updates, and “systemd” was updated. That might be related. On a “systemd” update, I notice a problem with the user manager processes. What I mostly notice is that shutdown or reboot within KDE doesn’t work – it just logs me out and puts me in the “lightdm” login screen. I then have to shutdown or restart from there.
user@1000.service - User Manager for UID 1000 Loaded: loaded (/usr/lib/systemd/system/user@.service; static) Active: active (running) since Sun 2014-12-07 15:40:41 EET; 5min ago Main PID: 1143 (systemd) Status: "Startup finished in 33ms." CGroup: /user.slice/user-1000.slice/user@1000.service |-1143 /usr/lib/systemd/systemd --user `-1144 (sd-pam)
Dec 07 15:40:41 linux-uezg.site systemd[1143]: pam_unix(systemd-user:session): session opened for user ozturk by (uid=0)
Apologies for resurrecting this thread, but I didn’t find anything more recent.
I’m having the same issue and I think it’s related to using network manager alongside mounting a network share. Something about the system hanging not being able to connect to the share after network manager has been shut down.
Does anyone with this issue have the same issue have that setup?
For me, 13.2 has been a lot better than 13.1 on shutdown time.
But there was one recent exception. It was taking so long that I forced a power-off.
I am not certain of the cause, but I have a pretty good guess. I had just setup the system as an NFS client, mounting the NFS share with autofs. I only use that share occasionally, so it is usually not mounted. But, on this occasion, I had used it. And NFS performance over WiFi had been quite poor (the computer is some distance from the AP, and there’s another computer in the house that is closer to the AP and was heavily using WiFi at the time). So I think the shutdown hang was related to this NFS mount. In subsequent uses, I have sometimes manually used “umount” before shutdown, and I never had a problem that way (“umount” was on the NFS share). On one occasion, I plugged in an ethernet cable to avoid the poor NFS performance problem. And shutdown was fine then even though I skipped the “umount”).
I used your ~/.kde4/shutdown suggestion earlier and made sure any program using the network share is stopped and then the shares unmounted (needed a permission in sudoers so I can do that with my user).
Now restarts and shutdowns are much much faster.