Enabling the embedded terminal plugin crashes GEdit and subsequently prevents GEdit to start b/c of missing key in GSettings schema

[Naël]

Using gedit and gedit-plugin-terminal 3.35.90-1 on an up-to-date Ubuntu 20.04 Focal Fossa, enabling the embedded terminal plugin in the application's preferences crashes the program with the following error on the standard output:

GLib-GIO-ERROR **: 18:56:20.046: Settings schema 'org.gnome.Terminal.Legacy.Profile' does not contain a key named 'allow-bold'
Trace/breakpoint trap (core dumped)

Subsequently trying to restart GEdit results in more instances of this error, until one removes 'terminal' from the list of plugins in the key 'active-plugins' of the schema 'org.gnome.gedit.plugins':

# Get list of plugins
$ gsettings get org.gnome.gedit.plugins active-plugins
# Set key to same list minus terminal
$ gsettings set org.gnome.gedit.plugins active-plugins "[...]"

The schema 'org.gnome.Terminal.Legacy.Profile' appears to be defined in /usr/share/glib-2.0/schemas/org.gnome.Terminal.gschema.xml, and it indeed does not contain a key named 'allow-bold'. That file belongs to gnome-terminal according to dpkg -S, which is why I'm going to file that bug against gnome-terminal too, just in case they can help. The key 'allow-bold' was apparently removed from that file in the most recent commit (2020-02-19) in the gnome-terminal repository, see following URL and look for 'allow-bold':

https://git.launchpad.net/ubuntu/+source/gnome-terminal/commit/?id=b4205722698333c0f0aff4af6b69186d6ed2516d

That change was published on 2020-02-27 in Focal as gnome-terminal 3.35.91-0ubuntu1, and I first encountered this problem when I tried to open GEdit on the following day (I had the embedded terminal as an active plugin).

Should I report to upstream GEdit, i.e. GNOME if I understand correctly? I don't know where they track their bugs.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gedit 3.35.90-1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 8 18:42:44 2020
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2019-12-29 (70 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
ProcCmdline: /usr/bin/gedit --gapplication-service
Signal: 5
SourcePackage: gedit
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_value () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_boolean () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libffi.so.7
Title: gedit crashed with signal 5 in g_settings_get_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceTop:
 g_settings_schema_get_value (key=0x5600561a9060 "allow-bold", schema=0x5600561de0a0) at ../../../gio/gsettingsschema.c:982
 g_settings_schema_get_value (schema=0x5600561de0a0, key=0x5600561a9060 "allow-bold") at ../../../gio/gsettingsschema.c:968
 g_settings_schema_key_init (key=key@entry=0x7ffed07f8100, schema=0x5600561de0a0, name=name@entry=0x5600561a9060 "allow-bold") at ../../../gio/gsettingsschema.c:1262
 g_settings_get_value (settings=0x5600561dd830, key=0x5600561a9060 "allow-bold") at ../../../gio/gsettings.c:1218
 g_settings_get_boolean (settings=<optimized out>, key=<optimized out>) at ../../../gio/gsettings.c:2142

[Naël (nathanael-naeri)]

There isn't any private information in the bug's attachments.

[Sebastien Bacher (seb128)]

The gedit-plugins source needs to be updated for the g-t change, could you report a bug upstream on https://gitlab.gnome.org/GNOME/gedit-plugins/issues ?

[Naël (nathanael-naeri)]

Done, and I've added a link to the upstream bug.

I'm going to remove the bug's attachments, as they are not useful, and make the bug public.

[Sebastien Bacher (seb128)]

Thanks

[Naël (nathanael-naeri)]

Merge request submitted by an upstream developer

[Reinhard (reinhard-fink)]

Work around to start gedit again, if broken from missing schema key:

install dconf (ow-level configuration system):
>> sudo apt update
>> sudo apt install dconf

start dconf:
>> dconf

Navigate to key:
org.gnome.gedit.plugins.active-plugins

and activate the default values:
['filebrowser', 'spell', 'modelines', 'time', 'docinfo']

or eliminate terminal in your actual values:

=> gedit will start again.

PS:
I miss old style config files :-(

[Naël (nathanael-naeri)]

A fix has been committed upstream and is now part of the new release for gedit-plugins, 3.36.1. How does it work for it to enter Ubuntu, does it need to enter Debian first?

(@Reinhard you can also edit keys using the command-line gsettings tool, e.g. "gsettings reset org.gnome.gedit.plugins active-plugins")

[Fabio Duran Verdugo (fabioduran)]

The fix has been sent at gnome repository, but I still get the issues in Ubuntu.

You can comment the line 147 at file /usr/lib/x86_64-linux-gnu/gedit/plugins/terminal.py and work again, meanwhile we'll wait the next update for gedit-plugins in Ubuntu.

[Naël (nathanael-naeri)]

The bug is fixed in gedit-plugins 3.36.1, and therefore in Ubuntu 20.04 Focal Fossa which has 3.36.2 at the moment. Previous releases are not affected by this bug.