summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorworldofpeace <worldofpeace@users.noreply.github.com>2019-04-25 09:40:32 -0400
committerworldofpeace <worldofpeace@users.noreply.github.com>2019-04-25 09:40:32 -0400
commitb2dc8c0fa3dcb4d84013ef2fc2932ed92bcb9267 (patch)
tree4cdf147e82605f48301b554070e174751b2889c2 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentb26153450c744bf901fd2fe2e07ac24e5aff0ef4 (diff)
gnome3.mutter328: backport changes from 3.32
gsettings-desktop-schemas made the following change in 3.32[0] > Change tablets'/touchscreens' "display" setting to "output" one > with different semantics. That coincides with GNOME/mutter#133[1] This caused a segmentation fault in gala on Fedora[2] > Settings schema 'org.gnome.desktop.peripherals.touchscreen' > does not contain a key named 'display' I haven't experienced said segfault here in NixOS but I don't see a reason not to use the solution reached there, which was to backport relevant change[1] to mutter 3.28. [0]: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c6edbc1a5b121fa3327d83049325becb [1]: https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1700337
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions