Bug 913705

Summary: [abrt] sear-0.6.4-0.6.g0b70ddb.fc17: Sear::Character::moveForward: Process /usr/bin/sear-bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Pat Kelly <pmkellly72>
Component: searAssignee: Bruno Wolff III <bruno>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: atorkhov, bruno
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:a06606feb630bae340591c9c8050e4d3cab9bb5b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 21:44:51 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: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: smolt_data
none
File: cgroup
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Pat Kelly 2013-02-21 20:42:46 UTC
Description of problem:
I just started the application and it crashed

Version-Release number of selected component:
sear-0.6.4-0.6.g0b70ddb.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        /usr/bin/sear-bin
crash_function: Sear::Character::moveForward
kernel:         3.7.3-101.fc17.i686.PAE

truncated backtrace:
:Thread no. 1 (3 frames)
: #0 Sear::Character::moveForward at Character.cpp:123
: #1 Sear::System::handleEvents at System.cpp:539
: #2 Sear::System::mainLoop at System.cpp:471

Comment 1 Pat Kelly 2013-02-21 20:42:49 UTC
Created attachment 700816 [details]
File: core_backtrace

Comment 2 Pat Kelly 2013-02-21 20:42:50 UTC
Created attachment 700817 [details]
File: environ

Comment 3 Pat Kelly 2013-02-21 20:42:52 UTC
Created attachment 700818 [details]
File: limits

Comment 4 Pat Kelly 2013-02-21 20:42:54 UTC
Created attachment 700819 [details]
File: backtrace

Comment 5 Pat Kelly 2013-02-21 20:42:56 UTC
Created attachment 700820 [details]
File: smolt_data

Comment 6 Pat Kelly 2013-02-21 20:42:58 UTC
Created attachment 700821 [details]
File: cgroup

Comment 7 Pat Kelly 2013-02-21 20:43:00 UTC
Created attachment 700822 [details]
File: executable

Comment 8 Pat Kelly 2013-02-21 20:43:02 UTC
Created attachment 700823 [details]
File: maps

Comment 9 Pat Kelly 2013-02-21 20:43:04 UTC
Created attachment 700824 [details]
File: dso_list

Comment 10 Pat Kelly 2013-02-21 20:43:06 UTC
Created attachment 700825 [details]
File: proc_pid_status

Comment 11 Pat Kelly 2013-02-21 20:43:08 UTC
Created attachment 700826 [details]
File: var_log_messages

Comment 12 Pat Kelly 2013-02-21 20:43:10 UTC
Created attachment 700827 [details]
File: open_fds

Comment 13 Bruno Wolff III 2013-02-21 21:36:18 UTC
Sear doesn't get much love upstream, but it could also be a video driver issue. I just tried it on f18 and got to the login menu. I don't have an f17 instance handy right now.

Comment 14 Fedora End Of Life 2013-07-03 21:01:00 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 15 Fedora End Of Life 2013-07-31 21:44:56 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.