Bug#935182: Concurrent file open results file deletion by the read-only instance
Package: libreoffice-core Version: 1:6.1.5-3+deb10u3 Severity: grave Hello, When two users on the same machine open the same file from a samba share, the second gets a notice about the file to be openned in read-only mode. 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. -- Package-specific info: Experimental features enabled: Installed VCLplugs: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++----= un libreoffice-gtk2 (no description available) un libreoffice-gtk3 (no description available) un libreoffice-kde5 (no description available) -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-core depends on: ii fontconfig2.13.1-2 ii fonts-opensymbol 2:102.11+LibO6.3.0-2~bpo10+1 ii libboost-date-time1.67.0 1.67.0-13 ii libboost-locale1.67.0 1.67.0-13 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libclucene-contribs1v52.3.3.4+dfsg-1 ii libclucene-core1v52.3.3.4+dfsg-1 ii libcmis-0.5-5v5 0.5.2-1 ii libcups2 2.2.10-6 ii libcurl3-gnutls 7.64.0-4 ii libdbus-1-3 1.12.16-1 ii libdbus-glib-1-2 0.110-4 ii libdconf1 0.30.1-2 ii libeot0 0.01-5 ii libepoxy0 1.5.3-0.1 ii libexpat1 2.2.6-2 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig12.13.1-2 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.3.0-6 ii libglib2.0-0 2.58.3-2 ii libgpgmepp6 1.12.0-6 ii libgraphite2-31.3.13-7 ii libharfbuzz-icu0 2.3.1-1 ii libharfbuzz0b 2.3.1-1 ii libhunspell-1.7-0 1.7.0-2 ii libhyphen02.8.8-7 ii libice6 2:1.0.9-2 ii libicu63 63.1-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-22.9-3 ii libharfbuzz0b 2.3.1-1 ii libhunspell-1.7-0 1.7.0-2 ii libhyphen02.8.8-7 ii libice6 2:1.0.9-2 ii libicu63 63.1-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-22.9-3 ii libldap-2.4-2 2.4.47+dfsg-3 ii libmythes-1.2-0 2:1.2.4-3 ii libneon27-gnutls 0.30.2-3 ii libnspr4 2:4.20-1 ii libnss3 2:3.42.1-1 ii libnumbertext-1.0-0 1.0.5-1 ii libodfgen-0.1-1 0.1.7-1 ii liborcus-0.14-0 0.14.1-6 ii libpng16-16 1.6.36-6 ii libpoppler82 0.71.0-5 ii librdf0 1.0.17-1.1+b1 ii libreoffice-common1:6.1.5-3+deb10u3 ii librevenge-0.0-0 0.0.4-6 ii libsm62:1.2.3-1 ii libstdc++68.3.0-6 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.4-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libxmlsec11.2.27-2 ii libxmlsec1-nss1.2.27-2 ii libxrandr22:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.11.1.32-2 ii uno-libs3 6.3.0-2~bpo10+1 ii ure 6.3.0-2~bpo10+1 ii zlib1g1:1.2.11.dfsg-1 Versions of packages libreoffice-core recommends: ii libpaper-utils 1.1.28 libreoffice-core suggests no packages. Versions of packages libreoffice-common depends on: ii libnumbertext-data 1.0.5-1 ii libreoffice-style-colibre 1:6.1.5-3+deb10u3 ii libreoffice-style-tango1:6.1.5-3+deb10u3 ii ure6.3.0-2~bpo10+1 Versions of packages libreoffice-common recommends: ii apparmor 2.13.2-10 ii libexttextcat-data 3.4.5-1 ii python3-uno1:6.1.5-3+deb10u3 ii ttf-mscorefonts-installer 3.7 ii xdg-utils 1.1.3-1 Versions of packages libreoffice-common suggests: ii libreoffice-style-colibre [libreoffice-style] 1:6.1.5-3+deb10u3 ii libreoffice-style-tango [libreoffice-style]1:6.1.5-3+deb10u3 Versions of packages libreoffice-java-common
Bug#935182: Concurrent file open results file deletion by the read-only instance
Hi,
Actually, we were almost certain that the problem will be forwarded to the
upstream, so we openned the bug on Document Fondation too.
We also tryed with the backports version, the problem is there too.
--
Gilles MOREL
Ce message ne s'autodétruira pas dans cinq secondes. Cinq, quatre, trois, deux,
un…
- Message original
Rene Engelhard
à Gilles MOREL , 935...@bugs.debian.org
copie à cont...@bugs.debian.org
le mardi 20 août 2019 à 18:53:06 +0200
avec Mutt/1.10.1 (2018-07-13)
Re: Bug#935182: Concurrent file open results file deletion by the read-only
instance
--
forwarded 935182 https://bugs.documentfoundation.org/show_bug.cgi?id=127057
thanks
Hi,
On Tue, Aug 20, 2019 at 06:30:06PM +0200, Rene Engelhard wrote:
> 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
Or https://bugs.documentfoundation.org/show_bug.cgi?id=127057. By chance
filed by you or someone in your organization?
Just for data: What happens with a ("real"/complete) 6.3.0 (as is in
buster-backports, of which you have parts installed)?
Regards,
Rene
signature.asc
Description: This is a digitally signed message part.
Bug#935182: Concurrent file open results file deletion by the read-only instance
Hi, For severity, I read severity's description and the first that seemed to fit was grave, since I got data loss. For multiple user on the same host, the host is actually a RDP server, served by xrdp. For the version, that's because I tryed to use the backports version of LO, but the problem is there too. -- Gilles MOREL Le premier tirage aléatoire est [51, 31, 38, 6, 16] et le second est [9, 9, 9, 9, 9]. Quel tirage est le plus aléatoire ? - Message original Rene Engelhard à Gilles MOREL , 935...@bugs.debian.org le mardi 20 août 2019 à 18:30:06 +0200 avec Mutt/1.10.1 (2018-07-13) Re: Bug#935182: Concurrent file open results file deletion by the read-only instance -- 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 fontconfig2.13.1-2 > ii fonts-opensymbol 2:102.11+LibO6.3.0-2~bpo10+1 [...] > ii libreoffice-common1: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-tango1:6.1.5-3+deb10u3 > ii ure6.3.0-2~bpo10+1 [...] > ii python3-uno1: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 signature.asc Description: This is a digitally signed message part.
