https://bugs.kde.org/show_bug.cgi?id=361704

            Bug ID: 361704
           Summary: window on external screen disappears when hibernating
                    with external screen connected and resuming when it is
                    not connected
           Product: kwin
           Version: 5.5.4
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kwin-bugs-n...@kde.org
          Reporter: mar...@lichtvoll.de

I have KMail and Konsole and other apps on external screen. I hibernate the
laptop. Next morning I resume it at work, without external screen connected
(cause I hold a training where I don´t have one for the laptop). KMail window
is gone. Konsole window is gone.

Reproducible: Always

Steps to Reproduce:
1. Open an application window on external screen.
2. Hibernate.
3. Disconnect external screen
4. Resume

Actual Results:  
I had KMail and konsole window on external screen.

KMail window gone. It is visible on the laptop screen in any activity. It is
not even in window bar in control panel. Process still running.

Same with Konsole except process not running anymore.

Akregator which was on laptop screen at the time of hibernation still is
displayed correctly.

kscreen seems to have recognized properly that external screen is gone. At
least it is not displayed anymore in systemsettings. xrandr also only lists
laptop screen.

Expected Results:  
Windows that were on the external screen are relocated to the internal screen
when the external screen is not available anymore.

Basic rule for all of this: A window is always visible or minimized and can be
made visible. Never ever a window is not accessible as long as at least *one*
display is working.

kwin from Debian Experimental 4:5.5.4-2 on Debian Sid/Experimental. Qt 5.5.1.

system and xrandr info, for now without external display connected:

martin@merkaba:~> phoronix-test-suite system-info

Phoronix Test Suite v5.2.1
System Information

Hardware:
Processor: Intel Core i5-2520M @ 3.20GHz (4 Cores), Motherboard: LENOVO
42433WG, Chipset: Intel 2nd Generation Core Family DRAM, Memory: 16384MB, Disk:
300GB INTEL SSDSA2CW30 + 480GB Crucial_CT480M50, Graphics: Intel HD 3000
(1300MHz), Audio: Conexant CX20590, Monitor: P24T-7 LED, Network: Intel 82579LM
Gigabit Connection + Intel Centrino Advanced-N 6205

Software:
OS: Debian unstable, Kernel: 4.6.0-rc2-tp520-btrfstrim+ (x86_64), Desktop: KDE
Frameworks 5, Display Server: X Server 1.18.3, Display Driver: intel 2.99.917,
OpenGL: 3.3 Mesa 11.1.2, Compiler: GCC 5.3.1 20160409, File-System: btrfs,
Screen Resolution: 1920x1080


martin@merkaba:~> xrandr                         
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 344mm x 193mm
   1920x1080     60.00*+  59.93    50.00  
   1680x1050     59.95    59.88  
   1600x1024     60.17  
   1400x1050     59.98  
   1280x1024     60.02  
   1440x900      59.89  
   1280x960      60.00  
   1360x768      59.80    59.96  
   1152x864      60.00  
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       59.94  
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)


I am tempted to classify this as critical, cause making an application window
inaccessible could be a reason for data loss. Yet, one usually can still send
it a TERM signal and I´d hope it would prompt for any unsaved work to be saved
on the internal screen then. So leaving as normal for now.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to