Closed Zenzi0 closed 1 year ago
I noticed this too, I found that my issue was that wlroots-git
and sway-git
had been updated out of sync, breaking something... somewhere. Can you try forcibly reinstalling both wlroots-git
and sway-git
, followed by a reboot to see if that changes anything?
If not, I'd just have to suggest sticking with the non -git
variants for now
So are you saying simply reinstalling wlroots-git
and sway-git
(and a reboot) fixed it for you? Unfortunately that didn't work for me.
Luckily the non-git
variants seem to work just fine. I have to admit I didn't even think these were an option. I thought we had to stick with -git
until some major future release. It's hard to keep up with the latest information (what's needed and what isn't) regarding sway and nvidia. I suppose this is one of the reasons you made sway-nvidia in the first place.
Thank you for your advice.
I don't suggest chaotic repo btw. Just stick with AUR & non-git packages as much as possible & it'll be fine. The wayland development is rapid fast. So there shouldn't be any far fetched differences between regular releases & rolling -gits.
Let me know if this is still an issue, the -git
versions seem to be working for me now
You are right, the -git
versions are working just fine. Not an issue anymore.
After updating my system and therefore wlroots to the latest available git (from chaotic-aur) the cursor is no longer visible. Moving the mouse also introduces lag/sluggishness to sway for a few seconds. This lag can be avoided by not using WLR_NO_HARDWARE_CURSORS=1. But then of course the cursor is also not visible.
This problem shouldn't be specific to your package. I am simply interested in whether anybody else is experiencing this and in possible solutions, of course.