[kwin] [Bug 370985] Chrome doesn't show its own minimize/maximize/close buttons when maximized

https://bugs.kde.org/show_bug.cgi?id=370985 --- Comment #6 from Martin Gräßlin --- > But I can have libunity installed and it still works with IceWM! Start icewm in a Plasma session and chrome won't have it. It's a DBus protocol Chrome interacts with through libunity. --

[kwin] [Bug 370985] Chrome doesn't show its own minimize/maximize/close buttons when maximized

https://bugs.kde.org/show_bug.cgi?id=370985 --- Comment #5 from Peter Eszlari --- (In reply to Martin Gräßlin from comment #4) > > A workaround that I found, is to remove libunity: > > $ sudo apt remove libunity9 > > Which shows the problem is in Chrome: they misdetect

[kwin] [Bug 370985] Chrome doesn't show its own minimize/maximize/close buttons when maximized

https://bugs.kde.org/show_bug.cgi?id=370985 --- Comment #4 from Martin Gräßlin --- (In reply to Peter Eszlari from comment #3) > If there is nothing you can do, how does it come, that other window managers > (IceWM) and KWin 5.5 have no such problem? It's not a problem of

[kwin] [Bug 370985] Chrome doesn't show its own minimize/maximize/close buttons when maximized

https://bugs.kde.org/show_bug.cgi?id=370985 --- Comment #3 from Peter Eszlari --- Actuallly, if you open Chrome and go to "chrome://gpu", you will find two entries: Window manager | KWin XDG_CURRENT_DESKTOP | KDE If there is nothing you can do, how does it come, that

[kwin] [Bug 370985] Chrome doesn't show its own minimize/maximize/close buttons when maximized

https://bugs.kde.org/show_bug.cgi?id=370985 --- Comment #2 from Peter Eszlari --- *** Bug 371025 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 370985] Chrome doesn't show its own minimize/maximize/close buttons when maximized

https://bugs.kde.org/show_bug.cgi?id=370985 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED