Bug 1284318

Summary: F23 - firewall-config needs authorization prompt to continue, but doesn't appear
Product: [Fedora] Fedora Reporter: Gerald Cox <gbcox>
Component: lxqt-commonAssignee: Helio Chissini de Castro <helio>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 23CC: helio, projects.rg, rdieter, ti.eugene
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-24 18:04:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Gerald Cox 2015-11-23 02:44:09 UTC
Description of problem:

When try to start firewall-config (via command line or firewalld-applet), after intial gui screen appears, receive popup which says cannot continue, not authorized.  When I run this under Plasma, I receive a popup which says system policy requires password to continue.  I enter the password, then receive the firewall-config gui.

Version-Release number of selected component (if applicable):
lxqt 010

How reproducible:
Start firewall-config gui via command line or firewalld-applet

Actual results:
Unauthorized message

Expected results:
Receive prompt for password, then normal operation.

Additional info:
Not sure if this is a packaging issue, or upstream.  If upstream, let me know and I'll open a ticket with them.  Thanks!

Comment 1 Raphael Groner 2015-11-24 12:21:18 UTC
Does it work if you start /usr/libexec/lxqt-policykit-agent in a terminal? You can add this also to autostart applications.

Comment 2 Gerald Cox 2015-11-24 18:04:36 UTC
(In reply to Raphael Groner from comment #1)
> Does it work if you start /usr/libexec/lxqt-policykit-agent in a terminal?
> You can add this also to autostart applications.

Yes!  Thank you very much!  Closing this as duplicate of rhbz#1220159

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