

Incorrect, actually. Firefox for Android uses Gecko like the desktop version, while the iOS version is stuck with WebKit.
“Life forms. You precious little lifeforms. You tiny little lifeforms. Where are you?”
- Lt. Cmdr Data, Star Trek: Generations
Incorrect, actually. Firefox for Android uses Gecko like the desktop version, while the iOS version is stuck with WebKit.
Maybe your GPU is set to a low power mode? I wonder if something like CoreCtrl might help you.
I don’t have this problem on my Debian 12 machines, which both use this browser on XFCE, but they have AMD graphics. Then again, I don’t online game that often, but when I have, I don’t recall any problems.
Not necessarily. It’s currently on the latest ESR version. I use the repo version on my laptop (stable) and testing and don’t have this problem.
In recent years, Debian has gotten a lot better about keeping stuff on the current ESR version.
Actually, with the work done on box86/box64, you might be able to get stuff running well - last I heard, they got triple A games running around 45 FPS on Asahi on Apple M1.
However, it would be totally unsupported, and who knows how well the Apple M series optimizations will work on another member of the ARM family. (Although, I wouldn’t be surprised if it’s been tried on Ampere at least once.)
Really, the biggest issue is probably power usage - I don’t know if it’s enough to increase your power bill significantly, but it would definitely consume more power than say, an i7. This is due to Altra CPUs really being more for server usage - performance per watt will likely be better overall for those kinds of workloads, but you’re probably not going to make full use of the hardware. These systems are really more of server dev kits than daily drivers.
For a desktop, I’d just recommend a PC with a high end consumer grade CPU like an i7 or Ryzen 7.
At least later GTK fixed the whole file picker thing, though.
I mean, they literally defended the rights of the devil. That automatically makes it a great episode.
How old is your laptop? Pretty much every Windows machine I’ve ever owned after a certain year requires you to type in your Bitlocker key, including my first-gen Surface Go from 2018.
Also, you often have to manually set up encryption on most Linux installs as well - I did it for my Thinkpad. I need to do it for my desktop as well - I should probably do a reinstall, but I’m thinking of backing everything up and trying to do it in-place just for fun. On top of that, we can finally transition to btrfs.
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.
Meanwhile, me:
My head canon is there is a different Musk they’re talking about that isn’t a Nazi, and Lorca’s name drop was mirror universe stuff. 😂
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.
I use the Chicago95 XFCE theme, which modifies the bash prompt.
C:\home\dexcube\Development\piper\build> python3
Python 3.13.2 (main, Mar 13 2025, 14:29:07) [GCC 14.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from decimal import Decimal
>>> Decimal('0.1') + Decimal('0.2')
Decimal('0.3')
Well, this is from Cast Your Pod to the Wind, which is full of rejects from The Else and random podcast tracks - granted some of them are really darn good rejects like “Brain Problem Situation”.
I think my taste is also skewed towards the weird semi-experimental tracks in general - I am a big “If Day for Winnipeg”.
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.
Weird. I don’t have this problem on my laptop or desktop; both use AMD GPUs.