Rhythmbox: Error while saving song information. Internal data stream error.

[Akaname]

Binary package hint: rhythmbox

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.12.8-0ubuntu4
Uname: Linux 2.6.34-020634rc6-generic #020634rc6 SMP Fri Apr 30 10:09:34 UTC 2010 i686 GNU/Linux

When trying to save song information for ogg vorbis files in Rhythmbox I get the following error message (after a few seconds):
"Error while saving song information. Internal data stream error."

The ogg vorbis files and their parent directories are on local hard drives and have existing write permissions.
They are originally encoded with oggenc and tagged with vorbiscomment. All play nicely within Rhythmbox. All other tag editors work without problems.

This makes Rhythmbox unusable for editing ogg vorbis files. Other file formats not tested.

I hope that there's a solution for all those different tagging problems within Rhythmbox (like mentioned in other bug reports).

Thanks for your work!

[Akaname (akaname)]

If I disable "Watch my library for new files" in Rhythmbox preferences, the problem is raised less frequently. It seems to have something to do with collection size and filesystem activity, like mentioned in https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/123460 .

Ok, not everybody has a collection of 20000 songs. But as Rhythmbox is the default music player in Ubuntu and Ubuntu is used by more and more people this problem should become present to more and more people, too.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better, however the report is missing some information, may you please run rhythmbox as: rhythmbox --debug &> rhythmbox-debug.txt ; perform the steps to reproduce the bug and attach that resulting log file to the report? Thanks in advance!.

[Akaname (akaname)]

I already did this. The log is attached to my second post.

[Jeff (jdorenbush)]

I'm having the same problem in Rhythmbox 0.13.1 (Lucid)

[Akaname (akaname)]

For me the problem seems to exist only on single-core machines. I never saw this on multi-core machines.

[Akaname (akaname)]

It seems like rhythmbox damages the files while causing "error while saving song information". After a fresh install of Ubuntu Maverick with Rhythmbox 0.13.1 on a new multicore laptop I experienced the same bug again on a freshly oggenc-encoded .oga file.

After that I checked the file playback. It played in rhythmbox, but it failed in totem.

So I checked the freshly encoded file with ogginfo:

ogginfo /home/suu/srv/music/repositories/1/items/1021/13.oga
Processing file "/home/suu/srv/music/repositories/1/items/1021/13.oga"...

New logical stream (#1, serial: 6e46d358): type vorbis
Vorbis headers parsed for stream 1, information follows...
Version: 0
Vendor: Xiph.Org libVorbis I 20090709
Channels: 2
Rate: 44100

Nominal bitrate: 192.000000 kb/s
Upper bitrate not set
Lower bitrate not set
User comments section follows...
 GENRE=soul
 ALBUM=Various: 100 Hits. Soul (Disc 2 of 5)
 TRACKNUMBER=13
 TITLE=Ain't No Sunshine
 ARTIST=Bill Withers
 DATE=2007-01-01
 REPLAYGAIN_REFERENCE_LOUDNESS=89.000000
 REPLAYGAIN_TRACK_GAIN=-4.770000
 REPLAYGAIN_TRACK_PEAK=0.926666
 REPLAYGAIN_ALBUM_GAIN=-4.770000
 REPLAYGAIN_ALBUM_PEAK=0.926666
WARNING: sequence number gap in stream 1. Got page 3 when expecting page 2. Indicates missing data.
WARNING: discontinuity in stream (1)
Negative or zero granulepos (0) on Vorbis stream outside of headers. This file was created by a buggy encoder
Vorbis stream 1:
 Total data length: 2906480 bytes
 Playback length: 2m:04.333s
 Average bitrate: 187.012118 kb/s
Logical stream 1 ended

All other freshly encoded files were ok. After checking my complete collection of 20000+ .oga songs with ogginfo i found 5 old defect files. They all were playable in rhythmbox, failed to play in totem and showed the same errors in ogginfo.

[Akaname (akaname)]

By the way I've got the original 20000+ .oga files on a file server within their original state after creation. They all were created 6 months ago via flac / metaflac --add-replay-gain / oggenc. As precaution no editings after that. I learned from previous tagging bugs of amarok several years ago, that damaged hundreds of songs.

I checked the original files with ogginfo: The original files are *not* damaged.

The local copies on laptop only were played and edited in rhythmbox. No other tagging softwares.

[Akaname (akaname)]

As an experiment I tagged 55 undamaged .oga files with rhythmbox, got only one error message and 55 damaged .oga files. This, as mentioned before, only happens when rhythmbox's music library contains a big number of files (in my case now 20000+), not with only a few hundred files.

Rhythmbox's tagging concept should be radically changed.

[Walter Garcia-Fontes (walter-garcia)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

[Launchpad Janitor (janitor)]

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]