| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
We don't want to quit yet because if we do, gnome-shell and still
mapped windows lose their theme and icons. But we have to unown our
DBus name otherwise gnome-session will hang waiting for us.
This only works due to a bug in gnome-session where it handles any
client name being unowned as if the client has disconnected. Will need
to be revisited when that bug is fixed in gnome-session.
https://bugzilla.gnome.org/show_bug.cgi?id=727049
|
|
|
|
|
|
|
|
|
|
|
|
| |
gnome-session asks all registered clients to stop after the user
confirms the poweroff/logout dialog, but we should ignore that
request, because non registered applications are still mapped
and they would lose their theme and icons if we die (and same
for the shell).
We will go away as soon as the X11 connection is closed or the
session bus dies anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=707790
|
|
|
|
|
|
|
| |
Let's use glib's builtin facilities for signals instead of
our own pipe.
https://bugzilla.gnome.org/show_bug.cgi?id=707790
|
|
|
|
|
|
|
| |
The SessionOver signal is legacy and is never emitted by
gnome-session.
https://bugzilla.gnome.org/show_bug.cgi?id=707790
|
| |
|
|
|
|
|
| |
This will be used across multiple plugins, so put it together with
the screensaver and session proxies.
|
|
|
|
|
|
|
| |
We're working actively to reduce the dependency on x11, but for
now this is a hard requirement.
https://bugzilla.gnome.org/show_bug.cgi?id=706419
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Much like with the session manager, several plugins need to connect
to the screen saver (to lock the screen in response to various events).
This commit adds a new api:
gnome_settings_bus_get_screen_saver_proxy
that parallels the existing gnome_settings_bus_get_session_proxy call, and
changes all users of their own screen saver proxies to use this shared proxy.
https://bugzilla.gnome.org/show_bug.cgi?id=705127
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The gnome-settings-session code is so named because it used to
exclusively house login session specific code (ConsoleKit/logind/gnome-session).
Since then it's been used more generally as a place to stuff singleton
dbus proxies used across multiple plugins.
This commit renames it to gnome-settings-bus to give it a more
appropriate name for its current role.
https://bugzilla.gnome.org/show_bug.cgi?id=705127
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Generating D-Bus proxies is more convienent and more typesafe
than using naked GDBusProxy objects.
As a first step this commit changes the common session manager proxy to
be generated from XML. Since the generated proxy can be compatibly used
in any existing GDBusProxy calls, this commit doesn't attempt to rewrite
all the plugins to use the generated apis. That can happen in future
clean ups.
https://bugzilla.gnome.org/show_bug.cgi?id=705127
|
|
|
|
|
| |
We'll just dispose the manager afterwards, so let the caller
do that instead of introducing another way to do it.
|
|
|
|
|
|
| |
And check for g_dbus_connection_register_object()'s retval.
https://bugzilla.gnome.org/show_bug.cgi?id=704791
|
| |
|
|
|
|
| |
Generally I add $(AM_FOO) before each modname_FOO variable.
|
|
|
|
| |
gnome-settings-daemon/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
|
| |
|
|
|
|
|
|
| |
Replace the bash-only substitution with an sh-compatible version.
https://bugzilla.gnome.org/show_bug.cgi?id=701322
|
|
|
|
|
|
| |
We were trying to remove a comma instead of a single-quote.
https://bugzilla.gnome.org/show_bug.cgi?id=701322
|
|
|
|
|
|
|
|
|
|
|
| |
In particular, we can't get the locale value out of GSettings
in order to set LC_PAPER etc, since calling into GSettings
initializes the dconf backend which in turn uses gdbus, which
starts a worker thread.
As a simple workaround, set up the locale environment in
a small wrapper script that then exec's the g-s-d binary.
https://bugzilla.gnome.org/show_bug.cgi?id=701322
|
| |
|
|
|
|
|
|
| |
Just as we set gnome-session's.
https://bugzilla.gnome.org/show_bug.cgi?id=693381
|
|
|
|
|
|
|
|
| |
When starting up, we tell gnome-session to set the environment variables
for new starting programs, but we don't set the environment for our
own children. Do this on start up, as soon as possible.
https://bugzilla.gnome.org/show_bug.cgi?id=693381
|
|
|
|
|
|
| |
User-specified format should also apply to the paper format.
https://bugzilla.gnome.org/show_bug.cgi?id=690750
|
|
|
|
|
|
| |
When constructing a string literal, one needs to use
stringification, not tokenization. This was causing
PluginName## to appear in debug output.
|
| |
|
| |
|
|
|
|
|
|
| |
Even before we've registered with gnome-session, to avoid
the window manager starting before some of the necessary early plugins
such as the cursor plugin.
|
|
|
|
| |
Shaves about 2.7k lines of code.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=690078
|
|
|
|
|
|
|
| |
This is intended for quickly and easily testing g-s-d changes
without having gnome-session restart it.
https://bugzilla.gnome.org/show_bug.cgi?id=689402
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=689070
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than having gdm load all the new plugins by default,
especially when gnome-settings-daemon gets updated and gdm doesn't,
keep a list of whitelisted plugins. Only those can be enabled, others
will be unknown and ignored.
By default, all plugins are whitelisted.
https://bugzilla.gnome.org/show_bug.cgi?id=662220
|
|
|
|
|
|
|
| |
Remove an #include that was missed by Colin's patch to remove the
systemd dependency.
https://bugzilla.gnome.org/show_bug.cgi?id=686650
|
|
|
|
|
|
|
|
|
|
|
|
| |
After porting both users of the helper code (the power and
color plugins) to use gnome-session's SessionIsActive property,
remove the libsystemd-login dependent code.
As originally intended, gnome-settings-daemon requires
systemd for the power plugin to work at run-time, but does
not hard depend on libsystemd-login itself at compile-time.
https://bugzilla.gnome.org/show_bug.cgi?id=686650
|
|
|
|
| |
Only if IBus is available though. #fallback
|
|
|
|
|
|
| |
See http://git.gnome.org/browse/glib/commit/?id=7c42ab23b55c43ab96d0ac2124b550bf1f49c1ec
https://bugzilla.gnome.org/show_bug.cgi?id=687072
|
|
|
|
|
|
|
|
| |
This ensures that any plugin idles will only run after RegisterClient
but also that we only call RegisterClient after Setenv since otherwise
Setenv isn't effective.
https://bugzilla.gnome.org/show_bug.cgi?id=686814
|
|
|
|
|
|
| |
This reverts commit dcb54d8a1c4ecacf6fbe17bdffefdca3b1e6d2d5.
https://bugzilla.gnome.org/show_bug.cgi?id=686814
|
|
|
|
| |
Commit e76a752c7d3901b3abbc1733b824c80a3dddec16 broke it.
|
|
|
|
|
|
|
|
| |
There is no need at all to do the listening for systemd or
ConsoleKit signals more than once in the gnome-settings-daemon
process.
https://bugzilla.gnome.org/show_bug.cgi?id=686554
|
| |
|
|
|
|
|
|
|
|
| |
Instead of offering both ConsoleKit and logind support.
We already require logind being available for inhibition and
suspend/hibernation in the power plugin, so requiring logind
for session tracking doesn't add any new dependencies.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're deferring some slower operations to idles, in plugins,
to have it happen after session registration and not slow down
login - but I've observed that the ordering is unreliable.
Sometimes we end up doing the RegisterClient call after the
initial set of idles.
Ensure that the session registration happens before other idles by
making the idle higher priority than the plugins.
https://bugzilla.gnome.org/show_bug.cgi?id=686579
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=686556
|
|
|
|
|
|
|
|
| |
Many plugins were creating these on their own, with ugly async
code. It seems much more straightforward and efficient to get
a proxy once, and keep it around for everybody to use.
https://bugzilla.gnome.org/show_bug.cgi?id=686556
|
|
|
|
|
|
|
|
|
|
|
| |
If IBus isn't installed, don't set the QT_IM_MODULE or XMODIFIERS
envvars, as that breaks other Input Methods.
As we advice people who don't want to use IBus to just uninstall
ibus itself, we should handle being built with IBus support but run-time
support not being there.
https://bugzilla.gnome.org/show_bug.cgi?id=685514
|
|
|
|
|
|
|
|
|
| |
If we are compiled with IBus support and the current session isn't
fallback then we always set the QT_IM_MODULE and XMODIFIERS
environment variables so that Qt and XIM supporting applications work
as best as possible.
https://bugzilla.gnome.org/show_bug.cgi?id=680313
|
|
|
|
|
|
|
|
| |
We already have a convenience macro for plugins to use to
define their types.
This commit augments and leverages that macro to remove
class_finalize function definition boilerplate.
|
| |
|