Rhythmbox stops playing when resizing any window

Thank you for your bug. Do you have any error printed on the command line if you run rhythmbox there? Does "rhythmbox -d" has any error about it?

Doesn't seem so : Here is what "rhythmbox -d" looks like while I
reproduce the bug : stopping at 23:05:28

(23:05:25) [0x61cc90] [rb_metadata_load] rb-metadata-gst.c:1091: element
state changing asynchronously: 2, 2
(23:05:26) [0x61cc90] [rb_metadata_load] rb-metadata-gst.c:1091: element
state changing asynchronously: 2, 2
(23:05:27) [0x61cc90] [rb_metadata_load] rb-metadata-gst.c:1097: failed
to go to PAUSED for
file:///media/samae/Musique/After%20Forever/Invisible%20Circles/Invisible%20Circles.m3u
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:936:
message of type 512
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:936:
message of type 64
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:936:
message of type 64
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:936:
message of type 64
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:936:
message of type 64
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:936:
message of type 64
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:936:
message of type 64
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:905:
caught error: Le flux est d'un type différent de celui supporté par cet
élément.
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:936:
message of type 64
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:936:
message of type 64
(23:05:27) [0x61cc90] [rb_metadata_bus_handler] rb-metadata-gst.c:903:
caught error: Erreur de données de flux interne., but we've already got one
(23:05:27) [0x61cc90] [rb_metadata_dbus_load]
rb-metadata-dbus-service.c:121: metadata error: Le flux est d'un type
différent de celui supporté par cet élément.
(23:05:27) [0x61cc90] [_send_error] rb-metadata-dbus-service.c:68:
attempting to return error: Le flux est d'un type différent de celui
supporté par cet élément.
(23:05:27) [0x17585b0] [action_thread_main] rhythmdb.c:2312: executing
RHYTHMDB_ACTION_LOAD for
"file:///media/samae/Musique/After%20Forever/Remagine/Black%20Emule.url"
(23:05:27) [0x61cc90] [_handle_message] rb-metadata-dbus-service.c:322:
handling metadata service message
(23:05:27) [0x61cc90] [rb_metadata_dbus_ping]
rb-metadata-dbus-service.c:279: ping
(23:05:27) [0x17585b0] [rb_metadata_load] rb-metadata-dbus-client.c:377:
sending metadata load request
(23:05:27) [0x61cc90] [_handle_message] rb-metadata-dbus-service.c:322:
handling metadata service message
(23:05:27) [0x61cc90] [rb_metadata_dbus_load]
rb-metadata-dbus-service.c:115: loading metadata from
file:///media/samae/Musique/After%20Forever/Remagine/Black%20Emule.url
(23:05:27) [0x61cc90] [rb_metadata_load] rb-metadata-gst.c:1006: loading
metadata for uri:
file:///media/samae/Musique/After%20Forever/Remagine/Black%20Emule.url
(23:05:27) [0x61cc90] [rb_metadata_load] rb-metadata-gst.c:1083: going
to PAUSED for metadata, uri:
file:///media/samae/Musique/After%20Forever/Remagine/Black%20Emule.url
(23:05:27) [0x61cc90] [rb_metadata_gst_typefind_cb]
rb-metadata-gst.c:775: found type text/plain
(23:05:27) [0x61cc90] [rb_metadata_load] rb-metadata-gst.c:1091: element
state changing asynch...

marking unconfirmed, looks like something weird is happening on your box, it's not happening to everybody so the bug is low importance, it might take some time before somebody can work on it

I guess I should reinstall feisty :)

Sebastien Bacher a écrit :
> marking unconfirmed, looks like something weird is happening on your
> box, it's not happening to everybody so the bug is low importance, it
> might take some time before somebody can work on it
>
> ** Changed in: rhythmbox (Ubuntu)
> Status: Needs Info => Unconfirmed
>

reinstalling the same software is not likely to make a difference, the code will be the same

The difference will be that I'll face a fresh install of my ubuntu :)
The one I have now has been upgraded from warty ! I guess so errors
sliped into the code when the software grew ...

Sebastien Bacher a écrit :
> reinstalling the same software is not likely to make a difference, the
> code will be the same
>

Hey I'm facing a :

(10:45:43) [0x61cc90] [rb_metadata_load] rb-metadata-gst.c:1091: element
state changing asynchronously: 2, 2

In rhythmbox and it prevent me to edit the ID tag of the song. Is it
normal ?

> Sebastien Bacher a écrit :
> reinstalling the same software is not likely to make a difference, the
> code will be the same
>

editing an ID tag seems to be a different topic. The package are binary, they are identical if you update from warty or install a new feisty, what change is what packages are installed and maybe your user configuration (if you don't keep it after reinstallation)

I solved that problem :)
I use quod libet instead. Thanks for your answers

Sebastien Bacher a écrit :
> editing an ID tag seems to be a different topic. The package are binary,
> they are identical if you update from warty or install a new feisty,
> what change is what packages are installed and maybe your user
> configuration (if you don't keep it after reinstallation)
>

how using quot libet fixes it?

Well it doesn't fix it, properly speaking, but insures me that the sound
wont stop will resizing one on my window.

:)

Sebastien Bacher a écrit :
> how using quot libet fixes it?
>

Do you still get the bug?

Yes, it still happens.
But know I use Ex Falso / Quod Libet and I have nothing to complain about.
When I resize rythmbox, it the whole system clock which stops and then I
loose some seconds everytime I reproduce the bug...

Sebastien Bacher a écrit :
> Do you still get the bug?
>

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducable with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Closing this report for now, feel free to re open it if you may test it in Gutsy Gibbon.