And that is still largely true - I’m still running XFCE with xorg on Debian, and I think the only issue I’ve had was Waydroid.

Will there come a day where what you say is true? Yes.

However, right now, a more apt example to convey your point is systemd; that’s true for most distros with a lot of community support. Even then, its hold isn’t absolute - Alpine seems like the most livable non-systemd distro, though I could be wrong.

As I’ve commented elsewhere on this post and others have said, this is a change that affects pretty much no one. I didn’t even know MBR (legacy BIOS) partition tables on UEFI boot was possible, honestly.

By no longer putting in the effort to maintain this bit that no one uses, work can be put to something someone uses.

Also, with Linux, specific distros can get encrapified (kind of happened to Ubuntu), but as others have said, there’s usually always another distro to jump to at worst.

For those panicking about it, this is not something you need to worry about. Here’s what this actually does:

Enforce the use of GPT partition tables for all UEFI-based Fedora installations for x86 architecture. This removes support for installing Fedora in UEFI mode on MBR-partitioned disks on x86 systems

You probably have already been using GPT on your UEFI system since you had a UEFI system. Even if you somehow were using MBR, this probably;

1. Won’t break existing installations, as it’s merely support for installs of this type
2. Would not be a problem even if somehow the broke existing installs, as it’s not difficult to convert MBR to GPT.

As much as I resonate with the issues, in this case, this isn’t what they’re doing at all.

This drops support only for UEFI on the MBR partition scheme typically used by a BIOS setup, which I honestly didn’t even know was possible.

This ends support for no hardware - almost all distro installations on UEFI have defaulted to GPT partition tables for a long time.

That’s not what this is saying.

It’s only support for UEFI on the old MBR partition table - GPT partitioning has been the default for ages now.

Do you have FluidSynth installed? I had similar issues recently - I just have a script that restarts pipewire automatically on login.

PS5 controller also works.

I booted Buildroot with kernel 5.17 on a Pentium II laptop off a CD I burned once - I needed to dump a drive once and that was the only hardware I had on hand that could dump 2.5” IDE drives and had a working CD drive so I could boot something other than the operating system installed on the drive:

Honestly, I rather like the default XFCE terminal. In fact, I was using it even before I used XFCE back when I was just playing with the default GNOME in VMs before I daily-drove Linux.

Is this xfce-winxp-tc? I ‘ve played with it before and it’s awesome.

However, I don’t use it because while the XP start menu replica is cool, I need a Win7-style search bar, and Whiskermenu sticks pit like a sore thumb here.

I think a 7 replica would be awesome, but I think some parts of Aero can only truly be replicated with a new WM and DE, such as the color changes in the taskbar for different applications. Many themes just fall short - proportions and effects are slightly off and such.

I think the main other distro I used in that VM at that time was Fedora 37 at that time, which should have also been using Wayland. I had made the VMs because I was working on Debian packaging for an application I liked and wanted to make sure the modifications I made didn’t break it on other distros.

I’m not necessarily a “Wayland is the embodiment of evil” kind of guy, but I love XFCE and pretty much won’t leave it unless it dies, meaning I’m on Xorg until they port XFWM4.

Not really, but I switched from Qwerty to Workman years ago, though I can live with Qwerty if I have to when it’s on someone else’s machine.

I use Workman because I found Colemak rather hard to learn, mostly because of the position of S being one over from where it was on Qwerty.

In order for them to be allowed on exams, I ghink they’re required to have a non-QWERTY layout.

Linux (and I think maybe even macOS) can do Ctrl+Shift+U, and then you type the Unicode hex number.

Discord also has an app from Linux - you can get it as a Flatpak (an official one) or as a native package, although they don’t provide a repo for native packages and expect you to manually download a package file every time there is an update.

For the native packages issue, someone created an apt repo on Github, and if you look in the CI routine, you can tell they’re using the official Discord packages and not modifying them.

Honestly, I should probably be sandboxing it more.

It’s annoying to use a proprietary service, but the This Might Be a Wiki community is rather enjoyable.

It’s not just packages. Ubuntu performance is terrible - it runs so much worse than other distros in VM. I don’t know about spins, but main Ubuntu takes 30 seconds to respond to some button presses whereas it’s nearly instant in other GNOME-using distros given equal or less resources.

Can you give more info about what you tried (commands, GUIS, etc)? What does it say when it denies your request?

Also, timezones usually go by cities - I for instance, I’m on AZ time as well, and the time zone for me is called America/Phoenix.

OP explicitly said Mint isn’t what they’re looking for.

I think my very first exposure to Linux was when I got a Pi 3 for Christmas when I was 10; by next year, I was trying out Ubuntu 16.04 in a VM.

However, it took several years before I began daily-driving; I had thrown it on an old laptop during my sophomore year of high school that I mostly used from the couch.

I then did a “test install” of Debian Testing on my main desktop pater that year, which just became what I used every day and quickly just became my main operating system.

I soon installed it on everything else I owned and haven’t looked back.

Exciting, as always. I just hope they can eventually add CMYK support.

I get color spaces are hard and there are workarounds involving Scribus, but I wonder if one could just have a custom SVG attribute that would be ignored by a standard SVG renderer (we’d have a similar placeholder RGB color, which we maybe would allow to be manually modified) and read by Inkscape when rendering to a format for print like PDF.