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 490522 - crash in Email: stavo scaricando la post...
crash in Email: stavo scaricando la post...
Status: RESOLVED DUPLICATE of bug 407187
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-26 14:03 UTC by vcilinux
Modified: 2007-11-20 06:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description vcilinux 2007-10-26 14:03:08 UTC
Version: 2.10

What were you doing when the application crashed?
stavo scaricando la posta dallo spool


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: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 118190080 vsize: 118190080 resident: 47624192 share: 33017856 rss: 47624192 rss_rlim: 4294967295
CPU usage: start_time: 1193407217 rtime: 1015 utime: 952 stime: 63 cutime:1 cstime: 3 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 -1209157920 (LWP 5936)]
[New Thread -1221244016 (LWP 5959)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209157920 (LWP 5936))

  • #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 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (927018 sec old) ---------------------
(mail-notification:2548): mail-notification-WARNING **: vcilinux@luxornet.com@hosting7.ticinocom.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2548): mail-notification-WARNING **: vcilinux@luxornet.com@hosting7.ticinocom.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2548): mail-notification-WARNING **: vcilinux@luxornet.com@hosting7.ticinocom.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2548): mail-notification-WARNING **: vcilinux@luxornet.com@hosting7.ticinocom.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2548): mail-notification-WARNING **: vcilinux@luxornet.com@hosting7.ticinocom.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2548): mail-notification-WARNING **: vcilinux@luxornet.com@hosting7.ticinocom.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2548): mail-notification-WARNING **: vcilinux@luxornet.com@hosting7.ticinocom.com: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2007-11-20 06:50:25 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 ***