SUMMARY Currently, Chromium-based browsers require running natively on Wayland to provide pinch-to-zoom and swipe gestures. Although still not enabled by default like in Mozilla Firefox, some users report that they've been running Chromium-based browsers successfully under GNOME Wayland. See an example here https://www.reddit.com/r/linux/comments/1cklr5b/want_pinch_to_zoom_swipe_gestures_in_brave_chrome However, in my testing on latest Fedora 40 with Plasma 6.0.4, the browser freezes and eventually crashes on force-quitting whenever a click and dragging action is performed. It seems the browser window becomes unresponsive to mouse inputs, although it still responds to keyboard inputs. But when closing the window the browser eventually crashes. STEPS TO REPRODUCE 1. Set #ozone-platform-hint flag to "Auto" or "Wayland" in chromium:///flags and restart the browser 2. Drag some webpage element around or drag a URL/bookmark into the bookmarks bar OBSERVED RESULT The browser is frozen to mouse inputs when a dragging action is performed. EXPECTED RESULT The browser should not freeze or crash when clicking and dragging. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LG Electronics Product Name: 15Z90Q-G.AA52P System Version: 0.1
Created attachment 169221 [details] Screen recording reproducing the issue During the demonstration I opened a new tab with the keyboard shortcut CTRL+T to showcase how the mouse click is unresponsive.
Especially because the issue is reproducible when dragging something from within the app itself, this is likely an issue in the app. But there's also a small chance it could be an issue in KWin, so I'm moving it there for the KWin devs to investigate.
In fact this is Bug 482142, which was just fixed for Plasma 6.1 *** This bug has been marked as a duplicate of bug 482142 ***