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 485460 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-10 17:33 UTC by ihab75
Modified: 2007-12-10 00:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description ihab75 2007-10-10 17:33:59 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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 177860608 vsize: 177860608 resident: 60198912 share: 46841856 rss: 60198912 rss_rlim: 4294967295
CPU usage: start_time: 1192036909 rtime: 895 utime: 818 stime: 77 cutime:0 cstime: 1 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 -1208424736 (LWP 3620)]
[New Thread -1276150896 (LWP 3858)]
[New Thread -1286640752 (LWP 3678)]
[New Thread -1265661040 (LWP 3643)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 169306

Thread 1 (Thread -1208424736 (LWP 3620))

  • #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/evolution/2.10/components/libevolution-mail.so
  • #11 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #12 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #13 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib/evolution/2.10/libeutil.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /lib/libgobject-2.0.so.0
  • #25 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #26 ??
    from /lib/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #33 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #34 ??
    from /lib/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #36 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #37 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (13 sec old) ---------------------
Remember to register some spam and ham messages before you
use bogofilter to evaluate mail for its probable spam status!
BBDB spinning up...
(evolution:3620): e-data-server-DEBUG: Loading categories from "/home/ihab/.evolution/categories.xml"
(evolution:3620): e-data-server-DEBUG: Loaded 29 categories
(mail-notification:3410): mail-notification-WARNING **: ihab75@pop.cs.umb.edu: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(evolution:3620): 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?)
(evolution:3620): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x94e9140'
(evolution:3620): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x94e9260'
(mail-notification:3410): mail-notification-WARNING **: ihab75@pop.cs.umb.edu: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
--------------------------------------------------
Comment 1 Tobias Mueller 2007-12-10 00:54:42 UTC 
Thanks for taking the time to report this bug.
It's most likely that this particular bug is the fedora specific bug 447591:
   GLib-GObject-WARNING **: gsignal.c:1669: signal
   `source_selected' is invalid for instance

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.
As debug symbols are missing, it's just a guess anyway since we can't determine the issue without debug information. Feel free to install debug information and open a new bug. See http://live.gnome.org/GettingTraces for details

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