Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Apple Bonjour compatibility layer of Avahi" warning causes SIGPIPE crash #2931

Closed
michaelrsweet opened this Issue Sep 6, 2008 · 1 comment

Comments

Projects
None yet
1 participant
@michaelrsweet
Copy link
Collaborator

michaelrsweet commented Sep 6, 2008

Version: 1.3.8
CUPS.org User: martin.pitt.canonical

We all know and love the "Apple Bonjour compatibility layer of Avahi" warning, as described in STR #2655.

Now I got a report (http://bugs.debian.org/497492) that this warning causes a cups crash:

[pid 3977] write(2, "*** WARNING * The program 'cups"..., 89) = 89
[...]
[pid 3977] write(2, "
* WARNING *** Please fix your a"..., 76) = -1 EPIPE (Broken pipe)
[pid 3977] --- SIGPIPE (Broken pipe) @ 0 (0) ---
[...]
Process 3977 detached
<... nanosleep resumed> 0xbfe312e4) = ? ERESTART_RESTARTBLOCK (To be restarted)
--- SIGCHLD (Child exited) @ 0 (0) ---
sigreturn() = ? (mask now [])
wait4(-1, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGPIPE}], 0, NULL) = 3977
write(2, "cupsd: Child exited on signal 13!"..., 34cupsd: Child exited on signal 13!

Thus it seems the warning is triggered by some child process which does not have a stderr and thus dies with a SIGPIPE. I cannot reproduce the crash, but the cause seems pretty clear.

Since STR #2655 made it quite clear that the avahi bonjour library usage isn't going away anytime soon, so I made a small patch to avoid the warning altogether.

@michaelrsweet

This comment has been minimized.

Copy link
Collaborator Author

michaelrsweet commented Sep 6, 2008

CUPS.org User: mike

This is an Avahi bug. We will not add any workarounds for their broken compatibility layer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.