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 534745 - crash in Evolution Mail:
crash in Evolution Mail:
Status: RESOLVED DUPLICATE of bug 330728
Product: evolution
Classification: Applications
Component: general
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-25 10:27 UTC by Claudio
Modified: 2008-05-26 04:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Claudio 2008-05-25 10:27:27 UTC
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: dlg-neu

Memory status: size: 579309568 vsize: 579309568 resident: 55214080 share: 28061696 rss: 55214080 rss_rlim: 18446744073709551615
CPU usage: start_time: 1211710985 rtime: 1550 utime: 1402 stime: 148 cutime:2 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x2b04e9baba20 (LWP 11136)]
[New Thread 0x41042950 (LWP 11308)]
[New Thread 0x42804950 (LWP 11307)]
[New Thread 0x41001950 (LWP 11184)]
0x00002b04df63eedf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b04e9baba20 (LWP 11136))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ect_check
    at gal-a11y-e-cell-text.c line 69
  • #6 ect_get_name
    at gal-a11y-e-cell-text.c line 81
  • #7 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #8 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #9 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #10 atk_focus_tracker_notify
    from /usr/lib/libatk-1.0.so.0
  • #11 ??
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at main.c line 782
  • #17 __libc_start_main
    from /lib/libc.so.6
  • #18 _start
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (6073 sec old) ---------------------
(evolution:3666): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3666): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3666): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3666): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3666): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3666): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3666): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-05-26 04:45:21 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 330728 ***