Bug 528623 – crash in Evolution Mail and Calendar: clicked on the junk butt...

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 528623 - crash in Evolution Mail and Calendar: clicked on the junk butt...


Summary:	crash in Evolution Mail and Calendar: clicked on the junk butt...


Status:	RESOLVED DUPLICATE of bug 528564

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-04-17 18:03 UTC by dan.mcdonald
Modified:	2008-04-18 00:21 UTC

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

Description dan.mcdonald 2008-04-17 18:03:45 UTC

What were you doing when the application crashed?
clicked on the junk button.


Distribution: Unknown
Gnome Release: 2.22.0 2008-03-26 (Mandriva)
BugBuddy Version: 2.22.0

System: Linux 2.6.24.4-desktop-1mnb #1 SMP Thu Mar 27 14:34:39 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Blue
Icon Theme: gnome

Memory status: size: 87822336 vsize: 87822336 resident: 18243584 share: 9637888 rss: 18243584 rss_rlim: 4294967295
CPU usage: start_time: 1208442971 rtime: 216311 utime: 190613 stime: 25698 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/evolution-exchange-storage'

Using host libthread_db library "/lib/i686/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1242089184 (LWP 11378)]
[New Thread -1245467760 (LWP 14998)]
[New Thread -1272976496 (LWP 14984)]
[New Thread -1283458160 (LWP 14983)]
[New Thread -1253860464 (LWP 14981)]
[New Thread -1245201520 (LWP 11379)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 195489

Thread 1 (Thread -1242089184 (LWP 11378))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 POA_GNOME_Evolution_Component__fini
at Evolution-skels.c line 506
#5 POA_GNOME_Evolution_Component__fini
at Evolution-skels.c line 506
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 google_breakpad::ExceptionHandler::HandleException
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#8 <signal handler called>
#9 get_message
at mail-stub-exchange.c line 2447
#10 connection_handler
at mail-stub.c line 271
#11 POA_GNOME_Evolution_Component__fini
at Evolution-skels.c line 506
#12 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#13 POA_GNOME_Evolution_Component__fini
at Evolution-skels.c line 506
#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 238
#17 __libc_start_main
from /lib/i686/libc.so.6
#18 _start
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
CalDAV Eplugin starting up ...
** (evolution:11261): DEBUG: mailto URL command: evolution %s
** (evolution:11261): DEBUG: mailto URL program: evolution
CalDAV Eplugin starting up ...
** (evolution:11369): DEBUG: mailto URL command: evolution %s
** (evolution:11369): DEBUG: mailto URL program: evolution
report junk?? ***SPAM*** Lexo Pse Mitrovica U Nda Qo edhe 40 SMS falas krejt Kosoven By Vala
BBDB spinning up...
report junk?? Lexo Pse Mitrovica U Nda Qo edhe 40 SMS falas krejt Kosoven By Vala
--------------------------------------------------

Comment 1 Pedro Villavicencio 2008-04-18 00:21:03 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 528564 ***