https://bugs.kde.org/show_bug.cgi?id=480905
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=480905
--- Comment #4 from Bug Janitor Service ---
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
https://bugs.kde.org/show_bug.cgi?id=480905
--- Comment #3 from Nate Graham ---
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?
https://bugs.kde.org/show_bug.cgi?id=480905
--- Comment #2 from gigastarcra...@proton.me ---
(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
https://bugs.kde.org/show_bug.cgi?id=480905
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
