unity-control-center in installed software is listed with wrong icon and title

The package is unity-control-center not gnome-control-center and seems to be due to missing appstream data.

Ping!

This bug was fixed in the package unity-control-center - 15.04.0+17.04.20170213-0ubuntu1

---------------
unity-control-center (15.04.0+17.04.20170213-0ubuntu1) zesty; urgency=medium

  [ Iain Lane ]
  * user-accounts: Reset the AccountsService password mode when setting
    the password. There's a codepath for directly setting the password
    when the user is setting their own, but this doesn't set the AS mode
    back to ACT_USER_PASSWORD_MODE_REGULAR. If you don't change this and
    you're in ACT_USER_PASSWORD_MODE_NONE, then you end up staying in
    the nopasswdlogin group. (LP: #1630156)

  [ Robert Ancell ]
  * Add AppData (LP: #1639507)

 -- <email address hidden> (<email address hidden>) Mon, 13 Feb 2017 10:04:53 +0000

Accepted unity-control-center into -proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity-control-center/15.04.0+16.10.20170214-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

I tested this on Ubuntu 16.04 LTS with gnome-software 3.20.1+git20170208.0.a34b091-0ubuntu1~xenial1 (still in xenial-proposed today). I enabled -proposed updates. unity-control-center shows in gnome-software as "Text Entry" on my computer. Ok, maybe I should install the updated unity-control-center (I think if this bug were fixed, that wouldn't actually be necessary).

I installed the updated unity-control-center, ran 'pkill gnome-software' and tried again. Same result.

I ran 'sudo rm -rf /var/cache/app-info; sudo rm -rf /var/lib/app-info; sudo appstreamcli refresh'. After killing gnome-software, I got the same result.

See also https://bugzilla.gnome.org/779379

Does appstreamcli generate local appstream data or just pull it from the server again? I'm not sure if this change requires a server-side refresh of the appstream data.

That's automatic and you can check it by just looking at the archive. I did not look in this case to see if it is right, but it was in the previous case (wine?).

I think someone should see my comment #4 on https://bugzilla.gnome.org/show_bug.cgi?id=779379

unity-control-center is still in xenial-proposed at https://launchpad.net/ubuntu/+source/unity-control-center/15.04.0+16.04.20170214-0ubuntu1

As part of a recent change in the Stable Release Update verification policy we would like to inform that for a bug to be considered verified for a given release a verification-done-$RELEASE tag needs to be added to the bug where $RELEASE is the name of the series the package that was tested (e.g. verification-done-xenial). Please note that the global 'verification-done' tag can no longer be used for this purpose.

Thank you!

Tested version 15.04.0+16.04.20170214-0ubuntu1, it doesn't solve this issue though.
However marking this as verification-done as per Iain's words:

16:18:55 <Laney> Trevinho: I think that verification-failed could be verification-done-xenial. The change works, it just happens to not fix the bug.

If unity-control-center is released then the task will be marked as Fix Released for this bug. How is that appropriate if the bug isn't really fixed?

Brian, we can easily reopen this bug for xenial.

Because of how the appstream metadata works, it's difficult to test a fix before uploading an attempt to -proposed.

I verify that this bug is fixed now for unity-control-center from xenial-proposed. I think the other half of this bug was fixed in gnome-software.

I also verified that this bug is fixed for unity-control-center 15.04.0+16.10.20170204-0ubuntu1 on Ubuntu GNOME 16.10. I installed unity-control-center and it shows in the Installed tab of GNOME Software with the correct name and icon.

This bug was fixed in the package unity-control-center - 15.04.0+16.10.20170214-0ubuntu1

---------------
unity-control-center (15.04.0+16.10.20170214-0ubuntu1) yakkety; urgency=medium

  [ Iain Lane ]
  * user-accounts: Reset the AccountsService password mode when setting
    the password. There's a codepath for directly setting the password
    when the user is setting their own, but this doesn't set the AS mode
    back to ACT_USER_PASSWORD_MODE_REGULAR. If you don't change this and
    you're in ACT_USER_PASSWORD_MODE_NONE, then you end up staying in
    the nopasswdlogin group. (LP: #1630156)

  [ Robert Ancell ]
  * Add AppData (LP: #1639507)

 -- <email address hidden> (<email address hidden>) Tue, 14 Feb 2017 09:16:44 +0000

The verification of the Stable Release Update for unity-control-center has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package unity-control-center - 15.04.0+16.04.20170214-0ubuntu1

---------------
unity-control-center (15.04.0+16.04.20170214-0ubuntu1) xenial; urgency=medium

  [ Iain Lane ]
  * user-accounts: Reset the AccountsService password mode when setting
    the password. There's a codepath for directly setting the password
    when the user is setting their own, but this doesn't set the AS mode
    back to ACT_USER_PASSWORD_MODE_REGULAR. If you don't change this and
    you're in ACT_USER_PASSWORD_MODE_NONE, then you end up staying in
    the nopasswdlogin group. (LP: #1630156)

  [ Robert Ancell ]
  * Add AppData (LP: #1639507)

 -- <email address hidden> (<email address hidden>) Tue, 14 Feb 2017 09:17:30 +0000