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 240286 - Evolution crashes when printing
Evolution crashes when printing
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
: 240981 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-03-25 21:27 UTC by Unknown Bug Buddy Submitter
Modified: 2003-04-09 17:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Unknown Bug Buddy Submitter 2003-03-25 21:27:51 UTC 
Package: Evolution
Priority: Normal
Version: 1.2.2
Synopsis: Evolution crashes when printing
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Description of Problem:
Evolution crashes, when I try to print an email. Not every email-print
by evolution crashes, this is the first time I found such an email.
But with that email, it is reproduceable. The email has no attachement
and (as it seems) no special characters, size is approx. 1kB.

Steps to reproduce the problem:
1. select email
2. press print-button
3. press ok-button
4. crash dialog-box appears

Actual Results:
email is not printed, and email folders are no more accessible until a
restart of evolution.

Expected Results:
email should be printed.


How often does this happen?
Every time with this email. It is the only email I had this effect until
now.

Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x403f55ca in waitpid ()
   from /lib/libpthread.so.0

+ Trace 35263

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_segv_handle
    from /usr/lib/libgnomeui.so.32
  • #2 message_browser_get_type
  • #3 __pthread_clock_settime
    from /lib/libpthread.so.0
  • #4 killpg
    from /lib/libc.so.6
  • #5 FT_Get_Glyph_Name
    from /usr/lib/libfreetype.so.6
  • #6 gff_pso_ensure_buffer_t1
    from /usr/lib/libgnomeprint.so.15
  • #7 gnome_font_face_pso_ensure_buffer
    from /usr/lib/libgnomeprint.so.15
  • #8 gnome_print_ps2_close
    from /usr/lib/libgnomeprint.so.15
  • #9 gnome_print_context_close
    from /usr/lib/libgnomeprint.so.15
  • #10 gpf_close
    from /usr/lib/libgnomeprint.so.15
  • #11 gnome_print_context_close
    from /usr/lib/libgnomeprint.so.15
  • #12 gnome_print_master_print
    from /usr/lib/libgnomeprint.so.15
  • #13 vfolder_edit_vfolders
  • #14 impl_Bonobo_UIComponent_execVerb
    from /usr/lib/libbonobox.so.2
  • #15 _ORBIT_skel_Bonobo_UIComponent_execVerb
    from /usr/lib/libbonobo.so.2
  • #16 ORBit_POA_handle_request
    from /usr/lib/libORBit.so.0
  • #17 ORBit_handle_incoming_request
    from /usr/lib/libORBit.so.0
  • #18 giop_main_handle_connection
    from /usr/lib/libIIOP.so.0
  • #19 OAF_ActivationContext_ParseFailed__alloc
    from /usr/lib/liboaf.so.0
  • #20 g_io_unix_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #21 g_main_dispatch
    from /usr/lib/libglib-1.2.so.0
  • #22 g_main_iterate
    from /usr/lib/libglib-1.2.so.0
  • #23 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #24 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #25 bonobo_main
    from /usr/lib/libbonobo.so.2
  • #26 main
  • #27 __libc_start_main
    from /lib/libc.so.6 


Unknown reporter: eschmann@uni-frankfurt.de, 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 Rodney Dawes 2003-04-09 14:59:52 UTC 
*** bug 240981 has been marked as a duplicate of this bug. ***
Comment 2 Gerardo Marin 2003-04-09 17:06:25 UTC 
Details of fix on bug 231551

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