No idea what krysp is, but audio is flawless in my case. Granted, only really used on x11 so far. I use vesktop flatpak on debian sid.

see my other comment

Give Vesktop a try. It’s a clone of discord and they say they support wayland for streaming just fine. It works fine but I haven’t tried the wayland streaming thing yet.

Ubuntu is a fork of unstable Debian packages

And where do you think debian stable packages come from exactly ?..

it’s basicaly the exact same thing. In both case :

• At some point freeze unstable (snapshot unstable in case of ubuntu),
• fix bugs found in the frozen set of packages,
• release as stable.

Not if root account is disabled. Which is by default on Ubuntu and Debian . You’d need sudo su - but well… No sudo left you know.

I tried to convert Debian to Ubuntu by replacing the Debian repos in apt with Ubuntu’s and following with dist-upgrade

Shouldn’t it work though ? Or be close to work with the appropriate options passed down to dpkg

It doesn’t work with root disabled.

The way to fix this is to boot in bash recovery where you land a root shell. From there you can hopefully apt install sudo if deb file is still in cache. If not, you have to make network function without systemd for apt install to work. Or, you can get sudo deb file and all missing dependencies from usb stick and apt install them from fs. Or just enable root, give it a password and reboot so you can su - and apt install sudo

• apt something that ended up removing sudo. No more admin rights.
• used rsync to backup pretty much everything in / , with remove source option…
• find with -delete option miss positioned. It deleted stuff before finding matching pattern
• chown / chmod on /bin and/or /usr/bin
• Removed everything in /etc

Also I’ve read that C# is C++++ (like put those + on 2x2 table, which in turns ressemble a #)

isn’t that kind of what AUR is, and exactly what people love about arch ?

Snap forces updates, and you cannot disable them. So if you use snaps, I guess you can stop worrying and keep going with your usual apt routine.

if you do not provide a root password during install, the default user is in sudoer.

I put my self hosted instance down on purpose and tried to access my phone’s app. It works and I can export to csv or json from there.

The likelihood of my phone & NAS breaking down at the same time seems rather thin.

wait what ?

So you are saying that the following code will keep throwing e but if I used throw e; it would basically be the same except for the stack trace that would be missing the important root cause ?!

try {
} catch (WhateverException e) {
    // stuff, or nothing, or whatever
    throw; 
}