|
Bugzilla – Full Text Bug Listing |
| Summary: | Plasma lockscreen can't unlock if there is no display manager installed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Alexey Rochev <equeim> |
| Component: | KDE Workspace (Plasma) | Assignee: | E-Mail List <opensuse-kde-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | equeim, fabian, fvogt |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Alexey Rochev
2018-09-13 14:47:45 UTC
What's the usecase for that setup? It would be possible to just ship the same file as xdm and sddm do in kscreenlocker and point KDE4_COMMON_PAM_SERVICE to it. It only contains includes anyway. >> What's the usecase for that setup?
I prefer to boot system in multi-use mode and launch X via startx is needed.
kscreenlocker in KDE:Frameworks5 ships its own PAM file now. Submitted to TW and will be part of Leap 15.1. This is an autogenerated message for OBS integration: This bug (1108329) was mentioned in https://build.opensuse.org/request/show/639230 Factory / kscreenlocker |