https://bugs.kde.org/show_bug.cgi?id=360719
kde@grau.net changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #17 from Viorel-Cătălin Răpițeanu ---
This issue doesn't seem to reproduce on my latest setup that's using the
proprietary nvidia driver (not even when I'm using 2 different input sources).
Since a lot changed during these 3 years, this
https://bugs.kde.org/show_bug.cgi?id=360719
Martin Gräßlin changed:
What|Removed |Added
CC||mwinth...@comcast.net
---
https://bugs.kde.org/show_bug.cgi?id=360719
Martin Gräßlin changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=360719
Martin Gräßlin changed:
What|Removed |Added
Component|general |core
--
You are
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #14 from Viorel-Cătălin Răpițeanu ---
(In reply to Bernd Steinhauser from comment #13)
> Can confirm this. Problem is that it happens randomly and thus is hard to
> track.
> I've often seen this happening when
https://bugs.kde.org/show_bug.cgi?id=360719
Bernd Steinhauser changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #12 from Viorel-Cătălin Răpițeanu ---
(In reply to Thomas Lübking from comment #11)
> The HW likely doesn't matter (at least not reg. the core issue of the
> pending menu)
> Try to disable the translucency
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #11 from Thomas Lübking ---
The HW likely doesn't matter (at least not reg. the core issue of the pending
menu)
Try to disable the translucency effect - while it doesn't see invoked, it might
still be prone to
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #10 from Viorel-Cătălin Răpițeanu ---
Created attachment 98057
--> https://bugs.kde.org/attachment.cgi?id=98057=edit
The computer specification used in the video.
I can still reproduce it on Qt 5.6. You must
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #9 from Martin Gräßlin ---
I fail to reproduce, but I'm also on Qt 5.6
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360719
Martin Gräßlin changed:
What|Removed |Added
Attachment #97962|text/x-log |text/plain
mime
https://bugs.kde.org/show_bug.cgi?id=360719
Thomas Lübking changed:
What|Removed |Added
Severity|grave |normal
--- Comment
https://bugs.kde.org/show_bug.cgi?id=360719
Viorel-Cătălin Răpițeanu changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #3 from Viorel-Cătălin Răpițeanu ---
Created attachment 97962
--> https://bugs.kde.org/attachment.cgi?id=97962=edit
Kwin qdbus log from the machine using bumblebee (intel + nvidia)
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #4 from Viorel-Cătălin Răpițeanu ---
Created attachment 97963
--> https://bugs.kde.org/attachment.cgi?id=97963=edit
Kwin qdbus log from a machine using nouveau (without acceleration)
On this machine the
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #2 from Viorel-Cătălin Răpițeanu ---
> SHIFT+Alt+F12
Disabling the compositor will recover the system state.
> Just to be sure - the popup remainder *is* a visual artifact, you cannot
> interact with it
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #8 from Viorel-Cătălin Răpițeanu ---
> Does it also happen when invoking the popup with Alt+F3?
I've tried this multiple times, and isn't.
The second popup remains drawn only when the first popup is invoked by
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #7 from Thomas Lübking ---
The "display glitch" is probably a red herring (you may be running out of
texture memory at some point)
On the bottom line, the unmap_notify event for the second popup is missed (so
the
https://bugs.kde.org/show_bug.cgi?id=360719
--- Comment #5 from Thomas Lübking ---
Ftr:
> Qt compile version: 5.6.0
nouveau is on the xrender compositor, the other system Sandybridge on GLX/3
=> "kcmshell5 kwincompositing", switch to xrender - does the issue remain?
20 matches
Mail list logo