Bug 617883

Summary: [abrt] crash in lxpolkit-0.1.0-0.1.20100402git5087383.fc13: Process /usr/libexec/lxpolkit was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jérémy Libion <ribionu>
Component: lxpolkitAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:365d869a61176673d9861581e8d572ae075adccb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-24 17:46:03 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 Jérémy Libion 2010-07-24 16:31:28 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/lxpolkit
component: lxpolkit
executable: /usr/libexec/lxpolkit
global_uuid: 365d869a61176673d9861581e8d572ae075adccb
kernel: 2.6.33.6-147.fc13.x86_64
package: lxpolkit-0.1.0-0.1.20100402git5087383.fc13
rating: 4
reason: Process /usr/libexec/lxpolkit was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Jérémy Libion 2010-07-24 16:31:34 UTC 
Created attachment 434168 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-07-24 17:46:03 UTC 
You submitted the same bug report already yesterday and the solution how to fix it is in bug 616730. Please follow the instructions from that bug and if they don't work, please make notice of it there but please do not submit the bug a third time without a comment.

Whenever you submit a bug report using the automatic bug reporting tool ABRT, please be so kind as to fill out all required fields, especially 'Comment' and 'How to reproduce'. TIA!

*** This bug has been marked as a duplicate of bug 616730 ***