Docky warns that there is no compositing support when running under Metacity with active compositing manager

Bug #552273 reported by Matt Sephton
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Docky
Invalid
Undecided
Unassigned

Bug Description

Docky warns that there is no compositing support when running under Metacity with active compositing manager. This is incorrect.

Notes:
It only happens infrequently when Docky is set to start when computer starts.
Running with -d from terminal does not produce the error.

To reproduce:
use Metacity
activate Metacity compositing manager (easiest way is to use Ubuntu Tweak, at the bottom of the Window Manager Settings page)
set Docky to start when computer starts
reboot

Ubuntu 9.10 Karmic Koala
+ Auto login
GNOME 2.28.1
ATI Mobility RADEON M6 LY
IBM ThinkPad X31

If I can provide any more info please let me know.

Revision history for this message
Matt Sephton (matt-sephton) wrote :
Revision history for this message
Robert Dyer (psybers) wrote :

Actually what you are seeing is that Docky starts before Metacity's compositor does, and it warns you of such. It is a race condition during startup and nothing we can do about it. You can set a delay in starting Docky (to give time for the compositor to start) or just live with the popup.

Changed in docky:
status: New → Invalid
Revision history for this message
Matt Sephton (matt-sephton) wrote :

Ah, that makes sense completely.

Please let me know how I can set a delay in starting Docky.

Revision history for this message
Robert Dyer (psybers) wrote :

Edit the docky launcher script and put a 'sleep 5' to sleep for 5 seconds.

Revision history for this message
Matt Sephton (matt-sephton) wrote :

Thanks.

Revision history for this message
Dario Panico (dariopan) wrote :

the launcher script isn't created by docky itself? shouldn't it be created with the default sleep?

Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :

Would it be possible to just have Docky wait 5 seconds before checking if compositing is available, rather than making Docky wait 5 seconds to start up at all?

Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :

Just looked through the source, it seems like Docky already does this. Maybe the time should be changed from 2 seconds to something longer (~5 seconds)? I get this whenever I shut down, and usually when I start up on my relatively speedy laptop.

Also, on shutdown, I feel like it appears instantly, rather than waiting 2 seconds. I'll observe next time I'm shutting down and report it if this is the case.

Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :

Nope, it appears that it waits 2 seconds as expected, but 2 seconds is a very short time. Is there any reason that it should not be increased?

(sorry for comment spam)

Revision history for this message
Robert Dyer (psybers) wrote :

Quite frankly it is a hack. The only reason I allow it is sometimes compositing dies and is reloaded, and generally in that case 2s is plenty.

For this specific bug, this hack may or may not help but MY opinion is that the bug needs fixed in gnome session by allowing ordering!

Revision history for this message
Matthew Pirocchi (matthew-pirocchi) wrote :

Robert: Sure, but in the meantime could it be increased to 5 seconds?

Revision history for this message
Mathijs Henquet (mathijshenquet) wrote : Re: [Bug 552273] Re: Docky warns that there is no compositing support when running under Metacity with active compositing manager

Altough this is not really a fix for docky. You can try to change the default window manager. There is a gconf key to do that but its easier with gnome-tweak. Just replace gnome-wm with compiz, you will have better boot speeds and no more errors.

Mathijs Henquet

Op 20 okt. 2010 om 21:03 heeft Matthew Pirocchi <email address hidden> het volgende geschreven:

> Robert: Sure, but in the meantime could it be increased to 5 seconds?
>
> --
> Docky warns that there is no compositing support when running under Metacity with active compositing manager
> https://bugs.launchpad.net/bugs/552273
> You received this bug notification because you are subscribed to Docky.
>
> Status in Docky: Invalid
>
> Bug description:
> Docky warns that there is no compositing support when running under Metacity with active compositing manager. This is incorrect.
>
> Notes:
> It only happens infrequently when Docky is set to start when computer starts.
> Running with -d from terminal does not produce the error.
>
> To reproduce:
> use Metacity
> activate Metacity compositing manager (easiest way is to use Ubuntu Tweak, at the bottom of the Window Manager Settings page)
> set Docky to start when computer starts
> reboot
>
> Ubuntu 9.10 Karmic Koala
> + Auto login
> GNOME 2.28.1
> ATI Mobility RADEON M6 LY
> IBM ThinkPad X31
>
> If I can provide any more info please let me know.
>
>

Revision history for this message
Dan Smith (mrdanpsmith) wrote :

I know you're saying there's nothing that can be done about it, but everyone that uses docky+ubuntu 10.10 is experiencing this problem. I get the race condition problem, but why can't there be an option to just turn the warning off entirely? I don't really see how it's a problem that there's no compositing and the themes don't work anyway. I don't really ever want the warning even if my compositing manager shuts down for some reason. Why not just make the warning optional?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.