Wireshark-bugs: [Wireshark-bugs] [Bug 553] Menu and Title bars inaccessible using GTK2 (non-lega
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553
--- Comment #53 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2012-10-05 10:03:51 PDT ---
(In reply to comment #51)
> Comment on attachment 9274 [details]
> Ensure window's x0,y0 is within the viewable area.
>
> Committed in r45331. Can someone with multiple monitor setup on Windows test
> with a recent automated version of at least 45331?
> http://www.wireshark.org/download/automated/
By the way, I should point out that while there was clearly a bug here, this
patch only fixed the problem with needlessly repositioning the visible window
if it appeared on a screen in which that screen's x,y was something other than
0,0. I actually could not reproduce this bug - either before or after this
patch was applied. If someone can reproduce it even after this latest patch,
then screen shots are only so useful. Please include the exact steps taken in
order to reproduce it.
And if this bug truly is fixed, then I tend to think that it's probably due to
upgrading to a newer version of GTK+ than anything to do with my patch. For
future reference, here's my current build information:
Version 1.9.0 (SVN Rev 45332 from /trunk)
Compiled (32-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Sep 24 2012), with AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, with AirPcap 4.1.1 build 1838.
Built using Microsoft Visual C++ 10.0 build 40219
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
