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 500674 - crash in Tasks: working calendar evoluti...
crash in Tasks: working calendar evoluti...
Status: RESOLVED DUPLICATE of bug 460409
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-30 16:11 UTC by Greg Ennis
Modified: 2007-11-30 19:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Greg Ennis 2007-11-30 16:11:17 UTC 
Version: 2.10

What were you doing when the application crashed?
working calendar evolution  seems to happen a lot


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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 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: 173441024 vsize: 173441024 resident: 85667840 share: 51556352 rss: 85667840 rss_rlim: 4294967295
CPU usage: start_time: 1196430563 rtime: 3424 utime: 3158 stime: 266 cutime:0 cstime: 5 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208203552 (LWP 3406)]
[New Thread -1324184688 (LWP 7573)]
[New Thread -1376633968 (LWP 7570)]
[New Thread -1247507568 (LWP 3485)]
[New Thread -1297364080 (LWP 3463)]
(no debugging symbols found)
0x0030f402 in __kernel_vsyscall ()

+ Trace 180233

Thread 2 (Thread -1324184688 (LWP 7573))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/i686/nosegneg/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/nosegneg/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 __nptl_deallocate_tsd
    from /lib/i686/nosegneg/libpthread.so.0
  • #10 start_thread
    from /lib/i686/nosegneg/libpthread.so.0
  • #11 clone
    from /lib/i686/nosegneg/libc.so.6 


----------- .xsession-errors (94 sec old) ---------------------
(evolution:3406): e-dateedit.c-WARNING **: time_text:00:00
(evolution:3406): e-utils-CRITICAL **: e_dialog_editable_get: assertion `GTK_IS_EDITABLE (widget)' failed
(evolution:3406): e-utils-CRITICAL **: e_dialog_editable_get: assertion `GTK_IS_EDITABLE (widget)' failed
(evolution:3406): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:3406): 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:3406): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97f57f8'
(evolution:3406): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97f5918'
--------------------------------------------------
Comment 1 Suman Manjunath 2007-11-30 19:57:41 UTC 
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 460409 ***