package slocate 3.1-1ubuntu3 failed to install/upgrade: subprocess pre-installation script returned error exit status 1

Bug #157661 reported by gezzed
274
Affects Status Importance Assigned to Milestone
slocate (Ubuntu)
Fix Released
High
Michael Vogt

Bug Description

Binary package hint: update-manager

ProblemType: Package
Architecture: i386
Date: Sat Oct 27 09:38:28 2007
Package: slocate 3.1-1ubuntu3
SourcePackage: slocate
ErrorMessage:
 subprocess pre-installation script returned error exit status 2
DpkgTerminalLog:

 Log started: 2007-10-27 09:38:26
 (Reading database ... 136738 files and directories currently installed.)

 Preparing to replace slocate 3.1-1ubuntu1 (using .../slocate_3.1-1ubuntu3_i386.deb) ...

 Removing `diversion of /etc/cron.daily/find to /etc/cron.daily/find.notslocate by slocate'

 dpkg-divert: rename involves overwriting `/etc/cron.daily/find' with

   different file `/etc/cron.daily/find.notslocate', not allowed

 dpkg: error processing /var/cache/apt/archives/slocate_3.1-1ubuntu3_i386.deb (--unpack):

  subprocess pre-installation script returned error exit status 2

ProblemType: Package
Architecture: i386
Date: Sat Oct 27 09:35:43 2007
DistroRelease: Ubuntu 7.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /tmp/tmpxCnfUH/backports/usr/bin/dpkg returned an error code (1), E:Sub-process /tmp/tmpxCnfUH/backports/usr/bin/dpkg returned an error code (1)

Package: update-manager 1:0.81
PackageArchitecture: all
SourcePackage: update-manager
Title: package update-manager 1:0.81 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /tmp/tmpxCnfUH/backports/usr/bin/dpkg returned an error code (1), E:Sub-process /tmp/tmpxCnfUH/backports/usr/bin/dpkg returned an error code (1)
Uname: Linux goide 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux

Revision history for this message
gezzed (gsosullivan) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bugreport as attachments to your bug report? Thanks in advance.

Changed in update-manager:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
cipher27 (cipher27) wrote :

hello,

I experienced this error today while upgrading from feisty. I have attached the requested files.

Revision history for this message
Justin "J" Lynn (jaesharp) wrote :

Workaround: error fixed by uninstalling slocate and re-installing updated package

Revision history for this message
evets (itsmewhoelse) wrote :

logs attached

Revision history for this message
Andrew Conkling (andrewski) wrote :

Renamed bug description to match apport's auto-generated description.

Revision history for this message
Phoenix591 (phoenix591) wrote :

same error here. oh and also upgrading to Hardy on Kubuntu adept fails with a command not found error after downloading the updater after pushing the button in adept.

Revision history for this message
riri (girardhenri) wrote : Re: [Bug 157661] Re: package slocate 3.1-1ubuntu3 failed to install/upgrade: subprocess pre-installation script returned error exit status 1

after a fresh install of kubuntu gutsy (64 bits) and updating it as
"gutsy" i upgraded like you (i think)
adept_manager --dist-upgrade-devel
Most of the time the upgrading is not fully done...
so I go in console and finished it with aptitude full-upgrade
and /or dpkg --configure -a as few debs are broken...
When it's done after there is rarely problems...
and always the same solution : wait till they update the broken links !!!
and with aptitude...

u
Kyle Elbert a écrit :
> same error here. oh and also upgrading to Hardy on Kubuntu adept fails
> with a command not found error after downloading the updater after
> pushing the button in adept.
>
>

Revision history for this message
David Baucum (maxolasersquad) wrote :

I got the same problem here.

Revision history for this message
kaotiks@gmail.com (kaotiks) wrote :

Same issue, added all logs from /var/log/dist-upgrade to see if they could lend a hand.

Revision history for this message
Shawn McMahon (smcmahon) wrote :

Workaround is easy:

sudo dpkg --ignore-depends slocate --remove slocate && sudo aptitude install slocate

Putting this comment here so when folks search for this bug they'll see how to fix it.

Revision history for this message
kaotiks@gmail.com (kaotiks) wrote :

Shawn's workaround worked like a charm.

Thanks for the help, hope I can return the favor.

Revision history for this message
reh4c (gene-hoffler) wrote :

Thanks, Shawn. Problem appears to be solved.

Revision history for this message
thomashenryboehm (thomasboehm) wrote :

Thank-you.

Revision history for this message
thomashenryboehm (thomasboehm) wrote :

Thank-ou

Revision history for this message
thomashenryboehm (thomasboehm) wrote :

Thank-you.

Revision history for this message
Matthew McGowan (mmcg069) wrote :

I had a similar issue upgrading my system in Hardy.

Preparing to replace slocate 3.1-1ubuntu3 (using .../slocate_3.1-1.1ubuntu1_i386.deb) ...
===============================================
===Error. The following diversions still exist:
diversion of /usr/bin/locate to /usr/bin/locate.notslocate by slocate
diversion of /usr/bin/updatedb to /usr/bin/updatedb.notslocate by slocate
diversion of /usr/share/man/man1/locate.1.gz to /usr/share/man/man1/locate.notslocate.1.gz by slocate
diversion of /usr/share/man/man1/updatedb.1.gz to /usr/share/man/man1/updatedb.notslocate.1.gz by slocate
===============================================
dpkg: error processing /var/cache/apt/archives/slocate_3.1-1.1ubuntu1_i386.deb (--unpack):
 subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/slocate_3.1-1.1ubuntu1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Alex Mayorga (alex-mayorga) wrote :

How to "re-dist-upgrade" if an initial upgrade has failed because of this bug?

GRUB still shows 7.10 when booting. How can I confirm if the PC is now on Hardy and convince GRUB of it.

Thanks in advance.

Revision history for this message
Michael Vogt (mvo) wrote :

The gutsy->hardy issue is fixed with the 3.1-1.1ubuntu2

Changed in slocate:
assignee: nobody → mvo
Revision history for this message
Stanley Sokolow (overbyte) wrote : Re: [Bug 157661] Re: package slocate 3.1-1ubuntu3 failed to install/upgrade: subprocess pre-installation script returned error exit status 1

[Hardy 8.04 alpha-1] I am confirming that the bug is fixed. When I ran
system update after receiving the following message, the issue is
resolved and slocate installed without the crash and error message it
used to cause. Thanks.

On Tue, 2007-12-18 at 18:54 +0000, Michael Vogt wrote:
> The gutsy->hardy issue is fixed with the 3.1-1.1ubuntu2
>
> ** Changed in: slocate (Ubuntu)
> Assignee: (unassigned) => Michael Vogt (mvo)
>

Revision history for this message
Andrew Conkling (andrewski) wrote :

Marking fixed then. Please reopen if the problem re-presents itself.

Changed in slocate:
status: Confirmed → Fix Released
Revision history for this message
Magnus Malmsten (magnus-malmsten) wrote :

Thank you,
workaraund did work for me.

Revision history for this message
songstruck (fininfo) wrote :

I've been running Gutsy successfully for months. Decided to try Xubuntu today and ran:
sudo apt-get install xubuntu-desktop

The install failed, generating the slocate error on this page. I tried the workaround:
sudo dpkg --ignore-depends slocate --remove slocate && sudo aptitude install slocate

but that also failed. In any case, how does it make sense to --remove slocate when slocate won't install?

I've tried the usual sudo apt-get install -f, but can't get past this slocate problem.

Any new suggestions? Thanks.

Revision history for this message
Alfredo Gemma (alfredo-gemma) wrote : Re: [Bug 157661] Re: package slocate 3.1-1ubuntu3 failed to install/upgrade: subprocess pre-installation script returned error exit status 1
  • unnamed Edit (1.3 KiB, text/html; charset=ISO-8859-1)

I made a fresh install of Hardy: the problem seems to be definitively fixed

On Wed, Apr 30, 2008 at 8:59 PM, songstruck <email address hidden> wrote:

> I've been running Gutsy successfully for months. Decided to try Xubuntu
> today and ran:
> sudo apt-get install xubuntu-desktop
>
> The install failed, generating the slocate error on this page. I tried the
> workaround:
> sudo dpkg --ignore-depends slocate --remove slocate && sudo aptitude
> install slocate
>
> but that also failed. In any case, how does it make sense to --remove
> slocate when slocate won't install?
>
> I've tried the usual sudo apt-get install -f, but can't get past this
> slocate problem.
>
> Any new suggestions? Thanks.
>
> --
> package slocate 3.1-1ubuntu3 failed to install/upgrade: subprocess
> pre-installation script returned error exit status 1
> https://bugs.launchpad.net/bugs/157661
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
songstruck (fininfo) wrote :

OK, problem is fixed in Hardy. That's not a solution for me as I'm still running Gutsy and can't afford additional upgrade issues right now.

For others like me, I was able to resolve this issue. The original error messages mention a problem overwriting /etc/cron.daily/find. I moved the file out of /etc/cron.daily and was able to move forward and install slocate. I'm not sure what impact this will have, but it's better than being stuck with an unfixable "broken index" issue.

I was still left with issues, but most of these were resolved by shutting down services that were mentioned in the error messages before running sudo apt-get install -f.

My apologies if this is the wrong forum for this kind of info. It seems that slocate error searches on Google will most likely direct you here. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.