Bug 546509 – crash in Evolution Mail:

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 546509 - crash in Evolution Mail:


Summary:	crash in Evolution Mail:


Status:	RESOLVED DUPLICATE of bug 541872

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.22.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-08-06 04:56 UTC by alano.br
Modified:	2008-08-07 01:26 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description alano.br 2008-08-06 04:56:29 UTC

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: Tango

Memory status: size: 723554304 vsize: 723554304 resident: 68358144 share: 29769728 rss: 68358144 rss_rlim: 18446744073709551615
CPU usage: start_time: 1217974608 rtime: 6856 utime: 6132 stime: 724 cutime:1850 cstime: 188 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f3430a1f790 (LWP 3705)]
[New Thread 0x40a1a950 (LWP 3822)]
[New Thread 0x42eba950 (LWP 3821)]
0x00007f342c2feedf in waitpid () from /lib/libpthread.so.0

+ Trace 204676

Thread 1 (Thread 0x7f3430a1f790 (LWP 3705))

#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 ??
from /usr/lib/xulrunner-1.9/libxul.so
#5 <signal handler called>
#6 ??
#7 ??
from /usr/lib/xulrunner-1.9/libxul.so
#8 ??
from /usr/lib/xulrunner-1.9/libxul.so
#9 ??
from /usr/lib/xulrunner-1.9/libxul.so
#10 ??
from /usr/lib/xulrunner-1.9/libxul.so
#11 ??
from /usr/lib/xulrunner-1.9/libxul.so
#12 ??
from /usr/lib/xulrunner-1.9/libxul.so
#13 XRE_TermEmbedding
from /usr/lib/xulrunner-1.9/libxul.so
#14 ??
from /usr/lib/xulrunner-1.9/libxul.so
#15 gecko_shutdown
from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
#16 exit
from /lib/libc.so.6
#17 __libc_start_main
from /lib/libc.so.6
#18 _start
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (12 sec old) ---------------------
W:Context Refresh Not implemented for this Song type 1
W:Context Refresh Not implemented for this Song type 1
W:Context Refresh Not implemented for this Song type 1
1009 songs and 3 playlists saved
W:Context Refresh Not implemented for this Song type 1
1009 songs and 3 playlists saved
1009 songs and 3 playlists saved
1009 songs and 3 playlists saved
Exit successful

(gnome-terminal:14816): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Aviso do gerenciador de janelas: last_user_time (1989768832) is greater than comparison timestamp (23932816).  This most likely represents a buggy client sending inaccurate timestamps in messages such
Aviso do gerenciador de janelas: 0x2e00020 (Terminal) appears to be one of the offending windows with a timestamp of 1989768832.  Working around...
RSS: cleaning all remaining sessions ...done
--------------------------------------------------

Comment 1 André Klapper 2008-08-07 01:26:57 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 541872 ***