Shotgun Desktop not launching - CentOS 7

Flow Production Tracking
1

Hi,

I installed SG Desktop using the shotgun_desktop-current-1.fc20.x86_64.rpm on a CentOS 7 machine (kernel version 3.10.0-1127.13.1.el7.x86_64).

Presently when I launch SG Desktop, nothing happens. The process doesn’t spawn nor do I get errors in the terminal as well. It was working fine previously on the same machine so I am pretty sure it’s a machine issue. I wanted to check how one would go about debugging the issue?

Thank you.

3 Likes
2

Update: sudo /opt/Shotgun/Shotgun works perfectly.

2 Likes
3

cat ~/.shotgun/logs/tk-desktop.log showed that for some reason my local python virtualenv was getting appended to the launch python path before /opt/Shotgun/Python/lib/python2.7/site-packages

I wasn’t able to resolve the issue by setting PYTHONPATH so I temporarily renamed my local env, this fixed the problem.

Relevant log lines:

Executable: /opt/Shotgun/Python/bin/python
Version: 2.7.14
sys.path:
- /opt/Shotgun/Resources/Python/tk-framework-desktopstartup/python
- /opt/Shotgun/Resources/Python
- /opt/Shotgun/Python/lib/python27.zip
- /opt/Shotgun/Python/lib/python2.7
- /opt/Shotgun/Python/lib/python2.7/plat-linux2
- /opt/Shotgun/Python/lib/python2.7/lib-tk
- /opt/Shotgun/Python/lib/python2.7/lib-old
- /opt/Shotgun/Python/lib/python2.7/lib-dynload
- **My Python env**/site-packages
- /opt/Shotgun/Python/lib/python2.7/site-packages

I can resolve this conflict at my end, leaving this here for future reference, perhaps something to check at runtime for future binaries?

7 Likes