Open Bug 1788602 Opened 2 years ago Updated 1 year ago

[Sommelier Chrome OS wayland compositor] No touchpad scrolling on Chromebook

Categories

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

Firefox 105
defect

Tracking

()

UNCONFIRMED

People

(Reporter: f.niedernolte, Unassigned)

References

(Blocks 2 open bugs)

Details

Steps to reproduce:

Install Firefox in a Crostini environment via Flatpak on a Chromebook.
Using two fingers to scroll up/down

Actual results:

Doesn't do anything

Expected results:

Scrolling up/down

I am experiencing the same issue. I have also found that after scrolling in the green square on this page, scrolling works again until you switch tabs or go to another page.

(In reply to ura from comment #1)

I am experiencing the same issue. I have also found that after scrolling in the green square on this page, scrolling works again until you switch tabs or go to another page.

Exactly the same experience for me. Works perfectly after scrolling in the green box, switch to a different tab and no more scrolling.

Can you try to run plain binaries if that's possible?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_Mozilla_binaries
Thanks.

Blocks: flatpak
Flags: needinfo?(f.niedernolte)
Priority: -- → P3

That doesn't work:

XPCOMGlueLoad error for file /home/peleke/Downloads/firefox/firefox/libxul.so:
libdbus-glib-1.so.2: cannot open shared object file: No such file or directory
Couldn't load XPCOM.
Flags: needinfo?(f.niedernolte)
Flags: needinfo?(f.niedernolte)

Okay, then it works and also the bug is solved this way. Just not very convenient to start and horizontal back/forward swipe gestures don't work but I can live with that.

Flags: needinfo?(f.niedernolte)

So, a couple of interesting findings about this very specific (and weird) behavior:

  • All the evidence points out to "sommelier", the ChromeOS Wayland compositor: I've followed @stransky advice and executed firefox using "mutter", instead of "sommelier", and I'm able to scroll fine, without any issues.
  • @ura link on its comment made me think that the problem might be specifically related to Firefox, but that's not what the evidence shows.
  • I wasn't able to reproduce the success reported by @Frederik Niedernolte (yes, I've also tried with "clean binaries"). It didn't worked for me. The only single thing that worked was to use another compositor, following the guide provided by @stransky.
  • After searching for a while, I was able to find some (I hope useful) extra information on this:
    • when using Firefox under Crostini (Flatpak or not, clean binaries or not, it doesn't matter, as far as I can tell) on the "X11/Xwayland bridge" mode, all works fine, without any problem. The only drawback is that the X11 produced tearing when scrolling. On Wayland-enabled firefox (MOZ_ENABLE_WAYLAND=1 with or without MOZ_USE_XINPUT2=1 - I believe this one works only on X11 backends, and it does wonders about the mouse scrolling, by the way), that doesn't happens.
    • on this link about Mir (the compositor made by Canonical), they talk about something related to a specific event ("wl_pointer.axis_stop") that might not be being sent, related to "libinput": https://github.com/MirServer/mir/pull/2275 (why is this related to the issue? Because after searching a while on the sommelier source code here - https://chromium.googlesource.com/chromiumos/platform2/+/HEAD/vm_tools/sommelier/sommelier-seat.cc - I don't see the same logic on the "axis_stop" thing. Maybe that's what's missing).

I'm gonna open a bug on the sommelier project on chromium, and I'll put a link to this issue, as reference, over there.
Hope it helps.

Flags: needinfo?(stransky)

(In reply to Daniel Wolff from comment #7)

So, a couple of interesting findings about this very specific (and weird) behavior:

  • All the evidence points out to "sommelier", the ChromeOS Wayland compositor: I've followed @stransky advice and executed firefox using "mutter", instead of "sommelier", and I'm able to scroll fine, without any issues.
  • @ura link on its comment made me think that the problem might be specifically related to Firefox, but that's not what the evidence shows.
  • I wasn't able to reproduce the success reported by @Frederik Niedernolte (yes, I've also tried with "clean binaries"). It didn't worked for me. The only single thing that worked was to use another compositor, following the guide provided by @stransky.
  • After searching for a while, I was able to find some (I hope useful) extra information on this:
    • when using Firefox under Crostini (Flatpak or not, clean binaries or not, it doesn't matter, as far as I can tell) on the "X11/Xwayland bridge" mode, all works fine, without any problem. The only drawback is that the X11 produced tearing when scrolling. On Wayland-enabled firefox (MOZ_ENABLE_WAYLAND=1 with or without MOZ_USE_XINPUT2=1 - I believe this one works only on X11 backends, and it does wonders about the mouse scrolling, by the way), that doesn't happens.
    • on this link about Mir (the compositor made by Canonical), they talk about something related to a specific event ("wl_pointer.axis_stop") that might not be being sent, related to "libinput": https://github.com/MirServer/mir/pull/2275 (why is this related to the issue? Because after searching a while on the sommelier source code here - https://chromium.googlesource.com/chromiumos/platform2/+/HEAD/vm_tools/sommelier/sommelier-seat.cc - I don't see the same logic on the "axis_stop" thing. Maybe that's what's missing).

I'm gonna open a bug on the sommelier project on chromium, and I'll put a link to this issue, as reference, over there.
Hope it helps.

Oh, by the way: I'm running Mozilla Firefox 115.0.2, from the Ubuntu focal-updates apt mirror.

Okay, thanks.

Flags: needinfo?(stransky)
Blocks: wayland
Summary: No touchpad scrolling on Chromebook → [Sommelier Chrome OS wayland compositor] No touchpad scrolling on Chromebook
You need to log in before you can comment on or make changes to this bug.