NTFS mount method in Kubuntu "System Settings" is broken

Thanks for taking the time to report this bug and helping to make Ubuntu better. Is there anymore information you can supply on this problem?

I am assuming (from your description) you using the 'Disk & Filesystem' application from 'System Settings' (KMenu -> System Settings). Is this correct? Are you using a language that uses non-ascii characters (such as Czech/Chinese)?

Can you run the graphical mount program from a Konsole window, and replicate the problem and then post the output in the terminal window? The mounting program is called `mountconfig` and you'll need to run it from the Terminal using sudo and your admin password.

sudo mountconfig

Hopefully this will give some more hints to what is happening.

That is correct, I am using "Disk and Filesystems" from "System Settings".
"Regional and Accessibility" > "Country or region" is set to Sweden. My locale is en_US.UTF-8.

The only output i get from konsole is;
"""
Error: "/var/tmp/kdecache-pelle" is owned by uid 1000 instead of uid 0.
Error: "/tmp/ksocket-pelle" is owned by uid 1000 instead of uid 0.
"""

I'll attach two (merged) screenshots, so you'll see what i mean.

That looks very similar the same behaviour that was happening in this Bug 141023. Yet that problem happened when there were non-ascii characters in the name/label/uuid fields. From your screenshots, this is clearly not the case.

I can replicate your problem with the radio buttons too. It also happens when using the HFS and VFAT formats.

I also noticed that if you create a new partition, then choose one of the HFS/NTFS/VFAT formats then choose another one of the HFS/NTFS/VFAT formats the following traceback is written to the terminal.

Traceback (most recent call last):
  File "/usr/bin/mountconfig", line 2563, in slotMountTypeChanged
    self.selectEntry(self.comboIndexToMountType[index])
  File "/usr/bin/mountconfig", line 2548, in selectEntry
    self.currentMountEntry.setMountType(mounttype)
  File "/usr/bin/mountconfig", line 1103, in setMountType
    self.extensionObjects[newtypename] = self.MountTypes[newtypename][0](self.extension)
  File "/usr/bin/mountconfig", line 751, in __init__
    super(MountEntryExtVFAT,self).__init__(base)
  File "/usr/bin/mountconfig", line 649, in __init__
    self.label = base.label
AttributeError: 'MountEntryExtVFAT' object has no attribute 'label'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/apport_python_hook.py", line 42, in apport_excepthook
    binary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))
IndexError: list index out of range

Original exception was:
Traceback (most recent call last):
  File "/usr/bin/mountconfig", line 2563, in slotMountTypeChanged
    self.selectEntry(self.comboIndexToMountType[index])
  File "/usr/bin/mountconfig", line 2548, in selectEntry
    self.currentMountEntry.setMountType(mounttype)
  File "/usr/bin/mountconfig", line 1103, in setMountType
    self.extensionObjects[newtypename] = self.MountTypes[newtypename][0](self.extension)
  File "/usr/bin/mountconfig", line 751, in __init__
    super(MountEntryExtVFAT,self).__init__(base)
  File "/usr/bin/mountconfig", line 649, in __init__
    self.label = base.label
AttributeError: 'MountEntryExtVFAT' object has no attribute 'label'

This at least gives us something to go forward with.

This bug was nominated for Gutsy but does currently not qualify for a 7.10 stable release update (SRU) and the nomination is therefore declined. According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https://wiki.ubuntu.com/StableReleaseUpdates .

The bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). To help improve the state of this bug see: https://wiki.ubuntu.com/Bugs/HowToTriage and https://wiki.ubuntu.com/DebuggingProcedures .

Kubuntu 8.04 has reached the end of its supported life, and unfortunately the Guidance user configuration tool and the Guidance Power Manager were the only Guidance apps to survive. The rest were removed from distribution and will not be receiving any more bugfixes. Thanks for understanding, and have a nice day.