connmand crashes in wifi plugin

Bug #620503 reported by Connel Hooley
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Connection Manager
Triaged
High
Kalle Valo
Network Menu
Invalid
Medium
Kalle Valo

Bug Description

I am trying to connect to my Wi-Fi 802.11 G network that is secured with WPA or WPA2 Personal encryption. I followed the following here http://www.omgubuntu.co.uk/2010/05/help-test-ubuntu-1010s-proposed-network.html but when I reboot after following those instructions the network indicator is there but clicking on it gives me one greyed out menu option saying "command not available". I am running Ubuntu 10.04.

Revision history for this message
Kalle Valo (kvalo) wrote :

I believe it actually says "connmand not available", meaning that connmand (Connection Manager daemon) is not running for some reason. I'm guessing that connmand doesn't start because NetworkManager is already running.

To debug this, first check that connman is installed:

dpkg -l connman

Syslog might contain hints why connman is not starting:

grep connmand /var/log/syslog

And then check that connmand is running and NetworkManager is not:

ps aux | less

Also you might want to revisit the installation instructions here:

https://wiki.ubuntu.com/ConnMan/Installation

Revision history for this message
Connel Hooley (connelhooley) wrote :
Download full text (25.5 KiB)

Sorry yes it does say "connmand not available" my mistake. Here are the outputs of the commands you told me to run. I couldn't find the conmand process in the ps aux | less. Posting it here just in case I missed it.

connel@connel-laptop:~$ dpkg -l connman
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=======================================-=======================================-==============================================================================================
ii connman 0.53+git.20100614t210259.168c346+dfsg-0 Intel Connection Manager daemon

connel@connel-laptop:~$ grep connmand /var/log/syslog
Aug 19 16:26:42 connel-laptop connmand[1155]: Connection Manager version 0.53
Aug 19 16:26:42 connel-laptop connmand[1155]: Checking loopback interface settings
Aug 19 16:26:42 connel-laptop connmand[1155]: System hostname is connel-laptop
Aug 19 16:26:42 connel-laptop connmand[1155]: Adding profile default
Aug 19 16:26:42 connel-laptop connmand[1155]: lo {newlink} index 1 operstate 0 <UNKNOWN>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth0 {create} index 2 type 1 <ETHER>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth0 {update} flags 4098 <DOWN>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth0 {newlink} index 2 address 00:21:9B:CC:20:93 mtu 1500
Aug 19 16:26:42 connel-laptop connmand[1155]: eth0 {newlink} index 2 operstate 2 <DOWN>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {create} index 3 type 1 <ETHER>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {update} flags 4098 <DOWN>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {newlink} index 3 address 00:22:5F:03:68:54 mtu 1500
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {newlink} index 3 operstate 2 <DOWN>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth0 {newlink} index 2 address 00:21:9B:CC:20:93 mtu 1500
Aug 19 16:26:42 connel-laptop connmand[1155]: eth0 {newlink} index 2 operstate 2 <DOWN>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth0 {update} flags 4099 <UP>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth0 {newlink} index 2 address 00:21:9B:CC:20:93 mtu 1500
Aug 19 16:26:42 connel-laptop connmand[1155]: eth0 {newlink} index 2 operstate 2 <DOWN>
Aug 19 16:26:42 connel-laptop connmand[1155]: Enabling quirks for unsupported driver
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {scan} capabilities 0x01
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {quality} flags 0x00
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {newlink} index 3 address 00:22:5F:03:68:54 mtu 1500
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {newlink} index 3 operstate 2 <DOWN>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {update} flags 69699 <UP,RUNNING,LOWER_UP>
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {newlink} index 3 address 00:22:5F:03:68:54 mtu 1500
Aug 19 16:26:42 connel-laptop connmand[1155]: eth1 {newlink} index 3 operstate 0 <UNKNOWN>
Aug 19 16:26:44 connel-laptop connman...

Revision history for this message
Kalle Valo (kvalo) wrote : Re: [Bug 620503] Re: Network indicator doesn't work. It just says "command not available"

Connel Hooley <email address hidden> writes:

> Here are the outputs of the commands you told me to run. I couldn't
> find the conmand process in the ps aux | less. Posting it here just in
> case I missed it.

Thanks, this was very helpful. connman crashes during boot and that's
why it's not running:

> Aug 19 16:26:44 connel-laptop kernel: [ 41.159167] connmand[1155]: segfault at 0 ip 00c0876f sp bfc78230 error 4 in wifi.so[c01000+9000]

[...]

> Aug 20 21:37:00 connel-laptop connmand[1185]: Connection Manager version 0.53
> Aug 20 21:37:01 connel-laptop kernel: [ 41.924147] connmand[1185]: segfault at 0 ip 004bc76f sp bffba290 error 4 in wifi.so[4b5000+9000]

I assume it happens everytime connman is started because you see the not
available message in the menu all the time and there are two entries of
connmand segfault in the log.

The crash happens in the connman's wifi plugin. What wifi device and
driver are you using? Outputs from lsmod and lspci (and lsusb if you are
using a usb device) help here.

As a workaround, and to verify that wifi plugin is really the culprit
here, you can ask connman to ignore your wifi device, which I assume to
be eth1, by editing /etc/default/connman and changing DAEMON_OPTS to
this:

DAEMON_OPTS="$DAEMON_OPTS -c -W wext -I eth1"

But I would really like to know more about the crash so that I can fix
it. It would help a lot if you can install the daily build version of
connman, enable apport temporarily and send the crash files to me, the
more the better :) Here are the instructions:

  1. Fetch and install connman daily build version for Ubuntu 10.04.
     Choose amd64 or i386 based on your architecture:

     https://launchpad.net/~indicator-network-developers/+archive/daily-ppa/+files/connman_0.56%2Bind-0ubuntu1~ind1%2Br2534%2B201008220428_amd64.deb
     https://launchpad.net/~indicator-network-developers/+archive/daily-ppa/+files/connman_0.56%2Bind-0ubuntu1~ind1%2Br2534%2B201008220428_i386.deb

  2. Reboot computer.

  3. Enable apport temporarily (it will be disabled again in next boot):

     sudo service apport start force_start=1

     https://wiki.ubuntu.com/Apport#How to enable apport

  4. Try to start connmand few times:

     sudo /etc/init.d/connman start

  5. Check that there are _usr_sbin_connmand crash files in /var/crash/
     and send them privately to me to <email address hidden>.

Please note that the daily build might not crash for you anymore. Let me
know how it goes.

--
Kalle Valo

Kalle Valo (kvalo)
Changed in connman:
status: New → Confirmed
Changed in indicator-network:
status: New → Confirmed
Changed in connman:
assignee: nobody → Kalle Valo (kvalo)
Changed in indicator-network:
assignee: nobody → Kalle Valo (kvalo)
Revision history for this message
Connel Hooley (connelhooley) wrote : Re: Network indicator doesn't work. It just says "command not available"

Hi, thanks for the detailed instructions. I'm away on holiday at the moment so won't be able to get back to you till Thursday. I'll send you the results as quick as I can.

Connel

Revision history for this message
Connel Hooley (connelhooley) wrote :

I followed your instructions. I installed and enabled the daily build version using the link to the .deb you gave me. I enabled apport and rebooted. The applet appears to be working fine now. I'm at home and I can connect to my Wi-Fi connection successfully. I looked in /var/crash/ and no crash logs were there.

I did notice however, that the old network manager allowed me to connect to the net using my phone as a 3G modem. I would simply plug in my Nokia N900 using a USB cable, selected PC Suite connection on the phone and then select the connection in the old network manager. However this doesn't work with the new indicator applet. Is this a different bug or our 3G connections not fully implementation yet?

I have installed ofono and usb-modeswitch but when I run "cmcc list" only my Wi-Fi connections are listed. Do I need these packages from the daily PPA also?

Sorry to go off topic a little. If it is a seperate bug I'll create another bug and supply any information I can to help.

Thanks Connel

Revision history for this message
Kalle Valo (kvalo) wrote : Re: [Bug 620503] Re: Network indicator doesn't work. It just says "command not available"

Connel Hooley <email address hidden> writes:

> I followed your instructions. I installed and enabled the daily build
> version using the link to the .deb you gave me. I enabled apport and
> rebooted. The applet appears to be working fine now. I'm at home and I
> can connect to my Wi-Fi connection successfully. I looked in /var/crash/
> and no crash logs were there.

Excellent. So the crash is fixed on newer connman versions.

Unfortunately connman version in maverick is quite a lot older than the
daily build you tried and it's difficult to say if this problem is
really fixed in maverick.

> I did notice however, that the old network manager allowed me to connect
> to the net using my phone as a 3G modem. I would simply plug in my Nokia
> N900 using a USB cable, selected PC Suite connection on the phone and
> then select the connection in the old network manager. However this
> doesn't work with the new indicator applet. Is this a different bug or
> our 3G connections not fully implementation yet?
>
> I have installed ofono and usb-modeswitch but when I run "cmcc list"
> only my Wi-Fi connections are listed. Do I need these packages from the
> daily PPA also?
>
> Sorry to go off topic a little. If it is a seperate bug I'll create
> another bug and supply any information I can to help.

Please file a new bug, I'll reply there. One issue per bug report, much
cleaner that way :)

--
Kalle Valo

Kalle Valo (kvalo)
summary: - Network indicator doesn't work. It just says "command not available"
+ connmand crashes in wifi plugin
Kalle Valo (kvalo)
Changed in indicator-network:
importance: Undecided → Medium
Kalle Valo (kvalo)
Changed in connman:
importance: Undecided → High
status: Confirmed → Triaged
Changed in indicator-network:
status: Confirmed → Invalid
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.