Bug 281607 - "Invalid iterator ID." on editing LDAP addressbook
Summary: "Invalid iterator ID." on editing LDAP addressbook
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdepim
Classification: Applications
Component: libkdepim (show other bugs)
Version: 4.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-08 09:17 UTC by Pavel Baranchikov
Modified: 2017-01-07 21:34 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Baranchikov 2011-09-08 09:17:55 UTC
Version:           4.4 (using KDE 4.6.0) 
OS:                Linux

Error appears on editing the LDAP address book entry, or adding a new one.

Reproducible: Always

Steps to Reproduce:
1. create LDAP address book with write access for the user (I use GSSAPI for authentication)
2. launch kaddressbook from console
3. add the address book to the KAddressBook application
4. try to add/edit entry from the address book

Actual Results:  
Error arrives in the console: "/usr/bin/akonadi_nepomuk_contact_feeder(9436)" Soprano: "Invalid iterator ID.". Entry looks like modification succeded. No real changes to LDAP has been made

Expected Results:  
The LDAP entry might be added/changed.
Comment 1 Christophe Marin 2011-09-08 09:28:32 UTC
> Version:           4.4 (using KDE 4.6.0) 

This version is too old, please retry with a current version (> 4.7.0)
Comment 2 Pavel Baranchikov 2011-09-09 13:49:05 UTC
Tried with KAddressbook 4.7.0 from KDE 4.7.0. The only difference is that there is no error in console. The address book entry is created in KAddressbook and is seen there, but no real modifications are made on the LDAP directory.
Comment 3 Pavel Baranchikov 2011-09-12 14:32:51 UTC
After akonadi server restart, the fake-created entries (that exist only locally, not at LDAP server) are deleted.
Comment 4 Denis Kurz 2016-09-24 20:59:56 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 21:34:56 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.