Yardy Sardley

Imagine basing your appeal on the equivalent of a courtroom seance. This is the world we live in.

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.

To interject with a somewhat pedantic point, nothing is truly apolitical. But there is something to be said about sensing the proper time and place to start a political argument.

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.

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.

Asking out of genuine naivety, why do you do that?

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

Yeah, I really wish people would be a little more tactful when they go on performative tirades like this. It’s giving “old man yells at cloud” energy. Ridiculous behaviour when you think about it. People can block clouds, yelling is worse than useless.

To be totally fair, nostr’s whole thing is that users can delete all of their federated data if they want to, so it makes sense if they are upset about having their data copied to a place they can’t control.

Not sure how realistic that is with the data being publicly accessible via the web, but I wouldn’t be surprised if the they have some kind of license that gives the dmca request the ability to hold a nonzero amount of water. Then again, I wouldn’t be suprised if completely fails, either.

I’m ashamed at having had a moment of celebration when the ceasefire happened. Treachery should have been obvious.

If it’s through steam, I wouldn’t expect there to be any issues.

Just make absolute certain you have a backup copy of any save files before deleting your current OS, for the sake of your relationship… I can only imagine how many hours someone might have put into a game that came out in 2009. Definitely not speaking from personal experience haha

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.

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.

Have you ever noticed those low effort reposts also getting the same top 10 comments as the original? It’s slop all the way down.

GNOME spawning 3 new DEs every time they have a major version update

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.