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 236129 - Crash: sigsegv on print GB-2312 encoded email to PS printer
Crash: sigsegv on print GB-2312 encoded email to PS printer
Status: RESOLVED DUPLICATE of bug 231551
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-12-27 11:13 UTC by nettleton
Modified: 2003-01-03 22:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description nettleton 2002-12-27 11:13:23 UTC 
Package: Evolution
Priority: Normal
Version: 1.2.0
Synopsis: sigsegv on print GB-2312 encoded email to PS printer
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Description of Problem:

Email from China, encoded as attachments using GB-2312 character
encoding but
aparantly not including any non-ASCII characters causes an immediate
sigsegv on print.
Other emails print OK.

Steps to reproduce the problem:
1. Select email
2. Print
3. 

Actual Results:

Crash

Expected Results:


How often does this happen?

Every time

Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...[New
Thread 8192 (LWP 17501)]
[New Thread 16385 (LWP 17552)]
[New Thread 8194 (LWP 17553)]
[New Thread 16387 (LWP 17554)]
[New Thread 24580 (LWP 17557)]
[New Thread 32773 (LWP 17559)]
[New Thread 40966 (LWP 17566)]
[New Thread 49159 (LWP 17567)]
[New Thread 57352 (LWP 17568)]
[New Thread 65545 (LWP 17569)]
[New Thread 73738 (LWP 17570)]

0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 32075

Thread 1 (Thread 8192 (LWP 17501))

  • #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 message_browser_get_type
  • #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 vfolder_edit_vfolders
  • #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: nettleton@xgc.com, 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 22:26:17 UTC 
Fix details on bug 231551

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