Yes, they can indeed be a problem for people with allergies. In my case dogs (and cats unfortunately) trigger respiratory issues. I had that issue at a workplace where dogs were allowed, not fun times. And unfortunately medication like antihistamines are not an option for everybody, personally I get extremely drowsy from them, even from the latest generation meds.

Sorry, the bomb was running MacOS. Your command was not valid and you’ve doomed us all.

Nah, I’m also fine with it. Fingerprint sensors hate me anyway, on every phone I owned I needed to rescan my prints every few weeks or so because they just won’t recognise me after a while. These days I just use passwords and pin codes.

Yeah, this definitely makes me feel old. 😅

Isn’t dendrite formation and the shorts they can cause a much bigger concern when dealing with old batteries that are being charged 24/7? Asking a genuine question here, so please don’t shoot me if I’m wrong. 🙂 I’d love to hear more about the most common failure modes and causes for li-po/ion batteries.

X11 is stuttery

Not for me

unsecure

Source?

unmaintaned

Received a number of commits just last week: https://gitlab.freedesktop.org/xorg

can’t really be updated for new features that are pretty important in 2024 (VRR, HDR).

VRR is supported, at least on AMD: https://wiki.archlinux.org/title/Variable_refresh_rate

For HDR you have a point, afaik.

Wayland gets so many more of the basics so much better than X11 it’s not even funny anymore.

And yet X11 works rock solid for me, while Wayland still crashes whenever I so much as look at it wrong. The amount of time and work I’ve lost because of Wayland crapping out on me isn’t even funny anymore. On AMD by the way, so no blaming Nvidia’s crappy Linux support.

Wayland will probably be the better product one day, but this day is not that day, at least not for every use-case. Great that it works fantastically for you, I genuinely advise you to keep using it, but keep in mind that ‘mileage may vary’ from person to person. Personally for now I’ll stick to X11, as I need to get work done and unfortunately don’t have time to muck around with Wayland’s antics.

Definitely a case of ‘to each their own’. I’ve got one at home, I never want to go back to mucking around with two monitors whether it is for work or gaming.

Unfortunately I just want to be able to work though and Wayland keeps hanging and crashing without producing any relevant logging, despite the fact I’m working on an AMD iGPU.

In the end Wayland and X are tools, if a tool doesn’t fit the job it gets replaced. I don’t care X is dead, at least it works for me. Probably not the most popular thing to tell around here, but it’s what it is.

Seems the CPU has become the bully these days:

CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
Keyboard: E
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
CPU: hey keyboard do you have anything for me?
…

This could be shorted to if your device has no driver it wont work which is obviously true.

What I tried to tell is that if you have to rely on community driver projects, don’t expect fun times, at least not when it comes to Realtek in my recent experience.

If you have very recent hardware and you find it doesn’t work out of the box on stable options the easiest thing to do is install a more recent kernel.

I already had the latest available kernel at the time, as in: the very latest officially released kernel by kernel.org. Ubuntu was just a last-ditch effort as it will sometimes have drivers included that other distros might not have, normally I wouldn’t touch it with a ten-feet pole and go either Arch or Manjaro. The driver simply wasn’t included in the kernel. How do I know? Because I stumbled upon some discussions that mentioned the lack of support and 3 kernel releases later support for my card was specifically mentioned in the changelog.

Respectfully if DKMS wasn’t automatically kicking in then you configured it incorrectly. It’s a lot easier to just rely on a package that sets this up for you properly.

Yes, like a Realtek-XXXX-dkms package, which simply didn’t work. I’ve configured stuff for DKMS before, scripting stuff for Linux is part of my daily workload, so yeah, you don’t need to tell me scripting beats doing stuff manually.

The fact that getting an f*cking wifi card to work takes this much effort is what I meant with ‘not fun times’ and for me validates the meme, anecdotal as it might be.

Resorting to other distros, configuring additional repos so you can install a different kernel version, having to try different community projects to see which gives you a working driver, having to deal with getting DKMS to work, this is all stuff which hampers Linux adoptment. And without more adoptment we won’t have to expect more support from manufacturers for desktop related consumer hardware. So yeah, that does make me cry a bit. It’s a catch-22 unfortunately.

It was the driver, now that support is provided by the kernel it is rock-solid.

In my cause it was actually a newer type of Realtek chip. 😞

Absolutely not outdated. I had a horrible time getting my hands on a working driver for the WiFi card in my brand new laptop last year. Horrible enough to resort to Ubuntu and even that gave me the finger. When I finally had it working I had to manually rebuild the damned thing each kernel update because I couldn’t convince DKMS to do it automatically. Had to wait two or three kernel releases for the card to be supported ‘out of the box’.

So no, fuck WiFI drivers in Linux. If it is not in the kernel and the manufacturer doesn’t provide one, don’t expect fun times.

It most certainly does. It’s the only distro that I do not trust anymore to do a proper job of automatically partitioning your drive during setup, after getting complaints from my parents that Ubuntu refused to install updates. Turned out it had created a rediciously small boot partition and was now complaining that it had not enough space left to install new kernel versions as they kept around all old ones. “Because users might want to use those”, according to their documentation. Bitch, you market yourself as the distro suitable for absolute beginners, but you not only expect them to know what a kernel is, but also that they clean them up their selves? What an absolutely moronic decision.

I’ve had broken installations after upgrades to a major version in the past and I’ve seen a number of colleagues switch to plain Debian or Arch derivatives after Ubuntu decided to crap out after a major upgrade.

I’ve seen Ubuntu systems not being able to upgrade due to circular dependencies that couldn’t be resolved by Apt, package Foo requires Bar, Bar requires Baz, Baz requires Foo. Or even packages from their own repository that couldn’t be upgraded because some dependency wasn’t available anymore.

Just a handful of the issues I’ve encountered with Ubuntu. Personally I’m done with that distro. If it works for you, by all means use it. But I don’t help friends and colleagues (we all get to choose our own distro fortunately, but also have to fix issues ourselves) anymore when they decide to go Ubuntu. Use a proper distro if you want my help, not that Fisher-Price ‘My First Linux’ crap.

Can’t answer that I’m afraid. My current provider fully supports IPv6 (and assigns a /48 😁 ), as did their predecessor, so my network has been dual-stack for years.

I can totally believe it. Here in the Netherlands we still have providers that haven’t implemented IPv6. We’ve had one (Delta) finally starting their IPv6 rollout to fiber customers this year, not sure if they already finished it. Some providers are just slow AF unfortunately.

Not just that, but ever since F32 every single fricking update managed to either break something completely or made some part of the OS too unstable for daily use. Bluetooth issues, crashing display server, system hanging on suspend, broken bootloader on some Secure Boot sysems (handover from EUFI to bootloader no longer happening) therefore rendering the system completely unable to boot… Just some issues I ran into when using Fedora as my daily driver for well over a year.

Fedora is great when it works, but always keep in mind that having a bleeding edge system comes at the cost of stability.