Closed blueyed closed 12 years ago
i don't think it's a bug at all. the error happens when the daemon can't bind to dbus for the requested name and fails therefor. i just added a more aggresive binding to dbus with retries and sleeps. this should help when the daemon is restarted so dbus got enough time to notice the old deamon missing. i think that logrotate caused the daemon died, but i could not reporduce it yet.
Thanks for fixing it.
For the record, it is this commit: c5c675fa247333380073b7a4a5878ab83f9537bc
ulatency crashed, and I reported it via Apport in the Launchpad bugtracker: https://bugs.launchpad.net/ubuntu/+source/ulatencyd/+bug/883977
ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: ulatencyd 0.5.0-3 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic-pae 3.0.6 Uname: Linux 3.0.0-13-generic-pae i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Oct 30 21:53:41 2011 ExecutablePath: /usr/sbin/ulatencyd InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: /usr/sbin/ulatencyd -d -f /var/log/ulatencyd ProcEnviron: PATH=(custom, no user) SHELL=/bin/sh Signal: 5 SourcePackage: ulatencyd StacktraceTop: u_dbus_setup () core_init () main () Title: ulatencyd crashed with signal 5 in u_dbus_setup() UpgradeStatus: Upgraded to oneiric on 2011-09-29 (31 days ago) UserGroups:
StacktraceTop: