After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 649422 - Network Manager 0.8.9: nothing happens when I select my wireless connection
Network Manager 0.8.9: nothing happens when I select my wireless connection
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2011-05-05 00:10 UTC by David Fajardo
Modified: 2011-07-08 15:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
This is the NM window open when I select my wireless connection but it crash 1 seg later (187.17 KB, image/png)
2011-05-05 00:10 UTC, David Fajardo
Details

Description David Fajardo 2011-05-05 00:10:30 UTC
Created attachment 187250 [details]
This is the NM window open when I select my wireless connection but it crash 1 seg later

Since I updated GNOME 3 and networkmanager-0.8.998-3 and network-manager-applet-0.8.998-2 I can't connect to my personal wireless connection. I select this in the Network Manager applet and it opens a window asking my password root, then I write the pass and nothing happens, the window close and not connect. I try connect again but the window crash: it close 1 seg later with the message "try again" (I have uploaded the photo). Apparently, I can connect with any wireless connection, less to mine. Wired connections works well.

I checked nm-connection-editor but not show my personal wireless connection as if I had never connected before. Seems that it delete or hide the wireless info with the update. While the wired and Mobile Broadband connection are there. Then, apparently the problem is with the NM and NM-applet update, because not recognize and doesn't let connect the wireless connections used.

With GNOME 2 I don't had any problem with the NM, until I updated it. The last version of NM and NM-applet that works well for me (in GNOME 3) are networkmanager-0.8.3-0.20110113 and network-manager-applet-0.8.2-4. For the moment, the fix I found was downgrade NM and NM-applet for these versions, and work well.

Today I probe a new update of networkmanager 0.8.999-1 and network-manager-applet 0.8.999-1 in Arch Linux but with the same problems.

Arch Linux x86_64
GNOME 3
The last version of NM I probed without fix were networkmanager 0.8.999-1 and network-manager-applet 0.8.999-1
Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

Some bugs reported related: 
https://bugs.archlinux.org/task/23738
https://bugs.archlinux.org/task/24006
Comment 1 Guilherme de Sousa 2011-05-05 12:14:09 UTC
My situation:

In nm-applet wireless networks that I use started appearing in zones that they don't exist. For example in my university it started showing my Home wireless router as available and with signal.. then I killed NetworkManager and started it again, and it showed a network I use at a coffee shop... And the worst part is that it shows my univ network (eduroam), but when I try to connect it asks for password immediately.. I insert it and it asks again, over and over.

Downgraded to NetworkManager&nm-applet and it started working again, so the problem is from the NetworkManager and not any of the dependencies I guess.

Best regards

setup:
ArchLinux i686
EeePc 1000h
Awesome WM
NetworkManager 
network-manager-applet
Comment 2 Dan Williams 2011-05-06 18:19:01 UTC
David; we found and fixed a bug recently that could be the cause of this one, but it didn't make 0.8.999.  Are you able to try git snapshots?  Is the bug regularly reproducible, and if so, do you know how to get a 'gdb' backtrace from NetworkManager?
Comment 3 David Fajardo 2011-05-07 04:39:24 UTC
Hello Dan: I tried install NM and NM-applet git version from yaourt in Arch Linux but for the moment has a problem with the package, however, the last week I installed both but had the same problem.

While I make the GDB report about NM (tomorrow I'm going to do), paste the error system log, where has some information related with the NM bug mentioned:

/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: ssh-agent not found!
/etc/gdm/Xsession: Setup done, will execute: gnome-session
GNOME_KEYRING_CONTROL=/tmp/keyring-cWVXkO
GNOME_KEYRING_CONTROL=/tmp/keyring-cWVXkO
GPG_AGENT_INFO=/tmp/keyring-cWVXkO/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-cWVXkO
GPG_AGENT_INFO=/tmp/keyring-cWVXkO/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-cWVXkO/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-cWVXkO
GPG_AGENT_INFO=/tmp/keyring-cWVXkO/gpg:0:1

(gnome-settings-daemon:3359): keybindings-plugin-WARNING **: La combinación de teclas (screenreader) está incompleta

(gnome-settings-daemon:3359): keybindings-plugin-WARNING **: La combinación de teclas (magnifier) está incompleta

(gnome-settings-daemon:3359): keybindings-plugin-WARNING **: La combinación de teclas (onscreenkeyboard) está incompleta
Failed to play sound: File or data not found
** Message: applet now removed from the notification area
      JS LOG: GNOME Shell started at Fri May 06 2011 23:12:14 GMT-0500 (COT)

** (nm-applet:3401): WARNING **: Failed to move connection 'Auto Fajardo!! ;)' to NetworkManager system settings: Saving connection failed: (0) writer.c.980: could not find suitable keyfile file name (/etc/NetworkManager/system-connections/Auto Fajardo!! ;)-1a80a4bb-d522-4b59-bfcd-721bdd585576 already used)
** Message: applet now embedded in the notification area

(gnome-shell:3390): Clutter-WARNING **: Failed to set the markup of the actor of class 'ClutterText': Error en la línea 1, carácter 56: Se cerró el elemento «span», pero el elemento que está abierto actualmente es «markup»

(gnome-shell:3390): Clutter-WARNING **: Failed to set the markup of the actor of class 'ClutterText': Error en la línea 1, carácter 56: Se cerró el elemento «span», pero el elemento que está abierto actualmente es «markup»
.
.
.
Comment 4 David Fajardo 2011-05-07 19:28:04 UTC
Hello Dan: The output gdb from network manager is this: http://pastebin.com/fiP0Guig

The NM never crashed, however, exist errors in the output when it try connect with my personal wifi "Fajardo!! ;)"

I hope the output is correct, if not, i will be attention to more indications.

Thanks Dan
Comment 5 David Fajardo 2011-05-11 22:35:12 UTC
Hello Dan,

I see the bug report continue as "NEEDINFO" status, ¿do you need more information about the bug?.

Yestarday changed to XFCE with a clean install, but the NM and NM-applet problem continue, so, as the problem have said others (in the links I attached in the first message)is not the window manager.

I forget answer that 0.8.999-1 is not a git version, is a stable version on Arch Linux, is the last update. And is in the extra repository:

[root@archlinux davirrirri]# pacman -Ss network manager
extra/networkmanager 0.8.999-1 [instalado]
    Network Management daemon
extra/network-manager-applet 0.8.999-1 [instalado]
    GNOME frontends to NetWorkmanager
Comment 6 David Fajardo 2011-05-11 22:40:05 UTC
Edit:
*is not a window manager problem, is the NM and NM-applet issue.
Comment 7 Fabio Durán Verdugo 2011-06-25 00:20:55 UTC
any news for this report?
Comment 8 Jiri Klimes 2011-07-04 13:48:25 UTC
David, could you update to networkmanager 0.8.9997-1 or current git snapshot and try again and report the result? There are number of fixes in that versions.
Comment 9 David Fajardo 2011-07-06 21:39:42 UTC
Hello Jiri, pitifully the problem continue. I tried with both: networkmanager and network-manager-applet from extra repository (0.8.9997-1) and git version from AUR (20110706-1).

The GDB output from networkmanager is this:
http://pastebin.com/niAckqDP
Comment 10 Jiri Klimes 2011-07-07 08:37:51 UTC
; (semicolon) character in SSID causes problems here.
SSID used to be specified as semicolon-separated int list in keyfile files. SSID is basically 0-32 octets.
But, in most cases SSIDs just use printable character. Thus keyfile supports SSID as strings (new format), and int list (older format) for compatibility. However, ; character in the string confuses the parser and it tries to read SSID in older format, resulting in the error. We should think of a way to solve that.
As a workaround, please don't use ; in your SSID.
Comment 11 Jiri Klimes 2011-07-07 13:34:36 UTC
keyfile plugin is enhanced to allow ';' in SSIDs:
30c41a4b800408150edcca9047a3996fa1d6ae68 (master)
Comment 12 David Fajardo 2011-07-08 15:40:13 UTC
Jiri, thanks a lot!. After all was a SSID problem :D 
Now networkmanager works perfect, lovely! 
Always grateful