Remuco Totem plugin error

[GoogleCodeExporter]

What is your environment?
* OS: Ubuntu 9.10
* Remuco version: 0.9.1.1
* Client device: Nokia 6131
* Player: Totem

Hi there!
Actually the plugin works really good, but I've got one error when I
enqueue files from the filebrowser of the client application. Totem hangs
for a couple of seconds (about 20), music / video is still playing but all
the controls / interface freeze. After the delay it continues to work
without any problem until I repeat queuing a file...
On console I get following error message:

(totem:2032): Unique-DBus-WARNING **: Error while sending message: 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.

I'm on Ubuntu 9.10 using remuco version 0.9.1.1 (ubuntu packages) and the
same client version on a Nokia 6131.

Thanks!

Original issue reported on code.google.com by andylem...@googlemail.com on 5 Nov 2009 at 9:04

[GoogleCodeExporter]

Though the Totem adapter is a plugin for Totem, it uses the command line call 
"totem
--enqueue" to enqueue files in Totem. This call, in turn, uses DBus to talk to 
the
Totem process, and here occurs the problem you reported. You can check this 
yourself
by running:
$ totem --enqueue <file>
If my guess is right, that should cause the same error.

The reason probably is that DBus is either not running or set up properly. In 
general
you need a running X session to have DBus working. If you run
$ env | grep DBUS
you should see a line like
> DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-...,guid=...

If you don't see this line (though you should on typical desktop linux 
systems), you
can start a DBus session bus manually, with:
$ eval ‘dbus-launch --sh-syntax --exit-with-session‘
$ echo $DBUS_SESSION_BUS_ADDRESS"

If you start Totem afterwards in the same shell, the error should be gone.

Original comment by obensonne@googlemail.com on 6 Nov 2009 at 10:08

• Changed state: Chatting
• Added labels: Component-Totem

[GoogleCodeExporter]

Nope your guess was not right, the error ONLY occurs when I enqueue a file(s) 
from my
mobile phone.
$ env | grep DBUS gives me:
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-hCydkjKTFF,guid=...  ->looks 
good..

It also would have surprised me if dbus would not work properly as there are 
many
other programs which use it.

Original comment by andylem...@googlemail.com on 6 Nov 2009 at 10:20

[GoogleCodeExporter]

I'll try to reproduce this in a karmic box as soon as possible.

Original comment by obensonne@googlemail.com on 7 Nov 2009 at 1:07

[GoogleCodeExporter]

This issue was closed by revision cbb1de8d56.

Original comment by obensonne@googlemail.com on 11 Nov 2009 at 11:31

• Changed state: Fixed