Several update-rc.d/insserv warnings

[Removed by request]

I'm using Ubuntu 15.10 dev with insserv 1.14.0-5ubuntu3 and sysv-rc 2.88dsf-59.2ubuntu1 and on configuring packages I have seen now for some time several update-rc.d/insserv warnings. If I'm reconfiguring all packages installed on my system they appear on:

- cron 3.0pl1-127ubuntu1:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: stop runlevel arguments (1) do not match cron Default-Stop values (none)
insserv: warning: current stop runlevel(s) (1) of script `cron' overrides LSB defaults (empty).

- cryptsetup 2:1.6.1-1ubuntu7:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

- grub-common 2.02~beta2-26ubuntu3:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

- keyboard-configuration 1.108ubuntu5:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

- ntp 1:4.2.6.p5+dfsg-3ubuntu6:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

- procps 1:3.3.9-1ubuntu8:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

- x11-common 1:7.7+7ubuntu4:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

[dino99 (9d9)]

This is seen since a while here too with 15.10 i386 gnome-shell session; as well on 15.04

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[dino99 (9d9)]

i does not see that issue now; the transitional gcc5 & libstdc++6 and other upgrades seem have fixed it.

[Removed by request (removed3425744)]

With an up-to-date system (Ubuntu 15.10 dev) I'm still seeing this issue on all the packages listed in the startpost on reconfiguring.

[dino99 (9d9)]

A reinstall example:

Preparing to unpack .../acpid_1%3a2.0.23-1ubuntu1_i386.deb ...
Unpacking acpid (1:2.0.23-1ubuntu1) over (1:2.0.23-1ubuntu1) ...
Processing triggers for man-db (2.7.3-1) ...
Processing triggers for systemd (225-1ubuntu4) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Setting up acpid (1:2.0.23-1ubuntu1) ...

so i'm not seeing your error here (GS session Wily i386)

[Removed by request (removed3425744)]

I have never seen this issue on acpid but I'm also seeing it for example on reinstalling cron. Can you check if this issue appears if you reinstall/reconfigure cron?

[dino99 (9d9)]

You are right about that one:

Preparing to unpack .../cron_3.0pl1-127ubuntu1_i386.deb ...
Unpacking cron (3.0pl1-127ubuntu1) over (3.0pl1-127ubuntu1) ...
Processing triggers for man-db (2.7.3-1) ...
Processing triggers for systemd (225-1ubuntu4) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up cron (3.0pl1-127ubuntu1) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: stop runlevel arguments (1) do not match cron Default-Stop values (none)

Looks like its one of the non transitionned yet, the latest upgrade is quite old:

cron (3.0pl1-127ubuntu1) vivid; urgency=low

  * Merge from Debian unstable. Remaining changes:
    - debian/control:
      + Move MTA to Suggests field.
    - debian/cron.upstart: Add Upstart script.
    - debian/rules: Call dh_installinit to install Upstart job properly.
    - d/cron.default: change to a deprecated message to make it clear
      that the file is no longer in use.

 -- Michael Vogt <email address hidden> Mon, 27 Oct 2014 10:19:21 +0100