[Bug]: Page hangs and becomes unresponsive after grabbing/dragging a link on Linux/Wayland (wayland_data_drag_controller error)

Open
#364 2 comments 0 reactions 0 assignees View on GitHub

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

bug upstream
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-dir command 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:

  1. Open any page with links (e.g. any search results page)
  2. Grab a link with the mouse and start dragging it (does not need to be dropped anywhere specific)
  3. The page hangs/lags, then becomes fully unresponsive: clicks are ignored, further drags don't work
  4. 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
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imputnet/helium-linux

All issues in imputnet/helium-linux

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.