You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to change the settings via gsettings or creating local.d settings (/etc/dconf/db/local.d/) files nothing happens or paths are non existent.
gsettings get com.github.amezin.ddterm bold-color
No such schema “com.github.amezin.ddterm”
If I look in dconf it states: No schema available. A schema is what describes the use of a key, and Dconf Editor can't find one associated with this key. If the application that was using this key has been uninstalled, or if this key is obsolete, you may want to erase it.
I believe this the problem why gsettings cannot set the values.
GNOME Shell extensions have schemas file(s) inside the extension installation directory, in schemas subdirectory.
There is gsettings --schemadir ... option and GSETTINGS_SCHEMA_DIR environment variable exactly for this case.
For system-wide installation (i. e. as a distro-specific package, or sudo make install) it's possible to install the schemas file into the default system-wide schemas directory (usually /usr/share/glib-2.0/schemas), but currently it's not performed.
After migration to meson build system #648 schemas will be installed into /usr/share/glib-2.0/schemas for system-wide installation.
GNOME Shell version
44.6 and 40.10
Session type
Wayland (
echo $WAYLAND_DISPLAY
output is non-empty)Special configuration
ddterm version
47 and 32
Linux distro
Fedora 39 and Red Hat 9.2
ddterm settings dump
Description
When I try to change the settings via gsettings or creating local.d settings (
/etc/dconf/db/local.d/
) files nothing happens or paths are non existent.If I look in dconf it states:
No schema available. A schema is what describes the use of a key, and Dconf Editor can't find one associated with this key. If the application that was using this key has been uninstalled, or if this key is obsolete, you may want to erase it.
I believe this the problem why gsettings cannot set the values.
However, this works:
The text was updated successfully, but these errors were encountered: