https://bugs.kde.org/show_bug.cgi?id=370494
Sebastian Kügler <se...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #17 from Sebastian Kügler <se...@kde.org> ---
So, good news.
This bug is a duplicate of another of bug:356864.
Here's a bit of context, before I redirect this bug's traffic to the other one,
which has tracked the related changes.
libkscreen's list of modes for each output were never assumed to change at
runtime, so a whole lot of components assumed it would never change and not
react to changes, the list of modes was constant, as reasonable assumption
given hardware. Less reasonable in vms, as we know. So the vm presents us with
changing modes for outputs, but these were never re-read (in our xrandr
backend), and changes never propagated through libkscreen's API to the kded
module (which handles all the policy bits and initiates the actual changes at
runtime). A few patches down the road, and I've now successfully (with git
master) resizing Plasma inside the VM window.
In my setup (qemu with neon git unstable inside, host is a debian unstable
thinkpad with intel graphics), I'm running into a bug, however. When at least
one axis of the vm window shrinks, I reliably get a black screen, when I grow
any or both axes, and kscreen's kded sets the new mode, it works again. I can
reproduce this behavior also with using bare xrandr, so I assume that this is
not a problem in kscreen. More info on that welcome, of course.
So git master has all the patches in place, and I'll look into backporting
these bits to Plasma 5.8.4.
*** This bug has been marked as a duplicate of bug 356864 ***
--
You are receiving this mail because:
You are watching all bug changes.
