Bugzilla – Bug 1074053
Virtualbox - Permissions problems dialogue box not showing up in German
Last modified: 2019-03-20 16:54:17 UTC
I am using the "Tumbleweed" distribution and just installed virtualbox using zypper.
My LXDE-Desktop is set to German language but for some reason the dialogue box "Permissions problem !" is in English. (Not a member of the vboxusers group)
I am happy to translate this string if necessary but IMHO the dialogue box should also be in German to provide a smoother openSUSE experience which is already quite good but could be even better.
Have a good christmas,
I guess this is an implementation issue with virtualbox.
I think I know how to add translations for the permissions and USB passthrough pop-ups. If you are still willing to do translations, I would appreciate seeing translations for the two sets below:
"You are not a member of the \"vboxusers\" group. Please add yourself to this group before starting VirtualBox. You could do it using: Yast / Security and Users / User and Group management. Don't forget re-login your user account!"
"USB passthrough requires read/write access to USB devices.
As a result, it opens a security hole.
Nonetheless, this feature is extremely useful and it may be worth the security risk. Thus the code defaults to enabling it.
If you agree that the risk is acceptable, then click 'Enable'.
You will not be asked this question again when VB is updated. If you later change your mind, run 'rm ~/.vbox/*'
If you wish to disable USB passthrough to plug the security hole, then click 'Disable'. You will be asked for the system password, and /etc/udev/rules.d/60-vboxdrv.rules will be changed.
These changes cannot be preserved through VB updates, thus this screen will be displayed again at that time."
Created attachment 776536 [details]
I am more than happy to do this and I am submitting my translations in the text file attached. It would be cool to have my name and email added to the translators credit list although this is not mandatory.
*** Bug 1129635 has been marked as a duplicate of this bug. ***