Cannot connect to WiFi as of upgrading to February 17th Daily of Connection Manager (DeprecationWarning)

I've recently (for the past couple of hours) been receiving a similar error with the previously uneffected daily which I have been using as a fallback (*0.69-0ubuntu1+ind1+r3264+201102120323*). The error output is as follows:
/
DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
  print "%s: %s" % (error._dbus_error_name, error.message)
net.connman.Error.Failed: Input/output error
/
I have a sneaky suspicion that this latest error has more to do with my router however, and I'll put that to the test once I reboot into Ubuntu.

Has anyone been able to replicate or confirm the original bug, or at least understand what any of these verbose errors mean?

Reported upstream @https://bugs.meego.com/show_bug.cgi?id=13718

I was advised by someone upstream to build *connman* from git to see whether this issue is unique to the launchpad.net builds and I received the same error message as with the launchpad.net dailies.

Kind Regards,

Lee Hyde.

It would seem that a recent update to *connman's* git tree has serendipitously fixed this bug, although the most recent daily on in the PPA is still affected. I'll stick with git for the time being, and report back in the unlikely event that the bug persists beyond the next few dailies.

Lee

First of all, this is just a warning:

/usr/bin/cmcc:379: DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
  print "%s: %s" % (error._dbus_error_name, error.message)

This means that I haven't updated the script's exception handling to the latest python syntax. It doesn't break anything (yet), but I should update the code to the latest syntax anyway.

But this is the real error:

org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

This means that we sent a dbus message to connman but didn't get any reply and hence the timeout. I'm guessing this happens because connman crashes. syslog would be able to confirm this, more info here:

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

If the bug is seen with connman PPA builds but not with the git version, it makes me suspect that there's a ubuntu specific change which causes the crash. My main suspect is 04-wifi-add-a-disconnected-timer.patch which we have to improve roaming between wifi access points.

> If the bug is seen with connman PPA builds but not with the git version,
> it makes me suspect that there's a ubuntu specific change which causes
> the crash. My main suspect is 04-wifi-add-a-disconnected-timer.patch
> which we have to improve roaming between wifi access points.

It's worth noting that I haven't been able to update to a more up-to-date daily build (from the Indicator-Network Daily PPA) since testing *connman* from git. It would appear that launchpad has been unable to successfully build any daily since late 26th Feb (although I note that a new build is available, so I'll give that a whirl and see if anything comes of it)

> I'm guessing this happens because connman crashes. syslog would
> be able to confirm this, more info here:
>
> https://wiki.ubuntu.com/ConnMan/Debugging

I'll test the latest daily and read the above link, and should this bug persist I'll attempt to provide more pertinent information as soon as practicable.

Kind Regards,

Lee.

Well, I've just updated to latest daily and all appears to be working well. I've yet to reboot, but I assume that the new build takes effect immediately, without need of a reboot. Is this assumption correct?

Regards,

Lee.

Lee Hyde <email address hidden> writes:

>> If the bug is seen with connman PPA builds but not with the git version,
>> it makes me suspect that there's a ubuntu specific change which causes
>> the crash. My main suspect is 04-wifi-add-a-disconnected-timer.patch
>> which we have to improve roaming between wifi access points.
>
> It's worth noting that I haven't been able to update to a more up-to-
> date daily build (from the Indicator-Network Daily PPA) since testing
> *connman* from git. It would appear that launchpad has been unable to
> successfully build any daily since late 26th Feb (although I note that a
> new build is available, so I'll give that a whirl and see if anything
> comes of it)

Yes, daily builds were broken last week while I was away. I fixed them
today and they should be running automatically again.

>> I'm guessing this happens because connman crashes. syslog would
>> be able to confirm this, more info here:
>>
>> https://wiki.ubuntu.com/ConnMan/Debugging
>
> I'll test the latest daily and read the above link, and should this bug
> persist I'll attempt to provide more pertinent information as soon as
> practicable.

Thanks. Please note that syslog might contain something confidential,
like passwords, so please be careful when uploading them.

--
Kalle Valo

I haven't encountered this bug in quite a while, so I'm going to go ahead and mark this as fixed.