system-settings may not be responding to system-image D-Bus signals

[Barry Warsaw]

While testing system-image 3.0.2 for vivid overlay, using the test plan here https://wiki.ubuntu.com/Process/Merges/TestPlan/ubuntu-system-image (3.B - manual download for s-i 3), two problems were noticed.

First, when using `system-image-cli --set auto_download=0`, the system-settings panel didn't notice the change in the auto_download value. At first I though it might be missing the SettingsChanged D-Bus signal, but then I realized that the signal is not sent when using system-image-cli (only when using the normal D-Bus API). system-settings would have to poll for that value. I will open a bugtask for system-image but 1) I'm not sure it's possible to send the signal from the -cli; 2) it's an odd corner case anyway because generally only developers/testers are using system-image-cli.

Second, when I invoke the manual download through system-settings, I don't see any progress. It goes from 0% to prompting to install the update, after a short wait. Please verify that system-settings is responding to the UpdateProgress signal.

[Barry Warsaw (barry)]

Bug task for ubuntu-system-image involves research to see if the SettingsChanged D-Bus signal can be sent when a setting is changed via system-image-cli.

[Jonas G. Drange (jonas-drange)]

Maybe system-image-cli should consume a dbus API from system-image-server? If not, in what other cases will the auto_download setting change remotely?

Apart from that, there's an actual bug in System Settings where if SI's dbus name changes (SI dies/restarts), we don't update our dbus proxy.

[Barry Warsaw (barry)]

On Apr 11, 2016, at 11:29 AM, Jonas G. Drange wrote:

>Maybe system-image-cli should consume a dbus API from system-image-
>server?

We used to do something just like this, as an option to si-cli, but it was
never used and caused problems for the test suite, so it eventually got ripped
out.

>If not, in what other cases will the auto_download setting change remotely?

It really shouldn't. It would be possible to tweak it directly via sqlite,
but that's crazy talk. And really, it most common cases it will only get
changed via D-Bus anyway.

>Apart from that, there's an actual bug in System Settings where if SI's
>dbus name changes (SI dies/restarts), we don't update our dbus proxy.

Don't forget that si-dbus is *designed* to self-exit after a timeout, by
default 10 minutes. It gets re-D-Bus activated on demand.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-system-settings - 0.3+16.10.20160523-0ubuntu1

---------------
ubuntu-system-settings (0.3+16.10.20160523-0ubuntu1) yakkety; urgency=medium

  * Catch connection errors asynchronously

 -- Ken VanDine <email address hidden> Mon, 23 May 2016 12:27:38 +0000