Can you name or link some models? I’d like to consider my options but haven’t found any yet.

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.

What explanation do people envision, after which they would both understand the mechanism of free will and are convinced it exists? That understanding just seems contradictory to me, so either it doesn’t exist or we can’t define it.

Not sure if this fits your usecase exactly, but LinkSheet can make redirection on android more configurable.

https://apt.izzysoft.de/fdroid/index/apk/fe.linksheet

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.

I think the argument is pretty solid as an alternative to writing PKGBUILDs yourself. Sure it doesn’t hold up for people unfamiliar, but Arch is build on the idea of getting yourself familiar with it.

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.

Seems like they at least could’ve made the page have a no-cache header so you don’t have to wipe the cache & history by hand.

Here’s why

Human rights

Tried going to the post example. For me it completely crashes the app.

Alternatively: Hauk

(No idea how they compare)