Bug 160864 - Screen stops refreshing after save, does not make a restore auto-save for files
Summary: Screen stops refreshing after save, does not make a restore auto-save for files
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
24.2.2.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-30 04:29 UTC by Mike Butash
Modified: 2024-05-15 15:06 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Butash 2024-04-30 04:29:10 UTC
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)
Comment 1 Mike Butash 2024-04-30 05:01:25 UTC
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.
Comment 2 Stéphane Guillou (stragu) 2024-05-15 15:06:10 UTC
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