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?
Hello everyone, so at my new job I'll get a MacBook snd until #AsahiLinux supports the security processor I will be a good girl and use #macOS. For someone coming from a setup mixing #ArchLinux, #Fedora#Silverblue / #CoreOS, even some #NixOS and does weird stuff with #podman sometimes: Are there some general recommendations from other #Linux exiles (I use vanilla #GNOME nowadays mostly, so maybe not too much lol?)
I currently plan to use the mac as mostly a shiny looking physical terminal + some vscode/vi, that should be mostly trivial. As such I'm mostly worried about things like a proper keyboard layout (I use us altgr-intl, caps mapped to ctrl, tab to esc).
Otherwise I'm thinking of grabbing #Firefox and activating Lockdown Mode. I've seen nix-home and will try setting that up for day-to-day tasks/tools.
Coming from Evolution, is Apple Mail decent? Any other "classic" GNOME tool I'd miss? Currently looking for trustworthy replacements for Nick's YT downloader, Warp (Wormhole GUI), Frog (OCR tool), Obfuscate (picture obfuscator/censoring tool), Characters (searching through Unicode symbols/emoji). Anything else I may take for granted but is different? ¹
¹ I already know the cli differences w.r.t. bsd based tools, but my personal scripts are mostly posix/ksh8x compliant anyway :D
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.
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. 😢
A 2009 #Macbook got a second life. It had #MacOS Sierra (EOL 4 years ago) installed and was terribly slow with it. The original hard drive replaced with SSD, memory upgraded from 4 to 8 GB, #Fedora#Linux (#Silverblue) installed and it's a decent laptop again.
Hmmm, immutable #Linux distros are currently ignored by the "How to quickly build a trimmed #LinuxKernel" text I recently added to the #kernel's documentation[1].
Is that fine for now? Or should I add a sentence or two about those?
For @fedora#silverblue at al. it seems using "ostree admin unlock --hotfix" might be the best solution when say doing a bisection.
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. ☺
I'd like to write migration scripts to move data from the old laptop to the new one. It would move #flatpak app data over, reinstall flatpaks there, move #Toolbx containers, perhaps desktop settings, too.
But maybe something like that already exists and I don't have to start from scratch. Any idea?
I bought a larger SSD to move my laptop to #Fedora#Silverblue (might later decide to use one of the derivatives, once it's just a "rebase and try it out" operation).
Can I choose XXHASH while installing Silverblue? I'd prefer a still fast, but more collision-resistant hash than CRC32C.
If I do btrfs, then I have to decide how to do space management. I'd kind of like at least to separate space utilization for / and /home (well, /var/home on Silverblue). Maybe /var/containers too.
Is the norm to have one big filesystem with subvolumes here, or to create multiple btrfs filesystems on separate devices?
Maybe I'm being a control freak and I should just make one big filesystem for / and lean into subvolumes for snapshots?
For VMs, are qcow2 files on btrfs actually a good way to go? This is a laptop, so VMs are not normally running, I just need to spin them up occasionally.
I have really started developing an interest in immutable Linux distros. In particular, as a Fedora Workstation fan, I’m interested in Fedora Silverblue. Having having a reliable, ABI/API stable os that is also leading edge sounds really good!
I just need to figure the best way to install DAW host and plugins to get the best performance and reliability. I’m suspecting Fedora Toolbox is probably the way to go, but I’m not 100% sure yet.
I've been playing with ublue's isogenerator to see if I can boot a VM off the custom ISO I make out of my startpoint repo at https://github.com/tunix/penguix and finally succeeded. But when I try to boot from it, the download simply never finishes and I can't understand whether it's stalled or something is wrong. 😞 #linux#fedora#silverblue#ublue
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...
OC Steam freezes after suspend
Hi,...