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.
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. 😢
Been curious about what it's like to use Bluefin? Here's a quick tour of it, walking through some of the main changes we make to Silverblue! https://www.youtube.com/watch?v=3_yyyUMecwo
For more stability, the Bluefin custom image defaults to GTS (grand touring support), meaning that we hang back one release of Fedora. It brings stability in general, but specifically to all the GNOME extensions we use.
I moved my backup desktop machine from #Kubuntu to Fedora #Silverblue. I've been using it on my laptop for a couple of months now without significant issue, but still manage to confuse myself once in a while about which toolbox container I am in.
Part of me is tempted to use #UBlue to make a custom #Fedora#Silverblue image to add in the Pop_OS Gnome extensions, make #vim the default editor, and #Thunderbird the default mail reader and call it "Blue Bacon Linux"
For users of any operating system, not just #Linux, what might keep you from trying/running an #immutable#Fedora desktop? If you are already running one, why did you choose it?
Question along these lines for @jorge and @UniversalBlue users in general: Do the Ublue images include "full" console Vim, or just Vim minimal (like stock #Silverblue)?
I also use the Flatpak Vim, but it would be nice for the default Vim in the terminal to recognize my .vimrc.
@dhry in general, using an atomic env like #silverblue 'properly' is a bit different from using a traditional packaged distro, it takes a minute to read up on docs or forums and get used to the differences. if it seems like too big of a leap you might just want to try Workstation for now?
I kept my #GoToSocial server going for about four months. I just killed it. It was in the Oracle Cloud, and the upgrade of #AlmaLinux from 9.2 to 9.3 was taking a long time. I thought it was hanging, and I hit ctrl-c. That stopped a "scriptlet." I reran the upgrade, which said it completed. I should have know then to remove the new kernel. I rebooted, and that was it.
I hadn't yet set up backups for this server because I considered it experimental.
Check out this great article from @LWN covering Bluefin! It's a good primer on Fedora Silverblue and how we're working on top of that with Bluefin's experience and tools. https://lwn.net/Articles/954059/
You CAN compile and run code with the Geany "mini" IDE Flatpak if you check the "Execute Programs in the VTE" box under Preferences--Terminal.
So far I have tested C++ and Ruby, and they both work. I don't think you'll be able to add Ruby Gems, but for some simple things, it might just work (until Flatpaks can interface with Toolbox/Distrobox containers).
#Silverblue and #Docker do exactly the same thing #Nixos does, minus the file system compatibility. This is where we step beyond Silverblue and Docker and into the system level reproducibility. Recall how /etc is a symlink farm into /nix/store and how /nix/store is read only? This presents a problem if you want to configure nginx, or samba, or nfs, or any other package that relies on /etc. So what’s the solution? The only directory in /etc that isn’t part of the symlink farm, /etc/nixos. Within /etc/nixos is a file called configuration.nix. This is where the magic happens. https://dollarrandom.com/posts/home-lab/nix-as-docker-host/
I'm trying to figure out GUI development workflows for #Fedora#Silverblue.
I went through a whole thing to connect the #VSCode#Flatpak to a #Toolbx, and while it worked, it was kind of underwhelming. Yeah, I can access the toolbox from the editor, but I can't compile/run from the VSCode menus.
If I'm not getting full integration in the IDE, why not just have a separate terminal with the Toolbox open?
I'm not sure why I can't just compile a C++ program from VS Code due to whatever Flatpak SDKs are already on the system.
I have trouble understanding how GNOME Builder "works" for non-GNOME/Flatpak development use cases. Just getting a binary out of there seems difficult.
For now I'm just falling back to the Geany Flatpak with Toolbox in a terminal. That's simple, and it works.
I'd like to be able to compile/run C++ and Ruby from an IDE, but I don't see it happening. What about Java and Python?
I get that everything is about containers, but I'm not finding a lot of documentation that "normal" people can follow, and it's very short on "Here's a GUI IDE workflow for atomic/immutable distros that is easy and works." Is this solved in #UniversalBlue?