* origin/pr/172:
Say which repository caused the error in warnings
Only make qrexec calls when necessary
Squash more PyLint warnings
Decode stderr in repo qrexec calls
Fix error handling
Fix `self` being undefined when showing warnings
Only apply repo preferences when "OK" is clicked
Don't use asserts for error handling
Check that repo management succeeded
Remove unnecessary assert
Squash some PyLint warnings
Add UI for managing Qubes update repositories
Fix typo
FixesQubesOS/qubes-issues#4550
Qubes Manager seems to try to guarantee that 10*init_mem is at
least max_mem by automatically adjusting init_mem to max_mem/10 if
inappropriate values are set. However, this may not guarantee that
10*init_mem >= max_mem due to rounding errors. This change fixes
these edge cases by basically rounding up the result of division
by 10.
Now port will be displayed as port_number [(service name)]
, and not just service name. Also added a tooltip with explanation
of what can be put in the 'port/service' field, renamed
the field to 'Port/service' and added some examples of pure port
numbers to the drop down.
fixesQubesOS/qubes-issues#5211
Now, when selecting a file fails for some reason
(lack of installed file manager, VM crashed on start,
anything), the user will get an error message.
references QubesOS/qubes-issues#5202
This helps in situations where the qrexec calls are forbidden; it also
prevents settings from being unintentionally changed and gives a
noticeable performance boost when the "OK" button is clicked.
Before this change, "foobar\n" on stderr would be rendered (in the
warning dialog) as "b'foobar\n'", which is ugly. Now it'll be rendered
just as "foobar", followed by an actual newline character.
Apparently Python exceptions don't take **kwargs, so we just pass a
dictionary as the second (regular) argument. While we're at it, we
pretty-print said dictionary when displaying error messages.
First of all, the method that was being called has asserts of its own,
so it's guaranteed to either succeed or crash the program with
AssertionError. Second, asserts are optimized out by the interpreter
when -O is passed. Therefore, this code is buggy because it sometimes
wouldn't be run, but we need the side effects.
Kernels are sorted with a rough algorithm, comparing groups of numbers
numerically, and names consisting of strings alphabetically.
fixesQubesOS/qubes-issues#5084
A simple checkbox in the 'Advanced' tab. Does not allow disabling
'provides_network' if the VM is in use as NetVM; instead, a tooltip
informs the user which VMs use it.
fixesQubesOS/qubes-issues#5079
Fixed dependencies, places where obsolete functions stopped working,
code fragments that started throwing warnings and an .ui file that
stopped being readable after the update.
* qubesos/pr/175:
More fixes to force tests to work
Tests for Create New VM
Tests for VM settings
Fixed spec
Tests for backup_utils file
Tests for Qubes Backup
Test changes related to fixes in https://github.com/QubesOS/qubes-manager/pull/176
Tests for qube manager
Tests for global settings
* origin/pr/176:
Fixed logs display in Qube Manager
Protected loading manager settings from malformed config files
Fixed bug with hiding last visible column
Added additional check for cloning a VM
Fixed unnecessary property set in Global Settings
Fixed bug in Global Settings
Changed the terms used in Create New VM Gui to the following:
-Qube based on a template (AppVM)
-Standalone qube
-Standalone qube copied from a template
references QubesOS/qubes-issues#4723
* origin/pr/167:
More documentation and added another column for default_dispvm to Qube Manager
Added DVM Template column to Qube Manager
Rewritten Qube Manager widgets
In rare case (when the Qube Manager was reverted to an older version
that does not have a column on which it was last sorted) downgrading
Qube Manager could result in a crash on start.
PCI devices are now handled as DeviceInfo objects, not (string,name) tuples;
furthermore, a device that no longer exists in the system can be
correctly removed via VM settings window (it is displayed as Unknown
device).
fixesQubesOS/qubes-issues#2789
* origin/pr/154:
Fix too long lines
Moved busy_cursor() inside save_changes()
Removed unneded calls to Override/Restore cursor
Removed duplicated call to save_changes()
Removed unneeded Cursor override/restore
Added busy_cursor()
Added BusyCursor for notify manager is working
Revert "Added progress bar to __save_changes__"
Revert "Increase progress wait time to 2s"
Increase progress wait time to 2s
Added progress bar to __save_changes__
Remove unneeded slot connections and reject overwrite
Changes in some fields (to be precise, drop-downs) were discarded
in VM Settings when changed after an 'Apply' and before an 'OK'.
fixesQubesOS/qubes-issues#4833
Added an 'Advanced' settings checkbox that allows the user to set a given
VM as template fo dispvms. It sets both the template_for_dispvms property
and the appmenus-dispvm feature - instead of delving into particulars
of how and which should be set, the user can just turn off the
whole setting if they want to make some changes in the vm and then turn
it on again.
fixesQubesOS/qubes-issues#4004
Prior to this commit, clicking on the "OK" button in the global settings
window would cause the dom0 memory boost and minimum VM memory fields to
be saved incorrectly, due to the fact that the code calculates the
values to be saved using the "MiB" as the units (i.e., factors of
1024), whereas the code would save the corresponding string into the
qmemman configuration file with the "M" suffix (indicating factors of
1000 instead of 1024).
Due to this bug, the aforementioned fields' values would be scaled down
every time the user clicked on the "OK" button in the global settings
window. For example, if the user entered 400 and hit 'OK', opening the
global settings window again would show the value 381.
Instead of always selecting for backup all the VMs that were selected
during last saved backup, now the GUI tool will disregard last selected
VMs and instead use VM attribute 'include_in_backups'
fixesQubesOS/qubes-issues#4713
In edge cases (usually when system locale is not installed) Gtk falls
back to 'C' (not C.utf-8 ...) locale. Fixed that to enforce utf-8 always.
fixesQubesOS/qubes-issues#4475
If system storage cannot be resized (due to belonging to an AppVM), the
system storage max field is grayed out without explanation; now it
will have a tooltip.
fixesQubesOS/qubes-issues#4617
According to changes in 4dc8631010 ,
memory balancing is now handled not by a special service but by
magic value of 0 maxmem. Added handling thereof to VM Settings -
also, settings will store the last used maxmem value in
qubesmanager.maxmem_value feature.
fixesQubesOS/qubes-issues#4480
To avoid conflict with scripts that make whonix magic,
if the user selects default netvm, we do not set any netvm and
trust the create_vm method to properly set it as default appropriate
for the given template.
fixesQubesOS/qubes-issues#1954
A working template manager; at the moment it only provides means
to easily change templates of multiple VMs at once, but it should also give tools to install new templates.
fixesQubeSOS/qubes-issues#4085
* origin/pr/132: (48 commits)
Fixed unreachable code thanks to travis
Clear searchbox pressing esc without need of selecting it
Fix errors when some domain fails to start
wait thread to finish when aborting
Don't terminate backup thread when aborting
Fix iterating and removing over list
Use 'qube' instead 'Qube'
Qube -> qube
Catch possible KeyError when starting dispVM
Fix authorship and python version
Create backup_window on the stack
Removed sigchld_handler old code
Fix pylint
Do not terminate the thread
Fix error/success message on dialog
Fix opening settings/boot dialog after VM creation
Add pylint disable too-few-methods
Fix travis errors
Removed unused import
Workaround for backup dialog modeless behaviour
...
