Bug 151004 - When closed in maximized state LibO 7.4 applications are then reopened with windows that are as small as possible (kf5 only)
Summary: When closed in maximized state LibO 7.4 applications are then reopened with w...
Status: RESOLVED DUPLICATE of bug 150856
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.4.1.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: KDE, KF5
  Show dependency treegraph
 
Reported: 2022-09-16 15:55 UTC by Callegar
Modified: 2022-09-18 22:59 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Callegar 2022-09-16 15:55:30 UTC
Description:
This is a very weird issue, that does not happen with LibO 7.3 and that I am observing with a linux KDE plasma desktop under X11.

If you open a libreoffice application (say calc), then maximize it, then close it, when you open the same application again the application window is made as small as possible. For writer, calc, this means an almost invisible window. You need to go to the application in the taskbar, right click, click "more" and from there resize or maximize again the window to make it visible.

Conversely, if you open a libreoffice app (again, say calc), then resize it to some size (not the maximum one!), close the application and launch it again, then the window is reopened at the same size it had when it was closed, that seems totally reasonable.

The issue has already been reported to the Kwin developers (https://bugs.kde.org/show_bug.cgi?id=459107), but the fact that LibO 7.3.x does not show the issue is strange and points towards the application rather than the window environment. The KDE developers say "It's actually quite possible as KWin respects the size that an app says it wants its window to open with. So it seems like that may have changed between 7.3 and 7.4."

I am seeing this on ubuntu 22.04 (in fact kubuntu) using LibO 7.4.1.2 based on the Document Fundation DEB packages.

Steps to Reproduce:
See above

Actual Results:
See above

Expected Results:
See above


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.4.1.2 / LibreOffice Community
Build ID: 3c58a8f3a960df8bc8fd77b461821e42c061c5f0
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: it-IT (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 Rafael Lima 2022-09-16 19:30:42 UTC
I started having this problem right after the update to LibreOffice 7.4.1 in KDE Plasma (Kubuntu 22.04). It seems that some setting in the user profile is causing the window to have a minimal size and be located at the top-left side of the screen.

If you manually resize the window and close the application (f.i. Writer), and then open it again, the previous size will be remembered.

But if you maximize the window and then close it, the next time you open Writer it will be again in a minuscule size at the top-left corner of the screen.

Can you confirm that this is what you're experiencing?

My system info:

Version: 7.4.1.2 / LibreOffice Community
Build ID: 40(Build:2)
CPU threads: 16; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Ubuntu package version: 1:7.4.1~rc2-0ubuntu0.22.04.1~lo1
Calc: threaded

Interestingly, this issue is not happening with the master build (7.5 alpha) that I have installed in the same machine.

This may be a kf5-only bug.
Comment 2 Rafael Lima 2022-09-16 19:35:22 UTC
Now that I read again your ticket, as well as the KDE ticket, I see that it is the same issue.

I'm setting this to NEW and marking it as kf5-only.

However, I feel this may be Kwin to blame?
Comment 3 Michael Weghorn 2022-09-17 07:49:05 UTC
(In reply to Rafael Lima from comment #2)
> However, I feel this may be Kwin to blame?

No, it's a LO issue, fixed in 7.4.2.

*** This bug has been marked as a duplicate of bug 150856 ***
Comment 4 Rafael Lima 2022-09-18 22:59:45 UTC
*** Bug 151038 has been marked as a duplicate of this bug. ***