The implemented solution will use KDateTime::Spec::LocalZone() do determine the offset from utc to use for the conversion,
this requires either a working ktimezoned or a build with libcalendaring to get access to timezone information.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Apr 15 2016
This will be released with akonadi 1.12.42.4
Apr 14 2016
the akonadiserver crashes in this code section:
- The tool will get a new option "--fix-utc-incidences"
- With this option we will rerun the format upgrade against all users, which
will rewrite all objects and and change the start/end/due dates accordingly.
- While rewriting the incidence we have to take dtstart, dtend, dtdue, rdate,
exdate and recurrenceid into account.
This has been fixed in kdepim-runtime 4.13.0.9
This has been fixed in kdepim-runtime 4.13.0.9
Apr 13 2016
A first version of a fix has been implemented in the akonadi dev/mysqlreconnect branch.
Nevermind, I have been able to reproduce this.
This will be fixed in kdepimlibs 4.13.0.14. Packaging pending.
In which application was this crash produced? Do we know anything about which folders have been moved?
This is a non-trivial change that will require extensive experimentation, planning, development and testing.
A better backtrace with debug symbols installed for libksieveui4 and kdelibs5 would be very useful.
Apr 11 2016
Apr 8 2016
This crash should be fixed in kdepimlibs 4.13.0.12 (which is currently being built).
KIO::TransferJob(0x11e8630)
QMap(("{internal~currenthost}cached-www-auth",
"true")("{internal~currenthost}www-auth-challenge", "Basic realm="Kolab
Freebusy"")("{internal~currenthost}www-auth-realm", "Kolab Freebusy"))
korganizer(26282)/kio (KIOJob) KIO::TransferJob::slotFinished:
KUrl("http://$URLTOUSERSXFB.xfb")
korganizer(26282)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished:
KIO::TransferJob(0x11e8630) KIO::Slave(0x81f92f0)
korganizer(26282)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished:
Updating ioslaves with new internal metadata information
korganizer(26282)/kio (Scheduler) KIO::SchedulerPrivate::jobFinished:
Updated configuration of "http" ioslave, pid= 26306
korganizer(26282)/kio (Scheduler)
KIO::SchedulerPrivate::updateInternalMetaData:
KIO::TransferJob(0x11e8630)
QMap(("{internal~currenthost}cached-www-auth",
"true")("{internal~currenthost}www-auth-challenge", "Basic realm="Kolab
Freebusy"")("{internal~currenthost}www-auth-realm", "Kolab Freebusy"))
korganizer(26282)/kdepimlibs (kcalcore)
KCalCore::ICalFormatImpl::Private::readIncidenceBase: The incidence
didn't have any UID! Report a bug to the application that generated
this file.Apr 7 2016
Fixed in kdepimlibs 4.13.0.11
Apr 6 2016
This has been an issue with recurring events. The occurrence date was not calculated correctly, resulting in the wrong date being taken for calculating the UTC offset (the switch from DST was recently). This has been fixed in kdepimlibs.
We have summertime, so it's actually UTC+2 so it's actually the recurring event that is off.
In the weekly agenda view, both are shown at 9:30 (visually, not the text)
Apr 5 2016
Database "akonadi" opened using driver "QMYSQL" Error code: 1062 DB error: "Duplicate entry 'message/rfc822' for key 'name'" Agent instance created in separate process. akonadi_maildispatcher_agent(8999)/libakonadi Akonadi::DefaultResourceJobPrivate::resourceCreateResult: Created maildir resource with id "akonadi_maildir_resource_0" AkonadiAgentServer(9020)/libakonadi Akonadi::CollectionSync::Private::execute: localListDone: false deliveryDone: true AkonadiAgentServer(9020)/libakonadi Akonadi::SessionPrivate::dataReceived: Server protocol version is: 44 Error text: "Duplicate entry 'message/rfc822' for key 'name' QMYSQL3: Unable to execute statement" Query: "INSERT INTO MimeTypeTable (name) VALUES (:0)" Error during insertion into table "MimeTypeTable" "Duplicate entry 'message/rfc822' for key 'name' QMYSQL3: Unable to execute statement" akonadi_mailfilter_agent(9001)/libakonadi Akonadi::EntityTreeModelPrivate::collectionFetchJobDone: Job error: "Failed to create mimetype record" for collection: ()
The "Trash folder" setting in the resource is set to the templates folder (no idea why, perhaps from one of the cases where I nuked the akonadi server but not config)
The output of the akonadi_kolab_resource_3 (not the maildir resource)
This would also mean we have to rename all packages, otherwise they are not coinstallable.
There have been reports of mails still not being sent out which was fixed by reopening the mail and sending it again (that is with the version that doesn't remove the stuck messages from the outbox)
Apr 2 2016
Apr 1 2016
One potential root cause could be a race condition during retrieveItems in the maildir resource (the item has been moved in the database, but the change has not been replayed, so the item sync ends up recreating the item that is still found on disk). This scenario aligns with the id of the item in the outbox being greater than the one in the sent mail folder and the missing attributes. It doesn't seem to align with the revision though.