[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2021-11-22 Thread Jason Liu
Confirmed that this is still an issue in focal. It is only an issue if I log onto a XFCE session and then log out, these two processes stay around: /usr/libexec/geoclue-2.0/demos/agent /usr/bin/python3 /usr/share/system-config-printer/applet.py When I remove the geoclue-2.0 from the

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2021-08-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2021-07-01 Thread Daniel Richard G.
Yes, it is still an issue in focal. Was there an update since last year that should have addressed this? ** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2021-06-30 Thread Dan Streetman
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title:

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2020-05-08 Thread Daniel Richard G.
Also related: LP: #1877532 It's possible that all the lingering processes are due to a couple of misbehaving applications. This isn't a great state of affairs (the cleanup process should not be so fragile that non-cooperative processes can stop it completely), but it might explain what's going

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2020-05-08 Thread Daniel Richard G.
Related: LP: #1877528 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1871726 Title: "systemd --user" and child processes fail to exit when user logs out Status in

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2020-04-10 Thread Daniel Richard G.
Could you try this using lightdm? It's possible that this may be a display-manager issue. I did notice that in a different (customized) configuration of Xubuntu, the user processes still remained after logout, but then killing the "systemd --user" process resulted in the login session ending.

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2020-04-10 Thread Sebastien Bacher
Thank you for your bug report, I can't confirm the bug on focal Using an uptodate system - start to gdm - login is 'userone' - create a 'dbguser' - logout from the 'userone' session - ssh dbguser@ $ loginctl list-sessions SESSION UID USER SEAT TTY 27 1001 dbguser pts/0 c3

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2020-04-09 Thread Daniel Richard G.
This occurs whether the user logs in (through lightdm) on the console, or remotely via xrdp. Running that command, as root, after the user (skunk) has logged in via lightdm: # loginctl list-sessions SESSION UID USER SEAT TTY 20 root c2 1000 skunk

[Touch-packages] [Bug 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

2020-04-09 Thread Sebastien Bacher
Thank you for your bug report, do you have that user logged in from a VT or ssh maybe? What's the output of $ loginctl list-sessions (log as another user to try the comment) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to