> 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.
--
Wireshark halts in Capture Interfaces window when started using gksu (Hardy,
Intrepid)
https://bugs.launchpad.net/bugs/198884
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
