Computer locks up with LibreOffice

English Applications
1

If I’m working on a project with LibreOffice Writer or Impress, after some time LibreOffice will lock up. Sometimes it locks up just those two programs, other times it locks up the computer. In the first instance, I can shut the computer down using the normal shutdown with the mouse clicking on icons in Tumbleweed. In the second instance, I have to shut the computer down using the power supply power switch as nothing on the desktop responds to mouse clicks.

The computer is running Tumbleweed 20250302.
KDE Plasma version 6.3.2
KDE Frameworks version 6.11.0
QT version 6.8.2
Kernel Version 6.13.5-1-default (64bit)
Graphics Platform X11

Processors 28 x Intel Core i7-14700
Memory 94 GB Ram
Graphics Processor Nvidia GeForce RTX 3050
Manufacturer ASUS

I appreciate what help can be given to diagnose this problem.

Mark

2

@Munguasafiwe Hi, caveat I don’t run Plasma… So you have the iGPU disabled in the BIOS? Please post the output from inxi -GSaz.

If you don’t have the iGPU disabled, then it could be intel vulkan fighting with nvidia vulkan…

Many applications use Graphics and Compute to run these days, so having both iGPU and dGPU is an advantage, no suse-prime (which should not be installed on your setup anyway) or switcherooctl needed.

This Graphics, Compute and GPU in use activity can be seen via nvtop.

3

For the first scenario, why shut down? If it’s simply LibreOffice locked up, why not kill the LIbreOffice app (whichever it is), then start it back up. I would use less intrusive kill options before opting for SIGKILL.

Have you checked logs for any clues. ?

Another option - the next time you run a L.O. app, run the L.O. app from a command line to see there is any output providing a clue.

For the second scenario, don’t rely on “mouse responses” … I’d be inclined to see if you get any response to switch to console one with CTRL-ALT-F1 (or if a laptop, might use CTRL fn ALT F1). If the console does show up, then see if a kill to the L.O. app restores things.

4

I had similar issues with some programs like KeePassCX and Onlyoffice recently. We discussed it a bit in this thread https://forums.opensuse.org/t/since-yesterdays-snapshot-plasmashell-crashes-constantly/183040/3

In the end it appears to be a QT bug that is solved in 6.8.3. See https://bugs.kde.org/show_bug.cgi?id=500326

Your symptoms sound the same.

5 
# inxi -GSaz
System:
  Kernel: 6.13.5-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.13.5-1-default
    root=UUID=1bf89c8b-88fa-4a74-9796-6ed18d986b80 splash=silent
    resume=/dev/disk/by-uuid/4d6c1461-ecf2-4c56-95c2-ca72834ecdec
    mitigations=auto quiet security=apparmor rd.driver.blacklist=nouveau
  Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A info: frameworks v: 6.11.0
    wm: kwin_x11 tools: avail: cinnamon-screensaver, lxlock, xscreensaver vt: 2
    dm: 1: GDM v: 47.0 2: SDDM note: stopped Distro: openSUSE Tumbleweed
    20250302
Graphics:
  Device-1: NVIDIA GA107 [GeForce RTX 3050 8GB] vendor: Micro-Star MSI
    driver: nvidia v: 570.124.04 alternate: nouveau,nvidia_drm
    non-free: 550/565.xx+ status: current (as of 2025-01; EOL~2026-12-xx)
    arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-2023 pcie:
    gen: 4 speed: 16 GT/s lanes: 8 link-max: lanes: 16 ports: active: none
    off: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 01:00.0 chip-ID: 10de:2582
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,vesa
    alternate: fbdev,nouveau,nv gpu: nvidia,nvidia-nvswitch display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 92 s-size: 530x301mm (20.87x11.85")
    s-diag: 610mm (24")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: Dell SE2422H
    serial: <filter> built: 2022 res: mode: 1920x1080 hz: 60 scale: 100% (1)
    dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
    drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland
  API: OpenGL v: 4.6.0 vendor: nvidia v: 570.124.04 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
    memory: 7.81 GiB
  API: Vulkan v: 1.4.304 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3050 driver: N/A device-ID: 10de:2582
    surfaces: xcb,xlib
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,
    kscreen-doctor, xfce4-display-settings wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
6

I only know how to use control/alt/esc on the keyboard to shut down a program that isn’t working properly. I’ve tried that, and the programs don’t respond.

As I tried to convey, sometimes it’s just LO that locks up, other times it spreads to the whole desktop and nothing responds. For that reason, I presume that the real problem isn’t LO, its something else and LO is just a symptom of whatever is really the issue. But I had to label this problem somehow, and LO was a convenient handle to pick on.

7

@Munguasafiwe So your running gdm for login and also X11, can you switch to Wayland?

8

Ok, tell me how to do this.

9

@Munguasafiwe If you log out and select your username, on the cog bottom right, there should be an option for Plasma with Wayland?

10

While I was waiting for your reply, I guessed that you wanted me to use plasma wayland. So I rebooted and selected plasma wayland on the restart. I’m in that session now and find that you gave me instructions just to logout and back in. What’s next?

11

@Munguasafiwe So just to confirm, your running a Wayland session now?

12

I did select that session, here’s the readout to let you confirm it.

inxi -GSaz
System:
  Kernel: 6.13.5-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.13.5-1-default
    root=UUID=1bf89c8b-88fa-4a74-9796-6ed18d986b80 splash=silent
    resume=/dev/disk/by-uuid/4d6c1461-ecf2-4c56-95c2-ca72834ecdec
    mitigations=auto quiet security=apparmor rd.driver.blacklist=nouveau
  Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A info: frameworks v: 6.11.0
    wm: kwin_wayland tools: avail: cinnamon-screensaver, lxlock, xscreensaver
    vt: 3 dm: 1: GDM v: 47.0 2: SDDM note: stopped Distro: openSUSE
    Tumbleweed 20250302
Graphics:
  Device-1: NVIDIA GA107 [GeForce RTX 3050 8GB] vendor: Micro-Star MSI
    driver: nvidia v: 570.124.04 alternate: nouveau,nvidia_drm
    non-free: 550/565.xx+ status: current (as of 2025-01; EOL~2026-12-xx)
    arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-2023 pcie:
    gen: 4 speed: 16 GT/s lanes: 8 link-max: lanes: 16 ports: active: none
    off: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 01:00.0 chip-ID: 10de:2582
    class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: nvidia
    unloaded: modesetting,vesa alternate: fbdev,nouveau,nv
    gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: HDMI-A-1 model: Dell SE2422H serial: <filter> built: 2022 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 93 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia gbm:
    drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia x11: drv: nvidia
  API: OpenGL v: 4.6.0 vendor: nvidia v: 570.124.04 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
    memory: 7.81 GiB display-ID: :1.0
  API: Vulkan v: 1.4.304 layers: 1 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3050 driver: N/A device-ID: 10de:2582
    surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,
    kscreen-doctor, xfce4-display-settings wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
13

@Munguasafiwe Hi the only thing I would do is add nvidia_drm.modeset=1 or maybe nvidia_drm.modeset=0 via YaST Bootloader, if/when you have any freeze going forward on Wayland.

14

Ok, thanks for the instruction. I’ll use the computer in plasma wayland for a few days to see what happens. Hopefully this will solve the issue.