#9059 NORM Not Tri: 2569 (NM 0.7) nm-tool incorrectly reports state: disconnected

[Zarro Boogs per Child]

#9059: 2569 (NM 0.7) nm-tool incorrectly reports state: disconnected
------------------------------------+---------------------------------------
           Reporter:  mikus         |       Owner:                                   
               Type:  defect        |      Status:  reopened                         
           Priority:  normal        |   Milestone:  Not Triaged                      
          Component:  not assigned  |     Version:  Development build as of this date
         Resolution:                |    Keywords:                                   
        Next_action:  never set     |    Verified:  0                                
Deployment_affected:                |   Blockedby:                                   
           Blocking:                |  
------------------------------------+---------------------------------------
Changes (by mikus):

  * status:  closed => reopened
  * resolution:  invalid =>


Comment:

 Replying to [comment:1 cjb]:
 > nm-tool finds out the state of the connection by asking NetworkManager.
 (So, if you've bypassed NetworkManager, it's unsurprising that it doesn't
 know what the state is.)

 [[BR]]Please believe me that nm-tool is reporting incorrectly

 I deliberately posted this ticket from a system whose connection was
 working for me.  I am now enclosing information taken right after the
 system booted - without me having intervened.  The results are the same --
 nm-tool incorrectly reports the state

 Note:  In both sets of reports, the Network Manager process *is* running.
 Also note:  On 767 in the same situation as my initial report, nm-tool
 does not say 'disconnected'.

-- 
Ticket URL: <http://dev.laptop.org/ticket/9059#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system