Bug 480905 - Plasmashell does not start when cpu-power governor is set to performance
Summary: Plasmashell does not start when cpu-power governor is set to performance
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Startup process (show other bugs)
Version: 5.27.10
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-05 15:01 UTC by gigastarcraft2
Modified: 2024-03-14 03:47 UTC (History)
2 users (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 gigastarcraft2 2024-02-05 15:01:18 UTC
STEPS TO REPRODUCE
1. Set cpupower governor to performance at boot (using service or GUI)
2. Restart PC.
3. Black screen, you have to run kstart plasmashell manually.

OBSERVED RESULT
Blank/black screen after a startup.

EXPECTED RESULT
Normal startup of a plasmashell.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.7.3 Artix OpenRC KDE Wayland
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.114.0 
Qt Version: 5.15.12

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-02-06 19:50:06 UTC
Is it consistent that only that setting is causing this? And when you go back to your prior CPU governor, it starts up normally. That seems rather odd. Can you list other customizations you've made to the system that may be relevant?
Comment 2 gigastarcraft2 2024-02-08 14:12:29 UTC
(In reply to Nate Graham from comment #1)
> Is it consistent that only that setting is causing this? And when you go
> back to your prior CPU governor, it starts up normally. That seems rather
> odd. Can you list other customizations you've made to the system that may be
> relevant?

Happened twice in a row after restarting and worked well after setting back to Shedutil. I checked again and this time setting to performance did not cause this. Weird!
Comment 3 Nate Graham 2024-02-13 20:16:24 UTC
Hmm, sounds like maybe this setting is not what's causing the issue, and it's caused by something else. Can you do some more debugging to see if you can figure out what setting or condition is triggering the issue? Thanks!
Comment 4 Bug Janitor Service 2024-02-28 03:46:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2024-03-14 03:47:02 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!