network-manager-applet crashes on connecting to Vista hosted ad-hoc wireless subnet

Bug #479085 reported by Wasa
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
New
Undecided
Unassigned

Bug Description

When I'm trying to connect to my Vista ad-hoc wireless network the network-manager-applet crashes with the foloowing record in the /var/log/messages:

Nov 8 20:25:31 wasa-laptop kernel: [21107.487412] nm-applet[14579]: segfault at 8 ip 00007f256f6c45bf sp 00007f255d5b9f30 error 4 in libgio-2.0.so.0.2200.2[7f256f692000+a6000]

Ad-hoc is WPA2-PSK/AES but there was no any options/passphrase shown when I'm choosing it in applet tray menu before applet is crashed.

ProblemType: Bug
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Mon Nov 9 14:24:48 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nm-applet
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IpRoute:
 172.17.2.0/24 dev eth0 proto kernel scope link src 172.17.2.29 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 172.17.2.2 dev eth0 proto static
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
SourcePackage: network-manager-applet
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
Wasa (v-egoshin) wrote :
Revision history for this message
Ximatz (ximatz) wrote :

Sorry, I am new to bug reporting, and I don't know if I am wright here or not. My apologizes if I should post this somewhere else.

I have also the same problem. The nm-applet crashes every time I try to connect to a wireless ad-hoc network made by a Windows machine. Following differences apply by me, though:
- The ad-hoc network was made by computer running Windows 7
- I am using a 32-bit version of Ubuntu (Linux 2.6.31-14-generic i686)

Unfortunately there is no record of the crash on any log file on my system every time the applet disappears. The only message I can get from the system is from the console. For this, I restart the applet from the console manually every time it crashes and try to select the ad-hoc wireless network again from the available networks list. This is what I get:

$ nm-applet
**
ERROR:applet.c:334:applet_menu_item_activate_helper_part2: assertion failed: (connection)
Aborted

This happens only with ad-hoc networks using WPA2-Personal encryption, as described in the original bug report. The nm-applet does not crash, if the ad-hoc network uses WEP encryption.

I have been using WEP encryption as a work around for this problem, but this is not a satisfactory solution.

Revision history for this message
Maciej Lopuszanski (mackos1-o2) wrote :

the same here.....

i was tying to setup adhoc network made by win vista and connecting from ubuntu 9.10 kernel:2.6.31-18.

only that i get is this cool looking error :)
ERROR:applet.c:334:applet_menu_item_activate_helper_part2: assertion failed: (connection)
Aborted

there is exactly no difference between secured adhoc or open adhoc connection. error just likes me no mater what.

Revision history for this message
Andrew Collette (andrew-collette) wrote :

This is still happening with a fully patched version of Karmic (9.10). When trying to connect to an ad-hoc network (with WPA2 hosted on a Windows 7 machine), nm-applet exits with:

ERROR:applet.c:334:applet_menu_item_activate_helper_part2: assertion failed: (connection)
Aborted

I can also confirm (as Ximatz wrote) that it does not happen with WEP enabled or in no-encryption (open) mode. However, WEP is completely inappropriate for this task... sharing an internet connection wirelessly requires good encryption.

I noticed this bug has been categorized as new/undecided since November. Are there any plans to address this?

Revision history for this message
Martinichka (m-lootsma) wrote :

Same happened here. Both machine are Ubuntu 10.4 32bit. I as well tried secure and open ad-hock connection. The error message I get is:
May 11 23:39:26 **** kernel: [ 106.299726] nm-applet[1282]: segfault at 0 ip 0805a6ea sp bf903350 error 4 in nm-applet[8048000+55000]

Hasn't been there any development on this bug since November?

Revision history for this message
Рустам Second_Fry Губайдуллин (secondfry) wrote :

Just affected me
[ 186.407535] nm-applet[5377]: segfault at 0 ip 0805a6ea sp bfcb4350 error 4 in nm-applet[8048000+55000]

Also, if I try to set SSID manually, it's changes to some strange text.
wlan0 IEEE 802.11bg ESSID:"g\xC6isQ\xFFJ\xEC)\xCD\xBA\xAB\xF2\xFB\xE3F|\xC2T\xF8\x1B\xE8\xE7\x8DvZ.c3\x9F\xC9\x9A"

Revision history for this message
Рустам Second_Fry Губайдуллин (secondfry) wrote :

There is some more info. This is my card:
00:0b.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)

If I try to "Create new wireless connection" nm-applet crashes.
rustam-desktop rustam # dmesg | grep segfault
[ 45.438295] nm-applet[2568]: segfault at 0 ip 0805a6ea sp bf89ffc0 error 4 in nm-applet[8048000+55000]
[ 116.688619] nm-applet[3062]: segfault at 0 ip 0805a6ea sp bf8da600 error 4 in nm-applet[8048000+55000]
[ 131.870163] nm-applet[3623]: segfault at 0 ip 0805a6ea sp bfd40f60 error 4 in nm-applet[8048000+55000]
[ 150.527491] nm-applet[4114]: segfault at 0 ip 0805a6ea sp bff7c0a0 error 4 in nm-applet[8048000+55000]
[ 159.986410] nm-applet[4677]: segfault at 0 ip 0805a6ea sp bff02060 error 4 in nm-applet[8048000+55000]
[ 173.320722] nm-applet[4888]: segfault at 0 ip 0805a6ea sp bfb45d00 error 4 in nm-applet[8048000+55000]
[ 186.407535] nm-applet[5377]: segfault at 0 ip 0805a6ea sp bfcb4350 error 4 in nm-applet[8048000+55000]

Revision history for this message
qdlaty (wojciech-kudla) wrote :

Same here. The device is:
10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
using iwl3945
Ubuntu 10.04, 64-bit, kernel: 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:05:27 UTC 2010 x86_64 GNU/Linux
It's impossible to create an ad-hoc network - neither with gnome-network-manager nor iwconfig.
The network's essid gets changed to something like:
"e\xCCM($H:\xA0\x00\xD2j\x14|\xE8w#\x9F\xA3\xB9\x05x\xAE\xCA\x98\x12S\x03\xFE\x05\x9F\x0Cj"
after several seconds.
Come on guys, is it so hard to take a look and propose a workaround or something?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.