Shotgun Desktop not opening

Hi all,

I’ve come across a new issue. Shotgun Desktop will not open the app UI at all, it goes through the Starting up Toolkit process but doesn’t open a window.

It’s running in the background but can’t open the app at all. I’ve tried uninstalling, removing all temp/cache files and reinstalling but no luck.

Thanks,
Amy

If this is a with in the past week or so that you have installed this the newer version Shotgun desktop was causing some issues in our pipe the Id look into installing 1.5.6 or 1.5.7 instead of 1.6.1

Hi guys,

I had a similar problem. With version 1.6.1, the DCCs don’t open and the Shotgun Desktop just doesn’t log anything, neither in the Shotgun Desktop console nor in the tk-desktop.log. I did this test on Windows 10, so I don’t know if this version is working on Linux or macOS.
For now, we just return to version 1.5.3 and that solved it.

Thanks

How did you revert the version?

Hi everyone,

We’d like to apologize, but something slipped through the cracks when we validated Shotgun Desktop 1.6.1 with older versions of the tk-desktop engine. We spent of lot of time making sure we reported incompatibilities when trying to load a version of tk-desktop that wasn’t Python 3 compatible in the Python 3 mode, but have been blindsided by Python 2 mode not being backwards compatible with older engines.

The gist of it is that because we are now packaging PySide2 instead of PySide, the PySide2 API doesn’t quite behave the same (QAction’s trigger signals being the biggest offender here) and it has introduced some bugs for users who have locked their site configuration’s tk-desktop engine to v2.4.12 and lower.

To avoid any future confusion with our users, we’ve released yesterday an update for Shotgun Desktop’s startup code that takes into account the tk-desktop version, the Shotgun Desktop version and reports any incompatibilities. It should auto download to your computer next time you launch Shotgun Desktop.

The pop-up will provide an explanation of the issue and suggest two ways to fix the problem.

image

Hopefully this will clear any confusion around this issue.

1 Like

To add to JF’s point, you can see all the Toolkit component version dependencies for v1.6.1 of Desktop in the Desktop Release Notes.

And @Ricardo_Musch, to answer your question, you can download any old versions of Desktop from the above link if you need to revert.

1 Like