#6525 NORM Never A: Presence not re-established after connecting to network

[Zarro Boogs per Child]

#6525: Presence not re-established after connecting to network
-------------------------------+--------------------------------------------
  Reporter:  bert              |       Owner:  Collabora     
      Type:  defect            |      Status:  new           
  Priority:  normal            |   Milestone:  Never Assigned
 Component:  presence-service  |     Version:                
Resolution:                    |    Keywords:                
  Verified:  0                 |    Blocking:                
 Blockedby:                    |  
-------------------------------+--------------------------------------------

Comment(by gdesmott):

 {{{
 <smcv> the connection to the session bus fell over
 <smcv> not necessarily dbus-python's fault
 <smcv> it's a little ambuiguous
 <smcv> possibility 1: the python code got disconnected
 <smcv> possibility 2: the service being started via StartServiceByName
 disconnected/crashed before it replied to whatever message, and that
 exception is libdb
 <smcv> it's clear that *someone* got disconnected from the session bus,
 but it's not entirely clear whether it's P <---> dbus-daemon <-/-> S or P
 <-/-> dbus-daemon <---> S
 <smcv> where P is the python code that generated that traceback, and S is
 the service it's trying to startus (via dbus-python) telling us about it
 <smcv> can you reproduce it while running a dbus-monitor? it'd be
 interesting to see who falls off the bus first
 }}}

 so P is PS and S is Gabble.
 As said, it would be good to be able to reproduce this problem while dbus-
 monitor is running

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