LibreOffice on Fedora 41 lags and is sometimes unresponsive

User Support
21 
Screen 0: swrast
22

That means software rendering. It would explain, why scrolling etc. is rather slow on your side.

Please try switching the driver entry from modesetting to intel or i915. Please be ready, to work with the console.

Over here Xorg.0.log looks like this:

[    26.029]    ABI class: X.Org ANSI C Emulation, version 0.4
[    26.055] (==) modeset(0): Backing store enabled
[    26.055] (==) modeset(0): Silken mouse enabled
[    26.133] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[    26.133] (==) modeset(0): DPMS enabled
[    26.133] (II) modeset(0): [DRI2] Setup complete
[    26.133] (II) modeset(0): [DRI2]   DRI driver: iris
[    26.133] (II) modeset(0): [DRI2]   VDPAU driver: va_gl
[    26.133] (II) Initializing extension Generic Event Extension
[    26.133] (II) Initializing extension SHAPE
[    26.133] (II) Initializing extension MIT-SHM
[    26.134] (II) Initializing extension XInputExtension
[    26.134] (II) Initializing extension XTEST
[    26.134] (II) Initializing extension BIG-REQUESTS
[    26.134] (II) Initializing extension SYNC
[    26.134] (II) Initializing extension XKEYBOARD
[    26.134] (II) Initializing extension XC-MISC
[    26.134] (II) Initializing extension SECURITY
[    26.134] (II) Initializing extension XFIXES
[    26.134] (II) Initializing extension RENDER
[    26.134] (II) Initializing extension RANDR
[    26.135] (II) Initializing extension COMPOSITE
[    26.135] (II) Initializing extension DAMAGE
[    26.135] (II) Initializing extension MIT-SCREEN-SAVER
[    26.135] (II) Initializing extension DOUBLE-BUFFER
[    26.135] (II) Initializing extension RECORD
[    26.135] (II) Initializing extension DPMS
[    26.135] (II) Initializing extension Present
[    26.136] (II) Initializing extension DRI3
[    26.136] (II) Initializing extension X-Resource
[    26.136] (II) Initializing extension XVideo
[    26.136] (II) Initializing extension XVideo-MotionCompensation
[    26.136] (II) Initializing extension SELinux
[    26.136] (II) SELinux: Disabled on system
[    26.136] (II) Initializing extension GLX
[    26.395] (II) AIGLX: Loaded and initialized iris
[    26.395] (II) GLX: Initialized DRI2 GL provider for screen 0

Edith adds: Maybe you’ll have to remove the glamor module section. (Though glamor used to be hardware agnostic …)

23

Change “modesetting” to “intel” and now i just have a black screen

24

ctrl + alt + f2 ?

25

Yes that work alt + f2 did nothing and i got scared for a second. going to change it i915 now

26

You need to add ctrl when X is running (in the foreground). As long as there are only console messages alt + f2 will do.

1 Like
27

Same issue with i915

28

Do you – by any chance – have a secondary video graphics adapter? Some nvidia stuff or something like that?

29

Have a nvidia gpu in my desktop but no egpu sadly

30

I mean the Qubes machine you’re currently fiddling with. If so, is there a BIOS/UEFI setting for VGA-init?

You need that DRI2 IMHO. Otherwise, you’ll have a very powerful number crunching machine … but LibreOffice UI will be pretty much a slouch. (Even though i thought the Intel stuff gets nicely detected, after all. Hadn’t much to do on my laptop here. Just some minor Xen tweaking.)

31

Sadly no the only thing in this machine is the igpu. It’s a nova custom machine and the version with the 4080 wasnt qubes certified

32

Then this should work. Without any additional driver settings. I’m using a certified NV41 myself. I’ll search the github issues and report back if I find anything.

(I would bet some money that it’s the DRI settings…)

1 Like
33

Thank you so much I’ve been trying to figure this out for a while now

34

The author of this post enforces the i915 driver to load via kernel boot params (wasn’t necessary anymore when using kernel-latest):

i915.force_probe=* i915.modeset=1

Maybe … but remove that xorg.conf.d/20-intel.conf first…

35

I’m on the move right now but for when i get to a desk how do I edit the kernel boot params? Sorry if this is a silly question

36

It’s not silly at all. You will see why… *drumsandtrumpets* … “It depends.”

In most cases, (permanent) changes to boot parameters are done through /etc/default/grub. They are taken from there when you build grub.cfg.

  1. grub2-mkconfig -o /boot/grub2/grub.cfg → LEGACY/BIOS setup
  2. grub2-mkconfig -o /boot/efi/EFI/qubes/[grub(x64)|xen].cfg → (U)EFI setup

Caution: The above are examples only. The exact files/filenames depend on your BIOS platform. Please look for them in /boot/. E.g. with

sudo find /boot/ -iname "*.cfg"

For a one-shot test, it might be enough to press e when you see the grub menu. Add the parameters at the end of the line with the kernel (vmlinuz) options. Exit/Save with f10.

1 Like
37

I’m not sure that modifying something on a working dom0’s X will improve the performance of libreoffice in a qube.

Libreoffice using gtk in a qube has terrible performance, there are workarounds in the forum for this.

What are you looking in dom0 that could improve this?

38

The dri2 driver for X11?

Those X11 drivers have been discussed before … just some examples:

@solene You can easily test the impact by switching to some driver with no accel on your NV41. Things will rather “crawl”.

39

Can you help me find these? I’d prefer to not make changes to dom0

40

what fixes did you try so far?

glxgears output seems ok to me?