Avainsanana Gnome

3.36.4-1ubuntu1~20.04.1 from -proposed fixed the issue

28. heinäkuuta 2020 klo 16.42
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Gnome

I can confirm that 3.36.4-1ubuntu1~20.04.1 from -proposed fixed the issue (in Boxes) for me, i.e. the dialog text is now wrapped and hence entirely legible.

Vastaa viestiin sen kontekstissa (Launchpad)

I think a warning is warranted

13. toukokuuta 2020 klo 15.23
Sijainti: Muut: Ask Ubuntu
Avainsanat: Gnome, turvallisuus

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.

Vastaa viestiin sen kontekstissa (Ask Ubuntu)

I removed all but the Ubuntu extensions, rebooted and then reproduced the issue

12. toukokuuta 2020 klo 16.27
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Gnome, Synaptic, Ubuntu

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.

Vastaa viestiin sen kontekstissa (Launchpad)

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)

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)

Keyboard shortcut restoring shortcut cut short when localized

10. huhtikuuta 2020 klo 15.38
Sijainti: Vianhallintajärjestelmät: Gnome GitLab
Avainsanat: Gnome, Launchpad, Ubuntu

Affected version

I’m using Ubuntu 20.04 and Wayland, with gnome-shell currently at version 3.36.1-4ubuntu1. (I originally filed this on Launchpad.)

Bug summary

When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English it says:

Boxes wants to inhibit shortcuts

You can restore shortcuts by pressing Super+Escape.

In my locale (Finnish), it says

Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

Voit palauttaa pikanäppäinten toiminnan painamalla Super...

(sic; see attached photo)

So the actual key combination is truncated, defeating the point of that part of the text.

This isn’t a localization error (AFAICT, based on the translation source). Rather, it’s caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed.

Screenshot

20200409_180221

Vastaa viestiin sen kontekstissa (Gnome GitLab)

Keyboard shortcut restoring shortcut cut short when localized

9. huhtikuuta 2020 klo 18.36
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Gnome

When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English (I think, based on [1]) it says:

Boxes wants to inhibit shortcuts

You can restore shortcuts by pressing Super+Escape.

In my locale (Finnish), it says

Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa.

Voit palauttaa pikanäppäinten toiminnan painamalla Super…

(sic; see attached photo)

So the actual key combination is truncated, defeating the point of that part of the text.

This isn’t a localization error (AFAICT; see [2]). It’s caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed.

(I’m reporting this against gnome-shell as opposed gnome-boxes based on [3]. Feel free to reassign as necessary.)

* [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28
* [2] https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10&show=all&search=pikan%C3%A4pp%C3%A4inten
* [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036

Vastaa viestiin sen kontekstissa (Launchpad)

Popup menu jumps to top left window corner when focus follows mouse (in Wayland)

6. huhtikuuta 2020 klo 16.06
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Gnome

I’m using 20.04 and a Wayland session. My preferred focus mode is to have it follow the mouse cursor:

$ gsettings get org.gnome.desktop.wm.preferences focus-mode
’mouse’

Unfortunately this causes GTK apps’ popup (RMB) menu to jump to the app window corner when opened. I’m attaching a screencast, where I demonstrate the bug first, then reset focus-mode to ’click’ to demonstrate the bug no longer manifesting. (Please excuse the flashing. It’s just a video artefact caused by Gnome’s built in screen recorder, which was the only one that at least somewhat worked.)

This has been reported upstream, where a fix was recently merged: https://gitlab.gnome.org/GNOME/mutter/issues/1103

Vastaa viestiin sen kontekstissa (Launchpad)

It’s cool, V14 is working just

6. toukokuuta 2019 klo 14.59
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Gnome, Javascript

@elvetemedve It’s cool, V14 is working just fine so I’ll just postpone updating the extension until sometime in the future. Thanks!

Vastaa viestiin sen kontekstissa (Github)

Release 16 doesn’t work in Gnome Shell 3.28 (Ubuntu 18.04): GObject.registerClass() used with invalid base class (is PanelMenuButton)

4. toukokuuta 2019 klo 21.02
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Gnome, Ubuntu

I’m using Ubuntu 18.04, which has Gnome Shell 3.28 (3.28.3+git20190124-0ubuntu18.04.1).

After I updated the extension to latest release (16), it fails to start. Gnome Shell reports this error:

Extension "System_Monitor@bghome.gmail.com" had error: TypeError: GObject.registerClass() used with invalid base class (is PanelMenuButton)

Downgrading to release 14 makes it work again.

Ubuntu’s appindicator extension has a similar issue from a while back, with pointers to an issue with the extensions website, but I’m unsure if this is related.

In any case, I decided to open this issue to at least document it. Feel free to close it if it’s intentional (Gnome Shell 3.28 no longer supported), or otherwise not a bug with System Monitor.

Vastaa viestiin sen kontekstissa (Github)

Vanhempia »