Started Session C1 Of User
Actual results: long shut-down waiting: a stop job is running for Session 1 of user antonio Expected results: clean shut-down as with other kernels Additional info: it seems that the problem is for one user, a different user gets a clean shut-down. On my laptop everything seems o.k.
There are many reasons why a system might hang during reboot/shutdown. It is a symptom, not a cause. If you do not have evidence that the root cause of your system hang is the same as the root cause of the system hang experienced by the initial reporter of this issue, then please do not reply to this issue.
If you see the same symptom for a different reason, then nothing that has been said on this issue report is going to help you, and anything you say on this issue report is just going to make it even more confusing to a reader.
Please contact your distribution vendor (Arch Linux, Ubuntu/Canonical, Mint, etc.) for initial support. If you have evidence that your issue is caused by systemd (not to be confused with a bug merely involving systemd) then you can report that as a separate bug, with a more specific description based on that evidence.
For example, the details provided by @grossws seem to indicate a bug in either kded5, sddm, or the systemd units provided with sddm. That is probably not a bug in systemd and will probably not be fixed by changing systemd, so this is the wrong place to ask for a solution.
Started Session C1 Of User Portal
It seems no-one is assigned to this bug. Why?
Here are some reasons why assigning a developer to work on this issue would be counterproductive:
Started Session C1 Of User Pdf
Because the issue was closed in 2016. Closed issues are not worked on. If you have evidence of a bug in systemd, please open a new issue to represent it, with a more specific title and description than this one, and do not mix it up with everything else that has been said in this thread.
Because there does not seem to be any particular evidence that any of the various problems that different people are experiencing are bugs in systemd, as opposed to bugs in particular services that they are running. Bugs in pieces of software outside systemd are not solved by changing systemd, they are solved by changing the other piece of software.
Because even if some or all of the problems reported in this comment thread were caused by bugs in systemd, no single volunteer is going to want to take responsibility for fixing a series of different bugs (some of which might be bugs in systemd, some of which are almost certainly not) that are getting mixed into this issue thread. That would be an endless task - by the time one had been solved, another would likely have been reported, because the title of this issue thread is so general that it could describe all sorts of different root causes. Again, if you have evidence of a bug in systemd, please open a new issue to represent it, and do not mix it up with everything else that has been said in this thread.