Bug 572473 – crash in Evolution Mail and Calendar: Deleteing an email messa...

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 572473 - crash in Evolution Mail and Calendar: Deleteing an email messa...


Summary:	crash in Evolution Mail and Calendar: Deleteing an email messa...


Status:	RESOLVED DUPLICATE of bug 569700

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.24.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:	2009-02-19 18:48 UTC by bryan.christ
Modified:	2009-02-20 03:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description bryan.christ 2009-02-19 18:48:16 UTC

What were you doing when the application crashed?
Deleteing an email message


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.15-170.2.24.fc10.x86_64 #1 SMP Wed Feb 11 23:14:31 EST 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Raleigh
Icon Theme: build

Memory status: size: 1229897728 vsize: 1229897728 resident: 95760384 share: 29155328 rss: 95760384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1235063026 rtime: 2082 utime: 1816 stime: 266 cutime:2 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f51b78947e0 (LWP 31339)]
[New Thread 0x7f51857fb950 (LWP 31920)]
[New Thread 0x7f518cf2e950 (LWP 31919)]
[New Thread 0x7f518f732950 (LWP 31747)]
[New Thread 0x7f51ab2b3950 (LWP 31645)]
[New Thread 0x7f51aaf78950 (LWP 31370)]
0x000000389440ec2f in __libc_waitpid (pid=31940, stat_loc=0x7fffbf8e2510, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 212709

Thread 2 (Thread 0x7f51857fb950 (LWP 31920))

#0 __lll_lock_wait
at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S line 130
#1 _L_lock_102
from /lib64/libpthread.so.0
#2 __pthread_mutex_lock
at pthread_mutex_lock.c line 86
#3 <signal handler called>
#4 camel_mime_parser_read
at camel-mime-parser.c line 655
#5 stream_read
#6 emfh_gethttp
at em-format-html.c line 525
#7 efh_format_exec
at em-format-html.c line 1299
#8 mail_msg_proxy
at mail-mt.c line 520
#9 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#10 g_thread_create_proxy
at gthread.c line 635
#11 start_thread
at pthread_create.c line 297
#12 clone
at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112



----------- .xsession-errors (118 sec old) ---------------------
(evolution:31339): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(evolution:31339): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(evolution:31339): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(evolution:31339): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(evolution:31339): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(evolution:31339): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(evolution:31339): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
*** NSPlugin Wrapper *** ERROR: NPP_Destroy() wait for reply: Message timeout
*** NSPlugin Wrapper *** WARNING:(../src/npw-wrapper.c:1858):invoke_NPP_Destroy: assertion failed: (rpc_method_invoke_possible(plugin->connection))
--------------------------------------------------

Comment 1 Akhil Laddha 2009-02-20 03:42:07 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 569700 ***