• It would be good to have a valid ldapurl, just to make sure that kontact is creating the same.
• kdebugdialog enable kldap and retry and give us the log.

It sounds mostly like the settings to LDAP are not correct and that's why the password is not storred.

~ cat .kde/share/config/kabldaprc
[LDAP]
NumHosts=0
NumSelectedHosts=1
SelectedAuth0=Simple
SelectedBase0=dc=example,dc=org
SelectedBind0=uid=doe,ou=People,dc=example,dc=org
SelectedHost0=ldab.example.org
SelectedMech0=DIGEST-MD5
SelectedPageSize0=0
SelectedPort0=389
SelectedSecurity0=None
SelectedSizeLimit0=0
SelectedTimeLimit0=0
SelectedUser0=
SelectedVersion0=3
~

The problem is reproducable:

There are responses in OTRS

OTRS #1100023
Requests for user comments should go there

OTRS #1100026
Requests for user comments should go there.

OTRS #1100028, there are user comments on that.

In T1238#19147, @adomaitis wrote:

OTRS ticket #1016880. All requests for user comments should go there.

OTRS ticket #1016880. All requests for user comments should go there.

while/after closing the application (probably a callback into something that is no longer existing).

Can you please add a screenshot pf the password dialog. There are different dialogs, that ask for the password...
Can you chack if the password is stored in kwallet? (in ldapclient)
cat .kde/share/config/kabldaprc (replace password and host and everything else that is sensible data with fake data, but please mark the part that you replaced)

The theorie I have is:

• baloo returns items, that are not valid anymore in PimItem, but akonadi tries to add them to the search collection and this fails fo the constrain.

only for triaging it.

Resolved in kdepim 4.13.0.16

Kontact now at least no longer crashes, the problem in libkolabxml remains though.

I'm running this patch from Kontact:4.13;Git, and it seems to work just fine. If no issues arise this will be rolled out to Kontact:4.13:Development

verified with our testinstance.
also valid for declinedinvitations.

The tabbed view can be enabled in the settings -> views -> agenda view -> "Switch between views with tabs"

This was most likely broken by kdepimlibs "Avoid deleting exceptions when disabling a calendar". In other words it used to work by chance due to a bug. It seems like we have to explicitly delete exceptions whereever the incidencechanger is used.

This probably needs to be fixed in CalendarView::deleteIncidence, after we have asked the user if he wants to delete all occurrences.

Nevermind the issue with search collections. The item is only linked into the collection, pimitemtable doesn't actually contain anything different, so the original idea should work just fine.

Can you be more clear what you mean with tabbed view? I have no glue in what situation you are talking about a tabbed view - in korganizer/kmail/calednerview/...?

We need to sit down, to construct a solution for that, where we get the full populated collection.

Can confirm with our test instance.

okay the delete a simple mail is a an issue when the trash resource is set and than kontact is not restarted. But it is fixed, when kontact is restarted.