miro.real crashed with DBusException in call_blocking()

[Donc]

Binary package hint: miro

Installed miro from synaptic, x64 architecture, miro crashed on startup

ProblemType: Crash
Architecture: amd64
Date: Wed Sep 26 20:02:29 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/miro.real
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: hsfengine
Package: miro 0.9.8.1-0ubuntu3
PackageArchitecture: amd64
ProcCmdline: /usr/bin/python2.5 /usr/bin/miro.real
ProcCwd: /home/djci
ProcEnviron:
 PATH=/home/djci/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/miro.real']
SourcePackage: miro
Title: miro.real crashed with DBusException in call_blocking()
Uname: Linux apollo 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux

[Chris Halse Rogers (raof)]

Can you reproduce this problem? It seems that you don't have a DBUS session bus running - what desktop (Ubuntu/Gnome, Kubuntu/KDE, Xubuntu/XFCE) are you using?

Although this is a problem in Miro, it seems to stem from a more systemic problem with your setup.

[Lafa (luis-alves)]

I also got it, in a 32 bit install of gutsy with the latest updates 10/12/2007
/
lafa@shuttle:~$ 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 address hidden>.

  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.

[Nizar Kerkeni (nizarus)]

same bug in hardy 64
result while lanching miro from command line :
~$ miro
/usr/lib/firefox
before 3
INFO Starting up Miro
INFO Version: 1.0
INFO Revision: unknown
INFO Builder: buildd@vernadsky
INFO Build Time: 1197365180.86
INFO Loading preferences...
INFO Starting event loop thread
INFO Restoring database...
INFO Connecting to /home/kerkeni/.miro/sqlitedb
TIMING Database load slow: 1.754
TIMING idle (Initializing database) too slow (1.892 secs)
INFO Spawning auto downloader...
INFO Spawning idle notifier
INFO idle notifier running
INFO Displaying main frame...
INFO *** Launching Downloader Daemon ****
INFO Creating video display...
WARNING Menu item action "RenameVideo" not implemented
WARNING Menu item action "FastForward" not implemented
WARNING Menu item action "Rewind" not implemented
WARNING Menu item action "UpVolume" not implemented
WARNING Menu item action "DownVolume" not implemented
INFO loaded renderer 'xinerenderer'
TIMING gtkAsyncMethod: <function initRenderers at 0x154d9b0> took too long: 1.469
TIMING gtkSyncMethod: <function getDisplay at 0x15cf6e0> took too long: 1.626
INFO First URL is https://www.miroguide.com/
WARNING Error setting up HTTP observer
Segmentation fault (core dumped)

[oto (otovon)]

Same problem as Nizar K for me.
I had no problem on gutsy, and since I upgraded to hardy, I get this segfault

[Richard Paul (richard-a-paul)]

I'm also getting the same problem as Nizar K on hardy.

[Chris Halse Rogers (raof)]

Oto, Richard Paul, Nizar K: You're seeing a different problem. Please file a new bug, preferably with the apport backtrace you should be able to find in /var/crash.

As yet, no one has answered my original question: What desktop environment are you using? (Gnome, KDE, XFCE)

[Joncohen (electrawise)]

Same for me two. It tends to crash less if you reduce the number of links on miro.

[FredBezies (fredbezies-deactivatedaccount)]

Miro seems to be broken on every single python update. This is kinda annoying.

[Bryce Harrington (bryce)]

Anyone still seeing this error? I'm not able to reproduce it on Lucid.

[Bryce Harrington (bryce)]

I'm going to go ahead and assume this is long since resolved. Donc if you're still seeing this error on Lucid please reopen with any additional detail you can provide.