Is TRYTOND_DATABASE_NAMES required?

Hi,

In version 8.0, I’m experiencing different behavior when logging in since the last update (trytond v8.0.13).

Without either -d <db_name> or TRYTOND_DATABASE_NAMES as an environment variable, I can no longer connect to a database:

ERROR:tryton.common.common:Traceback (most recent call last):
  File "/.../.../tryton/tryton/gui/main.py", line 261, in do_activate
    common.get_credentials()
  File "/.../.../tryton/tryton/common/common.py", line 1096, in get_credentials
    Login()
  File "/.../.../tryton/tryton/common/common.py", line 1153, in __init__
    func(parameters)
  File "/.../.../tryton/tryton/rpc.py", line 130, in login
    result = connection.common.db.login(username, parameters, language)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/xt0ph/.pyenv/versions/3.12.12/lib/python3.12/xmlrpc/client.py", line 1122, in __call__
    return self.__send(self.__name, args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/.../.../tryton/tryton/jsonrpc.py", line 347, in __request
    raise Fault(*response['error'])
tryton.jsonrpc.Fault: 'res.user'

Fault: 'res.user'

Hence my question: Are the TRYTOND_DATABASE_NAMES environment variable or the -d option now required, or have I missed something?

Until the fix of issue15185 is released.

In the meantime, exporting TRYTOND_DATABASE_NAMES with the database name, or launching the client with -d, should get you past the login fault — that matches the behaviour you describe. If pinning a version is easier for your setup, staying on 8.0.12 until the fix lands is the other option. Either is a temporary workaround, not a permanent config change.