Bug 483494 - When dragging a file into Chromium forced into native Wayland mode, it stops responding to the mouse
Summary: When dragging a file into Chromium forced into native Wayland mode, it stops ...
Status: RESOLVED DUPLICATE of bug 482142
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: master
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-13 23:14 UTC by Konstantin
Modified: 2024-05-15 23:03 UTC (History)
7 users (show)

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


Attachments
vid (3.83 MB, video/webm)
2024-04-10 03:05 UTC, Konstantin
Details
Similar bug on my arch linux KDE (3.04 MB, video/mp4)
2024-05-02 16:46 UTC, Wassim Akkari
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Konstantin 2024-03-13 23:14:09 UTC
If you drag an image or any file from Dolphin to another window − this window stops responding to the mouse cursor (clicking, hovering, does not respond to the mouse at all). The keyboard shortcuts work and you can exit or do something without the mouse.

In 100% of cases, the bug appears if you drag a Dolphin image or any file to Chromium.

The problem appeared around the beginning of February 2024. I thought this would no longer be the case in Plasma 6, but unfortunately the bug has persisted.

chrome://flags/ −> Preferred Ozone platform <Wayland>.

Operating System: Arch Linux 
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 32 × Intel® Core™ i9-14900KF
Memory: 62.6 ГиБ of RAM
Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2
Manufacturer: ASUS
Comment 1 Nate Graham 2024-04-09 22:10:53 UTC
Does this only happen when you drag to Chromium, or to other windows too? If so, which other windows?

If it's just Chromium, what happens if you run it in XWayland move rather than forcing it to native Wayland mode?
Comment 2 Konstantin 2024-04-10 03:04:34 UTC
If I switch Chromium to x11, then dragging files works and the mouse works fine. chrome://flags/ −> Preferred Ozone platform <x11>. But then there are a lot of other problems. Everything works more stable in Preferred Ozone platform <Wayland>. The problem is only with dragging files, I'll describe it in more detail below.

I'm attaching a video. If I drag absolutely any file into the browser window, it does not respond to the mouse. If you then drag any file into the browser window and wait for it to react to it, BUT do not release this file, but return it back to Dolphin, then Chromium works fine again and reacts to the mouse. But if you drag the file to Chromium again, the problem repeats. You need to drag any file to Chromium again, hold it over the window, but do not release the left mouse button and return it back to Dolphin.

And so it is every time I transfer any file to Chromium. This problem occurs only in Chromium and in 100% of cases.
Comment 3 Konstantin 2024-04-10 03:05:14 UTC
Created attachment 168325 [details]
vid
Comment 4 Konstantin 2024-04-10 03:10:30 UTC
The video shows that the cursor freezes, but nothing freezes. It also moves smoothly, it's just that Chromium doesn't react to it. I was recording a video in Spectacle. Please add the ability to customize video recording settings to Spectacle. Otherwise, it sets the settings automatically and the frame rate drops very much (it is dynamic) if I move only the mouse.
Comment 5 Nate Graham 2024-04-11 15:46:22 UTC
Thanks. This is either a problem with Chromium's native Wayland mode, or a problem in KWin's. I'll let the KWin developers determine from here which one it is.
Comment 6 Wassim Akkari 2024-05-02 16:46:20 UTC
Created attachment 169109 [details]
Similar bug on my arch linux KDE

I would like to input on this I have a similar bug but it's triggered differently, when I select any portion of text and drop it inside chrome the mouse gets stuck and I can't click anything anymore until I kill chrome, this happens only on KDE I tried the same thing on Gnome with Wayland enabled and it doesn't happen.

Steps to reproduce the problem
    1/ start chromium with -enable-features=UseOzonePlatform -ozone-platform=wayland
    2/ Go to any webpage (eg. wikipedia)
    3/ select any chunk of text using the cursor
    4/ Drag the text inside and drop it anywhere inside chromium

My Setup:

System:
  Kernel: 6.8.8-2-cachyos arch: x86_64 bits: 64 
  Desktop: KDE Plasma v: 6.0.4 tk: Qt v: 6.7.0 wm: kwin_wayland vt: 1 dm: SDDM
  Distro: CachyOS base: Arch Linux

GPU:

Graphics:
  Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] vendor: Lenovo
  driver: i915 v: kernel arch: Gen-12.2 ports: active: eDP-1 empty: DP-1,DP-2
    
  Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Lenovo
  driver: nvidia v: 550.78 arch: Ampere pcie: speed: 2.5 GT/s lanes: 8 ports:
   
  Monitor-1: HDMI-A-1 pos: right res: 1920x1080 size: N/A modes: N/A
  Monitor-2: eDP-1 pos: primary,left res: 2560x1600 size: N/A modes: N/A
Comment 7 Wassim Akkari 2024-05-03 06:11:51 UTC
And to answer Nate question, In my case when you drag text from chrome to other applications windows or to other chrome tabs or from outside chrome ti chrome nothing happens, the issue only triggers when you drag something (picture or text) from the same tab and you drop it in the same tab.
Comment 8 matiux 2024-05-05 22:33:21 UTC
Same situation.
Every time I accidentally drag, it freezes

Linux Arch
KDE6 (Wayland)
Chrome stable Version 124.0.6367.118 (Official Build) (64-bit)
Comment 9 Nate Graham 2024-05-15 23:03:33 UTC

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