juipeltje

Nice! Glad it’s solved

I’m not sure what /run/host/user-share/icons points to, it might be flatpak thing where it’s pointing to something outside the sandbox. I’m pretty sure you could just point it to .icons like this:

XCURSOR_PATH=~/.icons

Sorry for the late reply. icons.theme should be index.theme, although you said the theme you downloaded uses icons.theme. Maybe it’s interchangable? I’m not sure about that. Also, is the name of your theme Fluttershy? If so you should put that in the Inherits field, Name shouldn’t be necessary. Other than that it looks okay.

• agree
• disagree
• agree
• disagree
• don’t really have a strong opinion on it one way or the other i guess

(I use GNU Guix + GNU Emacs btw)

You might want to try creating a file called index.theme in .local/share/icons/default/ and putting this in it:

[Icon Theme]
Name=Default
Comment=Default Cursor Theme
Inherits=your-theme-here

cursors can be a pain in the ass to actually make them show up everywhere properly. If you’re using Xorg you might also need to set it in .Xresources:

Xcursor.theme: your-theme-here
Xcursor.size: 24

and then if you get into flatpaks you might have to mess with settings in flatseal to give it access to the cursor theme.

Hadn’t thought about it before since i don’t have a need for them, but yeah i think that could work with swaylock, cause i’m pretty sure you can configure it in such a way that the static indicator isn’t on the screen the whole time. I don’t know if it can do video files, but you might be able to use a gif instead. Only downside would be that you still have to enter your password to get rid of it again, which isn’t typical for a screensaver i think.

I’m assuming he means that it’s harder to tell? But swaylock will still inform you when it’s cleared out so idk.

I’ve found that depending on what distro/OS it is certain methods of burning the ISO don’t work correctly, no clue why. Windows needs their official tool, so because of that i use a vm to burn it. I’ve also had linux distros that couldn’t boot when dropping it onto a ventoy drive, and would only work when directly burning it with dd, so it might have something to do with what ISO you’re trying to burn and how you’re burning it.