GNOME Bugzilla – Bug 473218
crash in Tasks: kalendarz
Last modified: 2007-09-03 16:56:46 UTC
Version: 2.10 What were you doing when the application crashed? kalendarz 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 113221632 vsize: 113221632 resident: 44077056 share: 32231424 rss: 44077056 rss_rlim: 4294967295 CPU usage: start_time: 1188834599 rtime: 338 utime: 316 stime: 22 cutime:2 cstime: 6 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 -1208699168 (LWP 4950)] [New Thread -1219974256 (LWP 4984)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 160118
Thread 1 (Thread -1208699168 (LWP 4950))
----------- .xsession-errors (103 sec old) --------------------- we need to scale up scale = 1 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4950): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4950): 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 (evolution:4950): 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:4950): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a3b010' (evolution:4950): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8a3b130' --------------------------------------------------
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 437038 ***