• 1 Post
  • 53 Comments
Joined 2 years ago
cake
Cake day: December 2nd, 2023

help-circle

  • Edit: When you say you did it manually, what do you mean exactly?

    Check dmesg output when after the wifi drops and see what the kernel is doing. That could inform your decision. I have an old asus that started having a bunch of wifi bugs too, and I’m pretty sure they made some updates to iwlwifi. No solution though, I dont really care because that machine barely gets any use. Wifi always works perfect if I stay on a tty and don’t enter a graphical session.

    That being said I wouldn’t choose fedora for an older relative unless they were really into computers. While it has become more stable in recent years, they do break things from time to time.

    If you do decide to keep them on fedora, maybe try an atomic version. That way when things break you can just roll back with no issues and pin the working deployment. Chances are they just want a web browser and libreoffice so the learning curve wouldn’t really matter to them.





  • i3 is configured to use the program dmenu by default. A common replacement for that is rofi. I use wofi on sway. Rofi has more features, wofi is pretty simple but you can customize with css.

    Sway will read the i3 config you already have if you put it in the sway config folder. Then just download dmenu if you want that same behavior. Some things like mod+enter is binded to i3-sensible-terminal, so if you don’t have i3 installed on the box it won’t find a terminal to open. The fix is to change the binding to your preferred terminal emulator.

    All in all the transition is pretty painless.


  • A lot of times you will see the format string for the fedora version in the .repo file. This means its probably looking for f41. Since fedora updates fast, third party repos are usually slow to move to the next version and this repo probably doesnt exist causing dnf to fail. You can try and change the format string to the last available version. It usually works without issue, and updates aren’t disabled as long as the vendor updates that version










  • I think that it’s definitely a good case for overlaying with install. They say to use it sparingly because it increases the chances of something breaking, but that doesn’t mean it will. Something like a VPN usually needs liw level access that container isolation makes difficult.

    I’ve only had 1 issue on silverblue years ago where I couldn’t update because I had vim overlayed and they fixed it within a day or two.