Quod Libet errors when working with files on mounted NTFS partition

[Patrick Walker]

Quod Libet will display an error when saving changes to the tags of .mp3 or .ogg files (I assume this applies to all audio files, but have no other filetypes on my computer to test with) when they are located on a mounted partition of filesystem type NTFS. The changes are saved, indicating everything works fine, but every time it saves changes it reports this error:

Saving example.mp3 failed. The file may be read-only, corrupted, or you do not have permission to edit it.

Where "example.mp3" is the filename. This does not occur on the ext3 partition / exists on, but I am not sure if it happens with mounted ext3 partitions.

[Steven Robertson (stevenrobertson)]

On Mon, Jul 27, 2009 at 1:57 AM, Patrick Walker<email address hidden> wrote:
> Quod Libet will display an error when saving changes to the tags of .mp3
> or .ogg files (I assume this applies to all audio files, but have no
> other filetypes on my computer to test with) when they are located on a
> mounted partition of filesystem type NTFS.

I've tried to reproduce this behavior, but on my system saving when
the volume is mounted read-write via NTFS-3G works fine, and saving
when it is mounted read-only is not allowed by the application.

Please try the following:

* Examine the kernel log ('sudo dmesg') and mount options ('mount'
without arguments) to make sure the filesystem is mounted read-write
and is consistent. I've seen NTFS-3G set the write flag on a
filesystem even while mounted read-only.

* Use the mutagen-inspect tool ('mutagen-inspect /path/to/file') to
ensure that the files are really being changed by QL, and not just in
QL's internal database.

* Run Quod Libet from a terminal with debugging output enabled
('QUODLIBET_DEBUG=1 quodlibet') and post the relevant portion after
receiving the error message (or just post the whole thing).

Thanks,
Steven

[Patrick Walker (phobiac)]

I went through your suggested checklist, and found this:
1) The partition is mounted r/w, and I have permission to edit files and folders on it.
2) mutagen-inspect shows that the files are being modified
3) Running quodlib in at debug level 1 reported nothing that seemed at all helpful, which is curious considering that the error still shows. I have attached the relevant part of the log.
Even stranger, this was occurring on a file that it is not happening to now, but still happening to other files.