Evolution crash with SIGABRT when printing email out of range

Bug #292172 reported by Sami Pesonen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GtkHTML
Fix Released
Critical
gtk+2.0 (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

With Evolution 2.24.1 in Ubuntu 8.10 with latest updates if I open short email and (originally by accident) print e.g. pages 4-5 (even though email is only 1 page long) Evolution crashes with SIGABRT. If I print to file it seems to work but if I have real printer e.g. Epson Stylus C65 it crashes every time.

Installed evolution with debug symbols and collected backtrace as in instructions. Also screen shot about the print dialog attached.

Revision history for this message
Sami Pesonen (sampeson) wrote :
Revision history for this message
Sami Pesonen (sampeson) wrote :

added print dialog

Revision history for this message
Anthony Noto (angusthefuzz) wrote :

Thank you for filing a bug report and helping to make Ubuntu better. Are you able to print properly from other programs?

Revision history for this message
Sami Pesonen (sampeson) wrote :

I'm able to print from Evolution also but if I choose out of range pages then it will crash. If I print out of range in gedit it will get to forever loop but not crash. I report separate bug report about that...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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 evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sami Pesonen (sampeson) wrote :

It is there already in the original bug report, see gdb-evolution.txt

Revision history for this message
Sebastien Bacher (seb128) wrote :

the stacktrace has no debug symbol could you install the dbg variants and get a new one?

Revision history for this message
Sami Pesonen (sampeson) wrote :

new backtrace after installing dbg packages for glibc, libgtk,libgtkhtml,...

Revision history for this message
Sebastien Bacher (seb128) wrote :

the stacktrace has still no gtkhtml debug symbols

Revision history for this message
Sami Pesonen (sampeson) wrote :

...practice makes expert. Should be ok backtrace now.

Revision history for this message
Sami Pesonen (sampeson) wrote :

Is it ok now or is this bug still incomplete?

Changed in evolution:
status: Incomplete → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Yes it's ok now, will look upstream, thanks Sami.

Changed in evolution:
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

I've sent this upstream at: http://bugzilla.gnome.org/show_bug.cgi?id=561675 ; thanks for reporting.

Changed in gtkhtml3.14:
status: Confirmed → Triaged
Revision history for this message
Pedro Villavicencio (pedro) wrote :

this bug has been fixed upstream, also re assigning to gtk+, thanks.

Changed in gtk+2.0:
status: Triaged → Fix Committed
Changed in gtkhtml:
status: Unknown → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

the intrepid gtk version is supposed to have the fix for this issue, what gtk version do you use?

Revision history for this message
Jonathan Ernst (jonathan.ernst) wrote :

still crashes in jaunty (libgtk2.0-0 2.14.5-1ubuntu2)

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is fixed in jaunty now

Changed in gtk+2.0:
status: Fix Committed → Fix Released
Changed in gtkhtml:
importance: Unknown → Critical
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.