Installation of application from the click store appears not to work

Anecdotal reports from email indicated "I can't even install with pkcon"

Logs from vtuson

http://paste.ubuntu.com/8671759/

i see the following in /var/log/syslog when trying to install a package:

Oct 25 09:17:08 ubuntu-phablet dbus[735]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper)
Oct 25 09:17:08 ubuntu-phablet dbus[735]: [system] Successfully activated service 'org.freedesktop.systemd1'
Oct 25 09:17:14 ubuntu-phablet dbus[735]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out

Talking to Pat, we wondered if it was the unity-scope-click landing here:

http://people.canonical.com/~ogra/touch-image-stats/rtm/124.changes

(No proof other than a suspicious sounding name, of course)

Downgrading apt fixed the issue for me (it got updated on 125 for security fixes).

You can find the older packages at http://derived.archive.canonical.com/ubuntu-rtm/pool/main/a/apt/

The correct treatment for this is to notice that it's a recurrence of https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1368246 due to ubuntu-rtm/14.09 being stale; syncing the fixed packagekit into ubuntu-rtm/14.09 (and un-reverting apt) will fix it.

That certainly looks like the same bug from the repro steps.

So, for the purpose of recording on this bug, I'll note that it is planned to respin an image (128) with the apt package reverted.

As cjwatson notes, there is what looks like a better fix that should be used for future images.

Right, reverting does the job for now, but we should generally regard reverting security fixes as something to be strenuously avoided so we shouldn't consider the matter closed with that.

My suggestion is:

 * binary-sync new packagekit from utopic into 14.09, via a silo if you want
 * get a member of ~ubuntu-archive to un-revert the apt change as follows:
  * remove-package -A ubuntu-rtm -s 14.09 -m 'reverting to 1.0.9.2ubuntu2' apt
  * copy-package --from=ubuntu-rtm -s 14.09 -e 1.0.9.2ubuntu2 -b --force-same-destination apt

(Note that the --force-same-destination option requires lp:ubuntu-archive-tools >= r909, so the archive admin doing this should take care to update their local checkout first.)

apt must be done strictly after packagekit, but it doesn't particularly matter how much later. However, the remove-package and copy-package operations must be done as close as possible to each other, ideally in a single publisher run. The derived distributions publisher runs at "*/5 * * * *" in crontab(5) syntax, so it should be sufficient to run it at a minute ending in 1 or 6 from a system with reasonably reliable networking. The consequences are not permanent if you get this wrong, but it would cause the ubuntu-rtm archive to be essentially unusable for any kind of build operation for a few minutes, so it's best to make some effort to get it right.

I'm on holiday until Wednesday now and don't especially want to be coordinating this from a hotel room over the weekend. Other members of the archive admin team should be able to deal with this given the above description, though, so I suggest grabbing one of them on Monday or Tuesday.

FYI, I have now prepared a backported minimal security patch for apt.
I plan on requesting a silo and testing it on thursday.

It's probably better than risking any further regressions by doing the apt and packagekit version upgrades.