kspread crashed with SIGSEGV

Bug #448244 reported by Mikael Bergqvist
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
koffice
Invalid
High
koffice (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: koffice

Tried to open a .ksp file with kspread from koffice-kde4. The spread sheet was made with the previous version of kspread.
I deinstalled koffice-kde4, and installed koffice instead.

ProblemType: Crash
Architecture: i386
Date: Sat Oct 10 21:39:45 2009
Disassembly: 0x30a77a0: Cannot access memory at address 0x30a77a0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kspread
Package: kspread 1:1.6.3-7ubuntu10
ProcCmdline: kspread
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=sv_SE.UTF-8
 LANGUAGE=sv_SE:sv:en_GB:en
ProcVersionSignature: Ubuntu 2.6.31-13.43-generic
SegvAnalysis:
 Segfault happened at: 0x30a77a0: Cannot access memory at address 0x30a77a0
 PC (0x030a77a0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: koffice
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: kspread crashed with SIGSEGV
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:1837): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Mikael Bergqvist (mikaelb) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:KSpread::Style::parentName (this=0x0)
KSpread::StyleManager::loadXML (this=0x9a9f8a0,
KSpread::Doc::loadXML (this=0x9aad898, doc=@0xbfdf08a8)
KoDocument::loadNativeFormatFromStoreInternal (
KoDocument::loadNativeFormatFromStore (this=0x9aad898,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in koffice (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Should be fixed in KOffice 2.1.

visibility: private → public
Changed in koffice (Ubuntu):
status: New → Fix Released
Changed in koffice:
status: Unknown → Invalid
Changed in koffice:
importance: Unknown → High
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.