Bug 610040

Summary: [abrt] crash in bash-4.0.35-3.fc12: __wcscoll_l: Process /bin/bash was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jayrome <jayrome>
Component: bashAssignee: Roman Rakus <rrakus>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: rrakus, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:506641c5fd19e2eab0da087b9a957629f5cb5ba4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-01 15:22:35 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 Jayrome 2010-07-01 13:02:35 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /bin/bash /etc/rc0.d/K30sendmail stop
component: bash
crash_function: __wcscoll_l
executable: /bin/bash
global_uuid: 506641c5fd19e2eab0da087b9a957629f5cb5ba4
kernel: 2.6.32.14-127.fc12.i686
package: bash-4.0.35-3.fc12
rating: 4
reason: Process /bin/bash was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Jayrome 2010-07-01 13:02:39 UTC 
Created attachment 428399 [details]
File: backtrace
Comment 2 Roman Rakus 2010-07-01 13:41:47 UTC 
Did you use hibernation before?
Comment 3 Jayrome 2010-07-01 14:03:04 UTC 
I think yes, and I had a major failure when I turned it back on.
Comment 4 Roman Rakus 2010-07-01 15:22:35 UTC 

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