Comment 27 for bug 779752
Revision history for this message
| Patricio Santiago Marrone (cebollo3-l) wrote | #27 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Since this smells like race conditions to me (fails randomly, fails when loads too early, etc) I change the atostart command from 'docky' to 'sh -c "sleep 10; docky"' to give it some delay before it starts. All computers in the lab now booted a flawless docky. I think this shows that docky is being initialized before some of the components it needs, perhaps?
Note: In my case, I first tried sleep 5, but some computers still didn't load correctly. I increased it so that it got excecuted after the desktop was initialized.