These are the processes running after a starting KDE neon (Oracle VirtualBox VM), logging in (SDDM), and opening a konsole on the Desktop:



So which one of these is the offending session? Or is it even identified here?

Paul Loughman
snowhg@icloud.com




On Jun 11, 2016, at 12:10 PM, Harald Sitter via KDE Bugzilla <bugzilla_noreply@kde.org> wrote:

https://bugs.kde.org/show_bug.cgi?id=363851

Harald Sitter <sitter@kde.org> changed:

          What    |Removed                     |Added
----------------------------------------------------------------------------
          Assignee|neon@kde.org                |neon-bugs@kde.org

--- Comment #13 from Harald Sitter <sitter@kde.org> ---
If you were logged in on a terminal, or you were logged in over ssh, or you
switched user, or you logged out and back in again, you would end up with a
second session. There's possibly other cases, but generally those are the main
things.

Pretty much anything that resembles a login of any type will create a session.

And pretty much any process created as part of login but not killed by some
entity other than systemd would then block shutdown.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
neon mailing list
neon@kde.org
https://mail.kde.org/mailman/listinfo/neon

=