Invalid font prefix "ftrack" after installing Connect 2.0.0rc6

[John Kalaigian]

Greetings,

I encountered the following error after installing Connect 2.0.0rc6:

  File "C:\Python\Lib\site-packages\cx_Freeze\initscripts\__startup__.py", line 113, in run
  File "C:\Python\Lib\site-packages\cx_Freeze\initscripts\Console.py", line 15, in run
  File "source\ftrack_connect_package\__main__.py", line 194, in <module>
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0rc6-py3.7.egg\ftrack_connect\__main__.py", line 139, in main
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0rc6-py3.7.egg\ftrack_connect\ui\application.py", line 367, in __init__
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0rc6-py3.7.egg\ftrack_connect\ui\application.py", line 503, in login
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0rc6-py3.7.egg\ftrack_connect\ui\application.py", line 647, in loginWithCredentials
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0rc6-py3.7.egg\ftrack_connect\ui\widget\configure_scenario.py", line 42, in __init__
  File "C:\Python\lib\site-packages\qtawesome\__init__.py", line 188, in icon
  File "C:\Python\lib\site-packages\qtawesome\iconic_font.py", line 347, in icon
  File "C:\Python\lib\site-packages\qtawesome\iconic_font.py", line 397, in _parse_options
  File "C:\Python\lib\site-packages\qtawesome\iconic_font.py", line 431, in _get_prefix_chars

Whereas my python path is set to: C:\Python310, I did not encounter this issue with 2.0.0rc5.

Best,

John

[Patrick Boucher ftrack]

Hi John,

Can you try with the release version of Connect that can be found here?

Cheers,
Patrick

[John Kalaigian]

Hello Patrick,

Thanks for following up. I did uninstall all prior RC installations, as well as removed any files in my AppData\Local\ftrack directories, before installing that same version you provided. I was able to launch connect 2.0.0 without any issues. I was chatting with Lorenzo about this yesterday on slack, especially after I was successful of running connect 2.0.0 following the install. However, as of today following a restart to my system I'm encountering the same error once again:

  File "C:\Python\Lib\site-packages\cx_Freeze\initscripts\__startup__.py", line 113, in run
  File "C:\Python\Lib\site-packages\cx_Freeze\initscripts\Console.py", line 15, in run
  File "source\ftrack_connect_package\__main__.py", line 194, in <module>
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0-py3.7.egg\ftrack_connect\__main__.py", line 139, in main
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0-py3.7.egg\ftrack_connect\ui\application.py", line 367, in __init__
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0-py3.7.egg\ftrack_connect\ui\application.py", line 503, in login
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0-py3.7.egg\ftrack_connect\ui\application.py", line 647, in loginWithCredentials
  File "C:\Python\lib\site-packages\ftrack_connect-2.0.0-py3.7.egg\ftrack_connect\ui\widget\configure_scenario.py", line 42, in __init__
  File "C:\Python\lib\site-packages\qtawesome\__init__.py", line 188, in icon
  File "C:\Python\lib\site-packages\qtawesome\iconic_font.py", line 347, in icon
  File "C:\Python\lib\site-packages\qtawesome\iconic_font.py", line 397, in _parse_options
  File "C:\Python\lib\site-packages\qtawesome\iconic_font.py", line 431, in _get_prefix_chars

What is strange is that I do not have my python installed in C:\Python, nor do I have the packages listed in this stack trace.

[Patrick Boucher ftrack]

Thanks for the update. I'll have a chat with Lorenzo and one of us will get back to you.

[Lorenzo Angeli]

Hi @John Kalaigian I'm now looking into this issue.
it seems to be triggered due to a miss initialization of the icons during the fist storage scenario startup.

it'll be fixed in an upcoming patch version.
thanks for reporting it.

[Mathias Aerts]

Hi @Lorenzo Angeli,

I have ran into the same issue (exact same error log).
Interestingly, as a new user, ftrack connect launched correctly the first time around, it wasn't until I connected to our url and restarted the program that the issue popped up.
Has there been a patch for this, or should I try to find an older version of ftrack connect in the meantime?

Thank you for your time,
With kind regards