Bug 114079

Summary: Application window is higher then the screen and minimize/maximize functions stop to work, starting from the moment when an edited file is closed.
Product: LibreOffice Reporter: Nimrod <nimrodlaszlo>
Component: UIAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: enhancement CC: suokunlong, xiscofauli
Priority: medium    
Version: 5.1.6.2 release   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Nimrod 2017-11-26 23:26:01 UTC 
Description:
Bottom toolbars, zoom pane, etc. are off screen nnd window resize functionality is not available on Acer Aspire ONE - N450 laptop.

The screen resolution  does not meat the minimum requirements, but pleas read the report to enable the wider usage of LibreOffice.

Steps to Reproduce:
On a 1024x600 resolution screen:

1. Open LibreOffice Writer, or a *.odt file.
2. Colse the file, not Writer, using Ctrl+W, or the GUI (x)
3. Done.

Or:

1. Open LibreOffice from Menu > Libreoffice
2. Done.

Actual Results:  

1. The LibreOffice main app is larger then 600px, and the [Help] and [Extensions] buttons are offscreen.

2. The minimize maximize functions break completely.

Expected Results:
Functional minimize/maximize button on the GUI, and visible bottom toolbars when a new text document is created, 


Reproducible: Always


User Profile Reset: No



Additional Info:
Only by reducing the font size in the main app screen the unwante behaviour should be solved. Nothing else should be done.

The event itself cannot be considered a bug, because the minimum requirements are not met. The problem is that the app window size functionality breaks completely and will not restore even if the app fits in the screen. Therefore the only suspected reason behind this unwanted behaviour is the main screen size of LibreOffice, and not any bug nor problem in the applications, not in Writer nor in any other office app. Opening them on their own results in a 100% functional app even on 600px height.

Workaround:
1. Open a file directly, or
2. Close app, and go to step 1, or
3. Open specific app, eg: Writer or Calc directlys


User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36
Comment 1 Xisco Faulí 2017-11-27 10:08:42 UTC 
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone
else confirms it.
Comment 2 Nimrod 2017-11-27 11:01:38 UTC 
Sorry, I did not understand the options. 'New' was not equal to 'confirmed' in my vocabulary. This is my first report.
Comment 3 Kevin Suo 2017-11-27 11:37:35 UTC 
 Nimrod: Would you please copy paste the information on Help - About Libreoffice.
Comment 4 Kevin Suo 2017-11-27 11:38:50 UTC 
And also provide you Linux distribution name and version.
Comment 5 Nimrod 2017-11-28 16:15:59 UTC 
Sorry for the late response.
Here is the requested information:

LibreOffice:

Version: 5.1.6.2
Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2
CPU Threads: 2; OS Version: Linux 4.8; UI Render: default; 
Locale: en-US (en_US.UTF-8); Calc: group

Linux:

Release Linux Mint 18.2 Sonya 64-bit
Kernel Linux 4.8.0-53-generic x86_64
MATE 1.18.0

Memory: 981,1 MiB
Processor: Intel Atom 450 @ 1.66GHz x 2

Thank you for reviewing the case.
Comment 6 Kevin Suo 2017-11-28 23:11:27 UTC 
(In reply to Nimrod from comment #5)
Please  upgrade  to a most recent Libreoffice version to see if the  bug  is still there. The most recent Still version is 5.3.7.2, and the most  recent Fresh version is 5.4.3.2.

If the bug is still reproducible in the newest version, please set the Status field of this bug back to UNCONFIRMED.
Comment 7 Nimrod 2017-12-04 08:16:39 UTC 
(In reply to Kevin Suo from comment #6)

I manually installed LibreOffice_5.4.3.2_Linux_x86-64_deb from the website,
copied from help:

  Version: 5.4.3.2
  Build ID: 92a7159f7e4af62137622921e809f8546db437e5
  CPU threads: 2; OS: Linux 4.8; UI render: default; VCL: gtk2; 
  Locale: en-US (en_US.UTF-8); Calc: group

The main app is still off screen.  Setting it back to unconfirmed.
Comment 8 Maxim Monastirsky 2017-12-04 08:32:49 UTC 

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