… Stonking Stingray?

Running out of names, Canonical?

Debian - the very slight value hassle of having to install the web blobs for glances manually. This is really minor, because it only comes up occasionally, but it’s rare enough that I can’t remember what the path is each time.

That said, I totally agree with Debian’s stance on the issue, and I think glances should change their process. Debian’s way makes me acknowledge the risk of installing the blob. It’d be nice if there was a package I could install after going, yep, I know this is potentially dangerous.

Honestly I thought I’d be disappointed with Debian on my gaming machine, but it works fine. I updated Wine to the newer version on their site (instead of using Debian’s packages), and it works great.

Debian on my server, my desktop, my laptop, and my gaming computer. That last one might be the most questionable choice, but so far it has been working well.

Just works. No issues.

You have your answers, but I just want to note that what I do is run rsync from cron nightly, without the delete option.

Basically this reduces the chances of losing something by accidentally deleting it on the primary drive. Every few weeks/months, I run the rsync command with the delete option to clean up.

It’s not a perfect backup by any means, especially since I could erroneously delete something right before that second rsync command and lose it for good. But it does provide a measure of safety.

Debian, on the server, the laptop, the desktop, and the gaming machine. Debian.

I started with Slackware many years ago. Eventually switched to Kubuntu on my desktop and laptop machines, then later the server switched to Debian. The desktop and laptop switched later.

Ah that would do it. Disappointing. But thanks for the suggestions and finding that.

Yeah 3.0 on Trixie.

Sounds like that gimp-data-extras package shouldn’t apply to 3.x. So maybe that’s the fundamental problem.

Unfortunately, the message in the terminal isn’t helpful:

scriptfu-Message: 19:50:36.837: Error while executing script-fu-alien-glow-logo:

That’s it. There’s no additional info.

I just downloaded the Gimp appimage, but it doesn’t have the logo generation scripts in it. I feel like they’ve been abandoned and no one noticed.

I tried editing one of them to change the -1 in the gimp-text-fontname call to None, then Null. Restarted GIMP after each change, but I’m still getting the error.

But it sounds like it’s an error in the GIMP distribution…

This reminds me… My server demands to be known as hostname.local on my network. The other machines just respond to just hostname. I really should figure out why that is.

Pretty?

In my mind, I equate Gnome with OS X, while KDE is more like Windows.

I can use both competently, but I prefer KDE. Back when I used Ubuntu, I’d always use Kubuntu.

I’ve been using Linux almost exclusively at home since the late 1990s.

I have very few issues with it. I think Debian’s tendency to break my Nvidia drivers on my gaming machine is probably the worst, but that’s just a matter of running the installer again. It’s not really Debian’s fault, it’s just updating the kernel.

I wish WINE would let me use Bluetooth or even ANT+ connections to my smart bicycle trainer, but connecting via the phone works quite well most of the time (unless my wife starts the car and it grabs my Bluetooth phone connection). So that is my biggest wish. Well actually I wish Zwift ran natively on Linux. That’d be even better.

Funny that’s how my Slackware upgrades always went, but I’ve had a great experience with Debian every time.

In my previous job and my job at the bike shop, yes. But I don’t really care, its issues aren’t my problem.

Interesting. After I got the new Debian running, I just updated the source for Jellyfin (and a few other packages) to Trixie, and it updated just fine.

Well I finally upgraded to 13, a few months later. The only issue was the blob file in glances, which I was ready to deal with. Oh and I had to install php-mysql.

I don’t like that you can’t start the Debian upgrade and just walk away. It stops and asks you about configuration files, so you have to babysit it. Other than that, it works well.

For some reason, if I were doing the physical media route, I’d want to ship the drives via FedEx or something similar. Presumably this isn’t the only copy of the data. Even if you still need to go, just dragging these drives around seems risky.

I used VirtualBox on Linux to host my Home Assistant server for a while. I kept having odd issues with usb devices. I’d have to disconnect and reconnect them to get them working again.

Many people in the HA help groups say not to use VirtualBox, and at first I thought they were basing that on old info. But then I started having issues, too. On the other hand, kvm has been rock solid for a long time.

So I’m glad to see they continue to develop it, but I wouldn’t recommend it for heavy duty use. It’s useful to dipping toes into virtualization, or maybe for running systems for the short term (a few hours here and there, or something), but for long term use, I’d go another route. It’s certainly easier to set up the network in VirtualBox, I’ll grant that - it took me a while to get it right for HA on kvm. (Of course, that’s a one-time setup thing, too - I shouldn’t have to touch it again. And don’t ask me what I did, because I don’t remember!)

When I upgraded the desktop and laptop machines, I didn’t run into many issues. Had to reinstall the Nvidia drivers on the game machine. And deal with glances, but I mentioned that before.

I’ll probably update the server to 13 next week.

I had to rewrite part of my php-based photo management system, as it relied on a library that was originally written for php 4 or 5 and hasn’t been updated. Fortunately that wasn’t too hard. There might be other things lurking like that, but they aren’t critical problems - I can deal with them at leisure.

Did you go straight there, or go through 12?

Hey. I’m going through this right now. My server was 11, and I wanted to go to 13. I definitely didn’t want to get into a situation where the server required hours and hours of repair.

I’m halfway there. The upgrade to 12 went smoothly. The biggest headache was glances, first from the lack of web interface (which I was ready for), and the lack of RAID support (not ready). I might do the switch to 13 next week.