| 23 Aug 2025 |
 jasi 🏳️⚧️ | paging thoughts: I think file roller should be removed from the default install selection since it's not part of GNOME core apps/suite, it's also not seen any new releases outside of bugfix ones and conflicts with Files built-in de-archiving mechanism | 19:53:43 |
| jasi 🏳️⚧️ | Looking at what GNOME OS ships as a frame of reference https://gitlab.gnome.org/GNOME/gnome-build-meta | 19:54:55 |
| jasi 🏳️⚧️ | File roller doesn't have drag and drop support for example. | 19:56:48 |
| jasi 🏳️⚧️ | Ubuntu ships it though: https://packages.ubuntu.com/plucky/gnome | 19:57:39 |
|  ebeem-sama changed their profile picture. | 19:58:00 |
| jasi 🏳️⚧️ | Which I believe is to the chagrin of GNOME upstream. | 19:59:26 |
 Grimmauld (any/all) | i mean, system76/popos is more hated by gnome folks, but ubuntu is a close second | 20:02:24 |
| jasi 🏳️⚧️ | I don't even understand what the s76 drama was all about even after reading it. | 20:04:41 |
| jasi 🏳️⚧️ | In any case, hate is too strong a word, but I think Nix should aim to be closer to GNOME upstream like Fedora rather than putting our own spin on things like Ubuntu | 20:05:27 |
| jasi 🏳️⚧️ | Which I think we basically are for the most part | 20:09:04 |
| jasi 🏳️⚧️ | Keeping file roller also clobbers the file archiving/unarchiving done by nautilus itself. | 20:10:09 |
| 24 Aug 2025 |
|  @9lore:tchncs.de left the room. | 19:33:44 |
| 25 Aug 2025 |
|  NixOS Moderation Bot banned  @srid:matrix.org (<no reason supplied>). | 08:17:24 |
| 26 Aug 2025 |
|  misha joined the room. | 15:16:58 |
| misha | 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;
};
| 15:18:01 |
| misha | * 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;
};
| 15:18:10 |
| misha | * 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;
};
| 15:18:20 |
| misha | * 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;
};
| 15:18:25 |
| misha | Do more people have that issue? | 15:18:38 |
| misha | * 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;
};
| 15:24:08 |
| misha | * 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;
};
| 15:24:57 |
| misha | I am doing this, because turning the "Screen Keyboard" off while running dconf watch / shows that these settings are changed. | 15:25:44 |
| misha | It also keeps automatically toggling to "on", even when I manually turn if off in settings. | 15:39:21 |
| misha | (This is my set-up: https://git.pub.solar/misha/nixos) | 15:52:19 |
| 27 Aug 2025 |
|  amadaluzia changed their profile picture. | 11:30:50 |
| 28 Aug 2025 |
|  hyperparabolic joined the room. | 20:36:16 |
| hyperparabolic | 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.
| 21:01:33 |
| hyperparabolic changed their profile picture. | 21:27:33 |
| hyperparabolic changed their profile picture. | 21:28:09 |
| hyperparabolic changed their profile picture. | 21:29:34 |
