[palapeli] [Bug 366796] Ctrl-click should never, ever deselect all pieces
https://bugs.kde.org/show_bug.cgi?id=366796 --- Comment #7 from Stefan Majewsky --- (In reply to Ian Wadham from comment #6) > @Matthew: I had a brief look at how Palapeli is handling selects. It is > mostly home-grown and could be changed, but I won't be fixing it. See my > reply to Christoph. Yeah, that was a result of my naive over-engineering back in the day. It was on my laundry list to rip out that monstrosity and move to simple hard-coded mouse actions, see e.g. [1]. I don't have had the time for quite a while to hack on KDE (and if I had, i would push the KF5 port through first), but if anyone wants to cleanup this mess, then by all means go ahead. And CC me on the review request if you like some extra pair of eyes that's familiar with the codebase (or at least was 4 years ago). [1] https://majewsky.wordpress.com/2012/02/13/is-anyone-using-custom-mouse-actions-in-palapeli/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365333] no redraws with OpenGL compositing backends on amdgpu driver
https://bugs.kde.org/show_bug.cgi?id=365333 --- Comment #5 from Stefan Majewsky --- Addendum for point 1 in comment 4: Seeing that message again is especially critical in my situation since I moved from Catalyst to amdgpu, so the message did not apply to me when I saw it for the first time (when I set it to "Reuse screen content" while using the Catalyst driver). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365333] no redraws with OpenGL compositing backends on amdgpu driver
https://bugs.kde.org/show_bug.cgi?id=365333 --- Comment #4 from Stefan Majewsky --- Interesting. Then there may be two UI issues in there: 1. I did not see that message since it only appears when moving to that setting, not when the KCM starts out in it. 2. The message says "'Re-use screen content' causes severe performance problems on MESA drivers." It should be reworded to e.g. "severe performance and rendering problems", so people know what they're getting into when choosing that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365333] no redraws with OpenGL compositing backends on amdgpu driver
https://bugs.kde.org/show_bug.cgi?id=365333 --- Comment #2 from Stefan Majewsky --- Created attachment 5 --> https://bugs.kde.org/attachment.cgi?id=5&action=edit glxinfo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365333] no redraws with OpenGL compositing backends on amdgpu driver
https://bugs.kde.org/show_bug.cgi?id=365333 --- Comment #1 from Stefan Majewsky --- Created attachment 4 --> https://bugs.kde.org/attachment.cgi?id=4&action=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365333] New: no redraws with OpenGL compositing backends on amdgpu driver
https://bugs.kde.org/show_bug.cgi?id=365333
Bug ID: 365333
Summary: no redraws with OpenGL compositing backends on amdgpu
driver
Product: kwin
Version: 5.7.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: compositing
Assignee: kwin-bugs-n...@kde.org
Reporter: majew...@gmx.net
Last week, on my desktop PC, I switched from Catalyst to the new
xf86-video-amdgpu driver since the Catalyst driver suddenly started having
problems rendering some Steam games. After rebooting to switch to the new
kernel and X driver, I was greeted by a black screen.
Alt-Shift-F12 resolved the problem, and a few more attempts of Alt-Shift-F12
showed that the screen stopped redrawing whenever compositing was enabled. The
only exception is the mouse cursor which still moves appropriately, and changes
shape according to the surface beneath it.
I checked different settings in the kwincompositing KCM and found that the bug
only appears under the following settings:
* Rendering backend: OpenGL 2.0 or 3.1 (XRender works fine)
* OpenGL interface: GLX (EGL works fine)
* Tearing prevention: Reuse screen content ("Full screen repaints" and "Only
when cheap" appear to work fine in a short test)
The bug is really only hit when all three settings are set to the problematic
values. I first saw the problem in kwin 5.6 (after I installed the amdgpu
driver), and waited until this week to see if 5.7 would help, but the problem
is still reproducible.
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
