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 573213 - crash in Evolution Mail and Calendar: Clicked on File -> Print...
crash in Evolution Mail and Calendar: Clicked on File -> Print...
Status: RESOLVED DUPLICATE of bug 569892
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
: 573214 573215 573216 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-02-26 01:29 UTC by Aron Hsiao
Modified: 2009-02-26 03:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Aron Hsiao 2009-02-26 01:29:50 UTC 
What were you doing when the application crashed?
Clicked on File -> Print to print a message. Have now repeated three times; always crashes when clicking File -> Print. Just switched to evolution, so no previous experience with printing.


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.15 #3 PREEMPT Wed Feb 11 06:17:37 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Shiki-Human
Icon Theme: gnome-brave

Memory status: size: 156962816 vsize: 156962816 resident: 39931904 share: 22138880 rss: 39931904 rss_rlim: 18446744073709551615
CPU usage: start_time: 1235611670 rtime: 226 utime: 214 stime: 12 cutime:2 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb7ff0980 (LWP 31829)]
[New Thread 0xb5d62b90 (LWP 31923)]
[New Thread 0xb75e2b90 (LWP 31922)]
[New Thread 0xb6de1b90 (LWP 31874)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 212910

Thread 1 (Thread 0xb7ff0980 (LWP 31829))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 segv_redirect
    at main.c line 414
  • #8 <signal handler called>
  • #9 IA__g_object_ref
    at gobject.c line 2335
  • #10 gtk_grab_notify_foreach
    at gtkmain.c line 1702
  • #11 gtk_bin_forall
    at gtkbin.c line 128
  • #12 IA__gtk_container_forall
    at gtkcontainer.c line 1455
  • #13 gtk_grab_notify_foreach
    at gtkmain.c line 1705
  • #14 gtk_grab_notify
    at gtkmain.c line 1764
  • #15 IA__gtk_grab_add
    at gtkmain.c line 1793
  • #16 gtk_window_show
    at gtkwindow.c line 4345
  • #17 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #18 g_type_class_meta_marshal
    at gclosure.c line 878
  • #19 IA__g_closure_invoke
    at gclosure.c line 767
  • #20 signal_emit_unlocked_R
    at gsignal.c line 3174
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #22 IA__g_signal_emit
    at gsignal.c line 3034
  • #23 IA__gtk_widget_show
    at gtkwidget.c line 3003
  • #24 IA__gtk_dialog_run
    at gtkdialog.c line 1039
  • #25 _gtk_print_operation_platform_backend_run_dialog
    at gtkprintoperation-unix.c line 745
  • #26 IA__gtk_print_operation_run
    at gtkprintoperation.c line 2549
  • #27 html_engine_print_operation_run
    at htmlengine-print.c line 514
  • #28 gtk_html_print_operation_run
    at gtkhtml.c line 6098
  • #29 emfhp_complete
    at em-format-html-print.c line 190
  • #30 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #31 IA__g_closure_invoke
    at gclosure.c line 767
  • #32 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #33 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #34 IA__g_signal_emit_by_name
    at gsignal.c line 3071
  • #35 efh_format_done
    at em-format-html.c line 1338
  • #36 mail_msg_idle_cb
    at mail-mt.c line 500
  • #37 g_idle_dispatch
    at gmain.c line 4235
  • #38 g_main_dispatch
    at gmain.c line 2144
  • #39 IA__g_main_context_dispatch
    at gmain.c line 2697
  • #40 g_main_context_iterate
    at gmain.c line 2778
  • #41 IA__g_main_loop_run
    at gmain.c line 2986
  • #42 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #43 main
    at main.c line 690 


----------- .xsession-errors (18 sec old) ---------------------
(evolution:30755): camel-WARNING **: Could not open converter for 'X-UNKNOWN' to 'UTF-8' charset
[Thu, 26 Feb 2009 01:17:44 GMT] FATAL An error occurred trying to check the url on location change.
[TypeError] aURI is null
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:31187): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:31187): DEBUG: mailto URL program: evolution
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4c00002 specified for 0x4c00086 (KMail).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5600004 specified for 0x5600002 (kres-migra).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5600004 specified for 0x56015af (KResource ).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4c00004 specified for 0x4c00c2d (New Book -).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5a00004 specified for 0x5a00002 (KMailCVT I).
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:31829): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:31829): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Akhil Laddha 2009-02-26 03:38:29 UTC 
*** Bug 573214 has been marked as a duplicate of this bug. ***
Comment 2 Akhil Laddha 2009-02-26 03:38:37 UTC 
*** Bug 573215 has been marked as a duplicate of this bug. ***
Comment 3 Akhil Laddha 2009-02-26 03:39:25 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 569892 ***
Comment 4 Akhil Laddha 2009-02-26 03:40:35 UTC 
*** Bug 573216 has been marked as a duplicate of this bug. ***