Comment 28 for bug 198884
Revision history for this message
| nine (niin-deactivatedaccount-deactivatedaccount) wrote | #28 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> I wonder if it might be something releated to the stdout
I've been thinking that also. Or stderr.
When gksudo was used to start wireshark, and the dumpcap -S -M process is being sent a SIGPIPE (13, broken pipe), dumpcap does not exit. When sudo was used, dumpcap does. So I reckon it could also have something to do with signal handling.
Maybe someone knowing Gtk programming can have a look at it?
I also noticed that there have been upstream changes around hidden -Z
dumpcap option ('capture_child mode'). These changes were in Februari 2008. See the upstream ChangeLog file. It might be related but also it might not.