Created attachment 1159422 [details] systemd journal logs for session-1.scope (all users) Description of problem: While shutting down (or rebooting) the computer from the KDE Plasma desktop in the Fedora 24 Beta KDE spin, a stop job keeps running for a session (till now for Session 1) of my user account. It never ends and seems to be forcibly killed at the end of the timeout specified by the systemd DefaultTimeoutStopSec parameter. The systemd journal for session-1.scope is chock-full of errors. I am attaching a copy of it obtained through journalctl _SYSTEMD_UNIT=session-1.scope. Some of these errors may be related to bug #1323110 and bug #1211075. I experience this problem with the KDE spin, but not with the Workstation edition, but I don't know where the root cause of this problem lies. Version-Release number of selected component (if applicable): plasma-desktop 5.6.4-1.fc24 How reproducible: At almost every shutdown or reboot. Steps to Reproduce: 1. Install Fedora 24 Beta KDE spin. 2. Shut down or reboot the computer. 3. Repeat step 2 until the problem occurs (starts occurring within the first few times on my system). Actual results: A stop job runs for a user session and delays the shutdown process. Expected results: The shutdown process is not delayed. Additional info:
Can you logout of a session, and then login to VT (say as root), to check to see what user processes (if any) are still running?
Created attachment 1159778 [details] User processes remaining after logging out of KDE Plasma I have attached a list of processes for my user account that remain after logging out of the Plasma desktop environment. I am not sure which processes may be causing the issue. A mission-control* (perhaps mission-control-5) process, a gnome-keyring-daemon, and a defunct dbus-daemon are present in the list. Also, I observed the following:- 1. After logging out of Plasma, if I log in to a different VT as root and run ps -U username -u username, it lists the processes. If I run ps -U username -u username > some_regular_file, and then run the command again without redirection, it shows no more processes. I don't know if this is normal. 2. Shutting down or rebooting after logging out of Plasma does not cause the stop job problem. The stop job does not run and the shutdown is not delayed. It seems that something doesn't stop properly when shutting down or rebooting directly from Plasma.
PID TTY TIME CMD 1270 ? 00:00:00 systemd 1279 ? 00:00:00 (sd-pam) 1287 ? 00:00:00 gnome-keyring-d 1311 ? 00:00:01 dbus-daemon 1428 ? 00:00:00 mission-control 1474 ? 00:00:00 dbus-daemon <defunct> 1533 ? 00:00:00 at-spi-bus-laun 1538 ? 00:00:00 gam_server 1543 ? 00:00:00 dbus-daemon Hard to say, none of those are directly kde/plasma related. Not sure there's anything we can do about it (here)
How is it that the problem does not occur if I log out and then shut down (e.g., from the SDDM login screen)? Any clues there?
In the meantime, one workaround is to ask logind to kill these lingering processes is to edit /etc/systemd/logind.conf and set: KillUserProcess=yes (Looks like this may become the default in future systemd/logind releases anyway)
Already did that. That's how I ran it all along, otherwise it's too difficult to use a laptop. Hardly the way to go, though, I think. The problem occurs on neither the Workstation edition nor the XFCE spin, just the KDE one.
(In reply to Rex Dieter from comment #5) > In the meantime, one workaround is to ask logind to kill these lingering > processes is to edit > /etc/systemd/logind.conf and set: > KillUserProcess=yes Unfortunately, this suggestion did not work for me. The system still takes 90s to kill the user session unless I logout first.
Created attachment 1203006 [details] Phone screenshot of a stop job running at Fedora 24 laptop shutdown which takes too long and keeps increasing. This is a smartphone's screenshot of a stop job running at Fedora 24 laptop shutdown which takes too long and keeps increasing. I also got the user session stop jobs problem. It happened when /mnt/music was a samba share that was inaccessible due to this mageia v6 bug on the remote Samba service - https://bugs.mageia.org/show_bug.cgi?id=19356 - the laptop of the screenshot ran Fedora x86-64 v24.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.