Bug 236092 – Crash: printing problem

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 236092 - Crash: printing problem


Summary:	Crash: printing problem


Status:	RESOLVED DUPLICATE of bug 231551

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2002-12-24 20:34 UTC by johan
Modified:	2003-01-03 21:43 UTC

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

Description johan 2002-12-24 20:34:28 UTC

Package: Evolution
Priority: Normal
Version: 1.0.8
Synopsis: printing problem
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous

Description:
Description of Problem:
when I press print, evolution crashes 

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?
always

Additional Information:
printing works fine



Debugging Information:

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

(no debugging symbols found)...[New Thread 8192 (LWP 23470)]
[New Thread 16385 (LWP 23493)]
[New Thread 8194 (LWP 23494)]
[New Thread 16387 (LWP 23495)]
[New Thread 24580 (LWP 23498)]
[New Thread 32773 (LWP 23499)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 32020

Thread 1 (Thread 8192 (LWP 23470))

#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 preview_file_print_cmd
from /usr/lib/libgnomeprint.so.15
#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_button_clicked
from /usr/lib/libgtk-1.2.so.0
#23 gtk_real_button_released
from /usr/lib/libgtk-1.2.so.0
#24 gtk_marshal_NONE__NONE
from /usr/lib/libgtk-1.2.so.0
#25 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#26 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#27 gtk_button_released
from /usr/lib/libgtk-1.2.so.0
#28 gtk_button_button_release
from /usr/lib/libgtk-1.2.so.0
#29 gtk_marshal_BOOL__POINTER
from /usr/lib/libgtk-1.2.so.0
#30 gtk_signal_real_emit
from /usr/lib/libgtk-1.2.so.0
#31 gtk_signal_emit
from /usr/lib/libgtk-1.2.so.0
#32 gtk_widget_event
from /usr/lib/libgtk-1.2.so.0
#33 gtk_propagate_event
from /usr/lib/libgtk-1.2.so.0
#34 gtk_main_do_event
from /usr/lib/libgtk-1.2.so.0
#35 gdk_event_dispatch
from /usr/lib/libgdk-1.2.so.0
#36 g_main_dispatch
from /usr/lib/libglib-1.2.so.0
#37 g_main_iterate
from /usr/lib/libglib-1.2.so.0
#38 g_main_run
from /usr/lib/libglib-1.2.so.0
#39 gtk_main
from /usr/lib/libgtk-1.2.so.0
#40 bonobo_main
from /usr/lib/libbonobo.so.2
#41 main
#42 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6



Unknown reporter: johan@stevon.org, 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-01-03 21:43:10 UTC

Fix details on bug 231551

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