Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 553] Menu and Title bars inaccessible using GTK2 (non-lega

Date: Thu, 4 Oct 2012 10:57:28 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=553

--- Comment #46 from kproth@xxxxxxxxxxxxxxxxxxxxx 2012-10-04 10:57:27 PDT ---
(In reply to comment #45)
> But then again, if you change screen layouts so that there's some dead space,
> this program happily opens with its x0,y0 within the dead space, which would
> seem to indicate that there actually is no bug here at all, if we were to go by
> that.

But what if, instead of *changing* the screen layouts in between sessions of
word, you *start* with the dead space and see if you can get word to open with
the menu/ribbon hiding in the dead space?  My recollection of this issue was
that wireshark would open in the deadspace either on the first callup of the
app, or at least after moving the window onto that monitor and closing it.  I
doubt word does this.

-- 
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.