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 446387 - crash in Tasks:
crash in Tasks:
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-06-11 14:28 UTC by claudio
Modified: 2007-06-12 16:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description claudio 2007-06-11 14:28:40 UTC
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 170631168 vsize: 170631168 resident: 67481600 share: 16502784 rss: 67481600 rss_rlim: 4294967295
CPU usage: start_time: 1181571729 rtime: 8456 utime: 7461 stime: 995 cutime:45 cstime: 12 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 -1209059616 (LWP 1009)]
[New Thread -1230271600 (LWP 1088)]
[New Thread -1292960880 (LWP 1042)]
[New Thread -1262691440 (LWP 1035)]
[New Thread -1240761456 (LWP 1032)]
[New Thread -1219781744 (LWP 1029)]
(no debugging symbols found)
0x00f24402 in __kernel_vsyscall ()

Thread 3 (Thread -1292960880 (LWP 1042))

  • #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 (513169 sec old) ---------------------
(evolution:5050): camel-pop3-provider-WARNING **: Bad server response: To: revenue; timeoff
(evolution:5050): camel-pop3-provider-WARNING **: Bad server response: Subject: RE: Marshall 000
(evolution:5050): camel-pop3-provider-WARNING **: Bad server response: 
(evolution:5050): camel-pop3-provider-WARNING **: Bad server response: 
(evolution:5050): camel-pop3-provider-WARNING **: Bad server response: Sorry. Instead of F
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-06-12 16:03:05 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 ***