https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1740
James Westby <jw+debian@xxxxxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jw+debian@xxxxxxxxxxxxxxx
--- Comment #2 from James Westby <jw+debian@xxxxxxxxxxxxxxx> 2008-10-09 07:47:07 PDT ---
Hi,
Sergio Barjola did some more debugging on this issue, and
found the following,
looking at the process: gksudo---wireshark---dumpcap
I've found that gksudo is ignoring SIGPIPE signal, (ps -eo pid,ignored), so all
childs process too, unless they change with sigaction.
Enable default action of SIGPIPE before gksudo create the child process works
for me. (libgksu.c line 2506).
I've looking for why is SIGPIPE ignored in gksu process, and I found that it's
caused by communication with gconfd server.
When a application connect to the gconfd daemon to get properties, the
underlaying communication with CORBA it's ignoring SIGPIPE signal to avoid that
if server crash, the process receive the signal and terminate.
package: liborbit2 1:2.14.12-0.1
file: linc2/src/linc.c (line: 247 see comment why is signal ignored)..
He came up with a patch to make wireshark work again, by enabling
the default action for SIGPIPE. I attach the patch here for your
review.
Thanks,
James
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
