@ 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
.
I removed all but Desktop Icons, Ubuntu AppIndicators and Ubuntu Dock, rebooted and then reproduced the issue. Luckily I’ve found one way to reproduce this, albeit somewhat convoluted and still a bit unreliable, involving Synaptic and window tiling. And as it doesn’t seem to trigger the issue when using another account, I’m now working through settings differences between the two in hopes of finding something crucial.
While doing so, I did discover that dconf-editor is similarly affected:
touko 12 16:09:32 saegusa gnome-shell[8208]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client.
touko 12 16:09:32 saegusa gnome-shell[8208]: WL: error in client communication (pid 12364)
touko 12 16:09:32 saegusa dconf-editor[12364]: Error reading events from display: Katkennut putki
touko 12 16:09:32 saegusa boinc[2098]: No protocol specified
touko 12 16:09:32 saegusa boinc[2098]: No protocol specified
touko 12 16:09:33 saegusa boinc[2098]: No protocol specified
touko 12 16:09:33 saegusa boinc[2098]: No protocol specified
touko 12 16:09:34 saegusa gnome-shell[8208]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client.
touko 12 16:09:34 saegusa boinc[2098]: No protocol specified
touko 12 16:09:34 saegusa boinc[2098]: No protocol specified
touko 12 16:09:34 saegusa gnome-shell[8208]: WL: error in client communication (pid 12796)
touko 12 16:09:34 saegusa gnome-terminal-[12796]: Error reading events from display: Katkennut putki
touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service: Failed with result 'exit-code'.
touko 12 16:09:34 saegusa systemd[3569]: vte-spawn-da1941e8-60e5-48e5-868b-7348dd1158c7.scope: Succeeded.
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null
touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null
Looks like dconf-editor did not exit with FAILURE, but the dconf-editor window did disappear just as Gnome terminal’s did.
Happened again:
May 11 17:05:50 saegusa gnome-shell[3619]: WL: compositor bug: The compositor tried to use an object from one client in a ’wl_pointer.enter’ for a different client.
May 11 17:05:50 saegusa gnome-shell[3619]: WL: error in client communication (pid 5170)
May 11 17:05:50 saegusa gnome-terminal-[5170]: Error reading events from display: Katkennut putki
May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: Failed with result ’exit-code’.
May 11 17:05:50 saegusa systemd[3544]: vte-spawn-b269c64d-5376-49ec-83fc-9f4806ac4b30.scope: Succeeded.
May 11 17:05:50 saegusa systemd[3544]: vte-spawn-3294a176-7b32-4995-a11b-fe0fea8b07bc.scope: Succeeded.
May 11 17:05:50 saegusa systemd[3544]: vte-spawn-0b59afd0-1aed-4081-a7d1-801e7c405399.scope: Succeeded.
May 11 17:05:51 saegusa systemd[3544]: Started Application launched by gnome-shell.
But there’s still nothing in /var/crash, nor on the Error Tracker (aside from the aforementioned, unrelated crash from last week).