[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available

2023-06-03 Thread David Koppelman
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #5 from David Koppelman --- I meant that it's *not* likely I missed anything, due to the multi-second inactivity to suspend time. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available

2023-06-03 Thread David Koppelman
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #4 from David Koppelman --- (In reply to Nate Graham from comment #3) > Thanks. Out of curiosity, does the discrete GPU also render the logout > screen? The thing that appears when you click "Shut Down." If so, then I'm > guessing the

[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available

2023-06-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #3 from Nate Graham --- Thanks. Out of curiosity, does the discrete GPU also render the logout screen? The thing that appears when you click "Shut Down." If so, then I'm guessing the shader-based blur effects they both use are triggering

[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available

2023-05-31 Thread David Koppelman
https://bugs.kde.org/show_bug.cgi?id=470376 --- Comment #2 from David Koppelman --- When a system is set up for what Nvidia calls prime render offload, applications by default will use the integrated GPU. In order to use the discrete GPU the application has to have certain environment variables

[kscreenlocker] [Bug 470376] kscreenlocker uses discrete GPU when integrated GPU is available

2023-05-31 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470376 Nate Graham changed: What|Removed |Added Summary|kscreenlocker uses discrete |kscreenlocker uses discrete