diff options
author | Mart Raudsepp <leio@gentoo.org> | 2018-12-25 17:42:30 +0200 |
---|---|---|
committer | Mart Raudsepp <leio@gentoo.org> | 2018-12-25 17:50:36 +0200 |
commit | 8403a13490ce4e7f9c8a6c956ac11ee1289bab97 (patch) | |
tree | c0b51055cb18a08273bbc859450ae259c05ffc01 /gnome-base/gnome-settings-daemon/files | |
parent | www-servers/nginx: bump to v1.15.8 mainline (diff) | |
download | gentoo-8403a13490ce4e7f9c8a6c956ac11ee1289bab97.tar.gz gentoo-8403a13490ce4e7f9c8a6c956ac11ee1289bab97.tar.bz2 gentoo-8403a13490ce4e7f9c8a6c956ac11ee1289bab97.zip |
gnome-base/gnome-settings-daemon: fix build with glib-2.58
New glib does typeof() checking on g_clear_pointer macro calls,
which fails with code that passed something unsuitable as
g_clear_pointer destroy parameter. notify_notification_close
takes a second parameter, which is not a valid function signature
for g_clear_pointer, thus it errors now. Add upstream patch to
fix that.
Because in practice the destroy func call worked out fine with
earlier glib, without any known problems, there is no revbump by
considering it only a build fix (which strictly it's not).
Closes: https://bugs.gentoo.org/673706
Signed-off-by: Mart Raudsepp <leio@gentoo.org>
Package-Manager: Portage-2.3.52, Repoman-2.3.11
Diffstat (limited to 'gnome-base/gnome-settings-daemon/files')
-rw-r--r-- | gnome-base/gnome-settings-daemon/files/glib-2.58-compat.patch | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/gnome-base/gnome-settings-daemon/files/glib-2.58-compat.patch b/gnome-base/gnome-settings-daemon/files/glib-2.58-compat.patch new file mode 100644 index 000000000000..94e1cad666e3 --- /dev/null +++ b/gnome-base/gnome-settings-daemon/files/glib-2.58-compat.patch @@ -0,0 +1,33 @@ +From 3110457f72f70b2d283c1ad2f27b91b95d75d92f Mon Sep 17 00:00:00 2001 +From: Christian Hergert <chergert@redhat.com> +Date: Wed, 18 Jul 2018 19:31:17 -0700 +Subject: [PATCH] housekeeping: fix improper notify_notification_close() usage + +notify_notification_close() expects that a parameter will be available for +the error location, which could be a dangling pointer in a register or +on the stack in the case of some architectures. + +This was caught by GNOME/glib#1425 which allows us to check proper type +parameters. +--- + plugins/housekeeping/gsd-disk-space.c | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +diff --git a/plugins/housekeeping/gsd-disk-space.c b/plugins/housekeeping/gsd-disk-space.c +index 0ae40193..0eee94ea 100644 +--- a/plugins/housekeeping/gsd-disk-space.c ++++ b/plugins/housekeeping/gsd-disk-space.c +@@ -1017,7 +1017,9 @@ gsd_ldsm_clean (void) + g_clear_object (&ldsm_monitor); + g_clear_object (&settings); + g_clear_object (&privacy_settings); +- g_clear_pointer (¬ification, notify_notification_close); ++ /* NotifyNotification::closed callback will drop reference */ ++ if (notification != NULL) ++ notify_notification_close (notification, NULL); + g_slist_free_full (ignore_paths, g_free); + ignore_paths = NULL; + } +-- +2.17.0 + |