[no subject]

> which you can update to with 'yum upgrade NetworkManager*'.  It's highly
> likely that new build from over a year later will fix your problem.
>
> If you don't want to update, you could try to remove all the connections
> you can find from nm-connection-editor.

When I fire up nm-connection-editor I don't see any connections there.
I have never used this tool before, what should I be seeing?

> Those log messages mean
> something is providing a bad connection profile to NetworkManager.

Where are these connection profiles stored? I'd really like to get to
the bottom of this but I'm totally out of ideas.

Thanks a lot,
Daniel


> Dan
>
>
>> You can see the problems start with:
>>
>> Nov 17 02:28:34 localhost console-kit-daemon[1999]: WARNING: Couldn't
>> read /proc/2174/environ: Error reading file '/proc/2174/environ': No
>> such process
>> Nov 17 02:28:34 localhost NetworkManager: (eth0) supplicant interface
>> is now in state 1 (from 0).
>> Nov 17 02:28:34 localhost NetworkManager: killswitch_getpower_reply():
>> Error getting killswitch power: hal-ipw-killswitch-linux returned 255.
>> Nov 17 02:28:34 localhost NetworkManager: (eth0) supplicant interface
>> is now in state 2 (from 1).
>>
>> And there is more, stuff like:
>>
>> Nov 17 02:29:09 localhost gconfd (fetchinson-2449): Resolved address
>> "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only
>> configuration source at position 0
>> Nov 17 02:29:09 localhost gconfd (fetchinson-2449): Resolved address
>> "xml:readwrite:/home/fetchinson/.gconf" to a writable configuration
>> source at position 1
>> Nov 17 02:29:09 localhost gconfd (fetchinson-2449): Resolved address
>> "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only
>> configuration source at position 2
>> Nov 17 02:29:48 localhost NetworkManager: Missing required value 'name'.
>> Nov 17 02:29:48 localhost NetworkManager: 'connection' setting not
>> present.
>> Nov 17 02:29:48 localhost NetworkManager: Missing required value 'name'.
>>
>> I'm not sure what all this means, but maybe the gnome config files got
>> messed up?
>>
>> Cheers,
>> Daniel
>>
>>
>
>


-- 
Psss, psss, put it down! - http://www.cafepress.com/putitdown