| Bug ID |
11437
|
| Summary |
Button clicks and mouseover events fail randomly
|
| Product |
Wireshark
|
| Version |
1.12.6
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.12.6 (v1.12.6-0-gee1fce6 from master-1.12)
Copyright 1998-2015 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+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Jun 17 2015),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, with 32710MB of physical memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Button clicks on the top toolbars and throughout the interface simply don't
work half the time. Often I have to double-click (click twice, even slowly) to
get buttons to respond. Other times I completely lose the ability to click
certain UI elements.
Mouseover events have problems too. When the bug happens, hovering over toolbar
buttons causes no change in appearance; normally a border appears when you
hover over a button. If I click a menu item and it appears, hovering to other
menus does not change to those menus as expected in normal Windows behavior.
Normally when I start Wireshark, everything works right immediately. The above
symptoms may appear after the first or second click, or even a few seconds
later. Nonetheless, the UI starts getting "numb" as I am calling it very soon
after startup.
I'm willing to bet this is a GTK+ problem, but I haven't been able to find
anything about a GTK+ bug report that describes it, nor have I experienced it
in any other GTK+ app in Windows, so I'm reporting it specifically concerning
Wireshark.
Please let me know if there are any other debugging steps to take. Thanks!
You are receiving this mail because:
- You are watching all bug changes.