Summary: | window on external screen disappears when hibernating with external screen connected and resuming when it is not connected | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Martin Steigerwald <Martin> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 5.5.4 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | xwininfo -root -tree after external display disconnected, kmail window still exists |
Description
Martin Steigerwald
2016-04-13 06:48:16 UTC
kscreen is also 5.5.4 on the system. KF5 is compiled from git master as of last weekend. 5.6 Plasma is not yet available on Debian and free space on filesystem is small, so compiling it from master might exceed available free space. Yet I could compile parts of Plasma. I.e. just the window manager. I have kdesrc-build installed and setup. > It is not even in window bar in control panel. > Same with Konsole except process not running anymore. (Next time) check the output of "xwinfo -root -tree" on whether the window actually still exists (the taskbar and kwin are different processes) - the window is probably gone and that is because multiscreen is completely FUBAR in Qt5 (and plasmashell in addition, but that's not the problem here), ie. the bug is in the clients and caused by Qt. See bug #341497 - don't even try to trigger randr events of any type. *** This bug has been marked as a duplicate of bug 341497 *** Hmmm, I didn´t see any kwin_x11 crashes. Maybe not reported by Dr. Konqi? I will try the xwinfo -root -tree thing next time and post here. it's not a kwin crash. *every* qt5 client is prone to segfault or misbehave on randr events (in this case konsole/kmail) it's not really a dupe, just belongs into the same epic qt5 let-down Created attachment 98394 [details] xwininfo -root -tree after external display disconnected, kmail window still exists Thomas, the kmail window still exists but is not shown in window bar in control panel. I not reopening for now, since the QTBUG mentioned in bug #341497 also talks about disappeared windows. > xwininfo -root -tree xwininfo: Window id: 0xd5 (the root window) (has no name) Root window id: 0xd5 (the root window) (has no name) Parent window id: 0x0 (none) 150 children: 0x240004d "krunner": ("krunner" "krunner") 756x171+582+0 +582+0 0x7800001 (has no name): () 1x1+0+0 +0+0 0x1400001 (has no name): () 1x1+0+0 +0+0 0x481fa87 "Einrichten — KMail": ("kmail" "kmail2") 1181x797+2290+142 +2290+142 0x481fa85 "KMail": ("kmail" "kmail2") 484x462+2131+568 +2131+568 0x481fa83 "KMail": ("kmail" "kmail2") 776x33+2401+188 +2401+188 0x481fa81 "KMail": ("kmail" "kmail2") 348x131+2872+335 +2872+335 0x481fa7f "KMail": ("kmail" "kmail2") 455x193+2872+304 +2872+304 0x481fa7d "KMail": ("kmail" "kmail2") 334x645+2538+304 +2538+304 0x481fa79 "KMail": ("kmail" "kmail2") 22x22+2109+343 +2109+343 0x481fa77 "KMail": ("kmail" "kmail2") 477x207+2456+75 +2456+75 0x481fa75 "KMail": ("kmail" "kmail2") 417x324+2366+75 +2366+75 0x481fa73 "KMail": ("kmail" "kmail2") 484x631+2207+75 +2207+75 0x481fa71 "KMail": ("kmail" "kmail2") 668x552+2132+75 +2132+75 0xa000ba "Akregator": ("akregator" "akregator") 1920x1042+1920+38 +1920+38 0x481f9e8 "Lokale Ordner/[…]/_Posteingang — KMail": ("kmail" "kmail2") 1920x1042+1920+38 +1920+38 8 children: 0x481fa0c "KMail": ("kmail" "kmail2") 24x24+1209+609 +3129+647 0x481fa0a "KMail": ("kmail" "kmail2") 1920x937+0+75 +1920+113 0x481fa08 "KMail": ("kmail" "kmail2") 1920x38+0+37 +1920+75 0x481fa06 "KMail": ("kmail" "kmail2") 1920x37+0+0 +1920+38 0x481fa04 "KMail": ("kmail" "kmail2") 709x148+1211+864 +3131+902 0x481fa02 "KMail": ("kmail" "kmail2") 1920x30+0+1012 +1920+1050 0x481f9ec "KMail": ("kmail" "kmail2") 1920x937+0+75 +1920+113 1 child: 0x481f9ee "KMail": ("kmail" "kmail2") 1920x937+0+0 +1920+113 4 children: 0x481fa00 "KMail": ("kmail" "kmail2") 1x1+0+0 +1920+113 0x481f9fe "KMail": ("kmail" "kmail2") 5x937+478+0 +2398+113 0x481f9f2 "KMail": ("kmail" "kmail2") 1439x937+481+0 +2401+113 4 children: 0x481f9fc "KMail": ("kmail" "kmail2") 5x937+748+0 +3149+113 0x481f9fa "KMail": ("kmail" "kmail2") 100x30+0+0 +2401+113 0x481f9f8 "KMail": ("kmail" "kmail2") 750x937+0+0 +2401+113 0x481f9f4 "KMail": ("kmail" "kmail2") 688x937+751+0 +3152+113 1 child: 0x481f9f6 "KMail": ("kmail" "kmail2") 688x937+0+0 +3152+113 0x481f9f0 "KMail": ("kmail" "kmail2") 480x937+0+0 +1920+113 0x481f9ea "KMail": ("kmail" "kmail2") 160x160+0+0 +1920+38 0x1bab225 "KWin": ("kwin_x11" "kwin") 32x32+-32+-32 +-32+-32 Attached is the full window list with some window titles shortened due to privacy. please check "xwininfo" on such window - it apparenty fell out of management (maybe it's unmapped?) I restarted kmail, but Akregator still hides away, seems the window is unmapped:
> xwininfo -name "Akregator"
xwininfo: Window id: 0xa000ba "Akregator"
Absolute upper-left X: 1920
Absolute upper-left Y: 38
Relative upper-left X: 1920
Relative upper-left Y: 38
Width: 1920
Height: 1042
Depth: 24
Visual: 0xba
Visual Class: TrueColor
Border width: 0
Class: InputOutput
Colormap: 0xa000b9 (not installed)
Bit Gravity State: ForgetGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsUnMapped
Override Redirect State: no
Corners: +1920+38 --1920+38 --1920-0 +1920-0
-geometry 1920x1042+1920-0
Any further info you´d still want for that unmapped Akregator window? Otherwise I´d restart Akregator as well in order to use it again :) Sorry, you hopefully didn't wait too long ;-) Pretty much as predicted. The window got unmapped, thus fall out of management and thus is neither listed in the taskbar nor geometry corrected by the WM. It's completely ignored by everything (except the client, which may re-use it later on) The bottom line is really that Qt is completely broken reg. randr events (I doubt you'll see a non-qt5 client behaving this way) Pray for resolution in Qt 5.6 (which however has other regressions, *sigh*) Hmmm, thanks. I think it is of big importance to focus on the stability of the whole stack. In the end no matter whether its Qt or KF5 / Plasma causing the issue if the user experience is affected like that. I still think I do not yet have back the same stability as with latest KDE SC 4.14 or KDE 3.x, even though multiscreen always had issues for me. All the best to those who are into fixing these issues. Maybe only with Wayland this multiscreen stuff will finally work. Its about time. But what do I write there, I bet you know all this. Thanks again, Martin |