Comment 8 for bug 1815305
Revision history for this message
| Uwe Klotz (uklotzde-deactivatedaccount) wrote | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I have an (alarming) idea: If the temporary file could not be created successfully, then SafelyWritableFile will continue with the original file. The constructor takes the wrong path, because the member containing the original file name has already been initialized and is not reset upon failure!!
This failure might happen if the file system is (almost) full and neither the temporary copy can be created nor TagLib is able to finishing writing into the original file.
Unfortunately this bug also affects 2.1.