~vcs-imports/gnome-settings-daemon/master : changes

~vcs-imports/gnome-settings-daemon/master » Changes from revision 3359

From Revision 3359 to 3340

Rev	Summary	Authors	Date
3359	power: Remove unneeded libsystemd-login dep power: Remove unneeded libsystemd-login dep I wrongly added a libsystemd-login build dependency. We actually only have a run-time one for the power plugin. https://bugzilla.gnome.org/show_bug.cgi?id=686650#c11	Bastien Nocera	12 years ago
3358	color: Don't check SessionIsActive if it didn't change color: Don't check SessionIsActive if it didn't change	Bastien Nocera	12 years ago
3357	main: Remove libsystemd-login specific code main: Remove libsystemd-login specific code 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	Colin Walters	12 years ago
3356	color: Use gnome-session's SessionIsActive property color: Use gnome-session's SessionIsActive property Rather than gnome-settings-daemon's libsystemd-login dependent code. https://bugzilla.gnome.org/show_bug.cgi?id=686650	Bastien Nocera	12 years ago
3355	color: Use gnome-session's SessionIsActive property color: Use gnome-session's SessionIsActive property Rather than gnome-settings-daemon's libsystemd-login dependent code. https://bugzilla.gnome.org/show_bug.cgi?id=686650	Bastien Nocera	12 years ago
3354	Updated POTFILES.in Updated POTFILES.in	Piotr Drąg	12 years ago
3353	power: Don't try to unref a NULL pointer power: Don't try to unref a NULL pointer	Rui Matos	12 years ago
3352	power: Simplify {icon,state}_changed functions power: Simplify {icon,state}_changed functions	Bastien Nocera	12 years ago
3351	power: Remove status icon power: Remove status icon As it's only used in fallback. #fallback	Bastien Nocera	12 years ago
3350	a11y-settings: gnome-shell OSK doesn't need a11y a11y-settings: gnome-shell OSK doesn't need a11y So don't try and load the modules. Only Caribou in fallback mode would have needed it. #fallback https://bugzilla.gnome.org/show_bug.cgi?id=655985	Bastien Nocera	12 years ago
3349	a11y-keyboard: Remove fallback support code a11y-keyboard: Remove fallback support code The preferences dialogue and the status icon are now a first-class icon and popup-menu in gnome-shell. #fallback https://bugzilla.gnome.org/show_bug.cgi?id=686548	Bastien Nocera	12 years ago
3348	automount: Remove fallback automount code automount: Remove fallback automount code As the fallback mode is going away. #fallback https://bugzilla.gnome.org/show_bug.cgi?id=682859	Bastien Nocera	12 years ago
3347	keyboard: Remove fallback support keyboard: Remove fallback support IBus is now started if required. #fallback	Bastien Nocera	12 years ago
3346	main: Always set the IBus envvars main: Always set the IBus envvars Only if IBus is available though. #fallback	Bastien Nocera	12 years ago
3345	data: Remove Unity from autostart desktop file data: Remove Unity from autostart desktop file Unity uses fallback mode, and we don't support it anymore. #fallback	Bastien Nocera	12 years ago
3344	mouse: natural horizontal scroll fix mouse: natural horizontal scroll fix https://bugzilla.gnome.org/show_bug.cgi?id=686714	Ondrej Holy	12 years ago
3343	Updated Hebrew translation. Updated Hebrew translation.	Yaron Shahrabani	12 years ago
3342	color: Turn an harmless g_warning into a g_debug color: Turn an harmless g_warning into a g_debug	Rui Matos	12 years ago
3341	keyboard: Don't print warnings when calls were cancelled keyboard: Don't print warnings when calls were cancelled https://bugzilla.gnome.org/show_bug.cgi?id=687810	Bastien Nocera	12 years ago
3340	keyboard: Prevent potential infinite loop keyboard: Prevent potential infinite loop XKB would notify us in the same way if the lockedMods changed because of a programmatic, or a physical/human change. This causes us changing the Num-Lock state generating another event on top of the one we just processed, and might cause infinite loops and 100% CPU usage. Instead, we now only apply the settings: - on startup - when remember-num-lock is changed to true https://bugzilla.gnome.org/show_bug.cgi?id=679151	Bastien Nocera	12 years ago

Older »