Thunderbirds fails to write file to NTFS partition properly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thunderbird (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: thunderbird
With Thunderbird 2.0.0.18 running under Ubuntu 8.04, I received a message with a large, attached MS Word file. I saved the attachment in my Windows XP "Documents" directory with no problems, then decided to save the email as well, using Thunderbird's save as / file.
When I got back to Windows, the email, saved as an .html, refused to open. "File not found" said Windows, although the name was right there in the directory. Same with trying to copy, move, rename, or delete this file. I even tried and old command line trick, using rmdir -S, to get rid of the file, directory, and all - "directory not empty" was the reply. Finally, I was able to get rid of it by restarting Ubuntu, going to the Windows Documents directory, and simply deleting the file, which deleted without further incident.
Another telling item about the saved file, was that it was listed by Explorer as being only a couple of kilobytes long, whereas the same email, saved in my Ubuntu home directory (where it saves and opens without problems) is almost 200 kb, because of the included attachment. It seems to me that Thunderbird file / save fails to complete the write operation in writing to an NTFS partition. I've experience no problems when copying or saving files to the NTFS partition using other tools, such as Nautilus or the command-line cp command.
ProblemType: Bug
Architecture: i386
Date: Thu Nov 27 11:28:34 2008
Dependencies:
DistroRelease: Ubuntu 8.04
NonfreeKernelMo
Package: mozilla-thunderbird None [modified: /var/lib/
PackageArchitec
ProcEnviron:
PATH=/
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: thunderbird
Uname: Linux 2.6.24-21-generic i686
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 302762, and any other logs that are relevant for this particular issue.