Bug 483447 - icons only task manager unresponsive to user input after a period of time
Summary: icons only task manager unresponsive to user input after a period of time
Status: RESOLVED DUPLICATE of bug 483188
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager widgets (show other bugs)
Version: 6.0.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-13 15:14 UTC by zxq5
Modified: 2024-03-14 16:24 UTC (History)
2 users (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 zxq5 2024-03-13 15:14:25 UTC
SUMMARY

STEPS TO REPRODUCE
1. use the plasma desktop for any extended period of time, from my experience this can take anywhere between a few minutes up to a few hours
2. it generally happens after clicking the icon to open a window

OBSERVED RESULT
icons only task manager becomes unresponsive, the panel itself seems to be fully responsive, however clicking on any of the icons, whether that be left or right click seems to have no effect

EXPECTED RESULT
clicking the icon launches the given application

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-zen1-1-zen (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
opening and closing a window through the window buttons still results in the indicator for that app changing on the task manager. only the input seems to be broken
Comment 1 Nate Graham 2024-03-13 21:03:50 UTC
What GPU are you using? Is it from AMD? And do you have 2 or more screens?
Comment 2 zxq5 2024-03-13 22:34:27 UTC
(In reply to Nate Graham from comment #1)
> What GPU are you using? Is it from AMD? And do you have 2 or more screens?

I've got two monitors and yes I'm running an AMD card (6700XT)
Comment 3 Nate Graham 2024-03-14 16:24:34 UTC
Thanks, looks like it's Bug 483188.

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