There’s now an alpha version of the editor for 64 bit Linux ready for testing. We’ve tested it on Ubuntu 14.04 (LTS), Ubuntu 15.10 and Debian 8 and everything seems to be working as intended. As Ragnar mentioned this is brand new platform support and we’ve already seen issues with differences in the environment during our own testing. Therefore we would like to invite anyone that is interested to participate in an alpha test too weed out any additional issues before the intended release date at 2016-04-04.
An important thing to note if you decide to participate in the alpha test. Defold is released on different channels and the channel for this alpha test will be discontinued at which point editors downloaded from there will no longer receive updates. In order to jump to the stable version at 2016-04-04 you would need to download the stable version from the regular download link. Before you do this it is important that you synchronize (File > Synchronize) your projects so that you bring the stuff you’ve made while alpha testing to the stable version.
The alpha version with 64 bit Linux can be downloaded from the link below. If you encounter any problems please post them in this thread and ping me (@jakob.pogulis). We will do our best to address the issues before the intended release date.
Update 2016-03-29
There’s now a new alpha version ready for testing. We have addressed the issues with a missing configuration to use Mozilla for web content and the “Could not open window” error. If you experience any additional problems please continue to report them in this thread (ping @jakob.pogulis!) and I will get back to you as soon as possible.
You should start the editor by executing Defold-linux.sh.
Most of the time, that’s because Defold tries to launch a web server listening on port 8080. If it’s already occupied, you’ll have this error. To check if you already have something listening, type netstat -vltpn | grep 8080. you’ll get the offending process name, so you can change its port, as I haven’t found any option to change Defold’s web server listening port.
Message from @Erik_Bystrom (and slighty modified by me )
If you’re having problems starting the alpha build of Defold on Ubuntu 64bit, add this line to Defold.ini file, and just add the following at the end of the file, on a new line:
The reason for this problem is that by default no alternative webkit is installed, and thus we default to mozilla. But if an alternative webkit such as libwebkitgtk-1.0-0 is installed that will be selected instead and there will be a crash in the JVM (… soup …).
The solution to the problem is to add -Dorg.eclipse.swt.browser.DefaultType=mozilla to Defold.ini just as @Erik_Bystrom and @lstep pointed out.
For Fedora 23, No branches can be created. I was assuming this is a file creation permission problem, however I added those permissions, and still no dice. There is a fix for Debian Distro’s from Oct '15, no clue if that fix got merged. I’m not even sure it would work on Fedora.
Update: It creates this file structure Defold/branches/15194/7894, however no files are copied over.
@Fallendown, Do you have any error messages in the GUI console (Error Log or Problems tab)? When I had this problem (but on Ubuntu), the message was explicitly written in it (something like missing libssl.0.9.8).
com.dynamo.cr.client.RepositoryException: Unable to create branch
at com.dynamo.cr.client.LocalProjectClient.createBranch(LocalProjectClient.java:101)
at com.dynamo.cr.editor.wizards.ConnectionWizardBranchPagePresenter$CreateBranchRunnable.run(ConnectionWizardBranchPagePresenter.java:70)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: com.dynamo.server.dgit.GitException: /home/webdev/Defold/plugins/com.dynamo.cr.dgit_1.0.0.201603240816/git/x86_64-linux//bin/git: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
at com.dynamo.server.dgit.CGit.checkResult(CGit.java:105)
at com.dynamo.server.dgit.CGit.checkResult(CGit.java:100)
at com.dynamo.server.dgit.CGit.cloneRepo(CGit.java:149)
at com.dynamo.cr.branchrepo.BranchRepository.createBranch(BranchRepository.java:120)
at com.dynamo.cr.client.LocalProjectClient.createBranch(LocalProjectClient.java:99)
... 2 more
For me libcrypto is in the openssl_x86_x64 dependency which is installed along with the library and the dev versions…the only thing I can think of is maybe I need to create a symlink between Defold and libcrypto?
You should have a /lib64/libcrypto.so.1.0.0. Not sure how to get it. Maybe create a link from /lib64/libcrypto.so.10?
Try ln -s /lib64/libcrypto.so.10 /lib64/libcrypto.so.1.0.0 and then ldconfig.
I can get it from installing spotify however I need to remove the symlink we created, not quite sure how to do that on linux without messing something up. Sorry, switched to Linux to build meteor.js web applications…
build and launch returns this error:
INFO:ENGINE: Defold Engine 1.2.76 (215b8a2)
FATAL:ENGINE: Could not open window (-2).
I noticed that if I “Bundle >> Linux Application”, and go in that directory, I’ll get two executables, one for 32 bits (foobar.x86) and one for 64 bits (foobar.x86_64). The 32 bits app works fine (window displays with content), but the 64 bits begins showing some window but for less than 1ms (can’t see anything) and then returns to shell, without any error message anywhere.
Maybe it’s related to the fact that it doesn’t work in the GUI also as I guess it tries to run the 64 bits version.
I couldn’t find anything for now about why the 64 bit app doesn’t start (it’s the empty project with just the Defold logo).
@Todor_Imreorov@lstep
I’ve received an internal report about this as well. In that case the 64bit version of the engine works when there’s no multi architectural support, but it doesn’t when multi arch is enabled. If this is the case the 32bit version should work for you just as @lstep describes. I haven’t been able to reproduce this on my own machines yet, so I would really appriciate it if you could collect some data for me to look at.
Could you please try to bundle for Linux and then run the following commands
file .x86
file .x86_64
ldd .x86
ldd .x86_64
gdb .x86_64 (then write “run” in the prompt)
)
however I need to remove the symlink we created, not quite sure how to do that on linux without messing something up. Sorry, switched to Linux to build meteor.js web applications…