connman waits some minutes before scanning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
wpasupplicant (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: connman
When I boot the system and log in, connman does not immediately scan the wifi network looking for access points. Instead, it waits some minutes.
To workaround the problem, I've downloaded the source using "apt-get source connman" and launched the script test/start-
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: connman 0.55-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-
NonfreeKernelMo
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Wed Feb 16 19:43:46 2011
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
IpRoute:
192.168.1.1 dev eth1 scope link
192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.7
default via 192.168.1.1 dev eth1
MachineType: Dell Inc. Vostro 3500
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: connman
dmi.bios.date: 10/25/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0G2R51
dmi.board.vendor: Dell Inc.
dmi.board.version: A10
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Vostro 3500
dmi.product.
dmi.sys.vendor: Dell Inc.
affects: | connman (Ubuntu) → wpasupplicant (Ubuntu) |
Andrea Corbellini <email address hidden> writes:
> When I boot the system and log in, connman does not immediately scan the scanning, just after
> wifi network looking for access points. Instead, it waits some minutes.
>
> To workaround the problem, I've downloaded the source using "apt-get
> source connman" and launched the script test/start-
> the log in. The access points are found after just a few seconds.
Btw, if you use indicator-network you can just run 'cmcc scan' to
trigger a scan.
> NonfreeKernelMo dules: wl
This is a bug in the wl driver you are using, the first scan always
fails. As the driver is proprietary we can't fix it. But there's a
workaround for wpasupplicant, see bug #638303 for more.
--
Kalle Valo