GitLab

The user password specified during an express installation is cached
in plain text in ~/.config/gnome-boxes/unattended/setup-data.conf.
Instead, we should use the keyring - it's meant for this. As long as
the host user account has a password, the keyring will be encrypted
and protected in case the disk is stolen.

We store the password as a serialized GVariant dictionary because it
is more extensible than a simple string. In future we might want to
store multiple secrets for a particular media (eg., registration
passwords, product keys, etc.), and those can be accommodated by
specifying a different key in the dictionary.

Fallout from ae21e562

https://bugzilla.gnome.org/show_bug.cgi?id=777788

In the following patch, we will need libsecret to store the user
passwords during an express installation.

https://bugzilla.gnome.org/show_bug.cgi?id=777788

Fallout from ae21e562

https://bugzilla.gnome.org/show_bug.cgi?id=777788

This would otherwise lead to a crash during startup.

Fallout from ad606291

https://bugzilla.gnome.org/show_bug.cgi?id=769718

The problem is that currently a window will listen to notifications
from a machine long after it has been replaced with another machine.
This leads to unpredictable behaviour, like windows being removed
because one of its previous machines has been deleted.

https://bugzilla.gnome.org/show_bug.cgi?id=767214

The problem is that after removing a window, its deleted machine
is still able to send signals to it and consequentially to try
to remove it again during the actual machine deletion process,
which leads to undefined behaviour.

Let's simply disconnect the machine's callbacks in its window
when the machine is signaled as deleted.

https://bugzilla.gnome.org/show_bug.cgi?id=767214

This reverts commit 875e057f.

This breaks string freeze.

This reverts commit 5b18f9d7.

This breaks string freeze.

The GVirConfig.DomainInterface or GVirConfig.DomainGraphics
references kept in update_existing_domain() will get their
XML node destroyed when running GVirConfig.Domain.set_devices().

To workaround this problem, add the updated devices to the devices list
before calling set_devices().

https://bugzilla.gnome.org/show_bug.cgi?id=769718