I do use that sometimes. I was able to use it to look at similar laptop models to my Thinkpad to inform my purchase. I then uploaded a probe when I got my hands on it.

I see the need for posts with recommendations in some ways, though - neither the main site or the forum are the easiest to parse, and it doesn’t have every computer model. It is nice to have a human to guide you - it just isn’t so nice when the community starts to get cluttered with these requests.

Honestly part of it is some of these people just don’t do online research, and they might not read the community rules anyway, but it would be nice if we had an explicit rule that hardware recommendations either go to the annual post or be for very oddly specific needs.

I have been using Debian - it’s the only distro I’ve used in my 3 years of Linux as a daily driver, and I started using it in VMs instead of Ubuntu a while before that.

I also like stability and Debian’s community-oriented nature.

I am currently on Testing for my desktop, but plan to either go stable or do a reinstall when Trixie hits stable - I’m tired of rolling release and my programs changing frequently. I have really enjoyed Debian 12 + Flatpaks on my Thinkpad, so I think I will do that when summer rolls around.

Oh certainly. OP is probably doing something wrong. This was just a good excuse to vent about real problems with GTK.

On another note, I sometimes get tired of “Please recommend a good laptop” posts - they’re always just the same old advice: “I liked my Framework” or “Get a Thinkpad”.

I kind of wonder if we could just have an annual mega-post for Linux hardware that gets pinned and mentioned in the server links. For example, “(Pinned) Linux Hardware 2025”. Then we have a rule that you don’t do hardware recommendation posts unless it’s something extremely oddly specific, like “Best Linux hardware for a Pentium II build” or maybe even a question about people’s experiences with VFIO on recent motherboard.

I mean, this might be a bit more your fault in this case, but I agree with the sentiment.

They’re always changing something about the CSS sheets, and I find it a pain to develop for, granted it’s been a few years since I last touched it, and on a very hobbyist level at that. I quickly switched to Qt for that project. Now I use wxWidgets, which I guess just uses GTK, but I like that I don’t have to directly deal with GTK.

Fiddle with OpenRGB and see if it works. If it doesn’t, check if there’s any open issues for your model of card - you might be able to aid testing, and if you’re likely, someone might have already made a branch that hasn’t been merged yet. That was the case with my keyboard.

Googling it, some might also have support for using hooking to the motherboard RGB header instead of internal controls.

Tried that already.

Based on the report, this seems to be an actual bug - it was working fine for everyone before the update and only happens in the presence of FluidSynth.

Ubuntu probably hasn’t had this version of PipeWire yet.

My work around is working just fine for now, though.

I’ve done it with ffmpeg before - I think the command’s on the Arch wiki. I preserved subtitles as well. I overall remember it being pretty reasonable since I didn’t set it up to re-encode, just pass through original video.