[QGIS-Developer] Authentication seems broken in master

[Bernhard Ströbl]

Hi Andreas,
I was under the impression that the qgis-auth.db is supposed to reside 
at $HOME/.local/share/QGIS/QGIS3/profiles/default because that is where 
QGIS3 recently installed plugins (a while ago indeed it was 
$HOME/.qgis3). I just copied my qgis-auth.db from $HOME/.qgis2 to 
$HOME/.local/share/QGIS/QGIS3/profiles/default and get "Auth db query 
exec() FAILED", too, upon opening options-cAuthentication

Bernhard

Am 02.11.2017 um 15:18 schrieb Andreas Neumann:
> Hi Alessandro,
>
> Already at the start of QGIS I get two times the error message:
>
> WARNING: Auth db query exec() FAILED
>
> WARNING: Auth db query exec() FAILED
>
> This happens during startup of QGIS without any user interaction.
>
> I had a look at the permissions of $HOME/.qgis3/qgis-auth.db - and they
> seem fine to me.
>
> Perhaps, if I/we can fix this, the other subsequent error message go
> away as well?
>
> Thanks,
>
> Andreas
>
>
> On 2017-11-02 15:04, Alessandro Pasotti wrote:
>
>> On Thu, Nov 2, 2017 at 2:54 PM, Andreas Neumann <a.neumann at carto.net
>> <mailto:a.neumann at carto.net>> wrote:
>>
>>     Hi Alessandro,
>>
>>     Thank you for your reply.
>>
>>     I don't know what I need to do to fix the auth-db issues. I keep
>>     getting tons of error messages like
>>
>>     Auth DB query exec failed()
>>
>>     for existing connections.
>>
>>     This is for access through the GUI, not through Python.
>>
>>     Also, when I try to create a new auth config entry, it doesn't
>>     know my master password anymore and can't create a new one. Pretty
>>     broken currently.
>>
>>     Does this mean that my auth-db is corrupt and that I need to
>>     remove it and create a new one?
>>
>>
>>
>> I've honestly no idea: it is not broken for me, I'm using the auth
>> manager right now on master with no issues and the authmanager tests
>> are all green (and there are quite a few).
>>
>> I suggest you to file a bug report with some more details that can
>> help to reproduce the issue.
>>
>> Thanks!
>>
>>
>>
>>     Thanks for your reply,
>>
>>     Andreas
>>
>>     On 2017-11-02 14:38, Alessandro Pasotti wrote:
>>
>>
>>         On Thu, Nov 2, 2017 at 2:19 PM, Andreas Neumann
>>         <a.neumann at carto.net <mailto:a.neumann at carto.net>> wrote:
>>
>>             Same for me. Very annoying.
>>
>>             Bernhard please file a ticket and assign it to Alessandro
>>             or Luigi.
>>
>>             Thanks,
>>
>>
>>
>>             Andreas
>>
>>
>>         Hi,
>>
>>         the API has changed and the singleton has been removed.
>>
>>         Auth manager instance is now accessible through the
>>         QgsApplication as QgsApplication.authManager()
>>
>>         Please file a ticket for filling the API break document that
>>         the lazy coder forgot to do (blame on him!).
>>
>>         btw, the lazy coder did not forget to fill the API break
>>         document for the `get` removal, see
>>
>>         https://qgis.org/api/api_break.html#qgis_api_break_3_0_QgsAuthManager
>>         <https://qgis.org/api/api_break.html#qgis_api_break_3_0_QgsAuthManager>
>>
>>
>>         On 2017-11-02 14:05, Bernhard Ströbl wrote:
>>
>>             Hi all,
>>
>>             I cannot convince freshly compiled current master 1ffc3fd
>>             to save an authentication database.
>>             Furthermore the Python access to QgsAuthManager via
>>             QgsAuthManager.instance() seems broken, too:
>>             "type object 'QgsAuthManager' has no attribute 'instance'"
>>
>>             Both already worked in a former version (compiled about 2 weeks ago)
>>
>>             any hints?
>>             shall I file tickets?
>>
>>             regards
>>             Bernhard
>>
>>
>>             __________ Information from ESET Mail Security, version of virus signature database 16343 (20171102) __________
>>
>>             The message was checked by ESET Mail Security.
>>             http://www.eset.com
>>
>>
>>             _______________________________________________
>>             QGIS-Developer mailing list
>>             QGIS-Developer at lists.osgeo.org
>>             <mailto:QGIS-Developer at lists.osgeo.org>
>>             List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>             <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
>>             Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>             <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
>>
>>
>>
>>             _______________________________________________
>>             QGIS-Developer mailing list
>>             QGIS-Developer at lists.osgeo.org
>>             <mailto:QGIS-Developer at lists.osgeo.org>
>>             List info:
>>             https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>             <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
>>             Unsubscribe:
>>             https://lists.osgeo.org/mailman/listinfo/qgis-developer
>>             <https://lists.osgeo.org/mailman/listinfo/qgis-developer>
>>
>>
>>
>>
>>         --
>>         Alessandro Pasotti
>>         w3:   www.itopen.it <http://www.itopen.it>
>>
>>
>>
>>
>>
>> --
>> Alessandro Pasotti
>> w3:   www.itopen.it <http://www.itopen.it>
>
>
>


__________ Information from ESET Mail Security, version of virus signature database 16344 (20171102) __________

The message was checked by ESET Mail Security.
http://www.eset.com