| Bug ID |
12715
|
| Summary |
"Restart current capture" button
|
| Product |
Wireshark
|
| Version |
2.0.4
|
| Hardware |
x86
|
| OS |
Ubuntu
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 2.0.4
Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (64-bit) with Qt 5.5.1, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with libz 1.2.8, with GLib 2.48.0, with SMI 0.4.8, with c-ares
1.10.0, with Lua 5.2, with GnuTLS 3.4.10, with Gcrypt 1.6.5, with MIT Kerberos,
with GeoIP, with QtMultimedia, without AirPcap.
Running on Linux 4.4.0-31-generic, with locale C, with libpcap version 1.7.4,
with libz 1.2.8, with GnuTLS 3.4.10, with Gcrypt 1.6.5.
Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz
Built using gcc 5.3.1 20160413.
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Pressing "Restart current capture" toolbar button (green fin) only stops
capture, it does not clear previous captured frames and restart.
This bug only manifests if you are using a capture filter like "host
192.168.2.2". If no capture filter is used, no bug. The display filter is
irrelevant, only the capture filter.
After pressing this button, the only option is to "Close this capture file",
press "Continue without saving" and select interface again and restart the
trace, either by double clicking the interface or using enter or using the blue
fin button.
Please not that after selecting "Restart current capture", the "Start capturing
packets" button (blue fin) does not work either although it is not greyed.
This was first seen in version 2.0.1 and also happens in 2.0.4 (updated from
wireshark debian repository).
You are receiving this mail because:
- You are watching all bug changes.
