No programs can be added in the startup list.

[Giorgos Koklas]

Binary package hint: startup-tasks

This seems to be a random problem. Some have and some not.
To add a program to automatically startup I would go to :
system-->preferences-->sessions-->startup programs.
There I can add an application to the the list but it is not saved (if I close and reopen session manager it is not there and the app will not start on next login).

In the forums a workaround was suggested at this link:
http://ubuntuforums.org/showthread.php?p=1694346

[Greg Unger (mr-ory)]

I've been having the same problem. Confirmed.

[Sebastien Bacher (seb128)]

Thank you for your bug. Does changing the permissions for .config/autostart fix your problem?

[Giorgos Koklas (geo-kok-deactivatedaccount)]

Yes. The solution suggested in the forums (link provided above) does correct the problem. So by changing the permissions in .config/autostart it is solved.

[Sebastien Bacher (seb128)]

not a gnome-session bug then. Something you runned as admin changed the permission of that folder, if you figure what you probably can open a bug against it

[Giorgos Koklas (geo-kok-deactivatedaccount)]

Allow me to strongly doubt that. The reasons for that are:

1. The system was flawed since it was in a relatively "virgin" state, meaning that I encountered the problem in a relatively fresh installation the very first time i tried to add programs to the start up list.

2. Others have encountered the problem as mentioned in the forums. It is highly unlikely that we all screwed up the system in the same way!!!

3. I hardly knew at the time of the bug report how to change permissions in the system as a user. U see, CLI was something unknown to me at the time so I dont see how I could " break" it in that way......all I had done before discovering the bug was installing some apps through synaptic, such as Banshee and others, very mainstream apps....

[Sebastien Bacher (seb128)]

Le dimanche 26 novembre 2006 à 12:31 +0000, geokok a écrit :

> 1. The system was flawed since it was in a relatively "virgin" state,
> meaning that I encountered the problem in a relatively fresh
> installation the very first time i tried to add programs to the start up
> list.

Your user is not authorized to change the permission of that folder that
way and package do not change any user configuration, which means you
runned an application with sudo which did that

> 2. Others have encountered the problem as mentioned in the forums. It is
> highly unlikely that we all screwed up the system in the same way!!!

Why? How unlikely is it that some people runned the same program with
sudo?

> 3. I hardly knew at the time of the bug report how to change permissions
> in the system as a user. U see, CLI was something unknown to me at the
> time so I dont see how I could " break" it in that way......all I had
> done before discovering the bug was installing some apps through
> synaptic, such as Banshee and others, very mainstream apps....

One of that applications is broken then. Which one did you run with
sudo? Banshee is an application non installed by default by example.
It's likely that your problem comes from one application which is not
from the default set because otherwise we would probably have a bunch of
duplicate bugs about that

[Giorgos Koklas (geo-kok-deactivatedaccount)]

U could be right about that but unfortunately I cannot recall the apps installed before encountering the issue (and I really cant reformat just to try to "make it happen again".
Perhaps someone else has more details that will help to pin point what causes the issue.

[Daniel Silberschmidt (dansilber)]

Same problem here, was resolved with the suggested workaround

[Scott James Remnant (Canonical) (canonical-scott)]

This appears to have nothing to do with upstart?

[AmazingRando (toddp)]

I encountered this same problem. Changing ownership of .config/autostart did fix the problem, but it seems to me that what needs to happen is that gnome-sessions needs to display an error if it is unable to write the updated startup configuration, rather than close as though nothing is wrong. I suggest that we change this to be a bug with gnome-session that it doesn't have any error notification for this problem. What app might be changing the permissions of .config/autostart would then be a separate issue.