Hi all. Quick question: for some reason, the Screen Keyboard keeps popping up, and despite having the config below, the "Screen Keyboard" in settings remains toggled on.

      "org/gnome/desktop/a11y/applications" = {
        screen-keyboard-enabled = false;
      };

  "org/gnome/desktop/interface" = {
    toolkit-accessibility = false;
  };

Hi all. Quick question: for some reason, the Screen Keyboard keeps popping up, and despite having the config below, the "Screen Keyboard" in settings remains toggled on.

      "org/gnome/desktop/a11y/applications" = {
        screen-keyboard-enabled = false;
      };
  "org/gnome/desktop/interface" = {
    toolkit-accessibility = false;
  };

Hi all. Quick question: for some reason, the Screen Keyboard keeps popping up, and despite having the config below, the "Screen Keyboard" in settings remains toggled on.

   "org/gnome/desktop/a11y/applications" = {
        screen-keyboard-enabled = false;
      };
  "org/gnome/desktop/interface" = {
    toolkit-accessibility = false;
  };

Hi all. Quick question: for some reason, the Screen Keyboard keeps popping up, and despite having the config below, the "Screen Keyboard" in settings remains toggled on.

  "org/gnome/desktop/a11y/applications" = {
        screen-keyboard-enabled = false;
      };
  "org/gnome/desktop/interface" = {
    toolkit-accessibility = false;
  };

Hi all. Quick question: for some reason, the Screen Keyboard keeps popping up. Which is understandable because the "Screen Keyboard"

  "org/gnome/desktop/a11y/applications" = {
        screen-keyboard-enabled = false;
      };
  "org/gnome/desktop/interface" = {
    toolkit-accessibility = false;
  };

For some reason the "Screen Keyboard" remains toggled on, even though I explicitly try to turn it off like this:

  "org/gnome/desktop/a11y/applications" = {
        screen-keyboard-enabled = false;
      };
  "org/gnome/desktop/interface" = {
    toolkit-accessibility = false;
  };

I saw that the glycin packages were being split into libglycin and glycin-loaders (thank you very much whoever worked on that!), and I'm trying to adopt libglycin from nixpkgs unstable instead of my terrible hack at packaging it. The glycin-loaders package has several patches, one of which hard coded the path for bwrap. I'm not seeing the same in the libglycin, and seeing the expected failure in turn (env -i "bwrap" ... returns a "env: ‘bwrap’: No such file or directory" error because -i unsets the path variables that allows env to discover bwrap).

Is there some idiomatic way to work around this in nixos without the old patch being applied?

Happy to help out with this however I can as well if there's still some pending work on it. I wanted to try to upstream my libglycin packaging eventually, but it... needed work first, heh. I was still very new to nix packaging when I started it.