Bug 297267 - impossible to configure encrypted network via wicd-client-kde
Summary: impossible to configure encrypted network via wicd-client-kde
Status: RESOLVED DOWNSTREAM
Alias: None
Product: wicd-client-kde
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Anthony Vital
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-01 21:18 UTC by Evgeny
Modified: 2012-04-01 22:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
emerge --info (12.98 KB, text/plain)
2012-04-01 21:18 UTC, Evgeny 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Evgeny 2012-04-01 21:18:51 UTC 
Created attachment 70061 [details]
emerge --info

Compile wicd, wpa_supplicant (+ssl +gnutls +eap-sim ), wicd-client-kde

run wicd-client-kde, choose WPA/WEP/WPA2 network, check "Use encryption" 

Actual results: no possible encryption types are suggested. No field to type password.

Expected result: Drop-down menu with encryption options are became available, like when you start wicd-gtk

link to gentoo bugzila bug: 
https://bugs.gentoo.org/show_bug.cgi?id=409375
Comment 1 Anthony Vital 2012-04-01 21:31:56 UTC 
This typically happens when the default python binary (probably python3) is not the one used with Wicd (probably python2). You have to use the cmake flag -DPYTHONBIN=/path/to/python to make it work (the default is just "python"). You can try with -DPYTHONBIN=python2. 
Please let me know if this works or not.
Comment 2 Evgeny 2012-04-01 21:57:15 UTC 
Thank you it's real in it. I set default python to python2 and restart wicd, dbus and kde and now it works fine. Thank you.
Comment 3 Anthony Vital 2012-04-01 22:00:15 UTC 
Alright, I'm closing the report then.