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.
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#929923: missing dictionaries.xcu confuses non-US English locales (e.g. en_AU)
On Wed, Aug 21, 2019 at 03:44:36PM +1000, Trent W. Buck wrote: > I still advocate solving only MY problem, with a simple change: > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=929923;filename=929923.patch;msg=22 And I still say that it at least for en_GB is wrong. As said: color vs. colour. You say that Australia is used to both, Ok, I believe so - but I don't think so for en_GB. > However, I also considered a complex change: > generate debian/*.links automatically from */dictionaries.xcu. > > A proof-of-concept is attached. > If this is interesting, I can look at merging it into debian/helper.py. > If this is not interesting, I'm happy to just forget about it :-) IMHO, this definitely sounds interesting. "In emergency" we can just remove unwanted ones.. Regards, Rene
Bug#929923: missing dictionaries.xcu confuses non-US English locales (e.g. en_AU)
I still advocate solving only MY problem, with a simple change:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=929923;filename=929923.patch;msg=22
However, I also considered a complex change:
generate debian/*.links automatically from */dictionaries.xcu.
A proof-of-concept is attached.
If this is interesting, I can look at merging it into debian/helper.py.
If this is not interesting, I'm happy to just forget about it :-)
#!/usr/bin/python3
"""Create symlinks to simulate missing dictionaries.xcu.
LibreOffice provides spelling/hyphenation/thesaurus dictionaries for different language varieties (xx_YY).
When another variety is similar, and no dedicated dictionary is available, they are aliased together.
LibreOffice defines these aliases in a "dictionaries.xcu" file.
For example, de_AT has its own hyphenation dictionary, but re-uses de_DE's thesaurus dictionary.
https://sources.debian.org/src/libreoffice-dictionaries/1:6.3.0-1/dictionaries/de/dictionaries.xcu/#L46
https://sources.debian.org/src/libreoffice-dictionaries/1:6.3.0-1/dictionaries/de/dictionaries.xcu/#L80
Debian does not ship dictionaries.xcu files because
1. only LibreOffice understands them, but
other packages use the dictionaries themselves.
2. Debian packages the spelling/hyphenation/thesaurus dictionaries separately, but
dictionaries.xcu assumes they are packaged together.
If your locale is set to the original language (e.g. LANG=de_DE for
th_de_DE_v2.dat), this Just Works, because of fallback behaviour in
the individual apps (including LibreOffice).
If your locale is set to the aliased language (e.g. LANG=de_AT for
th_de_DE_v2.dat), a symlink is needed to help the app "see" the dictionary.
Prior to this script, those symlinks were created on an ad-hoc basis.
This script tries to fully automate that process, so that
1. there is less work for the Debian maintainer; and
2. more consistent behaviour between Debian and upstream.
---Trent W. Buck, Aug 2019, https://bugs.debian.org/929923
"""
import sys
import glob
import pprint
import types
import re
import lxml.etree
def main() -> None:
for d in xcu2dicts():
for f, l in zip(d.files, d.locales):
# Expand the "%origin%" variable to whatever it should be.
f = f.replace('%origin%',
{'DICT_SPELL': '/usr/share/hunspell',
'DICT_HYPH': '/usr/share/hyphen',
'DICT_THES': '/usr/share/mythes'}[d.format])
symlink_dst_path = f
prefix = re.fullmatch(
r'('
r'/usr/share/hunspell/|'
r'/usr/share/hyphen/hyph_|'
r'/usr/share/mythes/(?:th|thes|thesaurus)_'
r').*',
f).group(1)
suffix = re.fullmatch(
r'.*'
r'((?:_v2)?\.(?:dic|aff|dat|idx))',
f).group(1)
symlink_src_path = (
prefix +
IETF_locale_to_glibc_locale(l) +
suffix)
# FIXME: needs to use f'-p{package}', like helper.py:generate_installs().
if symlink_dst_path != symlink_src_path:
print('', # indent for make
'dh_link',
symlink_dst_path,
symlink_src_path,
'# ' + l, # comment
sep='\t')
# The upstream XCU use RFC 5646 notation (kmr-Latn-TR).
# The upstream dictionaries aren't completely consistent, but mostly use glibc notation (ks_IN@devanagari).
# libreoffice-dictionaries/debian/helper.py has a hand-written dict instead of this bodgy regex-replacement.
def IETF_locale_to_glibc_locale(lo_locale: str) -> str:
s = lo_locale
# Change -Latn- to @latin (YUK!)
s = re.sub(r'(.+)-Latn(-.+)?', r'\1\2@latin', s)
# Change -valencia to @valencia (YUK!)
s = re.sub(r'(.+)-valencia', r'\1@valencia', s)
# Change xx-YY to xx_YY
s = re.sub(r'([^-]+)-(.+)', r'\1_\2', s)
return s
# Scrape key/value pairs from the XCUs.
# Example output:
# [namespace(files={'%origin%/af_ZA.aff', '%origin%/af_ZA.dic'},
#format='DICT_SPELL',
#locales={'af-NA', 'af-ZA'}),
# namespace(files={'%origin%/hyph_af_ZA.dic'},
#format='DICT_HYPH',
#locales={'af-NA', 'af-ZA'})]
def xcu2dicts() -> list:
acc = []# accumulator
for xcu_path in glob.glob('dictionaries/*/dictionaries.xcu'):
xcu_obj = lxml.etree.parse(xcu_path)
nsmap = xcu_obj.getroot().nsmap
for d in xcu_obj.xpath('//node[@oor:name="Dictionaries"]/node', namespaces=nsmap):
format, = d.xpath('./prop[@oor:name="Format"]/value/text()', namespaces=nsmap)
files = {
l
for value in d.xpath('./prop[@oor:name="Locations"]/value/text()', namespaces=nsmap)
for l in value.split()}
Bug#886999: libreoffice-writer: Crashes when I switch page margins size
Package: libreoffice-writer Version: 1:6.3.0-2 Followup-For: Bug #886999 Dear Maintainer, I can duplicate the problem whenever I want to change page margins in LibreOffice Writer. 1. Go to Format --> Page (or via pressing F11, etc.) 2. In the Page options page, default for me is .79" and if I change to 1", I type (starting from the left margin box): 1 [tab] 1 [tab] 1 [tab] 1. 3. If I press tab again then the box normalizes and sets margins to 1" all around. If I press enter, it works. But if I don't press the tab key the 4th time, and my cursor/selection is still on the last box, and I press enter, then the new margins don't "initialize" and instead I get a consistent crash. Thanks! -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-writer depends on: ii libabw-0.1-1 0.1.3-1 ii libc6 2.28-10 ii libe-book-0.1-10.1.3-1+b2 ii libepubgen-0.1-1 0.1.1-1 ii libetonyek-0.1-1 0.1.9-1 ii libgcc11:9.2.1-2 ii libicu63 63.2-2 ii liblangtag10.6.2-1 ii libmwaw-0.3-3 0.3.15-2 ii libodfgen-0.1-10.1.7-1 ii libreoffice-base-core 1:6.3.0-2 ii libreoffice-core 1:6.3.0-2 ii librevenge-0.0-0 0.0.4-6+b1 ii libstaroffice-0.0-00.0.6-1 ii libstdc++6 9.2.1-2 ii libwpd-0.10-10 0.10.3-1 ii libwpg-0.3-3 0.3.3-1 ii libwps-0.4-4 0.4.10-1 ii libxml22.9.4+dfsg1-7+b3 ii uno-libs3 6.3.0-2 ii ure6.3.0-2 ii zlib1g 1:1.2.11.dfsg-1+b1 Versions of packages libreoffice-writer recommends: ii libreoffice-math 1:6.3.0-2 Versions of packages libreoffice-writer suggests: ii default-jre [java6-runtime] 2:1.11-72 ii fonts-crosextra-caladea 20130214-2 ii fonts-crosextra-carlito 20130920-1 ii libreoffice-base1:6.3.0-2 ii libreoffice-java-common 1:6.3.0-2 ii openjdk-10-jre [java6-runtime] 10.0.2+13-2 ii openjdk-11-jre [java6-runtime] 11.0.4+11-1 ii openjdk-8-jre [java6-runtime] 8u222-b10-1 ii openjdk-9-jre [java6-runtime] 9.0.4+12-4 Versions of packages libreoffice-core depends on: ii fontconfig 2.13.1-2 ii fonts-opensymbol2:102.11+LibO6.3.0-2 ii libboost-date-time1.67.01.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-contribs1v5 2.3.3.4+dfsg-1+b1 ii libclucene-core1v5 2.3.3.4+dfsg-1+b1 ii libcmis-0.5-5v5 0.5.2-1 ii libcups22.2.12-1 ii libcurl3-gnutls 7.65.3-1 ii libdbus-1-3 1.12.16-1 ii libdconf1 0.30.1-2 ii libeot0 0.01-5+b1 ii libepoxy0 1.5.3-0.1 ii libexpat1 2.2.7-1 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig1 2.13.1-2 ii libfreetype62.9.1-4 ii libgcc1 1:9.2.1-2 ii libglib2.0-02.60.6-2 ii libgpgmepp6 1.12.0-6 ii libgraphite2-3 1.3.13-8 ii libgstreamer-plugins-base1.0-0 1.16.0-2 ii libgstreamer1.0-0 1.16.0-2.1 ii libharfbuzz-icu02.6.0-1 ii libharfbuzz0b 2.6.0-1 ii libhunspell-1.7-0 1.7.0-2+b1 ii libhyphen0 2.8.8-7 ii libice6 2:1.0.9-2 ii libicu6363.2-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-3+b1 ii libldap-2.4-2 2.4.48+dfsg-1 ii libmythes-1.2-0 2:1.2.4-3+b1 ii libneon27-gnutls0.30.2-3 ii libnspr42:4.21-2 ii libnss3 2:3.45-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.37-1 ii libpoppler820.71.0-5 ii librdf0 1.0.17-1.1+b1 ii libreoffice-common 1:6.3.0-2 ii librevenge-0.0-00.0.4-6+b1 ii libsm6 2:1.2.3-1 ii libstdc++6 9.2.1-2 ii libx11-62:1.6.7-1 ii libxext62:1.3.3-1+b2 ii libxinerama12:1.1.4-2 ii libxml2 2.9.4+dfsg1-7+b3 ii
Bug#929923: missing dictionaries.xcu confuses non-US English locales (e.g. en_AU)
Hi, sorry for dropping the ball on this. On Sat, Jun 08, 2019 at 04:11:30PM +1000, Trent W. Buck wrote: > I can dig out the contemporary th_en_US_v2.dat from > snapshots.debian.org, and do a three-way diff between it, > mythes-en-au, and current (LO6.3) mythes-en-us. That will show > quantitatively how different they are. Would be nice as data. > > It feels kind of weird to link -au to -us, as afaik there are effective > > differences between the two. > > This is what LO does on non-Debian platforms. > To me, that's a pretty compelling argument. Don't think so. With the same argument you would symlink de_CH to de_DE - even when Swiss German replaces all "ß" with "ss". Which definitely would be a bad thing. > Also note that on Debian currently, en_GB &c have *no* options for a > thesaurus in apt. And what are you going to do about color vs. colour etc.? Regards, Rene
Processed: found 935182 in 1:6.1.5-1
Processing commands for cont...@bugs.debian.org: > found 935182 1:6.1.5-1 Bug #935182 [libreoffice-core] Concurrent file open on the same host results file deletion Marked as found in versions libreoffice/1:6.1.5-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 935182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#935182: Concurrent file open results file deletion by the read-only instance
retitle 935182 Concurrent file open on the same host results file deletion thanks Hi, On Tue, Aug 20, 2019 at 06:30:06PM +0200, Rene Engelhard wrote: > 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? OK, the bug I pointed to in my other message says so and that it works if you do it from PC A and B... That would (IMHO) make it even more "important" since "normal" access from A or B to file X works, just RDP and same host A doesn't... In any case, this bug is not a distribution to fix, this is something for upstream. Regards, Rene
Processed: Re: Bug#935182: Concurrent file open results file deletion by the read-only instance
Processing commands for cont...@bugs.debian.org: > retitle 935182 Concurrent file open on the same host results file deletion Bug #935182 [libreoffice-core] Concurrent file open results file deletion by the read-only instance Changed Bug title to 'Concurrent file open on the same host results file deletion' from 'Concurrent file open results file deletion by the read-only instance'. > thanks Stopping processing here. Please contact me if you need assistance. -- 935182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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
Processed: Re: Bug#935182: Concurrent file open results file deletion by the read-only instance
Processing commands for cont...@bugs.debian.org: > forwarded 935182 https://bugs.documentfoundation.org/show_bug.cgi?id=127057 Bug #935182 [libreoffice-core] Concurrent file open results file deletion by the read-only instance Set Bug forwarded-to-address to 'https://bugs.documentfoundation.org/show_bug.cgi?id=127057'. > thanks Stopping processing here. Please contact me if you need assistance. -- 935182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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
Bug#935148: libreoffice-common: After last upgrade libreoffice does not start properly - ERROR 4 forking process
tag 935148 + moreinfo tag 935148 + unreproducible thanks On Tue, Aug 20, 2019 at 10:01:49AM +0200, Branislav Staron wrote: > Start-Date: 2019-08-19 07:56:26 > Commandline: apt-get upgrade > Requested-By: branislav.staron (1903801450) > Upgrade: libreoffice-wiki-publisher:amd64 (1.2.0+LibO6.1.5-3+deb10u2, > 1.2.0+LibO6.1.5-3+deb10u3), libreoffice-style-breeze:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libreoffice-math:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libreoffice-script-provider-js:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libavformat58:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), > libreoffice-report-builder-bin:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), > libavfilter7:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-sdbc- > postgresql:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-java- > common:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libswresample3:amd64 > (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-base:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libreoffice-core:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libreoffice-librelogo:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libreoffice-sdbc-firebird:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), python3-uno:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), > libpostproc55:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-script- > provider-python:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), > libreoffice-base- > core:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-impress:amd64 > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-help-common:amd64 > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-style-colibre:amd64 > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavcodec58:amd64 (7:4.1.3-1, > 7:4.1.4-1~deb10u1), ure:amd64 (6.1.5-3+deb10u2, 6.1.5-3+deb10u3), libreoffice- > sdbc-hsqldb:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice- > writer:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavutil56:amd64 > (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-common:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libreoffice-kde5:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libreoffice-script-provider-bsh:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libswscale5:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), > libreoffice-nlpsolver:amd64 (0.9+LibO6.1.5-3+deb10u2, > 0.9+LibO6.1.5-3+deb10u3), > libreoffice:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), fonts- > opensymbol:amd64 (2:102.10+LibO6.1.5-3+deb10u2, 2:102.10+LibO6.1.5-3+deb10u3), > libreoffice-report-builder:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), uno- > libs3:amd64 (6.1.5-3+deb10u2, 6.1.5-3+deb10u3), libreoffice-style-tango:amd64 > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-help-en-us:amd64 > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-calc:amd64 > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-base-drivers:amd64 > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavresample4:amd64 (7:4.1.3-1, > 7:4.1.4-1~deb10u1), libreoffice-draw:amd64 (1:6.1.5-3+deb10u2, > 1:6.1.5-3+deb10u3), libreoffice-avmedia-backend-gstreamer:amd64 > (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), tzdata:amd64 (2019a-1, > 2019b-0+deb10u1) > End-Date: 2019-08-19 07:56:52 So uptodate buster. >* What exactly did you do (or not do) that was effective (or > ineffective): running libreoffice applications (with non root and root > user - the same behavior) Brilliant. And by running as root you mean sudo with what $HOME set? if $HOME was your home LO now created stuff as root in that dir. Never run stuff like this as root (or be sure you sanitize your environment.) >* What was the outcome of this action: application does not run. stderr: > ERROR 4 forking process Works here. There was https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499 once but this is a) fixed and b) apparmor is new enough. > I tried to see the following - no result: > - check apparmor logs (compliance apparmor profil) > type=AVC msg=audit(1566286788.299:237): apparmor="ALLOWED" > operation="exec" info="profile transition not found" error=-13 > profile="libreoffice-oopslash" name="/usr/lib/libreoffice/program/soffice.bin" > pid=7336 comm="osl_executeProc" requested_mask="x" denied_mask="x" > fsuid=1903801450 ouid=0 target="/usr/lib/libreoffice/program/soffice.bin" [...] > -- Configuration Files: > /etc/apparmor.d/usr.lib.libreoffice.program.oosplash changed: why did you change it? > /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin changed: why did you change it? > /etc/apparmor.d/usr.lib.libreoffice.program.xpdfimport changed:
Processed: Re: Bug#935148: libreoffice-common: After last upgrade libreoffice does not start properly - ERROR 4 forking process
Processing commands for cont...@bugs.debian.org: > tag 935148 + moreinfo Bug #935148 [libreoffice-common] libreoffice-common: After last upgrade libreoffice does not start properly - ERROR 4 forking process Added tag(s) moreinfo. > tag 935148 + unreproducible Bug #935148 [libreoffice-common] libreoffice-common: After last upgrade libreoffice does not start properly - ERROR 4 forking process Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 935148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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#935148: libreoffice-common: After last upgrade libreoffice does not start properly - ERROR 4 forking process
Package: libreoffice-common Version: 1:6.1.5-3+deb10u3 Severity: important Dear Maintainer, * What led up to the situation? -> apt-get update && apt-get upgrade Start-Date: 2019-08-19 07:56:26 Commandline: apt-get upgrade Requested-By: branislav.staron (1903801450) Upgrade: libreoffice-wiki-publisher:amd64 (1.2.0+LibO6.1.5-3+deb10u2, 1.2.0+LibO6.1.5-3+deb10u3), libreoffice-style-breeze:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-math:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-script-provider-js:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavformat58:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-report-builder-bin:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavfilter7:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-sdbc- postgresql:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-java- common:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libswresample3:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-base:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-core:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-librelogo:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-sdbc-firebird:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), python3-uno:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libpostproc55:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-script- provider-python:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-base- core:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-impress:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-help-common:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-style-colibre:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavcodec58:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), ure:amd64 (6.1.5-3+deb10u2, 6.1.5-3+deb10u3), libreoffice- sdbc-hsqldb:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice- writer:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavutil56:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-common:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-kde5:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-script-provider-bsh:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libswscale5:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-nlpsolver:amd64 (0.9+LibO6.1.5-3+deb10u2, 0.9+LibO6.1.5-3+deb10u3), libreoffice:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), fonts- opensymbol:amd64 (2:102.10+LibO6.1.5-3+deb10u2, 2:102.10+LibO6.1.5-3+deb10u3), libreoffice-report-builder:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), uno- libs3:amd64 (6.1.5-3+deb10u2, 6.1.5-3+deb10u3), libreoffice-style-tango:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-help-en-us:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-calc:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-base-drivers:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libavresample4:amd64 (7:4.1.3-1, 7:4.1.4-1~deb10u1), libreoffice-draw:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), libreoffice-avmedia-backend-gstreamer:amd64 (1:6.1.5-3+deb10u2, 1:6.1.5-3+deb10u3), tzdata:amd64 (2019a-1, 2019b-0+deb10u1) End-Date: 2019-08-19 07:56:52 * What exactly did you do (or not do) that was effective (or ineffective): running libreoffice applications (with non root and root user - the same behavior) * What was the outcome of this action: application does not run. stderr: ERROR 4 forking process * What outcome did you expect instead: I tried to see the following - no result: - check apparmor logs (compliance apparmor profil) type=AVC msg=audit(1566286788.299:237): apparmor="ALLOWED" operation="exec" info="profile transition not found" error=-13 profile="libreoffice-oopslash" name="/usr/lib/libreoffice/program/soffice.bin" pid=7336 comm="osl_executeProc" requested_mask="x" denied_mask="x" fsuid=1903801450 ouid=0 target="/usr/lib/libreoffice/program/soffice.bin" - run libreoffice with strace -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=sk_SK.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8), LANGUAGE=sk (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled 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.1.5-3+deb10u3 Versions of packages libreoffice-common recommends: ii apparmor2.13.2-10 ii fonts-liberation2 2.00.5-1 ii libexttextcat-data 3.4.5-1 ii python3-uno 1:6.1.5-3+deb10u3 ii xdg-utils 1.1.3-1 Versions of packages libreoffice-common suggests: ii libreoffice-style-breeze [libreoffice-style
