flatpak, KDE PIM, sandboxing and akonadi data

René J.V. Bertin rjvbertin at gmail.com
Thu Jul 4 15:37:13 BST 2019

On Thursday July 04 2019 16:24:09 Daniel Vrátil wrote:

>Yes, the Flatpak'ed Akonadi stores data, database and configuration completely 
>separately from the non-sandboxed Akonadi.

Thanks. Interesting in fact: I tried installing a few simple KDE applications through flatpak and they *do* get their settings from ~/.config . That doesn't mean of course that they store them there, and it's a bit counterproductive because you start getting warnings and non-optimal behaviour if you've configured your look and feel to use resources (themes, fonts, icons, ...) not available to the flatpak sandbox.

The resulting look was so awful that I didn't even feel like trying to install Kontact...

>Yes, you have to stop the main Akonadi and PIM apps before running the 
>Flatpak'ed one due to DBus name conflicts - unfortunately when I first created 
>the Flatpak it did not occur to me the DBus names are going to leak outside of 

I also checked that, and noted that flatpak'ed applications indeed use the same DBus instance. At least that allows them to integrate a bit better.


More information about the kdepim-users mailing list