Bug 551570

Summary: [abrt] crash detected in bash-4.0.35-2.fc12
Product: [Fedora] Fedora Reporter: Kaare Fiedler Christiansen <bugzilla.redhat>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: ameya.gore, anton, bugsvillecentral, cmwiest, dougsland, gansalmon, icj, itamar, jonathan, jones.peter.busi, kernel-maint, kujaz2, manoj.bgm, matzilla, me, mschmidt, rrakus, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:65fdab3f47225cd9944d3ee2738f85ed3f193e24
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-06 19:33:40 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
lspci output for inspiron 530
none
dmesg output for inspiron 530
none
logs.7z
none
gzipped tar of files requested in commet #15 none

Description Kaare Fiedler Christiansen 2009-12-31 11:10:25 UTC
abrt 1.0.0 detected a crash.

How to reproduce
-----
Not reproducible all the time, but has happened twice in approximately a month

1. Wait for the computer to hibernate while on battery power
2. Turn on the computer
3. Bash will coredump every time it is started

Comment: Happens every time bash is started, no matter if it's by starting a terminal, logging in at teh text prompt, or starting a script using bash as interpreter
Attached file: backtrace
cmdline: /bin/sh /usr/bin/abrt-gui
component: bash
executable: /bin/bash
kernel: 2.6.31.9-174.fc12.i686
package: bash-4.0.35-2.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 Kaare Fiedler Christiansen 2009-12-31 11:10:27 UTC
Created attachment 381074 [details]
File: backtrace

Comment 2 Roman Rakus 2010-03-05 15:21:29 UTC
Look like the problem appears only on F12 after hibernation. I don't have right now F12 on my notebook, but I'm pretty sure, the problem stands somewhere in hibernation (not directly in bash). Let's try to reassign bug to the kernel.

Comment 3 Roman Rakus 2010-03-05 15:34:04 UTC
*** Bug 547083 has been marked as a duplicate of this bug. ***

Comment 4 Roman Rakus 2010-03-05 15:34:49 UTC
*** Bug 543762 has been marked as a duplicate of this bug. ***

Comment 5 Roman Rakus 2010-04-06 16:03:30 UTC
*** Bug 578680 has been marked as a duplicate of this bug. ***

Comment 6 Michal Schmidt 2010-04-07 10:01:24 UTC
Since other people are using hibernation without problems, the bug may be hardware-dependent.

Could people seeing this (and the duplicates) bug please attach the output of "lspci -vvnn" and "dmesg"? Thanks.

Comment 7 Iván Jiménez 2010-04-08 01:08:18 UTC
Created attachment 405143 [details]
lspci output for inspiron 530

Comment 8 Iván Jiménez 2010-04-08 01:09:33 UTC
Created attachment 405144 [details]
dmesg output for inspiron 530

Comment 9 Roman Rakus 2010-05-20 11:42:13 UTC
*** Bug 590332 has been marked as a duplicate of this bug. ***

Comment 10 Roman Rakus 2010-05-20 11:47:57 UTC
*** Bug 569566 has been marked as a duplicate of this bug. ***

Comment 11 Matthieu Araman 2010-06-14 21:14:44 UTC
http://www.smolts.org/client/show/pub_7441b11b-0284-4d52-8467-3f98e3083ac5
Acer Aspire One , 1G RAM, model with Broadcom wifi 5312

Comment 12 Matthieu Araman 2010-06-14 21:15:21 UTC
oops, sorry wrong bug

Comment 13 Roman Rakus 2010-06-30 14:23:23 UTC
*** Bug 608899 has been marked as a duplicate of this bug. ***

Comment 14 Roman Rakus 2010-07-01 13:38:25 UTC
*** Bug 601486 has been marked as a duplicate of this bug. ***

Comment 15 Roman Rakus 2010-07-01 13:50:21 UTC
Newly added people to CC; can you please provide the output of "lspci -vvnn" and "dmesg"?

Comment 16 Jayrome 2010-07-01 14:01:11 UTC
Created attachment 428435 [details]
logs.7z

Dell mini 10v

Comment 17 Roman Rakus 2010-07-01 15:22:36 UTC
*** Bug 610040 has been marked as a duplicate of this bug. ***

Comment 18 Roman Rakus 2010-07-01 15:37:25 UTC
*** Bug 610028 has been marked as a duplicate of this bug. ***

Comment 19 Ondrej Vasik 2010-07-02 07:03:06 UTC
*** Bug 610023 has been marked as a duplicate of this bug. ***

Comment 20 Roman Rakus 2010-10-18 13:16:24 UTC
*** Bug 643243 has been marked as a duplicate of this bug. ***

Comment 21 Peter H. Jones 2010-10-18 14:47:41 UTC
Created attachment 454137 [details]
gzipped tar of files requested in commet #15

Attaching files requested in comment 15.
I have a hibernate bug, reported in bug 438107.

Comment 22 Bug Zapper 2010-11-04 02:09:44 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 23 Kaare Fiedler Christiansen 2010-11-06 19:33:40 UTC
I longer have Fedora 12 nor the hardware I originally saw this on.
Looking at duplicates it seems to have been reported on Fedora 12 only. If anyone in the CC list have seen this particular bug with bash crashing in later versions, please comment, and the bug can be reopened.

As for now I'm closing this bug.

Comment 24 Roman Rakus 2011-02-09 06:10:14 UTC
*** Bug 656792 has been marked as a duplicate of this bug. ***