https://bugs.documentfoundation.org/show_bug.cgi?id=161042
Bug ID: 161042
Summary: LO local instances hang when a network document save
is executed
Product: LibreOffice
Version: 24.2.3.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: myrbourf...@gmail.com
Description:
In Linux Mint 21.3 I work a lot with network documents (documents on a remote
shared location also running linux and accessed through ssh).
If I open one network document (calc) and one local document (calc) and run a
"save" on the network document, during the save even the local instance hangs.
As I work with very large documents, the whole libreoffice local and network
instance can hang for more than 1 minute in every save. My question is why the
local file also hangs if the upload of the network save is slow. Shouldn't they
two instances be independent? I understand the hanging of the remote document
but I don't justify the hanging of the local document.
Steps to Reproduce:
1. Open a big (> 30MB) network shared document (preferably through ssh)
2. Open a local document
3. Click "Save" on the network shared document
4. Try to use / edit the local document. It's impossible because even the local
instance of LO is hanging!
Actual Results:
Both local and network edited LO instances hang when a save is executed on the
remote document.
Expected Results:
Only the network edited LO instance should hang when a save is executed on the
remote document. The local opened document/instance should be fully functional
without hanging and without being affected by the network edited instance.
Reproducible: Always
User Profile Reset: No
Additional Info:
I'm using the following LO version:
Version: 24.2.4.0.0+ (X86_64) / LibreOffice Community
Build ID: aa225b41352f22c60f41fb9fa03c23b4e9359266
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: el-GR (en_US.UTF-8); UI: en-US
Calc: threaded
--
You are receiving this mail because:
You are the assignee for the bug.
