Bug 228078

Summary:	Mount dirty NTFS/FAT volumes
Product:	[Unmaintained] kresources	Reporter:	T. J. Brumfield <enderandrew>
Component:	local	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	enderandrew, nate, skierpage
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description T. J. Brumfield 2010-02-22 16:29:57 UTC

Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    openSUSE RPMs

Having switched some non-technical family members over to Linux, I often hear complaints that they can't mount flash drives. Usually this is because they did not unmount it cleanly in Windows previously. It is possible to open a console and do a force mount, but this isn't user friendly, nor obvious to the end-user.

What I'd like is a dialog that explains clearly why the volume is dirty, with instructions on how to properly dismount the drive on Windows, Mac and Linux. It should be explained this is the preferred fix for the issue.

There should also then be a prompt to do a force mount if the user desires. The user should never need to touch a konsole session for this.

Comment 1 Nate Graham 2017-11-29 06:33:21 UTC

Not sure this is a problem anymore. I can mount dirty flash drives just fine in Plasma 5 versions of things. Please leave a comment if you can still reproduce this in Plasma 5.

Comment 2 skierpage 2021-12-08 11:05:06 UTC

In my experience KDE Frameworks 5.88.0 on Qt 5.15.2 will silently mount FAT32 USB flash drives even if the dirty bit is set, and I don't think it checks the disk. Then when you click Safely remove from the drive's context menu in Dolphin or from the menu of Disks and Devices in the Plasma panel, KDE clears the dirty bit.

Windows 10 will warn that the drive may be dirty and invites you to check and repair it. So KDE/Linux's behavior is quite different from Windows. Maybe it should let the user know there may be a problem, and invite the user to Check and repair the drive (as KDE Partition Manager can do). If no one reopens this I'll file a separate bug against Solid.