Bug 493089

Summary: nm-applet reports warning: "Unhandled setting secret type (write) 'vpn/secrets' : 'GHashTable_ gchararray+gchararray_'"
Product: [Fedora] Fedora Reporter: Tomislav Vujec <tvujec>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: dcbw
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-10 03:01:28 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
Fix warning. none

Description Tomislav Vujec 2009-03-31 15:34:23 UTC 
Description of problem:
nm-applet reports warning "Unhandled setting secret type (write) 'vpn/secrets' : 'GHashTable_ gchararray+gchararray_' " for vpn secrets which are handled by the VPN plugin. 

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0.99

Additional info:
Either check if the secret is of the type vpn before the more general string type check, or do not warn when checking for string type. Latter could be more dangerous. Patch for the former is in the attachment.
Comment 1 Tomislav Vujec 2009-03-31 15:35:10 UTC 
Created attachment 337321 [details]
Fix warning.
Comment 2 Dan Williams 2009-04-09 01:29:14 UTC 

*** This bug has been marked as a duplicate of bug 468113 ***
Comment 3 Tomislav Vujec 2009-04-09 04:01:22 UTC 
Hmmm, are you sure? The warning I am getting seems to be non-issue, since the VPN plugin handles the keyring storage of 'vpn/secrets'. The comment to the code that checks for that type seems to claim so. I just reordered the checks so that it is actually reached, which in turn disables the warning.
Comment 4 Dan Williams 2009-05-10 03:01:28 UTC 

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