Re: Funny behavior for NM and the KDE plasmoid

2012-05-14 Thread Jirka Klimes
On Wednesday 25 of April 2012 20:38:49 Larry Finger wrote:
 I am running openSUSE 12.1 KDE using Rev 0.9.1.90-4.6.1-x86_64 ov
 NetworkManager, and version 0.9.1+0.9.0-1.6.1-x86_64 of the
 plasmoid-networkmanagement applet. For the most part, any problems that I
 see are the fault of the underlying wireless drivers; however, I do see one
 problem.
 
 In general, the applet shows whatever APs that show up in a
 manually-triggered scan. There is, however, one exception. If I have the
 Connect Automatically box checked for one of the APs, that AP rarely
 shows in the possible connections. The one major exception is when the
 driver is unloaded, and then reloaded, when the connection is started
 nearly instantly. I have not tested the nm-applet to see if it shows the
 same behavior.
 
 Are there any steps that I can take to help show where the problem happens?
 
 Thanks,
 
 Larry

I'm not complely sure what is your complaint about, whether KDE-nm GUI or NM 
core behaviour.

Nonetheless, if you run 'nmcli dev wifi list' you will see what APs NM knows 
about and that should also be available in GUIs.
KDE-nm, AFAIK, displays AP and configured connections mixed.
Connect Automatically has no influence on connection visibility. It only 
instructs NM that the connection can be auto-connected.

Jirka


___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Funny behavior for NM and the KDE plasmoid

2012-04-25 Thread Larry Finger
I am running openSUSE 12.1 KDE using Rev 0.9.1.90-4.6.1-x86_64 ov 
NetworkManager, and version 0.9.1+0.9.0-1.6.1-x86_64 of the 
plasmoid-networkmanagement applet. For the most part, any problems that I see 
are the fault of the underlying wireless drivers; however, I do see one problem.


In general, the applet shows whatever APs that show up in a manually-triggered 
scan. There is, however, one exception. If I have the Connect Automatically 
box checked for one of the APs, that AP rarely shows in the possible 
connections. The one major exception is when the driver is unloaded, and then 
reloaded, when the connection is started nearly instantly. I have not tested the 
nm-applet to see if it shows the same behavior.


Are there any steps that I can take to help show where the problem happens?

Thanks,

Larry
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list