From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: "printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] cupsd crashes when Avahi is used
Date: Thu, 05 Dec 2013 19:58:35 +0100 [thread overview]
Message-ID: <52A0CCDB.3020503@gmail.com> (raw)
In-Reply-To: <E3EE29B3-EDB7-4452-8803-9D150FBB3554@apple.com>
Thanks, I have added your answer to the bug report now.
Till
On 12/05/2013 07:48 PM, Michael Sweet wrote:
> Till,
>
> Based on the bug report, it sounds like this is an internal bug of Avahi.
>
> The fact that a production build of a library is forcing an assert is troubling - it doesn't allow the caller to perform any recovery and IMHO makes Avahi totally unsuited to production use at all.
>
> The fix on the CUPS side is easy - bundle mDNSResponder (Apache license) with Ubuntu and build CUPS against it. For Avahi, we'll need to get someone from Avahi to look at the issue...
>
>
> On Dec 5, 2013, at 1:25 PM, Till Kamppeter <till.kamppeter@gmail.com> wrote:
>
>> Hi,
>>
>> at Ubuntu many users (> 2000) hit the following bug:
>>
>> https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1131854
>>
>> It is an assert failure in a function of the Avahi library which makes
>> the CUPS daemon abort, naturally only if CUPS uses Avahi which is the
>> case in Ubuntu.
>>
>> The Ubuntu patches on CUPS do not change anything in the Avahi support,
>> so the problem most probably also occurs with other distributions.
>>
>> Anyone has already observed this problem? Can it be a CUPS bug? If it is
>> an Avahi bug, is it already known?
>>
>> Till
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
prev parent reply other threads:[~2013-12-05 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 18:25 [Printing-architecture] cupsd crashes when Avahi is used Till Kamppeter
2013-12-05 18:48 ` Michael Sweet
2013-12-05 18:58 ` Till Kamppeter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A0CCDB.3020503@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=msweet@apple.com \
--cc=printing-architecture@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.