home.social

#atomicfedora — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #atomicfedora, aggregated by home.social.

  1. Remember the last time Fedora Silverblue or Toolbox/Toolbx got a new feature? Me neither. Both have "maintenance mode" vibes.

    #Fedora #Silverblue #AtomicFedora #Toolbx #Toolbox

  2. I overlayed Syncthing in Fedora Silverblue, but I'm still overlay-free on Aeon.

    #AtomicFedora #Aeon

  3. Since I'm all in on KDE Plasma in Fedora Kinoite, I'm dropping Tuba and picking up Tokodon as my desktop Fediverse client

    #Fediverse #Fedora #Kinoite #AtomicFedora #Tuba #Tokodon #GoToSocial

  4. Fedora Silverblue 41 finally got the rsync update. A little later than I hoped for, but at least the patch is in.

    #Fedora #Linux #AtomicFedora #Silverblue #rsync #security

  5. One of the reasons I went with Fedora Silverblue was the perception that the Fedora Project and Red Hat seem keenly interested in working on and improving the system. The innovation and the engineering is a big part of Fedora, and I feel that continual push toward better tech.

    #linux #fedora #silverblue #atomicfedora

  6. Beating up on Fedora Silverblue isn't part of my day job, but I definitely do it.

    Would recommend.

    #linux #fedora #silverblue #atomicfedora #gnome

  7. I had no idea this existed:

    HeliumOS, an atomic Linux distribution based on AlmaLinux 9. It's an alpha release now, but an enterprise-Linux paced atomic system is something that has been missing for as long as atomic distros have been around.

    https://www.heliumos.org

    #HeliumOS #Linux #AtomicFedora #Atomic #AlmaLinux

  8. I split my workday between Fedora Silverblue 41 beta and OpenBSD 7.5 — both did great with my extreme number of windows and tabs open in multiple browsers with a smattering of text editors

    #Linux #BSD #OpenBSD #Fedora #AtomicFedora #Silverblue

  9. Fedora Silverblue 41 beta UPDATE:

    In today's image, Files/Nautilus now has "open in console" on right click — pretty much the same as the previous "open in terminal," though the terminal it opens is Ptyxis, and it tends to open it with two windows.

    Speaking of Ptyxis, the new terminal (in Silverblue for sure, maybe also in Workstation?) is optimized for use with containers. Click on the down arrow to the right of the plus sign on the left side of the window, and all of your Toolbox and Podman containers show. You can open them with the menu:

    #fedora #silverblue #linux #atomicfedora #ptyxis

  10. Hot Fedora Silverblue tip:

    Layer the fedora-release-kde package, and any KDE apps you are running will look way better when using the Breeze Dark theme.

    https://discussion.fedoraproject.org/t/fix-kde-rpms-and-flatpaks-by-including-this-package/132503

    #Fedora #Silverblue #AtomicFedora

  11. In my Fedora Silverblue 41 beta testing, I've been through maybe 50 suspend/resume cycles, and I haven't crashed the display server.

    That's a welcome change on my 2017 HP Envy (Intel) laptop, where Fedora Silverblue 40 and Debian 12 haven't been so solid in that regard.

    Last week I had performance issues with Google Chrome (Firefox was fine). Once I get to work on Monday I will give it another try. (I have a Chrome for business, Firefox for personal divide.)

    The display improvements will definitely have me sticking around.

    #fedora #fedora41 #silverblue #atomicfedora #linux #debian

  12. Sometimes in an LTS Linux distro (anything between 2 and 5+ years of support) you can hit a GNOME "sweet spot," and be reluctant to move on.

    I felt that way about the GNOME in Debian 11. It was the last GNOME to arrange the virtual desktops vertically, and the last for many GNOME releases to offer image preview when uploading.

    And I haven't been terribly happy with the GNOME in Debian 12.

    In Fedora, however, I ride the six-month cycle and get the latest GNOME features. And I'm very much OK with that.

    GNOME 47 (in Fedora 41) seems like an incremental release, and it's looking very good.

    (As far as performance goes, for me the DE doesn't matter, because once you start using a web browser, it dwarfs any DE in terms of memory and CPU usage. So I might as well enjoy what a full-fat DE has to offer.)

    https://release.gnome.org/47/

    #linux #fedora #silverblue #atomicfedora #debian #gnome

  13. I am really enjoying the Fedora Silverblue 41 beta.

    I haven't been with it long enough (I need a few more work days), but I'm feeling a performance gain and enjoying some extra polish in GNOME.

    I already run Wayland, so not having an Xorg option just tightens things up.

    There are paper-cut level bugs here and there, but nothing that's keeping me from doing what I want with the OS.

    There are things I'd like to see in Flatpak and Toolbox that aren't happening yet, but I have my ways of doing tasks that work for me now. That's an overall ecosystem thing and not a "Silverblue now" thing.

    #Fedora #Silverblue #AtomicFedora #Linux #GNOME

  14. I didn't think to check my Fedora Silverblue 41 Beta laptop for a lack of an X session. I'll have to take a look tonight.

    #Fedora #Linux #Silverblue #Wayland #AtomicFedora #Xorg

  15. I just upgraded my Fedora Silverblue system to 41 Beta.

    Looks the same, working great.

    #Fedora #Linux #Silverblue #AtomicFedora

  16. I have been using this app called EasySSH to manage multiple ssh connnections, and since it hasn't been updated in 3 years, I have been looking for alternatives.

    I finally bit the bullet and started using tmux, which is in OpenBSD base. I also added it to Fedora Silverblue (where IMHO it should also be in base).

    But that doesn't "automate" my sessions.

    There are all sorts of ways people do this by scripting tmux, but I'm starting with something I didn't know existed:

    ~/.ssh/config

    To start, I'm creating shortcuts in that file for all of my connections. That way they'll be easier to start — with or without tmux.

    https://linuxize.com/post/using-the-ssh-config-file/

    And while I appreciate the power of tmux, there should be a GUI way to do this (and I am open to suggestions).

    #OpenBSD #Linux #Fedora #ssh #OpenSSH #EasySSH #tmux #FedoraSilverblue #AtomicFedora

  17. I have been using this app called EasySSH to manage multiple ssh connnections, and since it hasn't been updated in 3 years, I have been looking for alternatives.

    I finally bit the bullet and started using tmux, which is in OpenBSD base. I also added it to Fedora Silverblue (where IMHO it should also be in base).

    But that doesn't "automate" my sessions.

    There are all sorts of ways people do this by scripting tmux, but I'm starting with something I didn't know existed:

    ~/.ssh/config

    To start, I'm creating shortcuts in that file for all of my connections. That way they'll be easier to start — with or without tmux.

    https://linuxize.com/post/using-the-ssh-config-file/

    And while I appreciate the power of tmux, there should be a GUI way to do this (and I am open to suggestions).

    #OpenBSD #Linux #Fedora #ssh #OpenSSH #EasySSH #tmux #FedoraSilverblue #AtomicFedora

  18. I have been using this app called EasySSH to manage multiple ssh connnections, and since it hasn't been updated in 3 years, I have been looking for alternatives.

    I finally bit the bullet and started using tmux, which is in OpenBSD base. I also added it to Fedora Silverblue (where IMHO it should also be in base).

    But that doesn't "automate" my sessions.

    There are all sorts of ways people do this by scripting tmux, but I'm starting with something I didn't know existed:

    ~/.ssh/config

    To start, I'm creating shortcuts in that file for all of my connections. That way they'll be easier to start — with or without tmux.

    https://linuxize.com/post/using-the-ssh-config-file/

    And while I appreciate the power of tmux, there should be a GUI way to do this (and I am open to suggestions).

    #OpenBSD #Linux #Fedora #ssh #OpenSSH #EasySSH #tmux #FedoraSilverblue #AtomicFedora

  19. I have been using this app called EasySSH to manage multiple ssh connnections, and since it hasn't been updated in 3 years, I have been looking for alternatives.

    I finally bit the bullet and started using tmux, which is in OpenBSD base. I also added it to Fedora Silverblue (where IMHO it should also be in base).

    But that doesn't "automate" my sessions.

    There are all sorts of ways people do this by scripting tmux, but I'm starting with something I didn't know existed:

    ~/.ssh/config

    To start, I'm creating shortcuts in that file for all of my connections. That way they'll be easier to start — with or without tmux.

    https://linuxize.com/post/using-the-ssh-config-file/

    And while I appreciate the power of tmux, there should be a GUI way to do this (and I am open to suggestions).

    #OpenBSD #Linux #Fedora #ssh #OpenSSH #EasySSH #tmux #FedoraSilverblue #AtomicFedora

  20. I have been using this app called EasySSH to manage multiple ssh connnections, and since it hasn't been updated in 3 years, I have been looking for alternatives.

    I finally bit the bullet and started using tmux, which is in OpenBSD base. I also added it to Fedora Silverblue (where IMHO it should also be in base).

    But that doesn't "automate" my sessions.

    There are all sorts of ways people do this by scripting tmux, but I'm starting with something I didn't know existed:

    ~/.ssh/config

    To start, I'm creating shortcuts in that file for all of my connections. That way they'll be easier to start — with or without tmux.

    https://linuxize.com/post/using-the-ssh-config-file/

    And while I appreciate the power of tmux, there should be a GUI way to do this (and I am open to suggestions).

    #OpenBSD #Linux #Fedora #ssh #OpenSSH #EasySSH #tmux #FedoraSilverblue #AtomicFedora

  21. I haven't played with GNOME Builder in a while. I was able to start a C++ project, then compile the "Hello World," then run the program and export the binary to my home directory. That was easy, all right.

    This was all using the Flatpak on Fedora Silverblue 40.

    #Linux #Fedora #Silverblue #AtomicFedora #GNOME #GNOMEBuilder #IDE #CPP

  22. Today has been a Fedora Silverblue 40 production day. The computer (2017 HP Envy Intel Core i7 7th Gen laptop) is running cool, and everything is extremely stable.

    My "stack" today (pretty simple for journalistic editing/production):

    GNOME desktop
    Clipboard Indicator, Caffeine and Emoji Copy extensions
    Google Chrome browser
    Celluloid media player
    Converseen batch image editor
    gThumb image editor
    gVim text editor
    Slack app
    Sticky notes (a new one for me)

    #Linux #Fedora #AtomicFedora #Silverblue

  23. Every once in a while, #Fedora is hit by a fairly consequential bug.

    In this case, for #AtomicFedora distros like #Silverblue, we now have a Secure Boot failure due to an out-of-date bootloader.

    I didn't know about the bug for weeks because I had Secure Boot turned off (and that's one way to get around it).

    Like every other time such a showstopper bug has appeared in Fedora, the community has found and promoted a fix, which in this case involves entering a series of commands in the terminal. That fix has been floating around for a while in Fedora Discussion:

    https://discussion.fedoraproject.org/t/after-a-system-update-bad-shim-signature-silverblue-f40/120347/32

    I did it, and I can confirm that it works.

    And now there is a Fedora Magazine post on the issue with a different fix — one that I think I like a little bit better:

    https://fedoramagazine.org/manual-action-needed-to-resolve-boot-failure-for-fedora-atomic-desktops-and-fedora-iot/

    This is a pretty terrible bug — especially for non-technical users — though I don't think Silverblue is at the "stable for regular users" stage.

    What I learned from the Fedora Magazine article is that in the way Silverblue is put together, SHIM and Grub are not regularly (or ever) updated, and newer kernels don't include the older key that those bootloading programs use to verify their origin. Hence, no booting.

    For Secure Boot users, there was always at least one bootable image remaining in the system, and that could be used until the user performed the manual fix (or turned off Secure Boot).

    In my case, I only turned on Secure Boot after the fact to check for this bug, and my "good" image was long gone. But since the fix worked, I was able to turn Secure Boot back on and boot successfully. (Since then I've turned Secure Boot off again so i can boot OpenBSD on my second hard drive.)

    It's another example of the openness and helpfulness of Fedora developers and users (the Friends part of the Four Foundations https://docs.fedoraproject.org/en-US/project/#_what_is_fedora_all_about).

    And I do like seeing that a permanent fix — in the form of enabling an updatable bootupd — will hopefully land in Fedora 41.

  24. Fedora tip: The Matrix channels are VERY helpful. I read the Silverblue channel often and just added Fedora Atomic Desktops.

    Also: overall Fedora, Workstation, Join Fedora and more

    https://chat.fedoraproject.org/#/welcome

    #Linux #Fedora #AtomicFedora #Silverblue

  25. If your #Fedora #Silverblue #AtomicFedora system has an image that won't boot with Secure Boot on, I can confirm that this workaround (which I got from Fedora Discussion) fixes the issue:

    https://discussion.fedoraproject.org/t/after-a-system-update-bad-shim-signature-silverblue-f40/120347/5

  26. You know the world is upside down when you have to boot into OpenBSD to print to a wireless HP printer because Fedora Silverblue just can't make it happen.

    #Linux #BSD #Fedora #Silverblue #AtomicFedora #OpenBSD #printingproblems #HP

  27. I'm running a Samba server on my Raspberry Pi, and I'm able to log in and use it without trouble on my Debian 12 system. But on Fedora Silverblue 40, I can create, delete and read files but cannot write to them.

    Any Silverblue users have a tip on what I can do to fix this?

    Could it be something related to UID?

    #RaspberryPi #samba #debian #fedora #silverblue #atomicfedora

  28. Now that I'm running the atomic/immutable Fedora Silverblue on my laptop, I have a greater appreciation for how the BSD operating systems keep the base separate from the packages.

    I wouldn't call OpenBSD and FreeBSD "immutable," but the base systems on both seem more impervious to the shenanigans of adding tons of software as well as operator error

    #fedora #atomicfedora #bsd #freebsd #openbsd