https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #17 from Bernd Steinhauser ---
FYI, a bug was reported upstream, the issue was found and got fixed:
https://bugs.freedesktop.org/show_bug.cgi?id=93746
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #16 from Bernd Steinhauser ---
(In reply to Thomas Lübking from comment #15)
> (In reply to Bernd Steinhauser from comment #14)
> > Around 60 fps, no change there. The left part of glxgears is still updated,
> > the right part is just a stat
https://bugs.kde.org/show_bug.cgi?id=357988
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #14 from Bernd Steinhauser ---
(In reply to Thomas Lübking from comment #13)
> If you
> - suspend the compositor
> - run glxgears
> - move it to be partially on the left and partially on the (middle) DP
> output and
> - re-attach the DP outp
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #13 from Thomas Lübking ---
- not even restarting the compositor (complete rebuild of GL context) "fixes"
it
- switching framebuffers (VT2 and back) fixes it
Ie. the part of the GL frontbuffer that is related to the particular output is
not
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #12 from Bernd Steinhauser ---
(In reply to Thomas Lübking from comment #11)
> That would suggest that switching the VT would alter the stack position of
> the plasma window, would it? Unlikely. Also interaction w/ the plasma window
> should
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #11 from Thomas Lübking ---
(In reply to Bernd Steinhauser from comment #10)
> somehow. And it seems like it creates that view with the wallpaper or the
> black screen that overlays the windows. Is that possible?
That would suggest that sw
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #10 from Bernd Steinhauser ---
Two more things that might be worth mentioning:
1. I switched to Console with the screen disconnected and back to see if it
occurs at well. After Reconnecting the screen, I saw screen corruption.
However, using
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #9 from Bernd Steinhauser ---
(In reply to Thomas Lübking from comment #8)
> - What's the state when just suspending the compositor - is the screen black
> as well?
No, that works fine.
> - What if you even "kwin_x11 --replace &"
Fine.
> - D
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #8 from Thomas Lübking ---
Sum up:
- kwin has a proper idea of the screen geometries
- not even restarting the compositor (complete rebuild of GL context) "fixes"
it
- switching framebuffers (VT2 and back) works
Smells a lot like an X11 dri
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #7 from Bernd Steinhauser ---
(In reply to Bernd Steinhauser from comment #5)
> During the disconnect, the only difference is the removed screen:
> -Number of Screens: 2
> +Number of Screens: 3
>
> +Name: DisplayPort-0
> +Geometry: 1920,0,1
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #6 from Bernd Steinhauser ---
Created attachment 96639
--> https://bugs.kde.org/attachment.cgi?id=96639&action=edit
glxinfo -l
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #5 from Bernd Steinhauser ---
(In reply to Thomas Lübking from comment #1)
> please dump "qdbus org.kde.KWin /KWin supportInformation" before and when
> this happens and ideally also when "resolving" the situation.
Wow, you're fast. :D
Duri
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #4 from Martin Gräßlin ---
can you please also output glxinfo -l
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #2 from Bernd Steinhauser ---
Created attachment 96637
--> https://bugs.kde.org/attachment.cgi?id=96637&action=edit
Log output when changing the screen
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #3 from Bernd Steinhauser ---
Created attachment 96638
--> https://bugs.kde.org/attachment.cgi?id=96638&action=edit
qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=357988
--- Comment #1 from Thomas Lübking ---
please dump "qdbus org.kde.KWin /KWin supportInformation" before and when this
happens and ideally also when "resolving" the situation.
Does restarting the compositor (SHIFT+Alt+F12, twice) "fix" it?
--
You are
17 matches
Mail list logo
