Summary: | No cursor on ARM, with llvmpipe | ||
---|---|---|---|
Product: | Wayland | Reporter: | Paul Kocialkowski <contact> |
Component: | wayland | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Paul Kocialkowski
2016-08-15 17:33:27 UTC
I think you may need to do a bit more investigation to determine which is at fault: the compositor or the drivers you use. I am quite sure the bug is not in Wayland, but either in the compositor, the drivers, or the combination of the two. I do not know how gnome-shell (is that the compositor running?) implements cursors, so I cannot guess the cause. You might get more attention filing a bug against GDM or GNOME's compositor, I believe. I'm entirely willing to bet that drmModeSetCursor is broken on tegra and imx-drm, due to not declaring discrete cursor planes. What happens if you press Windows - Shift - Space (release) then 'c'? That should force the cursors to go through the regular composition path. I just 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) I also noted that the same behaviour happens with the (experimental) etnaviv driver on imx, in addition to llvmpipe. Do you think I should bring it up with GNOME folks? Oh sorry, I didn't notice you were running GNOME. As Pekka says, this is not a generic 'Wayland' issue (especially as Weston works), but specific to GNOME's implementation. Can you please file a bug on Mutter at https://bugzilla.gnome.org so they can fix it? Submitted at https://bugzilla.gnome.org/show_bug.cgi?id=770001 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.