Bug 135418 - When started LO runs out of screen
Summary: When started LO runs out of screen
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.1.0.0.alpha0+
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-03 16:34 UTC by paps
Modified: 2022-03-05 03:34 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Infos about LibreOffice (116.01 KB, image/jpeg)
2020-08-21 11:35 UTC, paps
Details
LO opens out of screen (131.68 KB, image/jpeg)
2020-08-26 12:34 UTC, paps
Details
LO opens correctly (151.15 KB, image/jpeg)
2020-08-26 12:38 UTC, paps
Details

Note You need to log in before you can comment on or make changes to this bug.
Description paps 2020-08-03 16:34:47 UTC
Hi all,
often when I start LO it "shows" menubar and toolbars out of screen. 
I must run "killall soffice.bin. 
After restart the position is correct, then after some close/open (there is no a fixed number) the out of screen is there again. 
Today I ran it from terminal and got this: 
(soffice:30157): Gtk-WARNING **: Allocating size to OOoFixed 0x26a9660 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

I use debian jessie. 99% I use calc. LO is called from an application launcher and sometimes is invoked via Midnight Commander facility (enter on the filename).

paps
Comment 1 Timur 2020-08-20 08:35:22 UTC Comment hidden (obsolete)
Comment 2 paps 2020-08-21 06:54:44 UTC Comment hidden (obsolete)
Comment 3 Timur 2020-08-21 08:18:02 UTC
When you report back, please paste system into from Help About.
Comment 4 paps 2020-08-21 11:35:02 UTC
Created attachment 164533 [details]
Infos about LibreOffice

In addition to this information: I use an external monitor (4: 3) and therefore I have to adapt the laptop screen (16: 9) to the laptop
Comment 5 paps 2020-08-21 11:40:56 UTC
Deleted the user profile, ran it and everything was ok. Next time I opened Calc it was out of screen
Comment 6 Timur 2020-08-21 16:44:55 UTC
(In reply to paps from comment #4)
> In addition to this information: I use an external monitor (4: 3) and
> therefore I have to adapt the laptop screen (16: 9) to the laptop

Next time, please follow the rules:
1. search for existing bugs 
2. use all relevant info, and that you have external monitor is important, not to add later 
3. if not found and you report, use New bug form that leads you and suggests to reset profile etc. 


This looks like a duplicate of https://bugs.documentfoundation.org/show_bug.cgi?id=120903
Comment 7 Timur 2020-08-21 16:52:09 UTC
There's also https://bugs.documentfoundation.org/show_bug.cgi?id=99521
Comment 8 paps 2020-08-26 12:34:37 UTC
Created attachment 164718 [details]
LO opens out of screen
Comment 9 paps 2020-08-26 12:38:44 UTC
Created attachment 164719 [details]
LO opens correctly
Comment 10 paps 2020-08-26 12:42:43 UTC
Thank you for the suggestions, will follow them.
If there are no problems I will continue this way otherwise, pls, close the bug and I will open another as suggested

Anyway, I checked the bug you wrote are duplicate. In my opinion "my bug" is different.

Trying to resume.
I have an external monitor connected via VGA cable to a laptop. Monitor is 4:3 while laptop screen is 16:9.
I use this command to obtain a correct image on the monitor:

xrandr --newmode "1400x1050_60.00"  121.75  1400 1488 1632 1864  1050 1053 1057 1089 -hsync +vsync
xrandr --addmode DP1 1400x1050_60.00
xrandr --output DP1 --mode 1400x1050_60.00

All applications I use (browsers, email, games, programming, and so on) always open inside the screen of the monitor.
LO sometimes open as shown in attachment "LO opens out of screen"

Then I run killall soffice.bin, restart LO and it opens as shown in attachment "LO opens correctly"

Note: once LO opens out of screen all other occurences of LO opens out of screen 
until I dont kill soffice.bin
Comment 11 paps 2020-08-26 12:46:25 UTC
Sorry, forgot to say that even the laptop screen changes "dimension" according to the xrandr command
Comment 12 QA Administrators 2020-08-27 03:52:46 UTC Comment hidden (obsolete)
Comment 13 Buovjaga 2021-03-31 14:33:47 UTC
Which desktop environment / window manager are you using?
Comment 14 Dmitriy Siushkin 2021-07-27 10:49:41 UTC
no repro in

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: c5ca46e75e28ba4245d8544ca53c71fea87d1bbd
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: en-US (ru_RU); UI: en-US
Calc: CL
Comment 15 Natali Eroshenko 2021-08-04 14:21:13 UTC
no repro in Version: 7.1.5.2 (x64) / LibreOffice Community
Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5
CPU threads: 6; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win
Locale: en-US (ru_RU); UI: en-US
Calc: threaded
Comment 16 Timur 2021-08-05 11:20:37 UTC
Dmitriy and Natali: while it's useful to know that you don't repro in Win, bug is Linux, so please test if you can and have external monitor. 
Also, please always test reporter's LO version and master LO.

I still set Needinfo for Comment 13.
Comment 17 QA Administrators 2022-02-02 03:40:38 UTC Comment hidden (obsolete)
Comment 18 QA Administrators 2022-03-05 03:33:59 UTC
Dear paps,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp