Bug 494827 – crash in Email: opening calendar in evol...

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 494827 - crash in Email: opening calendar in evol...


Summary:	crash in Email: opening calendar in evol...


Status:	RESOLVED DUPLICATE of bug 436128

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

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-08 02:17 UTC by koshinsky
Modified:	2007-11-08 16:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description koshinsky 2007-11-08 02:17:07 UTC

Version: 2.10

What were you doing when the application crashed?
opening calendar in evolution


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Solaris
Icon Theme: Iris

Memory status: size: 171732992 vsize: 171732992 resident: 57581568 share: 41984000 rss: 57581568 rss_rlim: 4294967295
CPU usage: start_time: 1194488107 rtime: 576 utime: 525 stime: 51 cutime:56 cstime: 22 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209043232 (LWP 13676)]
[New Thread -1276044400 (LWP 13699)]
[New Thread -1254671472 (LWP 13696)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 176211

Thread 1 (Thread -1209043232 (LWP 13676))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libpango-1.0.so.0
#11 ??
from /usr/lib/libpango-1.0.so.0
#12 g_object_unref
from /lib/libgobject-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib/libgtk-x11-2.0.so.0
#38 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#39 ??
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_socket_add_id
from /usr/lib/libgtk-x11-2.0.so.0
#45 bonobo_socket_add_id
from /usr/lib/libbonoboui-2.so.0
#46 bonobo_control_frame_get_remote_window
from /usr/lib/libbonoboui-2.so.0
#47 ??
from /usr/lib/libbonoboui-2.so.0
#48 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#49 ??
from /lib/libgobject-2.0.so.0
#50 g_closure_invoke
from /lib/libgobject-2.0.so.0
#51 ??
from /lib/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#53 g_signal_emit
from /lib/libgobject-2.0.so.0
#54 gtk_widget_realize
from /usr/lib/libgtk-x11-2.0.so.0
#55 gtk_widget_map
from /usr/lib/libgtk-x11-2.0.so.0
#56 ??
from /usr/lib/libgtk-x11-2.0.so.0
#57 ??
from /usr/lib/libgtk-x11-2.0.so.0
#58 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#59 ??
from /usr/lib/libgtk-x11-2.0.so.0
#60 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#61 ??
from /lib/libgobject-2.0.so.0
#62 g_closure_invoke
from /lib/libgobject-2.0.so.0
#63 ??
from /lib/libgobject-2.0.so.0
#64 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#65 g_signal_emit
from /lib/libgobject-2.0.so.0
#66 gtk_widget_map
from /usr/lib/libgtk-x11-2.0.so.0
#67 ??
from /usr/lib/libgtk-x11-2.0.so.0
#68 ??
from /usr/lib/libgtk-x11-2.0.so.0
#69 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#70 ??
from /usr/lib/libgtk-x11-2.0.so.0
#71 ??
from /usr/lib/libgtk-x11-2.0.so.0
#72 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#73 ??
from /lib/libgobject-2.0.so.0
#74 g_closure_invoke
from /lib/libgobject-2.0.so.0
#75 ??
from /lib/libgobject-2.0.so.0
#76 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#77 g_signal_emit
from /lib/libgobject-2.0.so.0
#78 gtk_widget_map
from /usr/lib/libgtk-x11-2.0.so.0
#79 ??
from /usr/lib/libgtk-x11-2.0.so.0
#80 ??
from /usr/lib/libgtk-x11-2.0.so.0
#81 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#82 ??
from /usr/lib/libgtk-x11-2.0.so.0
#83 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#84 ??
from /lib/libgobject-2.0.so.0
#85 g_closure_invoke
from /lib/libgobject-2.0.so.0
#86 ??
from /lib/libgobject-2.0.so.0
#87 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#88 g_signal_emit
from /lib/libgobject-2.0.so.0
#89 gtk_widget_map
from /usr/lib/libgtk-x11-2.0.so.0
#90 gtk_widget_set_child_visible
from /usr/lib/libgtk-x11-2.0.so.0
#91 ??
from /usr/lib/libgtk-x11-2.0.so.0
#92 ??
from /usr/lib/libgtk-x11-2.0.so.0
#93 ??
from /lib/libgobject-2.0.so.0
#94 g_closure_invoke
from /lib/libgobject-2.0.so.0
#95 ??
from /lib/libgobject-2.0.so.0
#96 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#97 g_signal_emit
from /lib/libgobject-2.0.so.0
#98 ??
from /usr/lib/libgtk-x11-2.0.so.0
#99 ??
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#100 ??
from /lib/libglib-2.0.so.0
#101 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#102 ??
from /lib/libglib-2.0.so.0
#103 g_main_loop_run
from /lib/libglib-2.0.so.0
#104 bonobo_main
from /usr/lib/libbonobo-2.so.0
#105 main
#0 __kernel_vsyscall



----------- .xsession-errors (12 sec old) ---------------------
** (evolution:13676): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:13676): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:13676): e-data-server-ui-WARNING **: 設定鍵檔案沒有設定鍵‘pop:__mis@mail.lutek.com.tw_’
(evolution:13676): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:13676): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c44018'
(evolution:13676): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c44138'
(bug-buddy:13791): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤：元素‘b’已關閉，但開啟中的元素是‘span’
--------------------------------------------------

Comment 1 palfrey 2007-11-08 16:42:50 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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