soffice.bin crashed with SIGSEGV after closing all files

Bug #600118 reported by Cesare Mastroianni
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
openoffice.org (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: openoffice.org

Hi there. Thanks You all in advance for Your help.

Some now and then, when I quit OpenOffice after having close all files, I got a SIGSEGV crash. The crash alert pops up after some time I quit OO (more or less 10 seconds). The attached info have been automatically collected by the apport procedure.

Unfortunately, so far I was not able to reproduce the bug in a deterministic way: it happens under unknown circumstances. Moreover, the crash happens only while (after) quitting the program.

I recently installed all the -dbgsym packages needed to full trace the bug. From now on I will run office from "inside" gdb, and I hope to capture a valid report. In the meantime, please, have a look to the attached info.

Ciao
CM

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: openoffice.org-core 1:3.2.0-7ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Jun 30 09:06:10 2010
Disassembly: => 0x7f1e5efdced9: Cannot access memory at address 0x7f1e5efdced9
ExecutablePath: /usr/lib/openoffice/program/soffice.bin
ProcCmdline: /usr/lib/openoffice/program/soffice.bin -calc /home/username/.gvfs/username\ su\ sciallino-srv/Protocollo/Rubrica/rubrica-generale.xls -splash-pipe=5
ProcEnviron:
 LANGUAGE=it_IT:it:en_GB:en
 PATH=(custom, no user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1e5efdced9: Cannot access memory at address 0x7f1e5efdced9
 PC (0x7f1e5efdced9) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: openoffice.org
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: soffice.bin crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Cesare Mastroianni (cece) wrote :
visibility: private → public
Revision history for this message
Cesare Mastroianni (cece) wrote :

Today I was lucky (or unlucky) enough to detect a crash of OpenOffice running "inside" GDB.

See attached files.

Thank You in advance for Your help.

Ciao
CM

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Changed in openoffice.org (Ubuntu):
status: New → Fix Released
Revision history for this message
Cesare Mastroianni (cece) wrote :

<email address hidden> :: what does it mean "Fix Released"?

I didn't find any package upgrade after July 5th. Furthermore, I still I experienced some SIGSEGV crashes. Unfortunately the crashes happened when I was using OpenOffice alone (not from "inside" a gdb session). After the last crash, I run OpenOffice with gdb and I only got a SIGPIPE, which didn't cause a crash: it cause only a temporary stop (see attached TXT file).

I hope to be lucky enough to capture the SIGSEGV event from gdb, I hope soon ...

Ciao
CM

Changed in openoffice.org (Ubuntu):
status: Fix Released → New
Colan Schwartz (colan)
Changed in openoffice.org (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Cesare Mastroianni, thank you for reporting this bug and helping make Ubuntu better. Could you please attach the Calc file you were closing when this problem occurred? Does this problem occur for you in LibreOffice Calc?

sudo add-apt-repository ppa:libreoffice/ppa && sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install libreoffice-calc

Changed in openoffice.org (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Cesare Mastroianni (cece) wrote :

Dear Christopher,

I'd like to help You, but unfortunately the original crash happened on June 30th 2010, and I cannot remember which file was last opened. Since then, I experienced this bug almost daily, with many different files. Therefore, on September I decided to hard attack the problem and I spent a whole weekend trying to catch the situation running OpenOffice from "inside" gdb. However, incredible to say, I noticed that OpenOffice never crashes this way when ran from "inside" gdb!

So I'm actually unable to understand what to do to catch the bug.

I never used LibreOffice at all. I suppose that OpenOffice is the official office suite for Ubuntu, isn't it? On the other way, I reported an existing problem (almost daily crash events!) of OpenOffice ...

How could I help You to identify the crash reason?

Ciao
CM

Changed in openoffice.org (Ubuntu):
status: Incomplete → New
Revision history for this message
penalvch (penalvch) wrote :

Cesare Mastroianni, regarding your comment:

> How could I help You to identify the crash reason?

Test using LibreOffice. If it crashes, attach the Calc file(s) you were working on, mention the programs you were running at the time of the crash, and how to reproduce the crash.

Changed in openoffice.org (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openoffice.org (Ubuntu) because there has been no activity for 60 days.]

Changed in openoffice.org (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.