plucker crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

Bug #351087 reported by Leslie Johnson
6
Affects Status Importance Assigned to Milestone
plucker (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: plucker

Tried to open an ebook Palm ".pdb" file, and it crashed. As far as I know, the file is not corrupt.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/plucker
Package: plucker 1.8-29
ProcCmdline: plucker crows.pdb
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: plucker
StacktraceTop:
 ?? ()
 _gtk_marshal_BOOLEAN__BOXED (closure=0x8600bc0,
 IA__g_closure_invoke (closure=0x8600bc0,
 signal_emit_unlocked_R (node=0x84e4cc8, detail=0,
 IA__g_signal_emit_valist (instance=0x8517020, signal_id=30,
Title: plucker crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner vboxusers video

Revision history for this message
Leslie Johnson (bithits) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:MouseClickCallback (widget=0x8517020, event=0x84e06a0,
_gtk_marshal_BOOLEAN__BOXED (closure=0x8600bc0,
IA__g_closure_invoke (closure=0x8600bc0,
signal_emit_unlocked_R (node=0x84e4cc8, detail=0,
IA__g_signal_emit_valist (instance=0x8517020, signal_id=30,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
visibility: private → public
Changed in plucker (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Ludovic Rousseau (ludovic-rousseau-gmail) wrote :

Can you include the crows.pdb file causing the problem so I can try to reproduce the bug?

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.