When I maximize Google Chrome while it is using its own window decorations, the client side minimize/maximize/close buttons disappear. When tested with other WMs, this doesn't happen. OS: Kubuntu 16.10 Reproducible: Always
We don't have any control over Chrome's client side decoration. AFAIK this problem exists because of the progress indicator which Chrome interprets as "I'm on Unity" and hides the buttons. This is a pure bug by Chrome, it should use XDG_CURRENT_DESKTOP env variable instead. Please report to Chrome developers - there is nothing we can do about this.
*** Bug 371025 has been marked as a duplicate of this bug. ***
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 other window managers (IceWM) and KWin 5.5 have no such problem? A workaround that I found, is to remove libunity: $ sudo apt remove libunity9
(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, but of Plasma providing a dbus service previously only used in Unity. Apparently Chrome interprets the availability of that service as "I'm in Unity" instead of using the XDG_CURRENT_DESKTOP. Thus it removes the title bar as that's what's needed in Unity. > > A workaround that I found, is to remove libunity: > $ sudo apt remove libunity9 Which shows the problem is in Chrome: they misdetect the desktop.
(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 the desktop. But I can have libunity installed and it still works with IceWM!
> 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.