6.4 GTK Crash after GPU change

(I know it’s not a supported version, that’s why I’m asking here and not filling a issue)

After replacing a GPU, the Tryton can no longer be opened, it crashes with:

  File "C:/msys64/home/ced/tryton-6.4-64/tryton/gui/main.py", line 258, in do_command_line
  File "C:/msys64/home/ced/tryton-6.4-64/tryton/gui/main.py", line 255, in do_activate
  File "C:/msys64/home/ced/tryton-6.4-64/tryton/gui/main.py", line 533, in get_preferences
  File "C:/msys64/home/ced/tryton-6.4-64/tryton/gui/main.py", line 716, in sig_win_menu
  File "C:/msys64/home/ced/tryton-6.4-64/tryton/gui/window/view_form/__init__.py", line 3, in <module>
  File "C:/msys64/home/ced/tryton-6.4-64/tryton/gui/window/view_form/screen/__init__.py", line 3, in <module>
  File "C:/msys64/home/ced/tryton-6.4-64/tryton/gui/window/view_form/screen/screen.py", line 21, in <module>
  File "C:/msys64/home/ced/tryton-6.4-64/tryton/common/domain_parser.py", line 14, in <module>
  File "C:/msys64/home/ced/tryton-6.4-64/tryton/common/datetime_.py", line 6, in <module>
  File "C:/msys64/mingw64/lib/python3.9/site-packages/dateutil/parser/__init__.py", line 2, in <module>
  File "C:/msys64/mingw64/lib/python3.9/site-packages/dateutil/parser/_parser.py", line 50, in <module>
  File "C:/msys64/mingw64/lib/python3.9/site-packages/dateutil/tz/__init__.py", line 2, in <module>
  File "C:/msys64/mingw64/lib/python3.9/site-packages/dateutil/tz/tz.py", line 29, in <module>
  File "C:/msys64/mingw64/lib/python3.9/site-packages/dateutil/tz/win.py", line 17, in <module>
  File "C:/msys64/mingw64/lib/python3.9/ctypes/__init__.py", line 460, in <module>
  File "C:/msys64/mingw64/lib/python3.9/ctypes/__init__.py", line 374, in __init__

OSError: [WinError 87] El parámetro no es correcto

I tried to remove the .cache on AppData and to reinstall Tryton. Any other suggestions that can be causing this?

The same gtk version works ok on other computers.

Did you get any Tryton GTK-client to work? E.g. the official one, or a client from a former or later version.

The problem was a missing update on Windows updates. (KB2533623)

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.