Arkisto, toukokuu 2020

Turns out the online service was just a little slow to update

11. toukokuuta 2020 klo 15.23
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Gnome, Nautilus

Turns out the online service was just a little slow to update, and there are in fact reports sent. But the only one post-20.04-upgrade is [1] from last week, which is a gnome-shell crash and IIRC, unrelated to the terminal issue here. It seemed to be triggered by something related to media files and Nautilus, and the logs from the time are different; I’m attaching them here. (I had separated gnome-shell logs out from the main syslog, but I’ve since reverted back to having everything in syslog.)

* [1] https://errors.ubuntu.com/oops/26828e26-8fc9-11ea-acd0-fa163e983629

Vastaa viestiin sen kontekstissa (Launchpad)

Found no crash files either locally or online, so I’ve implemented the workaround now

11. toukokuuta 2020 klo 14.57
Sijainti: Vianhallintajärjestelmät: Launchpad

Thanks for the instructions, Daniel! I found no crash files either locally or online, so I’ve implemented the workaround now, and will try to trigger the crash again.

Vastaa viestiin sen kontekstissa (Launchpad)

This is probably Ubuntu bug #1875558

8. toukokuuta 2020 klo 15.55
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Ubuntu

For future reference, this was probably Ubuntu bug #1875558 (”libproxy1-plugin-gsettings triggers a lot of warnings”).

Vastaa viestiin sen kontekstissa (Github)

WL: compositor bug: The compositor tried to use an object from one client in a ’wl_pointer.enter’ for a different client (resulting in Gnome terminal crashing)

8. toukokuuta 2020 klo 15.31
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Gnome, Wayland

Since upgrading to 20.04 and switching to Wayland, Gnome terminal occasionally crashes. I interpret the corresponding logs to mean that it’s actually Wayland that fails to do something in the background, which then takes down Gnome terminal:

touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client.
touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client communication (pid 11639)
touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events from display: Katkennut putki
touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded.
touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded.
touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Failed with result 'exit-code'.

I have yet to nail down the precise circumstances, as this has (so far) been somewhat rare, having occurred perhaps once or twice a week.

Since the log mentions pointer, I should perhaps mention that I’ve set `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome terminal also exhibits other misbehaviour wrt. to this, occasionally refusing to get focus, or alternatively losing the focus, despite mouse cursor being over the terminal window.

Vastaa viestiin sen kontekstissa (Launchpad)

Constantly logging ”No protocol specified”

1. toukokuuta 2020 klo 17.21
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: BOINC

Boinc-client logs ”No protocol specified” incessantly, twice every second on my setup.

    -- Logs begin at Wed 2020-03-25 14:45:19 EET, end at Fri 2020-05-01 17:14:34 EEST. --
    touko 01 00:00:00 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:00 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:01 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:01 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:02 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:02 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:03 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:03 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:04 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:04 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:05 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:05 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:06 saegusa boinc[2083]: No protocol specified

…and on and on…

    touko 01 17:14:54 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:55 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:55 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:56 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:56 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:57 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:57 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:58 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:58 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:59 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:59 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:00 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:00 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:01 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:01 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:02 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:02 saegusa boinc[2083]: No protocol specified

Vastaa viestiin sen kontekstissa (Launchpad)

« Uudempia