Bug 233857 – Crashes when printing a message

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 233857 - Crashes when printing a message


Summary:	Crashes when printing a message


Status:	RESOLVED DUPLICATE of bug 231551

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-11-13 09:16 UTC by rkm
Modified:	2002-11-13 19:04 UTC

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

Description rkm 2002-11-13 09:16:07 UTC

Package: Evolution
Priority: Critical
Version: 1.0.8
Synopsis: Crashes when printing a message
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Description of Problem:
I choose the message and try to print it but evolution stay out of
order

Steps to reproduce the problem:
1. Check the printer status 
2. Made print of diferent message 
3. 

Actual Results:
it still doesn't work 

Expected Results:
Reliable printing

How often does this happen?
it is random on selected message


Additional Information:
Printing for another mail cliant as kmail and OpenOffice is not cause
any problem




Debugging Information:

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

(no debugging symbols found)...[New Thread 8192 (LWP 3211)]
[New Thread 16385 (LWP 3242)]
[New Thread 8194 (LWP 3243)]
[New Thread 16387 (LWP 3244)]
[New Thread 24580 (LWP 3247)]
[New Thread 40965 (LWP 3250)]
[New Thread 188422 (LWP 3287)]
[New Thread 172040 (LWP 3285)]
[New Thread 204810 (LWP 3289)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 30289

Thread 1 (Thread 8192 (LWP 3211))

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



Unknown reporter: rkm@gask.pl, 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 2002-11-13 19:04:22 UTC


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