[Akonadi] [Bug 375410] Can't fetch email from oauth configured GMail account

2018-11-06 Thread Kolya Ay 
https://bugs.kde.org/show_bug.cgi?id=375410

Kolya Ay  changed:

   What|Removed |Added

 CC||kolya...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 375410] Can't fetch email from oauth configured GMail account

2018-10-04 Thread Fabian Vogt 
https://bugs.kde.org/show_bug.cgi?id=375410

Fabian Vogt  changed:

   What|Removed |Added

 CC||fab...@ritter-vogt.de

--- Comment #5 from Fabian Vogt  ---
(In reply to Daniel Vrátil from comment #4)
> Looks like a packaging error, distributions tend to include .so symlinks in
> their -dev sub-packages but in this case, we need to have the .so in the
> main package, because it's a plugin. Please open a ticket in your
> distribution's tracker.
> 
> (marking as resolved, this is a downstream/packaging issue)

I would say this is partially due to upstream.
Plugins installing a .so with versioning does not make sense and should be
avoided.
That's likely how the mistake happened in the first place.

I just tried removing the SOVERSION/VERSION in libkgapi/src/saslplugin and the
cyrus-sasl pluginviewer still showed the plugin. I'm not sure why the
cyrus-sasl plugins use 3.0.0 though.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 375410] Can't fetch email from oauth configured GMail account

2017-03-08 Thread Daniel Vrátil 
https://bugs.kde.org/show_bug.cgi?id=375410

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DOWNSTREAM

--- Comment #4 from Daniel Vrátil  ---
Looks like a packaging error, distributions tend to include .so symlinks in
their -dev sub-packages but in this case, we need to have the .so in the main
package, because it's a plugin. Please open a ticket in your distribution's
tracker.

(marking as resolved, this is a downstream/packaging issue)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 375410] Can't fetch email from oauth configured GMail account

2017-02-11 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=375410

--- Comment #3 from carlosdema...@gmail.com ---
Finally got this working.  There needs to be a symbolic link pointing from
libkdexoauth2.so to libkdexoauth2.so.3.  Sasl then finds the plugin and all is
peachy!  Is this a cmake problem or a packaging problem?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 375410] Can't fetch email from oauth configured GMail account

2017-02-05 Thread bugzilla_noreply 
https://bugs.kde.org/show_bug.cgi?id=375410

carlosdema...@gmail.com changed:

   What|Removed |Added

 CC||carlosdema...@gmail.com

--- Comment #2 from carlosdema...@gmail.com ---
On kde neon dev edition, kdepim-runtime installs libkdexoauth2.so to:

carlos@carlos-N55SF:/usr/lib/x86_64-linux-gnu/sasl2$ ls
libanonymous.so libdigestmd5.so.2   libntlm.so
libplain.so.2
libanonymous.so.2   libdigestmd5.so.2.0.25  libntlm.so.2  
libplain.so.2.0.25
libanonymous.so.2.0.25  libkdexoauth2.so.3  libntlm.so.2.0.25  libsasldb.so
libcrammd5.so   libkdexoauth2.so.3.0.0  libotp.so 
libsasldb.so.2
libcrammd5.so.2 liblogin.so libotp.so.2   
libsasldb.so.2.0.25
libcrammd5.so.2.0.25liblogin.so.2   libotp.so.2.0.25
libdigestmd5.so liblogin.so.2.0.25  libplain.so

saslpluginviewer reports:

carlos@carlos-N55SF:/usr/lib/x86_64-linux-gnu/sasl2$ saslpluginviewer 
Installed and properly configured auxprop mechanisms are:
sasldb
List of auxprop plugins follows
Plugin "sasldb" ,   API version: 8
supports store: yes

Installed and properly configured SASL (server side) mechanisms are:
  DIGEST-MD5 EXTERNAL OTP CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS
Available SASL (server side) mechanisms matching your criteria are:
  DIGEST-MD5 OTP CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS
List of server plugins follows
Plugin "digestmd5" [loaded],API version: 4
SASL mechanism: DIGEST-MD5, best SSF: 128, supports setpass: no
security flags: NO_ANONYMOUS|NO_PLAINTEXT|MUTUAL_AUTH
features: PROXY_AUTHENTICATION|SUPPORTS_HTTP
Plugin "otp" [loaded],  API version: 4
SASL mechanism: OTP, best SSF: 0, supports setpass: yes
security flags: NO_ANONYMOUS|NO_PLAINTEXT|FORWARD_SECRECY
features: WANT_CLIENT_FIRST|PROXY_AUTHENTICATION
Plugin "crammd5" [loaded],  API version: 4
SASL mechanism: CRAM-MD5, best SSF: 0, supports setpass: no
security flags: NO_ANONYMOUS|NO_PLAINTEXT
features: SERVER_FIRST
Plugin "ntlm" [loaded], API version: 4
SASL mechanism: NTLM, best SSF: 0, supports setpass: no
security flags: NO_ANONYMOUS|NO_PLAINTEXT
features: WANT_CLIENT_FIRST|SUPPORTS_HTTP
Plugin "plain" [loaded],API version: 4
SASL mechanism: PLAIN, best SSF: 0, supports setpass: no
security flags: NO_ANONYMOUS|PASS_CREDENTIALS
features: WANT_CLIENT_FIRST|PROXY_AUTHENTICATION
Plugin "login" [loaded],API version: 4
SASL mechanism: LOGIN, best SSF: 0, supports setpass: no
security flags: NO_ANONYMOUS|PASS_CREDENTIALS
features:
Plugin "anonymous" [loaded],API version: 4
SASL mechanism: ANONYMOUS, best SSF: 0, supports setpass: no
security flags: NO_PLAINTEXT
features: WANT_CLIENT_FIRST|DONTUSE_USERPASSWD
Installed and properly configured SASL (client side) mechanisms are:
  DIGEST-MD5 EXTERNAL OTP CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS
Available SASL (client side) mechanisms matching your criteria are:
  DIGEST-MD5 EXTERNAL OTP CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS
List of client plugins follows
Plugin "digestmd5" [loaded],API version: 4
SASL mechanism: DIGEST-MD5, best SSF: 128
security flags: NO_ANONYMOUS|NO_PLAINTEXT|MUTUAL_AUTH
features: PROXY_AUTHENTICATION|NEED_SERVER_FQDN|SUPPORTS_HTTP
Plugin "EXTERNAL" [loaded], API version: 4
SASL mechanism: EXTERNAL, best SSF: 0
security flags: NO_ANONYMOUS|NO_PLAINTEXT|NO_DICTIONARY
features: WANT_CLIENT_FIRST|PROXY_AUTHENTICATION
Plugin "otp" [loaded],  API version: 4
SASL mechanism: OTP, best SSF: 0
security flags: NO_ANONYMOUS|NO_PLAINTEXT|FORWARD_SECRECY
features: WANT_CLIENT_FIRST|PROXY_AUTHENTICATION
Plugin "crammd5" [loaded],  API version: 4
SASL mechanism: CRAM-MD5, best SSF: 0
security flags: NO_ANONYMOUS|NO_PLAINTEXT
features: SERVER_FIRST
Plugin "ntlm" [loaded], API version: 4
SASL mechanism: NTLM, best SSF: 0
security flags: NO_ANONYMOUS|NO_PLAINTEXT
features: WANT_CLIENT_FIRST|SUPPORTS_HTTP
Plugin "plain" [loaded],API version: 4
SASL mechanism: PLAIN, best SSF: 0
security flags: NO_ANONYMOUS|PASS_CREDENTIALS
features: WANT_CLIENT_FIRST|PROXY_AUTHENTICATION
Plugin "login" [loaded],API version: 4
SASL mechanism: LOGIN, best SSF: 0
security flags: NO_ANONYMOUS|PASS_CREDENTIALS
features: SERVER_FIRST
Plugin "anonymous" [loaded],API version: 4
SASL mechanism: ANONYMOUS, best SSF: 0
security flags: NO_PLAINTEXT
features: WANT_CLIENT_FIRST

so it appears the plugin is built and installed to the correct position but
sasl isnt loading it.  Plugin version

[Akonadi] [Bug 375410] Can't fetch email from oauth configured GMail account

2017-02-04 Thread Daniel Vrátil 
https://bugs.kde.org/show_bug.cgi?id=375410

Daniel Vrátil  changed:

   What|Removed |Added

 CC||dvra...@kde.org

--- Comment #1 from Daniel Vrátil  ---
Could you please provide output from the "pluginviwer" utility?

The message from SASL (SASL(-4): no mechanism) indicates that SASL cannot find
the XOAUTH plugin. If you have PIM installed in a prefix, you may need to
manually copy libkdexoauth.so to /usr/lib64/sasl2/ because SASL loads plugins
only from there and ignores LD_LIBRARY_PATH and similar.

-- 
You are receiving this mail because:
You are watching all bug changes.