Bug 121911 - Working in LibreOffice is not possible in portrait mode of monitor
Summary: Working in LibreOffice is not possible in portrait mode of monitor
Status: RESOLVED DUPLICATE of bug 116290
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.1.2.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-04 19:37 UTC by Alexander Kallenbach
Modified: 2019-01-15 02:04 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
screenshot (1.53 MB, image/png)
2018-12-04 19:38 UTC, Alexander Kallenbach
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kallenbach 2018-12-04 19:37:25 UTC
Description:
I've turned my screen around to work in portrait mode. Sadly LibreOffice which has been maximized came out of this mode. I'm not able to use LibreOffice in a maximized window. The window didn't fit into the screen and therefore it isn't possible to work with LibreOffice in portrait mode. I'll attach a screenshot to clarify what I mean.

I'm on a machine running Ubuntu 18.10. My screen has a resolution set to 2550*1440, scaling is set to 200% (sadly it isn't possible to set scaling to 150%).

I've already created a bugreport on launchpad: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1806292?comments=all

Steps to Reproduce:
1. Open LibreOffice
2. Turn your laptop to use it in portrait mode

Actual Results:
Maximized window isn't possible. Window doesn't fit to screen. Effective working not possible.

Expected Results:
Maximizing is possible even in portrait mode.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Comment 1 Alexander Kallenbach 2018-12-04 19:38:44 UTC
Created attachment 147290 [details]
screenshot
Comment 2 Adolfo Jayme Barrientos 2019-01-15 02:04:07 UTC
This should be fixed in the next version

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