Bug 475022 – crash in Tasks: start the application

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 475022 - crash in Tasks: start the application


Summary:	crash in Tasks: start the application


Status:	RESOLVED DUPLICATE of bug 425093

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
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-09-09 03:10 UTC by johnzfan
Modified:	2007-12-04 17:02 UTC

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

Description johnzfan 2007-09-09 03:10:28 UTC

Version: 2.12

What were you doing when the application crashed?
start the application			


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.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 550899712 vsize: 550899712 resident: 43266048 share: 34095104 rss: 43266048 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189307369 rtime: 72 utime: 64 stime: 8 cutime:1 cstime: 6 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 46912498621840 (LWP 7309)]
[New Thread 1084229968 (LWP 7336)]
(no debugging symbols found)
0x0000003f9d00d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 161452

Thread 1 (Thread 46912498621840 (LWP 7309))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 strchr
from /lib64/libc.so.6
#4 camel_url_new_with_base
from /usr/lib64/libcamel-1.2.so.10
#5 camel_url_new
from /usr/lib64/libcamel-1.2.so.10
#6 ??
from /usr/lib64/evolution/2.12/components/libevolution-mail.so
#7 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#8 ??
from /lib64/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit
from /lib64/libgobject-2.0.so.0
#11 ??
from /usr/lib64/evolution/2.12/components/libevolution-mail.so
#12 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#13 ??
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit_by_name
from /lib64/libgobject-2.0.so.0
#16 ??
from /usr/lib64/evolution/2.12/libefilterbar.so.0
#17 g_object_set_valist
from /lib64/libgobject-2.0.so.0
#18 g_object_set
from /lib64/libgobject-2.0.so.0
#19 ??
from /usr/lib64/evolution/2.12/components/libevolution-mail.so
#20 ??
from /usr/lib64/evolution/2.12/components/libevolution-mail.so
#21 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#22 ??
from /lib64/libglib-2.0.so.0
#23 g_main_loop_run
from /lib64/libglib-2.0.so.0
#24 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#25 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
  Resource id:  0x1600313
(evolution:7309): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:7309): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:7309): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:7309): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:7309): evolution-mail-CRITICAL **: mail_tool_uri_to_folder: assertion `uri != NULL' failed
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x1a5
--------------------------------------------------

Comment 1 palfrey 2007-12-04 17:02:37 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

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