system crashes (freezes) while LibreOffice is running

[Ringelkrat]

While libreoffice is running, the whole system crashes randomly. There is no regularity and it happens at least with libreoffice writer, calc, draw and impress. It happens, even when the libreoffice window is not focused or on top of other windows. Sometimes it happens after minutes, sometimes after hours. I can not see any relation to the functions I use in libreoffice. It happens also, when working with some very basic spreadsheets without importing pictures, graphs or whatsoever.
Also, I can not detect any significant changes in CPU or memory usage, just before it happens.

I can only tell, that it might be a bug in libreoffice, as this only happens while libreoffice is running. I am observing this for about half a year now.

The symptoms:
 * Everything is frozen. The windows and buttons do not react any more. Actually I think the mouse disappears (I am not sure on that).
 * I can not change to an other terminal.
 * I case some sound or music was playing it continues.
 * I can not restart X via CTRL+ALT+BACKSPACE any more
The only thing I can do is to switch off my computer (by pressing the power button for a long time).

This bug makes libreoffice unreliable on this system and working with it can be quite frustrating, as all unsaved changes are lost!

$lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04
$apt-cache policy libreoffice
libreoffice:
  Installiert: (keine)
  Kandidat: 1:3.3.4-0ubuntu1
  Versionstabelle:
     1:3.3.4-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ natty-updates/universe amd64 Packages
     1:3.3.2-1ubuntu4 0
        500 http://de.archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: libreoffice-core 1:3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-13.55-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Mon Feb 27 02:01:11 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to natty on 2011-09-25 (154 days ago)
---
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
DistUpgraded: Log time: 2011-09-25 16:06:46.298574
DistroCodename: natty
DistroRelease: Ubuntu 11.04
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 5.100.82.38+bdcom, 2.6.38-12-generic, x86_64: installed
 bcmwl, 5.100.82.38+bdcom, 2.6.38-13-generic, x86_64: installed
 bcmwl, 5.100.82.38+bdcom, 2.6.38-11-generic, x86_64: installed
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:161d]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Hewlett-Packard HP ProBook 6460b
NonfreeKernelModules: wl
Package: xorg 1:7.6+4ubuntu3.2
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=de_DE:en
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-13-generic root=UUID=591551af-239b-442e-a423-f8ee2f1975c5 ro vga=799 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-13.55-generic 2.6.38.8
Renderer: Unknown
Tags: natty ubuntu compiz-0.9
Uname: Linux 2.6.38-13-generic x86_64
UpgradeStatus: Upgraded to natty on 2011-09-25 (154 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/27/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SCE Ver. F.03
dmi.board.name: 161D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 97.40
dmi.chassis.asset.tag: CNU1234JXQ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.03:bd04/27/2011:svnHewlett-Packard:pnHPProBook6460b:pvrA0001D02:rvnHewlett-Packard:rn161D:rvrKBCVersion97.40:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 6460b
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2
version.ia32-libs: ia32-libs 20090808ubuntu13
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2.1
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

[penalvch (penalvch)]

Ringelkrat, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 941708

Could you please execute and attach the results to this bug:
lspci -nn | grep VGA

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

apport information

[Ringelkrat (ringelkrat)]

Please notice, that the debug information I just added, has not been recorded just after a crash, as I just restarted my system. But I have been asked to add this kind of debugging information in comment #2. Also I have been asked to attach this information:
$lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)

Shall I submit this debug information again, just after a crash, or is it not relevant? As the crash does not appear regularly, and I avoid to use libreoffice, because of it's annoying behaviour, it might take a while (weeks?) until I can provide this information.

[penalvch (penalvch)]

Ringelkrat, the next step is to attach all relevant information noted in:
https://help.ubuntu.com/community/DebuggingSystemCrash
https://wiki.ubuntu.com/X/Debugging

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

[Ringelkrat (ringelkrat)]

I tried to execute the reporting procedure from [1, 2] and especially [3]:

Nothing has been logged in kern.log during occurrence of the crash. The last logs were from the reboot process, which was necessary after the crash. The messages before were logged long before the system froze.

Xorg.0.log seem to be reset at reboot. Thus I can not tell if something has been written there before the final freezing.

When the system crashes (freeze), I can not switch to a terminal (via CTRL+ALT+F1). Thus I can not save a trace dump. But I noticed, that I can still move the mouse, although the rest of the screen is frozen. At the moment I have no second machine available, which I could use to inspect the "sick" machine via ssh.

I did a memtest just in case, which passed (1/1).

I future I might use the following commands while using libreoffice:
sudo tail -f /proc/kmsg &> kmsg &
tail -f /var/log/syslog &> syslog &
tail -f /var/log/Xorg.0.log &
To log further details, if it helps. But as I said, I do not use libreoffice this often, thus it might take a while until I deliver this data. Remember that this issue does only occur while using libreoffice.

[1] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/941708/comments/29
[2] https://help.ubuntu.com/community/DebuggingSystemCrash
[3] https://wiki.ubuntu.com/X/Reporting

[Ringelkrat (ringelkrat)]

Libreoffice crashed again and my system "froze". I was running the commands I announced yesterday in order to log any messages. Unfortunately there was no message recorded close (time) to the occurrence of the failure. Maybe these commands are not suitable?

sudo tail -f /proc/kmsg &> kmsg &
tail -f /var/log/syslog &> syslog &
tail -f /var/log/Xorg.0.log &

The only option left I see to acquire more information regarding this malfunction, is to login into my machine during the crash via ssh and get a task dump. Although I do not know if this is actually possible, as the ssh service might crash as well? As this would demand a lot of work with my equipment available, I will only continue in case anybody thinks it is promising. Or advises me to gather information otherwise.

Until then I will rest my effort, as I lost hope.

[Ringelkrat (ringelkrat)]

I had the possibility to use a second machine to log myself in while libreoffice crashed again. I killed all libreoffice processes and restarted gdm. Without success. What else could I try? There was nothing interesting in Xorg.0.log: Only the commands from the boot process and this line: XKB: reuse xkmfile /var/lib/xkb/server-CAE9F94AD0857228BEC3B96F0E73BC5E4CBF4CE2.xkm

What else can I try?

[penalvch (penalvch)]

Ringelkrat, you may be having a kernel oops. If so, could you please capture it following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Capturing_OOPs ?

[Ringelkrat (ringelkrat)]

As the version of Ubuntu (11.04) is not supported any more, I have installed Ubuntu 12.04 LTS. The VGA controller is still the same. Since then I have not experienced this bug any more. But as already said, it only occured sporadically. So I can not confirm that this bug is resolved. In case this bug report expires, the resason might be the clean install (of the new version).

[Launchpad Janitor (janitor)]

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.]

[Hotteterre (luca-rossetto)]

I'm experimenting the same bug on Ubuntu 13.10 with Nvidia proprietary drivers. If any of LibreOffice applications is running, after a while the system freezes.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Ringelkrat, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/941708/comments/35 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Hotteterre, so your hardware may be tracked, could you please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

[Hotteterre (luca-rossetto)]

Yes, here it is:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261237