Bug#929923: missing dictionaries.xcu confuses non-US English locales (e.g. en_AU)
Rene Engelhard wrote: > 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. As I hinted before, mythes-en-us already contains "colour", though admittedly not in all cases: bash5$ grep -Fc color /usr/share/mythes/th_en_US_v2.dat 960 bash5$ grep -Fc colour /usr/share/mythes/th_en_US_v2.dat 661 A quick analysis of Debian 10's mythes-en-us [1] shows, * About 4.3% of the words are valid British-only words ((276K - 208K) ÷ 1.6M). * About 3.8% of the words are valid American-only words ((269K - 208K) ÷ 1.6M). So according to hunspell (the same spell-checker LibreOffice uses), th_en_US_v2.dat is actually more British than American :-) [1] bash5$ dpkg-query -W mythes-en-us hunspell hunspell-en-us hunspell-en-gb hunspell1.7.0-2 hunspell-en-gb 1:6.2.0-1 hunspell-en-us 1:2018.04.16-1 mythes-en-us1:6.2.0-1 bash5$ wc -w /usr/share/mythes/th_en_US_v2.dat | numfmt --to si # how many words in total? 1.6M /usr/share/mythes/th_en_US_v2.dat bash5$ hunspell -l -d en_US,en_GB /usr/share/mythes/th_en_US_v2.dat | wc -l | numfmt --to si # how many words misspelt in "both" english varieties (i.e. false positives)? 208K bash5$ hunspell -l -d en_US /usr/share/mythes/th_en_US_v2.dat | wc -l | numfmt --to si # how many words misspelt in en_US? 276K bash5$ hunspell -l -d en_GB /usr/share/mythes/th_en_US_v2.dat | wc -l | numfmt --to si # how many words misspelt in en_GB? 269K PS: Out of curiosity, I looked up some references re "colour" specifically. The OED is different enough from en-GB to have its own locale (en-GB-oxendict), but AFAIK it is nevertheless the primary reference for en-GB spelling. I don't have a dead-tree version; it's online version appears to live here: https://www.lexico.com/en/definition/color https://www.lexico.com/en/definition/colour https://www.lexico.com/en/definition/-our which simply has rather dogmatic labels "US" and "British", though it notes that "-our" is merely a "variant spelling". Fowler (1e) definition of "colo(u)r" (p. 83) directs me to "See -OR & -OUR", which says It is not worth while either to resist such a gradual change or to fly in the face of national sentiment by trying to hurry it. The American abolition of -our [...] has probably retarded rather than quickened English progress in the same direction. For en-AU, the AGPS Style Manual (5e) on §3.1 through §3.18 (pp. 39-42) simply advises doing whatever Macquarie says. I don't have a copy of Macquarie handy, and the online version is paywalled.
Bug#935182: Concurrent file open results file deletion by the read-only instance
found 935182 1:6.3.0-1 thanks On Wed, Aug 21, 2019 at 08:47:00AM +0200, Gilles MOREL wrote: > Actually, we were almost certain that the problem will be forwarded to the > upstream, so we openned the bug on Document Fondation too. Would have been nice to tell the upstream URL then in the report already since this then can be marked as such directly :) > We also tryed with the backports version, the problem is there too. OK, marking as such. Regards, Rene
Processed: Re: Bug#935182: Concurrent file open results file deletion by the read-only instance
Processing commands for cont...@bugs.debian.org: > found 935182 1:6.3.0-1 Bug #935182 [libreoffice-core] Concurrent file open on the same host results file deletion Marked as found in versions libreoffice/1:6.3.0-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#935148: libreoffice-common: After last upgrade libreoffice does not start properly - ERROR 4 forking process
close 935148 thanks Hi, On Wed, Aug 21, 2019 at 08:59:03AM +0200, Ing. Branislav Staron wrote: >Debian Buster was installed as RC. And apparmor reported too many AVC >denials. Profile changes were made with aa-logprof. I was too lazy to diff them, to be honest. Why did you think you need to change it? (Note I think that not all denials need to be fixed.) >I have used apparmor profiles from the latest libreoffice-common update >and everything now works fine. OK, so let's close this then. Regards, Rene
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: > close 935148 Bug #935148 [libreoffice-common] libreoffice-common: After last upgrade libreoffice does not start properly - ERROR 4 forking process Marked Bug as done > 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#935148: libreoffice-common: After last upgrade libreoffice does not start properly - ERROR 4 forking process
Hi Well thank you. Na utorok, 20. augusta 2019 18:26:28 CEST Rene Engelhard napísali: > 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? Debian Buster was installed as RC. And apparmor reported too many AVC denials. Profile cha
