Yardy Sardley

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 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.

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.

Points are completely invisible in list view.

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.

Honestly, huge shout out to the wave of enshittification crashing through Google and reddit and forcing me off their platforms. Decade-long debilitating addiction solved.

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.

You know a conspiracy theory is psychotic when it presumes a massive multi-billion dollar corporation would manipulate consumers into supporting their left-wing agenda.

They’re obviously doing it for the money.

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.

Depending what format of audio, you can embed the image into the metadata

I mean, technically Linux is still at 2.6, they’ve just been making up version numbers for the last 20 years or so.

I never really thought about it before, but it seems obvious now. Trekkies and open source tech folks would have a massive overlap, and Lemmy kind of exists perfectly within that intersection of utilitarian principles. So of course we would all find each other here.

For the past couple weeks it’s been Flower Moon by Dooms Children

You wasted 3 hours of your life so far lol

But yeah. I find the most mysterious and time-consuming of problems are usually caused by a very minor detail that is so obvious it gets overlooked immediately.

And even if you know that’s probably the case, sometimes your brain will just discard information that isn’t consistent with its assumed reality, and it tells you the piece of code you just read is fine when it’s obviously not.

Troubleshooting/debugging is fun.

And the data harvesting app is nothing more than a stripped-down browser with the company’s color scheme slapped on it.

This happened to me a few weeks ago and the pain is still fresh. Please tell us your data is safely backed up, OP.

I’m trying to figure out what demographic would be downvoting this to hell. Arch users getting triggered by a clickbait title? Arch haters trying to cope with a somewhat charitable take on arch users? Or are we all just downvoting for the meme?

The only difference between those two versions of linux is that the new one was built with a newer version of gcc. That doesn’t really narrow the problem down, though. As far as I’m aware, emergency mode is caused by either a kernel panic or a failure to mount a needed filesystem. I’m leaning towards a corrupted kernel, since it doesn’t sound like you changed your fstab or had any problem mounting /. I would run fsck -f on your boot partition, then try to re-download and reinstall the new package.

If that doesn’t work, then you can add IgnorePkg = linux linux-headers to pacman.conf so you can update without installing the broken package, until you resolve the underlying issue. Or your can install a different kernel altogether.

As for preventing problems in the future, there’s only so much you can do. Check archlinux.org before updating to see if anything requires manual intervention, and pay close attention while running pacman in case something goes wrong. You already seem to know the most important part, which is to keep a set of packages that are certain to work, so you can easily downgrade if a crash does happen.