- Subprocess Installed Post-installation Script Cydia
- Cydia Subprocess Post-installation Script Returned Error Exit Status 1
I went to install bsnes the other day and for whatever reason the installation failed. Now, I cannot update, install new packages, or do basically any apt-get commands as they all try to process this broken package and fail. Attempting to install a new package also just dooms it to the same fate. The error I get is: Setting up google-chrome-stable (33.0.1750.152-1). /var/lib/dpkg/info/google-chrome-stable.postinst: 124: /var/lib/dpkg/info/google-chrome-stable.postinst: update-alternatives: not found dpkg: error processing google-chrome-stable (-configure): subprocess installed post-installation script returned error exit status 127 Setting up bsnes (0.088-7). /var/lib/dpkg/info/bsnes.postinst: 5: /var/lib/dpkg/info/bsnes.postinst: update-alternatives: not found dpkg: error processing bsnes (-configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: google-chrome-stable bsnes E: Sub-process /usr/bin/dpkg returned an error code (1) I have been searching on Google and here on Ask Ubuntu but have not found a working solution.
The commonly suggested fix is to run the following: sudo apt-get clean && sudo apt-get autoremove sudo apt-get -f install sudo dpkg -configure -a This however does not work. The apt-get commands all fail with the same error as above and the dpkg command just doesn't help. The other thing they often suggest to purge it via Synaptic or the command line, which also fails. Thanks for the help. For advanced users, use at your own risks. According to the following error message: subprocess installed post-installation script returned error exit status 127 You may want to edit /var/lib/dpkg/info/packagename.postinst and comment everything (or better yet, try to understand it and identify the issue), then try apt-get again. Note that though in this particular question the message concerns 'post-installation', it could have mentioned e.g.
'pre-removal' or 'post-removal' instead (in which cases the extension of the file to be edited would have been.prerm or.postrm). Other than those which you have already posted, there are few other commands which can be helpful.
Autoclean clears out the local repository of retrieved package files. Sudo apt-get autoclean. Force installation/removal of packages. ☠Use with caution sudo apt-get -force-yes install and sudo apt-get -force-yes remove Also as always, you can use dpkg to install, remove and purge packages.
Install sudo dpkg -i. Remove sudo dpkg -r. Purge sudo dpkg -P.
• Introduction Congratulations on having chosen the cycle computer with altimeter functions from ECHOWELL. Echowell ecr2 user manual.
Help I am really new to all of this, could you give me some details on how you fixed this, I am experiencing the exact same thing right now, and I have tried everything and can't find anything online that has the same errors that I am getting, here are the 2 that I get everytime I try to install something while I am in Cydia. Subprocess post-installation script returned error exit status 255 2. Subprocess/usr/bin/dpkg returned an error code (1) I am very frustrated this happens everytime I try to install anything then I get a warning telling me to either remove the install or reinstall it, which of course does no good. If you could tell me how to fix this (please remember I am very, very new to all of this & I know nothing I am learning from YouTube and reading everything I can find) so please treat me as a newbie! I would appreciate it so much and you will be my hero for the day! Thank you so very much!
Subprocess Installed Post-installation Script Cydia
How To Fix Cydia Error Code 1; cydia sub-process /usr/bin/dpkg returned an error code (1) Method 2 IMPORTANT: USER WITH THEMES & FONTS TWEAK IS NOT RECOMENDED TO USE THIS METHOD BEFORE REMOVING THE TWEAKS -THEMES AND FONTS TWEAKS. SOME PEOPLE REPORT THAT THIS METHOD CAN BRICK UR DEVICE, DO IT CAREFULLY WITH YOUR OWN RISK!! ESPECIALLY FOR IOS 10 JAILBREAK!!
Cydia Subprocess Post-installation Script Returned Error Exit Status 1
![Subprocess installed post-installation script cydia Subprocess installed post-installation script cydia](/uploads/1/2/3/8/123812726/615623567.png)
![Subprocess Post Installation Script Cydia Subprocess Post Installation Script Cydia](/uploads/1/2/3/8/123812726/850247523.jpg)
How To Fix Cydia Error Code 1; cydia sub-process /usr/bin/dpkg returned an error code (1) Method 2 IMPORTANT: USER WITH THEMES & FONTS TWEAK IS NOT RECOMENDED TO USE THIS METHOD BEFORE REMOVING THE TWEAKS -THEMES AND FONTS TWEAKS. SOME PEOPLE REPORT THAT THIS METHOD CAN BRICK UR DEVICE, DO IT CAREFULLY WITH YOUR OWN RISK!! ESPECIALLY FOR IOS 10 JAILBREAK!!
I've seen this message several times whenever someone has a problem installing, upgrading or removing some piece of software, but I wonder, what does it mean, and more importantly, is possible to solve it? (Reading database. 81657 files and directories currently installed.) Removing mongodb-10gen. Arg: remove invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found.
Dpkg: error processing mongodb-10gen (-remove): subprocess installed pre-removal script returned error exit status 100 invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found. Dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 100 Errors were encountered while processing: mongodb-10gen E: Sub-process /usr/bin/dpkg returned an error code (1) (the above is just an example, not my actual problem). That message is generic.
It just means that the dpkg instance called by apt/ apt-get failed for some reason. It doesn't explain why, how, or give hints how to solve it. As a diagnostic message, it is not useful. You need to read the lines before the message (sometimes quite a number of them) to find the real error that prevents you from completing the installation.
Yeah, but how do I solve it? There is no single way to solve it. There are so many reasons why this can happen that it's futile to attempt to list them all in a single post. Each and every circumstance is almost unique to that package/environment.
But, there's redemption. The fact that you see this message means that probably there is more relevant information in the lines before the message. For illustrative purposes I will use a example: (Reading database. 81657 files and directories currently installed.) Removing mongodb-10gen. Arg: remove invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found.
Dpkg: error processing mongodb-10gen (-remove): subprocess installed pre-removal script returned error exit status 100 invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found. Dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 100 Errors were encountered while processing: mongodb-10gen E: Sub-process /usr/bin/dpkg returned an error code (1) Now, to find the problem, you need to read backwards:.
![Cydia Cydia](/uploads/1/2/3/8/123812726/565601046.png)
E: Sub-process /usr/bin/dpkg returned an error code (1) doesn't tell me anything useful. So moving on. Errors were encountered while processing: mongodb-10gen just tells me what package have problems. Is useful but not enough. subprocess installed post-installation script returned error exit status 100: this tells me that the script that failed was the postinst, the one executed in post-installation.
This will come handy in some situations, but not in this one. dpkg: error while cleaning up: nothing useful here.
invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found. This tells us that invoke-rc.d, a binary that controls the init script in most Debian-like system, failed. It failed because it couldn't find the /etc/init.d/mongodb script. We need to create it or copy from somewhere else so it starts working again.
Reinstalling the package is also normally an option for file not found errors. In this case, reporting a bug is not necessary because is probable that we were the ones that removed the script, but if you are completely sure you didn't touch the file (a debsums -sla should confirm it) then report a bug. So, what exactly do you need to get help? Ideally, the complete output of the problem. It's also helpful to include the output of sudo dpkg -C and sudo apt-get check, and the output of apt-cache policy package1 package2. Where 'package1 package2.' Includes all the packages with problems.