Bug 511270 - Setting GPU offload variables globally breaks Plasma on Wayland after resume
Summary: Setting GPU offload variables globally breaks Plasma on Wayland after resume
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.4.5
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-28 15:14 UTC by Werner Sembach [TUXEDO]
Modified: 2025-12-03 16:32 UTC (History)
3 users (show)

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

Attachments
Broken panel bug (431.91 KB, image/png)
2025-10-28 15:14 UTC, Werner Sembach [TUXEDO] 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Werner Sembach [TUXEDO] 2025-10-28 15:14:25 UTC 
Created attachment 186259 [details]
Broken panel bug

SUMMARY
Setting GPU offload variables globally e.g. by an `/etc/envionment` that looks like this:
```
__NV_PRIME_RENDER_OFFLOAD=1
__GLX_VENDOR_LIBRARY_NAME=nvidia
DRI_PRIME=1
```
breaks Plasma on Wayland after resume.

STEPS TO REPRODUCE
1. Set __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia DRI_PRIME=1 gobally
2. Start Plasma on Wayland
3. Suspend and resume

OBSERVED RESULT
Panel is blank and/or unresponsive. Background is black or doesn't refresh (e.g. windows leave trails when being moved).

EXPECTED RESULT
Desktop shows up as normal

SOFTWARE/OS VERSIONS
Linux: 6.14.0-113033-tuxedo
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.8.2
Comment 1 David Edmundson 2025-10-28 16:39:29 UTC 
Generally if you change with environment variables you are on your own. 

If changing nvidia env vars breaks plasma then either they're being used wrong or this is an nvidia problem unless proved otherwise.
Comment 2 Werner Sembach [TUXEDO] 2025-10-28 16:49:11 UTC 
(In reply to David Edmundson from comment #1)
> Generally if you change with environment variables you are on your own. 
> 
> If changing nvidia env vars breaks plasma then either they're being used
> wrong or this is an nvidia problem unless proved otherwise.

The same behavour happens when using KWIN_DRM_DEVICES https://invent.kde.org/plasma/kwin/-/wikis/Environment-Variables#kwin_drm_devices to make plasma run on the nvidia gpu.
Comment 3 Nate Graham 2025-10-29 21:03:41 UTC 
Is everything on the system also set up according to https://community.kde.org/Distributions/Packaging_Recommendations#Proprietary_NVidia_driver_configuration?
Comment 4 Werner Sembach [TUXEDO] 2025-11-03 17:57:31 UTC 
(In reply to Nate Graham from comment #3)
> Is everything on the system also set up according to
> https://community.kde.org/Distributions/
> Packaging_Recommendations#Proprietary_NVidia_driver_configuration?

With nvidia.NVreg_PreserveVideoMemoryAllocations=1 the bug does not trigger, however this does not seems to be set by default on ubuntu (but would have to double check with a fresh install so no guarantee).

Thanks for the hint.
Comment 5 Bug Janitor Service 2025-11-18 03:47:18 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 6 Werner Sembach [TUXEDO] 2025-11-18 13:38:48 UTC 
changed to reported, but also somewhat "works for me" so feels free to close it
Comment 7 TraceyC 2025-12-03 16:32:26 UTC 
Closing as requested