Bug 346396

Summary: new windows have no border if previous window was tiled
Product: [Plasma] kwin Reporter: Judas C <ikkohime>
Component: decorationsAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mint (Ubuntu based)   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Judas C 2015-04-20 14:08:24 UTC 
kwin -v   gives :
Qt: 4.8.6
KDE Development Platform: 4.13.3
KWin: 4.11.11
When using the window tiling on screen edge (enabled in Workspace Behavior - Screen Edges), the next windows (of the same application) opened have no border (title bar has no problem). 




Reproducible: Always

Steps to Reproduce:
1. Tile window by dragging to screen edge
2. Open new window of same application
I could only reproduce for applications that remember window size.

Actual Results:  
New window has no borders (but has a normal title bar).


Expected Results:  
New windows should have borders, regardless of previous window's tiling.

Borderless windows can be resized horizontally and diagonally, but not vertically.
- Tiling the borderless window does nothing.
- Resizing horizontally does nothing.
- Resizing diagonally redraws borders.
- Minimizing-unminimizing does nothing.
- Maximizing-unmaximazing redraws borders.
Comment 1 Thomas Lübking 2015-04-20 14:35:19 UTC 
The window is stored/reopened in vertical maximization mode, check
   xprop _NET_WM_STATE
(the click the window)

That's not really a bug (the deco is encouraged to remove the resp. borders in that state), but likely (related to) bug #324957

There's slight inprovement in KDE5, but as long as KDE4 clients stay around, we cannot remove the WM side part of the "hack" (and even afterwards we'd need to check behavior of other clients itw.)

I'll dupe this to the KMainWindow bug.

*** This bug has been marked as a duplicate of bug 324957 ***
Comment 2 Judas C 2015-04-20 21:01:48 UTC 
xprop reports :
_NET_WM_STATE(ATOM) = _NET_WM_STATE_MAXIMIZED_VERT

Indeed it seems related to 324957

Too bad there's no fix. Thanks anyway.