The problem only occourse with incorrect formatted To field (rcm and kmail format it correctly).

https://support.kolabsys.com/provider?Action=AgentTicketZoom&TicketID=21254&ArticleID=75252&ZoomExpand=0#75252

mmh hard to descide what happens here.

This is fine - we need to connect to result (KJob *) to get the correct signal we search for

with kleopatra it should be possible to debug it further.

well make sure that gnupgp2, libpgp4 and libkleo4 is installed. And gpg-agent is running. This should fix the problem. I triggered a new build with kleopatra. So at least kleopatra can now be installed und used.

but still kleopatra is not needed for providing cryptosupport.

At least wiered why OBS do not read the complete kleopatra.install file.

Create a category (by creating an event with a new category) or use a existing one.

The not ended Akonadi::TagFetchJob only occures if no tag is avaiable in Akonadi.
Than TagFetchJob::doHandleResponse is not callled and no timer is triggered that ends the result.

The problem is that the job do not trigger onTagsReceived:

looks fine

Can reproduce - via rcm:

• create new category
• create a event with that new category tag

Works in kdepim and @machniak tells, it should not be an issue for roundcube anymore.

Create a Event as jane:

• start at monday (13.6)
• repeat on dates wednesday (15.6) & Friday (17.6)
• invite john to the event

At least from the Screenshots it is Roundcube issue.

@mollekopf : When I understood you correctly, there is no way to provide debug symbols because of legal issues, because windows disallow them.

moved now to messageviewer.

Now the rendering step is splittd away from the process, but still it lives inside mimetreeparser.

the priority change happended by accident

Added the infomations - but have no glue what is there technical level. That's why only some points.

ship it

now it checks if we have anything to add and do not crash,
if there is is nothing to add.

this does not fix the issue and i rework this patch

I have now look through the code paths in kdepim that interacts with ldap. We actually use kdepim/libkdepim/ldap/ldapclientsearch.* for getting seach relusts from ldap servers (incidenceeditor,resourcemanagement and addresslineedit).
ldapclientsearch reads the config by itself and is treiggered to reread it when the config file is changed.
it uses ldapclientsearchconfig to set a ldapserver settings with password:

• 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:

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.