Bug 486197 – 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 486197 - crash in Calendar: 进行手选项设置


Summary:	crash in Calendar: 进行手选项设置


Status:	RESOLVED DUPLICATE of bug 441638

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	2.10.x (obsolete)
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-13 00:25 UTC by cuizhigang
Modified:	2007-10-14 13:29 UTC

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

Description cuizhigang 2007-10-13 00:25:58 UTC

What were you doing when the application crashed?
进行手选项设置


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 159043584 vsize: 159043584 resident: 39374848 share: 23126016 rss: 39374848 rss_rlim: 4294967295
CPU usage: start_time: 1192234880 rtime: 984 utime: 929 stime: 55 cutime:1 cstime: 2 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 -1208727840 (LWP 6334)]
[New Thread -1356878960 (LWP 6427)]
[New Thread -1293571184 (LWP 6361)]
[New Thread -1221014640 (LWP 6352)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 169862

Thread 2 (Thread -1356878960 (LWP 6427))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 ??
from /lib/libglib-2.0.so.0
#9 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#10 g_slist_free
from /lib/libglib-2.0.so.0
#11 g_strsplit
from /lib/libglib-2.0.so.0
#12 camel_uid_cache_new
from /usr/lib/libcamel-provider-1.2.so.10
#13 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 ??
from /lib/libglib-2.0.so.0
#16 ??
from /lib/libglib-2.0.so.0
#17 start_thread
from /lib/libpthread.so.0
#18 clone
from /lib/libc.so.6



----------- .xsession-errors (6 sec old) ---------------------
(evolution:6334): 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?)
BBDB spinning up...
(evolution:6334): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa044000'
(evolution:6334): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa044120'
(evolution:6334): 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:6334): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa044240'
(evolution:6334): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa044360'
(evolution:6334): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:6334): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------

Comment 1 Tobias Mueller 2007-10-14 13:29: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 441638 ***