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 604609 - crash in Evolution Mail: Checking mail...
crash in Evolution Mail: Checking mail...
Status: RESOLVED DUPLICATE of bug 557613
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-12-15 10:56 UTC by nowak2000
Modified: 2009-12-16 04:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description nowak2000 2009-12-15 10:56:07 UTC
What were you doing when the application crashed?
Checking mail...


Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-11-21 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-2-686 #1 SMP Fri Dec 4 00:53:20 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks Compact
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 199122944 vsize: 199122944 resident: 73351168 share: 28733440 rss: 73351168 rss_rlim: 18446744073709551615
CPU usage: start_time: 1260783029 rtime: 9193 utime: 8466 stime: 727 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

Really redefine built-in command "frame"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "thread"? (y or n) [answered Y; input not from terminal]
Really redefine built-in command "start"? (y or n) [answered Y; input not from terminal]
[Thread debugging using libthread_db enabled]
[New Thread 0xafbffb70 (LWP 8524)]
[New Thread 0xaebfdb70 (LWP 8521)]
[New Thread 0xaf3feb70 (LWP 8507)]
[New Thread 0xb0595b70 (LWP 20192)]
[New Thread 0xb0fbbb70 (LWP 20191)]
[New Thread 0xb35fcb70 (LWP 20057)]
[New Thread 0xb3dfdb70 (LWP 20056)]
[New Thread 0xb4dffb70 (LWP 20054)]
[New Thread 0xb5745b70 (LWP 20053)]
_______________________________________________________________________________
     eax:FFFFFE00 ebx:00002150  ecx:BF8B1A2C  edx:00000000     eflags:00000293
     esi:BF8B1A2C edi:00000000  esp:BF8B1944  ebp:BF8B1A48     eip:B80C2424
     cs:0073  ds:007B  es:007B  fs:0000  gs:0033  ss:007B    o d I t S z A p C 
[007B:BF8B1944]---------------------------------------------------------[stack]
BF8B1974 : 00 00 00 00  00 00 00 00 - 00 00 00 00  00 00 00 00 ................
BF8B1964 : 2C 1A 8B BF  00 00 00 00 - 01 00 00 00  00 00 00 00 ,...............
BF8B1954 : 84 51 C4 B6  00 00 00 00 - 57 2A C0 B6  50 21 00 00 .Q......W*..P!..
BF8B1944 : 48 1A 8B BF  00 00 00 00 - 2C 1A 8B BF  0B 5F 9C B7 H.......,...._..
[007B:BF8B1A2C]---------------------------------------------------------[ data]
BF8B1A2C : 52 81 BE B6  50 21 00 00 - FF FF FF FF  FF FF FF FF R...P!..........
BF8B1A3C : 84 51 C4 B6  00 00 00 00 - A8 1B 8B BF  98 1A 8B BF .Q..............
[0073:B80C2424]---------------------------------------------------------[ code]
0xb80c2424 <__kernel_vsyscall+16>:	pop    %ebp
0xb80c2425 <__kernel_vsyscall+17>:	pop    %edx
0xb80c2426 <__kernel_vsyscall+18>:	pop    %ecx
0xb80c2427 <__kernel_vsyscall+19>:	ret    
0xb80c2428:	add    %ch,(%esi)
0xb80c242a:	jae    0xb80c2494
------------------------------------------------------------------------------
0xb80c2424 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 segv_redirect
    at main.c line 432
  • #6 <signal handler called>
  • #7 __pthread_mutex_lock
    at pthread_mutex_lock.c line 50
  • #8 e_flag_set
    at e-flag.c line 83
  • #9 try_open_e_book_cb
    at em-utils.c line 2001
  • #10 emit_async_open_response
    at e-book.c line 2814
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at main.c line 732


---- Critical and fatal warnings logged during execution ----

** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 
** evolution **: atk_object_set_name: assertion `name != NULL' failed 


----------- .xsession-errors (305213 sec old) ---------------------
0xafabbc60 feof        : ret:0
0xafabbc60 fread       : size:1 : nmemb:512 : ret:512
0xafadef80 fwrite      : size:1 : nmemb:512 : ret:512
0xafabbc60 feof        : ret:0
0xafabbc60 fread       : size:1 : nmemb:512 : ret:44
0xafadef80 fwrite      : size:1 : nmemb:44 : ret:44
0xafabbc60 feof        : ret:0
ERROR: neon: neon.c:981 (neon_aud_vfs_fread_impl): <0xafabc408> Buffer underrun, trying rebuffering
0xafabbc60 fread       : size:1 : nmemb:512 : ret:512
0xafadef80 fwrite      : size:1 : nmemb:512 : ret:512
0xafabbc60 feof        : ret:0
0xafabbc60 fread       : size:1 : nmemb:512 : ret:512
0xafadef80 fwrite      : size:1 : nmemb:512 : ret:512
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2009-12-16 04:17:58 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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