| Summary: | Power management actions shown even when they don't fit the use case of remote login | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Sebastian Mogl <sebastian.mogl> |
| Component: | Session Management | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | natalie_clarius, nate, sebastian.mogl |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 5.27.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Sebastian Mogl
2024-01-24 17:04:53 UTC
So after doing some research, this is probably best implemented as a session-management-backend in plasma-worspace in libkworkspace/sessionmanagementbackend.cpp¹.
* New Class that implements and only allows logout.
* logout by running the command: `x2goterminate-session`
* Session status would be always Ready
* Hook in initializer that uses the X2go-Backend if the `X2GO_SESSION` envoirnment variable is set before checking for logind after checking for the test session variable.
¹: https://invent.kde.org/plasma/plasma-workspace/-/blob/master/libkworkspace/sessionmanagementbackend.cpp
Locking could be handled by running `x2gosuspendsession`, but that isn't handled by the backends yet.
|