| Summary: | RFE: refuse *explicit* screen-lock-request if some native console shell is logged-in | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreenlocker | Reporter: | Pavel Raiskup <praiskup> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | bshah, mgraesslin |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
This is outside the scope of kscreenlocker and in general of a desktop environment. Because I'd like to have this fixed, some day (not never), where can I forward this? Personally I think this is the job of whatever application runs on the virtual terminal. It needs something like a lock screen. So that once you switch away from the vt, it automatically locks the vt. Hms, that's interesting re-definition of the problem :). Thanks. Is there a portable (across environments) way to lock the screen so I can file a bug against the app in question? Sorry I don't know. |
.. and throw an ugly warning instead! It happens from time to time that user has to switch to native console (CTRL-ALT-F{2..6}) to fix/kill something. Any such login shell (not explicitly logged-out) might there survive for ages and become to be an open door for attacks. Or please provide this function at least as an optional feature. Original report: https://bugzilla.redhat.com/show_bug.cgi?id=1275591