[apport] ssindex crashed with SIGSEGV

Bug #115821 reported by Omar
2
Affects Status Importance Assigned to Milestone
gnumeric (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnumeric

This errors appeared at the start of KDE. No information about which application it was or what caused the problem.

ProblemType: Crash
Architecture: i386
Date: Sat May 19 19:22:39 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/ssindex
Package: gnumeric 1.7.8-0ubuntu1
PackageArchitecture: i386
ProcCmdline: ssindex -i /home/oghanchi/backup/Case\ Logging\ Percentage.gnumeric
ProcCwd: /home/oghanchi
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
Signal: 11
SourcePackage: gnumeric
Stacktrace:
 #0 0xb7ce678b in ?? () from /usr/lib/libspreadsheet-1.7.8.so
 #1 0x0004c6d8 in ?? ()
 #2 0x4aff51c5 in ?? ()
 #3 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/libspreadsheet-1.7.8.so
 ?? ()
 ?? ()
 ?? ()
Uname: Linux oghanchi-desktop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
Omar (oghanchi) wrote :
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:gnm_style_update (style=0x806b748) at ../../src/mstyle.c:110
gnm_style_hash (style=0x806b748) at ../../src/mstyle.c:196
IA__g_hash_table_lookup (hash_table=0x8090d40, key=0x806b748) at ghash.c:231
sheet_style_find (sheet=0x8196808, s=0x806b748) at ../../src/sheet-style.c:74
rstyle_ctor (res=0xbf9f863c, new_style=0x4321404, pstyle=0x0, sheet=0x0) at ../../src/sheet-style.c:111

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Changed in gnumeric:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. Have you been able to reproduce this issue ?

Changed in gnumeric:
status: Confirmed → Incomplete
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gnumeric:
status: Incomplete → Invalid
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.