Bug 255831

Summary: I cannot edit the label of a fat32 or ext4 partition, label text field not typable
Product: [Applications] partitionmanager Reporter: Rafael <EagleScreen>
Component: generalAssignee: Volker Lanz <vl>
Status: RESOLVED NOT A BUG    
Severity: normal CC: ilikefoss
Priority: NOR    
Version: 1.0.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Rafael 2010-11-01 19:42:32 UTC
Version:           unspecified (using KDE 4.5.2) 
OS:                Linux

Partitionmanager 1.0.3
The label of a fat32 partition is not editable because the text field to type the label seems to be broken.

Reproducible: Always

Steps to Reproduce:
1. Open partitionmanager.
2. Select a disk with some fat32 partition.
3. Right click on a fat32 partition and select properties.
4. Click on the text field to input a label.
5. The cursor seems to be ready to type a new label, but when I type, nothing happens.

Actual Results:  
5. The cursor seems to be ready to type a new label, but when I type, nothing happens.

Expected Results:  
When I type the label with the keyboard, the text should be captured in the text box. And the label should be set or changed.

OS: Linux (i686) release 2.6.35-22-generic
Compiler: cc
Comment 1 Rafael 2010-11-01 19:47:04 UTC
Also happens with ext4 partitions.
Comment 2 Volker Lanz 2010-11-02 09:51:55 UTC
Thank for using KDE Partition Manager and for taking the time to report this issue.

KDE Partition Manager 1.0.3 does not support setting or changing the file system label for FAT16 and FAT32 file systems (also see View -> File System Support in the application), so the behaviour you describe is expected.

I cannot reproduce this for ext4 file systems. Can you please check again? I'm closing this issue for now, but feel free to reopen if there actually is a problem with ext4 file systems.

Note that you cannot change the label as long as the file system is mounted.
Comment 3 John 2023-03-07 05:52:30 UTC
I can confirm this problem still exists on KDE Partition 22.12.3!
On Debian 12 (unstable repository).