On 11/3/20 6:10 AM, Kuang-Chun Cheng wrote:
Mike McCarthy, W1NR sysop@w1nr.net 於 2020年11月3日 週二 下午7:56寫道：
Can you reproduce the problem with this document?
And, when the crash happened, could you still ping the computer from another device in the network?
Crashing hard so that only a reset helps is usually only possible with a kernel bug or hardware issue, not something LibreOffice should be able to do.
Regards, Simon
I would agree. In my experience, so called "lockups" are usually the result of the video crashing. If you can ping then try ssh to the box and do init 3 then init 5 to reset the graphics and see if that clears it.
Hi
In my case, when the LibreOffice lockup happened, the PC was still alive. The Desktop/GUI is frozen, and the only thing still working is the mouse pointer which still follows the mouse movement. However, you can only move the mouse pointer, but clicking on the mouse button doesn't work.
Keyboard seems to die, but Ctrl-Alt-F2 still works. So I can use text mode to kill the Desktop session (mate-session, gdm-session) to logout, then the system will back and GUI login dialog show up.
I can't repeat the problem, but it happens sometime (at CentOS 6x, 7x & 8x).
I spend hours upon hours in libreoffice calc and libreoffice writer on both CentOS 7 and CentOS 8.
I use the standard gnome desktop, not gnome classic or mate.
I have NEVER had a lockup in libreoffice.
These are the basic build requirements for libreoffice:
autoconf automake bc binutils bison desktop-file-utils doxygen findutils flex gcc-c++ gdb git gperf icu make perl(Digest::MD5) zip python-devel boost-devel cups-devel expat-devel fontpackages-devel glm-devel hyphen-devel libicu-devel libjpeg-turbo-devel lpsolve-devel openldap-devel pam-devel pkgconfig(bluez) pkgconfig(cppunit) pkgconfig(dbus-glib-1) pkgconfig(dconf) pkgconfig(epoxy) pkgconfig(evolution-data-server-1.2) pkgconfig(freetype2) pkgconfig(glew) >= 1.10.0 pkgconfig(glu) pkgconfig(gobject-introspection-1.0) pkgconfig(graphite2) pkgconfig(gstreamer-1.0) pkgconfig(gstreamer-plugins-base-1.0) pkgconfig(gtk+-2.0) pkgconfig(gtk+-3.0) pkgconfig(harfbuzz) pkgconfig(hunspell) pkgconfig(ice) pkgconfig(lcms2) pkgconfig(libabw-0.1) pkgconfig(libcdr-0.1) pkgconfig(libclucene-core) pkgconfig(libcmis-0.5) pkgconfig(libcurl) pkgconfig(libetonyek-0.1) pkgconfig(libexttextcat) pkgconfig(libfreehand-0.1) pkgconfig(libidn) pkgconfig(liblangtag) pkgconfig(libmspub-0.1) pkgconfig(libmwaw-0.3) pkgconfig(libodfgen-0.1) pkgconfig(liborcus-0.12) pkgconfig(libpagemaker-0.0) pkgconfig(librevenge-0.0) pkgconfig(libstaroffice-0.0) pkgconfig(libvisio-0.1) pkgconfig(libwpd-0.10) pkgconfig(libwpg-0.3) pkgconfig(libwps-0.4) pkgconfig(libxml-2.0) pkgconfig(libxslt) pkgconfig(libzmf-0.0) pkgconfig(mdds-1.2) pkgconfig(mythes) pkgconfig(neon) pkgconfig(nss) pkgconfig(poppler) pkgconfig(poppler-cpp) pkgconfig(redland) pkgconfig(sane-backends) pkgconfig(xext) pkgconfig(xinerama) pkgconfig(xt) pkgconfig(zlib) postgresql-devel unixODBC-devel ant bsh java-devel junit pentaho-reporting-flow-engine liberation-mono-fonts liberation-sans-fonts liberation-serif-fonts rpmlib(FileDigests) <= 4.6.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1
They are very gnome (gtk) centric. Maybe mate or another external build is impacting this? Or maybe you have upgraded one of these rpms outside of CentOS-7?
This file lists all the packages in the build root at the time of building:
https://buildlogs.centos.org/c7.2003.00.x86_64/libreoffice/20200401031402/5....
Specifically, starting at the line:
DEBUG util.py:417: ant noarch 1.9.4-2.el7 c7.1810.00.x86_64 2.0 M
any (especially the *-devel) files can be linked against and very important to proper operation of LibreOffice. The updates provided bu official CentOS packages should continue to work, any 3rd party replacements may not.
All that being said .. The only thing I can really provide is that I do not see this issue.