Hi,

On Tue, Aug 20, 2019 at 04:52:52PM +0200, Gilles MOREL wrote:
> Package: libreoffice-core
> Version: 1:6.1.5-3+deb10u3
> Severity: grave

2 grave           makes the package in question unusable by most or all users, 
or causes data loss, or
                  introduces a security hole allowing access to the accounts of 
users who use the package.
[...]
4 important       a bug which has a major effect on the usability of a package, 
without rendering it completely
                  unusable to everyone.

Ok, one might argue this as data loss, but I don't think this is grave enough to
warrant grave, important looks more suited. But anyways.

> When two users on the same machine open

Why two users on the same machine, same file? I could understand the
scenario of same file on samba share, different computers... Or do
you use some graphical "remote desktop" thingy allowing access of more
people to one comuter?

> If the first user saves modification while the second user have the file 
> openned, the first user gets an error saying the file does not exists anymore.
> And then, the file is actually deleted once the second user closes the file.

LO has lockinbg problems like this. This is nothing new. In fact, quick googling
just gave me
https://bugs.documentfoundation.org/show_bug.cgi?id=115747#c28

> Versions of packages libreoffice-core depends on:
> ii  fontconfig                2.13.1-2
> ii  fonts-opensymbol          2:102.11+LibO6.3.0-2~bpo10+1
[...]
> ii  libreoffice-common        1:6.1.5-3+deb10u3
[...]
> ii  uno-libs3                 6.3.0-2~bpo10+1
> ii  ure                       6.3.0-2~bpo10+1
[...]
> ii  libreoffice-style-colibre  1:6.1.5-3+deb10u3
> ii  libreoffice-style-tango    1:6.1.5-3+deb10u3
> ii  ure                        6.3.0-2~bpo10+1
[...]
> ii  python3-uno                1:6.1.5-3+deb10u3
[...]
> ii  libreoffice-style-colibre [libreoffice-style]  1:6.1.5-3+deb10u3
> ii  libreoffice-style-tango [libreoffice-style]    1:6.1.5-3+deb10u3
[...]
> ii  libreoffice-common  1:6.1.5-3+deb10u3

etc.

It's probably not related (and would be a bug in the newer LO)
but why are you mixing 6.1.5 and 6.3.0 packages?

Regards,

Rene

Reply via email to