on startup scripts

[James Takac]

Hi Mario

On Sunday 13 May 2007 18:53:07 Mario Vukelic wrote:
> On Sun, 2007-05-13 at 18:02 +1000, James Takac wrote:
> > That's System->Preferences->Sessions-Startup programs. But it wont
> > remeber anything added on either of my systems (ubuntu 7.04)
>
> Click new, enter a name and command, click ok. This does not work?
>

That appears to work to this point

> > and it wont let me set
> > the order or priority either.
>
> After creating an entry, go to the tab "current session" and enter the
> order here (possibly you have to log out and in first, if you cannot yet
> find the newly created entry in the list)
>

Entry not there to set priority 

> > Would be nice if it did but tis either broken
> > in this respect on my sys
>
> Did you click the Help button in the session properties? I suppose not,
> because, e.g., how to enter the order is explained there, and everything
> else, in great detail.
>

First thing I did. Followed instructions implicitly and still wont remember 
the addition of anything I put in the start progs section which is 
frustrating. Nothing like following instructions that for some reason just 
dont wanna work on a particular set of systems LOL

Just had a look at gdesklets itself. Tis a python prog. Could that be the 
reason it doesn't get remembered via this method? Somehow I doubt .

> > or maybe need to be root?
>
> No

Didn't think so.

>
> >  Another thought here. I'm
> > guessing this modifies a script somewhere. Anyone know which one?
>
> $HOME/.gnome2/session
>
> > Maybe I can
> > modify it directly?
>
> The format is pretty understandable, but there are many magic numbers in
> there and I have no idea how to correctly generate them.


Thx. this maybe where I need to look then?

Just found online others are having the same prob with 
System->Preferences-Sessions->Startup Programs not working. Check out

https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/71200

to see what I mean. Seems it's considered a bug that happenes on some systems 
and not others. This is exactly what I am experiencing on my systems. Seems 
the solution is to change the permissions in .config/autostart. Seems the 
prob is that root is set as the owner when it should be the user. Just 
changed the owner and I can confirm it now works

James