Bug 351161 - Window size changed (minimized) after a window shade/unshade
Summary: Window size changed (minimized) after a window shade/unshade
Status: RESOLVED DUPLICATE of bug 348064
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.3.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-10 17:18 UTC by Peter Tselios
Modified: 2015-08-19 08:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Tselios 2015-08-10 17:18:19 UTC
When I shade a window **of a KDE** application the shade function operates as it should exactly as it did in KDE 4.x. However, when "unshade" the window, it's size is not was before the shade, but it's the minimum size that a window my have. 

Reproducible: Always

Steps to Reproduce:
1. Open an application (like Konsole, or Knoqueror), but not in maximized mode. 
2. Shade the window. In some applications you will notice that the window is re-sized. 
3. "Unshade" the window. The Window now, has a different than the origianal size, usually a minimal one.

Actual Results:  
Window was not un-shaded with the correct size. 

Expected Results:  
Shade and "Unshade" should not alter the window size. 

This it not happening in GTK (or other toolkits) based applications. For example, Skype, Thunderbird and Firefox do not have that problem.
Comment 1 Thomas Lübking 2015-08-10 17:33:22 UTC
see bug #348064 - there's a major bug across however all applications (with a server side titlebar!)

in addition to that, Qt5 modal dialogs feel required to mess their and their mainwindows geometry on re-mapping (happens on unshading as well) but that's a bug in Qt5

try the behavior on xterm. same problem? dupe of above (fixed in 5.4)
Comment 2 Peter Tselios 2015-08-19 07:44:15 UTC
Sorry, I don't have xterm. It seems like a duplicated bug indeed.
Comment 3 Thomas Lübking 2015-08-19 08:17:54 UTC
Pre-emptive duping, please re-open if not fixed with the other bug.

*** This bug has been marked as a duplicate of bug 348064 ***