Bug 895676

Summary: [abrt] foobillard-3.0a-18.fc17: proceed_dt: Process /usr/bin/foobillard was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: ZetaFunction <zetafunction11>
Component: foobillardAssignee: Gwyn Ciesla <gwync>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: gwync
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:59bcab7a8b918c2227a7008c4783efb2b6810998
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 02:56:39 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
File: smolt_data none

Description ZetaFunction 2013-01-15 18:49:23 UTC
Version-Release number of selected component:
foobillard-3.0a-18.fc17

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/foobillard
crash_function: proceed_dt
executable:     /usr/bin/foobillard
kernel:         3.6.11-5.fc17.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 proceed_dt at billmove.c:1352
 #1 Idle_timer at billard3d.c:1679
 #2 sys_main_loop at sys_stuff.c:705

Comment 1 ZetaFunction 2013-01-15 18:49:25 UTC
Created attachment 678974 [details]
File: backtrace

Comment 2 ZetaFunction 2013-01-15 18:49:27 UTC
Created attachment 678975 [details]
File: cgroup

Comment 3 ZetaFunction 2013-01-15 18:49:30 UTC
Created attachment 678976 [details]
File: core_backtrace

Comment 4 ZetaFunction 2013-01-15 18:49:32 UTC
Created attachment 678977 [details]
File: dso_list

Comment 5 ZetaFunction 2013-01-15 18:49:34 UTC
Created attachment 678978 [details]
File: environ

Comment 6 ZetaFunction 2013-01-15 18:49:36 UTC
Created attachment 678979 [details]
File: limits

Comment 7 ZetaFunction 2013-01-15 18:49:38 UTC
Created attachment 678980 [details]
File: maps

Comment 8 ZetaFunction 2013-01-15 18:49:40 UTC
Created attachment 678981 [details]
File: open_fds

Comment 9 ZetaFunction 2013-01-15 18:49:43 UTC
Created attachment 678982 [details]
File: proc_pid_status

Comment 10 ZetaFunction 2013-01-15 18:49:45 UTC
Created attachment 678983 [details]
File: var_log_messages

Comment 11 ZetaFunction 2013-01-15 18:49:47 UTC
Created attachment 678984 [details]
File: smolt_data

Comment 12 Fedora End Of Life 2013-07-03 23:51:56 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 Fedora End Of Life 2013-08-01 02:56:42 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.