[Kde-pim] Mime type problem in Akonadi resource

David Jarvie djarvie at kde.org
Tue Aug 24 19:15:02 BST 2010


On Tuesday 24 August 2010 13:27:19 David Jarvie wrote:
> Since updating Akonadi yesterday, the KAlarm Akonadi resource (which by default isn't built yet) crashes on startup in Akonadi::ItemSerializer::serialize(). It looks as if the metatype for class KAEvent (which is the payload type for the resource) is not being recognised in the relevant akonadi_serializer class, despite the fact that its source file includes kaevent.h, which contains a declaration Q_DECLARE_METATYPE(KAEvent);
> 
> Is there some other requirement for a custom metatype to be recognised in Akonadi serializers? (There is an X-Akonadi-Class entry in the .desktop file.)

It turns out that the mime type is not being recognised in PluginRegistry::findBestMatchImpl(), resulting in a null metatype. Yet the relevant mime type is in the Akonadi database (verified by akonadiconsole, in the mimetypetable database table). It's specified in the .desktop files for both the resource and the akonadi_serializer.

So why might the mime type not be recognised by KMimeType?

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20100824/2c811be7/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list