A typical bike-riding leftist urbanite who also happens to be a hockey-crazy Western Canadian.

  • 0 Posts
  • 38 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle
  • Such is the problem with dictators in any situation. A benevolent dictator might be one of the most productive ways to run a project, but at some point there has to be a successor. Even a mildly-less-benevolent dictator could cause a lot of damage. Linux needs a governance structure with checks and balances even if it means slower decision making; it’s too important to let fall into the wrong hands.





  • It definitely could be a hardware failure, but if the system still boots fine, it’s probably not that. Based on the symptoms, I think you might have clobbered your PATH variable. This can happen when you do something like PATH=/new/path/ because the variable gets overwritten. You have to remember to preserve the existing value with PATH=$PATH:/new/path/. Don’t worry, this is reversible.

    The best thing to do would be to fix or temporarily remove the commands you used to set PATH in whatever profile or .rc file it’s in. You can run whatever text editor you have installed by specifying the path to the executable. I don’t know exactly where vim is on Fedora, but it’s probably something similar to /sbin/vim or /usr/bin/vim. Keep trying locations until you find the right one. Then log out and back in and it should be fixed.

    You might also be able to login as root and use the shell normally to fix the problem, depending on which file contains the faulty command. Hopefully this helps.











  • A really common issue with sway is that it doesn’t run as a login shell, so none of your .profile or other environment settings get sourced when you login. I think that might be the problem here.

    Try closing your sway session, then login to a tty and run sway. If the qt themes work properly then it’s definitely an environment issue.



  • Fellow Arch user here (btw). It’s exactly the same as building AUR packages. Clone a git repo containing a PKGBUILD, use makepkg to build it, and pacman to install it. The nice thing is you can host a repo of your built packages and install them on other systems really easily. The big downside is that dependency management is not automated, so it will take some time and annoyance to map out what packages you need to build and in what order, if you want a fully source-bootstrapped system.