My favourite is SicMu Player. The name sucks but it’s the best and lightweight folder base music player for me. Quite customizable as well.
Well, everyone has a different taste. I don’t like transparency or even gaps but as I see from unixporn, a lot of people do.
Also, matcha addiction does that to people. :P
I guess currently there isn’t one, at least directly. I read that there is an undergoing work to separate the window management in River, probably you should check back later after those changes are done. I’m also waiting for those changes to get a more traditional navigation.
Similar thing happens to me with my two monitor setup. No problem when I use single monitor. No problem when I use two monitor. However when I plugged out the second monitor or switch to single monitor with my script, the CPU starts doing random spikes on single cores in short intervals. Only a reboot fixes this.
No problem! My first switch to Wayland was with Hyprland. It’s very fancy and I see how this tool can get along with it quite nicely. Though I was a Bspwm user and switched to River recently. I usually only see my wallpaper when I first boot the system and if I want to run a non-automated program. But still even for me this can be useful when I work with two monitors.
Would this run on River by the way? Since River handles workspaces a little differently.
That’s an interesting way to put it. I like how everyone does different things on their workspaces and some of them can be pretty clever. :)
Neat! Though if you’re using a tiling WM, having a wallpaper is kinda useless.
I guess I’ll finally try Lemmy’s block feature.
New Empire Earth looks great too.
Unless there is a raccoon involved. Then it’s both.
I see. I checked its documents now and it seems it can be usable on Hyprland only, depending on hyprctl.
I think those are changing according to which sandbox environment you currently use. Probably one for root account (for programs you use with sudo), one for flatpaks and one for normal user.
Can we use it on outside of Hyprland? I installed it but doesn’t show up on nwg-look. No idea if I can use it at all.
Apparently those cursors can be used on both Xorg and Wayland with their respective specs, and they are even located at ~/.icons or /usr/share/icons. Maybe this is some kind of a transition stage. However hyprcursor isn’t located there.
So even if there was a native Wayland cursor, that wouldn’t fix it too unless everything is native Wayland?
Some compositors allow Xwayland to request moving the real pointer instead of doing emulation, but River apparently doesn’t.
Then this shouldn’t happen with native Wayland apps I assume. I guess some problems could occur since it’s a transition layer. Though I don’t know the working mechanism of Xwayland. I’m kinda confused. So this is a pointer issue but not input issue?
I haven’t tried it but I can try. Recently I learned about Hyprcursor in a post which was saying native Wayland cursor. However I couldn’t really find anything about native Wayland cursors so I asked here.
I installed the Mocha pack and it seems fine so far. Thanks.
I see. So nothing really changed? I was starting to think that it might be related to permissions in Wayland, apparently not.
That’s either a compositor or driver bug, please report it (as I’ve never seen that on Plasma, to your compositor first).
Hmm, in that case it could be a Hyprland issue. I would say wlroots but they stopped using wlroots and I switched to River recently. Haven’t happened on River yet but it’s been only a week so I cannot say for now.
That’s because it moves the X11 pointer but not the real one. A cursor theme can’t change that.
The real one? It was fine on Xorg though. I tried to put my user into input group, thinking could be related to a permission issue but it didn’t change anything.
Sure, but my post isn’t about customizing really. It’s about Xorg vs Wayland cursors, which I don’t know any Wayland cursor I can use.
Last version update is from 30 March 2023. It doesn’t follow Android UI and has its own, works without a problem. I see no problem here, as long as it works. At least for Android 14, should be fine for 15 too.