[No schema found]

[dimitrioschatzinikolis]

Hi,

I was able to run all the steps described, I am able to change the settings via the command line, and I confirm the changes via dconf-editor, but I am still not able to open in the terminal of my choice (tested with alacritty and wezterm). One thing that I noticed it's different, is that in the dconf-editor, question marks show up and also "No schema found" errors. (screenshot below)

My OS is Ubuntu 22.04.1

Any ideas how to tackle this?

Thanks, d.

[Abhinav1217]

Similar thing with me.

I used pip to install the extension, and use the gsettings commands from the readme. For the last command I got

abhinav@abhinav-sol ~ $ gsettings set com.github.stunkymonkey.nautilus-open-any-terminal flatpak system
No such key “flatpak”

But now my nautilus has been broken, When I run from terminal, I get following error

abhinav@abhinav-sol ~ $ nautilus

(org.gnome.Nautilus:25712): GLib-GIO-ERROR **: 16:32:39.178: Settings schema 'com.github.stunkymonkey.nautilus-open-any-terminal' does not contain a key named 'flatpak'
Trace/breakpoint trap (core dumped)

Since nautilus isn't starting because of this, I need urgent help.

[Stunkymonkey]

please update to version 0.4.0 and make sure the schema is compiled via glib-compile-schemas /usr/share/glib-2.0/schemas or glib-compile-schemas ~/.local/share/glib-2.0/schemas/

[Abhinav1217]

I was on 0.4.0.

I updated the system to gnome shell 43 today, then when I realized I lost the "open with alacritty" option in context menu, I installed using pip install --user nautilus-open-any-terminal and restarted nautilus using nautilus -q . I made sure version installed was same as on your github release page.

When I lost nautilus (error message as mentioned), I used the uninstall instructions on your readme to get it back.

[dimitrioschatzinikolis]

please update to version 0.4.0 and make sure the schema is compiled via glib-compile-schemas /usr/share/glib-2.0/schemas or glib-compile-schemas ~/.local/share/glib-2.0/schemas/

Thanks for the answer. So I am on 0.4.0. I installed it from this repository with the system-wide command. I compiled the schemas, as per your suggestion -> this results that 2 new files are showing in my usr/share/glib-2.0/schemas folder, namely the gschemas.compiled and the com.github.stunkymonkey.nautilus-open-any-terminal.gschema.xml.

I expected after this, that if I open the dconf editor, and navigate to com/github/stunkymonkey/nautilus-open-any-terminal folder, the keys would show up, but there exists no such folder. I tried to set it up via the command-line, as you indicate in your instructions. The keys are created, and I can see them via dconf editor, but the "No schema found" error remains. (as shown in the image I attached above).

Any hints?

Thanks in advance.

[Stunkymonkey]

I tried to set it up via the command-line, as you indicate in your instructions. The keys are created, and I can see them via dconf editor, but the "No schema found" error remains. (as shown in the image I attached above).

This is super hard to debug and very system dependend. On arch-linux I did some testing half a year ago, but since then the code stayed the same.

[Abhinav1217]

I did some testing half a year ago, but since then the code stayed the same.

I only got this issue when system was upgraded with gnome 43. It was working fine until gnome 42, and 41.

[Stunkymonkey]

i suspect this is a dconf problem I am still on gnome 41 and will switch on end of november to 43. Lets see then

[betoma]

I'm on Gnome 42 and I was having a similar issue -- even after running the commands in the README to install, I was getting the "no schema found" error. For me, the schema wasn't showing up in dconf-editor either. I found that, despite installing everything as instructed, the schema xml file never got copied to /usr/share/glib-2.0/schemas. Once I manually copied that file to that folder using the command line, I was able to re-compile schemas and everything worked as intended.

[dmytrodubinin]

In Gnome 43, Fedora 37 the same issue

[victante]

For me the problem seemed to solve itself once I removed flatpak dconf-editor and used the native one (Fedora 37 with Gnome 43). After everything was installed, native dconf-editor was able the find the schemas. Maybe it has something to do with flatpak's limited filesystem access?

[dmytrodubinin]

For me the problem seemed to solve itself once I removed flatpak dconf-editor and used the native one (Fedora 37 with Gnome 43). After everything was installed, native dconf-editor was able the find the schemas. Maybe it has something to do with flatpak's limited filesystem access?

I have native Fedora rpm package, but problem is here

[Abhinav1217]

For me the problem seemed to solve itself once I removed flatpak dconf-editor and used the native one (Fedora 37 with Gnome 43). After everything was installed, native dconf-editor was able the find the schemas. Maybe it has something to do with flatpak's limited filesystem access?

I am not using flatpak, I am using pip.

[Abhinav1217]

I am still on gnome 41 and will switch on end of november to 43. Lets see then

Have you switched to G43?

[Soupy710]

I'm facing the same issue as well. Nautilus does not open and the logs say that the "flatpak" key doesn't exist. This issue is there from the day I upgraded to gnome 43. Facing this on arch-linux.

[Stunkymonkey]

I can confirm that on NixOS with gnome 43 it does not work as well.

[greatquux]

After a whole crapload of troubleshooting (20 minutes but it felt like an hour lol) I discovered that my system-wide install via pip3 had installed an old version of the schema in /usr/local/share/glib-2.0/schemas, and that was taking precedence over the new system-installed version from this repository. I have no idea why it was old or didn't include the flatpak key? But by doing the pip3 uninstall, dconf-editor then started the show the proper entries from this repository's system-wide install.

[Stunkymonkey]

so is this still an issue?

on NixOS it is a different issue (it can be tracked at: https://github.com/NixOS/nixpkgs/issues/33277)

[Stunkymonkey]

I am closing this due to inactivity. This is almost certainly an system-configuration problem an not a problem with the package itself.