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 476683 - crash in Tasks: working on evolution sen...
crash in Tasks: working on evolution sen...
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-09-13 19:35 UTC by Greg Ennis
Modified: 2007-09-24 16:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Greg Ennis 2007-09-13 19:35:21 UTC
Version: 2.10

What were you doing when the application crashed?
working on evolution sending a email.


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.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 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: 162308096 vsize: 162308096 resident: 64176128 share: 44724224 rss: 64176128 rss_rlim: 4294967295
CPU usage: start_time: 1189709634 rtime: 2062 utime: 1900 stime: 162 cutime:31 cstime: 22 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 -1208191264 (LWP 3371)]
[New Thread -1348719728 (LWP 4148)]
[New Thread -1327740016 (LWP 4145)]
[New Thread -1226036336 (LWP 3451)]
[New Thread -1247409264 (LWP 3448)]
[New Thread -1236526192 (LWP 3413)]
(no debugging symbols found)
0x009be402 in __kernel_vsyscall ()

Thread 3 (Thread -1327740016 (LWP 4145))

  • #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 (88 sec old) ---------------------
(evolution:3371): gtkhtml-WARNING **: No such file or directory
(evolution:3371): gtkhtml-WARNING **: No such file or directory
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
(evolution:3371): 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:3371): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa51b918'
(evolution:3371): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa51ba38'
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
--------------------------------------------------
Comment 1 Suman Manjunath 2007-09-24 16:49:06 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 ***