Bug 611732 - [abrt] crash in bash-4.0.35-3.fc12: do_lookup_x: Process /bin/bash was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in bash-4.0.35-3.fc12: do_lookup_x: Process /bin/bash was killed...
Alias: None
Product: Fedora
Classification: Fedora
Component: bash (Show other bugs)
(Show other bugs)
Version: 12
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Roman Rakus
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:5a13d93c844ea42577e38763ef3...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-06 10:10 UTC by colinmw
Modified: 2014-01-13 00:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-17 12:45:05 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (38.33 KB, text/plain)
2010-07-06 10:10 UTC, colinmw
no flags Details

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
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.

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