Fedora Core 5 / Amarok 1.4.3 (amarok-1.4.3-3.fc5)

I have 'broken' around 500 flac files in my music library by editing the tags from Amarok.

# flac -t 03\ -\ Miles_From_Our_Home.flac
03 - Miles_From_Our_Home.flac: ok

# metaflac --list --block-type=VORBIS_COMMENT 03\ -\ Miles_From_Our_Home.flac
METADATA block #1
  type: 4 (VORBIS_COMMENT)
  is last: false
  length: 167
  vendor string: reference libFLAC 1.1.2 20050205
  comments: 6
    comment[0]: ARTIST=Cowboy Junkies
    comment[1]: ALBUM=Miles From Our Home
    comment[2]: GENRE=Rock
    comment[3]: Date=1998
    comment[4]: TrackNumber=3
    comment[5]: TITLE=Miles From Our Home

## Add comment 'TEST' with Amarok.

# metaflac --list --block-type=VORBIS_COMMENT 03\ -\ Miles_From_Our_Home.flac
METADATA block #1
  type: 4 (VORBIS_COMMENT)
  is last: false
  length: 187
  vendor string: reference libFLAC 1.1.2 20050205
  comments: 7
    comment[0]: ALBUM=Miles From Our Home
    comment[1]: ARTIST=Cowboy Junkies
    comment[2]: DATE=1998
    comment[3]: DESCRIPTION=Test
    comment[4]: GENRE=Rock
    comment[5]: TITLE=Miles From Our Home
    comment[6]: TRACKNUMBER=3

# flac -t 03\ -\ Miles_From_Our_Home.flac
03 - Miles_From_Our_Home.flac: testing, 100% complete

03 - Miles_From_Our_Home.flac: ERROR while decoding data
                              state = FLAC__STREAM_DECODER_UNPARSEABLE_STREAM

The FLAC stream may have been created by a more advanced encoder.  Try
  metaflac --show-vendor-tag 03 - Miles_From_Our_Home.flac
If the version number is greater than 1.1.2, this decoder is probably
not able to decode the file.  If the version number is not, the file
may be corrupted, or you may have found a bug.  In this case please
submit a bug report to
    http://sourceforge.net/bugs/?func=addbug&group_id=13478
Make sure to include an email contact in the comment and/or use the
"Monitor" feature to monitor the bug status.

# metaflac --show-vendor-tag 03\ -\ Miles_From_Our_Home.flac
reference libFLAC 1.1.2 20050205

It is now impossible for me to decode these files (even with the 'force' option). How can I recover these files?

Regards

Clive

I have added a bugzilla (134751) for this issue.