can't see cursor under wayfire
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start with src/core/seat/cursor.cpp and check how the cursor manager is created and used with wlroots 0.19. The report says wlr_xcursor_manager_load is missing; confirm the relevant wlroots API and how output scale is handled. Done means the cursor image appears in the reported Wayfire setup, with a suitable regression check if the project has one.
Written by the indexing model from the issue text.
Description
Wayfire version
0.10.1-2.fc45 (Fedora 45, wlroots-0.19.3)
GPU / Driver
VMware virtual machine (vmwgfx driver)
Describe the bug
In wayfire the mouse cursor is not visible: the mouse still responds (window borders highlight on hover), but the cursor image itself is not displayed. On the same machine, the cursor in niri works normally. sddm starts wayfire as a Wayland session (DRM backend).
Root cause (confirmed; unrelated to cursor theme data): due to API changes starting from wlroots 0.19, wlr_xcursor_manager_create(name, size) only creates an empty manager and no longer loads the theme; the theme must be loaded separately by calling wlr_xcursor_manager_load(manager, scale) (compositors should call it when each output is created, according to its scale). Fedora's wayfire 0.10.1 never calls wlr_xcursor_manager_load (source src/core/seat/cursor.cpp only contains create/destroy/set_xcursor; upstream master likewise lacks it).
To Reproduce
- Run wayfire 0.10.1-2.fc45 on wlroots-0.19.x
- Observe the mouse cursor image not being displayed
Expected behavior
The mouse cursor image should be visible, as it is in niri on the same machine.
Screenshots / Videos / Stacktrace
N/A — no crash; visual issue only.
Additional context
Long-term / alternative options:
- File a bug upstream against wayfire (0.10.1 is missing the
wlr_xcursor_manager_loadcall) / wait for a Fedora update to fix it; - Or use niri as the daily driver (the cursor has always worked there).
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 249
- Avg merge
- 7d 13h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from WayfireWM/wayfire
-
touchpad_scroll_speed is ignored for touchpads (get_scroll_speed checks for TABLET_PAD)Possibly taken @italopaesano claimed this 15 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
WayfireWM/wayfire#3148 · 1 comment ·
Maintainers usually reply within 3 days
-
easy enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
WayfireWM/wayfire#3005 · 14 comments ·
Maintainers usually reply within 3 days
-
Invisible windowsOpenbug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
WayfireWM/wayfire#3187 · 1 comment ·
Maintainers usually reply within 3 days
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 3 days
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 53/100
WayfireWM/wayfire#3164 · 2 comments ·
Maintainers usually reply within 3 days
All issues in WayfireWM/wayfire
Similar issues
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#2385 ·
Maintainers usually reply within 1 day
-
type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tensorflow/tflite-micro#3995 ·
Maintainers usually reply within 1 day
-
CPU update 1.31xOpenspeed-report
Difficulty 1/5 Under an hour Newbie friendliness 75/100
mw00/project-maya#961 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
godotengine/godot#125376 ·
Maintainers usually reply within 1 day