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 464399 - crash in Tasks: Closing down Evolution. ...
crash in Tasks: Closing down Evolution. ...
Status: RESOLVED DUPLICATE of bug 455329
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-07 15:29 UTC by lortiz
Modified: 2007-09-21 13:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description lortiz 2007-08-07 15:29:55 UTC
Version: 2.10

What were you doing when the application crashed?
Closing down Evolution.  Claimed it was 'Expunging and storing'


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.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve-Tangerine
Icon Theme: Crux

Memory status: size: 184643584 vsize: 184643584 resident: 96911360 share: 41144320 rss: 96911360 rss_rlim: 4294967295
CPU usage: start_time: 1186487185 rtime: 3287 utime: 2816 stime: 471 cutime:1 cstime: 5 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 -1208264992 (LWP 14367)]
[New Thread -1231033456 (LWP 15729)]
[New Thread -1297093744 (LWP 14757)]
[New Thread -1252406384 (LWP 14732)]
[New Thread -1241916528 (LWP 14397)]
(no debugging symbols found)
0x00c3f402 in __kernel_vsyscall ()

Thread 2 (Thread -1231033456 (LWP 15729))

  • #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_message_info_ptr
    from /usr/lib/libcamel-provider-1.2.so.10
  • #7 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #9 camel_folder_summary_save
    from /usr/lib/libcamel-provider-1.2.so.10
  • #10 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #11 camel_folder_sync
    from /usr/lib/libcamel-provider-1.2.so.10
  • #12 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #13 camel_store_sync
    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 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #17 g_thread_create_proxy
    at gthread.c line 594
  • #18 start_thread
    from /lib/libpthread.so.0
  • #19 clone
    from /lib/libc.so.6


----------- .xsession-errors (5498 sec old) ---------------------
(evolution:14367): libecal-WARNING **: e-cal.c:317: Unexpected response
(evolution:14367): libecal-WARNING **: e-cal.c:317: Unexpected response
(evolution:14367): libecal-WARNING **: e-cal.c:317: Unexpected response
(evolution:14367): libecal-WARNING **: e-cal.c:317: Unexpected response
(evolution:14367): libecal-WARNING **: e-cal.c:317: Unexpected response
** Message: Response 1
** Message: Deleting!
(evolution:14367): e-data-server-CRITICAL **: e_categories_get_icon_file_for: assertion `cat_info != NULL' failed
(evolution:14367): e-data-server-CRITICAL **: e_categories_get_icon_file_for: assertion `cat_info != NULL' failed
--------------------------------------------------
Comment 1 palfrey 2007-09-21 13:05:01 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 455329 ***