GNOME Bugzilla – Bug 268360
e-d-s crash when entering LDAP address in composer
Last modified: 2005-09-28 12:32:00 UTC
Distribution: Novell Linux Desktop 9 (i586) Package: Evolution-Data-Server Priority: Blocker Version: GNOME2.6. unspecified Gnome-Distributor: Novell, Inc. Synopsis: e-d-s crash when entering address in composer Bugzilla-Product: Evolution-Data-Server Bugzilla-Component: Contacts Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Was entering an email address in the Cc: field in the composer. Four characters in, e-d-s crashed. Steps to reproduce the crash: 1. Reply to existing mail. 2. Add a new name in the Cc: field (I got as far as "kfra") Expected Results: Stability How often does this happen? Once so far, though I've seen variations on this bug many times in the past. Additional Information: NLD 9 release candidate 3ish (rolling updates) evolution-2.0.1-1.3 evolution-data-server-1.0.1-2.3 Needless to say, I'm inclined to blame addressbook lookup. Debugging Information: Backtrace was generated from '/usr/local:/opt/gnome:/usr/libexec/evolution-data-server' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1084296640 (LWP 4888)] [New Thread 1114897328 (LWP 10393)] [Thread debugging using libthread_db enabled] [New Thread 1084296640 (LWP 4888)] [New Thread 1114897328 (LWP 10393)] [Thread debugging using libthread_db enabled] [New Thread 1084296640 (LWP 4888)] [New Thread 1114897328 (LWP 10393)] [New Thread 1094794160 (LWP 10391)] [New Thread 1096895408 (LWP 4963)] [New Thread 1087503280 (LWP 4895)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in ?? ()
+ Trace 51035
Thread 3 (Thread 1094794160 (LWP 10391))
Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** bug 268368 has been marked as a duplicate of this bug. ***
Unfortunately, the backtrace here isn't very helpful...
It does appear to be LDAP related. These reports are fairly old though, we should check for more duplicates.
*** bug 266960 has been marked as a duplicate of this bug. ***
Could be a dupe of 69069
Reassigning bugs that no longer belong to me.
Is this still valid?
I've had similar crashes in 2.2, but not yet in 2.3. I can try to reproduce it once I get to the office.
Please try to get the debug traces?
*** This bug has been marked as a duplicate of 300157 ***
Removed erroneous target milestone values and set them to FUTURE