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 487082 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 487081
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-16 09:03 UTC by mahajan.deepak
Modified: 2007-10-16 11:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mahajan.deepak 2007-10-16 09:03:01 UTC
Version: 2.10

What were you doing when the application crashed?



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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 589701120 vsize: 589701120 resident: 84004864 share: 28966912 rss: 84004864 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192525368 rtime: 465 utime: 418 stime: 47 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 46912496337040 (LWP 24443)]
[New Thread 1136679248 (LWP 24473)]
[New Thread 1105209680 (LWP 24464)]
[New Thread 1084229968 (LWP 24460)]
(no debugging symbols found)
0x000000352d20d97f in waitpid () from /lib64/libpthread.so.0

Thread 2 (Thread 1136679248 (LWP 24473))

  • #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 /lib64/libglib-2.0.so.0
  • #12 ??
    from /lib64/libglib-2.0.so.0
  • #13 start_thread
    from /lib64/libpthread.so.0
  • #14 clone
    from /lib64/libc.so.6


----------- .xsession-errors (189740 sec old) ---------------------
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Christoph Wolk 2007-10-16 11:28:51 UTC
*** Bug 487083 has been marked as a duplicate of this bug. ***
Comment 2 Christoph Wolk 2007-10-16 11:33:28 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 487081 ***