Bug 240566 – Crash: Problem printing some email

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 240566 - Crash: Problem printing some email


Summary:	Crash: Problem printing some email


Status:	RESOLVED DUPLICATE of bug 231551

Product:	evolution
Classification:	Applications
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	Normal major
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-03-31 14:41 UTC by chay
Modified:	2003-03-31 21:13 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description chay 2003-03-31 14:41:11 UTC

Package: Evolution
Priority: Major
Version: 1.2.3
Synopsis: Problem printing some email
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous

Description:
Description of Problem:
Problem printing some html-email

Steps to reproduce the problem:
1. Select the message
2. Select print.
3. Evolution-mail crashes

Actual Results:
I have to restart evolution

Expected Results:
Print the email

How often does this happen?
Only with one message

Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/evolution-mail'

(no debugging symbols found)...(no debugging symbols found)...[New
Thread 16384 (LWP 25138)]
[New Thread 32769 (LWP 25181)]
[New Thread 16386 (LWP 25182)]
[New Thread 32771 (LWP 25183)]
[New Thread 49156 (LWP 25186)]
[New Thread 65541 (LWP 25199)]
[New Thread 81926 (LWP 25200)]

0x403acbf4 in waitpid () from /lib/libpthread.so.0

+ Trace 35413

Thread 1 (Thread 16384 (LWP 25138))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_segv_handle
from /usr/lib/libgnomeui.so.32
#2 message_browser_get_type
#3 __pthread_sighandler
from /lib/libpthread.so.0
#4 <signal handler called>
#5 strlen
from /lib/libc.so.6
#6 t1_get_glyph_name
from /usr/lib/libfreetype.so.6
#7 FT_Get_Glyph_Name
from /usr/lib/libfreetype.so.6
#8 gff_pso_ensure_buffer_t1
from /usr/lib/libgnomeprint.so.15
#9 gnome_font_face_pso_ensure_buffer
from /usr/lib/libgnomeprint.so.15
#10 gnome_print_ps2_close
from /usr/lib/libgnomeprint.so.15
#11 gnome_print_context_close
from /usr/lib/libgnomeprint.so.15
#12 gpf_close
from /usr/lib/libgnomeprint.so.15
#13 gnome_print_context_close
from /usr/lib/libgnomeprint.so.15
#14 gnome_print_master_print
from /usr/lib/libgnomeprint.so.15
#15 preview_file_print_cmd
from /usr/lib/libgnomeprint.so.15
#16 gtk_marshal_NONE__NONE
from /usr/lib/libgtk-1.2.so.0
#17 gtk_handlers_run
from /usr/lib/libgtk-1.2.so.0
#18 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#19 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#20 gtk_button_clicked
from /usr/lib/libgtk-1.2.so.0
#21 gtk_real_button_released
from /usr/lib/libgtk-1.2.so.0
#22 gtk_marshal_NONE__NONE
from /usr/lib/libgtk-1.2.so.0
#23 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#24 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#25 gtk_button_released
from /usr/lib/libgtk-1.2.so.0
#26 gtk_button_button_release
from /usr/lib/libgtk-1.2.so.0
#27 gtk_marshal_BOOL__POINTER
from /usr/lib/libgtk-1.2.so.0
#28 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#29 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#30 gtk_widget_event
from /usr/lib/libgtk-1.2.so.0
#31 gtk_propagate_event
from /usr/lib/libgtk-1.2.so.0
#32 gtk_main_do_event
from /usr/lib/libgtk-1.2.so.0
#33 gdk_event_dispatch
from /usr/lib/libgdk-1.2.so.0
#34 g_main_dispatch
from /usr/lib/libglib-1.2.so.0
#35 g_main_iterate
from /usr/lib/libglib-1.2.so.0
#36 g_main_run
from /usr/lib/libglib-1.2.so.0
#37 gtk_main
from /usr/lib/libgtk-1.2.so.0
#38 bonobo_main
from /usr/lib/libbonobo.so.2
#39 main
#40 __libc_start_main
from /lib/libc.so.6
#0 waitpid
from /lib/libpthread.so.0



Unknown reporter: chay@asi.cl, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Gerardo Marin 2003-03-31 21:13:15 UTC

Details of fix on bug 231551

*** This bug has been marked as a duplicate of 231551 ***