From kde-pim  Tue Aug 01 16:12:44 2017
From: Christian Mollekopf <chrigi_1 () fastmail ! fm>
Date: Tue, 01 Aug 2017 16:12:44 +0000
To: kde-pim
Subject: Re: Kube flatpak: SASL(-4): no mechanism available: No worthy mechs found
Message-Id: <1501603964.194746.1059751896.42014002 () webmail ! messagingengine ! com>
X-MARC-Message: https://marc.info/?l=kde-pim&m=150160398126937

On Mon, Jul 31, 2017, at 10:23 PM, Daniel Vr=C3=A1til wrote:
> On Monday, July 31, 2017 9:47:03 PM CEST Christian Mollekopf wrote:
> > Yeah, this seems to be a flatpak only issue.
> >=20
> > You could try "pluginviewer -c" or "saslpluginviewer -c" to list
> > available plugins.
> >=20
> > I have opened a ticket in phabricator: https://phabricator.kde.org/T6687
>=20
> The SASL plugin is likely installed to the /app prefix, so you need to
> set=20
> SASL_PATH env variable to point to /app/usr/lib(64)/sasl2 first, then to
> the default location and all should work.
>=20

Thanks for the hint =3D)

I can see the sasl plugins in
.local/share/flatpak/runtime/org.kde.Platform/x86_64/master/active/files/li=
b/sasl2,
and according to my understanding that should be mounted under /usr (the
app filesystem is mounted under /app),
so, I think this should work. Also, it seems to work for Kontact?

I've now added  "--env=3DSASL_PATH=3D/app/usr/lib/sasl2;/usr/lib/sasl2" to
the flatpak, perhaps it helps.

Cheers,
Christian