Till, as I wrote, this patch is already in hardy. It came as a backport
from upstream in 0.6.21-2
avahi (0.6.21-2) unstable; urgency=low
* debian/patches/20_avahi-libdns_sd-crash.patch
+ Added. Fix a segfault when registering services with libdns_sd before the
avahi daemon finished starting up (from upstream SVN)
-- Sjoerd Simons <[EMAIL PROTECTED]> Sun, 09 Sep 2007 12:15:55 +0200
And then it was released in upstream-0.6.22 :
avahi (0.6.22-1) unstable; urgency=low
<..snip..>
[ Sjoerd Simons ]
* New upstream release
<..snip..>
* debian/paches/20_avahi-libdns_sd-crash.patch
- Removed. Fixed upstream
-- Sjoerd Simons <[EMAIL PROTECTED]> Thu, 03 Jan 2008 17:00:24 +0100
This is why I was asking if it was really confirmed in hardy (in this case,
there would be under hardy a supplementary cause to the segfault/abort)
As this bug is timing/system load dependent, anyone who have triggered
the bug on one of one's box will be helpful during testing (that I bet
will be far from short, to not stress Martin anymore with regressions
(xorg-server was probably the straw that broke his camel’s back ;-) )
--
[Gutsy SRU request] CUPS fails to start on boot
https://bugs.launchpad.net/bugs/183652
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
