Ignition Version: 8.3.8
Designer Launcher Version: 1.3.8
Edge Panel Trial
Environment: Debian 13 (Xfce) in VMware Workstation
Perspective module is installed and active in both cases.
When opening the project in the Designer from Windows 11, the Perspective node appears normally.
When opening the same project from Debian using the Designer Launcher, the Project Browser does not show the Perspective node.
Windows:
Linux:
The perspective module may be failing to load in the designer on debian, are there any errors in the designer console?
Usual suspect is AV/FW but this has helped people in the past
Thanks for the suggestion. I checked the Designer console and found JxBrowser initialization errors.
The same error appears while loading both the Vision and Perspective modules:
"[Designer-Startup] ERROR designer.JXBrowserUtil -- Failed to start Browser Engine with options
com.teamdev.jxbrowser.engine.EngineOptions:
autoplayEnabled: false
chromiumDir: /root/.ignition/cache/resources/jxbrowser/8.16.0
chromiumSwitches:
diskCacheSize:
fileAccessFromFilesAllowed: false
isGpuDisabled: false
isIncognitoEnabled:true
language:en-us
passwordStore:
remoteDebugginPort: 9222
renderingMode: OFF_SCREEN
isSandboxDisabled: false
secureOriginWhitelist:
isTouchMenuEnabled: false
userAgent:
userDataDir:/tmp/JxBrowser-UserData-25cdcaf9-2124-451c-8c4c-b940252e5d8e
webSecurityDisabled: false
.
com.teamdev.jxbrowser.engine.ChromiumProcessStartupFailureException: Process exit code: 1"
I also performed additional testing.
When running the Designer as root on Debian, the Perspective node is missing from the Project Browser, as shown in the screenshot from my original post.
But when running the Designer as a normal user on Debian, the Perspective node appears normally and works as expected.
At this point I'm not sure whether the JxBrowser error is directly related, since the same error occurs during Vision startup and Vision still loads correctly.
The only reproducible difference I found is that the issue occurs when running the Designer as root, while running it as a normal user works correctly.
Since running the Designer as a normal user resolves the issue for me, I will continue using it that way for now.
We use an "embedded" web browser, called JxBrowser, which is ultimately Chromium. Chromium doesn't want to be run as root, for the sake of security, and actively prevents you from launching as root unless you jump through some hoops. Running the designer process as not-root is definitely recommended practice, for this and other reasons.
