Your fstab file can remain unchanged and still fail, if the drive or user identifiers have changed unexpectedly. It depends on how you've configured your fstab entries, which is why it's helpful to share them. In future, no one will be able to offer much assistance without seeing the entry details. Either way, glad you were able to get it sorted!
Can you read/write to the disks as root? If so, then something has likely gone sideways with your fstab entry. For example, the device name, order, or UID/GID may have changed, depending on how you've configured the entry.
It's difficult to assist much more without seeing the contents of /etc/fstab.
I used DDG for the first link, but then searched Google with a portion of the error message in quotes. Either way, I'm glad it sorted itself out!
Hah any time, man! Your work and YT vids are what really got me hooked me on Silverblue and the cloud native workflow! I'll never look at computing the same way again lol.
The biggest hurdles are unavoidable under stock Android, but it really depends on your needs. What are you trying to protect against?
Any offline or disconnected smart TV, pi 4 with Kodi (LibreElec), Steam Link, blu-ray player, AVR, and a Logitech Harmony remote to tie it all together. We have a huge disc collection that we've ripped and we also grab media from the library.
Fair points. I've only ever taken Mint for a quick spin and that was a decade ago. I just see it constantly recommended as one of the most user-friendly distros, thus the maybe recommendation.
Personally, I'm all in on Fedora Atomic for my hosts and (mostly) Arch in my containers.
Obviously, lightweight is open to some interpretation but Silverblue can be made very lightweight by simply uninstalling the default flatpaks. You'll be left with a very basic GNOME shell and greeter, without any of the common GNOME extras. From there you could easily install your own window manager, greeter, and whatever apps you need.
For all its faults (and there are many), Huawei continually features some of best phone cameras available worldwide.
thayerw
joined 1 month ago
It seems to be isolated to GrapheneOS users, but I do think it's something that Voyager is doing since it isn't happening anywhere else. Either there's an issue with the reply function, or the way it's being called in certain circumstances. Anecdotally, I recall that it started after a GOS update, and Voyager hadn't been updated at the time. Maybe something changed in GOS' Vanadium/WebView which has essentially broken Voyager.