Bug 486220 – 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 486220 - crash in Calendar:


Summary:	crash in Calendar:


Status:	RESOLVED DUPLICATE of bug 442030

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-13 03:15 UTC by 13313325996
Modified:	2007-10-15 13:27 UTC

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

Description 13313325996 2007-10-13 03:15:03 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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 139980800 vsize: 139980800 resident: 49528832 share: 34902016 rss: 49528832 rss_rlim: 4294967295
CPU usage: start_time: 1192245031 rtime: 442 utime: 414 stime: 28 cutime:2 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 -1208441120 (LWP 3375)]
[New Thread -1243264112 (LWP 3424)]
[New Thread -1255011440 (LWP 3411)]
[New Thread -1232774256 (LWP 3410)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 169881

Thread 1 (Thread -1208441120 (LWP 3375))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libbonoboui-2.so.0
#11 ??
from /lib/libglib-2.0.so.0
#12 bonobo_ui_engine_dispose
from /usr/lib/libbonoboui-2.so.0
#13 ??
from /usr/lib/libbonoboui-2.so.0
#14 ??
#15 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#16 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#18 e_shell_close_all_windows
#19 ??
#20 ??
from /lib/libglib-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /lib/libglib-2.0.so.0
#24 bonobo_main
from /usr/lib/libbonobo-2.so.0
#25 main
#0 __kernel_vsyscall



----------- .xsession-errors (88 sec old) ---------------------
CalDAV Eplugin starting up ...
** (evolution:3375): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3375): DEBUG: mailto URL program: evolution
(evolution:3375): 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:3375): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9abd000'
(evolution:3375): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9abd120'
CalDAV Eplugin starting up ...
(evolution:3375): e-data-server-DEBUG: Loading categories from "/home/zhang/.evolution/categories.xml"
(evolution:3375): e-data-server-DEBUG: Loaded 29 categories
(evolution:3375): e-utils-WARNING **: calling e_icon_factory_get_icon_filename with unknown icon_size value (48)
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-10-15 13:27:50 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 442030 ***