https://bugs.kde.org/show_bug.cgi?id=371284
--- Comment #16 from Martin Gräßlin <mgraess...@kde.org> ---
Thanks, I expected to see:
ClientMessage event, serial 21, synthetic YES, window 0x3000005,
message_type 0x132 (_NET_WM_MOVERESIZE), format 32
which is not there. That means KWin does trigger the move. But why? There are
three different ways how KWin could trigger the move itself:
1. Right click window decoration -> More Actions -> Move
2. Click window decoration
3. Modifier+click anywhere on the window
Given the videos we can clearly rule out option 1. So somehow we go into
possibility 2 or 3. First thing: could it be that your tool triggers the meta
key? I have heard that some tablets do that. To rule out please change the
setting back to Alt.
For the possibility 2: please use xev again but slightly different. Use
xwininfo, click on krita. That will give you a window id. Now pass that to xev
with:
xev -id <id from xwininfo>
This will record all motion events. Thus we should hopefully be able to
reconstruct where the actual mouse events are, whether they go into the window
decoration, but we just don't see it.
--
You are receiving this mail because:
You are watching all bug changes.
