GLib-GIO:Settings schema 'org.gnome.Geary' does not contain a key named 'single-key-shortcuts'

Bug #1876771 reported by hkdb
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
geary (Ubuntu)
Expired
Low
Unassigned

Bug Description

If users have been using Geary (installed from .deb) in previous Ubuntu releases, after upgrading to 20.04 LTS, Geary doesn't launch.

Attempting to launch it from terminal, the below message shows:

GLib-GIO:Settings schema 'org.gnome.Geary' does not contain a key named 'single-key-shortcuts'
Trace/breakpoint trap (core dumped)

This is due to the new /usr/share/glib-2.0/schemas/org.gnome.Geary.gschema.xml not being compiled and placed into /usr/local/share/glib-2.0/schemas/. The new changes were introduced in Geary 3.35.2. In order for the new changes to apply and be made available for Geary, a working post-install hook must be included with the .deb. Upstream uses this post-install hook for Flatpak:

https://gitlab.gnome.org/GNOME/geary/-/blob/mainline/build-aux/post_install.py

Perhaps we can use the above and add an extra step of moving the compiled file to /usr/local/share/glib-2.0/schemas/ is needed for our situation as the compiled output goes to /usr/share/glib-2.0/schemas/ but Geary reads from /usr/local/share/glib-2.0/schemas/?

I have done a quick write-up about how to manually fix the problem as an interim solution:

https://link.medium.com/4I8KKvqLb6

For my specific situation, this happened after upgrading to 20.04 [amd64] with this package from 19.10 [amd64] running Geary 3.34.2-eoan-1 from https://launchpad.net/~hkdb/+archive/ubuntu/geary.

1. Description: Ubuntu 20.04 LTS
   Release: 20.04
2. geary:
     Installed: 3.36.1-1
     Candidate: 3.36.1-1
     Version table:
    *** 3.36.1-1 500
        500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
        100 /var/lib/dpkg/status
3. Geary would launch normally
4. Geary crashes on launch

Thanks!

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The /usr/local isn't used by Ubuntu, if there is content here it's a local installation and such the responsability of the local administrator who decided to override the Ubuntu version. Try cleaning or moving away /usr/local and see if it resolves your issue

Changed in geary (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for geary (Ubuntu) because there has been no activity for 60 days.]

Changed in geary (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.