Tickets :: [#8707] turba "read failed: (0) success"

6.0.0-beta1

7/5/25

Summary	turba "read failed: (0) success"
Queue	Turba
Queue Version	2.3.2
Type	Bug
State	Duplicate
Priority	1. Low
Owners
Requester	reinhold.may (at) gmx (dot) de
Created	11/13/2009 (5713 days ago)
Due
Updated	11/30/2009 (5696 days ago)
Assigned
Resolved	11/30/2009 (5696 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	Yes

11/30/2009 10:10:12 AM	Matt Selsky	Comment #5 Version ⇒ 2.3.2	Reply to this comment
OP can confirm, but I think they were using Turba 2.3.2, not FW_3.

11/30/2009 09:21:23 AM	Jan Schneider	Comment #4	Reply to this comment
If this is really a duplicate, it shouldn't happen in FW_3 anymore.

11/30/2009 07:55:40 AM	Matt Selsky	Comment #3 State ⇒ Duplicate	Reply to this comment
Duplicate of ~~bug 8595~~.

11/30/2009 07:07:24 AM	spm (at) boiteauxlettres (dot) sent (dot) at	Comment #2	Reply to this comment
This bug prevents vcard importation and syncML synchronization. See ~~ticket #8735~~. The proposed fix solves both of these issues. Dave.

11/13/2009 05:55:42 PM	reinhold (dot) may (at) gmx (dot) de	Comment #1 Priority ⇒ 1. Low New Attachment: turba_ldap_read_success_0.patch Patch ⇒ Yes Milestone ⇒ Summary ⇒ turba "read failed: (0) success" Type ⇒ Bug State ⇒ Unconfirmed Queue ⇒ Turba	Reply to this comment
turba displays an LDAP error on when the ldap search result is empty. Bugfix posted by Andy Dorman here: http://lists.horde.org/archives/turba/Week-of-Mon-20090921/006254.html but hasn't added but to this bug tracking system as far as I could see.