Skip to content
This repository has been archived by the owner on Jan 26, 2024. It is now read-only.

Cursor not visible on external monitor until window is created #415

Open
BenJarg opened this issue May 4, 2023 · 9 comments
Open

Cursor not visible on external monitor until window is created #415

BenJarg opened this issue May 4, 2023 · 9 comments
Labels
A: bug Something isn't working

Comments

@BenJarg
Copy link
Contributor

BenJarg commented May 4, 2023

Info

dwl version: 797e0c7
wlroots version: 0.16.2

Description

I've noticed this for a while, although it's not consistent. It's common when I first plug in my external monitor, then move the cursor to the external monitor, the cursor is at first not visible. When I open the first window on the external monitor, the cursor then becomes visible.

@BenJarg BenJarg added the A: bug Something isn't working label May 4, 2023
@sevz17
Copy link
Collaborator

sevz17 commented May 8, 2023

Can you check #416?

@BenJarg
Copy link
Contributor Author

BenJarg commented May 12, 2023

@sevz17 I got the issue again today, with #416 applied.

@sevz17
Copy link
Collaborator

sevz17 commented May 12, 2023

Does the external monitor have different scale?

@BenJarg
Copy link
Contributor Author

BenJarg commented May 12, 2023

@sevz17 No, both are set to the default scale (1).

@sevz17
Copy link
Collaborator

sevz17 commented Jun 23, 2023

I think it's related to this issue https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/2119

@sevz17
Copy link
Collaborator

sevz17 commented Nov 20, 2023

@BenJarg, do you think you could test if this happens in wlroots-next?

@BenJarg
Copy link
Contributor Author

BenJarg commented Nov 20, 2023

@sevz17 Sure, I'm running on wlroots-next currently. I haven't seen it in a while, even since before moving to wlroots-next, and I believe the change that made this stop happening was setting WLR_DRM_NO_ATOMIC=1 which reverts to some legacy drm behavior. I've removed that now though from my environment, and I'll give it ~a week and then let you know if I see it return or not for wlroots-next.

@BenJarg
Copy link
Contributor Author

BenJarg commented Nov 24, 2023

@sevz17 I had it happen again with wlroots-next once I removed WLR_DRM_NO_ATOMIC=1.

@sevz17
Copy link
Collaborator

sevz17 commented Nov 24, 2023

I see...

Can you send the stderr of dwl -d?

EDIT: Since I'll be doing the migration to Codeberg tomorrow... can you wait until then?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants