Bug 478873 – crash in Tasks: email

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 478873 - crash in Tasks: email


Summary:	crash in Tasks: email


Status:	RESOLVED DUPLICATE of bug 472050

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-21 08:30 UTC by pc
Modified:	2007-12-04 18:24 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description pc 2007-09-21 08:30:27 UTC

Version: 2.10

What were you doing when the application crashed?
email


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.18-8.1.10.el5xen #1 SMP Thu Sep 13 12:46:46 EDT 2007 x86_64
X Vendor: The XFree86 Project, Inc
X Vendor Release: 40300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 789893120 vsize: 789893120 resident: 156446720 share: 48758784 rss: 156446720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190334685 rtime: 4283 utime: 3665 stime: 618 cutime:24 cstime: 114 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496390288 (LWP 8478)]
[New Thread 1115699536 (LWP 8553)]
[New Thread 1136945488 (LWP 8490)]
[New Thread 1105209680 (LWP 8484)]
(no debugging symbols found)
0x0000003e39a0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 164339

Thread 1 (Thread 46912496390288 (LWP 8478))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_utf8_offset_to_pointer
from /lib64/libglib-2.0.so.0
#4 ??
from /usr/lib64/libedataserverui-1.2.so.8
#5 ??
from /usr/lib64/libedataserverui-1.2.so.8
#6 ??
from /usr/lib64/libedataserverui-1.2.so.8
#7 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#8 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#9 ??
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit
from /lib64/libgobject-2.0.so.0
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#16 ??
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /lib64/libgobject-2.0.so.0
#19 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#20 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#21 ??
from /lib64/libgobject-2.0.so.0
#22 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#23 g_signal_emit
from /lib64/libgobject-2.0.so.0
#24 gtk_widget_grab_focus
from /usr/lib64/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#27 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#28 ??
from /lib64/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#30 g_signal_emit
from /lib64/libgobject-2.0.so.0
#31 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#32 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#33 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#35 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#36 ??
from /lib64/libglib-2.0.so.0
#37 g_main_loop_run
from /lib64/libglib-2.0.so.0
#38 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#39 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 palfrey 2007-12-04 18:24:25 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 472050 ***