Version-Release number of selected component: ember-0.7.0-10.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/ember.bin --home /home/domini/.ember crash_function: luaH_getstr executable: /usr/bin/ember.bin kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 luaH_getstr at ltable.c:467 #1 luaH_get at ltable.c:483 #2 lua_rawget at lapi.c:644 #3 tolua_open at src/lib/tolua_map.c:289 #4 tolua_Lua_open at Lua.cxx:518 #5 Ember::Application::initializeServices at ../../src/main/Application.cpp:385
Created attachment 840987 [details] File: backtrace
Created attachment 840988 [details] File: cgroup
Created attachment 840989 [details] File: core_backtrace
Created attachment 840990 [details] File: dso_list
Created attachment 840991 [details] File: environ
Created attachment 840992 [details] File: limits
Created attachment 840993 [details] File: maps
Created attachment 840994 [details] File: open_fds
Created attachment 840995 [details] File: proc_pid_status
Created attachment 840996 [details] File: var_log_messages
Created attachment 840997 [details] File: exploitable
Another user experienced a similar problem: started Ember, it immediately crashed. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/ember.bin --home /home/brian/.ember crash_function: luaH_getstr executable: /usr/bin/ember.bin kernel: 3.11.10-301.fc20.x86_64 package: ember-0.7.0-10.fc20 reason: ember.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I installed it via Apper and clicked the Ember entry in the popup dialogue after installation. After a few moments the program crashed. This program crashed as well when launching via other means. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/ember.bin --home /home/apapsch/.ember crash_function: luaH_getstr executable: /usr/bin/ember.bin kernel: 3.15.10-200.fc20.x86_64 package: ember-0.7.0-10.fc20 reason: ember.bin killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.