LibreOffice on Fedora/Debian AppVM: Minimized Window and Lagging

apparatus · October 6, 2024, 11:10am

It’s a known issue:

Editing cells in LibreOffice calc is laggy

opened 02:59PM - 20 Jun 23 UTC

T: bug C: templates P: default needs diagnosis affects-4.1

[How to file a helpful issue](https://www.qubes-os.org/doc/issue-tracking/) #…## Qubes OS release R4.1 ### Brief summary Editing spreadsheet cell directly in the cell has noticeable lag between keypress and showing the effect. Edit field above the spreadsheet doesn't have this problem. ### Steps to reproduce 1. Open LibreOffice Calc 2. Create new spreadsheet 3. Click any cell 4. Enter some characters ### Expected behavior They appear immediately. ### Actual behavior They appear with noticeable (but small) delay. Editing cell by clicking on it and then clicking on the edit field at the top doesn't have this issue. The issue happens at least in Fedora 37 (libreoffice-7.4.6.2-2.fc37.x86_64) and Ubuntu 22.04 (libreoffice 1:7.3.7-0ubuntu0.22.04.3) templates. I have _not_ verified how it behave outside of Qubes (might be a good first step in diagnosis).

You can try to use the fix with kf5 from there or this fix:

I guess it’s this issue:

github.com/QubesOS/qubes-issues

Some programs (especially LibreOffice) open as tiny windows

opened 12:10AM - 05 Nov 17 UTC

closed 11:15AM - 30 Nov 21 UTC

andrewdavidwong

T: bug P: major ux C: desktop-linux-xfce4 R: upstream issue

#### Qubes OS version:  `R3.2` #### Affected TemplateVMs:  `fedora-25-minimal` --- ### Steps 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 `*.ods` files every time. Even if I create a new AppVM based on the same template and copy the `*.ods` files there (from the problematic AppVM), the problem still occurs.

You can try a fix from there.