Bug 484266 - Regular Task Manager (not icons-only) frequently becomes uninteractable on multi-monitor setup
Summary: Regular Task Manager (not icons-only) frequently becomes uninteractable on mu...
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.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-22 17:49 UTC by Nicolas F.
Modified: 2024-04-12 21:23 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 Nicolas F. 2024-03-22 17:49:53 UTC
SUMMARY

I have a 1920x1080 secondary monitor, and a 2560x1440 primary monitor. The task manager (regular version, not icons-only version) frequently no longer responds to clicks or hover of the mouse on the primary monitor (but not the secondary monitor) until the panel is manually edited and resized. This started happening with Plasma6. Tray icon can still be interacted with as can the clock, but start menu can't. Panel is non-floating.

STEPS TO REPRODUCE
1. Have two monitors of different resolutions. Add a panel on the primary monitor, switch it to non-floating, set the task manager to the regular version.
2. Use the system for a while

OBSERVED RESULT

Entries in the task manager can no longer be clicked or interacted with in other ways. They still update when otherwise focused though.

EXPECTED RESULT

Task manager doesn't break

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux 6.8.1, Wayland
(available in About System)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION

This does not happen on my laptop which only has one display.

AMDGPU, RX 7900 XT, Mesa 24.0.3, but hopefully a bug in which the panel clearly still renders properly but just doesn't know where the mouse cursor is is not driver dependent.
Comment 1 Nate Graham 2024-04-12 21:23:28 UTC
*** This bug has been marked as a duplicate of bug 483188 ***