Bug 287317 - Clicking on the Action/Vendor link does not work
Summary: Clicking on the Action/Vendor link does not work
Status: CONFIRMED
Alias: None
Product: policykit-kde-agent-1
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Dario Freddi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-22 23:46 UTC by S. Burmeister
Modified: 2021-03-09 07:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2011-11-22 23:46:18 UTC
Version:           unspecified (using KDE 4.7.3) 
OS:                Linux

If a policykit dialogue appears one can open the details and see what action the dialogue is about. The action is a link and if one hovers it it states "click to edit org…" Yet clicking on it does nothing. Clicking on "Vendor" opens ~/Documents – not sure how that is related to "Vendor".

Reproducible: Always

Steps to Reproduce:
Trigger a policykit dialogue, e.g. via systemsettings.
Click on the links for Action and Vendor

Actual Results:  
Nothing happens for "Action"
~/Documents opens for "Vendor"

Expected Results:  
Open an editor (module) to edit the "Action" settings
Not sure what "Vendor" should do, but opening ~/Documents in a browser seems useless
Comment 1 Max Lin 2012-03-21 04:57:33 UTC
Confirmed with source build environment.
It always got the actionId is "org.kde.polkitkde1.readauthorizations", the vendorName as "System policy settings" and empty vendorUrl, and also I doubt Application entry will be empty at all due to  looks nothing to feed m_appname. I am not sure that its a available function but it seems not useful currently.

Steps to reproduce:
1. SystemSettings -> Actions Policy
2. choice any policy then authentication dialog pop-up -> click Details button then there shows more information of this action
3. click Action or Vendor, and saw empty Application entry
or try "kcmshell4 kcm_polkitactions"
Comment 2 Martin Bříza 2013-03-27 14:04:56 UTC
Confirming, this happens when you don't have the kcm_polkitactions module installed. Will decide what to do about it...
Comment 3 Justin Zobel 2021-03-09 07:30:33 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.