Bug 514059 – crash in Calendar: 在垃圾箱中的一封邮件的标题上点了一下右键，出现右...

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 514059 - crash in Calendar: 在垃圾箱中的一封邮件的标题上点了一下右键，出现右...


Summary:	crash in Calendar: 在垃圾箱中的一封邮件的标题上点了一下右键，出现右...


Status:	RESOLVED DUPLICATE of bug 489872

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	unspecified
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-02-03 12:22 UTC by ziwen_xu
Modified:	2008-02-04 15:18 UTC

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

Description ziwen_xu 2008-02-03 12:22:53 UTC

Version: 2.10

What were you doing when the application crashed?
在垃圾箱中的一封邮件的标题上点了一下右键，出现右键菜单，还没有做出任何选择，就显示要崩溃了。


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

System: Linux 2.6.23.14-64.fc7 #1 SMP Sun Jan 20 22:20:19 EST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 783224832 vsize: 783224832 resident: 89001984 share: 48939008 rss: 89001984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1202034544 rtime: 4763 utime: 4418 stime: 345 cutime:1773 cstime: 189 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 46912496366960 (LWP 3148)]
[New Thread 1136945488 (LWP 3200)]
[New Thread 1105209680 (LWP 3172)]
(no debugging symbols found)
0x000000356160d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 187915

Thread 1 (Thread 46912496366960 (LWP 3148))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
from /lib64/libglib-2.0.so.0
#4 ??
from /lib64/libglib-2.0.so.0
#5 ??
from /lib64/libglib-2.0.so.0
#6 g_slice_free1
from /lib64/libglib-2.0.so.0
#7 g_slist_foreach
from /lib64/libglib-2.0.so.0
#8 pango_layout_line_unref
from /usr/lib64/libpango-1.0.so.0
#9 ??
from /usr/lib64/libpango-1.0.so.0
#10 ??
from /usr/lib64/libpango-1.0.so.0
#11 g_object_unref
from /lib64/libgobject-2.0.so.0
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#14 ??
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /lib64/libgobject-2.0.so.0
#17 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#23 gtk_widget_unparent
from /usr/lib64/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#25 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#26 ??
from /lib64/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#28 g_signal_emit
from /lib64/libgobject-2.0.so.0
#29 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#30 g_object_run_dispose
from /lib64/libgobject-2.0.so.0
#31 ??
from /usr/lib64/evolution/2.10/libeutil.so.0
#32 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#33 ??
from /lib64/libgobject-2.0.so.0
#34 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#35 g_signal_emit
from /lib64/libgobject-2.0.so.0
#36 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#37 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#38 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#39 ??
from /lib64/libgobject-2.0.so.0
#40 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#41 g_signal_emit
from /lib64/libgobject-2.0.so.0
#42 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#44 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#45 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#46 ??
from /lib64/libgobject-2.0.so.0
#47 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#48 g_signal_emit
from /lib64/libgobject-2.0.so.0
#49 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#50 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#51 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#52 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#53 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#54 ??
from /lib64/libglib-2.0.so.0
#55 g_main_loop_run
from /lib64/libglib-2.0.so.0
#56 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#57 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (2211 sec old) ---------------------
0:  7 7b e0 55  8 ed 31 e4 
8:  0  f 2d c0 db 85 3e 14 
16: 1f 40  0 84 11 3d  7 7b 
24:EvaPacketManager::processReceiveIM -- unknown transfer type: 6b
 e0 55  8 ed 31 e4 31 68 
32: fe ed 77 43 de 6a 6f aa 
40: 7f d2 18 66 99 5e  0 81 
48: 1f 8d 47 a5 a7 4d  0  0 
56:  0  0  0  1  0  0  0  0 
64:  0  0  0  0  0  0  0  0 
72:  0  0  0  0  0  0  0  0 
80:  0  0  0 6b  0 6b  0  0 
88:  0  0  0  1  0  0 1f 8d
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-04 15:18:45 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
the maintainers need more information to fix the bug. Could you please answer
the questions in the other report in order to help the developers?

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