Opened 6 years ago
Last modified 6 years ago
#18392 new defect
Accented Characters causes the "Failed to set the global VirtualBox extra data for key GUI/GroupDefinitions" bug
| Reported by: | Fochi | Owned by: | |
|---|---|---|---|
| Component: | GUI | Version: | VirtualBox 6.0.4 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | all |
Description (last modified by )
VirtualBox 6.0.4 presents the following failure report when you move the position of a virtual machine inside a group: "Failed to set the global VirtualBox extra data for key GUI/GroupDefinitions"
Affected Hosts: All. Already confirmed in Windows and Linux (KDE) hosts.
Affected Guests: ANY.
Is it reproducible? Yes, always. Just follow instructions bellow.
Instructions to reproduce the bug:
- Begin with !Virtualbox version 5.2 with some guest machines.
- Create a group with 2 or more machines
- Rename the group using accented characters (for example á é ç ã etc)
- Move the position of any machine upwards or downwards inside the group.
- It works perfectly in this version of VirtualBox 5.x
- Upgrade VirtualBox to Version 6.0.x
- Move the position of any machine upwards or downwards inside the group.
- It throws "Failed to set the global VirtualBox extra data for key GUI/GroupDefinitions"
Workaround: Rename ALL WORKGROUPS that use accented characters using only standard basic American characters. Of course this is not desirable for non English speaking users. It is only a workaround.
Other issues and MORE BUGS (or other aspects of the same bug):
- On VirtualBox 6.x it is NOT possible to rename the group back to accented characters (generally they are generated using 2 key presses: the accent followed by the standard letter), but here is where you will see ANOTHER RELATED BUG: My Brazilian Portuguese Keyboard has a key with the letter "ç" and !Virtualbox 6.x just accepts the letter "ç" and enters in the bug condition described above.
- Whenever any machine group is named using accented characters, !Virtualbox is completely unable to cleanly shutdown. I have already described this failure mode in another completely different bug report: #18318 . The main bug is described here and whenever it is fixed, the other bug is going to be fixed as well as it is only a collateral effect of the bug reported here.
I hope this explanation is clear enough to trigger a bug fix action.
Regards,
Hilário Fochi Silveira
