Bug 689708 - [abrt] policycoreutils-2.0.85-19.fc14: spec_hasMetaChars: Process /usr/sbin/restorecond was killed by signal 11 (SIGSEGV)
Summary: [abrt] policycoreutils-2.0.85-19.fc14: spec_hasMetaChars: Process /usr/sbin/r...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3620a635e63e64d309799588496...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-22 08:50 UTC by matt_home123
Modified: 2012-07-27 13:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-27 13:22:30 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (26.30 KB, text/plain)
2011-03-22 08:50 UTC, matt_home123 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description matt_home123 2011-03-22 08:50:48 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 26932 bytes
cmdline: /usr/sbin/restorecond -u
component: policycoreutils
Attached file: coredump, 4866048 bytes
crash_function: spec_hasMetaChars
executable: /usr/sbin/restorecond
kernel: 2.6.35.11-83.fc14.x86_64
package: policycoreutils-2.0.85-19.fc14
rating: 4
reason: Process /usr/sbin/restorecond was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300783261
uid: 500

How to reproduce
-----
1.
2.
3.
I was doing a automated update. While the update was in progress the pc locked up. I held the power button down to shut the pc off. I did a reboot and had to press "yes" several times and then typed in fsck.
Comment 1 matt_home123 2011-03-22 08:50:50 UTC 
Created attachment 486754 [details]
File: backtrace
Comment 2 Daniel Walsh 2012-07-27 13:22:30 UTC 
Since this version of Fedora is no longer supported I am closing this bugs.  If you are still seeing this bug in a current version of fedora, please reopen the bugzilla with the appropriate version number.
Note You need to log in before you can comment on or make changes to this bug.