Bug 488480 – 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 488480 - crash in Calendar: 移动


Summary:	crash in Calendar: 移动


Status:	RESOLVED DUPLICATE of bug 442949

Product:	evolution
Classification:	Applications
Component:	Calendar
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-10-20 02:16 UTC by qiwuzhong
Modified:	2007-10-24 04:55 UTC

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

Description qiwuzhong 2007-10-20 02:16:42 UTC

Version: 2.10

What were you doing when the application crashed?
移动


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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 165330944 vsize: 165330944 resident: 43978752 share: 23142400 rss: 43978752 rss_rlim: 4294967295
CPU usage: start_time: 1192844845 rtime: 5238 utime: 4812 stime: 426 cutime:1 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208748320 (LWP 2831)]
[New Thread -1265149040 (LWP 2984)]
[New Thread -1287521392 (LWP 2982)]
[New Thread -1232335984 (LWP 2906)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 171589

Thread 1 (Thread -1208748320 (LWP 2831))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 free
from /lib/libc.so.6
#6 g_free
from /lib/libglib-2.0.so.0
#7 pango_glyph_string_free
from /usr/lib/libpango-1.0.so.0
#8 ??
from /usr/lib/libpango-1.0.so.0
#9 g_slist_foreach
from /lib/libglib-2.0.so.0
#10 pango_layout_line_unref
from /usr/lib/libpango-1.0.so.0
#11 ??
from /usr/lib/libpango-1.0.so.0
#12 ??
from /usr/lib/libpango-1.0.so.0
#13 g_object_unref
from /lib/libgobject-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#16 ??
from /lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /lib/libgobject-2.0.so.0
#18 ??
from /lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#20 g_signal_emit
from /lib/libgobject-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#26 ??
from /usr/lib/libgtk-x11-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
from /usr/lib/libbonoboui-2.so.0
#31 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib/libbonoboui-2.so.0
#34 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libbonoboui-2.so.0
#37 ??
from /usr/lib/libbonoboui-2.so.0
#38 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#39 ??
from /usr/lib/libgtk-x11-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#42 ??
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgtk-x11-2.0.so.0
#44 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgtk-x11-2.0.so.0
#46 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#47 ??
from /usr/lib/libgtk-x11-2.0.so.0
#48 gtk_rc_reparse_all_for_settings
from /usr/lib/libgtk-x11-2.0.so.0
#49 gtk_rc_reparse_all
from /usr/lib/libgtk-x11-2.0.so.0
#50 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#51 ??
from /usr/lib/libgconf-2.so.4
#52 gconf_listeners_notify
from /usr/lib/libgconf-2.so.4
#53 ??
from /usr/lib/libgconf-2.so.4
#54 ??
from /usr/lib/libgconf-2.so.4
#55 ??
from /lib/libglib-2.0.so.0
#56 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#57 ??
from /lib/libglib-2.0.so.0
#58 g_main_loop_run
from /lib/libglib-2.0.so.0
#59 bonobo_main
from /usr/lib/libbonobo-2.so.0
#60 main
#0 __kernel_vsyscall



----------- .xsession-errors (41 sec old) ---------------------
96: 3a fb 3c 2e  0  0  0  0 
104:  0  f a2  0  2  0  0  0 
112: ff  0  1  0  0EvaPacketManager::processReceiveIM -- unknown transfer type: 6b
(evolution:2831): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:2831): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8d9ba20'
(evolution:2831): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8d9bb40'
(evolution:2831): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
(evolution:2831): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8d9bc60'
(evolution:2831): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8d9bd80'
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-24 04:55:37 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 442949 ***