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


Summary:	crash in Calendar:


Status:	RESOLVED DUPLICATE of bug 431459

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-12-29 01:26 UTC by sai
Modified:	2007-12-29 14:03 UTC

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

Description sai 2007-12-29 01:26:07 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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 140660736 vsize: 140660736 resident: 39567360 share: 30457856 rss: 39567360 rss_rlim: 4294967295
CPU usage: start_time: 1198891339 rtime: 95 utime: 85 stime: 10 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 -1208957216 (LWP 6639)]
[New Thread -1295570032 (LWP 6663)]
[New Thread -1285080176 (LWP 6661)]
[New Thread -1221698672 (LWP 6657)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 183408

Thread 1 (Thread -1208957216 (LWP 6639))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 g_main_context_check
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 g_main_loop_run
from /lib/libglib-2.0.so.0
#8 bonobo_main
from /usr/lib/libbonobo-2.so.0
#9 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(evolution:32139): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9b7a918'
(evolution:32139): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9b7aa38'
(evolution:32139): GLib-GObject-CRITICAL **: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed
(evolution:32139): GLib-GObject-CRITICAL **: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed
(evolution:32139): Pango-CRITICAL **: pango_cairo_context_set_font_options: assertion `PANGO_IS_CONTEXT (context)' failed
CalDAV Eplugin starting up ...
** (evolution:6639): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:6639): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
--------------------------------------------------

Comment 1 Tobias Mueller 2007-12-29 14:03:14 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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