"gksu wireshark -k -i eth0" doesn't start automatically the capture

Bug #284573 reported by liquidator87
Affects Status Importance Assigned to Milestone
gksu (Ubuntu)

Bug Description

Binary package hint: wireshark

As the title says,

"gksu wireshark -k -i eth0" should start automatically the capture, but it doesn't, you need to manually start it.

Note that "sudo wireshark -k -i eth0" from CLI works good.

James Westby (james-w)
Changed in wireshark:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Soum (das-soumyadipta) wrote :

Just executing "gksu" without the rest of the above command and then putting, "wireshark -k -i eth0" in the small window that appears, works.

Revision history for this message
Evan Huus (eapache) wrote :

Still present in Oneiric.

When I try the gksu line in a terminal, I get the following error:

g_dbus_connection_real_closed: Remote peer vanished with error: Error sending message: Broken pipe (g-io-error-quark, 0). Exiting.

For what it's worth, running wireshark as root isn't recommended for security reasons. For a more complete discussion, please see bug #513903

Revision history for this message
Balint Reczey (rbalint) wrote :

This issue is still present in Xenial, but it is most likely a gksu issue.

affects: wireshark (Ubuntu) → gksu (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.