Each time I log in I have to click on the wireless icon and put a tick on the 'enable wireless' option to start the wireless connection. I have the 'Edit Network Connection' on 'Connect automatically' and also 'System connection' ticked as well. I noticed that in 'Advanced permissions' each time I add myself as an available user to use the connection it resets upon reboot.

How can I have wireless enabled when I log in?

I followed these instructions with no luck:

http://forum.sabayon.org/viewtopic.php? ... 40#p131240

Please confirm that your wireless connection is indeed a "System connection" and that no power saving systems or physical switches are telling NetworkManager to start with Wireless disabled.

In my experience, connections must be created as System Connections, and cannot be switched afterward (at least for me, the state never stuck - I had to recreate it).

thanks bcooksley,

I've tried with 'System Connection' on and off several times. Tried erasing the net information and re-adding several times. I don't know if the power manager is touching the net connection.

I've been using KDE for a long time and this is the first time this has happened to me. I think its the default Chakra setup. They must have added something.

Too bad. Because this, as small as it is, might be a deal breaker for me using Chakra.

You can probably disable this behaviour. First thing you'll need to check is the configuration of NetworkManager itself. Unfortunately, this varies depending on the distribution. Probably best to check the init script which starts NetworkManager...

You can switch between system and user connections at will in Plasma NM 0.8.80 and beyond. I basically use only user connections to make kwallet stores them. When using system connection the secrets are stored in plain text.

Send the output of command 'rfkill list' when the problem happens. If rfkill is blocking the wireless you will have to configure it to do not do so. Check if 'cat /sys/module/rfkill/parameters/default_state' returns '1', if not then you need to configure rfkill in /etc/modprobe.conf or the file Chakra uses to pass parameters to kernel modules.

KDE's powermanagement software (Bluedevil) does not affect NetworkManager's behaviour. Usually it is rfkill, the computer's BIOS, a driver problem or a problem in NetworkManager itself that causes wifi to be disabled when it should not be. Send the me the outpout of the commands below:

uname -a
rfkill list
cat /var/lib/NetworkManager/NetworkManager.state

Also send me the file ~/.xsession-errors and NetworkManager's log file.

Thank you bcooksley and lamarque but I have since put Arch back on the computer.

I do know that I need to have rfkill installed and have a daemon running to get the net to properly run in Arch so maybe that's what was needed in Chakra?

Anyways, just wanted to let you guys know so you know that I appreciate the advice. The next time I install Chakra I'll try those solutions.