Re: nm and wireless

[igel <ich freak gmx net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey Jirka,
there was no reaction to left-clicking whatsoever for nm-applet.
However, yesterday, I entered the credentials to one of the wireless
networks under the "Edit Connection -> Wireless" right-click menu as
"Wireless connection 1" and now, I cannot reproduce the problem any
more, so I consider the issue resolved, although I have no clue what
actually caused this in the first place.

thanks anyways
- -igel

On 09/04/2012 09:18 AM, Jirka Klimes wrote:
> On Monday 03 of September 2012 20:05:47 igel wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Hey Jirka and thanks for answering.
>> 
>> On 09/03/2012 03:00 PM, Jirka Klimes wrote:
>>> On Monday 13 of August 2012 10:59:04 igel wrote:
>>>> I don't quite understand where it should show my wifi device
>>>> - The only place where it does show up is in the "Network 
>>>> Connections" dialog, under "wireless" (I'll attach a
>>>> snapshot again) called "System (wlan0)".
>>>> 
>>>> I do not have a "/var/log/NetworkManager.log", does nm use
>>>> the syslog facilities? Then it should show up in
>>>> /var/log/messages (my syslog-ng is configured to dump
>>>> everything there); However, a # grep wlan0 /var/log/messages
>>>> revealed Aug 13 10:39:44 localhost NetworkManager[3797]:
>>>> SCPlugin-Ifnet: wireless_setting added for wlan0 Aug 13
>>>> 10:39:44 localhost NetworkManager[3797]:    SCPlugin-Ifnet:
>>>> Using dhcp method for wlan0 Aug 13 10:39:44 localhost
>>>> NetworkManager[3797]: SCPlugin-Ifnet: Connection verified
>>>> wlan0:1 Aug 13 10:39:44 localhost NetworkManager[3797]:
>>>> <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
>>>> Aug 13 10:39:44 localhost NetworkManager[3797]: <info>
>>>> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 4)
>>>> Aug 13 10:39:44 localhost NetworkManager[3797]: <info>
>>>> (wlan0): exported as 
>>>> /org/freedesktop/NetworkManager/Devices/0 Aug 13 10:39:44 
>>>> localhost NetworkManager[3797]: <info> (wlan0): now managed
>>>> Aug 13 10:39:44 localhost NetworkManager[3797]: <info>
>>>> (wlan0): device state change: 1 -> 2 (reason 2) Aug 13
>>>> 10:39:44 localhost NetworkManager[3797]: <info> (wlan0):
>>>> preparing device. Aug 13 10:39:44 localhost
>>>> NetworkManager[3797]: <info> (wlan0): deactivating device
>>>> (reason: 2). Aug 13 10:39:44 localhost dhcpcd[2837]: wlan0:
>>>> removing interface Aug 13 10:39:44 localhost 
>>>> NetworkManager[3797]: <info> (wlan0): supplicant manager
>>>> state: down -> idle Aug 13 10:39:44 localhost
>>>> NetworkManager[3797]: <info> (wlan0): device state change: 2
>>>> -> 3 (reason 0) Aug 13 10:39:44 localhost
>>>> NetworkManager[3797]: <info> (wlan0): supplicant interface
>>>> state:  starting -> ready
>>>> 
>>>> So I take it nm is aware of my wifi device!
>>> 
>>> Yes, according to the logs, NM is aware of your Wi-Fi device
>>> and you should be able to see available networks simply by 
>>> left-clicking the nm-applet icon.
>> 
>> I am aware that this is the behavior that I _should_ observe.
>> However, in practice I don't, that's why I wrote to the mailing
>> list. I attached a screenshot of how my nm-cli looks like when
>> right clicked to my orinigal email, and it can also be found in
>> the bugreport I opened at
>> https://bugzilla.gnome.org/show_bug.cgi?id=682233
>> 
>> Here it also shows that "nmcli dev wifi" actually finds all
>> wireless networks in range, yet they are not in the right-click
>> menu of nm.
>> 
> As I wrote before, you have to click nm-applet icon with *left*
> mouse button to see the wireless networks. Right-click just shows
> menu you attached in your first screeenshot.
> 
> If you still have problems, it may be useful to look at
> ~/.xsession-errors where nm-applet should log. Or try to run
> nm-applet in a terminal and you would see possible errors in the
> terminal.
> 
>> I suspect that this is because I am not using gnome as a desktop 
>> environment but E17?
>> 
> That shouldn't be a problem, nm-applet is supposed to run in E17
> without a problem.
> 
>> thanks again for the attention! - -igel
> 
> Jirka
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBFwecACgkQacCjHxaKeMS4KwCcDyGsdDrq/onD0BjDMTrJKRuM
yYIAn3fY2E0qpFiMn5U1Y19Mkc/RyMT+
=6uwM
-----END PGP SIGNATURE-----