Apologies for being a little direct on the last post.
I think that in many cases this bug might just be caused by those two syndaemon instances running, which would make sense as oneiric made the switch from lightdm to gdm, and this does not happen on my laptop if I use gdm (whoch does NOT start its own syndaemon instance).
Of course, it is possible some people have the same bug behaviour with other causes.
Apologies for being a little direct on the last post.
I think that in many cases this bug might just be caused by those two syndaemon instances running, which would make sense as oneiric made the switch from lightdm to gdm, and this does not happen on my laptop if I use gdm (whoch does NOT start its own syndaemon instance).
Of course, it is possible some people have the same bug behaviour with other causes.
Regards
Sven