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 487225 - crash in Tasks: Happens when starting ev...
crash in Tasks: Happens when starting ev...
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-16 17:21 UTC by roverwolf
Modified: 2007-10-22 22:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description roverwolf 2007-10-16 17:21:45 UTC 
Version: 2.10

What were you doing when the application crashed?
Happens when starting evolution (every time)


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.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 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: 631934976 vsize: 631934976 resident: 41709568 share: 32940032 rss: 41709568 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192555229 rtime: 48 utime: 37 stime: 11 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 46912496500880 (LWP 9416)]
[New Thread 1126189392 (LWP 9464)]
[New Thread 1115699536 (LWP 9442)]
[New Thread 1094719824 (LWP 9439)]
(no debugging symbols found)
0x00000032ed00d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 170620

Thread 3 (Thread 1115699536 (LWP 9442))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 <signal handler called>
  • #4 camel_index_add_name
    from /usr/lib64/libcamel-1.2.so.10
  • #5 camel_folder_summary_info_new_from_parser
    from /usr/lib64/libcamel-provider-1.2.so.10
  • #6 camel_folder_summary_add_from_parser
    from /usr/lib64/libcamel-provider-1.2.so.10
  • #7 ??
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #8 ??
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #9 ??
    from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #10 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #11 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /lib64/libglib-2.0.so.0
  • #13 ??
    from /lib64/libglib-2.0.so.0
  • #14 start_thread
    from /lib64/libpthread.so.0
  • #15 clone
    from /lib64/libc.so.6 


----------- .xsession-errors ---------------------
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
CalDAV Eplugin starting up ...
** (evolution:9416): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:9416): 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
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-22 22:45:27 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 ***