Wireshark-bugs: [Wireshark-bugs] [Bug 11950] New: "...using this filter" turns white (not green
Date: Thu, 31 Dec 2015 23:49:37 +0000
| Bug ID | 11950 |
|---|---|
| Summary | "...using this filter" turns white (not green or red). Plus dropdown arrow does nothing. |
| Product | Wireshark |
| Version | 2.0.1 |
| Hardware | x86-64 |
| OS | Windows 7 |
| Status | CONFIRMED |
| Severity | Minor |
| Priority | Low |
| Component | Qt UI |
| Assignee | bugzilla-admin@wireshark.org |
| Reporter | asdf51020@gmail.com |
Created attachment 14194 [details] White field. Should be green or red, never white. Build Information: Version 2.0.1 (v2.0.1-0-g59ea380 from master-2.0) 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 Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia, with AirPcap. Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap. Intel(R) Xeon(R) CPU X5550 @ 2.67GHz, with 3071MB of physical memory. Built using Microsoft Visual C++ 12.0 build 31101 -- >From the homescreen, "...using this filter:" turns white (not green or red) as soon as you type a period (host 172.) If you type "host 172.16.0.1" and press enter, it creates a new capture with filter "host 172", which captures nothing. If you type "host 172.16.0.1", it turns white, but after you wait 20 seconds, it finally turns green. Once it turns green, and you start the capture it works just fine. It should be red for an invalid command and green for a valid command, never white. All employees are used to hitting enter right away. They now have to remember to wait 20 seconds to hit enter every single time. It is always red/green until you enter the first "." after the first octet. The issue seems to be only with this character. Also, the dropdown arrow all the way on the right of this field doesn't do anything at all. Never had these issues with the old 1.xx versions.
You are receiving this mail because:
- You are watching all bug changes.