Issue 102944 - Dialog opens in second (non existing) monitor.
Summary: Dialog opens in second (non existing) monitor.
Status: CLOSED DUPLICATE of issue 42282
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 3.1
Hardware: PC (x86_64) Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-19 11:47 UTC by stockfeltm
Modified: 2009-06-19 12:13 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description stockfeltm 2009-06-19 11:47:47 UTC 
I just moved my workstation - using OpenOffice 3.01 and Windows XP64 - from one
location to another and in the process also changed from a dual monitor setup to
a single monitor setup. Aside from that and the mouse, all else are being equal.

Only now when I double-click an image in OOo Writer to change its properties, no
menu window appears and OOo freezes. Until I hit Esc, then it goes back to normal.

I tried rebooting the computer and I tried upgrading to OOo 3.1, no change. I am
guessing it might be related to which monitor is "primary" or something - it
might be the case that OOo tries to open the window on a nonexistant display -
but I am just guessing.

I intended to work at home over the weekend to meet a deadline on monday, so
this was kind of a letdown.
Comment 1 eric.savary 2009-06-19 12:06:59 UTC 
So no freeze because you can get control over the program again by pressing Esc.
= no P2.

As you describe the problem, it seems that the system still expects a second
monitor so you should check your graphic device settings.

The same should also appear in other software as OOo. So that this issue is
probably invalid.

At least seems to be (if only OOo related) a framework problem.
Comment 2 Olaf Felka 2009-06-19 12:13:31 UTC 
known issue

*** This issue has been marked as a duplicate of 42282 ***
Comment 3 Olaf Felka 2009-06-19 12:13:55 UTC 
duplicate