Whenever I select Tools -> Options or press ALT + F12, the LibreOffice UI stops responding. The window can be resized but the contents are no longer re-drawn. Most odd is that this problem only occurs in my main profile. A fresh Linux account does not exhibit this problem. I've tried every safe mode option and removed ~/.config/libreoffice in the problem profile (the main one) to no avail. LibreOffice says nothing in the terminal before ceasing to respond. (Except for not being able to find a JRE, which I've already played with and didn't make a difference if one was present and found or not present.)
On which Linux distrib are you and how did you install LO ?
Arch Linux $ uname -a > Linux comet 5.14.14-zen1-1-zen #1 ZEN SMP PREEMPT Wed, 20 Oct 2021 21:35:17 +0000 x86_64 GNU/Linux
Ok for Arch and how did you install LO 7.2.2 ?
With pacman. $ pacman -Qi libreoffice-fresh > Name : libreoffice-fresh > Version : 7.2.2-1 > ...
Additional info: the optional dependencies java-runtime: adds java support [installed] java-environment: required by extension-wiki-publisher and extension-nlpsolver pstoedit: translates PostScript and PDF graphics into other vector formats libmythes: for use in thesaurus [installed] beanshell: interactive java -- good for prototyping/macros libwpg: library for importing and converting WordPerfect Graphics format [installed] sane: for scanner access [installed] unixodbc: adds ODBC database support [installed] gst-plugins-base-libs: for multimedia content, e.g. in Impress [installed] libpaper: takes care of papersize [installed] postgresql-libs: for postgresql-connector [installed] mariadb-libs: for mysql-connector [installed] coin-or-mp: required by the Calc solver gtk3: for GTK3 integration [installed] kio: for KF5 KDE desktop integration [installed]
Just to be sure it's not a pb with gtk or kde, could you open a term/console and do: - export SAL_USE_VCLPLUGIN=gen - launch LO and try to reproduce the pb ?
Problem still exists exists with SAL_USE_VCLPLUGIN=gen
Ok so a last thing to try would be to be sure it's no Skia related, see https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28Skia.29. Also, which previous LO version did work in your machine? (if there's one)
Problem persists with SAL_SKIA=raster and setting UseSkia to false in ~/.config/libreoffice/4/user/registrymodifications.xcu > Also, which previous LO version did work in your machine? (if there's one) This has been a long-standing problem for quite a few versions now (since 5.x?). It hasn't bothered me enough to put in the effort to diagnose and do a bug report on it until now. Of particular anguish is the lack of verbosity on the command line that might give me a hint as to what LO is getting stuck on.
Argh... The next step (but this one is bigger) is to build sources (see https://wiki.documentfoundation.org/Development/BuildingOnLinux). It would allow you may to use flag like enable-dbgutil so you would have max debug information. But I know it takes some time to retrieve sources + to build (depending of the power of your machine of course but on mine, Ryzen 2600 + 32Gb, it takes about 2 hours I think). Now it's up to you, I can understand you don't have time or don't want to for example. Very weird that's it's bound to your user (not LO) profile. Xisco: did you encounter a similar bug or do you know whom we may ping here?
This actually shouldn't be too bad, as I can just gank the PKGBUILD from the main Arch repos and make a few adjustments. Time to put the i5-10600KF to the test.
Build failed for me. Log at https://bwt.com.de/failed-compile.log
Tuned PKGBUILD to build with --enable-dbgutil: https://bwt.com.de/PKGBUILD
Just for info, here's my autogen.input: CC=clang CXX=clang++ --enable-online-update --with-privacy-policy-url=https://yourdomain/privacy-policy --enable-compiler-plugins --enable-dbgutil --enable-evolution2 --enable-qt5 --enable-kf5 --enable-gtk3-kde5 --enable-skia=debug --enable-ext-nlpsolver --enable-ext-ct2n --enable-ext-numbertext --enable-ext-wiki-publisher --enable-dbus --enable-werror --enable-dependency-tracking --enable-python=fully-internal --without-system-mariadb --enable-bundle-mariadb --enable-symbols --enable-avahi --enable-eot --enable-odk --with-lang=en-US en-GB es fr hu pt pt-BR it de ru --with-myspell-dicts Did you follow https://wiki.documentfoundation.org/Development/BuildingOnLinux#Arch_Linux ? It worked for me on Debian testing + on Win10 but I'm not a building expert, I just followed instructions. Perhaps you may use dev mailing list or IRC (see https://wiki.documentfoundation.org/Development, in "Getting Started with Development" part) and try to ping someone?
Tried again, enabling everything specified above that wasn't explicitly enabled or was explicitly disabled (except for myspell-dicts, which relies on privacy-policy-url). I also switched from gcc to clang using the CC and CXX environment variables (which required a little tweaking in /etc/makepkg.conf). And I still bomb out at the same place. Unable to complete network request to host "localhost". -Failed to establish a connection. :shrug: It was worth a shot.
Luboš/Michael: any idea what's the building pb here?
Clang-based failed compile log: https://bwt.com.de/failed-compile-clang.log Updated PKGBUILD used: https://bwt.com.de/PKGBUILD2
Just to be sure, does "ping localhost" work ? For me, it's defined in /etc/hosts, there's the line: 127.0.0.1 localhost
$ ping -c 4 localhost PING localhost(localhost.local.lan (::1)) 56 data bytes 64 bytes from localhost.local.lan (::1): icmp_seq=1 ttl=64 time=0.010 ms 64 bytes from localhost.local.lan (::1): icmp_seq=2 ttl=64 time=0.045 ms 64 bytes from localhost.local.lan (::1): icmp_seq=3 ttl=64 time=0.013 ms 64 bytes from localhost.local.lan (::1): icmp_seq=4 ttl=64 time=0.014 ms --- localhost ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3058ms rtt min/avg/max/mdev = 0.010/0.020/0.045/0.014 ms $ cat /etc/hosts # Static table lookup for hostnames. # See hosts(5) for details. # #<ip-address> <hostname.domain.org> <hostname> 127.0.0.1 localhost.local.lan localhost ::1 localhost.local.lan localhost 192.168.redactd comet.local.lan comet
Searching the message "Unable to complete network request to host "localhost"", I found: https://stackoverflow.com/questions/22338165/firebird-unable-to-complete-network-request-to-host Is there any firewall enabled on your machine? If yes, could you disable it just to try (or at least disable filter on port 3050 which seems the by default port according to the link)
I do, actually. A simple statefull firewall using iptables. So I added an unconditional allow for port 3050. Still failed at the same spot. So then I disabled iptables.service. Still failed at the same spot. Willing to go on a wild goose chase, I uncomment skip-networking in /etc/my.cnf.d/server.conf. Still failed at the same spot.
s/uncomment/commented-out/
Just wondering: - since the goal is to debug, I suppose you're trying to build LO from your usual Linux account but perhaps the build, at least the Firebird part, may work on the fresh account? (and so you could launch LO built on the "ok" account from the "ko" account, hoping there won't be any rights pb of course...) - could there be any firewall rule or specific security rule on the "ko" account which could explain the "localhost" error message and perhaps even the initial bug here?
Tried compiling under the other account and it got stuck at the same place as well.
Ok so build pb and bugtracker pb seem not related. So Do you have some security on kernel (apparmor) or something? Search the network error message + Arch, I found this ref too https://bugs.archlinux.org/task/61984 but it's been closed for a while :-( You can try a verbose build for Firebird part with: make GMAKE_OPTIONS='VERBOSE=1' firebird to try to retrieve extra info. Anyway, you can add this line on autogen.input for the moment: --disable-firebird-sdbc (+ launch autogen.sh again so it'll be taken into account) in order to not build Firebird since your primary goal is to know why Tools/Options make LO not respond.
Debug output: http://ix.io/3DET
(In reply to ph3 from comment #26) > Debug output: http://ix.io/3DET Before launching "make debugrun", please try "make" before to know if the build is ok or not.
Please see if you can close as a duplicate of Bug 146852, as this bug has no motion.
Dear ph3, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear ph3, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp