Bug 394319 - sasl plugin for xoauth2 not properly registered(?)
Summary: sasl plugin for xoauth2 not properly registered(?)
Status: RESOLVED FIXED
Alias: None
Product: libkgapi
Classification: Frameworks and Libraries
Component: General (show other bugs)
Version: GIT
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-16 10:52 UTC by Michi
Modified: 2019-03-09 08:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
sasl plugins (5.62 KB, text/plain)
2018-05-16 10:52 UTC, Michi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michi 2018-05-16 10:52:39 UTC
Created attachment 112684 [details]
sasl plugins

since updating to the latest git version I can no longer connect to the gmail server.

akonadictl says:
org.kde.pim.kimap: sasl_client_start failed with: -4 "SASL(-4): no mechanism available: No worthy mechs found"

now, if I call pluginviewer from cyrus-sasl it shows me the list of registered plugins which I will upload as an attachment. Note that libkdexoauth2.so.3.0.0 is installed under /usr/lib64/sasl2/ together with all the other sasl plugins.

I assume it has to do with commmit 2af9da57a20f041f55fcff5ccdf6d687b9d99510
Comment 1 Daniel Vrátil 2019-02-21 23:55:18 UTC
The problem was in the soname (or the missing soname symlinks) if I recall correctly, this should be fixed now, though.

Is this still reproducible? I haven't heard anything from opensuse packagers in a while about this.
Comment 2 Michi 2019-02-22 13:10:52 UTC
(In reply to Daniel Vrátil from comment #1)
> The problem was in the soname (or the missing soname symlinks) if I recall
> correctly, this should be fixed now, though.
> 
> Is this still reproducible? I haven't heard anything from opensuse packagers
> in a while about this.

it is indeed working now

bye Michi
Comment 3 Bug Janitor Service 2019-03-09 04:33:06 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!