Wireshark-bugs: [Wireshark-bugs] [Bug 11033] New: Some problems with the "Filter:" input field

Date: Sat, 07 Mar 2015 11:01:08 +0000
Bug ID 11033
Summary Some problems with the "Filter:" input field
Product Wireshark
Version 1.12.1
Hardware x86-64
OS Ubuntu
Status UNCONFIRMED
Severity Normal
Priority Low
Component GTK+ UI
Assignee [email protected]
Reporter [email protected]

Build Information:
wireshark 1.12.1 (Git Rev Unknown from unknown)

Copyright 1998-2014 Gerald Combs <[email protected]> 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 (64-bit) with GTK+ 3.14.7, with Cairo 1.14.0, with Pango 1.36.8, with
GLib 2.43.3, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
with libnl 3, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without Python,
with GnuTLS 3.3.8, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Feb 25 2014 21:09:53), without AirPcap.

Running on Linux 3.19.0-7-generic, with locale C, with libpcap version 1.6.2,
with libz 1.2.8, GnuTLS 3.3.8, Gcrypt 1.6.2.
AMD Phenom(tm) II X6 1045T Processor

Built using gcc 4.9.2.
--
I'm noticing some problems with the "Filter:" input field:

- If I'm selecting text the selection is not visible (the cursor stops blinking
but the background color of the selected text is the same as without any
selection).
- CTRL + C and CTRL + X does delete the selected text without copying/cutting
it.
- Typing something in the "Filter:" input field and choosing one of the
suggestions from the appearing list requires a double click while choosing a
recently used filter needs only a single click (entries in the suggestion list
from the "Filter string:" input field in the "Display Filter" dialog (if
"Filter:" is clicked) are even not clickable).
- A few seconds after typing something in the "Filter:" input field the cursor
gets stuck (instead of blinking it is permanently visible).


You are receiving this mail because:
  • You are watching all bug changes.