Bug 499420 - Plasma switches to software rendering backend after waking from screen lock
Summary: Plasma switches to software rendering backend after waking from screen lock
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.2.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-02 17:12 UTC by Byron
Modified: 2025-02-21 19:36 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Byron 2025-02-02 17:12:44 UTC
SUMMARY
After the timeout period where displays go into power saving mode after the computer is locked, waking from this state will often have plasmashell be in the software rendering mode, and also will have set the backend to software in kdeglobals. It may be related to my monitor having a deep power saving mode, where it will disconnect after an unspecified time, however I can't seem to replicate it consistently. I am also using an Nvidia 3070 Ti with official drivers.

STEPS TO REPRODUCE
1. Have screens go into power saving mode
2. Wake computer
3. Observe Software Rendering notification in system tray
4. Observe scene backend in kdeglobals set to software

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Byron 2025-02-02 17:16:59 UTC
Sorry accidentally submitted before finishing the template
OBSERVED RESULT
Software Rendering notification in system tray and kdeglobals scene backend set to software, plus all the oddities that come with software rendering.

EXPECTED RESULT
Remains in automatic rendering mode when waking from power saving 

SOFTWARE/OS VERSIONS
Linux: Nobara Linux 41, kernel 6.12.11-204.nobara
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1

ADDITIONAL INFORMATION
Comment 2 John Kizer 2025-02-06 20:26:36 UTC
Hi - for what it's worth, I don't see this issue on my Fedora KDE 41 device with an NVIDIA card and proprietary drivers.

Just to check - do you have multiple monitors? If so, does the issue also occur if only one monitor is attached?

And does the issue occur if only the monitors power down, or does it happen when the overall device also enters a sleep state?

Thanks!
Comment 3 Bug Janitor Service 2025-02-21 03:46:47 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 4 Byron 2025-02-21 19:36:47 UTC
(In reply to John Kizer from comment #2)
> Hi - for what it's worth, I don't see this issue on my Fedora KDE 41 device
> with an NVIDIA card and proprietary drivers.
> 
> Just to check - do you have multiple monitors? If so, does the issue also
> occur if only one monitor is attached?
> 
> And does the issue occur if only the monitors power down, or does it happen
> when the overall device also enters a sleep state?
> 
> Thanks!

I'm not entirely sure what changed but I haven't noticed this issue anymore, so I think I'll just call this resolved.