https://bugs.kde.org/show_bug.cgi?id=472158
Bug ID: 472158
Summary: Dragging Firefox tabs on to Desktop under Wayland is
incredibly, incredibly slow. Works great in x11.
Classification: I don't know
Product: kde
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: dekaymail+...@gmail.com
Target Milestone: ---
This is a Wayland deal breaker for me because I use this function all the time.
Dragging a Firefox tab onto the desktop to create a separate window for it is
too slow to be useable
STEPS TO REPRODUCE
1. Have multiple tabs open within one window in Firefox.
2. Drag one of the tabs onto the desktop so it separates that tab into its own
window.
3. A thumbnail of the tab being dragged appears at the drop location
OBSERVED RESULT
The dragged tab takes many seconds to appear at the drop location and the time
seems to get longer each time you try. I have waited over a minute before
canceling (see below).
EXPECTED RESULT
The dragged tab should open instantly in a new window at the drop location on
the desktop.
SOFTWARE/OS VERSIONS
Linux version: 6.3.8-arch1-1 (Arch system up to date as of early July 2023)
KDE Plasma Version: 5.27.5-1
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
Hardware: Ryzen 1700 GPU with AMD RX560 GPU and amdgpu driver
Mesa version: 23.1.3-1
ADDITIONAL INFORMATION
- The more times you try to do this, the slower it seems to get. And if you
click on the desktop while waiting for the operation to complete, it cancels
it. The thumbnail it creates in the drop area disappears.
- Running "top" while trying this shows no sudden spike in cpu usage
- This works instantaneously on x11
- Right click on tab -> Move Tab -> Move tab to new window works
instantaneously on Wayland
- Drag and drop of a tab from a native KDE application like Konsole works
instantaneously
- Wayland otherwise seems to work well
- The last time I tried Wayland was many months ago (can't remember exactly how
long) and this problem was there at that time as well so this is not new. I
didn't file a bug then because I thought it was just general Wayland breakage.
--
You are receiving this mail because:
You are watching all bug changes.
