foo

I use Grub for my bootloader so I’m probably not the best person to ask for rEFind problems, but a good place to start for everything Arch related is the wiki. The page for rEFInd has a configuration section that outlines where the config files are and how to read them. Check that everything there matches what you expect it to be: https://wiki.archlinux.org/title/REFInd#Configuration.

If you’ve verified that your bootloader config is correct and it’s installed on the drive you’re booting from correctly another config to check is /etc/fstab to ensure you have a root device set in there too. The wiki is your friend here too: https://wiki.archlinux.org/title/Fstab

You’ll need to post more info about your bootloader/fstab config. The error ERROR: device ' ' not found implies there’s something set to an empty string.

Don’t feed the trolls y’all.

What does this have to do with Linux?

I use a mix of shell commands, terminal file manager, and GUI file manager depending on the task at hand.

The terminal file managers are quicker to navigate to a particular file/directory since it doesn’t require typing commands but I can still navigate with a few key strokes as opposed to using a GUI.

https://support.mozilla.org/en-US/questions/1325905

Liferea has “search folders” that let you define conditions for which stories/feeds show up in them.

What distro are you using? I haven’t seen /etc/crontab in quite a while with the advent of the /etc/cron.d directory. That said, crontab -e will handle this stuff for you.

Edit: I see, Ubuntu. I’m not too familiar with what they’re doing over there. I have an /etc/cron.d dir on my Arch boxes. Some other stuff to check though: does any cron job run? If not, is the service running? You could also redirect this script’s output to a file under /tmp or something to check if it’s running and what might be going wrong. Beyond that, check the systemd logs for any errors.

0 * * * * * root /mnt/nas/freshrss/backups/backup.sh

Why do you have root in there? If you need something to run as root do sudo crontab -e and edit the root user’s crontab accordingly. The user shouldn’t be specified in the crontab directly.

Write to their customer support and complain.

This doesn’t really answer your question, but you may want to consider hanging on to Thunderbird given massive UI upgrade that’s coming very soon for it: https://blog.thunderbird.net/2023/07/our-fastest-most-beautiful-release-ever-thunderbird-115-supernova-is-here/