Bug 37644 - [EDITING] Insert Special Character dialog opens off-screen
Summary: [EDITING] Insert Special Character dialog opens off-screen
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-26 13:21 UTC by Adam Thompson
Modified: 2012-08-31 10:04 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Thompson 2011-05-26 13:21:30 UTC
Choosing Insert->Special Character causes LibO Writer to hang.  Reproducible on a blank document, doesn't seem to matter what (if anything) is open.
No concomitant disk activity, no correlated CPU activity, just... non-responsive.

Oddly, Windows does *not* flag the application as "Not Responding", so the main event thread is still running.  It is not, however, possible, to exit LibO Writer except by killing the process.  File recovery works perfectly upon restart (so far).

I have no idea what other information might be needed to track this down, sorry - ask, and I shall attempt to deliver.

(N.B. inserting the character manually via the Windows keypad method works fine.)
Comment 1 Adam Thompson 2011-05-26 15:00:59 UTC
I just discovered (the hard way :-) that the identical behaviour occurs when clicking on the "..." button in the "Edit Footnote" dialog, to select a custom footnote character.
Comment 2 Adam Thompson 2011-05-26 15:04:25 UTC
Oops.
Well, this is still a major bug, it's just not what I thought it was.

The dialog window does open up and work properly, but it opens up offscreen.  Thus, it *appears* that LibO has sort-of hung.  I guess I never tried hitting ESC...

New bug to describe the actual problem coming right up :-).
Comment 3 Adam Thompson 2011-05-26 15:10:54 UTC
(Changed this bug instead of opening a new one, since I still can.)

I can also specify one possible reason this is happening to me: I regularly change monitor configurations.  At home, I have an irregular desktop geometry: one 1200x1920 (portrait-mode) monitor, one 1280x800 monitor [laptop display] on the right, aligned to the bottom of the large display.
At one office I visit frequently, I have the 1280x800 display to the left, aligned to roughly the middle of a 1280x1024 display.
If that dialog window remembers its previous position from when it was open on the right-hand 1280x1024 display, when I come back home it might re-open in the empty top-right quadrant where I have no display.
It's also possible it's opening with one pixel displayed along the edge of one of the monitors; if so, I can't see it.
The only way I could regain control of the dialog was to use Alt+Space and select the Move menu option...
Comment 4 Adam Thompson 2011-05-26 15:21:00 UTC
Confirmed that the identical behaviour exists for File->Export As PDF, and also confirming that the window is NOT visible on screen at all - not even one pixel.
Comment 5 Björn Michaelsen 2011-12-23 12:03:53 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 6 sasha.libreoffice 2012-02-29 03:04:20 UTC
Thanks for bugreport. And I have some questions:
It reproducible in version 3.5 of LibreOffice?
It reproducible only on Windows?
Which version of Windows used?
Comment 7 Adam Thompson 2012-02-29 10:09:14 UTC
I experienced this bug in 3.3.2, I've barely used 3.5 at all so don't know if it still occurs.
The bug occurred under Windows 7 x64 Professional.
I haven't tried under any other OS.
And I also don't have such an irregular monitor configuration anymore, nor do I change layout all that often now, so I can't provide much more info at this point.
Comment 8 Florian Reisinger 2012-08-14 13:58:38 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 9 Florian Reisinger 2012-08-14 13:59:54 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 10 Florian Reisinger 2012-08-14 14:04:32 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 11 Florian Reisinger 2012-08-14 14:06:42 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian