Bug 103598 - LibreOffice on Ubuntu: Menu and title bars messed up when maximize/minimize
Summary: LibreOffice on Ubuntu: Menu and title bars messed up when maximize/minimize
Status: RESOLVED DUPLICATE of bug 101952
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
5.2.2.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-31 11:03 UTC by MAS
Modified: 2016-10-31 12:51 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
LibreOffice on Ubuntu: Menu and title bars messed up when maximize/minimize (56.91 KB, image/png)
2016-10-31 11:03 UTC, MAS 		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 MAS 2016-10-31 11:03:53 UTC 
Created attachment 128378 [details]
LibreOffice on Ubuntu: Menu and title bars messed up when maximize/minimize

Steps to reproduce:

1. Launch Liber Writer or Calc on Ubuntu 16.04 

2. Create new file

3. Maximize the window 

4. Minimize the window 

5. Repeat 3 then 4

Result: Multiple title (and menu) bars overlap. Then it is very difficult to access the menus and recognise the boundaries of the working area.
Comment 1 MAS 2016-10-31 11:07:21 UTC 
Version: 5.2.2.2
Build ID: 1:5.2.2-0ubuntu1~xenial0
OS Version: Linux 4.4; UI Render: default;
Comment 2 Adolfo Jayme Barrientos 2016-10-31 11:55:21 UTC 
It doesn’t look like you’ve installed LibreOffice properly. For starters, you’re missing the “libreoffice-gtk” package; that’s why there’s no desktop integration. Could you please install that and try again?
Comment 3 MAS 2016-10-31 12:31:14 UTC 
Thanks,  Adolfo.

Installing libreoffice-gtk corrected the issue (I don't know why it was missing though).
Comment 4 Adolfo Jayme Barrientos 2016-10-31 12:45:05 UTC 
It could be due to a package management problem. Anyway, I’m glad you could solve this issue!
Comment 5 Maxim Monastirsky 2016-10-31 12:51:33 UTC 

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