SABnzbd Forums

Hi,

On two different machines running Ubuntu Lucid Lynx, automatic update fails:

E: sabnzbdplus: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 6

Which means more or less: Post-install subprocess returned a state output error 6

The software runs correctly despite this.

Unforeseen side-effect of some changes to the init script, fixed in 0.5.3~rc1-0ubuntu1~jcfp2. Thanks for reporting.

Receiving the same error trying to update from 0.5.3~rc1-0ubuntu1~jcfp1~lucid to 0.5.3~rc1-0ubuntu1~jcfp2~lucid:

E: /var/cache/apt/archives/sabnzbdplus_0.5.3~rc1-0ubuntu1~jcfp2~lucid_all.deb: subprocess new pre-removal script returned error exit status 6

When trying to uninstall get:

E: sabnzbdplus: Package is in a very bad inconsistent state - you should  reinstall it before attempting a removal.

When trying to reinstall get:

E: Unable to correct problems, you have held broken packages.

So I am currently unable to remove, reinstall, or update.

I have exactly the same problems. Broken packages, unable to remove, reinstall or update!

Same problem here!

Please fix it!

To fix it manually, just :

sudo gedit /etc/default/sabnzbdplus


In the file, add your username (the Lucid one, to enable to Sabnzbdplus to find your Home) after USER= (without space)
Then comment all the uncommented lines to have the same pattern as below:

# This file is sourced by /etc/init.d/sabnzbdplus
#
# When SABnzbd+ is started using the init script, the
# --daemon option is always used, and the program is
# started under the account of $USER, as set below.
#
# Each setting is marked either "required" or "optional";
# leaving any required setting unconfigured will cause
# the service to not start.

# [required] user or uid of account to run the program as:
USER=YOUR_USER_NAME

# [optional] full path to the configuration file of your choice;
#            otherwise, the default location (in $USER's home
#            directory) is used:
#CONFIG=

# [optional] hostname/ip and port number to listen on:
#HOST=
#PORT=

# [optional] extra command line options, if any:
#EXTRAOPTS=


Then save the file, and in console: sudo apt-get upgrade

It should be OK.

Thank you. I´ll try it out later...

Indeed this bug is triggered only when the init script is not used, i.e. when the USER variable in /etc/default/sabnzbdplus doesn't have a valid user. So adding that there, as Striatum suggests, fixes the upgrade problem. Be sure to revert to your previous "empty" configuration by restoring /etc/default/sabnzbdplus to its original state after the upgrade if you don't want to have the program started as a service on every boot.

I'll release a proper fix later, requiring no such manual interaction. Currently, launchpad is undergoing maintenance, so I can't upload anything right now.

Uploading now. Should work although some debugging output may be shown. Once the newest version has been built and published (status here), upgrading via aptitude should just work, synaptic may complain about broken packages on startup but its usual "Reload, Mark, Apply" sequence shouldn't have a problem. Apt-get might request you run sudo apt-get -f install but is otherwise fine.

Apologies for the inconvenience, my own specific setup is immune to this issue which is why I didn't catch it in normal testing. Murphy's law in action.

Yes, 0.5.3~rc1-0ubuntu1~jcfp3~lucid fixed it.
Thank you very much!

Thank you so much. Now it works!

thx 4 ur fix!

but i still have a problem.
my design is damaged and i cannot get plush back to work again.
is there a way to completely deinstall/remove sabnzbd+ and then reinstall so plush and other skins will work again? (no skin works)...

/€: nvm now it just works Oo"