Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

startup/gui/project : Don't import GafferUI modules in headless mode #3237

Merged
merged 1 commit into from
Jun 28, 2019

Conversation

themissingcow
Copy link
Contributor

@themissingcow themissingcow commented Jun 28, 2019

This startup script is shared with the dispatch app. The dispatch app runs without a gui by default (unless --gui is specified). If dispatch is run on a machine with no X display, the imports of GafferUI cause a QXcbConnection Could not connect to display error and a subsequent abort.

We now only initialize bookmarks if the application sourcing the startup file has already loaded the UI modules.

This startup script is shared with the `dispatch` app. The dispatch app
runs without a gui by default (unless --gui is specified). If dispatch
is run on a machine with no X display, the imports of `GafferUI` cause
a `QXcbConnection Could not connect to display` error and a subsequent
abort.

We now only initialize bookmarks if the application sourcing the startup
file has already loaded the UI modules.
@themissingcow themissingcow self-assigned this Jun 28, 2019
@johnhaddon johnhaddon merged commit 12c763f into GafferHQ:master Jun 28, 2019
@themissingcow themissingcow deleted the dispatchNoGui branch July 5, 2019 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants