Closed Bug 1788723 Opened 2 years ago Closed 2 years ago

[KDE] Cursor keep in "dragging more" forever after dragging some text

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 105
defect

Tracking

()

RESOLVED MOVED

People

(Reporter: leandrosansilva, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0

Steps to reproduce:

Select some text, drag it.

The issue can be easily reproduced and I've recorded a video showing it happening: https://www.youtube.com/watch?v=Zef7ZaAv-mA

I'm using the official build downloaded from the mozilla website. Manjaro x86_64 with KDE and using Wayland.

Actual results:

On dragging, the mouse cursor enter the "dragging mode", but after releasing the text, the cursor did not return to its previous state.

Expected results:

The cursor should have returned to its previous state (pointer, for instance)

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

I am also experiencing this bug. For reference, this is Firefox 106.0 in KDE Wayland. This bug only occurs when I have the environment variable MOZ_ENABLE_WAYLAND=1 set, so it does not happen when Firefox is running in xwayland. Changing the cursor theme does not help.

Thanks for the report.

Can you please try mutter compositor?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_different_Wayland_compositor
Thanks.

Blocks: linuxdad
Flags: needinfo?(leandrosansilva)
Priority: -- → P3
Summary: Cursor keep in "dragging more" forever after dragging some text → [KDE] Cursor keep in "dragging more" forever after dragging some text

I am also seeing this bug (on KDE Wayland). It doesn't happen in mutter.

(In reply to Martin Stránský [:stransky] (ni? me) from comment #3)

Thanks for the report.

Can you please try mutter compositor?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_different_Wayland_compositor
Thanks.

when I run
mutter --wayland --nested

and then

WAYLAND_DISPLAY=wayland-1 MOZ_ENABLE_WAYLAND=1 firefox

It opens an empty mutter window with a blue background and then opens firefox separately as a normal window on the kwin desktop. I tried swapping it to wayland-0 and wayland-2 and wayland-3 and it did not work. Am I running the command wrong?

(In reply to spittingverse from comment #5)

(In reply to Martin Stránský [:stransky] (ni? me) from comment #3)

Thanks for the report.

Can you please try mutter compositor?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_different_Wayland_compositor
Thanks.

when I run
mutter --wayland --nested

and then

WAYLAND_DISPLAY=wayland-1 MOZ_ENABLE_WAYLAND=1 firefox

It opens an empty mutter window with a blue background and then opens firefox separately as a normal window on the kwin desktop. I tried swapping it to wayland-0 and wayland-2 and wayland-3 and it did not work. Am I running the command wrong?

Close all firefox windows before running the firefox command.

Thanks, I can now also confirm that the bug does not occur with mutter.

I think this one is already solved by Vlad on KDE side but I can't find relevant bug.

Blocks: wayland-kde
No longer blocks: linuxdad
Flags: needinfo?(leandrosansilva)

Great, Thanks.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → MOVED
You need to log in before you can comment on or make changes to this bug.