@Corb_The_Lesser It is technically possible to have a live mode on Fedora Atomic Desktops, but that has not been implemented. It's an area where the Fedora Atomic Desktops SIGs could use contributions, but otherwise it's just not something they've been able to get around to.
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...
@garrett Yeah, it's the same pyside2 problem I ran into in toolbox. Pyside2 has been dropped from Fedora, I think that was because it's not working on current Python.
I think this is a temporary state, and when FreeCAD moves to Pyside6 along with the Qt6 framework, it will be easier. But that's not going to come before FreeCAD 1.0 I think.
So I think at least currently I'll start from a Debian container since @yorik is using Debian.
@yorik Building and running it in a debian:latest container is working, thank you! I used both shiboken and pyside as packaged, not using pip. The current docker build instructions are missing three packages. But one seems to have been intentionally removed, so I just put the information in github for someone who knows what's intended to decide what to do about it.
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.
FreeCAD has plenty of paths in configuration. Some of them might not work and still need fixing. It would still be better than starting over entirely from scratch, speaking as a user.
Please feel free to describe specific examples where you feel that this would be damaging so we can have a conversation about specifics rather than sweeping generalities.
@siosm@swick@adamw@garrett@notting I'm not ignoring this, by the way — my idea is to use this thread of conversation to think through and do a better job of writing up a more coherent feature suggestion.
@deflockcom if you're looking for a home server solution, CoreOS may be a better fit since it still uses rpm-ostree but may not be so focused on the IoT use case in it's configuration.
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. 😢