Bug 1924212 - KDE live images boot to SDDM or lock screen
Summary: KDE live images boot to SDDM or lock screen
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-02 20:00 UTC by Adam Williamson
Modified: 2021-02-05 23:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-05 23:58:16 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Adam Williamson 2021-02-02 20:00:10 UTC 
Since Fedora-Rawhide-20210130.n.0, Fedora KDE live images always seem to boot to SDDM or a lock screen (I'm not sure which it is), when they should boot to an unlocked, logged-in desktop. This result is consistent across multiple runs of multiple tests on openQA staging and production.

The only relevant package that I can see changed in 20210130.n.0 is plasma-workspace:

Package:      plasma-workspace-5.20.90-9.fc34
Old package:  plasma-workspace-5.20.90-7.fc34
Summary:      Plasma workspace, applications and applets
RPMs:         libkworkspace5 plasma-lookandfeel-fedora plasma-workspace plasma-workspace-common plasma-workspace-devel plasma-workspace-doc plasma-workspace-geolocation plasma-workspace-geolocation-libs plasma-workspace-libs plasma-workspace-wayland plasma-workspace-x11 sddm-breeze
Size:         61.74 MiB
Size change:  4.71 KiB
Changelog:
  * Fri Jan 29 2021 Rex Dieter <rdieter> - 5.20.90-9
  - pull in upstream fix for lockscreen detection (kde#432251)

Notably, SDDM did *not* change in that compose. So plasma-workspace is where I'm filing for now. If it turns out to be something else, we can move it.
Comment 1 Adam Williamson 2021-02-05 23:58:16 UTC 
This seems to have gone away in the last couple of composes. It may have been to do with the debug kernel KASAN issue.
Note You need to log in before you can comment on or make changes to this bug.