https://bugs.kde.org/show_bug.cgi?id=437973
--- Comment #6 from Nate Graham ---
Hmm. Can you attach the output of `kscreen-doctor -o` before you trigger the
bug (when it's working properly) and then immediately after you trigger the bug
(when the refresh rate gets reset)?
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=437973
--- Comment #5 from Tim ---
(In reply to Nate Graham from comment #4)
> (In reply to Tim from comment #1)
> > Some additional info. Found in the journalctl this is what seems to cause
> > the issue:
> >
> > 6/1/21 10:53 PM kscreen_backend_launcher
https://bugs.kde.org/show_bug.cgi?id=437973
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=437973
Tim changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO |---
https://bugs.kde.org/show_bug.cgi?id=437973
Nate Graham changed:
What|Removed |Added
Component|libkscreen |common
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=437973
--- Comment #1 from Tim ---
Some additional info. Found in the journalctl this is what seems to cause the
issue:
6/1/21 10:53 PM kscreen_backend_launcherkscreen.xrandr: RRSetCrtcConfig
(change output)
Output: 449 ( "DP-1" )
CR
https://bugs.kde.org/show_bug.cgi?id=437973
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
Product|
