[Bug]: Page hangs and becomes unresponsive after grabbing/dragging a link on Linux/Wayland (wayland_data_drag_controller error)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- linux
- Domain
- desktop
Research direction
Start by checking the Chromium Wayland drag-controller errors and upstream fixes linked in the issue, then identify how this Linux browser build incorporates its Chromium base. The report provides reproducible drag steps and the expected behavior: after a failed or aborted link drag, the page should remain clickable. No specific project file or test is named, so locating the affected integration will take familiarity with the build.
Written by the indexing model from the issue text.
Description
Operating system
Linux
Version
0.15.4.1 (deb)
Have you tested that this is not an upstream issue or an issue with your configuration?
- I have tried reproducing this issue in Chrome and it could not be reproduced there
- I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
- I have tried reproducing this issue in Helium with a new and empty profile using
--user-data-dircommand line argument and it could not be reproduced there
Description
[Bug]: Page hangs and becomes unresponsive after grabbing/dragging a link (Linux/Wayland) — wayland_data_drag_controller error logged
Related but distinct from imputnet/helium#2300 (Windows, drop-outside-WebView): this is on Linux/Wayland (GNOME/Mutter) and the journal shows the Wayland data drag controller failing to start the drag, after which the whole page stops accepting mouse input.
Crash ID
No response
How to Reproduce?
Steps to reproduce the behavior:
- Open any page with links (e.g. any search results page)
- Grab a link with the mouse and start dragging it (does not need to be dropped anywhere specific)
- The page hangs/lags, then becomes fully unresponsive: clicks are ignored, further drags don't work
- Even Ctrl+R (reload) does not work — the only way to recover is clicking the reload button in the bottom toolbar of Helium
Actual behavior
After grabbing and dragging a link, the page becomes unresponsive until it is reloaded via the bottom toolbar. Keyboard shortcuts (Ctrl+R) are also dead.
Journal log shows exactly at the moment of the failed drag (8 occurrences across Aug 14–15, one per repro):
ERROR:ui/ozone/platform/wayland/host/wayland_data_drag_controller.cc:179] Invalid state when trying to start drag. source=kMouse
Example (full line):
Aug 15 16:39:14 laptop helium.desktop[651141]: [651141:651141:0815/163914.675527:ERROR:ui/ozone/platform/wayland/host/wayland_data_drag_controller.cc:179] Invalid state when trying to start drag. source=kMouse
The drag never effectively starts at the compositor side, but the page stays in a "drag in progress" state and ignores all further input.
Expected behavior
The page should remain clickable after a failed/aborted drag.
Additional context
- Ubuntu 24.04.4, GNOME 46 (Mutter), Wayland (
XDG_SESSION_TYPE=wayland) - This is a known class of Chromium Wayland DnD bugs with multiple partial upstream fixes that still reproduce on recent Chromium bases:
- https://issues.chromium.org/issues/336449364 (drag leaves browser ignoring mouse input)
- https://github.com/brave/brave-browser/issues/54081 (same exact error on Chromium 146, March 2026)
- https://bugs.kde.org/show_bug.cgi?id=482142 (KWin-specific variant, fixed by compositor patches)
- Upstream fixes: https://github.com/chromium/chromium/commit/b1176ff8ff4eea4308bf50492ca457661efc17ec (M135), https://chromium.googlesource.com/chromium/src/+/b3319430c1155a1716b441f225ef93f16493b5cb
- Since it still reproduces in Helium 0.15.4.1 on GNOME/Mutter with the exact error the upstream fixes targeted, it's worth tracking here as well (marking upstream as appropriate)
- Keyboard input (e.g. typing in the omnibox) still works; only mouse events are ignored — consistent with a stuck Wayland drag session
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 63
- Avg merge
- 28m
- Merged PRs (30d)
- 11
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from imputnet/helium-linux
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
imputnet/helium-linux#385 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#459 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
imputnet/helium-linux#457 ·
Maintainers usually reply within 1 day
-
feat
Difficulty 3/5 1-2 days Newbie friendliness 48/100
imputnet/helium-linux#455 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
imputnet/helium-linux#454 ·
Maintainers usually reply within 1 day
All issues in imputnet/helium-linux
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
varnish/helm-varnish#173 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
command: update-lgsm distro: Debian engine: source2 game: Counter-Strike 2 regression: yes reproducible: always severity: low type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
GameServerManagers/LinuxGSM#5242 ·
Maintainers usually reply within 1 day
-
📦 Update Request
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cdnjs/packages#2225 · 1 comment ·
Maintainers usually reply within 3 days