https://bugs.kde.org/show_bug.cgi?id=509765

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #7 from [email protected] ---
I think I'm encountering this same bug.  I'm on:
CachyOS 24.12
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.18.0-3-cachyos (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVIDIA GeForce RTX 4070

I have 2 monitors.  The primary is set to 144.06hz and the smaller is set to
59.91hz.  If I turn the primary one off (using the button on the bottom of the
monitor), then turn it back on, it does not come back on, (and mentions that it
has no input as if the cable is disconnected.) Moving the mouse or hitting a
key on the keyboard does not bring it back, (but the computer has not crashed,
I see the input on the 2nd monitor.) The smaller monitor does flash as if
re-setting what windows go on what monitors and what backgrounds to use at this
point, but that doesn't bring the primary monitor back.

If I unplug the primary one while it's turned on and reconnect it, it comes
back up no problem.

If I turn off the primary monitor, turn it back on, unplug it and reconnect it,
it comes back up.

If I unplug the secondary monitor while the primary one is in the broken state,
the primary ones comes back.

If I start with the secondary monitor unplugged, turn off the primary one, turn
it back on, then plug in the secondary one it fixes the primary one.

If I set the primary monitor to 60hz then it can be turned off and back on
without issue.

If I set the primary monitor to 120hz it has the same problems as the 144.06hz
configuration.

If I hit ctrl-alt-f2 when the monitor is in the broken state it comes back up,
(and remains up if I switch back to ctrl-alt-f1.)

I don't seem to have drm_info installed. Would it be useful at this point to
install it to get you it's output?  Is there any other debugging info that
would help track down this bug?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to