Bug 111954 - The scale of the windows is off (things are cut off on all the edges).
Summary: The scale of the windows is off (things are cut off on all the edges).
Status: RESOLVED DUPLICATE of bug 107764
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.4.0.3 release
Hardware: All Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: VCL-OpenGL
  Show dependency tree / graph
 
Reported: 2017-08-22 03:44 UTC by law97010
Modified: 2017-09-26 08:44 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
scale issues - see how the edges are cut off, and the menu is missing. (124.91 KB, image/png)
2017-08-22 03:44 UTC, law97010 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description law97010 2017-08-22 03:44:55 UTC 
Created attachment 135714 [details]
scale issues - see how the edges are cut off, and the menu is missing.

The window has all the edges cut off.  I cannot see the menu, and the mouse does not point to the spot where the click is registered (it is one or two rows above where the mouse pointer is pointing.
Comment 1 Buovjaga 2017-09-02 13:49:24 UTC 
Maybe download and merge this registry fragment to make sure that it is not an OpenGL problem: https://bugs.documentfoundation.org/attachment.cgi?id=118060
Comment 2 Mark 2017-09-25 19:22:04 UTC 
Same behavior right here, Windows 10 on a 1920x1080 screen.
Registry setting to disable OpenGL worked for me.
Comment 3 Buovjaga 2017-09-26 07:48:52 UTC 
(In reply to Mark from comment #2)
> Same behavior right here, Windows 10 on a 1920x1080 screen.
> Registry setting to disable OpenGL worked for me.

Ok, interesting. Could you find this file, open it in a text editor and copy & paste the contents here to a comment: C:\Users\User\AppData\Roaming\LibreOffice\4\cache\opengl_device.log
Comment 4 Buovjaga 2017-09-26 08:44:35 UTC 
Ah, I realized there is already a report for this.

*** This bug has been marked as a duplicate of bug 107764 ***