Bug 386196 - Can't create new LVM volume group - unable to type in "Volume Group Name:" field
Summary: Can't create new LVM volume group - unable to type in "Volume Group Name:" field
Status: RESOLVED FIXED
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (show other bugs)
Version: 3.2
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-26 05:43 UTC by Xtal
Modified: 2017-10-26 09:38 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
"New volume group" window: can't type in the "Volume Group Name:" field (30.15 KB, image/png)
2017-10-26 05:43 UTC, Xtal
Details
My partition table on the disk (108.46 KB, image/png)
2017-10-26 05:46 UTC, Xtal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xtal 2017-10-26 05:43:47 UTC
Created attachment 108567 [details]
"New volume group" window: can't type in the "Volume Group Name:" field

I've created a LVM2 PV partition on my disk.  And now I'm trying to create the volume group from the menu option: Tools > Create Volume Group

It won't let me type in the "Volume Group Name:" field, and therefore I also can't hit "Ok" to create the volume group.

When I run partitionmanager with a terminal open to view its text output, this error message comes up every single time I press a key in the field (but no characters appear in the text field):

QRegularExpressionPrivate::doMatch(): called on an invalid QRegularExpression object

I've attached a screenshot of the screen I'm talking about.

I'm using: "partitionmanager 3.2.0" - installed from the official Manjaro repos, 64bit OS.

I'm not overly experienced with LVM, so please let me know if I've misunderstood something.
Comment 1 Xtal 2017-10-26 05:46:17 UTC
Created attachment 108568 [details]
My partition table on the disk

Just adding this in case it's relevant at all.
Comment 2 Xtal 2017-10-26 06:04:29 UTC
Also I should have mentioned, this PV is inside LUKS.  Not sure if that makes any difference?
Comment 3 Andrius Štikonas 2017-10-26 09:37:01 UTC
Yeah, I already saw this issue and fixed.

Version 3.2.1 was released to specifically fix this bug.
Please ask your distribution to upgrade.