Resuming timer timer:
Starting timer: QDateTime("Wed Jun 22 16:10:51 2016") 300000
IntervalCheck, collectionExpired: 24
Resuming timer timer:- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jun 22 2016
As a workaround it was suggested to restart akonadi on kontact start, or with a menu option, so users have at least a possibility to fix the issue themselves without restarting their system.
One theory would be that the notification mechanism breaks down, so regular fetches etc. keep working, but kontact no longer reacts to changes.
Jun 20 2016
This ticket now tracks the problem of the event that isn't shown.
It apparently does work sometimes, but not reliably.
Jun 13 2016
Jun 10 2016
Jun 9 2016
Fixed in kdepim 4.13.0.21, kdepimlibs 4.13.0.26
Fixed in kdepim 4.13.0.21
Fixed in kdepimlibs 4.13.0.26, kdepim 4.13.0.21
Fixed in kdepimlibs 4.13.0.26
Fixed in kdepimlibs 4.13.0.26
Fixed in kdepimlibs 4.13.0.26
Jun 8 2016
ok 4.13.0.17 should be used already.
The problem only occourse with incorrect formatted To field (rcm and kmail format it correctly).
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.
The problem is:
- The user has his own identity and that of a delegator configured
- The user creates an event with his own identity as organizer and the delegator as attendee in his own calendar
- Because the delegator is recognized as one of the own identities, the event is (in this case incorrectly) filtered from the own calendar.
Another problem is a segfault, if you close kontact.
Otrs bug is closed
Jun 7 2016
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:
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
I don't know why this ticket exists, but there's T1278 which was for Roundcube. So, maybe this is to check on kdepim.
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.
Jun 6 2016
moved now to messageviewer.