SUMMARY *** Just a quick suggestion to avoid to go crazy with 3rd parts libraries... I had a problem with openSSL (which I didn't know) that causes kdeconnect not to read or create the certificates. The error message from kdeconnectd at startup was: "Failed to load Legacy provider". It was ununderstandable (at least for me) what was the problem. I had to download the source code and debug it to understand that the problem was on openSSL. Maybe a better management of the exceptions and exceptions messagges could be useful in the portion of codes that use 3rd parties libraries. *** STEPS TO REPRODUCE 1. delete (or invalidate) your ssl config file 2. try to launch kdeconnectd OBSERVED RESULT EXPECTED RESULT Failed to load Legacy provider SOFTWARE/OS VERSIONS Linux/KDE Plasma: slackware current (but ubuntu current too) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Just a suggestion for the future, nothing more. Thank you for your great job!
I agree that the message is confusing. This message is printed by QCA, re-assigning the bug.
So what would be considered ok? assing "OpenSSL" in front of "Legacy"?
Well, I don't know... somenthing like "Cannot read or create certificate", but my suggestion wasn't only for my specific case... It would be a general way on coding using 3rd party libraries. Thank you!
Something like "Cannot read or create certificate" makes no sense as error for QCA to report given that is not the error that is happening at that particular point in time.
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!