Bug 499252 - Cannot move second window on taskbar from first grab
Summary: Cannot move second window on taskbar from first grab
Status: RESOLVED DUPLICATE of bug 491100
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: git-stable-Plasma/6.3
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-28 19:13 UTC by Eugene Savitsky
Modified: 2025-01-31 09:32 UTC (History)
2 users (show)

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

Attachments
video (1.06 MB, video/webm)
2025-01-28 19:13 UTC, Eugene Savitsky 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Savitsky 2025-01-28 19:13:24 UTC 
Created attachment 177771 [details]
video

1. Open two Firefox (or whatever) windows. Window 1 (W1) and window 2 (W2)
2. Try to move W1 to a different place on the taskbar.
3. Now try to move W2 - it does not, it behaves as W1 still has the focus/selected.
4. Select/focus some other window on the taskbar.
5. Now the W2 moves as expected.
Comment 1 David Redondo 2025-01-29 12:50:56 UTC 
Hi please attach your system info. this sounds alot like https://bugs.kde.org/show_bug.cgi?id=491100 which should have been fixed with Qt 6.8.1
Comment 2 Eugene Savitsky 2025-01-30 21:01:35 UTC 
(In reply to David Redondo from comment #1)
> Hi please attach your system info. this sounds alot like
> https://bugs.kde.org/show_bug.cgi?id=491100 which should have been fixed
> with Qt 6.8.1

Operating System: openSUSE Tumbleweed 20250127
KDE Plasma Version: 6.3.80
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.1
Kernel Version: 6.13.0-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics
Memory: 14,5 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 82RQ
System Version: IdeaPad 3 17ABA7
Comment 3 David Redondo 2025-01-31 09:32:45 UTC 

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