[Bugs] #3119 UNSP: traceback after Sugar startup

[Sugar Labs Bugs]

#3119: traceback after Sugar startup
------------------------------------------+---------------------------------
    Reporter:  erikos                     |          Owner:  erikos              
        Type:  defect                     |         Status:  new                 
    Priority:  Unspecified by Maintainer  |      Milestone:  0.94                
   Component:  sugar                      |        Version:  0.93.x              
    Severity:  Major                      |       Keywords:  11.3.0 collaboration
Distribution:  Unspecified                |   Status_field:  New                 
------------------------------------------+---------------------------------

Comment(by erikos):

 In neighborhood.py we have the same issue.

 {{{
 diff --git a/src/jarabe/model/neighborhood.py
 b/src/jarabe/model/neighborhood.py
 index 828cb14..efbc695 100644
 --- a/src/jarabe/model/neighborhood.py
 +++ b/src/jarabe/model/neighborhood.py
 @@ -159,6 +159,10 @@ class ActivityModel(gobject.GObject):
      current_buddies = gobject.property(type=object,
 getter=get_current_buddies)

  class _Account(gobject.GObject):
      __gsignals__ = {
          'activity-added': (gobject.SIGNAL_RUN_FIRST, gobject.TYPE_NONE,
 @@ -251,7 +255,12 @@ class _Account(gobject.GObject):
              self._check_registration_error()
              self._connection = None
          elif self._connection is None:
 -            self._prepare_connection(properties['Connection'])
 +            if 'ConnectionStatus' not in properties:
 +                return
 +            if properties['ConnectionStatus'] ==
 CONNECTION_STATUS_CONNECTED:
 +                self._prepare_connection(properties['Connection'])
 }}}

 We can solve this by checking if the connection has been established
 already.

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/3119#comment:3>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system