Bug 139200

Summary: A large part of the window may appear off-screen if the monitor/screen config has changed
Product: LibreOffice Reporter: Vincent Lefevre <vincent-docf>
Component: UIAssignee: Not Assigned <libreoffice-bugs>
Status: UNCONFIRMED ---    
Severity: minor    
Priority: low    
Version: 7.0.4.2 release   
Hardware: All   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Bug Depends on:    
Bug Blocks: 104160    

Description Vincent Lefevre 2020-12-24 00:17:08 UTC
It seems that LibreOffice applications remember the position and size of windows after restart, but do not remember the screen definition. The consequence is that if the screen has changed (which is common with a laptop that sometimes has an external monitor attached) and has a smaller definition, then a large part of the document window may appear off-screen. I had this issue, where the top, the bottom, the left and the right parts of the window were all off-screen, meaning that I could not do anything to be able to move or resize the window (all window controls were off-screen, and the menu and toolbar of the LibreOffice application were not accessible either). The only thing I could do was to remove the config directory (~/.config/libreoffice).
Comment 1 Timur 2020-12-24 16:59:28 UTC Comment hidden (obsolete)
Comment 2 Vincent Lefevre 2020-12-24 22:22:29 UTC
Currently I can't test to reproduce with a change of screen definition, but I believe that the following steps will trigger the issue:

1. On a machine with a high-definition screen connected, run "libreoffice".
2. Maximize the window (to have a better chance to reproduce the issue).
3. Quit LibreOffice.
4. Log out and switch off the machine.
5. Connect a screen with a lower definition (for a laptop, it could just be the laptop screen, with no external monitor attached).
6. Boot and log in.
7. Run "libreoffice".

I suppose that LibreOffice doesn't detect the change of screen definition and uses the same window size, which doesn't fit in the screen after the change of monitor.

Actually, I could do a test by artificially resizing a window to make it larger than the current screen definition, but I don't know whether this test is significant or just too artificial (I just have my laptop with its 3200x1800 screen, and no external monitors here, so that I cannot test a change of the screen definition). In case this matters, my window manager is FVWM.

Window before quitting LibreOffice:

xwininfo: Window id: 0x5a0007d "LibreOffice"

  Absolute upper-left X:  69
  Absolute upper-left Y:  104
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 4758
  Height: 2770
  Depth: 24
  Visual: 0x2b
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x5a00002 (installed)
  Bit Gravity State: NorthWestGravity
  Window Gravity State: StaticGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +69+104  --1627+104  --1627--1074  +69--1074
  -geometry 4758x2770+69+104

Window obtained after quitting and restarting LibreOffice:

xwininfo: Window id: 0x5a0007d "LibreOffice"

  Absolute upper-left X:  -1559
  Absolute upper-left Y:  -959
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 4758
  Height: 2770
  Depth: 24
  Visual: 0x2b
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x5a00002 (installed)
  Bit Gravity State: NorthWestGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +-1559+-959  -1+-959  -1--11  +-1559--11
  -geometry 4758x2770-1--11

What is surprising is that the position has changed completely, with large parts in the negatives, which makes them completely inaccessible. I think this is what makes  this bug worse: in addition to the issue that the window doesn't fit in the screen after a change of monitor, the new startup position also makes the window hardly controllable.

I couldn't find an existing bug with the same or a similar issue.
Comment 3 QA Administrators 2020-12-25 03:53:34 UTC Comment hidden (obsolete)