After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 673586 - daemon: Drop dbus activation capability
daemon: Drop dbus activation capability
Status: RESOLVED FIXED
Product: gnome-settings-daemon
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2012-04-05 16:35 UTC by Ray Strode [halfline]
Modified: 2012-04-05 17:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
daemon: Drop dbus activation capability (6.70 KB, patch)
2012-04-05 16:35 UTC, Ray Strode [halfline]
none Details | Review
daemon: Drop dbus activation capability (6.72 KB, patch)
2012-04-05 16:37 UTC, Ray Strode [halfline]
none Details | Review
daemon: Drop dbus activation capability (8.24 KB, patch)
2012-04-05 16:55 UTC, Ray Strode [halfline]
committed Details | Review

Description Ray Strode [halfline] 2012-04-05 16:35:47 UTC
Years ago, GDM activated gnome-settings-daemon via dbus as
part of its hand-rolled greeter session. These days it uses
gnome-session instead of a hand-rolled session, and so
gnome-settings-daemon no longer needs to be activatable.

Furthermore, when gnome-settings-daemon is activated, the only
way it functions is if it's subsequently given an "Awake" call.
This limitation was added because it was getting unintentionally
activated in none-GNOME sessions (when those sessions were hosting
gnome apps, like rhythmbox), causing all sorts of havoc.

This doesn't-function-until-Awake-called limitation means that if
settings daemon ever crashes and gets unintentionally dbus activated
before gnome-session has a chance to respawn it, then the whole desktop
breaks (since whatever accidentally activates it won't call Awake).
This actually happens in practice because gnome-shell's power indicator
tries to track the power plugin's object properties.

This commit removes the ability for gnome-settings-daemon to be dbus
activated. It only causes problems, and no longer solves anyway.
Comment 1 Ray Strode [halfline] 2012-04-05 16:35:49 UTC
Created attachment 211405 [details] [review]
daemon: Drop dbus activation capability
Comment 2 Ray Strode [halfline] 2012-04-05 16:37:15 UTC
Created attachment 211406 [details] [review]
daemon: Drop dbus activation capability

Years ago, GDM activated gnome-settings-daemon via dbus as
part of its hand-rolled greeter session. These days it uses
gnome-session instead of a hand-rolled session, and so
gnome-settings-daemon no longer needs to be activatable.

Furthermore, when gnome-settings-daemon is activated, the only
way it functions is if it's subsequently given an "Awake" call.
This limitation was added because it was getting unintentionally
activated in none-GNOME sessions (when those sessions were hosting
gnome apps, like rhythmbox), causing all sorts of havoc.

This doesn't-function-until-Awake-called limitation means that if
settings daemon ever crashes and gets unintentionally dbus activated
before gnome-session has a chance to respawn it, then the whole desktop
breaks (since whatever accidentally activates it won't call Awake).
This actually happens in practice because gnome-shell's power indicator
tries to track the power plugin's object properties.

This commit removes the ability for gnome-settings-daemon to be dbus
activated. It only causes problems, and no longer solves anyway.
Comment 3 Ray Strode [halfline] 2012-04-05 16:55:14 UTC
Created attachment 211412 [details] [review]
daemon: Drop dbus activation capability

Years ago, GDM activated gnome-settings-daemon via dbus as
part of its hand-rolled greeter session. These days it uses
gnome-session instead of a hand-rolled session, and so
gnome-settings-daemon no longer needs to be activatable.

Furthermore, when gnome-settings-daemon is activated, the only
way it functions is if it's subsequently given an "Awake" call.
This limitation was added because it was getting unintentionally
activated in none-GNOME sessions (when those sessions were hosting
gnome apps, like rhythmbox), causing all sorts of havoc.

This doesn't-function-until-Awake-called limitation means that if
settings daemon ever crashes and gets unintentionally dbus activated
before gnome-session has a chance to respawn it, then the whole desktop
breaks (since whatever accidentally activates it won't call Awake).
This actually happens in practice because gnome-shell's power indicator
tries to track the power plugin's object properties.

This commit removes the ability for gnome-settings-daemon to be dbus
activated. It only causes problems, and no longer solves anyway.
Comment 4 Bastien Nocera 2012-04-05 17:10:37 UTC
Review of attachment 211412 [details] [review]:

Looks good to commit to master once branched.
Comment 5 Ray Strode [halfline] 2012-04-05 17:26:06 UTC
Attachment 211412 [details] pushed as b778aad - daemon: Drop dbus activation capability

gnome-3-4 seems to be already branched.