Bug 250462 - Windows shrink to minimum size when all outputs disabled
Summary: Windows shrink to minimum size when all outputs disabled
Status: RESOLVED DUPLICATE of bug 154365
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-07 17:26 UTC by kde2eran
Modified: 2010-10-10 17:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kde2eran 2010-09-07 17:26:18 UTC
Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

When all outputs are disabled, windows are resized to the smallest possible size. Later, when some output is connected, the windows remain tiny and the desktop is unusable until the windows are resized.

There are many cases where all outputs are temporarily disabled.
In software: while using the xrandr binary for managing displays.
In hardware: when the only active output is on an external output and you disconnect it (by pulling out the cable or by lifting the laptop out of the dock), some drivers will turn off that output in X. This happens on the ThinkPad T400s with DisplayPort, for example.

It seems to affect most windows, but sometimes not all of them. I'm not sure what's the pattern. In particular, after disconnecting and reconnecting the monitor, if I open a new window and then again disconnect and reconnect, the new window does *not* get resized.

See also bug 179722 about another case where windows are shrunk to minimum size.


Reproducible: Sometimes

Steps to Reproduce:
xrandr --output HDMI2 --off; sleep 1; xrandr --output HDMI2 --auto

Actual Results:  
All (or most) windows are minimizes to the smallest possible size.

Expected Results:  
Windows should reappear at the same size (if the same resolution was chosen), or resized the same as if there was a direct transition from the old resolution to the new resolution.
Comment 1 FiNeX 2010-10-10 17:51:47 UTC

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