Robert: glad you try to tackle that, at last! ;-)

I've a few logs that can be interesting to you, with a file triggering this. 
See attached log excerpt, where you can find:
(09:57:12) [0x8cd1408] [rhythmdb_add_import_error_entry] rhythmdb.c:2148: 
adding import error for [FILE1]: Empty file
(09:57:12) [0x8cd1408] [rhythmdb_entry_new] rhythmdb.c:1613: emitting entry 
added
[...]
(09:57:12) [0xa01dc60] [rb_metadata_bus_handler] rb-metadata-gst.c:946: message 
of type state-changed from id3demux0
(09:57:12) [0xa01dc60] [rb_metadata_bus_handler] rb-metadata-gst.c:946: message 
of type state-changed from id3demux0
(09:57:12) [0xa01dc60] [rb_metadata_handle_missing_plugin_message] 
rb-metadata-gst.c:864: got missing-plugin message from decodebin: 
gstreamer|0.10|rhythmbox-metadata|ID3 tag demuxer|decoder-application/x-id3
(09:57:12) [0xa01dc60] [rb_metadata_bus_handler] rb-metadata-gst.c:884: got 
error message from decodebin
(09:57:12) [0xa01dc60] [rb_metadata_bus_handler] rb-metadata-gst.c:900: caught 
error: A ID3 tag demuxer plugin is required to play this stream, but not 
installed. 
(09:57:12) [0xa01dc60] [rb_metadata_load] rb-metadata-gst.c:1098: failed to go 
to PAUSED for [FILE2]
(09:57:12) [0xa01dc60] [rb_metadata_get_missing_plugins] 
rb-metadata-gst.c:1513: adding [gstreamer|0.10|rhythmbox-metadata|ID3 tag 
demuxer|decoder-application/x-id3,ID3 tag demuxer] to return data

So you can see that an empty MP3 file seems to trigger the problem, and
the other one is actually corrupt, only 2,1KB, and I cannot read ID3 tag
from it. I attached it too, that can be a useful testcase.

** Attachment added: "Part of RB log output"
   http://launchpadlibrarian.net/26058657/rb-error.log

-- 
Rhythmbox tries to find a codec for a m3u/html file
https://bugs.launchpad.net/bugs/343707
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in ubuntu.

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

Reply via email to