djpohly / dwl

dwm for Wayland - ARCHIVE: development has moved to Codeberg
https://codeberg.org/dwl/dwl
Other
1.93k stars 284 forks source link

Invisible cursor using Intel graphics card #517

Open theyspeon opened 9 months ago

theyspeon commented 9 months ago

Info

dwl version: v0.4-61-gd6fabe3 wlroots version: wlroots-0.16.99_1 GPU: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller

Description

Starting DWL displays my cursor fine initially, but the cursor becomes invisible when I spawn a window. I am still able to interact with things on my screen and click on things, but the cursor is gone. When I close out of all of windows, the cursor does not reappear, it just stays invisible until I restart DWL entirely again. Here are the logs generated by DWL after starting it with the -d option, opening a web browser with bemenu, closing that window, and then stopping DWL https://pastebin.com/DzjkNVrD.

sevz17 commented 9 months ago

Wrong log, seems like you posted the stdout not the stderr. (use 2> instead of >)

EDIT: where did that wlroots come from?, I don't recognize that version, is it from the 0.16 branch of git?

EDIT 2: does it disappear right after creating the window, or when it enters the window?. also, what type is the window?, is a layer_surface (e.g, application launchers, bars), a xdg_shell (typically what we call native wayland applications, e.g. foot, browsers in wayland mode), or xwayland (X11 apps)?

sevz17 commented 9 months ago

For the record, someone (presumably you) said this in discord:

It seems that setting WLR_NO_HADWARE_CURSORS fixes the issue if one is using an NVIDIA graphics card, but I am using an Intel graphics card, and setting the env variable does not change anything for me.

theyspeon commented 9 months ago

That version of wlroots I got from the package manager I am using. I did not build wlroots myself. The cursor disappears right after creating the window, immediately gone. I am using native Wayland apps. Yes that was me in Discord. Logs generated using the same steps as before (opening and closing the web browser) except using the command dwl -d 2> dwlissue.txt: https://pastebin.com/HijahcmT