GNOME Bugzilla – Bug 232978
Performing a search against an Active Directory LDAP server caused a crash.
Last modified: 2013-09-10 14:03:39 UTC
Package: Evolution Priority: Normal Version: 1.1.2 Synopsis: Performing a search against an Active Directory LDAP server caused a crash. Bugzilla-Product: Evolution Bugzilla-Component: Contacts [was: Addressbook] Description: Using the LDAP interface to the local AD server and performing a search caused wombat to toss its cookies and die a horrible screaming death. What's up with that? Debugging Information: (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)...[New Thread 1024 (LWP 10481)] 0x410af369 in __wait4 () at __wait4:-1 in __wait4
+ Trace 29584
Thread 1 (Thread 1024 (LWP 10481))
Unknown reporter: peter@berghold.net, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** bug 234280 has been marked as a duplicate of this bug. ***
*** bug 234716 has been marked as a duplicate of this bug. ***
*** bug 234429 has been marked as a duplicate of this bug. ***
This should be fixed in 1.2
I don't know what you're talking about in your resolution notes. This is NOT resolved. I have reported it for 1.2, not any other version. Bojan
1.2 Working here to an AD with Exchange 2K. I do have a problem with Evo loosing the LDAP link and failing to authenticate until I do a killev.
*** http://bugzilla.ximian.com/show_bug.cgi?id=35221 has been marked as a duplicate of this bug. ***
*** bug 235291 has been marked as a duplicate of this bug. ***
Changing target milestone since too many duplicates arrive.
*** bug 235551 has been marked as a duplicate of this bug. ***
set milestone to 1.2.2.
*** bug 235802 has been marked as a duplicate of this bug. ***
*** bug 237748 has been marked as a duplicate of this bug. ***
Missed 1.2.2 milestone. Setting to 1.2.3 and duplicates keep arriving...
*** http://bugzilla.ximian.com/show_bug.cgi?id=37817 has been marked as a duplicate of this bug. ***
*** bug 238841 has been marked as a duplicate of this bug. ***
*** bug 238914 has been marked as a duplicate of this bug. ***
*** bug 240151 has been marked as a duplicate of this bug. ***
Got mine to blow up like this by changing my LDAP Active Directory to anonymous authentification and waiting for it to time out after the first connection and trying to look at the LDAP data again. Before having anonymous set-up, it would connect fine as a user but after timeout it would fail to authenticate again until I did a killev. Evolution 1.2.4 Gentoo 1.4 w/ gcc3.2.2
This bug is still present in 1.4.0. It was running on Red Hat 8.0, Ximian Desktop 2, everything up-to-date as of July 2, 2003.
*** bug 236597 has been marked as a duplicate of this bug. ***
*** bug 244172 has been marked as a duplicate of this bug. ***
*** bug 240699 has been marked as a duplicate of this bug. ***
*** http://bugzilla.ximian.com/show_bug.cgi?id=44533 has been marked as a duplicate of this bug. ***
Since there are no individual reports of this crash in 1.4, I'm closing this report as presumed fixed in 1.4 (Yes, I know there's a mentioned 1.4 here, but without a backtrace it's probable it's a different problem since no other reports arrived with a similar backtrace). If anybody can duplicate this problem in 1.4.4 or greater, please open a new report. Presuming fixed.
I have still this problem with evolution 1.4.5 on debian woody. Random when I try to performing a search against an AD LDAP server, caused a crash...When the errorr occurred I must restart the software. I think the bug is present also in the version 1.4.x bye.
Sorry, wihtout a backtrace there's nothing we can do.
It appeared in 1.4.5 indeed. The backtrace there is useless, tho. Reopening
*** bug 251603 has been marked as a duplicate of this bug. ***
When I try to use AD as a directory server I get the following output when trying to connect to the server (env CAMEL_VERBOSE_DEBUG=1 evolution >& /tmp/camel.out) (evolution:6266): e-minicard-CRITICAL **: file e-addressbook-view.c: line 1646 (e_addressbook_view_discard_menus): assertion `view->view_instance' failed I am using evolution-1.4.5-7 on Fedora Core 1. I know that the directory is AD 2003. I have tried to use a ADAM (Active Directory Application Mode) with Evolution and it works great! I am only have issues with AD 2003. This may not be of any use, but I have filled a bug with apache in regards to mod_auth_ldap not working with AD 2003. This may be a related issue: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26538
The same is happening to me. I'm connecting to AD (2k) with authentication and without SSL. I also found that: 1) When the AD Contact Folder is placed in the Autocomplete folder list, names are cut in the first accentuated character. For instance "Andréa XXX YYY" is shown as "Andr". 2) When I try to type the name "Andréa" on the "To" field, evolution dies after I type the "é" character. Here's the backtrace generated by bug-buddy: Backtrace was generated from '/usr/bin/evolution-1.4' (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)...(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)...[New Thread 16384 (LWP 12771)] [New Thread 32769 (LWP 12778)] [New Thread 16384 (LWP 12771)] [New Thread 32769 (LWP 12778)] [New Thread 16386 (LWP 12779)] [New Thread 32771 (LWP 12781)] [New Thread 49156 (LWP 12782)] [New Thread 65541 (LWP 12783)] [New Thread 81926 (LWP 12784)] [New Thread 98311 (LWP 12785)] [New Thread 114696 (LWP 12786)] [New Thread 131081 (LWP 12787)] [New Thread 147466 (LWP 12789)] [New Thread 163851 (LWP 12790)] [New Thread 180236 (LWP 12791)] [New Thread 196621 (LWP 12794)] [New Thread 213006 (LWP 12814)] [New Thread 16384 (LWP 12771)] [New Thread 32769 (LWP 12778)] 0x411d29eb in waitpid () from /lib/libpthread.so.0
+ Trace 49576
Thread 15 (Thread 213006 (LWP 12814))
Thread 14 (Thread 196621 (LWP 12794))
Thread 13 (Thread 180236 (LWP 12791))
Thread 11 (Thread 147466 (LWP 12789))
Thread 10 (Thread 131081 (LWP 12787))
Thread 9 (Thread 114696 (LWP 12786))
Thread 8 (Thread 98311 (LWP 12785))
Thread 7 (Thread 81926 (LWP 12784))
Thread 6 (Thread 65541 (LWP 12783))
Thread 5 (Thread 49156 (LWP 12782))
Thread 4 (Thread 32771 (LWP 12781))
Thread 3 (Thread 16386 (LWP 12779))
Evolution 2.0.2 on Debian Sid here. I have been having this problem since before 1.2 I believe. We have a W2K Active Directory, and Evo or Evo's Data Server crashes. It happens only when it is trying to autocomplete addresses in the to/cc/bcc boxes, and it sometimes keeps the mouse pointer grabbed because it has already popped up the drop down window (albeit empty).
Hi, I'm running SuSE 9.2 with the default versions of Evolution and the connector that's supplied with that (evolution 2.0.1). I've experienced the problem quite few times. My observations are as follows: 1) It seems to happen more frequently when I'm running on a slow link. 2) I think it's possibly only happening (certainly happens more frequently) when it tries to complete on the surname. 3) Once you've got it to complete by using the first name, then completion on the surname seems to work okay after that(is it caching it ? ). Thanks for your help and good luck with hunting problem down.
I need a stack trace from version 2.0.
With evolution-2.2.0.0.200503210400-0.snap.novell.0.1 I don't get a crash. Eventhough the search result is displayed, but I get an error message 'Unable to preform search. This query did not complete successfully.'
Based on last comment closing the bug.
*** Bug 303625 has been marked as a duplicate of this bug. ***