Bug 643835

Summary: system-config-firewall org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.firewall.auth:
Product: [Fedora] Fedora Reporter: Martin Krizek <mkrizek>
Component: PolicyKit-kdeAssignee: Orphan Owner <extras-orphan>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: extras-orphan, jreznik, kevin, lorenzo, ltinkl, rdieter, smparrish, twoerner
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-18 10:47:18 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
kcrash none

Description Martin Krizek 2010-10-18 09:17:46 UTC 
Description of problem:
See Actual results.

Version-Release number of selected component (if applicable):
system-config-firewall-1.2.27-1.fc14.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Clean install
2. Menu -> Administration -> Firewall
3.
  
Actual results:
Following error is shown "org.fedoraproject.slip.dbus.service.PolKit.NotAuthorizedException.org.fedoraproject.config.firewall.auth:". The first time system-config-firewall was run, the KDE crash hander was triggered.

Expected results:
Dialog for root password should be shown.

Additional info:
The output of kcrashed attached. Running KDE desktop. System is Fedora 14 Final TC1. Running system-config-firewall as root works fine.
Comment 1 Martin Krizek 2010-10-18 09:19:03 UTC 
Created attachment 454055 [details]
kcrash
Comment 2 Thomas Woerner 2010-10-18 09:33:28 UTC 
According to the kcrash output, this seems to be a PolicyKit1-KDE problem.

Reassigning to PolicyKit1-KDE.
Comment 3 Jaroslav Reznik 2010-10-18 10:47:18 UTC 

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