Bug 10207 - "Select connection" window don't show any connections
: "Select connection" window don't show any connections
Status: RESOLVED WORKSFORME
Product: Connectivity
ICD
: 5.0/(3.2010.02-8)
: All Maemo
: Unspecified normal (vote)
: ---
Assigned To: unassigned
: icd-bugs
:
:
:
:
  Show dependency tree
 
Reported: 2010-05-19 16:03 UTC by Kimmo Ahola
Modified: 2011-11-04 16:00 UTC (History)
1 user (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Kimmo Ahola (reporter) 2010-05-19 16:03:10 UTC
SOFTWARE VERSION:
3.2010.02-8

EXACT STEPS LEADING TO PROBLEM: 
(Explain in detail what you do (e.g. tap on OK) and what you see (e.g. message
Connection Failed appears))
1. Tap "Internet Connection" from status bar.

EXPECTED OUTCOME:
"Select Connection" window opens and I can see all the neighbor WLAN access
points and cellular operators GPRS service name.

ACTUAL OUTCOME:
"Select Connection" window opens. First time it will try to find networks
(spinning logo), after that only says "No connection available".

REPRODUCIBILITY:
(always, less than 1/10, 5/10, 9/10)
Current situation: always

EXTRA SOFTWARE INSTALLED:
vpnc and vpngui

OTHER COMMENTS:

The "Select Connection" window was working without problems, but after one day
it stays blank. If I remember correctly, that happened after VPN (vpnc)
connection died (very quick yellow label flashed up in the display, didn't
catch the message).

Now I can start the Internet connection by using the WLAN or GPRS interface by
using the dbus-send command (http://wiki.maemo.org/Phone_control#Networking). I
can see the cellular GPRS connection information and WLAN APs from Settings ->
Internet Connections -> Connections (and from
/var/lib/gconf/system/osso/connectivity/IAP/ directory).

I don't know if this behavior is normal, but right now icd2 looks like to be
restarted when "Internet Connection" is pushed:
----
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: Received
com.nokia.icd2.select_req (u) request
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: tracking
info sender ':1.56' and message (nil) added to request 0x3a160
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: requesting
request 0x3a160, attr 1, (null)/0/(null),(null)/0/[ASK]
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: running
module 'libicd_policy_merge.so' new_request policy
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: running
module 'libicd_policy_ask.so' new_request policy
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: Requesting
'Select connection' dialog
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: policy iap
ask pending returned
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: 'Select
connection' dialog responded (2)
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: policy
returned ICD_POLICY_WAITING for request 0x3a160
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: request
0x3a160 is waiting for actions
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: request
0x3a160 with status ICD_REQUEST_WAITING
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: Received
com.nokia.icd2.scan_req (u) request
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: scan start
for type 'DUMMY'
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2572]: '[SCAN]'
type 'DUMMY' ICD_STATUS_CHANGED_SIG with status SCAN_START, '' sent to '(null)'
May 19 16:00:41 Nokia-N900-42-11 waitdbus[2607]: trying to connect to the
system bus
May 19 16:00:41 Nokia-N900-42-11 waitdbus[2607]: got connection
May 19 16:00:41 Nokia-N900-42-11 icd2 0.87+fremantle6.1+0m5[2608]: icd2 version
0.87+fremantle6.1+0m5 starting
----
Comment 1 Kimmo Ahola (reporter) 2010-05-19 16:55:37 UTC
The problem was solved by removing all IAPs from
/var/lib/gconf/system/osso/connectivity/IAP directory and rebooting the device.
So looks like some of IAPs %gconf.xml file was corrupted.
Comment 2 Andre Klapper maemo.org 2010-05-19 17:02:14 UTC
(No codefix included, hence resetting resolution)
Comment 3 Erik Nygren 2011-11-04 16:00:52 UTC
I also encountered this problem.  It may be worthwhile to make this more robust
to corrupted files in that directory.  (Tracking down this bug as the root
cause took quite awhile.)