Ubuntu 15.04 - Failed installation of ubuntu-desktop package (whoopsie package)

[bugproxy]

-- Problem Description --
When installing the ubuntu-desktop package in Ubuntu 15.04 during the set up of a package the following message is displayed and the installation doesn't go any further:

Setting up whoopsie (0.2.47) ...
Error getting authority: Error initializing authority: Error calling StartServi24)yName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 2
Failed to execute operation: Connection timed out

I am able to reproduce this issue when installing the ubuntu-desktop package on top of a fresh install, but in a different test, I tried to install only the whoopsie package where the package installation stops and I did not see this issue.

I am attaching below the full log of the apt-get installation.

The problem is on starting the systemd script. If I stop it, it makes progress. There are other systemd initi scripts that are failing also...

> Can you try by switching the init system back to upstart, and re-installing?
>
> See [1]; probably this will do: init=/sbin/upstart
>
> [1]
> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2015-March/001130.
> html

Mauricio, the installation of the packages went properly by adding the init=/sbin/upstart to the boot line. I attached the full installation log above.

But when restarting the system, the following message is issued and the system doesn't seem to be bootable anymore.

* Restoring resolver state... [ OK ]
 * Starting uuid generator uuidd [ OK ]
 * speech-dispatcher disabled; edit /etc/default/speech-dispatcher
/lib/init/init-d-script: 12: /etc/rc2.d/S02whoopsie: -c: not found
basename: missing operand
Try 'basename --help' for more information.
 * saned disabled; edit /etc/default/saned

Interesting. It installed, but failed to stop services.
Hm, it seems that whoopsie thing is broken intermediarily between upstart and systemd.

Trying to get rid of whoopsie may help.
Do you need an 'Ubuntu error tracker submission' tool? :)

I'd suggest you to try to remove it.
If some things depend on it, and are not important, pull them off/ignore dependencies, and try again. That might help.

Nonetheless, it's certainly worth a launchpad bug for Canonical to look at.

Another work-around, much less disruptive, is just ignore the rc script failing in the reboot chain. :)

You can find a symlink for it in /etc/rc{6,0}.d (reboot/shutdown).. just renaming it to w/out a leading K should effectively disable it from the reboot/shutdown runlevel change chain.. and hopefully that will get the issue out of the way for now.

Ah, the other comment mention it's rc2.d (an startup/single user runlevel, IIRC).. you can try the renaming there to, but to w/out a leading S.

IIRC this command should achieve that too:
$ sudo update-rc.d whoopsie disable

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

Default Comment by Bridge

[Brian Murray (brian-murray)]

I was unable to recreate this when I installed the ubuntu-desktop package in a vivid amd64 chroot.

[Frédéric Bonnard (frediz)]

I couldn't reproduce that exactly but got the same symptom on other packages.
From what I've been checking, I think this bug is the same problem as this one :
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1436448