Bug 502424 – crash in Tasks:

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 502424 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 447591

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-12-08 00:20 UTC by skoh
Modified:	2007-12-10 00:30 UTC

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

Description skoh 2007-12-08 00:20:06 UTC

Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 622424064 vsize: 622424064 resident: 56729600 share: 32808960 rss: 56729600 rss_rlim: 18446744073709551615
CPU usage: start_time: 1197067325 rtime: 817 utime: 719 stime: 98 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496412016 (LWP 10113)]
[New Thread 1147169104 (LWP 10142)]
(no debugging symbols found)
0x0000003b6ec0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 181181

Thread 1 (Thread 46912496412016 (LWP 10113))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_slice_alloc
from /lib64/libglib-2.0.so.0
#4 g_list_append
from /lib64/libglib-2.0.so.0
#5 filter_option_add
from /usr/lib64/evolution/2.10/libfilter.so.0
#6 ??
from /usr/lib64/evolution/2.10/libfilter.so.0
#7 filter_part_xml_create
from /usr/lib64/evolution/2.10/libfilter.so.0
#8 ??
from /usr/lib64/evolution/2.10/libfilter.so.0
#9 rule_context_load
from /usr/lib64/evolution/2.10/libfilter.so.0
#10 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#11 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#12 mail_call_main
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#13 mail_send_queue
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#14 mail_send_receive
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#15 GNOME_Evolution_Component_sendAndReceive
from /usr/lib64/evolution/2.10/libeshell.so.0
#16 e_shell_send_receive
#17 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#18 bonobo_closure_invoke_va_list
from /usr/lib64/libbonobo-2.so.0
#19 bonobo_closure_invoke
from /usr/lib64/libbonobo-2.so.0
#20 ??
from /usr/lib64/libbonoboui-2.so.0
#21 Bonobo_UIComponent_execVerb
from /usr/lib64/libbonobo-2.so.0
#22 ??
from /usr/lib64/libbonoboui-2.so.0
#23 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#24 ??
from /lib64/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#26 g_signal_emit
from /lib64/libgobject-2.0.so.0
#27 ??
from /usr/lib64/libbonoboui-2.so.0
#28 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#29 ??
from /lib64/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#31 g_signal_emit_by_name
from /lib64/libgobject-2.0.so.0
#32 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#33 ??
from /lib64/libgobject-2.0.so.0
#34 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#35 g_signal_emit
from /lib64/libgobject-2.0.so.0
#36 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#37 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#38 ??
from /lib64/libgobject-2.0.so.0
#39 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#40 g_signal_emit
from /lib64/libgobject-2.0.so.0
#41 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#43 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#44 ??
from /lib64/libgobject-2.0.so.0
#45 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#46 g_signal_emit
from /lib64/libgobject-2.0.so.0
#47 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#48 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#49 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#50 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#51 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#52 ??
from /lib64/libglib-2.0.so.0
#53 g_main_loop_run
from /lib64/libglib-2.0.so.0
#54 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#55 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
ptrace: Operation not permitted.
/mnt/data/Home/songwk/1: No such file or directory.
No stack.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
(evolution:10113): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:10113): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8e74b0'
(evolution:10113): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8e6cb0'
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff4c5fd000
--------------------------------------------------

Comment 1 Tobias Mueller 2007-12-10 00:30:38 UTC

Thanks for taking the time to report this bug.
It's most likely that this particular bug is the fedora specific bug 447591:
   GLib-GObject-WARNING **: gsignal.c:1669: signal
   `source_selected' is invalid for instance

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.
As debug symbols are missing, it's just a guess anyway since we can't determine the issue without debug information. Feel free to install debug information and open a new bug. See http://live.gnome.org/GettingTraces for details

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