I will say I had an extra buggy experience last night too. Out of nine or so missions, we couldn't extract from two of them because no one could enter the pelican. If you did manage to clip into the pelican, you would just hang out in there and never extract.
I can see the justification of the pelican talking off immediately if its damaged. My team makes a conscious effort to consolidate samples and have that player enter the pelican first if it's smoking.
I've been using fedora on a small intel 6th gen or newer mini pc. I then cook up some custom launch scripts that cause JMP to run at login. I use cockpit and a CMK agent for remote monitoring and management.
I got sick of the lack certificate management on Android TV and how much you need to do to make it reasonably private.
If you are on the latest mesa drivers (hence fedora over a more LTS release), and you install Jellfin Media Player via flatpak, everything should just work with hardware decoding.
You can self-host the kiwix server in docker and grab .zim files for whatever wiki you want to host. Wikipedia is one of those files.
I can also vouch that Android Auto works in a work profile.
That's most likely the problem. In my experience, nearly all tor exit nodes are flagged as such and captchas are nearly impossible to "pass" when using such an exit node. I would try using a free VPN to test. Try protonvpn without an account and see if you can get past the captcha.
Are you using a VPN? It might be that changing your exit IP might help. I've noticed captchas get harder to pass if your on a VPN that has a lot of traffic trying to pass captchas. Probably DDoS protection.
I would cd into the user folder that you want to add / remove files from and see what the ownership is to begin with and simply replicate ownership to match what's already there.
Generally, in my experience, modifying the backing storage for a nextcloud instance is more of a PITA than its worth. I would just mount the webDAV in your file manager. This way the nextcloud db stays in sync with the backing storage.
If you are going to be making direct modifications to the backing storage, check this form post on modifying the nextcloud config to have it look for changes on the filesystem.
As for the permission side of things, run ls -lh in the folder that you want to make changes and see what the user:group is for ownership of the existing files and make sure your new files match. Chmod and chown will be your friends here and chmod has a --reference option that let's you mirror permissions from an existing file, a real time saver.
Hopefully this helps!
Thanks! Flatpak-KCM is perfect as I'm thinking I'll move to fedora KDE in a couple days when f40 drops. I'm hoping that the Wayland experience on NVIDIA GPUs will be smoother there than on GNOME.
To add on to this, if you are using flatpak apps and want granular permission control, check out flatseal. Fedora (IMO) has one of the best flatpak integrations out of the box. Other "sandboxing" or containerized app deployments are snaps (made by Canonical), and appimage (I'm not entirely sure this qualifies as an app container).
From my experience, flatpaks is currently leading in adoption when compared to the other two.
I'm not entirely sure tbh. Like I said, mixed results depending on the app, but my working throey is that the session installer can automatically install apps that have the same signature and don't require any changes in permissions. I've seen some apps do in-place upgrades with no user touch but some don't.
I've had better success with auto-update using Driod-ify. At the very least the client downloads the updates automatically so it's just a matter of tapping install.
For container management I use portainer CE and for the rest I use CheckMK.
I dont know if this qualifies as a "toaster" but Ive used this docking bay in the past for a NAS and it served my purposes decently well. One thing to keep in mind is that random IO will be lacking with a usb interface. Also, this particular chipset does powercycle all the drives when one is removed so drive swaps end up requiring you to power the entire system off to perform. Also no integrated cooling may be a deal breaker as you illuded to.
If I was basing a nas build off of a PI, I would look to use the PCIe 1x2.0 interface on the pi 5 as a HBA.
It depends on the size of your budget (if it exists at all). Your probably better off doing some e-waste dumpster diving. Shoot for something with a 3rd gen i3 / i5 or newer and at least 4gb of RAM.
That generation is when Intel added MPEG hardware encoder so it opens up a lot of options for self-hosting media servers.
https://flathub.org/apps/org.gnome.SoundJuicer
I then run the album through Picard to make sure all the tagging is correct.
Just to make sure. Are you copying to your ZFS pool directory or a dataset? Check to male sure your paths are correct.
Push vs pull shouldn't matter but I've always done push.
If your zpool is not accessible anymore after a transfer then there is a low-level problem here as it shouldn't just disappear.
I would installe tmux on your ZFS system and have a window with htop running, dmesg, and zpool status running to check your system while you copy files. Something that severe should become self evedent pretty quickly.