a2d0b128b7
Prior to this commit, whenever the user selected the default kernel in a VM's "Advanced Settings" dialog in Qubes Manager, the "uses_default_kernel" flag would not be saved as expected. Instead of the intent to use the default kernel version for the VM in the future, the VM would be stuck with the specific kernel version and not any new future default kernel versions. This issue occurs because the "kernel" property setter for the QubesVm class resets the "uses_default_kernel" member variable to False, and Qubes Manager sets the "uses_default_kernel" property before setting the "kernel" property. Resolve this issue by making sure that the "uses_default_kernel" member variable of the VM in question is set after the "kernel" member variable. |
||
---|---|---|
.tx | ||
i18n | ||
icons | ||
qubesmanager | ||
rpm_spec | ||
.gitignore | ||
.travis.yml | ||
about.ui | ||
backupdlg.ui | ||
build-deps.list | ||
globalsettingsdlg.ui | ||
informationnotes.ui | ||
logdlg.ui | ||
mainwindow.ui | ||
Makefile | ||
Makefile.builder | ||
multiselectwidget.ui | ||
networknotes.ui | ||
newappvmdlg.ui | ||
newfwruledlg.ui | ||
org.qubesos.QubesManager.conf | ||
org.qubesos.QubesManager.xml | ||
qubes-manager | ||
qubes-manager.desktop | ||
qubes-vm-settings | ||
qubesmanager.pro | ||
README.md | ||
releasenotes.ui | ||
resources.qrc | ||
restoredlg.ui | ||
settingsdlg.ui | ||
version |
Qubes Manager
Managing translations
Adding new language
- Add
i18n/qubesmanager_LANGUAGECODE.ts
(replaceLANGUAGECODE
with actual code, for examplees
) toqubesmanager.pro
-TRANSLATIONS
setting. - Run
make res update_ts
Regenerating translation source files (.ts
)
make res update_ts
This will keep translated strings, but will add new ones.
Updating translations
Commit updated .ts
files into i18n
directory.