In fact I wasn't able to reproduce the same behavior in maverick : the
.desktop file was correctly remove when I remove it in gnome-session-
properties. So I won't open a new bug report : this is now OK.
--
autostart of gnome-settings-daemon can be prevent by one file
https://bugs.launchpad.net/b
I agree with you. However I got a trouble because of this design : I
disabled and remove the launch of g-s-d using gnome-session-properties
but g-s-d still doesn't launch during following startup.
I will open a separate bug for this because gnome-session-properties
doesn't show .desktop file that
thank you for your bug report but user configurations take over system
one by design otherwise you would not have a way to change those
configurations for your user, that's not a bug, remove the .local one to
go back to the system value
** Changed in: gnome-settings-daemon (Ubuntu)
Importance:
** Description changed:
Binary package hint: gnome-settings-daemon
- I sometime got some trouble with gnome-settings-daemon (maybe the one of Bug
#312501), so I added gnome-settings-daemon to the applications the are launched
with the user's session.
+ I sometime got some trouble with gnome
** Summary changed:
- [lucid] theme not used until gnome-settings-daemon is started
+ autostart of gnome-settings-daemon can be prevent by one file
** Description changed:
Binary package hint: gnome-settings-daemon
- This occurs until I run gnome-settings-daemon, so I added it to the
appli
