After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 770001 - No cursor with wayland on ARM with llvmpipe (and etnaviv)
No cursor with wayland on ARM with llvmpipe (and etnaviv)
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: wayland
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2016-08-16 16:28 UTC by contact
Modified: 2021-07-05 13:51 UTC
See Also:
GNOME target: ---
GNOME version: 3.19/3.20



Description contact 2016-08-16 16:28:39 UTC
When running wayland on ARMv7 (tested both on a tegra124 nyan_big and an imx6q cubox-i), no cursor is shown on screen. This happens when running GDM and GNOME on Wayland. Both devices were using mesa with llvmpipe. The imx6q was also tested running the (experimental) etnaviv mesa driver.

However, running the same setup (with llvmpipe) on Intel x86 hardware with LIBGL_ALWAYS_SOFTWARE=1 in /etc/environment doesn't trigger the issue.

Note that while the cursor is not shown, it can still be used (blindly) so it doesn't seem to be an input-related issue.

Wayland version is 1.11, GNOME and GDM are 3.20. System in Parabola (Arch-derivative).

I tried two things:
* Super + Shift + Space (then release) c: didn't do anything particular, cursor didn't show up (on both tegra and imx)
* Running weston-launch does show a cursor normally (on both tegra and imx)

The issue was reported at wayland: https://bugs.freedesktop.org/show_bug.cgi?id=97356 but it was concluded that mutter is the culprit here.
Comment 1 GNOME Infrastructure Team 2021-07-05 13:51:04 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.