Yardy Sardley

That would work.

I’m not sure what could be in (or missing from) your environment that would break sudo, but it’s a place to check at least.

One big difference is that sway doesn’t run as a login process (and neither does gdm), meaning none of your .profile files are getting sourced. Check how your environment variables differ between i3 and sway and see if that might be the issue.

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.

Schwede contemplated selling his car, but after racking up more than 60,000 miles on it, there was little value left in it.

That’s a pretty steep devaluation curve. Do electric cars just wear out that fast? Or is this more of a hype-cycle rug pull situation?

I’m gonna join in with everyone and recommend completely zeroing all the drives (make sure you unmount them before doing it). It will take a while but at least you will have drives in a known state and can eliminate that as a possible issue.

Linus himself uses a macbook, I’m sure the mainline kernel has decent support for somewhat recent hardware

If both engines failed, that means they would have lost hydraulic power too, which is probably the reason they couldn’t extend the landing gear or try to go around a second time.

One of the theories floating around is that a bird strike caused one engine to flame out and the pilots pulled the cutoff switch on the wrong engine. It wouldn’t be the first time something like that happened.

I don’t know, but aiming for a short runway with a wall at the end doesn’t seem to work.

The more it hurts the more it shows you really care, right?

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.

It always amazes me that French politicians have the gall (pun not intended) to even attempt stuff like this, considering the last 250 years of political context in the region.

If only people cared about workers getting trapped in cycles of desperation in literally every other industry even half as much as they pretend to care about sex workers.

Did you only try F2? It’s possible the graphical session is on tty2 - see if ctl+alt+F1/ 3 does anything

You should look into kodi. It’s a big screen oriented media player/organizer app.

Not just mp3, all lossy audio formats use psychoacoustic analysis. That’s how they figure out which data to throw out.

Not sure if sarcasm or actual disinformation. You’re not supposed to trust the aur, that’s kinda the whole point of it. The build scripts are transparent enough to allow users to manage their own risk, and at no point does building a package require root access.

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.

I second the wayland option. Then you at least have a working gui with all your settings and recent work intact while you try to find the glitch in your Xorg install.

There’s openSUSE tumbleweed. It’s rpm based like fedora and it’s rolling-release like arch. I don’t know what the 3rd party/nonfree software situation is like. Maybe someone else can chime in on that front.

I will add, as an arch user, I think you could easily tweak your current system to be less annoying with the updates, but I realize that’s not the question you’re asking so feel free to disregard that.