It requires hard-coded compiled schema to be in extension UUID folder, else it fails.
This is a rare scenario, since extension shouldn't have hard-coded schema location by itself. It should respect Gnome extension standards of schema location.
If there is any other extension which produces error like this:
GLib.FileError: Failed to open file “/usr/share/gnome-shell/extensions/flypie@schneegans.github.com/schemas/gschemas.compiled”: open() failed: No such file or directory
Than it's very easy to add it to this workaround list.
It requires hard-coded compiled schema to be in extension UUID folder, else it fails.
This is a rare scenario, since extension shouldn't have hard-coded schema location by itself. It should respect Gnome extension standards of schema location.
If there is any other extension which produces error like this:
GLib.FileError: Failed to open file “/usr/share/gnome-shell/extensions/flypie@schneegans.github.com/schemas/gschemas.compiled”: open() failed: No such file or directory
Than it's very easy to add it to this workaround list.