Linux distro's heading to where macOS today: where the root filesystem is mostly immutable, but not entirely. #ChromeOS arrived there a decade ago, but everyone seems to be moving in the same direction.
I decided to try building #FreeCAD from source. I used a F39 toolbox on my #Fedora 40 #Silverblue and installed the prereqs; most from packages, but pyside2 from pip (inside the toolbox) since it hasn't been packaged in Fedora for years. The segfault I'm getting from libshiboken isn't illuminating to me. I could imagine a missing dependency on a package causing a segfault, or maybe no one is building FreeCAD on Fedora and it just doesn't work on F39. 🤔
Not clear that I'm close enough to the beaten path for this to be worth a bug report, though. Quite likely PEBCAK...
I was so happy yesterday! I had a desktop computer that had been sitting around my house for several years, and I decided to bring it back to life. I bought a new NVIDIA RTX 4060 card and a new case for it. I transferred all the old components to the new case and fired it up, installed Fedora Silverblue, and even played a bit of Fallout 4 at full graphics settings. It was such a breeze!
However, today when I tried to turn it on, I think the motherboard just gave out. Looks like it's time for a new CPU, motherboard, and memory.
For the fellow nerds out there, what would you recommend? I'm looking to play some games and compile Rust code.
Is there any good Blog post to learn #uBlue customization with relatively limited knowledge about #Docker? I don't like the idea of a distro that I can't customize easily so normal #Silverblue doesn't sound like my favorite choice but uBlue, #VanillaOS and similar approaches sound very tempting and I love the concept of #Atomic distros in general! Also, do you think it's easy enough to learn to imediately switch my main computer over or should I do some more testing in VMs first?
I'm on #Fedora#Silverblue 40, and I'm now seeing a lot of "No video with supported format and MIME type found" errors.
I don't have mozilla-openh264 installed, so I guess that might make sense? Let's fix that...
# rpm-ostree install mozilla-openh264<br></br>...<br></br>error: Could not depsolve transaction; 1 problem detected:<br></br> Problem: package noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64 from @System conflicts with openh264 provided by openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264<br></br> - package openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264 obsoletes noopenh264 < 1:0 provided by noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64 from @System<br></br> - package mozilla-openh264-2.4.0-2.fc40.x86_64 from fedora-cisco-openh264 requires openh264(x86-64) = 2.4.0-2.fc40, but none of the providers can be installed<br></br> - conflicting requests<br></br># rpm -qa | grep noopenh264<br></br>noopenh264-0.1.0~openh264_2.4.0-1.fc40.x86_64<br></br># rpm-ostree install --uninstall noopenh264 mozilla-openh264<br></br>error: Package/capability 'noopenh264' is not currently requested<br></br>
There's clearly something I don't understand here. I don't know how noopenh264 is installed but not requested and still causes a conflict. I must be alone in having this problem based on lack of bugs that I can find in RH's bugzilla.
I don't think I saw this problem on Silverblue 39, but I was using that for only a few days before rebasing on 40, and was previously on my "classic" Fedora 39 installation where it definitely wasn't showing up with the rpmfusion packages installed.
Silverblue and Fedora Atomic users - here's a guide on how to rebase to Fedora 40.
The graphical example used is for Silverblue, but if you follow the terminal instructions they will work on any Fedora Atomic Desktop. Just pay attention to use the name of your variant where applicable.
If anything goes bad, you can rollback to Fedora 39. Additionally you can pin your current image if you need to go back after a few updates.
(And then restart your system, of course. You can always roll back to your older pinned version of 39 should anything go wrong. Also, although not required, it’s always a good idea to install the latest updates in the current version of the OS before rebasing.)
Just rebooted and I’m up and running with Fedora Silverblue 40.
(Just tried reinstalling mozilla-openh264 – so videos work in Firefox – but it failed with the same error. Not a big deal, I’m using @Vivaldi as my main browser these days anyway and I guess the Fedora folks will fix this in time.)
More importantly, I wonder if the screen reader has been fixed yet. (Yes, Fedora ships with a broken screen reader.)
The main thing that I run into with #Fedora#Silverblue that really doesn't "just work" — unlike pretty much everything else— is video playback. The way to "fix" it gets more convoluted with every release, too.
Anyway, for Fedora 40 it seems to now be: sudo rpm-ostree override remove noopenh264 --install openh264 --install gstreamer1-plugin-openh264 --install mozilla-openh264
I really wish H.264 wasn't so widely adopted as the de-facto codec.
First papercut with #Silverblue — I have roughly forever kept a symlink /m → /media/johnsonm because I really don't like typing all that.
I built a local package with that symlink to get my symlink back, and then when I tried to install it immediately hit https://github.com/projectatomic/rpm-ostree/issues/233 which it says to "see" but that's not super useful.
As far as I can tell that's "u kant haz" and I'll have to retrain my fingers to something else. 😢
I have upgraded my personal laptop to #Fedora#Silverblue just in time for the upgrade to Fedora 40 to be an update in the background and then a trivial, quick reboot into the upgraded system with an option to roll back if something goes wrong.
I started this update in December, by starting with a new (larger) drive. I put it into a USB-3 NVME carrier, attached it to a VM, and did an install and updates until it looked like I got the software I wanted complete.
Then an unrelated hardware failure made me back-burner it until tonight. I booted the VM, did a quick rpm-ostree upgrade, and rebooted the VM into the latest release. Four months of updates and it was fast and trivial. Copied my home directory over from the old drive to the new drive, popped it in, and I'm up and running.
I'm really looking forward to not watching minutes of updates scroll by with the system unusable at the boot screen.
And if I need any files from the old install, I have the old drive in the USB-3 NVME carrier. ☺
But after that, the update to Fedora 40 with rpm-ostree rebase fedora:fedora/40/x86_64/silverblue just ran in the background for 10-15 minutes and was then an uneventful quick reboot after the "command finished" notification popped up, at my convenience, no slower than any other reboot.
If it hadn't worked right for some reason, ESC at boot time to get the grub menu and choose 39 instead would have been easy.
I, again, am thinking about combining Silverblue as my base system with a more complex Nix setup to replace toolbox (which is effectively a separate whole Linux to maintain or throw away regularly, or build a CI for to create new images, etc. -- nah).
Now, Nix works fine, but it needs to store things under /nix because most binaries are prefix dependent and not portable in their location. But what if I download the nix store to $HOME/.nix instead and then launch a light-weight throw-away container/namespace that simply maps $HOME/.nix to /nix but keeps everything else identical?
Would that work? Did someone already build that stuff?
Tooted about a #Fedora issue yesterday, in which I couldn't install it at all. I now have, ahem, "screenshots" so hopefully someone smarter than I can point me in the right direction.
I am booting from a 16GB SanDisk Cruzer Blade.
On UEFI, I get a message to say the image is invalid / unsupported.
On BIOS, the installer starts (after a successful self-test) but immediately crashes with a big, scary Python error.
#OpenBSD 7.5 seems likely to be released soon. I considered switching back. But I just don't feel like I could make it a "forever OS", because there are factors which could force me to use something else. Either I get a new computer and have unsupported hardware, or somebody makes me use some software that doesn't run on it.
#Silverblue seems a safer bet for both of these possibilities.
How do you name your devices? I name my devices after #philosophers. I've had Schopenhauer, Kant, Diogones, Socrates, etc. But for this newly installed laptop using #GNOME#Silverblue, I decided for something a bit different.
My new system is called Fanton, after Frantz Fanton, who studied the psychology of #colonization - that is both the colonized and the colonizers. His statement that colonization dehumanizes both still rings true today.