'Cannot mount volume' details are not selectable

Thank you for taking the time to report this bug and helping to make Ubuntu better. Which version of Ubuntu are you using?

Ubuntu Gutsy on ia64/amd64

ntfs-3g 1.826 supports mount in this case.

But why is the -o force not enabled by default?

If the case's that it's potentially dangerous to mount a dirty volume, the package should ASK the user what to do, ignore the case that can lead to data loss and mount it, or "Do not mount".

The possibility of data loss in dirty unmount situations is relatively small, so small that every volume should be mountable without any data loss.
I have always forced the mount, and nothing bad has happened.

Maybe someone could post a new bug or blueprint of this one?
Preferably one, that has rights to make this change as a "High" or "Medium" priority, as this is pretty important for users who come from Windows!

A sample case:
Person A installs Ubuntu on his laptop, and has Windows XP/Vista on his desktop, he has some external HD drives which he uses pretty often.
A copies some files from his Windows desktop to the drive, hoping he could copy the files to his laptop, and when the copying is ready, he just pulls the USB-cable off his desktop (like 9 of 10 windows users do! 7 of 10 don't even know the possibility to "Safely remove hardware"!!!) and plugs it in his Ubuntu laptop and waits a moment.. Then a window pops in and tells Mr. A that the volume cannot be mounted. He thinks about "What the heck is a volume?" "And why it can't be.. umm.. mounted?? It worked in my precious Windows XP!" He then tries to unplug it, and plug it back in, and again, the same window comes out and tells Mr. A that the "Volume cannot be mounted". A does not have the interest to check the "Details" -printout, and even if he does, he does not know where to use the forced mount command! Mr. A then plugs the drive to his Windows desktop and it works. He then thinks about what could be the problem, and gets an answer: "As it works in Windows, and not in Ubuntu, the reason is that damn Ubuntu which does not just work".
But if we just had showed him a warning "This drive has been removed unsafely. If you have an Windows computer, plug the drive back into it and use "Safely remove hardware" to remove it, and after that you can use it safely in this computer. If you wish, you can force the mounting of the drive, which however, can lead to data loss." And buttons "Force" and "Cancel". Maybe the user cancels it, "Safely removes it" in windows, and then plugs it back into his Ubuntu laptop and it works. Or if the user don't have an Windows computer available, Forces the mounting with his own risk.
And again, another happy user!

Your choice after all, but that's how i see it.
If anyone wishes to create a new blueprint or bug, you can copy that scenario into the Details of it.

Hmmm this particular issue really shits me....

I like the dumb arse "Homer Simpson" approach....

"Light Bulb ON - Light Bulb OFF"

"Light Bulb ON - Light Bulb OFF"

"Light Bulb ON - Light Bulb OFF"

"Light Bulb ON - Light Bulb OFF"

And while I WISH and DESIRE to be able to program all this neato stuff into code so that every one can use it, for the time being I am only able to whine about this issue.

It shits me how sometimes the drive or USB card readers DO just work and other times they refuse to mount... or work when mounted etc...

So about the only thing I can do for now is winge at other people - Ohhhh boo hoo hoo it's fucked... it doesn't work... YOU fix it and make it work for me... I can't cope, it's all too hard... Oh woe is me"....

If I could and knew how, I'd love to write up the coding to so that ALL USB drives - be they cards from my camera or my Winslows USB backup drive, would just "plug and work"....

So rather than just whine and expect everyone else to do it for me... I'd like to be a contributor too..

If some one would like to teach me how to program for Ubuntu Linux, I'd be happy to start working on it...

Contact me at

callmeshane303ATyahoo.com

could you try if you still get the issue? that seems to work correctly in intrepid?

Problem still exists in Intrepid, just had it happen today (or user couldn't figure out how to do it, I wasn't physically present). In any case this problem still persists in Ubuntu Intrepid.

The bug has been sent on http://bugzilla.gnome.org/show_bug.cgi?id=574287

This package has been removed from Ubuntu. Closing all related bugs.