https://bugs.kde.org/show_bug.cgi?id=377901
Kenneth Lakin <kennethla...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kennethla...@gmail.com
--- Comment #3 from Kenneth Lakin <kennethla...@gmail.com> ---
This affects me, too, exactly as described.
I'm using 32-bit ~x86 Gentoo Linux on a 32-bit system.
KWin/Plasma 5.9.2
QT 5.7.1 and 4.8.7
xorg 7.4-r2
Wayland is not installed.
I'm using kwin_x11 rather than kwin_wayland
If I refrain from either Alt+Tabbing _or_ switching virtual desktops, kwin is
perfectly happy to keep resizing and moving windows. If I do _either_ of those
things, kwin emits a single "QXcbConnection: XCB error: 3 ... " message to
stdout every time I try to move or resize a window. Alt+Tab doesn't produce any
messages to stdout.
While kwin is failing to resize/move windows, I can:
Alter window Z-order (either by clicking on a window's titlebar or using the
raise/lower window keyboard shortcuts)
Switch between virtual desktops.
Create new windows.
Close windows.
Start krunner (but unlike normal (where it automatically gets keyboard focus) I
have to manually click it for it to have keyboard focus).
The only "fix" is to restart kwin_x11 and never press alt+tab, or switch
virtual desktops. :(
I've tried restarting kwin_x11 by doing all of
killall kwin_x11 ; sleep $X ; kwin_x11 &
kwin_x11 --replace &
kstart5 -- kwin_x11 --replace
kwrapper5 kwin_x11 --replace &
None of them fix the problem.
I've gotta use this computer for work, so I'm going to begrudgingly go throw
all my state in a trash fire and restart KDE. I politely suggest that someone
fire up a VM and leave it running for ~49.5 days to debug this. Some of us have
long-running systems that we don't want to have to restart for no reasonable
reason.
(Don't get me wrong. As a programmer, I get that KDE is a complicated system.
I'm also fully aware that most folks working on it are volunteers. :) I'm also
aware that the faulty component might not even be _in_ KDE. But, like, _Windows
95_ was affected by this sort of error. Everyone who _ever_ works with anything
having to do with time should have learned from that. ;))
I'm more than happy to provide additional information upon request. :)
--
You are receiving this mail because:
You are watching all bug changes.
