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 465514 - crash in Tasks: Logging into Yahoo
crash in Tasks: Logging into Yahoo
Status: RESOLVED DUPLICATE of bug 447591
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-10 21:03 UTC by robertd05
Modified: 2007-11-30 17:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description robertd05 2007-08-10 21:03:45 UTC
Version: 2.10

What were you doing when the application crashed?
Logging into Yahoo


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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 148873216 vsize: 148873216 resident: 44666880 share: 32657408 rss: 44666880 rss_rlim: 4294967295
CPU usage: start_time: 1186778530 rtime: 806 utime: 641 stime: 165 cutime:104 cstime: 51 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 -1208608016 (LWP 3023)]
[New Thread -1307509872 (LWP 3368)]
[New Thread -1221043312 (LWP 3367)]
[New Thread -1231533168 (LWP 3366)]
[New Thread -1273500784 (LWP 3364)]
[New Thread -1297089648 (LWP 3082)]
[New Thread -1263002736 (LWP 3078)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1307509872 (LWP 3368))

  • #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 __nptl_deallocate_tsd
    from /lib/libpthread.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6


----------- .xsession-errors (1180 sec old) ---------------------
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
(evolution:3023): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one
(evolution:3023): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'
** (evolution:3023): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3023): DEBUG: mailto URL program: evolution
(evolution:3023): 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:3023): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa577010'
(evolution:3023): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa577130'
--------------------------------------------------
Comment 1 Suman Manjunath 2007-11-30 17:51:58 UTC
(evolution:3023): GLib-GObject-WARNING **: gsignal.c:1669: signal
`source_selected' is invalid for instance `0xa577010'
(evolution:3023): GLib-GObject-WARNING **: gsignal.c:1669: signal
`source_selected' is invalid for instance `0xa577130'

This is bug #447591, which is fixed now.
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 447591 ***