Wireshark-bugs: [Wireshark-bugs] [Bug 3292] New: Wireshark GUI opens in a non-existent monitor l
Date: Sat, 28 Feb 2009 19:08:13 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3292 Summary: Wireshark GUI opens in a non-existent monitor location Product: Wireshark Version: unspecified Platform: PC URL: http://asiapac.com.au/ OS/Version: Windows XP Status: NEW Severity: Normal Priority: Low Component: Wireshark AssignedTo: wireshark-bugs@xxxxxxxxxxxxx ReportedBy: wireshark.org@xxxxxxxxxxxxxx Tony Austin <wireshark.org@xxxxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #2791| |review_for_checkin? Flag| | Created an attachment (id=2791) --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=2791) Default opening location of Wireshark (in non-existent monitor) Build Information: Version 1.0.6 (SVN Rev 27387) -- I am using Windows XP Pro (SP2). I've assigned this a "normal" priority, since it is irritating but not a showstopper. I happen to have a somewhat unusual arrangement of four LCD monitors, each 1600x1200 resolution and arranged in an inverted-T configuration (three monitors in a horizontal row, and one above the central monitor). Whenever I start Wireshark I can see an entry in the Windows task bar, but not on any of the four LCD monitors. After a bit of sleuth work, I found that Wireshark places its GUI in the non-existent top left monitor. I can only see the GUI if: (A) I right-click the task bar icon and select "Maximize" or (B) I use the Windows Properties/Settings panel to drag the bottom left monitor vertically upwards until the Wireshark GUI appears (after which I can drag the Wireshark GUI to the central bottom monitor). It is only when I selected "Save window position" under preferences that Wireshark would restart in one of the four real monitors. (Otherwise it would keep restarting in the op left non-existent monitor position.) Now that I've found the preference setting, it doesn't worry me too much, but thought it was worth reporting since it's obvious this is a classy bit of software and thought you'd want to correct this little quirk. A tricky one, this, and I wish you good luck in sorting it out. Cheers, Tony. CEO, Asia/Pacific Computer Services -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
- Prev by Date: [Wireshark-bugs] [Bug 3251] Launch Error Message
- Next by Date: [Wireshark-bugs] [Bug 3288] Wireshark is not filtering wireless packets based on wlan.qos.eosp filter
- Previous by thread: [Wireshark-bugs] [Bug 3216] mysql : fix for "FIXME: write mysql_dissect_row_packet()"
- Index(es):
- Get Wireshark
- Download
- Code of Conduct