Hi,

On Fri, 13 Mar 2015 09:36:29 +0000, Simon McVittie wrote:
> Looking at <https://bugs.debian.org/762512> it seems that the intention
> these days is:
>
> * gnome-settings-daemon is only intended to work with GNOME Shell
>   (or at least Mutter);
> * non-Shell GNOME sessions should run gnome-flashback components instead of
>   gnome-settings-daemon;
> * non-GNOME sessions should not run either
>
> In particular, the Compiz- and Metacity-based sessions provided by
> gnome-session-flashback already do this, so they should no longer be
> affected by this.
>
> gnome-flashback and/or g-s-d maintainers: is what I said above accurate?

In GNOME Flashback, we *do* use gnome-settings-daemon, just not all
components of it do something useful for us.

So non-Shell GNOME sessions should run gnome-flashback components
(it is possible to enable/disable needed components via GSettings)
*in addition to* gnome-settings-daemon.

The code that makes mouse cursor appear is libidle-monitor [1].
That code is based on code in Mutter and is not needed when the
window manager is Mutter (or something based on it).

[1]: 
https://git.gnome.org/browse/gnome-flashback/tree/gnome-flashback/libidle-monitor

Note: There should be no Compiz-based session in Debian, if one is
shown for you, please report a bug :)

> On Wed, 30 Jul 2014 at 10:52:08 +0200, Michał Politowski wrote:
>> Same problem under gnome-session-flashback.
>> Disabling the cursor plugin with dconf also helped here (after restart).
>
> This particular case should have been fixed in September (gnome-panel/3.8.1-4)
> according to <https://bugs.debian.org/762512>, because gnome-session-flashback
> no longer uses gnome-settings-daemon.

Yes, it should no longer be an issue.

--
Dmitry Shachnev

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to