Same behaviour here. So let's hope that Mara will succeed building a new version for SF. At least the Android Version works on my Xperia. On my J1 it always crashed.
[D] unknown:0 - QML debugging is enabled. Only use this in a safe environment. -------------------------------------------------------------------------------------------------------------------- [ This is Stellarium for Sailfish 0.9 - http://thelarge.org/stellarium-sailfish ] [ SF and N9 port Copyright(C) 2012-2014 Marko Srebre; Stellarium 0.12.4 Copyright (C) 2000-2013 Fabien Chereau et al ] -------------------------------------------------------------------------------------------------------------------- Writing log file to: "/home/nemo/.stellarium-sf/log.txt" File search paths: 0 . "/home/nemo/.stellarium-sf" 1 . "/usr/share/stellarium-sf" Attempting to use an existing older config file. Config file is: "/home/nemo/.stellarium-sf/config.ini" Using Wayland-EGL Defaulting to webview scaling factor of 1.0 No default allowed orientations defined. Check your device configuration! QOpenGLShaderProgram::uniformLocation( tex ): shader program is not linked GL vendor is "Qualcomm" GL renderer is "Adreno (TM) 405" FBO Supported true QGLShader::compile(Vertex): INTERNAL ERROR: no main() function! ERROR: 0 compilation errors. No code generated. Failed to add default projection vertex shader: "" QGLShader::compile(Vertex): INTERNAL ERROR: Call to undefined function! ERROR: 0 compilation errors. No code generated. Failed to compile vertex shader of builtin shader " plainShader " : "" StelQGL2Renderer::init failed to load plain shader ASSERT failure in void StelMainSkyItem::paint(): "Failed to initialize renderer", file ../stel-sf-0.9.1/src/StelMainSkyItem.cpp, line 187 INTERNAL ERROR: no main() function! ERROR: 0 compilation errors. No code generated. INTERNAL ERROR: Call to undefined function! ERROR: 0 compilation errors. No code generated. bash: line 1: 18238 Aborted DISPLAY=':0.0' QT_LOGGING_TO_CONSOLE='1' QT_NO_JOURNALD_LOG='1' /usr/bin/stellarium-sf Application finished with exit code 134.