Bug 652878 - [abrt] bash-4.0.38-1.fc12: raise: Process /bin/bash was killed by signal 6 (SIGABRT)
Summary: [abrt] bash-4.0.38-1.fc12: raise: Process /bin/bash was killed by signal 6 (S...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: bash
Version: 12
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Roman Rakus
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:dc1bfe9fab16a4322152e8f92bf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-13 07:05 UTC by Jim
Modified: 2014-01-13 00:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-15 15:50:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (33.64 KB, text/plain)
2010-11-13 07:05 UTC, Jim
no flags Details

Description Jim 2010-11-13 07:05:15 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: -bash
component: bash
crash_function: raise
executable: /bin/bash
kernel: 2.6.32.23-170.fc12.i686.PAE
package: bash-4.0.38-1.fc12
rating: 4
reason: Process /bin/bash was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
time: 1289629781
uid: 500

Comment 1 Jim 2010-11-13 07:05:18 UTC
Created attachment 460206 [details]
File: backtrace

Comment 2 Roman Rakus 2010-11-15 13:19:39 UTC
Can you please provide some steps to reproduce? Did you use hibernation?

Comment 3 Jim 2010-11-15 15:43:50 UTC
Unfortunately, I don't have a good way to reproduce the problem. Yes, as I recall, I was coming out of a hibernation, but I'm not 100% sure as I'm struggling to remember exactly how it happened. I do remember not placing any repro steps in there because I wasn't doing anything at the time. It just happened. However, I don't remember exactly what the machine was doing (if it was hibernating or not). Apologies.

Comment 4 Roman Rakus 2010-11-15 15:50:44 UTC
ok, I can't reproduce it, so closing as worksforme. Feel free to reopen when you will have some reproducer.


Note You need to log in before you can comment on or make changes to this bug.