https://bugs.kde.org/show_bug.cgi?id=376155
--- Comment #2 from Yichao Yu <yyc1...@gmail.com> ---
I suspect that this is caused by
```
commit 9934f5b57537feae54afd0c4366c90253638ada2
Author: Martin Gräßlin <mgraess...@kde.org>
Date: Fri Sep 16 14:27:50 2016 +0200
Properly implement maximize of ShellClient
Summary:
This brings some more checks from Client to ShellClient. Thus the
states are better adjusted.
Unfortunately the X11 implementation is also slightly adjusted, so could
create regressions in worst case.
BUG: 368393
Reviewers: #kwin, #plasma_on_wayland
Subscribers: plasma-devel, kwin
Tags: #plasma_on_wayland, #kwin
Differential Revision: https://phabricator.kde.org/D3507
```
And I assume this might be one of the "worst case".
The following patch seems to fix the issue for me locally though I'm not sure
if it's the right solution. I'll submit a review if no one proposed a better
solution in a few days.
```
diff --git a/geometry.cpp b/geometry.cpp
index 64b5d67ca..420549aeb 100644
--- a/geometry.cpp
+++ b/geometry.cpp
@@ -3333,11 +3333,11 @@ void AbstractClient::setQuickTileMode(QuickTileMode
mode, bool keyboard)
m_quickTileMode = QuickTileNone; // Temporary, so the maximize
code doesn't get all confused
setGeometry(electricBorderMaximizeGeometry(keyboard ?
geometry().center() : Cursor::pos(), desktop()), geom_mode);
}
+ setMaximize(false, false);
+
// Store the mode change
m_quickTileMode = mode;
- setMaximize(false, false);
-
emit quickTileModeChanged();
return;
```
--
You are receiving this mail because:
You are watching all bug changes.
