Connman-0.67 Crashes and/or Hangs on Start-up
marathon96 at gmail.com
Sun Jan 30 15:11:46 PST 2011
On 1/30/11 2:46 PM, Samuel Ortiz wrote:
> On Sun, Jan 30, 2011 at 01:37:30PM -0800, Grant Erickson wrote:
>> The requested log output is as follows. It would seem that the wifi.so
>> plug-in and the wpa_supplicant are not even communicating:
>> # /sbin/wpa_supplicant -ddd -t -u &
>> 1296422968.146540: Providing DBus service 'fi.epitest.hostap.WPASupplicant'.
> Your wpa_supplicant is built to only provide the legacy D-Bus interface, which
> is why the wifi.so plugin doesn't talk to it.
> I don't know if you build your wpa_supplicant yourself, but you can build it
> so that it supports both interfaces. (which is why I was asking for your
> wpa_supplicant .config file, i.e. the build config file wpa_supplicant uses).
Thanks for the clarification on which '.config' file was intended. I do
build wpa_supplicant from source, the .config for which is:
DBUS_INCLUDE := $(DBUSCFLAGS)
DBUS_LIBS := $(DBUSLDFLAGS)
DBUS_VERSION := $(DBUSVERSION)
CFLAGS += $(OPENSSLCFLAGS) $(NETLINKCFLAGS) $(LINUXCFLAGS)
wpa_supplicant: LIBS += $(DBUSLDFLAGS) $(OPENSSLLDFLAGS)
wpa_passphrase: LDFLAGS += $(OPENSSLLDFLAGS)
When last I'd tried setting CONFIG_CTRL_IFACE_DBUS_NEW=y around the
connman-0.63 time frame, it caused wpa_supplicant to segment fault so I
turned it off as it didn't seem necessary.
I'll give it another go with connman-0.68 and the non-legacy wifi.so and see
Thanks for the tip. Would it make sense, from a debugging perspective, to
have the Wi-Fi plug-in emit some log message if it cannot find the new D-Bus
More information about the connman