@elvetemedve It’s cool, V14 is working just fine so I’ll just postpone updating the extension until sometime in the future. Thanks!
Release 16 doesn’t work in Gnome Shell 3.28 (Ubuntu 18.04): GObject.registerClass() used with invalid base class (is PanelMenuButton)
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.
Tested this again and it seems to have been fixed at some point by some Ubuntu (18.04) updates: my test user still had version 8 of the extension, and I could no longer reproduce the issue, neither before nor after updating the extension to release v9. My main user’s desktop now also appears unaffected.
(I was going to try the workaround reported by @ChrisLancs, but ended up not having to. My ”List type” is set to ”Disabled”.)
A new log; still nothing useful from colord AFAICT, despite the –verbose.
…except that –debug isn’t one of gsd-color’s recognized parameters, and adding it caused GDM to fail to start. I changed it to –verbose which is available.
10.08 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color –help-all
gsd-color [OPTION?] color
-h, –help Show help options
–help-all Show all help options
–help-gtk Show GTK+ Options
–class=CLASS Program class as used by the window manager
–name=NAME Program name as used by the window manager
–gdk-debug=FLAGS GDK debugging flags to set
–gdk-no-debug=FLAGS GDK debugging flags to unset
–gtk-module=MODULES Load additional GTK+ modules
–g-fatal-warnings Make all warnings fatal
–gtk-debug=FLAGS GTK+ debugging flags to set
–gtk-no-debug=FLAGS GTK+ debugging flags to unset
–exit-time Exit after n seconds time
–dummy-name Name when using the dummy daemon
-v, –verbose Verbose
–display=DISPLAY X display to use
There’s also –gtk-debug and –gdk-debug, but I could do with a little help for what to select for those, as just giving ’all’ seems a little counterproductive (for instance, ”touchscreen” and ”interactive” don’t seem very useful here).
10.03 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color –gtk-debug help
Supported debug values: misc plugsocket text tree updates keybindings multihead modules geometry icontheme printing builder size-request no-css-cache baselines pixel-cache no-pixel-cache interactive touchscreen actions resize layout all help
10.04 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color –gdk-debug help
Supported debug values: events misc dnd xim nograbs input cursor multihead xinerama draw eventloop frames settings opengl all help
Error parsing option –gdk-debug
(Looks like –gdk-debug reports an error with ’help’, despite having just listed it as one of the options.)
Sure, I’ve now set it up thus and will post the results once I hit this again (it seems pretty unpredictable, so could be anything from days to weeks).
Here you go. Had this occur twice in a row just now, so my original theory of the second login never failing was false.
Okay, did it! https://gitlab.gnome.org/GNOME/gnome-terminal/issues/30
Some years back (2013/2014 maybe?) the ’New Window’ and ’New Tab’ menu items were combined into a single ’New Terminal’ item.
This apparently met with resistance from users, so Fedora and recently also Ubuntu have chosen to build Gnome terminal with
DISUNIFY_NEW_TERMINAL_SECTION to restore the old behavior.
This unfortunately leaves users of those distros, like myself, who actually prefer the simplicity of ’New Terminal’, with no practical way to restore that functionality (beyond rebuilding the package with the compile-time switch reverted).
After hearing me out, the Ubuntu maintainer suggested I file a bug here, asking to turn the compile-time option into a Gsetting so that the behavior could be more easily adjusted per user preferences.
So that is what I’m asking here.