Bug 1218284 - Running xdg-desktop-portal the first time sets cpu frequency governor to powersave
Summary: Running xdg-desktop-portal the first time sets cpu frequency governor to powe...
Status: RESOLVED INVALID
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-20 23:36 UTC by Simon Vogl
Modified: 2023-12-21 01:23 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Vogl 2023-12-20 23:36:23 UTC 
Running xdg-desktop-portal sets the cpu governor to powersave if it was previously set to performance on first run

Steps to reproduce:

-Boot up a system to login manager.

-log into icewm session.

-start xterm

set the cpu governor to "performance" by running this in xterm:

sudo cpupower frequency-set --governor performance

- run xdg-desktop-portal in xterm.

What should happen:

the cpu governor is still set to "performance".

What actually happens:

the cpu governor is now set to "powersave" for some reason.

Absolutlely zero interesting output containing "governor" or "powersave" from journalctl...

Any idea what might be wrong here?
Comment 1 Simon Vogl 2023-12-21 01:23:38 UTC 
Nevermind, I'm stupid, I didn't realize power-profiles-daemon does that automatically.

//Case Closed.