** Changed in: gparted
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262161
Title:
dmraid failure when array name contains spaces
To manage notifications about this
** Changed in: gparted
Status: Unknown = New
** Changed in: gparted
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262161
Title:
dmraid failure when array name
** Also affects: gparted via
https://bugzilla.gnome.org/show_bug.cgi?id=649509
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262161
Title:
dmraid
You set the name when you created the array with the bios utility, so
this isn't a bug in dmraid. gparted shouldn't choke on such names
though, so reassigning the bug there.
** Package changed: dmraid (Ubuntu) = gparted (Ubuntu)
--
You received this bug notification because you are a member
I believe that this is the same as the following upstream report:
https://bugzilla.gnome.org/show_bug.cgi?id=649509
** Bug watch added: GNOME Bug Tracker #649509
https://bugzilla.gnome.org/show_bug.cgi?id=649509
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It appears to be the same as that upstream report, yes.
The RAID name has been set by the manufacturer in this case, and to
dual-boot without re-installing everything it was necessary to use it.
Is it correct behaviour for `dmraid` to escape the space to `\x20` in
this case though, given it is a
