Problem seem to persist on Jaunty.
I _may_ have seen it survive a few times, but I am uncertain of the
circumstances, and can't reliably reproduce.
Anyway I have found a workaround.
In /usr/lib/pm-utils/sleep.d/ I have created "50syndaemon" as follows:
#!/bin/sh
resume_syndaemon()
{
if [ ! "$( pidof syndaemon )" ]; then
export DISPLAY=:0.0
sudo -u gaute syndaemon -d -t -i 2
fi
}
case "$1" in
thaw|resume)
resume_syndaemon
;;
*) exit $NA
;;
esac
exit 0
--
I cannot quite see how this could be generalized however.
There is the hardcoded username, and I guess DISPLAY=:0.0 cannot always be
guaranteed,
and a user may have wanted other arguments to syndaemon anyway.
I guess the right thing to do is make the daemon survive in the first place.
I would still like to contribute to this, but it would be good to know if I am
the only one that have this problem,
and if not, then some guidance on what to try or how to instrument would be
good.
--
syndaemon gone after resume on intrepid and jaunty
https://bugs.launchpad.net/bugs/326117
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
