At my wit's end. Running LibreOffice 5.1.6.2 (the std repo version) on Ubuntu 16.04 (64-bit).
azed@azed-H270N:~$ uname -a
Linux azed-H270N 4.10.0-37-generic #41~16.04.1-Ubuntu SMP Fri Oct 6 22:42:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
LO has always had a tendency to "hang" on my 16.04 system, but now it is regularly taking down the whole system.
Doing anything quickly in LO - sweep-selecting text, executing two commands in quick succession - seems to bring-on the problem.
The size of the document may also be a factor. The problem has tended to occur when I am working on a long (600 page, 3.6MB) doc, but this may only be because I tend not to work on short docs for very long.
Symptoms:
The whole system freezes. The mouse pointer remains mobile, but the system is otherwise unresponsive. After a few minutes of stasis, the system crashes back to the login screen.
After logging back-in, I am greeted by the LO document-recovery dialogue. The doc comes back OK, but all work done after the last LO autosave is lost.
After one crash, LO is much more likely to crash again.
Steps taken:
I have increased the memory used for the LO graphics cache to 190MB, and the memory / object to 12MB, but this has not improved things.
I have also tried calling LO from a terminal with gtk2 rather than gtk3, using:
SAL_USE_VCLPLUGIN=gtk libreofficeas detailed here:
Force LibreOffice 5.1.2.2 to use gtk2 instead of gtk3?
But no joy/improvement (didn't seem to change anything).
After the last crash, I examined
~/.xsession-errors,/var/log/dmesgand/var/log/syslog. The last yielded:Oct 12 16:20:38 azed-H270N gnome-session[1707]: ** (soffice:1998): WARNING **: Unknown event notification 36 Oct 12 16:24:26 azed-H270N gnome-session[1707]: ** (soffice:1998): WARNING **: Unknown event notification 36 Oct 12 16:24:26 azed-H270N systemd[1]: Starting Cleanup of Temporary Directories... Oct 12 16:24:26 azed-H270N systemd-tmpfiles[2712]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Oct 12 16:24:26 azed-H270N systemd[1]: Started Cleanup of Temporary Directories. Oct 12 16:24:38 azed-H270N gnome-session[1707]: ** (soffice:1998): WARNING **: Unknown event notification 36 Oct 12 16:29:12 azed-H270N gnome-session[1707]: message repeated 3 times: [ ** (soffice:1998): WARNING **: Unknown event notification 36] Oct 12 16:34:46 azed-H270N org.gnome.zeitgeist.SimpleIndexer[1551]: ** (zeitgeist-fts:2105): WARNING **: Unable to get info on application://nautilus-autostart.desktop Oct 12 16:39:46 azed-H270N systemd[1]: Starting Automatically fetch and run repair assertions... Oct 12 16:39:46 azed-H270N snap-repair[2949]: error: cannot use snap-repair on a classic system Oct 12 16:39:46 azed-H270N systemd[1]: Started Automatically fetch and run repair assertions. Oct 12 16:49:33 azed-H270N kernel: [ 2426.455211] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [946], reason: Hang on render ring, action: reset Oct 12 16:49:33 azed-H270N kernel: [ 2426.455238] drm/i915: Resetting chip after gpu hang Oct 12 16:49:33 azed-H270N kernel: [ 2426.455284] [drm] RC6 on Oct 12 16:49:33 azed-H270N kernel: [ 2426.471991] [drm] GuC firmware load skipped Oct 12 16:49:51 azed-H270N kernel: [ 2444.435136] drm/i915: Resetting chip after gpu hang Oct 12 16:49:51 azed-H270N kernel: [ 2444.435196] [drm] RC6 on Oct 12 16:49:51 azed-H270N kernel: [ 2444.449146] [drm] GuC firmware load skipped Oct 12 16:50:11 azed-H270N kernel: [ 2464.434387] drm/i915: Resetting chip after gpu hang Oct 12 16:50:11 azed-H270N kernel: [ 2464.434449] [drm] RC6 on Oct 12 16:50:11 azed-H270N kernel: [ 2464.446462] [drm] GuC firmware load skipped Oct 12 16:50:31 azed-H270N kernel: [ 2484.433590] drm/i915: Resetting chip after gpu hang Oct 12 16:50:31 azed-H270N kernel: [ 2484.433655] [drm] RC6 on Oct 12 16:50:31 azed-H270N kernel: [ 2484.448736] [drm] GuC firmware load skipped Oct 12 16:50:49 azed-H270N kernel: [ 2502.416895] drm/i915: Resetting chip after gpu hang Oct 12 16:50:49 azed-H270N kernel: [ 2502.416960] [drm] RC6 on Oct 12 16:50:49 azed-H270N kernel: [ 2502.431102] [drm] GuC firmware load skipped Oct 12 16:51:09 azed-H270N kernel: [ 2522.416124] drm/i915: Resetting chip after gpu hang Oct 12 16:51:09 azed-H270N kernel: [ 2522.416192] [drm] RC6 on Oct 12 16:51:09 azed-H270N kernel: [ 2522.432185] [drm] GuC firmware load skipped Oct 12 16:51:24 azed-H270N kernel: [ 2537.204555] sysrq: SysRq : This sysrq operation is disabled. Oct 12 16:51:26 azed-H270N kernel: [ 2538.876556] sysrq: SysRq : This sysrq operation is disabled. Oct 12 16:51:27 azed-H270N kernel: [ 2540.500557] sysrq: SysRq : This sysrq operation is disabled. Oct 12 16:51:29 azed-H270N kernel: [ 2542.415352] drm/i915: Resetting chip after gpu hang
Questions:
Is my problem related to this bug:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574266
would upgrading to a newer version of LO from the official LO ppa help matters?
Has anyone else come across this prob?
New solution ideas?
Any help very gratefully received. LO is a key app for me. If I can't rely on it, it makes my 16.04 system virtually useless.