Bug 431729

Summary: Visual issues after hibernation with multi monitor setup: Panel spans over to 2nd monitor and wallpapers change
Product: [Plasma] kwin Reporter: postix <postix>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: postix
Priority: NOR Flags: vlad.zahorodnii: Wayland+
Version First Reported In: 5.20.5   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screenshots for a)-d)
journalctl.log (sanitized)

Description postix 2021-01-17 12:21:56 UTC
Created attachment 134964 [details]
Screenshots for a)-d)

SUMMARY

I have a multi monitor setup consisting of two screens, where the external monitor is plugged in to a laptop.

a) When the laptop becomes closed, its screen turns off as expected and all windows move to the external monitor.
b) Next I turn off the external monitor, which makes the laptop finally hibernating by itself.
c) Then I turn on the laptop again and log in: The desktop wallpaper has changed and the panel reaches out of the screen.
d) Finally I turn on the external monitor again and also find here a different wallpaper (I had set some time earlier) and the rest of the panel.


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Kernel Version: 5.10.2-2-MANJARO
Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.10 driver: modesetting resolution: 1: 2560x1440~60Hz 2: 3840x2160~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.3.1


ADDITIONAL INFORMATION
Scaling: 2.0
Comment 1 postix 2021-01-17 12:24:38 UTC
Created attachment 134965 [details]
journalctl.log (sanitized)
Comment 2 postix 2021-01-17 13:13:29 UTC
I have to logout and login back again to "repair" this issue.


Also I don't see it on Wayland, however, this may be due to

```
[ 6756.042959] thunderbolt 0-3: device disconnected
[ 6756.216831] traps: kwin_wayland[20001] general protection fault ip:7feb7728bb63 sp:7ffce23911b0 error:0 in KWinWaylandDrmBackend.so[7feb77277000+24000]
[ 6756.217177] audit: type=1701 audit(1610883855.103:482): auid=1001 uid=1001 gid=1002 ses=12 subj==unconfined pid=20001 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1
--
[ 6884.792882] thunderbolt 0-3: device disconnected
[ 6884.993185] kwin_wayland[21022]: segfault at 2c00000785 ip 0000002c00000785 sp 00007fff5939ff38 error 14 in kwin_wayland[55cb33582000+12000]
[ 6884.993195] Code: Unable to access opcode bytes at RIP 0x2c0000075b.
[ 6884.993264] audit: type=1701 audit(1610883982.993:675): auid=1001 uid=1001 gid=1002 ses=14 subj==unconfined pid=21022 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1
```

kwin_wayland segfaulting, when the external monitor turns off. Could be #420160, #390306, #415240
Comment 3 Vlad Zahorodnii 2021-01-18 08:11:45 UTC
Can you check core dumps by running coredumpctl list kwin_wayland or maybe attach a debugger to kwin to get the backtrace of the crash?
Comment 4 postix 2021-01-18 11:15:05 UTC
(In reply to Vlad Zahorodnii from comment #3)
> Can you check core dumps by running coredumpctl list kwin_wayland or maybe
> attach a debugger to kwin to get the backtrace of the crash?

Well, this is actually a different issue; I just tried to emphasize that I only could reproduce it (always) on X11, while I did not see this issue on kwin_wayland most likely due to the crash.

I had already posted a stacktrace for a similar issue here: 
https://bugs.kde.org/show_bug.cgi?id=419728#c4
but I may do it again for this issue when I find the time to build kwin_wayland debug again this week (hopefully).
Comment 5 Bug Janitor Service 2021-02-02 04:33:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2021-02-17 04:33:16 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 7 postix 2021-02-17 10:53:34 UTC
Still an issue, also on boot; I will check it again and try to get the relevant debug info once I reinstalled the system after Plasma 5.21.1 comes out.