Description: After an update to my arch linux system going from 24.2.0-1 to 24.2.2-2, I am having problems using calc or writer that in both cases, saving the file seem to trigger the UI to stop refreshing the window. It seems to still works, but not reflect UI changes, such as if I click and drag, it acts like it's highlighting, I can right click and get a menu, but I see no changes to the actual window workspace. If I type something and save, it is reflected on reopening the file and works normally until I save the file, then freezes again. More concerning, if I open a new or existing file, make a change, save or save-as, it freezes the screen, and I use a small script to kill all the libreoffice pids to kill -9 everything, but then upon restart where I expect to see that file in the restore list as I have for some 2 decades, it doesn't add that to the restore list or act like it's ever seen the file. Normally I would expect open any file, save the file, forcibly kill/crash libreoffice, that it would assuredly open and restore that and all the other files I have open. It's been one failsafe constant in my life since moving to linux mid-2000's using openoffice and later libreoffice. This seems sort of like a weird compositor issue I have with KDE/kwin where windows stop refreshing after a week or two uptime, but this only seems to do it to the active libreoffice document, and not the other calc/writer docs also open. I'd expect/witnessed with compositor issues before it will affect all windows for an app (including libreoffice), so instead seems more a UI problem with libreoffice alone. Steps to Reproduce: For arch linux: 1.Open LibreOffice Base 2.Get Document Recovery window, Recover Selected prior open documents 3.Click on opened file, Ctrl-o to open new file (calc or writer) 4.Click on Untitled file, add some text content, ctrl-shift-s file to save-as a file where ever 5.Observe after saving clicking in the document, dragging, typing, the work space of the window does not reflect changes, but menu and clicking does change pointer to reflect it is doing something 6.Observe clicking other libreoffice windows, calc or writer, others respond normally for a time, others freeze the same way 7.Issue a kill -9 to all libreoffice pids to abort all instances 8.Click to open again Libreoffice Base 9.Observe the new file freshly saved is not part of Recovery, only the original files recovered 10.Re-open the prior saved file, observe changes were saved, visible or not prior to force kill 11.Repeat ad nauseam Actual Results: 1.Windows freeze updating UI after any kind of save or auto-save, unable to edit file 2.New windows added/edited, saved or not are no longer recovered after crash after upgrade Expected Results: 1.Quick save or save-as should not freeze the UI and allow normal continued work after manual or auto-save 2.Any forced or unexpected crash of unsaved "Untitled #" or saved named files are expected to be included in recovery after manual save or auto-save interval (10min) Reproducible: Always User Profile Reset: No Additional Info: Arch Linux on Lenovo Thinkpad T15g G2 Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 16; OS: Linux 6.8; UI render: default; VCL: kf6 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US 24.2.2-2 Calc: threaded DE: KDE Plasma 6.0.4, xorg session (not wayland)
I did end up starting in safe mode per recommendation, wiping the profile new, and was able to again reproduce this behavior even in safe mode.
Thank you for the report. Do you reproduce the same issue: - in LO 24.2.3? - when using other VCL plugins? For example: SAL_USE_VCLPLUGIN=kf5 libreoffice24.2 or SAL_USE_VCLPLUGIN=gen libreoffice24.2 or SAL_USE_VCLPLUGIN=gtk3 libreoffice24.2
Created attachment 194243 [details] strace soffice --writer 2>2-writer-24-2-3-2-freeze.txt output
Created attachment 194244 [details] strace soffice --safe-mode --writer 2>2-safe-mode-writer-24-2-3-2.txt output
Having same issue. LibreOffice version information: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 6.9; UI render: default; VCL: kf6 (cairo+xcb) Locale: et-EE (et_EE.UTF-8); UI: et-EE 24.2.3-3 Calc: threaded But when downloaded an AppImage version https://appimages.libreitalia.org/LibreOffice-fresh.full.help-x86_64.AppImage, then that issue is gone: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba CPU threads: 8; OS: Linux 6.9; UI render: default; VCL: kf5 (cairo+xcb) Locale: et-EE (et_EE.UTF-8); UI: et-EE Calc: threaded Tested also https://appimages.libreitalia.org/daily/LibreOfficeDev-24.8.0.0.alpha0.basic-x86_64.AppImage and also there is issue gone. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: abdb93ce28febd7c4b4e5dad164ee8a394b499b9 CPU threads: 8; OS: Linux 6.9; UI render: default; VCL: kf5 (cairo+xcb) Locale: et-EE (et_EE.UTF-8); UI: en-US Calc: threaded it seems to be KDE Frameworks (kf) version issue: kf5 vs kf6. Used system: KDE 6.0.4 KDE Frameworks 6.2.0 Qt 6.7.0 Kernel 6.9.1 Display server: X11 GPU: nVidia Quadro M2000M/PCIe/SSE2 inxi -xxxGz Graphics: Device-1: NVIDIA GM107GLM [Quadro M2000M] vendor: Lenovo driver: nvidia v: 550.78 arch: Maxwell pcie: speed: 2.5 GT/s lanes: 16 ports: active: none off: eDP-1 empty: DP-1,DP-2,DP-3 bus-ID: 01:00.0 chip-ID: 10de:13b0 class-ID: 0300 Device-2: Lite-On Integrated Camera driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-8:2 chip-ID: 04ca:7058 class-ID: 0e02 Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0 compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 143 s-size: 341x191mm (13.43x7.52") s-diag: 391mm (15.39") Monitor-1: eDP-1 mapped: DP-4 note: disabled model: LG Display 0x054f res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") modes: 1920x1080 API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1 API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78 glx-v: 1.4 direct-render: yes renderer: Quadro M2000M/PCIe/SSE2 API: Vulkan v: 1.3.279 layers: 1 surfaces: xcb,xlib device: 0 type: discrete-gpu driver: nvidia device-ID: 10de:13b0
Tested: SAL_USE_VCLPLUGIN=kf5 libreoffice --writer ... and still Help->About shows the use of kf6 and freezing issue persisted: Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 6.9; UI render: default; VCL: kf6 (cairo+xcb) Locale: et-EE (et_EE.UTF-8); UI: et-EE 24.2.3-3 Calc: threaded But when used: SAL_USE_VCLPLUGIN=gen libreoffice --writer then no freezing issue anymore, program info showed (also LibreOffice menus were instead of system one): Version: 24.2.3.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 8; OS: Linux 6.9; UI render: default; VCL: x11 Locale: et-EE (et_EE.UTF-8); UI: et-EE 24.2.3-3 Calc: threaded
The freeze with kf6 is most likely the issue described in tdf#160565 (and fixed in the current development version of LibreOffice). -> Closing as duplicate For auto-recovery not working as expected: Please create a separate bug report if that is still an issue with a version containing the above fix - it sounds like a separate issue. *** This bug has been marked as a duplicate of bug 160565 ***
Sorry for the late response, but yes, I can confirm using "SAL_USE_VCLPLUGIN=gen libreoffice" does let saving work without freezing, and as well auto-save seems to be working as well to restore unsaved files. This was after an upgrade to Plasma 6 as well in Arch. Only weirdness I'm seeing using SAL_USE_VCLPLUGIN=gen is still with autosave, in that if I have two files opened, and unsaved file with change, and a saved file without changes, hard killing the app and restarting it, it only wants to recover and reopen the unsaved file, and does NOT reopen the saved file. In the past as long as I can remember, it has always reopened both saved AND unsaved files after a crash/kill, so not sure if this is somehow related to the kf6 issue, or some other random behavior now changed.
(In reply to Mike Butash from comment #8) > In the past as long as I can remember, it has always reopened both saved AND > unsaved files after a crash/kill, so not sure if this is somehow related to > the kf6 issue, or some other random behavior now changed. This is unrelated and was done on purpose, please see bug 160769.