Bug 611732

Summary: [abrt] crash in bash-4.0.35-3.fc12: do_lookup_x: Process /bin/bash was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: colinmw
Component: bashAssignee: Roman Rakus <rrakus>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: rrakus, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:5a13d93c844ea42577e38763ef3edc964b9277fa
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-17 12:45:05 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 colinmw 2010-07-06 10:10:30 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /bin/sh /usr/sbin/gdm -nodaemon
component: bash
crash_function: do_lookup_x
executable: /bin/bash
global_uuid: 5a13d93c844ea42577e38763ef3edc964b9277fa
kernel: 2.6.32.14-127.fc12.x86_64
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 colinmw 2010-07-06 10:10:33 UTC
Created attachment 429726 [details]
File: backtrace

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

Comment 3 colinmw 2010-08-17 11:47:42 UTC
Sorry, typically I don't use the linux gui environment, although it is loaded on boot up. It may have been related to that process.

The machine is not a laptop so hibernation may not apply.

Comment 4 Roman Rakus 2010-08-17 12:45:05 UTC
Hm ok. I will close this bug. Feel free to reopen it when you will have some reproducer.