[Bugs] #1546 UNSP: migrating large data store causes DBus timeout

Sugar Labs Bugs bugtracker-noreply at sugarlabs.org
Tue Nov 10 16:07:20 EST 2009


#1546: migrating large data store causes DBus timeout
------------------------------------------+---------------------------------
    Reporter:  sascha_silbe               |          Owner:  tomeu                      
        Type:  defect                     |         Status:  new                        
    Priority:  Unspecified by Maintainer  |      Milestone:  Unspecified by Release Team
   Component:  sugar-datastore            |        Version:  Git as of bugdate          
    Severity:  Major                      |       Keywords:                             
Distribution:  Unspecified                |   Status_field:  New                        
------------------------------------------+---------------------------------
 Migrating a large data store (from v0 to v2 or for the version support
 branch v0/v1/v2 to v3) causes a DBus timeout because migration happens
 during activation (i.e. after sugar-datastore has been sent a DBus message
 and the sender is waiting for a reply).
 Since Sugar doesn't start up properly (Journal not shown, uncolored
 entries in home view) users might be tempted to restart Sugar right away
 (especially on XO-1s that don't give any indication of "disk" activity). I
 haven't tried what happens in that case, but two data store instances both
 doing migration is quite likely and the outcome might very well be a data
 store broken beyond repair.

 {{{
 1257886897.213287 DEBUG root: STARTUP: Loading the journal
 1257886922.372650 ERROR dbus.proxies: Introspect error on
 :1.7:/org/laptop/sugar/DataStore2: dbus.exceptions.DBusException:
 org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
 causes include: the remote application did not send a reply, the message
 bus security policy blocked the reply, the reply timeout expired, or the
 network connection was broken.
 1257886922.373063 DEBUG dbus.proxies: Executing introspect queue due to
 error
 Traceback (most recent call last):
   File "/home/sascha.silbe/sugar-jhbuild/install/bin/sugar-session", line
 125, in setup_journal_cb
     journalactivity.start()
   File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.5/site-
 packages/jarabe/journal/journalactivity.py", line 353, in start
     get_journal()
   File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.5/site-
 packages/jarabe/journal/journalactivity.py", line 348, in get_journal
     _journal = JournalActivity()
   File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.5/site-
 packages/jarabe/journal/journalactivity.py", line 118, in __init__
     self._setup_main_view()
   File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.5/site-
 packages/jarabe/journal/journalactivity.py", line 152, in _setup_main_view
     self._main_toolbox = MainToolbox()
   File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.5/site-
 packages/jarabe/journal/journaltoolbox.py", line 65, in __init__
     self.search_toolbar = SearchToolbar()
   File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.5/site-
 packages/jarabe/journal/journaltoolbox.py", line 120, in __init__
     self.refresh_filters()
   File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.5/site-
 packages/jarabe/journal/journaltoolbox.py", line 295, in refresh_filters
     for service_name in model.get_unique_values('activity'):
   File "/home/sascha.silbe/sugar-jhbuild/install/lib/python2.5/site-
 packages/jarabe/journal/model.py", line 474, in get_unique_values
     return _get_datastore().find_unique_values(dbus.Dictionary({},
 signature='sv'), key)
   File "/usr/lib/pymodules/python2.5/dbus/proxies.py", line 68, in
 __call__
     return self._proxy_method(*args, **keywords)
   File "/usr/lib/pymodules/python2.5/dbus/proxies.py", line 140, in
 __call__
     **keywords)
   File "/usr/lib/pymodules/python2.5/dbus/connection.py", line 622, in
 call_blocking
     message, timeout)
 dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not
 receive a reply. Possible causes include: the remote application did not
 send a reply, the message bus security policy blocked the reply, the reply
 timeout expired, or the network connection was broken.
 }}}

-- 
Ticket URL: <http://bugs.sugarlabs.org/ticket/1546>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system


More information about the Bugs mailing list