Okay, for the KDE it is recommended to configure your wireless connection as a ‘System Connection’, and assuming you’re using a WPA passphrase, select, but don’t add it in the config box. Instead, make sure that you have set ‘Store connection secrets’ to ‘In secure storage (encrypted)’. When you do try to connect for the first time, the kwallet password manager will open, and prompt you with its authentication password, and then to add the required passphrase. I hope this makes sense to you.
One more precision
when i am root i did’nt need password for connection but when i am user i need password for connection.
Don’t log in to your desktop as root. It’s bad practice and not necessary.
[QUOTE and i give root password (tree time) and after to connection is droped. I am sur the password is good so looks like a bug in policies.
[/QUOTE]
I think this weird behaviour can happen when you add the passphrase in the NM settings, and use kwallet as well. I have experienced similar strange behaviour with the KDE network manager, but all went away when I started over, as explained above.
On 09/21/2012 06:16 AM, Enthalpie wrote:
>
> deano_ferrari;2489064 Wrote:
>> Don’t log in to your desktop as root. It’s bad practice and not
>> necessary.
> just for test I NEVER use root session only when i got problem
> thank’s
The problem with logging into the KDE GUI as root may change some settings
making it impossible for a normal user to work after that, You may have that
condition.
Use the KDE Connection Manager and delete all connections. Then add the
connection back as suggested above.
OK
yes i have icon and so on but if i clic on delete for one connection, Knetworkmanager still ask me for a password (root) and because it does’nt get it i can’t delete the connection. same thing if i want to add . may be some information to help, when i add new connection, i did’nt see any wireless network in the scan windows . the network which was "not connected disparear from the available network ? I am not sur i am clear ?
regards
On 09/21/2012 12:16 PM, Enthalpie wrote:
> OK
> yes i have icon and so on but if i clic on delete for one connection,
> Knetworkmanager still ask me for a password (root) and because it
> does’nt get it i can’t delete the connection. same thing if i want to
> add . may be some information to help, when i add new connection, i
> did’nt see any wireless network in the scan windows ?
> regards
Because it was set up wrong in the first place, you will need the root password
to undo it. I thought that might be obvious.
When you create the new connection, you should choose to use kwallet to store
the secrets. If you do not use the wallet for any other passwords, it is
reasonably safe to have a blank password for it. Once you do that and tell the
system to always allow knetworkmanager to use it, you will never need a root
password to establish the connection.
The problem with logging into the KDE GUI as root may change some settings
making it impossible for a normal user to work after that, You may have that
condition.
I agree with Larry here, that logging in as root appears to have changed some crucial settings with the system connections. They are stored in the /etc/NetworkManager/system-connections/ directory
Here we are guy
1°) remove old connections OK
2°) on Knetworkmanager no more connections
3°) create new one with all good parameters good news no one ask me for root password
4°) clic on apply … wait wait … and no connection were created but
I have for org.freedesktop.NetworkManager.wifi.share.open
Any No
Inactive console No
Active console Yes
The polkit-kde config XML files are stored in the /usr/share/polkit-1/actions/ directory.
I’ll be the first to admit that polkit configuration is a changing landscape, and it is not easy to keep up with all the changes made. There was a time when changes made by the KDE System Settings >> Action Policy utility seemed to have little or no effect for some authentication roles. Perhaps this has changed. Did you try changing it yet?
Hi
thanks for answer I will learn at your message. but first yes , i made changes a lot
is it possible to delete config.xml file and suse will re create it at login ?
I’m still yet to learn (or be convinced) that any other file is written to. If the org.freedesktop.NetworkManager.policy file was was deleted, you’d need to reinstall this package.
