Bug 448696

Summary:	on dual 4K monitor setup panels freeze and/or crashes
Product:	[Plasma] plasmashell	Reporter:	Alex <alex>
Component:	Panel	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED BACKTRACE
Severity:	crash	CC:	kde, notmart
Priority:	NOR
Version First Reported In:	5.23.5
Target Milestone:	1.0
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Alex 2022-01-18 09:36:17 UTC

SUMMARY
***
This is a (very) long standing bug, I just decided to report it because I see no progress between releases.

I have two 4K monitors, on the primary I've the default panel on the bottom, on the second I created a simple panel with just the task manager.
That panel almost always crashed, and when it doesn't crash it freezes becoming useless.
***

STEPS TO REPRODUCE
1.  two monitor setup (mine are 4K, I don't know if this important)
2.  create a panel on the secondary screen with just a few widgets (i.e.: only taskmanager)
3.  after a few minutes of usage the panel is not there anymore. Sometime it's there but frozen/useless

When I want to fix things (for a few minutes) I usually kill plasmashell and run it again

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Marco Martin 2022-01-18 10:22:19 UTC

Can you try to produce a backtrace when plasma actually crashes?

Comment 2 Alex 2022-01-18 10:46:44 UTC

I've no notifications that plasma crashes: at a certain point I just notice that the panel on the second screen is gone.

What can I do?

Comment 3 Bug Janitor Service 2022-02-02 04:37:39 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 4 Bug Janitor Service 2022-02-17 04:36:59 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 5 Alex 2022-02-17 09:36:03 UTC

The problem is happening less frequently with latest KDE release, but now there are other problems: https://bugs.kde.org/show_bug.cgi?id=450435

Comment 6 David Edmundson 2022-02-17 11:03:25 UTC

Any crashes need a backtrace to be actionable