After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 633760 - iPod can't playback files written by rhythmbox
iPod can't playback files written by rhythmbox
Status: RESOLVED DUPLICATE of bug 625054
Product: rhythmbox
Classification: Other
Component: iPod
0.13.x
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-11-02 00:34 UTC by Rui Matos
Modified: 2010-11-09 18:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rui Matos 2010-11-02 00:34:02 UTC
I'm using Fedora 14's rhythmbox-0.13.1-1.fc14.x86_64.

I drag mp3 files into the iPod and all seems OK. Then I quit Rhythmbox and eject the iPod.

The iPod software does see the new files but when trying to play them it will skip them all as if they were 0 seconds long.

All files uploaded with a previous version of Rhythmbox (rhythmbox-0.12.6-5.fc12.i686) continue to work as usual.

I tried to upload these files with gtkpod and it worked OK which prompted me to see what was different. I discovered that gtkpod writes files with names like

./iPod_Control/Music/F01/libgpod288378.mp3

while Rhythmbox is writing files like

./iPod_Control/Music/F03/01 Louisiana

while on the previous version that worked (under Fedora 12) it wrote files like

./iPod_Control/Music/F00/01 - First Song.mp3

It seems the new version writes file names without the .mp3 extension. Maybe that's the cause of the problem?
Comment 1 Jonathan Matthew 2010-11-09 18:01:41 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 625054 ***