Version-Release number of selected component: xonotic-0.7.0-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: xonotic-sdl crash_function: dGetConfiguration executable: /usr/bin/xonotic-sdl kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 dGetConfiguration #1 dCheckConfiguration at ode.cpp:2251 #2 World_Physics_Init at world.c:1534 #3 World_Init at world.c:38 #4 Host_Init at host.c:1255 #5 Host_Main at host.c:673
Created attachment 840818 [details] File: backtrace
Created attachment 840819 [details] File: cgroup
Created attachment 840820 [details] File: core_backtrace
Created attachment 840821 [details] File: dso_list
Created attachment 840822 [details] File: environ
Created attachment 840823 [details] File: limits
Created attachment 840824 [details] File: maps
Created attachment 840825 [details] File: open_fds
Created attachment 840826 [details] File: proc_pid_status
Created attachment 840827 [details] File: var_log_messages
Another user experienced a similar problem: When i try to lauch xonotic-glx, xonotic-sdl or xonotic-sdl-wrapper i get the following: Game is Xonotic using base gamedir data Xonotic Linux 11:00:05 Aug 4 2013 - release Current nice level is below the soft limit - cannot use niceness Skeletal animation uses SSE code path Segmentation fault (core dumped) reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: xonotic-glx crash_function: dGetConfiguration executable: /usr/bin/xonotic-glx kernel: 3.14.7-200.fc20.x86_64 package: xonotic-0.7.0-2.fc20 reason: xonotic-glx killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Just trying to launch xonotic-sdl, recieved the following error then crashed. Game is Xonotic using base gamedir data Xonotic Linux 11:00:05 Aug 4 2013 - release Current nice level is below the soft limit - cannot use niceness Skeletal animation uses SSE code path Segmentation fault (core dumped) reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: xonotic-sdl crash_function: dGetConfiguration executable: /usr/bin/xonotic-sdl kernel: 3.14.7-200.fc20.x86_64 package: xonotic-0.7.0-2.fc20 reason: xonotic-sdl killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Opening any xonotic binary. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: xonotic-sdl crash_function: dGetConfiguration executable: /usr/bin/xonotic-sdl kernel: 3.16.2-200.fc20.x86_64 package: xonotic-0.7.0-2.fc20 reason: xonotic-sdl 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.