Forum

Full Version: update-rc.d: error
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Software
XBian version: 1.0.RC2
XBMC version: 13.0.RC1
Overclock settings: default

Hardware
Cubox-i2-ultra
Network: wireless
Connected devices: TV, usb storage, cubox-i2 internal devices

Problem description:
update / upgrade after an "apt-get -f install" breaks with:

Code:
plymouth (0.8.8-16) wird eingerichtet ...
update-initramfs: deferring update (trigger activated)
update-rc.d: error: expected NN after start
usage: update-rc.d [-n] [-f] <basename> remove
       update-rc.d [-n] <basename> defaults [NN | SS KK]
       update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
       update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
        -n: not really
        -f: force

The disable|enable API is not stable and might change in the future.
dpkg: Fehler beim Bearbeiten des Paketes plymouth (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
plymouth
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've googled a while and found that may be an issue in an
var/lib/dpkg/info/*.postinst - script. but I didn't find the right one (I checked the plymouth and the initramfs, but my knowledge about this scripts is less than basic)

How to reproduce:
1. I started with a sd-card copy (with dd) from 14. April: Nearly clean image, actual update/upgrade, some small changes: wifi-config + lirc-config
2. apt-get update: no error
3. apt-get upgrade: some issues, -f was recommended by script
4. apt-get -f install: more installations
5. apt-get update: no error
6. apt-get upgrade: breaks with the code above

Are there any recommendations?
Thanks
Hello,

I have the same problem...have you find a solution ?

Thanks

(6th May, 2014 03:26 PM)hf42 Wrote: [ -> ]Software
XBian version: 1.0.RC2
XBMC version: 13.0.RC1
Overclock settings: default

Hardware
Cubox-i2-ultra
Network: wireless
Connected devices: TV, usb storage, cubox-i2 internal devices

Problem description:
update / upgrade after an "apt-get -f install" breaks with:

Code:
plymouth (0.8.8-16) wird eingerichtet ...
update-initramfs: deferring update (trigger activated)
update-rc.d: error: expected NN after start
usage: update-rc.d [-n] [-f] <basename> remove
       update-rc.d [-n] <basename> defaults [NN | SS KK]
       update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] .
       update-rc.d [-n] <basename> disable|enable [S|2|3|4|5]
        -n: not really
        -f: force

The disable|enable API is not stable and might change in the future.
dpkg: Fehler beim Bearbeiten des Paketes plymouth (--configure):
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
plymouth
E: Sub-process /usr/bin/dpkg returned an error code (1)

I've googled a while and found that may be an issue in an
var/lib/dpkg/info/*.postinst - script. but I didn't find the right one (I checked the plymouth and the initramfs, but my knowledge about this scripts is less than basic)

How to reproduce:
1. I started with a sd-card copy (with dd) from 14. April: Nearly clean image, actual update/upgrade, some small changes: wifi-config + lirc-config
2. apt-get update: no error
3. apt-get upgrade: some issues, -f was recommended by script
4. apt-get -f install: more installations
5. apt-get update: no error
6. apt-get upgrade: breaks with the code above

Are there any recommendations?
Thanks
Try the new cubox-i image on the Xbian download page Cubox-i Latest
I've installed it, run it and upgraded it without issues, but .........

See Xbian Cubox-i thread

Where this should have been posted.
(5th Jun, 2014 04:36 AM)IriDium Wrote: [ -> ]Try the new cubox-i image on the Xbian download page Cubox-i Latest

That's nice for people who haven't installed and customized their own software. But does a solution exist for us who don't want to wipe and start over?
From this post :
https://imx.solid-run.com/forums/viewtopic.php?f=7&t=528&start=450#p8092

Quote:While the problem is the plymouth run level, a solution is to comment lines 54, 55, 56 and 59, 60, 61 in the file /var/lib/dpkg/info/plymouth.postinst

it work for me.
(7th Jun, 2014 01:09 AM)belese Wrote: [ -> ]From this post :
https://imx.solid-run.com/forums/viewtopic.php?f=7&t=528&start=450#p8092

Quote:While the problem is the plymouth run level, a solution is to comment lines 54, 55, 56 and 59, 60, 61 in the file /var/lib/dpkg/info/plymouth.postinst

it work for me.

This solution worked for me, but I actually gave priorities to those runlevel scripts.

So, I changed /var/lib/dpkg/info/plymouth.postinst, line 55 from
Code:
update-rc.d plymouth start . 2 3 4 5 . stop . 0 6 . >/dev/null || exit $?
to
Code:
update-rc.d plymouth start 41 2 3 4 5 . stop 41 0 6 . >/dev/null || exit $?

and line 60 from
Code:
update-rc.d plymouth-log start . S . >/dev/null || exit $?
to
Code:
update-rc.d plymouth-log start 40 S . >/dev/null || exit $?
Nice one for the wiki
@all

Debian/Jessie is full of such bugs.

in the latest xbian-update I delivered replacement for update-rc.d which simply accepts three different types of it's call.

because some packages still used old one no more supported, some matched the actual version which is currently by default delivered and last but not least some packages are using format which is not supported (yet) even on SID (i suppose those packages were cloned from master repositories and maintainers at Debian didn't bother to downgrade the control scripts to match Debians older versions of system utilities).

Now and them I still considering re-release Cubox-i version on Wheezy. But when that platform started, Wheezy had libc6 core libs at 2.13(or 2.14) and I was hitting issues with Cubox's binary gfx drivers on that old libc. Now wheezy is at 2.19 and I know 2.18 was already ok.

So maybe. Yesterday I finished with img build tool and img is created from scratch in ~20minutes. It would of course mean also to recompile all XBian's packages against new root and currently we have only few packages converted into full auto building. It will take few more days for others.

But then it will be onclick taking maybe 3-4 hours without human involvement so for Cubox-i it could be benefit for free.
Let's see later.
Reference URL's