Gnome has defaulted to Wayland for a long time, so it sounded more like you had an issue with a different desktop environment, not X11 vs Wayland

Gnome isn’t orthogonal to Wayland.

You’d need to check if you were using the X11 or Wayland session of Gnome

I would generally just set the RPATH to $ORIGIN in the ELF file

lsof just reads from /proc and gives you formatted output

https://github.com/lsof-org/lsof/blob/master/lib/dialects/linux/dproc.c#L297

You should probably enable debian-security at least…

They’re on 6.12.101

NCurses, Media Player Client, c Plus Plus

Wondering if those AI trainers know every character you put in that file is another token they’re paying for

I’d had a dedicated windows drive for a little while… Maybe a bug and not malice, but the forced Windows 8 -> 10 upgrade deleted everything on my second drive that windows wasn’t installed on

If you’re using rsync and not scp or a USB stick, I’m pretty sure you’re already in the top 50%

I will say the Rust stdlib seems to make TOCTOU bugs really easy to make for filesystem operations

But, yes, Ubuntu switching to a test project hurts it

Ah, if you’re saying it should have been designed based off 5.25" I’m down :)

It’s grossly exaggerated because it was designed when we had UX designers

It has to look okay all the way down to 8x8 pixels

BSDs are also monolithic kernels, just like Linux, macOS, and Windows NT

FreeBSD has been trying to make it easier to run as a desktop OS by supporting the Linux APIs so they can use the WiFi and Graphics drivers from Linux

OpenBSD handles security by supporting fewer features. E.g. they do not support Bluetooth as it’s an insecure protocol, and they disabled SMT due to the hardware bugs in AMD/Intel/ARM - so they are more secure, but slower

They’ll get loaded, even without root

GitHub manages not one, but TWO nines of availability.

Sometimes both nines are even in the front!

deleted by creator

Edit: to be clear, this advice is specific to Ubuntu. If you come across this and need advice for a different distro, message me or reply to this

Yes.

Ubuntu doesn’t follow upstream kernels, so they will have to make a custom backport for 6.17 to fix the kernel

It’s very unlikely you need the module that has the bug, so the mitigation should work for you

Just double check lsmod | grep aead

As long as that module is not loaded, and you have the kmod update that adds /etc/modprobe.d/disable-algif.conf you’re protected

The kmod change makes it so the affected module cannot be loaded, it was their initial workaround

I don’t want to go in the cart!

V8.40 => V8.40 🤔