Docky doesn't works in session start

What does show? Is it classic? My guess is that Do is starting before compiz, or whatever compositor you're using.

Don't shows nothing because I have the next settings:
Appearance = Docky
Hide window at start.
Don't show notification icon.

But if I press Super + Space it shows the classic window, I have to change the appearance from Docky to Classic and from Classic to Docky again to show me the bar.

"My guess is that Do is starting before compiz". Probably this is the problem, but this is something that this program should be expected, since the execution order of programs, at the beginning of the session, is unpredictable.

The "Avant Window Navigator" shows an error message if it detects that Compiz is not running. But if Compiz starts when the message is present, it's hidden and the AWN bar starts correctly.

On Mon, Feb 2, 2009 at 12:26 PM, Simon <email address hidden> wrote:

> but this is something that this program should be expected,
> since the execution order of programs, at the beginning of the session,
> is unpredictable.
>

Right, Do still starts, just not with a theme that requires compositing.

The "Avant Window Navigator" shows an error message if it detects that
> Compiz is not running. But if Compiz starts when the message is present,
> it's hidden and the AWN bar starts correctly.
>

We do start correctly. This isn't our bug, fix your session startup so that
Do starts after compiz. An easy way it just to make a little startup script
that sleeps for 15 seconds or so before Do starts.

--
--Alex Launi

> We do start correctly. This isn't our bug, fix your session startup so that
> Do starts after compiz. An easy way it just to make a little startup script
> that sleeps for 15 seconds or so before Do starts.
>
> --
> --Alex Launi
>

No Alex. It's a genome-do bug. If DO needs some other feature to run correctly and this feature isn't available because the OS is still loading it...

It is a problem of DO run after, and not before, that feature is available.

Do does run correctly. Do doesn't crash, it just responds to your active
environment. If your computer starts up Do before it starts compositing
that's not our fault. We handle it gracefully.

--
--Alex Launi

I also have this problem. I followed alex's advice and wrote a script that does sleep 10 and then gnome-do which solves the problem. I don't really think this is ideal, though. Can't you just use a black background if compositing is off?

Alex,

Is this an issue we should take up with Gnome? I suppose maybe Compiz is not starting (or at least not done loading) until after some of the startup applications have already begun. I would think maybe Gnome-DO could account for this, as on the other bug report, but more likely this could happen to other applications if Gnome doesn't solve the problem.