Kiitos neropatille, joka kippasi koko hiekkakuormansa aiemmin raportoimani möykkyisen tienalituksen eteen niin, että nyt siellä on niiden möykkyjen lisäksi kuvan mukainen pottupelto. Tälle kesähessulle saa minun puolestani antaa suoraan potkut heti sen jälkeen, kun on jälkensä korjannut.


Minä, omasta puolestani, toivotan tervetulleeksi uudet robottivaltiaamme.
@ 8:55 4 terabytes of footage?! Wow, that is… underwhelming. I have storage many times over that just for my home use, and I assume they’re filming in raw super hi-res and keeping multiple takes to maximize editing freedom. I suppose it could be an accurate figure (I don’t see why he would lie to make it seem smaller rather than larger), but it’s like saying ”we had a photoshoot for a magazine and filled an entire memory card!” I mean, that’s the minimum that I’d expect from a professional-level shoot.
Youtube appropriately auto-captions Jessica’s speech simply as ”music” 😁
My guess is this is due to bug #1785354: ”/etc/fstab: fs_passno is 0 for all file systems”. So yes, you should probably correct it.
Alikulun hiekkapohja on aika möykkyisessä kunnossa. Alikulku on myös aika pimeä, ja viereiseltä isolta mäeltä alas ajaessa nämä möykky-yllätykset voivat olla vaarallisiakin.
After doing manual dconf cleanup, I’ve been unable to reproduce the issue. That’s since posting the previous comment, so a few days now. So I think I’ll hold off on reporting this upstream for the time being, but I’ll go ahead and do that if the problem still manifests itself.
Thanks again, Daniel.
I think a warning is warranted: you may be tempted to do a dconf reset -f /, but besides clearing out schema-less keys, reset resets all affected values to their defaults. In any case, I recommend backing up your existing configuration (with dconf dump / >my-dconf.dump) before issuing a dconf reset.