[sugar] odd dbus sugar error

[Marco Pesenti Gritti]

Marco Pesenti Gritti wrote:
> Dan Williams wrote:
>> Marco,
>>
>> I'm not seeing this after a rawhide update when clicking the 'Share'
>> button for a web activity:
>>
>> Traceback (most recent call last):
>>   File 
>> "/home/dcbw/Development/olpc/sugar-jhbuild/build/lib/python2.4/site-packages/sugar/logger.py", 
>> line 55, in _log
>>     self._messages, timeout = 1000)
>> TypeError: log() got an unexpected keyword argument 'timeout'
>>
>> Relevant code snippet is this:
>>
>>         self._console.log(self._console_id, self._levels,
>>                           self._messages, timeout = 1000)
>>
>> In this case, log() is a D-Bus method.  'timeout' should be a supported
>> keyword for the dbus python bindings.  However, it doesn't seem to be
>> getting picked up as a keyword argument through all the dbus python
>> binding __getattr__ magic.  I'll try to investigate more, wondering if
>> you had any ideas right away.
>>
>>   
>
> I checked in a fix. For the shell process we are actually using the 
> console object itself rather than the dbus service, so we can't pass 
> the timeout arg for that case.

There is actually still a dbus error... it doesn't stop things to work 
though.

Strange one... It looks like after I start an activity (and the activity 
send some messages to the console), the first message the presence 
service try to send to the console cause this traceback:

Traceback (most recent call last):
  File "/home/marco/sugar-jhbuild/source/sugar/sugar/logger.py", line 
58, in _log
    self._messages, timeout = 1000)
  File "/usr/lib/python2.4/site-packages/dbus/proxies.py", line 102, in 
__call__
    reply_message = self._connection.send_with_reply_and_block(message, 
timeout)
  File "dbus_bindings.pyx", line 455, in 
dbus_bindings.Connection.send_with_reply_and_block
DBusException: 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.

The method has been successfully invoked though, apparently. Also the 
subsequent invocations works fine.

Not sure what is going on, needs more investigation.

Marco