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 511837 - crash in Tasks: starting evo
crash in Tasks: starting evo
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-24 17:33 UTC by Richard Hyde
Modified: 2008-01-24 23:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Richard Hyde 2008-01-24 17:33:14 UTC 
Version: 2.10

What were you doing when the application crashed?
starting evo


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 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 224862208 vsize: 224862208 resident: 72929280 share: 57647104 rss: 72929280 rss_rlim: 4294967295
CPU usage: start_time: 1201195922 rtime: 335 utime: 297 stime: 38 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 -1208682784 (LWP 10600)]
[New Thread -1376781424 (LWP 10629)]
[New Thread -1286607984 (LWP 10608)]
[New Thread -1264505968 (LWP 10605)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 186647

Thread 2 (Thread -1376781424 (LWP 10629))

  • #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_refresh_info
    from /usr/lib/libcamel-provider-1.2.so.10
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 start_thread
    from /lib/libpthread.so.0
  • #19 clone
    from /lib/libc.so.6 


----------- .xsession-errors (2686915 sec old) ---------------------
Cannot append message to mbox file: /home/rhyde/.evolution/mail/local/Cron: File too large
(evolution:13329): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Cannot append message to mbox file: /home/rhyde/.evolution/mail/local/Cron: File too large
(evolution:13329): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Cannot append message to mbox file: /home/rhyde/.evolution/mail/local/Cron: File too large
(evolution:13329): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Cannot append message to mbox file: /home/rhyde/.evolution/mail/local/Cron: File too large
(evolution:13329): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Cannot append message to mbox file: /home/rhyde/.evolution/mail/local/Cron: File too large
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Tobias Mueller 2008-01-24 23:10:51 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 ***