Summary: | security/plasma5-kscreenlocker: "Start New Session" does not work | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Raphael Kubo da Costa <rakuco> |
Component: | Individual Port(s) | Assignee: | Gleb Popov <arrowd> |
Status: | In Progress --- | ||
Severity: | Affects Only Me | CC: | arrowd, avg, dmk, grahamperrin, mikael, sv |
Priority: | --- | Flags: | arrowd:
maintainer-feedback+
|
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Raphael Kubo da Costa
2019-10-13 18:57:24 UTC
Yes it's still broken. I should clarify that the original report was for sddm. Later, I tried lightdm and with it "Start New Session" does indeed start a new X/lightdm session. Works for me with current SDDM and Plasma. Andriy, can you check it out again? I can switch users under SDDM. My issue is switching back to the first one. When I do that (by logging out the second user) the first user can't open up any new windows; the XAuth permissions are all messed up. (In reply to Dwayne MacKinnon from comment #4) Can you provide exact steps to reproduce the problem? (In reply to Gleb Popov from comment #5) 1) Lock the screen (either timeout or manual lock is fine.) 2) Use Start New Session to log in as a second user. 3) Log out of the second session. 4) Unlock the screen for the first session. 5) Try to open any new window (firefox, konsole, kmail, anything.) Indeed, I managed to reproduce this! After following outlined steps it is impossible to run any X application. Running "kwrite" yields: qt.qpa.xcb: could not connect to display :0 I believe, this is an upstream SDDM problem. Another interesting thing is that after switching back to the first user, it somehow gains an ability to shutdown/reboot the machine even if it hasn't before. I tried pulling in this patch: https://github.com/sddm/sddm/pull/1230 however it didn't help with this issue. I have some other PRs to sddm in flight, so I'll get back to this issue after these land. Meanwhile, any info on how that XAUTHORITY thing works would be really appreciated. I implemented fix for that, but it depends on many changes, so this is blocked by upstream for now. I'm waiting for a new ConsoleKit release. |