soffice.bin crashed with SIGSEGV in g_hash_table_lookup()

Bug #847013 reported by Carl Ansell
This bug report is a duplicate of:  Edit Remove
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Was trying to close a print preview when the crash occured.

Ubuntu 11.10
LibreOffice 3.4.2-2ubuntu3

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libreoffice-core 1:3.4.2-2ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
Date: Sun Sep 11 14:06:35 2011
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer /home/username/Documents/School\ Work/Chemistry/Van\ der\ Waals\ Forces.odt --splash-pipe=7
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: libreoffice
StacktraceTop:
 ?? ()
 g_hash_table_lookup () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libreoffice/program/../share/extensions/menubar/Linux_x86/menubar.uno.so
 ?? () from /usr/lib/libreoffice/program/../basis-link/program/libsfxli.so
 ?? () from /usr/lib/libreoffice/program/../basis-link/program/libsfxli.so
Title: soffice.bin crashed with SIGSEGV in g_hash_table_lookup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Carl Ansell (afccarl1994) wrote :
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libreoffice (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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