I believe my comment #13 has been incorrectly interpreted. I wrote it in response to someone "assigning" this bug to gnome-bugs #673055 (I received a notification of the change). I wanted to make sure we don't end up interpreting the upstream bug as a fix for this one and hence wait on it (instead, pointed to the debian patch to be taken care).
I have been using this work around for sometime now and it really has reduced my stress level since :). For now while waiting for the official fix to land, I just did following to do away with manual launch.
1. renamed syndaemon to syndaemon-bin and
2. created a sh script "syndaemon" with following content
"
#!/bin/sh
syndaemon-bin -i 2 -t -K -R
"
Hi Sebastien,
I believe my comment #13 has been incorrectly interpreted. I wrote it in response to someone "assigning" this bug to gnome-bugs #673055 (I received a notification of the change). I wanted to make sure we don't end up interpreting the upstream bug as a fix for this one and hence wait on it (instead, pointed to the debian patch to be taken care).
I have been using this work around for sometime now and it really has reduced my stress level since :). For now while waiting for the official fix to land, I just did following to do away with manual launch.
1. renamed syndaemon to syndaemon-bin and
2. created a sh script "syndaemon" with following content
"
#!/bin/sh
syndaemon-bin -i 2 -t -K -R
"
Thanks.