Wireshark-bugs: [Wireshark-bugs] [Bug 11176] New: Refresh interface during live-capture leads to
| Bug ID |
11176
|
| Summary |
Refresh interface during live-capture leads to corrupt interface handling
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86
|
| OS |
Ubuntu
|
| Status |
UNCONFIRMED
|
| Severity |
Trivial
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
rknall@gmail.com
|
Build Information:
Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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 libpcap, with POSIX capabilities (Linux), without libnl,
with libz 1.2.8, with GLib 2.40.2, with SMI 0.4.8, with c-ares 1.10.0, with Lua
5.2, with GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP.
Running on Linux 3.14.22-031422-generic, with locale de_DE.UTF-8, with libpcap
version 1.5.3, with libz 1.2.8, with GnuTLS 2.12.23, with Gcrypt 1.5.3.
Intel(R) Core(TM) i7-3615QE CPU @ 2.30GHz (with SSE4.2)
Built using gcc 4.8.2.
--
This bug is applicable to both the GTK and the Qt interface, but both handle it
differently.
To reproduce, follow these steps:
1. Start a live capture
2. Click during the live capture on "Capture->Refresh interfaces"
3. Observe, that the capture keeps going and is not interrupted (this is
actually ok, and makes sense).
4. Restart the capture via the button in the menubar:
In Qt step 4 leads to "No interface selected", packets remain
In Gtk step 4 leads to a restart of the capture, but no packets will be
captured, additionally, the "Start Capture" button is not accessible.
Should the menuitem for Restarting the capture really be accessible during a
live-capture? Because, that would be the easy fix, to just disable the menuitem
during a live-capture and reenable it once the capture-file is closed.
You are receiving this mail because:
- You are watching all bug changes.
