Public bug reported:

Binary package hint: rhythmbox
I'm not completely sure what's going on... I've noticed when I click on the 
Rhythmbox icon in my launcher, it seems to do all the loading, but does not 
bring up Rhythmbox.  When I click on the icon again, it pops up fairly quickly.
So I ran it from the command line first this time, and it gave me this:

Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/PIL/__init__.py", line 38, in activate
    
  File "/var/lib/python-support/python2.5/dbus/bus.py", line 151, in 
add_signal_receiver
    path, **keywords)
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 382, in 
add_signal_receiver
    self._require_main_loop()
RuntimeError: To make asynchronous calls, receive signals or export objects, 
D-Bus connections must be attached to a main loop by passing mainloop=... to 
the constructor or calling dbus.set_default_main_loop(...)

(rhythmbox:6144): GLib-GObject-WARNING **: Two different plugins tried
to register 'ArtDisplayPlugin+RBPythonPlugin'.

(rhythmbox:6144): Rhythmbox-CRITICAL **: rb_plugin_activate: assertion
`RB_IS_PLUGIN (plugin)' failed

Running rhythmbox in a different command line immediately went to
another prompt, but the program came up like it does from the launcher.

** Affects: rhythmbox (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Rhythmbox has errors and won't open with first command
https://bugs.launchpad.net/bugs/288394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to