Ubuntu
gnumeric package

gnumeric crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

Bug #537190 reported by Mike Linksvayer
96
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTK+
Expired
Medium
gnumeric (Ubuntu)
Invalid
Medium
Unassigned
gtk+2.0 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnumeric

$ lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

$ apt-cache policy gnumeric
gnumeric:
  Installed: 1.10.0-1ubuntu1
  Candidate: 1.10.0-1ubuntu1
  Version table:
 *** 1.10.0-1ubuntu1 0
        500 http://us.archive.ubuntu.com lucid/universe Packages
        100 /var/lib/dpkg/status

I was using gnumeric and didn't expect it to crash.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Mar 11 00:46:23 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gnumeric
Package: gnumeric 1.10.0-1ubuntu1
ProcCmdline: gnumeric
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-15.22-generic
SegvAnalysis:
 Segfault happened at: 0x488a7a: fldl 0x18(%ecx)
 PC (0x00488a7a) ok
 source "0x18(%ecx)" (0x00000018) not located in a known VMA region (needed readable region)!
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnumeric
StacktraceTop:
 ?? () from /usr/lib/libspreadsheet-1.10.0.so
 ?? () from /usr/lib/libspreadsheet-1.10.0.so
 _gtk_marshal_BOOLEAN__BOXED (closure=0x8128410,
 g_type_class_meta_marshal (closure=0x8128410,
 IA__g_closure_invoke (closure=0x8128410,
Title: gnumeric crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Uname: Linux 2.6.32-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
Mike Linksvayer (ml-gondwanaland) wrote :
visibility: private → public
Revision history for this message
Jean Bréfort (jean-brefort-normalesup) wrote :

stack trace does not show any code from gnumeric. Loos like a signal issue. What were you doing exactly? I'm using gnumeric every day and it does not crash. Might be related with the use of gtk+-2.19.x.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Please keep bugs with the coredump attached private until after the apport team has completed the retrace actions. Thanks.

visibility: public → private
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 set_destination (icon_view=0xbfa42074, context=0xbfa420b8,
 g_value_set_boxed () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnumeric (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please provide the requested information (see comment #2 above)? Thanks!

visibility: private → public
Changed in gnumeric (Ubuntu):
status: New → Incomplete
Revision history for this message
Andreas J Guelzow (aguelzow) wrote :

According to the stack trace of comment #5, gtk_icon_view_get_dest_item_at_pos was called with a valid GtkIconVIew two valid integers for drag_x and drag_y and two arguments that are NULL (as permitted by the documentation). The crash happens 24 layers deeper in gtk.

I think this bug should be considered a gtk bug.

Revision history for this message
Andreas J Guelzow (aguelzow) wrote :

The only gnumeric code in all of this is (in main (argc=1, argv=0xbfa42ca4) at ../../src/main-application.c:457):

  gtk_main ();

The arguments to this call are surely correct.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for so much help with this bug. I added gtk to "Affects" and will forward the bug upstream.

Changed in gnumeric (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=614499

Changed in gtk+2.0 (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gtk:
status: Unknown → New
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

According to upstream, the attached stacktrace is not good. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gtk+2.0 (Ubuntu):
status: Triaged → Incomplete
Bug Watch Updater (bug-watch-updater)
Changed in gtk:
importance: Unknown → Medium
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

According to upstream, the attached stacktrace is not good. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Revision history for this message
Charlie Kravetz (cjkgeek) 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 (Ubuntu):
status: Triaged → Invalid
Changed in gtk+2.0 (Ubuntu):
status: Incomplete → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in gtk:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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