Bug 115151 - MacBook Pro Screen truncation
Summary: MacBook Pro Screen truncation
Status: RESOLVED DUPLICATE of bug 114985
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.7.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-22 14:44 UTC by Tim Burns
Modified: 2018-01-22 15:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Help screen truncation (also seen in other dialogs) (189.37 KB, image/png)
2018-01-22 15:11 UTC, Tim Burns
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Burns 2018-01-22 14:44:06 UTC
Description:
I have seen evidence on my Mac Book Pro of screen artefacts being truncated. I have done a reinstall (using AppCleaner to do it deep) and still find this occurring, particularly in Help.

Steps to Reproduce:
1.Launch LO
2.Launch Help
3.

Actual Results:  
As you can see, the top filed is off the screen. I have seen this in other dialogs as well - I have witnessed the top row of icons in Writer being "off the screen" - reinstall seems to have cleared that

Expected Results:
Everything is visible and fields can accept input 


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Safe Mode reset did not clear this

Version: 5.4.4.2
Build ID: 2524958677847fb3bb44820e40380acbe820f960
CPU threads: 8; OS: Mac OS X 10.13.2; UI render: default; 
Locale: en-GB (en_GB.UTF-8); Calc: group


User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/604.4.7 (KHTML, like Gecko) Version/11.0.2 Safari/604.4.7
Comment 1 Xisco Faulí 2018-01-22 15:05:59 UTC
Could you please attach a screenshot ?
Comment 2 Tim Burns 2018-01-22 15:11:33 UTC
Created attachment 139262 [details]
Help screen truncation (also seen in other dialogs)
Comment 3 Xisco Faulí 2018-01-22 15:15:55 UTC
This is because the tab is displayed. Dupe of bug 114985
It will be fixed soon. Thanks for reporting it!

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