gnome-settings-daemon has been split up into separate daemons, which
means we'll need to invoke those separately.

See https://bugzilla.gnome.org/show_bug.cgi?id=772370

https://bugzilla.gnome.org/show_bug.cgi?id=772408

It is already done in the wrapper script, and needs to stay there.

See https://bugzilla.gnome.org/show_bug.cgi?id=756324
See https://bugzilla.gnome.org/show_bug.cgi?id=766176

https://bugzilla.gnome.org/show_bug.cgi?id=772562

e83da6fb introduced a regression where
clicking cancel on the power off dialog causes the dialog to reopen
itself in case any JIT inhibitor has been taken, since the inhibitors
are removed here and removing the inhibitor causing the dialog to reopen
to support functionality that was removed from gnome-shell three years
ago. To fix this, set the manager phase to running before removing the
inhibitors to ensure the power off dialog does not reopen.

https://bugzilla.gnome.org/show_bug.cgi?id=728151

(cherry picked from commit 92772626)

Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>

Apparently dash doesn't support >& and some people use dash.

This commit changes it to the more wordy form > ... 2>&1 .

https://bugzilla.gnome.org/show_bug.cgi?id=770363

This feature is the same as gnome.fallback kernel argument on Linux.
FreeBSD users can force the check result of gl-helper to be accelerated
or non-accelerated by setting gnome.fallback kernel environment variable
with the bootloader or kenv system call.

https://bugzilla.gnome.org/show_bug.cgi?id=765491

To give a user the option to use some other input method framework but
IBus, gnome-session should not override the QT_IM_MODULE and XMODIFIERS
environment variables if they are already set. The desired approach has
been implemented in gnome-settings-daemon:

https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=21a16d25d981f3ce34b764dbc8005dbf8edfbe97

It would be consistent to change gnome-session in a similar way.

dbus-update-activation-environment was introduced with dbus 1.10.4
gnome-session by itself does not depend on any specific version of
dbus at all - but on dbus-glib-1 (DBUS_GLIB_REQUIRED=0.76)

The latest version of dbus-glib (ver 106) requires dbus-1 1.8: it is
thus a valid setup to run not have dbus-update-activation-environment
on the system. Warning the user about its absence is alerting users
for not reason.

I have discovered a heap overflow with the help of an address sanitizer.

The require_dbus_session() function has this code:

        new_argv = g_malloc (argc + 3 * sizeof (*argv));

The intention is to allocate space for (argc + 3) pointers. However obviously a
parenthesis is missing, therefore only argc bytes + 3 * pointer size gets
allocated, which is insufficient space. This leads to invalid memory writes.

The fix is trivial: Parentheses around argc + 3.

https://bugzilla.gnome.org/show_bug.cgi?id=768441

Future versions of gettext will fail if this header is missing.

https://bugzilla.gnome.org/show_bug.cgi?id=768294

Michael Catanzaro authored Jun 30, 2016 and Michael Catanzaro committed Jul 01, 2016

Since the renderer string is now used to display the graphics label in
gnome-control-center, we need to make sure it gets set even if software
rendering is in use, else we wind up showing an empty string to the
user.

https://bugzilla.gnome.org/show_bug.cgi?id=768292

https://bugzilla.gnome.org/show_bug.cgi?id=766836

This tool does not exist anymore.

https://bugzilla.gnome.org/show_bug.cgi?id=766836