And “nothing” does not fit, either.

I have been sort of following Wayland’s development for over 10 years now. I have been using Wayland for over 2 years now. I have been reading and watching various lengthy arguments online for and against it. I still don’t feel like I actually know it even is, not beyond some handwavey superficialities. Definitely not to the extent and depth I could understand what X11 was and how to actually work with it, troubleshoot it when necessary and achieve something slightly unusual with it. I feel like, these days, you are either getting superficial marketing materials, ELI5 approaches that seem to be suited at best to pacify a nosy child without giving them anything to actually work with, or reference manuals full of unexplained jargon for people who already know how it works and just need to look up some details now and then…

Maybe I’m getting old. I used to like Linux because I could actually understand what was going on…

The KDE team has already determined that this is not a bug and that both you and me must just be imagining it:

https://bugs.kde.org/show_bug.cgi?id=481058

Legalisiert soll das ganze bis zur 12. Schwangerschaftswoche werden, und dann soll immer noch eine Beratung verpflichtend sein.

Frage: Wie lange dauert es im Normalfall, bis eine Frau überhaupt merkt, dass sie schwanger ist? Wie lange dauert es in ungewöhnlichen oder extremen Fällen? Wie lange muss man auf so einen Beratungstermin warten? Wie lange anschließend auf einen Termin für die Durchführung der Prozedur?

Okay, who is “they”?

Context?

It’s a lot better than the system that just randomly throws in your USB drives with your SCSI/SAS/SATA/PATA drives. Or the systems that calls everything a SCSI drive when it usually isn’t a SCSI drive.

Smartctl works on nvme drives. Use it.

btop for bling

htop for practical utility

top for minimalism, availability, reliability

I recognize Kirby, and that’s about it.

Yes, support for sessions in Plasma.

groundzero

Several years ago now. On at least two of those tries, after maybe a month or some of daily driving, suddenly the fs goes totally unresponsive and because it’s the entire system, could only reboot. FS is corrupted and won’t recover. There is no fsck. There is no recovery. Total data loss.

Could you narrow it down to just how long ago? BTRFS took a very long time to stabilise, so that could possibly make a difference here. Also, do you remember if you were using any special features, especially RAID, and if RAID, which level?

Out of interest, since I’ve not used the “recommended partion setup” for any install for a while now, is ext4 still the default on most distros?

I recently installed Nobara Linux on an additional drive, because after 20 years, I wanted to give Linux gaming another shot (works a lot better than I had hopes for, btw), and it defaulted to btrfs. I’ll assume so does Fedora, because I cannot imagine Nobara changed that part over the Fedora base for gaming purposes.

Well passwordless.

Same thing in this context. But sure, an encrypted partition would work.

Dunno about ideal, but it should work.

It does have quite a bit of overhead, meaning it’s not the fastest out there, but as long as it’s fast enough to serve the media you need, that shouldn’t matter.

Also, you need to either mount it manually on the command line whenever you need it or be comfortable with leaving your SSH private key in your media server unencrypted. Since you are already concerned with needing to encrypt file share access even in the local network, the latter might not be a good option to you.

The good part about it is, as long as you can ssh from your media server to your NAS, this should just work with no additional setup needed.

Interesting. Though it does seem to to require your private key to be unencrypted…

Is sshfs an option? Unfortunately, I don’t think you can put that into /etc/fstab, though…

Hey, that actually did it! Not cookies, technically, but “local storage”, but anyway…

Thanks for the hint!

*edit: In retrospect, I should have saved what Photon had saved there in local storage. This was definitely still a bug, Photon, like any other web application, really, must be able to deal with data stored by older versions of itself, even if those older versions were buggy.

Anyway, I disabled all of those in Firefox’ Add-On page (so not just via their own disable buttons), reloaded the page and… no difference. Still just a blank page.