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 458723 - crash in Tasks: I wasn't doing anything ...
crash in Tasks: I wasn't doing anything ...
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-20 17:39 UTC by 9321fasdf12345
Modified: 2007-07-26 21:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description 9321fasdf12345 2007-07-20 17:39:34 UTC
Version: 2.10

What were you doing when the application crashed?
I wasn't doing anything in particular, but the status bar listed "Storing folder" and "Fetching mail" -- i.e. concurrent access to the same folder.


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.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 594845696 vsize: 594845696 resident: 58847232 share: 30507008 rss: 58847232 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184953081 rtime: 711 utime: 589 stime: 122 cutime:143 cstime: 21 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496427168 (LWP 5326)]
[New Thread 1147435344 (LWP 5367)]
[New Thread 1147169104 (LWP 5363)]
[New Thread 1105209680 (LWP 5339)]
[New Thread 1084229968 (LWP 5335)]
0x00000036c420d97f in __libc_waitpid (pid=5380, stat_loc=0x7fff30b14aec, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 3 (Thread 1147169104 (LWP 5363))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 81
  • #3 <signal handler called>
  • #4 camel_index_add_name
    at camel-index.c line 183
  • #5 camel_folder_summary_info_new_from_parser
    at camel-folder-summary.c line 1015
  • #6 camel_folder_summary_add_from_parser
    at camel-folder-summary.c line 920
  • #7 summary_update
    at camel-mbox-summary.c line 485
  • #8 mbox_summary_check
    at camel-mbox-summary.c line 572
  • #9 local_refresh_info
    at camel-local-folder.c line 476
  • #10 mail_msg_proxy
    at mail-mt.c line 500
  • #11 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #12 g_thread_create_proxy
    at gthread.c line 591
  • #13 start_thread
    at pthread_create.c line 296
  • #14 clone
    from /lib64/libc.so.6


----------- .xsession-errors (18 sec old) ---------------------
(evolution:5326): camel-WARNING **: Could not create key entry for word '2dd6eed': Interrupted system call
(evolution:5326): camel-WARNING **: Could not create key entry for word 'idd': Interrupted system call
(evolution:5326): camel-WARNING **: Could not create key entry for word '2790': Interrupted system call
(evolution:5326): camel-WARNING **: Could not create key entry for word 'c862f67': Interrupted system call
(evolution:5326): camel-WARNING **: Could not create key entry for word 'sioc4': Interrupted system call
--------------------------------------------------
Comment 1 André Klapper 2007-07-26 21:51:00 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 339602 ***