Bug 464568 - Plasma Wayland randomly freezes
Summary: Plasma Wayland randomly freezes
Status: RESOLVED DUPLICATE of bug 463353
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: 5.26.5
Platform: Neon All
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-20 21:21 UTC by lidraritri
Modified: 2023-01-21 10:23 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lidraritri 2023-01-20 21:21:59 UTC
SUMMARY
During Plasma sessions based on Wayland the system suddenly freezes and becomes completely unresponsive for about 20 to 30 seconds after which it *usually* becomes responsive again while in other cases I need to force a reboot. It only happens when using Wayland, X11 sessions doesn't seem to suffer from the same problem. Moreover, it actually does not cause a crash, it just freezes.

STEPS TO REPRODUCE
I really don't have a way to reproduce the issue since it happen pretty randomly and in an independent way with respect to what I'm doing.

OBSERVED RESULT
The interface becomes completely unresponsive.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.26
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.101.0 
Qt Version: 5.15.8
Graphics Platform: Wayland

ADDITIONAL INFORMATION
I'm on a Framework Laptop with Intel i7 12th Gen. I have a dual monitor setup with a Dell D300 Docking Station so I have installed DisplayLink drivers to handle the two monitors. I think it was worth mentioning since this is the reason why I'm using Wayland instead of X11 because I needed to set two different scaling for the laptop display and the two other monitors. However, the issue come up also when using the laptop without external monitors.
Comment 1 David Edmundson 2023-01-21 10:23:20 UTC
There's not enough to go on to leave this report open, it sounds like it could be 463353.

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