I also got it, in a 32 bit install of gutsy with the latest updates 10/12/2007
/
[EMAIL PROTECTED]:~$ miro
/var/lib/python-support/python2.5/dbus_bindings.py:1: DeprecationWarning: The
dbus_bindings module is not public API and will go away soon.
Most uses of dbus_bindings are applications catching the exception
dbus.dbus_bindings.DBusException. You should use dbus.DBusException
instead (this is compatible with all dbus-python versions since 0.40.2).
If you need additional public API, please contact the maintainers via
<[EMAIL PROTECTED]>.
from dbus.dbus_bindings import *
ERROR:dbus.proxies:Introspect error on
:1.1:/org/participatoryculture/dtv/OneTime: 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.
Traceback (most recent call last):
File "/usr/bin/miro.real", line 102, in <module>
iface.HandleArgs(dbusargs)
File "/var/lib/python-support/python2.5/dbus/proxies.py", line 63, in __call__
return self._proxy_method(*args, **keywords)
File "/var/lib/python-support/python2.5/dbus/proxies.py", line 135, in
__call__
**keywords)
File "/var/lib/python-support/python2.5/dbus/connection.py", line 603, 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.
--
miro.real crashed with DBusException in call_blocking()
https://bugs.launchpad.net/bugs/145413
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs