Bug 995624

Summary: [abrt] springlobby-0.169-3.fc18: exit: Process /usr/bin/springlobby was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dimitar H Dimitrov <dimityr_7>
Component: springlobbyAssignee: Gilboa Davara <gilboad>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: gilboad
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d290f3955a8e090f9c35636ad89204ca0e63acfc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-22 16:08:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Dimitar H Dimitrov 2013-08-09 21:22:31 UTC
Description of problem:
1.Start the game
2.Click on single player
3.Choose a map
4.Set n bots to play also
5.Click on start
Result: The game was not started
6.Close the window
Result: Game is crashed.

Version-Release number of selected component:
springlobby-0.169-3.fc18

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/bin/springlobby
crash_function: exit
executable:     /usr/bin/springlobby
kernel:         3.10.4-100.fc18.x86_64
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (3 frames)
 #22 exit at exit.c:99
 #23 __libc_start_main at libc-start.c:257
 #24 _start

Comment 1 Dimitar H Dimitrov 2013-08-09 21:22:34 UTC
Created attachment 784994 [details]
File: backtrace

Comment 2 Dimitar H Dimitrov 2013-08-09 21:22:38 UTC
Created attachment 784995 [details]
File: cgroup

Comment 3 Dimitar H Dimitrov 2013-08-09 21:22:41 UTC
Created attachment 784996 [details]
File: core_backtrace

Comment 4 Dimitar H Dimitrov 2013-08-09 21:22:45 UTC
Created attachment 784997 [details]
File: dso_list

Comment 5 Dimitar H Dimitrov 2013-08-09 21:22:48 UTC
Created attachment 784998 [details]
File: environ

Comment 6 Dimitar H Dimitrov 2013-08-09 21:22:52 UTC
Created attachment 784999 [details]
File: exploitable

Comment 7 Dimitar H Dimitrov 2013-08-09 21:22:55 UTC
Created attachment 785000 [details]
File: limits

Comment 8 Dimitar H Dimitrov 2013-08-09 21:22:58 UTC
Created attachment 785001 [details]
File: maps

Comment 9 Dimitar H Dimitrov 2013-08-09 21:23:02 UTC
Created attachment 785002 [details]
File: open_fds

Comment 10 Dimitar H Dimitrov 2013-08-09 21:23:05 UTC
Created attachment 785003 [details]
File: proc_pid_status

Comment 11 Dimitar H Dimitrov 2013-08-09 21:23:08 UTC
Created attachment 785004 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2013-12-21 14:27:22 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.

Comment 13 Dimitar H Dimitrov 2013-12-22 00:45:12 UTC
Currently I am using fedora 20, but springlobby can not be installed because of dependency issue on one of the packages (spring-installer).

Comment 14 Gilboa Davara 2013-12-22 15:01:18 UTC
Please open a separate bug report.
I'll try and fix it ASAP.

- Gilboa

Comment 15 Gilboa Davara 2013-12-22 15:07:28 UTC
I just checked, springlobby no longer requires spring-installer.
Can you try rpm -e springlobby; yum --enablerepo=updates-testing install springlobby and report the output.
If it doesn't work, please post the output of the second command in a separate bug report.

- Gilboa

Comment 16 Dimitar H Dimitrov 2013-12-22 16:08:45 UTC
I'll close this issue. New issue was opened about dependency of spring-installer.