Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upLibreOffice Calc opens as a tiny window #3281
Comments
andrewdavidwong
added
bug
C: desktop-linux-xfce4
UX
labels
Nov 5, 2017
andrewdavidwong
added this to the Release 3.2 updates milestone
Nov 5, 2017
andrewdavidwong
changed the title from
LibreOffice opens as a tiny window
to
LibreOffice Calc opens as a tiny window
Nov 5, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
donob4n
Feb 8, 2018
Here is someone experimenting same problem using wayland and working fine with Xorg: https://ask.libreoffice.org/en/question/143015/opening-window-size-using-wayland-fedora-27/
So probably the problem is something related with Qubes GUI and DUMMY screens. It seems hard to fix without modifying Libreoffice, I will try to investigate.
donob4n
commented
Feb 8, 2018
|
Here is someone experimenting same problem using wayland and working fine with Xorg: https://ask.libreoffice.org/en/question/143015/opening-window-size-using-wayland-fedora-27/ So probably the problem is something related with Qubes GUI and DUMMY screens. It seems hard to fix without modifying Libreoffice, I will try to investigate. |

andrewdavidwong commentedNov 5, 2017
•
edited
Edited 4 times
-
andrewdavidwong
edited Nov 5, 2017 (most recent)
-
andrewdavidwong
edited Nov 5, 2017
-
andrewdavidwong
edited Nov 5, 2017
-
andrewdavidwong
edited Nov 5, 2017
Qubes OS version:
R3.2Affected TemplateVMs:
fedora-25-minimalSteps to reproduce the behavior:
In Nautilus, double-click a LibreOffice Calc file (e.g.,
*.ods).Expected behavior:
Good: It opens to a sensible default size.
Best: It remembers the size at which you last closed it, and reopens to that size.
Actual behavior:
In most cases, it opens as a tiny window (small enough that the content of the file is not even visible).
General notes:
The behavior is not consistent. For example, I have two AppVMs based on the same template. In one of them, this problem doesn't exist. In the other one, this problem happens with
*.odsfiles every time. Even if I create a new AppVM based on the same template and copy the*.odsfiles there (from the problematic AppVM), the problem still occurs.