Rhythmbox crashes while playing (Edgy)

[Marc Nieper-Wißkirchen]

When manually starting Rhythmbox from the console afterwards, nothing happens, i.e. the program hangs without showing any output.

pkill-ing rhythmbox doesn't help either.

Calling rhythmbox-client however does work.

[Sebastien Bacher (seb128)]

Thanks for your bug. That looks like a dbus issue. Do you still have the issue after restarting dbus (/etc/init.d/dbus restart) by example?

[Marc Nieper-Wißkirchen (marc-nieper-wisskirchen)]

2006/10/24, Sebastien Bacher <email address hidden>:
>
> Thanks for your bug. That looks like a dbus issue. Do you still have the
> issue after restarting dbus (/etc/init.d/dbus restart) by example?

As the error has only occured sporadically, I cannot tell at the moment.
However, I'll try to restart dbus, once the error occurs again.

By the way, another issue I had with Rhythmbox was that one couldn't import
music folders that were mount points of logical volumes. This was with the
Dapper-version. I haven't checked whether the problem occurs with the Edgy
version as well.

Best,

Marc

[Daniel Holbach (dholbach)]

Please report the other issue as another bug report. Thanks a lot - it makes it easier to follow up.

[mon (javiermon-deactivatedaccount)]

I think this happens on my edgy box aswell

attached crash report

[Sebastien Bacher (seb128)]

kmon, your bug seems to be a different one

[Carlos Flores (cafg10)]

It has happenined to me too, here is my crash report

[Thomas Jagoditsch (tja)]

crashes here too while playing.

[Sebastien Bacher (seb128)]

Carlos, Thomas, we appreciate your participation, could you open new bugs when you are not use of what you are doing instead of commenting on some other random bug though? Your crashes are different from that bug and are not being useful on that page

[Sebastien Bacher (seb128)]

Crash to dbus-glib:

#0 0xb7bdd6cc in dbus_g_method_return_error (context=0x0, error=0x847278c) at dbus-gobject.c:1996
1996 {
(gdb) bt
#0 0xb7bdd6cc in dbus_g_method_return_error (context=0x0, error=0x847278c) at dbus-gobject.c:1996
#1 0xb701e53e in IA__g_slist_find_custom (list=0x8667da0, data=0x847278c, func=0xb7bdd6b0 <dbus_g_method_return+782>)
    at gslist.c:389
#2 0xb7be1acc in dbus_g_proxy_set_interface (proxy=0x81ee830, interface_name=0x8472428 "\001") at dbus-gproxy.c:2036
#3 0xb7b868ce in dbus_connection_dispatch (connection=0x8667da0) at dbus-connection.c:3779
#4 0xb7bd951d in watch_toggled (watch=0x81f0268, data=0x0) at dbus-gmain.c:455
#5 0xb7006802 in IA__g_main_context_dispatch (context=0x81c9aa0) at gmain.c:2045
#6 0xb70097df in g_main_context_iterate (context=0x81c9aa0, block=1, dispatch=1, self=0x81626a8) at gmain.c:2677
#7 0xb7009b89 in IA__g_main_loop_run (loop=0x816b1d0) at gmain.c:2881
#8 0xb773d574 in IA__gtk_main () at gtkmain.c:1024
#9 0x0806bccf in main (argc=1, argv=0xbfe255e4) at main.c:381

[Sebastian Dröge (slomo)]

Should probably confirmed... there was even a duplicate of this one already.