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.
A typical bike-riding leftist urbanite who also happens to be a hockey-crazy Western Canadian.
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
I’m ashamed at having had a moment of celebration when the ceasefire happened. Treachery should have been obvious.
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.
GNOME spawning 3 new DEs every time they have a major version update
Welp. It was nice to feel some hope for a couple of weeks. I’ll cherish the memories. I don’t think I’ll be feeling that emotion again for a very long time.
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.
Probably have a few cards running the displays and the rest of them mining some sphere-themed memecoin
Alright, but if I end up getting stuffed in a goo-filled pod so the AI can suck my energy out through a massive plug in the back of my head, I’m gonna be pretty upset.
Username checks out
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.
Definitely looks like the AI has been sending her transcripts of the vacation it’s been attending with her family.
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 already don’t trust AI, there’s no way I’d want it to be the arbiter of potentially critical job-related information in a workplace. For probably less money than licensing and running an AI, a company could just hire a stenographer to sit in meetings all day, take notes, and send those notes to concerned parties. Better yet, why not get certain people to send info directly via email, instead of scheduling a bunch a pointless meetings. How’s that for innovation
I think this is a good enough reason to actually put in some effort to phase out ipv4 and dhcp. There shouldn’t be a way for some random node on the network to tell my node what device to route traffic over. Stateless ipv6 for the win.
Banks having “sound” balance sheets while losing actual boatloads of money to sub-prime lending makes me a little nervous, having lived through the year 2008 and all.
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.