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 508401 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 407187
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-09 23:43 UTC by jrenones
Modified: 2008-01-18 12:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jrenones 2008-01-09 23:43:42 UTC 
Version: 2.10

What were you doing when the application crashed?



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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 160460800 vsize: 160460800 resident: 75718656 share: 35000320 rss: 75718656 rss_rlim: 4294967295
CPU usage: start_time: 1199921586 rtime: 4733 utime: 4543 stime: 190 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 -1208792336 (LWP 12394)]
[New Thread -1311007856 (LWP 12459)]
[New Thread -1260401776 (LWP 12425)]
[New Thread -1239016560 (LWP 12398)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 184728

Thread 1 (Thread -1208792336 (LWP 12394))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_str_hash
    from /lib/libglib-2.0.so.0
  • #6 g_hash_table_insert
    from /lib/libglib-2.0.so.0
  • #7 em_folder_tree_model_set_folder_info
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #8 em_folder_tree_model_set_folder_info
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #9 em_folder_tree_model_set_folder_info
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #10 em_folder_tree_model_set_folder_info
    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 (23746 sec old) ---------------------
(evolution:2992): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:2992): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:2992): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:2992): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:2992): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:2992): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
(evolution:2992): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2008-01-18 12:30:36 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 407187 ***