Rhythmbox fails to launch when remuco-rhythmbox is installed

[GoogleCodeExporter]

What is your environment?
* OS: Ubuntu 9.10 Karmic
* Remuco version: 0.9.1.1+dfsg-1
* Client device: Sony Ericsson K800i (Not relevant)
* Player: Rhythmbox

What steps will reproduce the problem?
1. Install Rhythmbox
2. Install remuco-rhythmbox (other remuco-packages has no effect)
3. Launch Rythmbox

What is the expected behavior? What happens instead?
Rhythmbox is, of course, expected to start, in stead the panel where the
icon is going to appear flickers, and the mouse shows loading for ~10
seconds, then nothing.

Additional information:
It worked yesterday, but today, for some reason, it does not work with
remuco-rhythmbox installed.
All packages installed through synaptic from Ubuntu repos.

Original issue reported on code.google.com by mads...@gmail.com on 5 Oct 2009 at 9:45

[GoogleCodeExporter]

Same as issue 18 ? Note the last comments there and the duplicate issue 43.

Original comment by obensonne@googlemail.com on 5 Oct 2009 at 9:48

• Changed state: Incomplete

[GoogleCodeExporter]

It seems the problem only exists when the plugin is enabled in Rhythmbox. Also, 
after
re-installation of rythmbox "base" packages, rhythmbox works fine. After one or 
two
times _quiting_ Rythmbox, with remuco plugin enabled, the problem appears. The 
first
time I then try to start rb, some seconds of "waiting" on the mouse, then I try 
again
and it works. After quiting again, I try to launch, and now two faulty tries 
before
success. After disabling the plugin, the problem is sort of reset.

Also when rb does start, it seems to mess up the panels, because they flicker. 
Both
when starting rb and when quiting.

Original comment by mads...@gmail.com on 5 Oct 2009 at 9:59

[GoogleCodeExporter]

Sorry, Im not technical enough to see if it is the same problem... Here is the 
output
of terminal:
______________________________________
***@***-***:~$ rhythmbox
TypeError: Cannot create a consistent method resolution
order (MRO) for bases Buildable, GInterface, Orientable
**
ERROR:/build/buildd/pygobject-2.18.0/gobject/pygobject.c:924:pygobject_new_full:
assertion failed: (tp != NULL)
Aborted (core dumped)
______________________________________

From applications menu, it works sometimes, and does not other times. from 
terminal
it fails every time.

Original comment by mads...@gmail.com on 5 Oct 2009 at 10:07

[GoogleCodeExporter]

Looks like the same issue. You can do a simple check if yours is the same:

1) Enable the Python Console plugin in Rhythmbox
2) Open the Python Console (in the now visible Tools menu)
3) Type this:
   >>> s = shell.props.queue_source
   or this:
   >>> s= shell.get_player().props.source

If RB crashes here, than this it's the same problem as in issue 18, i.e. not a 
Remuco
bug. Finally Karmic is still beta, so we should see if this gets fixed by 
package
updates in the next days.

Original comment by obensonne@googlemail.com on 5 Oct 2009 at 10:30

• Added labels: Component-Rhythmbox

[GoogleCodeExporter]

It doesnt crash on either of those commands with both remuco and python console
pluging enabled.

Original comment by mads...@gmail.com on 6 Oct 2009 at 8:53

[GoogleCodeExporter]

I'll try to reproduce this in a Karmic VM as soon as possible.

May be related to https://bugzilla.gnome.org/show_bug.cgi?id=588133 .

Original comment by obensonne@googlemail.com on 6 Oct 2009 at 7:03

• Changed title: Rhythmbox fails to launch when remuco-rhythmbox is installed
• Changed state: Accepted

[GoogleCodeExporter]

Ok. Just let me know if you need any terminal outputs or anything. I was simply
impressed by the ease of use (and installation) and number of functions in 
remuco, so
I don't mind helping out at all.

Original comment by mads...@gmail.com on 6 Oct 2009 at 8:52

[GoogleCodeExporter]

I cannot reproduce this issue in a Karmic installation with all currently 
available
package updates. I started RB several times and used it together with Remuco 
for a while.

Do you still experience this issue after updating your packages? If yes, are 
you able
to provide reproducible step-by-step instructions for this issue?

Original comment by obensonne@googlemail.com on 10 Oct 2009 at 5:05

• Changed state: Incomplete

[GoogleCodeExporter]

I know that my system is not updated. I am afraid to breake it because of 
partial 
upgrades. I will post back here if the problem persists after all packages are 
updated. 
For now we can assume the problem is solved with some Karmic updates...

Original comment by mads...@gmail.com on 11 Oct 2009 at 1:21

[GoogleCodeExporter]

Not a bug, so far. Feel free to reopen when seeing this again.

Original comment by obensonne@googlemail.com on 12 Oct 2009 at 12:25

• Changed state: Invalid

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

On rhythmbox 0.12.6 inside Ubuntu Karmic, I get the same error when starting, 
and
rhythmbox immediately crashes. Removing remuco immediately resolves the problem.

---
TypeError: Cannot create a consistent method resolution
order (MRO) for bases Buildable, Orientable, ImplementorIface
**
ERROR:/build/buildd/pygobject-2.18.0/gobject/pygobject.c:924:pygobject_new_full:
assertion failed: (tp != NULL)
Aborted

Original comment by locke.db on 3 Mar 2010 at 4:48

[GoogleCodeExporter]

@locke.db:
Please check if your crash is similar to this one:
http://bugzilla.gnome.org/show_bug.cgi?id=580022

Original comment by obensonne@googlemail.com on 3 Mar 2010 at 4:58