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.

I’ve been enjoying my Thinkpad E16 1st gen AMD on Debian 12. You do have to run a newer kernel to get it working. I ran into a bit of Wi-Fi trouble because I accidentally got a Realtek model, but I’ve long since fixed the issue entirely - I’ve posted the solution elsewhere here.

On another note, maybe we should just have a yearly hardware recommendations post pinned on this forum - it feels like we get a question like this every week or so and they sort of clutter the forum, no offense intended to OP.

Edit: Here’s my Linux Hardware probe from when I first got the laptop https://linux-hardware.org/?probe=1e50fb1862

Borg Backup, whenever I feel like it - usually monthly.

On an unrelated note:

Why do you have Teddy Ruxpin as your desktop background, and more importantly, why do I feel such reverence for it as a very non-stereotypical background for a Linux user?

I use Debian with XFCE, but while I love XFCE, it might not be everyone’s thing. If you do give it a try, make sure to use Whisker Menu instead of the default app menu, and also set keyboard mappings to your liking.

P.S: Ubuntu’s pushing for Snaps, not Flatpaks. Flatpaks are actually pretty good - makes it really easy to install a newer software version when the one in Debian repos doesn’t suffice.

Also, it’s not only Ubuntu pushing for Wayland - most distros or DEs either have it working or are working towards it (there are some exceptions). XFCE is still on xorg, but working on Wayland. The problem is xorg is on life support and not getting a lot of new features.

I’ve had a very good experience with a similarly-speced AMD E16 gen 1.

The only issue I’d warn you about is the Wi-Fi modem might be a Realtek on some models. Mine came with one, and while on recent kernels, it mostly worked well out of the box, it had one issue: something went weird with ACPI when I switched between certain networks, which caused the card to crash and completely disconnect to the system unless I rebooted. I was able to find a fix by changing some options with modprobe.d, which I detail here: https://startrek.website/post/14342770 . Since that, it’s been an extremely smooth experience.

Same. I love my E16 Gen 1.

For battery life, I’d recommend you install CoreCtrl so you can adjust your power settings. That, combined with a few other things (I think the Arch Wiki covers most of them) allows me to get quite a lot out of my Thinkpad in Debian.

I’ve had a good time with my Thinkpad E16 Gen 1 over the past few months (definitely lower spec than your machine - pretty much all of them have only an iGPU). A lot of them are still upgradable - I upgraded mine from 8GB of RAM to 24GB, and the thing had dual drive bays, so I just left the stock 256GB Windows drive and put in a 2TB alongside it for Linux stuff.

As long as you have a recent kernel, hardware support is decent, so long as you avoid the models with Realtek (my E16 does have Realtek, but I managed to smooth out issues).

BTW usually the graphics glitches weren’t immediate, but would come after waking it from sleep a few times.

As an ex-Linux on Surface Go 1 user, I didn’t like the experience. Under Debian Testing, it was always mostly usable, but I’d come across the weirdest bugs, like graphics glitches. Also, last time I checked, the camera was miserable to set up - I got it working, but it’s really weird. Secure boot was also really painful.

Running Linux on the Surface Go made me curse the Surface line and put the Go in a junk drawer. I might go back to it one day, but I have no reason at the moment. Still, if you already own one, it’s worth a shot.

If you go ahead, though:

1. Whatever easily supported the linux-surface kernel.
2. I really don’t know. I don’t quite use Linux in that manner.
3. No. SD cards are slow, so the system will take an eternity to load. Put personal files on the SD and the install internal, not the other way around.
4. I have no idea about the pen, but the keyboard mostly worked fine. I remember it having problems in the Debian installer, so I had to use a USB hub dongle and a keyboard to install, but after that I remember it working pretty well both mainline and linux-surface.

Debian is on the right track. XFCE might work - I remember it running pretty well on a laptop with 4 gigs.

Not necessarily - pavucontrol switched to GTK4, and there are a lot of other applications that I use that are on it as well. If XFCE stays on X11, I wouldn’t be able to run any application that updates to GTK5 (except through some hack like running Weston nested in X, which I used to do when I used Waydroid).

Stares in Debian Testing. (Though I use Bookworm on my laptop, probably soon to be Trixie. Nice thing about Trixie is I’ll no longer have to use the Backports kernel on my Thinkpad and can just stay on the LTS one.)

Let’s just hope XFCE can finish the transition before then. If not, I am not looking forward to having to shop for a new DE.

I’m not sure about NVIDIA drivers. Otherwise, it depends on what kernel your distro is using; if it’s Debian, there’s a chance you might have problems, though you could install the backports kernel, which I do on my Thinkpad E16.

I think it wasn’t actually Stallman - it’s a common misattribution.

Depends on your hardware and distro. Might not be so bad assuming it’s one of those old Thinkpads. Also, though, if you’re on Debian; they deblob their kernel already and put the blobs in separate packages so they can be optionally used. Don’t install any blobs and you’re good.

It’s mostly a breeze. The only misery I can recall is I remember I had a wonky knockoff Arduino board that kept jumping serial ports, but that was a hardware issue.