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 239683 - Crash: Segmentation Violation trying to print e-mail message
Crash: Segmentation Violation trying to print e-mail message
Status: RESOLVED DUPLICATE of bug 231551
Product: evolution
Classification: Applications
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-03-13 19:33 UTC by jerry
Modified: 2003-03-15 01:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jerry 2003-03-13 19:33:47 UTC 
Package: Evolution
Priority: Normal
Version: 1.0.8
Synopsis: Segmentation Violation trying to print e-mail message
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous

Description:
Description of Problem:
Evolution crashes when trying to print e-mail messages

Steps to reproduce the problem:
1. highlight an e-mail message
2. click on file-print
3. when printer window opens click print

Actual Results:
Crashes with a segmentation violation

Expected Results:
Should print document

How often does this happen?
This isn't something that happens everytime. Once it happens I am unable
to print from evolution for it seems days. Then poof it works again. I
have tried rebooting, but it doesn't help. Just one day it will
work..yesterday it worked today not.

Additional Information:
Running RH 8.0 with the most up-to-date kernel ( Linux ftp2.fptech.net
2.4.18-26.8.0 )



Debugging Information:

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

(no debugging symbols found)...[New Thread 8192 (LWP 20769)]
[New Thread 16385 (LWP 20800)]
[New Thread 8194 (LWP 20801)]
[New Thread 16387 (LWP 20802)]
[New Thread 24580 (LWP 20805)]
[New Thread 40965 (LWP 20810)]
[New Thread 507910 (LWP 21439)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 34868

Thread 1 (Thread 8192 (LWP 20769))

  • #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 impl_Bonobo_UIComponent_execVerb
    from /usr/lib/libbonobox.so.2
  • #19 _ORBIT_skel_Bonobo_UIComponent_execVerb
    from /usr/lib/libbonobo.so.2
  • #20 ORBit_POA_handle_request
    from /usr/lib/libORBit.so.0
  • #21 ORBit_handle_incoming_request
    from /usr/lib/libORBit.so.0
  • #22 giop_main_handle_connection
    from /usr/lib/libIIOP.so.0
  • #23 orb_handle_connection
    from /usr/lib/liboaf.so.0
  • #24 g_io_unix_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #25 g_main_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #26 g_main_iterate
    from /usr/lib/libglib-1.2.so.0
  • #27 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #28 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #29 bonobo_main
    from /usr/lib/libbonobo.so.2
  • #30 main
  • #31 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6 


Unknown reporter: jerry@fptech.net, 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-15 01:14:36 UTC 
Details of fix on bug 231551

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