Bug 509564 – crash in Tasks: Nothing

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


Summary:	crash in Tasks: Nothing


Status:	RESOLVED DUPLICATE of bug 339602

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

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-15 08:24 UTC by sabelo
Modified:	2008-01-15 11:47 UTC

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

Description sabelo 2008-01-15 08:24:14 UTC

Version: 2.10

What were you doing when the application crashed?
Nothing			


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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 173223936 vsize: 173223936 resident: 44306432 share: 33865728 rss: 44306432 rss_rlim: 4294967295
CPU usage: start_time: 1200385206 rtime: 283 utime: 231 stime: 52 cutime:0 cstime: 0 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 -1208232224 (LWP 4290)]
[New Thread -1329927280 (LWP 4312)]
[New Thread -1262490736 (LWP 4302)]
[New Thread -1240249456 (LWP 4298)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 185394

Thread 4 (Thread -1240249456 (LWP 4298))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 camel_index_add_name
from /usr/lib/libcamel-1.2.so.10
#7 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#8 camel_folder_summary_add_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#9 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#10 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#11 camel_local_summary_check
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#12 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#13 camel_folder_append_message
from /usr/lib/libcamel-provider-1.2.so.10
#14 camel_filter_driver_filter_message
from /usr/lib/libcamel-provider-1.2.so.10
#15 camel_filter_driver_filter_folder
from /usr/lib/libcamel-provider-1.2.so.10
#16 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#17 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#18 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#19 ??
from /lib/libglib-2.0.so.0
#20 ??
from /lib/libglib-2.0.so.0
#21 start_thread
from /lib/libpthread.so.0
#22 clone
from /lib/libc.so.6



----------- .xsession-errors (8 sec old) ---------------------
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x2c00003
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x2800078
CalDAV Eplugin starting up ...
** (evolution:4290): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4290): 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
calendar-gui-Message: launch_alarm_daemon_cb(): Child process did not give an error message, unknown failure occurred
--------------------------------------------------

Comment 1 Tobias Mueller 2008-01-15 11:47:47 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 339602 ***