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 487539 - crash in Tasks: Deleting mail that had b...
crash in Tasks: Deleting mail that had b...
Status: RESOLVED DUPLICATE of bug 479007
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-17 15:08 UTC by Chris Brazfield
Modified: 2007-11-29 06:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Chris Brazfield 2007-10-17 15:08:34 UTC 
Version: 2.10

What were you doing when the application crashed?
Deleting mail that had been popped from server. 


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 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 137379840 vsize: 137379840 resident: 66093056 share: 40509440 rss: 66093056 rss_rlim: 4294967295
CPU usage: start_time: 1192619948 rtime: 3206 utime: 2659 stime: 547 cutime:590 cstime: 277 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 -1208658208 (LWP 7190)]
[New Thread -1283916912 (LWP 8218)]
[New Thread -1296041072 (LWP 7208)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 170869

Thread 1 (Thread -1208658208 (LWP 7190))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 camel_message_info_free
    from /usr/lib/libcamel-provider-1.2.so.10
  • #6 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #7 camel_folder_free_message_info
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #9 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #11 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #17 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #18 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(evolution:7190): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed
(evolution:7190): e-table-CRITICAL **: e_tree_memory_node_set_data: assertion `path' failed
(evolution:7190): e-table-CRITICAL **: e_tree_memory_node_get_data: assertion `path' failed
(evolution:7190): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed
(evolution:7190): e-table-CRITICAL **: e_tree_memory_node_set_data: assertion `path' failed
(evolution:7190): e-table-CRITICAL **: e_tree_memory_node_get_data: assertion `path' failed
(evolution:7190): camel-CRITICAL **: camel_folder_free_message_info: assertion `info != NULL' failed
(evolution:7190): e-table-CRITICAL **: e_tree_memory_node_set_data: assertion `path' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2007-11-29 06:21:47 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
the maintainers need more information to fix the bug. Could you please answer
the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 479007 ***