NixOS GNOME | 402 Members | |
| A room for maintainers of GNOME & GNOME-Related desktop environments (xfce, cinnamon, pantheon...) | 93 Servers |
| Sender | Message | Time |
|---|---|---|
| 6 Dec 2023 | ||
| Also my logs are full of these messages:
| 08:55:30 | |
| * Upgraded to NixOS 23.11 yesterday. Now GNOME Shell crashes sometimes.
| 10:42:20 | |
| 7 Dec 2023 | ||
| 20:41:22 | ||
| 8 Dec 2023 | ||
| This could be caused by an extension. Do you have any? | 08:00:26 | |
I'm developing a GNOME extension that requires libgsound. These typically have to be patched with GIRepository.append_search_path..bla bla in nixpkgs. Can I do anything on my end to make my extension more Nix-friendly? | 08:05:01 | |
| I guess I'm going to wrap GSound imports in a try-catch and gracefully disable the features that require it if it fails to import. Still, that doesn't eliminate the need for a nixpkgs patch. Any other suggestions? | 08:07:41 | |
| 08:09:49 | ||
| No | 08:54:27 | |
| I think what would help though if extensions generally exposed their dependencies in the metadata.json | 08:55:16 | |
| Oh with the new ES Modules system we can do static analysis to detect used dependencies quite easily actually! Plenty of tooling in JS world already does this | 09:27:02 | |
| Oh, that would be very interesting if you could integrate that into our automatic packaging | 09:55:12 | |
| 10:24:34 | ||
In reply to @rpanades:matrix.orgCan someone let me what is going on with 45 and 23.11? Everything Electron seems to be broken and non-Electron apps too | 10:25:49 | |
| I've been having issues and talking for the past week on the Nix/NixOS channel with no real feedback | 10:26:10 | |
| There was nothing about this in the release notes or anywhere else | 10:28:00 | |
In reply to @piegames:matrix.orgI'll take a look | 10:30:35 | |
In reply to @adham-omran:matrix.orgIsn't this a repeat of https://github.com/NixOS/nixpkgs/issues/244742 | 14:56:49 | |
| BTW for large upgrades I'd be careful that (1) you reboot and (2) don't use opengl-using apps from very far away nixpkgs version (than your OS). | 14:57:45 | |
In reply to @piegames:matrix.orgbtw looks like https://github.com/NixOS/nixpkgs/commit/af9e3ddc1da4c96d35b326d20ba09cedb1a5ac3b still is not sufficient | 20:07:55 | |
at this point, I am leaning towards creating wrapper for extension.js that does our typelib manipulation and then uses top-level await of dynamic import to load the actual extension.js file | 20:09:27 | |
In reply to @jtojnar:matrix.orgWhy not? | 20:10:07 | |
I am guessing the GPasteGtk import here sometimes gets resolved before the body of ./__nix-prepend-search-paths.js is evaluate | 20:11:50 | |
| I assumed that imports are resolved sequentially and module’s body is evaluated after all static imports in the module are resolved | 20:13:45 | |
| but it might not be correct | 20:14:03 | |
| there is loader specification draft but it is not clear to me if it matches the implementations: https://github.com/whatwg/loader | 20:17:16 | |
| piegames: I am trying the wrapper approach in https://github.com/NixOS/nixpkgs/pull/272995 | 22:29:18 | |
In reply to @jtojnar:matrix.orgDid you try it already? | 22:32:36 | |
Also how well does this approach generealize, so that we may hook this into buildGnomeExtension | 22:32:51 | |
| yes, it appears to work | 22:33:22 | |
After some reflection, I think that I'd like to package all extensions with buildGnomeExtension, even those not on extensions.gnome.org. This will require some modifications but it should be feasible | 22:33:27 | |