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 477595 - crash in Tasks: adding my password to th...
crash in Tasks: adding my password to th...
Status: RESOLVED DUPLICATE of bug 475583
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-16 21:43 UTC by weillo
Modified: 2007-09-29 18:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description weillo 2007-09-16 21:43:50 UTC 
What were you doing when the application crashed?
adding my password to the smtp server


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 137621504 vsize: 137621504 resident: 34762752 share: 21344256 rss: 34762752 rss_rlim: 4294967295
CPU usage: start_time: 1189985288 rtime: 1980 utime: 1807 stime: 173 cutime:72 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208858912 (LWP 3137)]
[New Thread -1229386864 (LWP 3481)]
[New Thread -1271526512 (LWP 3474)]
[New Thread -1336271984 (LWP 3381)]
[New Thread -1239901296 (LWP 3213)]
[New Thread -1293894768 (LWP 3205)]
(no debugging symbols found)
0x008f6402 in __kernel_vsyscall ()

+ Trace 163413

Thread 1 (Thread -1208858912 (LWP 3137))

  • #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_free1
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free_1
    from /lib/libglib-2.0.so.0
  • #10 g_slist_remove
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (19 sec old) ---------------------
(nautilus:3253): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(evolution:3137): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3137): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3137): 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:3137): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa222128'
(evolution:3137): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa222248'
(evolution:3137): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3137): e-data-server-ui-WARNING **: El archivo de claves no tiene la clave «smtp:__weillo;auth_PLAIN@smtp.correo.yahoo.es_»
(evolution:3137): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3137): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 Suman Manjunath 2007-09-29 18:54:15 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 475583 ***