Ran sudo pkg update -f and installed the recommended packages this morning for FreeBSD 13.2-STABLE. Libreoffice has literally disappeared off my system. It will not open, I cannot find any commands, I cannot even reinstall. Come one...what is going on?
I apologise for the inconvenience. What version of FreeBSD do you run? Do you use the quarterly or rather the main package branch? This some times happens when there is a build failure on our package cluster. I recommend not using "-f" for "pkg update" unless you are ok with this sort of thing. Instead check the list carefully and perhaps lock packages that you wish to keep. As a temporary workaround, you can try to reinstall the package from your local cache: pkg add /var/cache/pkg/libreoffice-7.5.4.2_1.pkg # for quarterly pkg add /var/cache/pkg/libreoffice-7.5.5.2_3.pkg # for latest The specific package versions depend on when you last updated. When in doubt, check /var/cache/pkg for the latest version you find.
I have the same issue. I'm using "latest". Can't reinstall because it's not in my /var/cache
As I put in the ticket, I'm running 13.2-STABLE. I've dropped the -f from my updates so it won't happen again. However, attempting a reinstall from /var/cache installed libreoffice, but due to changes (I assume) with dependencies, it will not start. I will wait for the next update.
Folks, please be patient, pkg cluster is rebuilding all requirements for the recent libreoffice and packages will be appears soon
(In reply to Dima Panov from comment #4) Many thanks ;-) Always patient, or we wouldn’t be here ;-)
(In reply to Rob Belics from comment #2) Did you create a ZFS boot environment before updating? bectl(8) <https://man.freebsd.org/cgi/man.cgi?query=bectl&sektion=8&manpath=freebsd-release>
Folks, I was just reading (and commenting) this https://forums.freebsd.org/threads/libreoffice-package-abandoned.90458/ which pointed me here. As it seems, the actual problem is an endless-loop hanging libreoffice build. This is normal, I'm experiencing this very same hang for about a year already, and it happens randomly every 2nd or 3rd build. Workaround: just rerun the build.
I just observed the problem again (libreoffice build not completing). This is the hanging process: UID PID PPID C PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 85059 71727 0 20 0 1713960 22856 uwait I - 19:52.43 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding utf8 --release 8 -Xlint:-options -g -d /var/local/ports/usr/ports/editors/libreoffice/work/libreoffice-7.6.2.1/workdir/CustomTarget/jvmfwk/jreproperties/ /var/local/ports/usr/ports/editors/libreoffice/work/libreoffice-7.6.2.1/jvmfwk/plugins/sunmajor/pluginlib/JREProperties.java # ps axH | grep 85059 85059 - I 0:00.02 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u 85059 - I 0:00.05 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u 85059 - I 0:00.00 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u 85059 - S 6:46.50 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u 85059 - I 0:00.00 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u 85059 - S 6:43.71 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u 85059 - S 6:32.78 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u 85059 - S 0:00.68 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u 85059 - I 0:00.00 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u 85059 - I 0:00.03 /usr/local/openjdk11/bin/javac -J-Xmx128M -encoding u And this (truss) is what it does: 85059: 0.011988157 0.012034650 _umtx_op(0x18c56bee2068,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x18c5a8e0ddb8) ERR#60 'Operation timed out' 85059: 0.014322564 0.014362192 _umtx_op(0x18c56bee2080,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x18c5a9b08db8) ERR#60 'Operation timed out' 85059: 0.014734241 0.000229620 _umtx_op(0x18c56bee2038,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x18c59ef43db8) ERR#60 'Operation timed out' 85059: 0.015662659 0.001040724 _umtx_op(0x18c56bee2068,UMTX_OP_WAIT_UINT_PRIVATE,0x0,0x18,0x18c5a8e0ddb8) ERR#60 'Operation timed out' Ther is no other system call shown, only these _umtx_op going on endlessly. IS there somebody knowlegdeable about the behaviours of the javac? Can we somehow fix this? There is a similar bug description for a different product here - seems like that is a FreeBSD specific problem: https://github.com/bazelbuild/bazel/issues/1250
libreoffice packages are available on pkg.freebsd.org again.
So what was the bug in the javac, and how was it fixed?