Bug 424002

Summary: Plasmashell hangs after some time when external display is connected
Product: [Plasma] plasmashell Reporter: Davy <just4kdebugs>
Component: generic-performanceAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: jeff.lemos.a, nate, noahadvs, plasma-bugs-null
Priority: NOR    
Version First Reported In: 5.17.5   
Target Milestone: 1.0   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Debug log of plasmashell
New crash information added by DrKonqi

Description Davy 2020-07-08 16:24:34 UTC
Created attachment 129980 [details]
Debug log of plasmashell

SUMMARY

After a certain amount of time plasmashell seems to hang for unknown reasons. This means that no interaction with the panels is possible anymore and the desktop doesn't update (only the windows rendered above are visible).

Certain features of the desktop are functional when the hang occurs. This includes the task switcher and global shortcuts like for invoking krunner or the task manager. But sometimes, krunner is affected as well. Sometimes it seem to affect the stability of unrelated applications (Chromium browser, Elektron Apps) as well.

This behavior is present at least since March 2020.


STEPS TO REPRODUCE
Sadly I don't know how I can reproduce this behavior. But it seems to be related with some kind of user activity.
It's also my work system so I don't want to tinker too much. I tried my best to give you as much information as possible.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: NixOS 5.4.50 20.09pre233323.dc80d7bc4a2 64 bit
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.7

The hardware is a Thinkpad T470p with Intel graphics. There's always plenty of RAM and CPU available. I'm always using one or two external displays.

ADDITIONAL INFORMATION

Once I kill/restart the plasmashell process, everything is functional again.

I tried to turn on some logging but there are no traces of an error for me. I attached the output of the following command line until the hang behavior occurs:

env QT_LOGGING_RULES="* = true; qt.scenegraph.* = false; qt.quick.hover.trace = false; qt.qpa.events = false; qt.qpa.input.* = false; qt.quick.mouse.target = false;" plasmashell --replace 2>&1 | gawk '{ print strftime("[ %T ]%t") $0 }' > plasma_report.log

I filtered some very noisy events since they seemed to be rather unrelated.
Comment 1 jeferson 2020-07-15 18:10:17 UTC
Created attachment 130143 [details]
New crash information added by DrKonqi

plasmashell (5.18.5) using Qt 5.14.2

- What I was doing when the application crashed:

It usually happens when I am doing actions which involve the workspace or managing windows.

- Unusual behavior I noticed:

plasmashell gets killed, then either the screen goes black and then returns with plasmashell restarted or if it cant be restarted I have to access the Desktop by Krunner

- Custom settings of the application:

Aritim-Dark global theme
Arc-Dark Plasma style
Materia Manjaro  Dark Solid window decoration
Breeze GTK-2 application style
Dark-Oympic GTK-3 application style

-- Backtrace (Reduced):
#5  0x00007f46c88ad971 in ProcessDraw<std::integral_constant<bool, true>, std::integral_constant<bool, false>, std::integral_constant<bool, false>, std::integral_constant<bool, false>, std::integral_constant<bool, false>, std::integral_constant<bool, true> >(SWR_CONTEXT*, DRAW_CONTEXT*, unsigned int, void*) (pContext=<optimized out>, pDC=0x555a32832240, workerId=<optimized out>, pUserData=<optimized out>) at ../mesa-20.0.8/src/gallium/drivers/swr/rasterizer/core/context.h:475
#6  0x00007f46c8904bc2 in WorkOnFifoFE(SWR_CONTEXT*, unsigned int, unsigned int&) (pContext=pContext@entry=0x555a317ec680, workerId=workerId@entry=0, curDrawFE=@0x7f469f3fdbdc: 97) at ../mesa-20.0.8/src/gallium/drivers/swr/rasterizer/core/threads.cpp:764
#7  0x00007f46c8907271 in workerThreadMain<true, true>(void*) (pData=<optimized out>) at ../mesa-20.0.8/src/gallium/drivers/swr/rasterizer/core/ringbuffer.h:87
[...]
#9  0x00007f46d0263eaa in start_thread (arg=<optimized out>) at pthread_create.c:479
#10 0x00007f46d0196b2f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Comment 2 Davy 2021-01-02 11:40:17 UTC
I found out that it only happens when I use an external display on the internal graphic port of the Thinkpad T470p.

When I don't use an external display, this bug doesn't occur. The same thing when I'm using the ports of the docking station.
Comment 3 Noah Davis 2023-08-09 21:16:57 UTC
Is this still a problem for you with Plasma 5.27?

The only interesting thing I saw in the backtrace was this:

> #9  0x0000555a2dc54ac7 in PanelView::event(QEvent*) (this=0x555a2e475a90, e=0x7ffe0930e340) at /usr/src/debug/kde-plasma/plasma-workspace-5.18.5-r1/plasma-workspace-5.18.5/shell/panelview.cpp:976
Comment 4 Bug Janitor Service 2023-08-24 03:45:28 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 5 jeferson 2023-08-24 13:41:20 UTC
Indeed after some updates I am not seeing that problem anymore