The GPU driver issue would really only be a problem for Nvidia stuff.

Ransom may be too dumb to understand it, but he is principled enough to accept and support it.

When all else fails:

s/tf/e/

“Oh, we don’t do it for the numbers. We do it to quiet the voices in our heads.”

I love Lower Decks as a while, but I think this is the single best-written line in the entire show.

No! Needole is already bad enough!

They Might Be Giants collaborated with them and released a new t-shirt in 2025, I think to commemorate the anniversary of their initial collaboration back in the mid 2000s.

Either that, or OP amalgamated several occurrences in TNG…

I wish Lemmy had a way to distinguish between disliking the news and shooting the messenger.

?

10 minutes of Memory Alpha searching yields no results. I’m truly stumped.

EDIT: I see mentions of Beverly Crusher getting turned into a dog by Q, but nothing similar for Riker.

For me, as long as Debian still packages it and disables these features, I’ll be fine, but LibreWolf looks more and more tempting these days, and having tried it a bit, I can live with the minor annoyances.

The Star Trek IV punk is one of those jokes that’s so unfunny it causes an integer overflow and loops back around to absolutely hilarious.

I feel like it was more than the package manager whining; I think xorg literally wouldn’t start after the update, although it’s been so long now that I could be misremembering.

Honestly, I probably could have salvaged the install if I’d wanted to without too much difficulty, but it was just a VM for testing distro packaging rather than a daily driver device.

Still, what you say is good to know, and perhaps I should hold back on the Pacman slander. I’ve just been using Debian for around 4 years now and had pretty good reliability; then again, Debian (and most distros, with their pitiful documentation) would probably be very hard to use without Archwiki.

Eh, I disagree with you on Pacman. It could be possible I was doing something stupid, but I’ve had Arch VMs where I didn’t open them for three months, and when I tried to update them I got a colossally messed up install.

I just made a new VM, as I really only need it when I need to make sure a package has the correct dependencies on Arch.

Eh; testing doesn’t break THAT often. Having used it on many of my devices for almost 4 years, I can count on one hand the number of times it broke in a way I had to chroot in to fix it.

This is very unlikely to be because they are using testing.

Still, using Debian Stable is probably a smarter idea for this user.

I like using this on my desktop, but it’s way too easy to trigger this by accident on a laptop, so I disable it on there.

My best guess is that it’s not a Flatpak permissions issue as others are claiming; the software is just trying to use your iGPU (which is usually crappy) instead of your dGPU.

Try taking whatever command you use to start the program and tacking DRI_PRIME=1 on the front. This has often worked for me on applications regardless of whether they’re native or Flatpak.

The weird thing about that is I feel like whoever are Bashir’s commanding officers during the rest of his career would have had to have hand-picked him despite that, and thus wouldn’t have qualms about promoting him either.

iOS has been getting a bit buggier for me these past few years, but iOS 26 is a whole other level of bad.

With what Google’s been doing to AOSP, I just hope GrapheneOS and LineageOS can hold on just long enough until we can get some livable solution for Linux phones.

I like to use pythonz in this case; it’s a tool to manage Python installs, and it puts the installs in a directory under your home directory, not affecting anything in the system.

It does build each version from source, which introduces some quirks; I’ve found compilation for some Python versions works better with clang, and sometimes, you need to enable build options.

Still, I think this is a good way to do things; just start whichever Python version you want, and then create a venv with it.