Bug 509331 - plasma6.5-dev: dragging a picture in a chrome based browser makes the current tab unusable
Summary: plasma6.5-dev: dragging a picture in a chrome based browser makes the current...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: Wayland drag-and-drop (other bugs)
Version First Reported In: 6.4.80
Platform: Other Linux
: HI major
Target Milestone: ---
Assignee: KWin default assignee
URL: https://issues.chromium.org/issues/44...
Keywords: regression
Depends on:
Blocks:
 
Reported: 2025-09-09 22:40 UTC by slartibart70
Modified: 2025-09-28 12:46 UTC (History)
4 users (show)

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


Attachments
no-clickedy-clicks (419.38 KB, video/webm)
2025-09-16 12:34 UTC, slartibart70
Details
no click will be recognized - video (985.42 KB, video/webm)
2025-09-19 14:19 UTC, gelberknopff
Details

Note You need to log in before you can comment on or make changes to this bug.
Description slartibart70 2025-09-09 22:40:21 UTC
The current nightly build of plasma 6.5-dev breaks chrome-based browsers when clicking-and dragging a picture This also happens in electron-based UIs, like vscode, here e.g. drag an icon in the sidebar.

The effect is, that the current browser-tab crashes, a reload (by context-menu on the tab itself) does not help
The mouse-cursor cannot click links any more or select text, scrolling is still possible.
(Seems like the end-drag event gets lost somehow?)
You can of course close the tab and reopen the page in a new tab, but something easy like this does not work in vscode. Here you need to reload the whole vscode application.

Interestingly, firefox behaves properly.

One thing to note is, that the dragging itself does not really drag the picture. Its more like a small preview-icon appears in the middle of the original picture, but this mini icon itself is also stuck and not draggable
Same for firefox, but firefox recovers and is still usable afterwards

This problem should be addressed quickly, because dragging items in chrome or vscode happens quite often (in chrome more by 'accident', in vscode intentionally)

Tested with:
edge, Version 140.0.3485.54 (Official build)
chromium, Version 140.0.7339.80 (Official Build) 
brave, 1.81.137 / chromium 139.0.7258.158
firefox 142.0.1
===
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.80
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.1
Kernel Version: 6.16.5-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Comment 1 Nate Graham 2025-09-16 12:08:53 UTC
I can't reproduce this issue with today's git master and 140.0.7339.127 (Official Build) (64-bit). Can you update and try again?

If you can reproduce it, please write specific steps to reproduce that can be followed to the latter which will reproduce the issue. Thanks!
Comment 2 slartibart70 2025-09-16 12:29:41 UTC
i did todays update, also using chromium  140.0.7339.127 
Still the same problem

One thing has changed: i can now drag the mini-image around (while still clicking), but releasing the mouse-button does not register any clicks on the webpage any more (scrolling is still working)
Comment 3 slartibart70 2025-09-16 12:34:22 UTC
i attached a video.
After releasing the mouse button, the hand-pointer is still active, any left/right clicks (anywhere on the page) are not registered
Comment 4 slartibart70 2025-09-16 12:34:55 UTC
Created attachment 184977 [details]
no-clickedy-clicks
Comment 5 slartibart70 2025-09-19 13:36:05 UTC
one thing to note:
chrome/brave/vscode must run as wayland (check with 'xlsclients' if not sure)
Maybe it's related to my gpu?:  (depends which gpu Nate was checking on when trying to reproduce)

Operating System: Fedora Linux 42
KDE Plasma Version: 6.5.80
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics
Memory: 64 GiB of RAM (58,5 GiB usable)
Graphics Processor: AMD Radeon 780M Graphics
Manufacturer: LENOVO
Product Name: 21K5000JGE
System Version: ThinkPad P14s Gen 4
Comment 6 gelberknopff 2025-09-19 14:18:35 UTC
I can reproduce it on Fedora (KDE 6.5.80) Brave and Chromium: 

Operating System: Fedora Linux 42
KDE Plasma Version: 6.5.80
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4070 Ti (Driver Version: 580.82.07)
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D54
System Version: 2.0


But i can't reproduce it on CachyOS (KDE 6.4.5)

Operating System: CachyOS Linux 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 64 GiB of RAM (62,7 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4070 Ti
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D54
System Version: 2.0

I ask a friend on Kubuntu, he can't reproduce it on this system either. 
(Sadly further no specs right now).


I will also attach a small video.

After release, no click will be recognized in this tab, also no "mouse over" animation.
Comment 7 gelberknopff 2025-09-19 14:19:34 UTC
Created attachment 185099 [details]
no click will be recognized - video
Comment 8 gelberknopff 2025-09-19 14:36:19 UTC
I switched to KDE 6.4.4 on the same Fedora System. 

And there, i can't reproduce it. 

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4070 Ti
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D54
System Version: 2.0
Comment 9 Leia 2025-09-19 16:47:45 UTC
can also reproduce here, fresh kwin master build, doesn't happen on 6.4

Operating System: Arch Linux 
KDE Plasma Version: 6.4.90
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.12.47-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 4600G with Radeon Graphics
Memory: 32 GiB of RAM (30.7 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUS
Comment 10 Leia 2025-09-19 17:41:46 UTC
i git bisected it to this commit: https://invent.kde.org/plasma/kwin/-/commit/b5f3cb2b77ba4e8611a332910be808bd8f75b1c7
Comment 11 Bug Janitor Service 2025-09-24 06:37:25 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/8145
Comment 12 Vlad Zahorodnii 2025-09-24 11:23:41 UTC
I filed a chromium bug report at https://issues.chromium.org/issues/447037092
Comment 13 Vlad Zahorodnii 2025-09-24 19:07:32 UTC
Git commit 91bdecaf99d178c0469234e3264a59f67c668109 by Vlad Zahorodnii.
Committed on 24/09/2025 at 18:32.
Pushed by vladz into branch 'Plasma/6.5'.

Revert "wayland: Check current drag and drop action"

This reverts commit b5f3cb2b77ba4e8611a332910be808bd8f75b1c7.

This caused a regression in Chromium. It appears that Chromium gets
confused by a dnd_drop_performed event when a dnd session is cancelled,
i.e.

  wl_data_source.dnd_drop_performed
  wl_data_source.cancelled

M  +0    -164  autotests/integration/dnd_test.cpp
M  +2    -1    src/wayland/seat.cpp

https://invent.kde.org/plasma/kwin/-/commit/91bdecaf99d178c0469234e3264a59f67c668109
Comment 14 Nate Graham 2025-09-26 00:18:39 UTC
Resolving because that fixes the issue from our side. Once the Chromion bug is resolved, we can re-evaluate.
Comment 15 slartibart70 2025-09-28 12:46:52 UTC
just a question to Vlad:
this is only on the plasma6.5 branch - wouldn't it be a good idea to integrate into master as well?