Wireshark-bugs: [Wireshark-bugs] [Bug 12533] New: Ctrl+ shortcuts that are not text-related do n
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 15 Jun 2016 19:01:38 +0000
Bug ID 12533
Summary Ctrl+ shortcuts that are not text-related do not work when focus is on display filter field
Product Wireshark
Version 2.0.4
Hardware x86-64
OS Windows 10
Status UNCONFIRMED
Severity Normal
Priority Low
Component GTK+ UI
Assignee bugzilla-admin@wireshark.org
Reporter mromans@gmail.com 

Build Information:
Wireshark 2.0.4 (v2.0.4-0-gdd7746e from master-2.0)

Copyright 1998-2016 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.11.0, 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 10, build 10586, 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) Core(TM) i5-4300U CPU @ 1.90GHz (with SSE4.2), with 8089MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 40629
--
The only ctrl+ shortcuts that work from within the display filter field are
those that apply to the text in the field. (ctrl+a, ctrl+c, ctrl+x, etc.)

Program-related shortcuts (like ctrl+o, ctrp+p, etc.) do not work when there is
a text cursor in that field. (I have not checked other fields to see if the
problem exists there as well.)

With other programs (i.e., Chrome), I can hit "ctrl+o" or "ctrl+p" from within
fields, so I would expect Wireshark to function the same as well.

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