https://bugs.kde.org/show_bug.cgi?id=494927
Bug ID: 494927
Summary: kscreeen_locker does not unlock screen if there is a
2nd display connected
Classification: Plasma
Product: kscreenlocker
Version: 6.2.1
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: saroum...@rbox.me
Target Milestone: ---
SUMMARY
kscreeen_locker does not unlock screen if there is a 2nd display connected.
STEPS TO REPRODUCE
1. Connect a 2nd screen
2. Let the session autolocks and the screens goes in sleep mode
3. Wake up the screens with keyboard, the prompt for unlocking is displayed on
primary screen
4. Type the password press enter
OBSERVED RESULT
The field for entering the password is blanked, nothing else is changed, no
error message, the unlock screen stays on screen.
You can try to type the password again for the same result.
Logs :
oct. 17 12:55:49 host kscreenlocker_greet[17115]: pam_systemd_home(kde:auth):
New sd-bus connection (system-bus-pam-systemd-home-17115) opened.
oct. 17 12:55:49 host kscreenlocker_greet[17115]: qt.qpa.wayland: Creating a
fake screen in order for Qt not to crash
oct. 17 12:55:50 host kscreenlocker_greet[17115]: qt.qpa.wayland: Creating a
fake screen in order for Qt not to crash
oct. 17 12:55:51 host kscreenlocker_greet[17115]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: Property 'startAuthenticating' of object TypeError: Type error is
not a function
oct. 17 12:55:55 host kscreenlocker_greet[17115]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280:
TypeError: Property 'respond' of object 1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not
a function
EXPECTED RESULT
kscreen_locker unlocks the screen
SOFTWARE/OS VERSIONS
Archlinux
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel 6.6.56-1-lts
Graphics Platform : Wayland
ADDITIONAL INFORMATION
With only 1 screen I do not reproduce the problem.
As soon as I power off the 2nd screen, the problem disappear.
Information about the screens : (the primary screen is on DP-2, the 2nd screen
is on HDMI-A-2)
$ kscreen-doctor -o
Output: 1 HDMI-A-2
disabled
connected
priority 0
HDMI
Modes: 1:1024x768@60! 2:1920x1080@60 3:1920x1080@60 4:1920x1080@60
5:1920x1080@50 6:1600x1200@60 7:1680x1050@60 8:1664x1040@60 9:1440x1080@60
10:1280x1024@60 11:1440x900@60 12:1280x960@60 13:1152x864@60 14:1280x720@60
15:1280x720@60 16:800x600@60 17:720x480@60 18:720x480@60 19:640x480@60*
20:640x480@60 21:1280x1024@60 22:1024x768@60 23:1280x800@60 24:1280x720@60
Geometry: 0,0 640x480
Scale: 1
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: none
Color profile source: sRGB
Brightness control: supported, set to 100%
Output: 2 DP-2
enabled
connected
priority 1
DisplayPort
Modes: 25:3840x2160@60*! 26:3840x2160@60 27:3840x2160@50
28:3840x2160@48 29:3840x2160@30 30:2560x1440@60 31:1920x1200@60
32:1920x1080@60 33:1920x1080@60 34:1920x1080@60 35:1600x1200@60
36:1680x1050@60 37:1600x900@60 38:1280x1024@60 39:1440x900@60
40:1280x800@60 41:1152x864@60 42:1280x720@60 43:1280x720@60 44:1280x720@60
45:1024x768@60 46:800x600@60 47:720x480@60 48:720x480@60 49:640x480@60
50:640x480@60 51:640x480@60 52:1600x1200@60 53:1280x1024@60 54:1024x768@60
55:2560x1600@60 56:1920x1200@60 57:3840x2160@60 58:3200x1800@60
59:2880x1620@60 60:2560x1440@60 61:1920x1080@60 62:1600x900@60
63:1368x768@60 64:1280x720@60
Geometry: 0,0 1920x1080
Scale: 2
Rotation: 1
Overscan: 0
Vrr: Automatic
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: /home/user/Documents/Calibration/HD #1 2018-12-13 20-57
2.2 F-S XYZLUT+MTX.icc
Color profile source: ICC
Brightness control: supported, set to 100%
--
You are receiving this mail because:
You are watching all bug changes.
