summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorcolin <colin@uninsane.org>2022-10-14 06:38:35 -0700
committerJan Tojnar <jtojnar@gmail.com>2022-10-25 17:26:07 +0200
commit22834c42cc688b4e52a96d17b0d2a71698125239 (patch)
tree705f5d63ca2678d7cd9b0ced15bf366f5c1ad61a /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent1ce20e8b30c6053044e5019c4f141df8bcdceaad (diff)
gnome.nautilus: use the gtk4 FileChooser settings schema (fixes crash-on-start)
upstream PR for more context: <https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/1013> with the recent nixpkgs bump from GNOME 42 -> 43, we build nautilus with gtk4 (as upstream expects). if the user has nothing else in their environment providing gtk3, then nautilus fails to locate a gtk3 gsettings schema it depends on. i.e. ```console $ nautilus (org.gnome.Nautilus): GLib-GIO-ERROR **: Settings schema 'org.gtk.Settings.FileChooser' is not installed ``` we could solve this on our end by adding gtk3 to `gappsWrapperArgs`, but this seems like an upstream bug: i believe they mean to use the gtk4 settings schemas instead of the legacy gtk3 ones.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions