Bug 440668 - Rhythmbox cannot transfer some files to VFAT iPods
Rhythmbox cannot transfer some files to VFAT iPods
Product: Fedora
Classification: Fedora
Component: rhythmbox (Show other bugs)
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Bastien Nocera
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-04-04 09:27 EDT by Brad Walker
Modified: 2008-04-04 09:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-04 09:42:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brad Walker 2008-04-04 09:27:10 EDT
Description of problem:
On Windows-formatted iPods, Rhythmbox cannot write songs with filenames that
violate VFAT naming conventions (no :, ?, etc.). Sometimes it writes them, but
only when RB truncates the invalid characters off the filename.

Rhythmbox won't transfer "02 Humoresque: City Montage.flac" with the colon near
the beginning.
Rhythmbox will transfer "06 Violin Sonata No. 1 in G minor, BWV 1001: IV.
Presto.flac" since it cuts off most of the end of the filename.

Version-Release number of selected component (if applicable):

How reproducible:
100% with a filename with an invalid character near the beginning.

Actual results:
Rhythmbox pops up a "cannot write file" error dialog.

Expected results:
Rhythmbox writes file without problems.

Additional info:
Rhythmbox has this in the GNOME bugzilla:
I'm writing this report because I'd like to see the patch attached to that
ticket (http://bugzilla.gnome.org/attachment.cgi?id=79726&action=view) in
Fedora's distribution until rhythmbox commits a cleaner solution. I've tested
the patch with rhythmbox-0.11.5-3.fc9.x86_64 and it fixed the file transfer problem.
Comment 1 Bastien Nocera 2008-04-04 09:42:54 EDT
Added the patch in rhythmbox-0.11.5-7

Note You need to log in before you can comment on or make changes to this bug.