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 456032 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 441638
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-11 21:10 UTC by santiago.hoyos
Modified: 2007-07-12 11:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description santiago.hoyos 2007-07-11 21:10:24 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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 162652160 vsize: 162652160 resident: 69787648 share: 41095168 rss: 69787648 rss_rlim: 4294967295
CPU usage: start_time: 1184182555 rtime: 4964 utime: 4497 stime: 467 cutime:73 cstime: 29 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 -1208965408 (LWP 2427)]
[New Thread -1307575408 (LWP 3475)]
[New Thread -1220166768 (LWP 2847)]
[New Thread -1295250544 (LWP 2472)]
[New Thread -1241539696 (LWP 2442)]
(no debugging symbols found)
0x007e6402 in __kernel_vsyscall ()

Thread 2 (Thread -1307575408 (LWP 3475))

  • #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 (44 sec old) ---------------------
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files
CalDAV Eplugin starting up ...
** (evolution:2427): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2427): 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:2427): e-data-server-DEBUG: Loading categories from "/root/.evolution/categories.xml"
(evolution:2427): e-data-server-DEBUG: Loaded 29 categories
(evolution:2427): 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:2427): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9eac498'
(evolution:2427): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9eac5b8'
--------------------------------------------------
Comment 1 palfrey 2007-07-12 11:16:55 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 ***