This is the command I used after unlocking the luks device in a rescue environment and confirming it not mounting further:

sudo btrfs rescue zero-log /dev/mapper/luksroot

After that, I could mount again and boot.

Here's more info on the command, to verify advice is sound: https://manpages.debian.org/testing/btrfs-progs/btrfs-zero-log.8.en.html#zero

EDIT: For me it didn't happen during an update, btw. You might still need the chroot approach to make the system bootable again.

I've had this exact error a couple of weeks ago. You have to clear the replay log (and lose potentially 30 seconds of disk writes). Let's see if I can find exact instructions before the end of my commute.

That'd be fine by me, if I could also actually buy a good TV that supports DP.

On the other hand, I also think it's bullshit that I pay for HDMI through both my GPU & TV, and the HDMI forum still denies me that bought functionality.

Wikipedia is financially pretty stable, afaik. Not saying you shouldn't donate, but you might want to look into what happens with it. It won't necessarily be used to cover costs of running the website.

Haskell

It's been a while since I've watched it myself, but remember them going into the ownership structure.

https://www.youtube.com/watch?v=hNZy603as5w

There's basically no way for them to not make it a subscription model.

Good to mention that (in the Netherlands) when you've provided fingerprints for a new identification card, the fingerprints are wiped from any system after you've received the card, remaining only on the card itself.

Interestingly, as ChatGPT might be trained on these ELI5 questions and as a result they are asked more infrequently, it might get worse over time or out of date on these types of questions by its own doing. I especially wonder how bad this influence will get on subjects that you'd normally search stackoverflow for.

I wonder if internally the emoji's are added through a different mechanism that doesn't pick up the original request. E.g. another LLM thread that has the instruction "Is this apologetic? If it is, answer with exactly one emoji." After this emoji has been forcefully added, the LLM thread that got the original request is trying to reason why the emoji would be there, resulting in more apologies and trolling behaviour.

Explained by someone that doesn't know the technical side super well.

1: It's a new protocol for displaying. The main difference from X11, as I understand it, is a simplification of the stack. Eliminating the need for a display server, or merging the display server and compositor.

2: Some things impossible (or difficult) with X11 are much better supported in Wayland. Their not necessarily available, as the Wayland protocol is quite generic and needs additional protocols for further negotiation. Examples are fractional scaling & multiple displays with differing refresh rates.

Security is also improved. X11 did not make some security considerations (as it is quite old, maybe justifiably so). In X11 it's possible for any application to "look" at the entire display. In Wayland they receive a specific section that they can draw into and use. (This has the side-effect of complicating stuff like redshifting the screen at night, but in my experience that has fully caught up).

3: If you're interested, are in desktop application development (but I have no experience in that regard) or have a specific need for Wayland.

4: I think X won't die for a long long time if "ever". I'm not super familiar with desktop app development, but I don't think it requires more work to keep supporting X.

On the other hand, most of the complaints about Wayland I've heard were ultimately about support. At some point, when you're a normal user, the distro maintainer should be able to decide to move to Wayland without you noticing, apart from the blurriness being gone with fractional scaling.

Here's why

Human rights

If what the first commenter said is true. They will just implement RCS or an alternative in the EU and make up some reason why they can't or won't for the US market.