package nautilus-dropbox (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

Bug #937546 reported by krizzna
144
This bug affects 21 people
Affects Status Importance Assigned to Milestone
nautilus-dropbox (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

unmet dependencies prior to install dropbox

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: nautilus-dropbox (not installed)
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.92-0ubuntu1
AptOrdering: nautilus-dropbox: Purge
Architecture: amd64
Date: Tue Feb 21 14:47:40 2012
DpkgTerminalLog:
 Removing nautilus-dropbox ...
 Purging configuration files for nautilus-dropbox ...
 dpkg: error processing nautilus-dropbox (--purge):
  subprocess installed post-removal script returned error exit status 2
ErrorMessage: subprocess installed post-removal script returned error exit status 2
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120220)
SourcePackage: nautilus-dropbox
Title: package nautilus-dropbox (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
krizzna (krizzna-budiman) wrote :
Revision history for this message
Raphaël Hertzog (hertzog) wrote :

Please attach /var/log/apt/term.log. I want to see a former failure recorded in your log file.

In any case, the bug is in dropbox.com's package (version 0.7.1) not in the Ubuntu package (version 0.7.1-2). There's not much that I can do.

Revision history for this message
Snoopyski (sgauvin) wrote :

Works now with the last updates... Tks :-)

Revision history for this message
Raphaël Hertzog (hertzog) wrote :

Snoopyski, are you sure you're referring to the same problem ? (aka this bug is about the post-removal script failing during upgrade... nothing else).

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus-dropbox (Ubuntu):
status: New → Confirmed
Revision history for this message
Raphaël Hertzog (hertzog) wrote :

(Subscribing David Euresti of Dropbox to this bug since this bug is in the official Dropbox package and not in the Ubuntu one)

I looked into this bug even though it's not in the Ubuntu package. The postrm is failing with exitcode 2. After analysing the postrm, and having made some tries, I believe that it's the "apt-key rm 5044912E" (function uninstall_key) that is failing and returning.

┏(ubuntu-devel-i386) rivendell:~/tmp
┗(511)$ sudo apt-key rm 5044912E
gpg: key "5044912E" not found: eof
gpg: 5044912E: delete key failed: eof
┏(ubuntu-devel-i386) rivendell:~/tmp
┗(512)$ echo $?
2

I would suggest to stop relying on apt-key and instead you should provide a keyring file in /usr/share/keyrings/ and just put a symlink to this file in /etc/apt/trusted.gpg.d/ in the postinst configure (and drop that symlink in the postrm purge). It's cleaner.

Otherwise you should either ignore the failure "apt-key rm" or only call it after having it checked that the key to remove is still in APT's keyring.

Revision history for this message
Raphaël Hertzog (hertzog) wrote :

Marking the bug as invalid since it doesn't affect the official ubuntu package.

Changed in nautilus-dropbox (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Raphaël Hertzog (hertzog) wrote :

It would be nice if someone could confirm my analysis. If you have the problem (and still have version 0.7.1 installed, and not 0.7.1-2), please edit /var/lib/dpkg/info/nautilus-dropbox.postrm to add a "set -x" line just after the first line (i.e. after the line that starts with "#!"). Then run "sudo dpkg -P nautilus-dropbox" in a terminal and paste the output here. Thank you in advance.

Revision history for this message
David Euresti (david-dropbox) wrote :

Thanks for the report! We will fix it in the next version.

tags: added: bugpattern-written
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.