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 509829 - crash in Tasks: using evolution with ima...
crash in Tasks: using evolution with ima...
Status: RESOLVED DUPLICATE of bug 445309
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-16 05:30 UTC by zeugma
Modified: 2008-01-16 12:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description zeugma 2008-01-16 05:30:43 UTC 
Version: 2.10

What were you doing when the application crashed?
using evolution with imaps against exchange 2007 server.


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.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 149897216 vsize: 149897216 resident: 55861248 share: 40017920 rss: 55861248 rss_rlim: 4294967295
CPU usage: start_time: 1200461335 rtime: 316 utime: 286 stime: 30 cutime:0 cstime: 0 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 -1208543520 (LWP 10427)]
[New Thread -1292264560 (LWP 10503)]
[New Thread -1303049328 (LWP 10466)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 185524

Thread 2 (Thread -1292264560 (LWP 10503))

  • #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 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #7 PR_Lock
    from /usr/lib/libnspr4.so
  • #8 ??
    from /usr/lib/libnspr4.so
  • #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 (20 sec old) ---------------------
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a5 specified for 0x42008f7 (Error: p4 ).
CalDAV Eplugin starting up ...
** (evolution:10427): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:10427): DEBUG: mailto URL program: evolution
(evolution:10427): 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:10427): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa6fa020'
(evolution:10427): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa6fa140'
(evolution:10427): e-data-server-ui-WARNING **: Key file does not have key 'imap:__mnielsen;auth_NTLM@owa.goldengate.com_'
--------------------------------------------------
Comment 1 Tobias Mueller 2008-01-16 12:42:04 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, 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.


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