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 521101 - crash in Tasks: setting up preferences
crash in Tasks: setting up preferences
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-03-07 22:19 UTC by ron
Modified: 2008-03-20 15:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ron 2008-03-07 22:19:19 UTC
Version: 2.10

What were you doing when the application crashed?
setting up preferences


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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 134901760 vsize: 134901760 resident: 47927296 share: 36691968 rss: 47927296 rss_rlim: 4294967295
CPU usage: start_time: 1204927770 rtime: 219 utime: 198 stime: 21 cutime:36 cstime: 13 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 -1208427792 (LWP 4697)]
[New Thread -1283736688 (LWP 4722)]
[New Thread -1241216112 (LWP 4716)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208427792 (LWP 4697))

  • #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/libgobject-2.0.so.0
  • #6 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #7 g_param_spec_pool_list_owned
    from /lib/libgobject-2.0.so.0
  • #8 ??
    from /lib/libgobject-2.0.so.0
  • #9 ??
    from /lib/libgobject-2.0.so.0
  • #10 g_type_class_unref
    from /lib/libgobject-2.0.so.0
  • #11 g_type_free_instance
    from /lib/libgobject-2.0.so.0
  • #12 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #14 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #19 ??
  • #20 ??
    from /lib/libpthread.so.0
  • #21 ??
  • #22 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 g_slice_alloc
    from /lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall


----------- .xsession-errors (80 sec old) ---------------------
localuser:Ron being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2963
CalDAV Eplugin starting up ...
** (evolution:4308): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4308): 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
CalDAV Eplugin starting up ...
** (evolution:4697): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4697): 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:4697): 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...
--------------------------------------------------
Comment 1 Akhil Laddha 2008-03-20 15:10:30 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 447591 ***