I'm using jdeb to generate my .deb installer for debian based distros. The application is installed with no error, but when I try running service myapp start
it fails with the below's exception (The application keeps running but the FX scene never gets displayed):
2016-12-30 11:19:51,468 [main] INFO o.s.c.s.DefaultLifecycleProcessor - Starting beans in phase 0
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:58)
Caused by: java.lang.UnsupportedOperationException: Unable to open DISPLAY
at com.sun.glass.ui.gtk.GtkApplication.<init>(GtkApplication.java:68)
at com.sun.glass.ui.gtk.GtkPlatformFactory.createApplication(GtkPlatformFactory.java:41)
at com.sun.glass.ui.Application.run(Application.java:146)
at com.sun.javafx.tk.quantum.QuantumToolkit.startup(QuantumToolkit.java:257)
at com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:211)
at com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:675)
at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:695)
at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$155(LauncherImpl.java:182)
at java.lang.Thread.run(Thread.java:745)
Meanwhile if I simply run sudo /etc/init.d/myapp start
it runs with no error and my first FX scene is displayed.
Bellow is my maven configuration for jdeb:
<plugin>
<artifactId>jdeb</artifactId>
<groupId>org.vafer</groupId>
<version>1.5</version>
<executions>
<execution>
<id>appassembler</id>
<phase>package</phase>
<goals>
<goal>jdeb</goal>
</goals>
<configuration>
<deb>${project.build.directory}/${project.build.finalName}.deb</deb>
<snapshotExpand>false</snapshotExpand>
<!-- expand "SNAPSHOT" to what is in the "USER" env variable -->
<snapshotEnv>USER</snapshotEnv>
<verbose>true</verbose>
<controlDir>${basedir}/src/deb/control</controlDir>
<dataSet>
<data>
<src>${project.build.directory}/${project.build.finalName}-uber.jar</src>
<type>file</type>
<mapper>
<type>perm</type>
<prefix>/opt/stone/${project.build.finalName}</prefix>
<filemode>755</filemode>
<user>root</user>
<group>root</group>
</mapper>
</data>
<data>
<src>src/deb/upstart/${project.build.finalName}.conf</src>
<type>file</type>
<mapper>
<type>perm</type>
<prefix>/opt/stone/${project.build.finalName}</prefix>
<filemode>755</filemode>
<user>root</user>
<group>root</group>
</mapper>
</data>
</dataSet>
</configuration>
</execution>
</executions>
</plugin>
And here's my post installation script:
#!/bin/bash
echo Creating symblink...
sudo ln -s /opt/stone/acs/acs-uber.jar /etc/init.d/acs
echo Creating service...
sudo update-rc.d acs start 98 5 .
echo Starting service...
sudo service acs restart
Quoting an answer from elsewhere that worked for me with javafx as root on Ubuntu ... Maybe this can help someone else. I had the same question as you but for a normal user. Let's say I want to start firefox using the user account foo. I'm logged in as bar:
[bar@localhost ~]$ sudo -u foo -H firefox
Sadly that command failed with the same error as in the question (i.e. no protocol specified & cannot open display)
My solution was to simply add the user foo to the list of authorised access to the X server.
xhost si:localuser:foo
And that was it, I was then able to launch Firefox (and other X application) using sudo and the user foo.