In version 1.0.0 the "Capture Interfaces" Dialog freezes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Wireshark |
Fix Released
|
Critical
|
|||
wireshark (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: wireshark
To reproduce - in Ubuntu Hardy - start Wireshark as root, and then from the top menu, select "Capture." Now, pick "Interfaces" from the drop-down menu. The "Capture Interfaces" dialog opens as expected. The interfaces show captured packets counters as expected. However, you cannot successfully pick any of the option buttons such as "Start" or "Options" or even "Close". Picking any of those causes the entire application to freeze, and it must be dismissed from a root console.
I am using Ubuntu 8.04 and have taken every update offered for every installed application, including one that arrived today for Wireshark. I use Wireshark frequently, and although there is a simple workaround for this bug (you can start a capture form the "Options" dialog), the Capture Interfaces dialog is a handy part of Wireshark, and I would like to see it work properly.
$ lsb_release -rd
Description: Ubuntu 8.04.2
Release: 8.04
#######
Version 1.0.0
Copyright 1998-2008 Gerald Combs <email address hidden> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled with GTK+ 2.12.9, with GLib 2.16.3, with libpcap 0.9.8, with libz
1.2.3.3, with POSIX capabilities (Linux), with libpcre 7.4, without SMI, with
ADNS, with Lua 5.1, with GnuTLS 2.0.4, with Gcrypt 1.2.4, with MIT Kerberos,
with PortAudio V19-devel (built Mar 12 2008), without AirPcap.
Running on Linux 2.6.24-23-generic, with libpcap version 0.9.8.
Built using gcc 4.2.3 (Ubuntu 4.2.3-2ubuntu7).
Wireshark is Open Source Software released under the GNU General Public License.
Check the man page and http://
thanks
Changed in wireshark: | |
importance: | Unknown → Critical |
status: | Unknown → Fix Released |
Hi,
I'm on same environment. After little experimentation i found that launching wireshark with gksu causes this problem abd wireshark works fine if I launch it using "kdesu".
Thanks.
Mohsin Saleem