Bug 490268 - Screen Locker Loses Visual Effects When Monitor and Laptop Screen Sleeps
Summary: Screen Locker Loses Visual Effects When Monitor and Laptop Screen Sleeps
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.1.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-14 18:48 UTC by Unknown
Modified: 2025-03-19 05:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Backtrace output from error dialog on login. (60.92 KB, text/plain)
2024-07-14 18:48 UTC, Unknown
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2024-07-14 18:48:48 UTC
Created attachment 171662 [details]
Backtrace output from error dialog on login.

SUMMARY

When my laptop is plugged into a monitor and then turns off the monitor, there's a chance for the lock screen to have its effects bugged. The lock screen still works, it's just the effects applied that gets buggy.

STEPS TO REPRODUCE
1. Plug laptop to separate monitor and keep the laptop screen also open.
2. Let the monitors sleep by the lock screen.
3. Awaken the device.

OBSERVED RESULT

When the monitors wakes up and lock screen appears:
- The profile picture is missing a white frame and is a rectangle instead of a circle.
- The shadow and blur effects have disappeared.
The lock screen does work as usual, and you can unlock and continue to use the desktop as normal.

EXPECTED RESULT

The lock screen should be able to keep its effects.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.1.2
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION

I wasn't sure what product to report his as a bug in, but when error dialog shows up on login. It seems like kscreenlocker, but the backtrace always says there's a segfault on plasmashell.
Comment 1 TraceyC 2025-03-04 23:04:12 UTC
Thanks for the bug report. Are you still seeing this in Plasma 6.3.2? If you are, we need some additional information.  Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:


#8  0x0000715833a6f112 in ?? () from /usr/lib/libQt6Gui.so.6
#9  0x0000715834818647 in ?? () from /usr/lib/libQt6Quick.so.6
#11 0x00007158330c9747 in ?? () from /usr/lib/libQt6Core.so.6

Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks again!
Comment 2 Bug Janitor Service 2025-03-19 03:47:06 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Unknown 2025-03-19 05:15:40 UTC
I haven't been able to replicate this bug as of late, as I have switched primary computers and a different distro.