Bug 569566

Summary: [abrt] crash in bash-4.0.35-2.fc12: Process /bin/bash was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: cmwiest
Component: bashAssignee: Roman Rakus <rrakus>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: ilyes.gouta, rrakus, tsmetana, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:a919685d0a6ddf26c342c458ac54378e8bfb34be
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-20 11:47:57 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

Description cmwiest 2010-03-01 18:02:30 UTC 
abrt 1.0.7 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: bash
comment: On opening a new terminal the program crashed and failed to open or start.  Multiple instances
component: bash
executable: /bin/bash
kernel: 2.6.31.12-174.2.22.fc12.i686
package: bash-4.0.35-2.fc12
rating: 4
reason: Process /bin/bash was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.Open a terminal
2.
3.
Comment 1 cmwiest 2010-03-01 18:02:32 UTC 
Created attachment 397147 [details]
File: backtrace
Comment 2 Roman Rakus 2010-03-05 15:28:22 UTC 
I have some other abrt reported bugs against bash. Do you have any 100%
reproducer? Do you see this issue (only) after you hibernate your system?
Comment 3 cmwiest 2010-03-06 00:32:51 UTC 
Yeah it only seems to happen after I have hibernated the system, but it doesn't do it every time.  If I reboot the system it solves the problem.
Comment 4 Roman Rakus 2010-05-20 11:47:57 UTC 

*** This bug has been marked as a duplicate of bug 551570 ***