Unfortunately there seems to be no way to reproduce the bug, it *just happens*.
The only thing I have noticed is it tends to happen when wireless networks are detected or when network manager connects to one of the wireless networks available.
I have created a personalized launcher by myself, which forces docky to wait 5 seconds after login before starting up, in order to let network manager connect, but it's nothing more than a workaraound.
Docky is mentioned only once in my current .xsession-errors file, here comes the code:
Docky version: 2.0.6-1 (Archlinux only)
Unfortunately there seems to be no way to reproduce the bug, it *just happens*.
The only thing I have noticed is it tends to happen when wireless networks are detected or when network manager connects to one of the wireless networks available.
I have created a personalized launcher by myself, which forces docky to wait 5 seconds after login before starting up, in order to let network manager connect, but it's nothing more than a workaraound.
Docky is mentioned only once in my current .xsession-errors file, here comes the code:
** Message: pygobject_ register_ sinkfunc is deprecated (GtkWindow) register_ sinkfunc is deprecated (GtkInvisible) register_ sinkfunc is deprecated (GtkObject)
** Message: pygobject_
** Message: pygobject_
[Info 18:12:50.618] Docky version: 2.0.6 Release
[Info 18:12:50.731] Kernel version: 2.6.35.0
[Info 18:12:50.733] CLR version: 2.0.50727.1433
I hope these few lines of code can help you!