KAutoStart

[Christian Esken]

Am Samstag, 4. März 2006 23:08 schrieb Lubos Lunak:
> On Saturday 04 March 2006 23:03, Christian Esken wrote:
> > Am Samstag, 4. März 2006 22:24 schrieb Lubos Lunak:
> > >  Actually we support 3 phases Really Soon(TM). As soon as my startup
> > > patches are in SVN. Phase 0 for kdesktop+kicker (->no need for
> > > autostart-after= as that seems to be used for these two only, and
> > > moreover it doesn't right now really work anyway), phase 1 for parts of
> > > the desktop and phase 2 for everything else than can wait (you don't
> > > really need all that systray nonsense immediately).
> >
> > Hmmm .... why doesn't it work reliably?
> 
>  Autostart code handling waits for the app to register with DCOP (or just 
> waits until it's launched, I'm not sure), which happens rather soon in the 
> app's startup process and way before it's actually up and ready.
> 
> > Is the reason, that we don't know 
> > when the autostart is ready/finished? If this is the reason, then the
> > phases also won't work.
> 
>  They do :). Ksmserver has the same problem, as registration with the session 
> manager also happens soon, but kdesktop and kicker have special code to tell 
> ksmserver they're really ready.
> 
> > Take for example volume restauration: It must have 
> > FINISHED, before the login sound is played. How can you guarantee that? At
> > the moment I cannot, but hope to do so in KDE4 (see
> > https://bugs.kde.org/show_bug.cgi?id=91267).
> 
>  Kcminit is completely performed[*] before ksmserver (which triggers the login 
> sound) is launched, so I fail to see your problem.

The problem is as follows:
1) kcminit is run ... it is not restore volumes
2) ksmserver is started ... triggers login sound
3) Autostart programs are launched: autostart/restore_kmix_volumes.desktop restores volumes

Probably restore_kmix_volumes.desktop just shouldn't be a normal autostart application, but triggered "manually" before ksmserver.

   Christian

-- 
Is Unix ready for the Desktop? See http://www.kde.org