package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

Asked by mohan on 2017-04-11

system gets hang whenever multiple apps are running simultaneously, i have to remove the battery to make it again work......

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: deja-dup 34.2-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
AptOrdering:
 file-roller:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Apr 11 12:18:26 2017
DpkgTerminalLog:
 Preparing to unpack .../file-roller_3.22.1-0ubuntu1_amd64.deb ...
 Unpacking file-roller (3.22.1-0ubuntu1) over (3.22.0-1ubuntu1) ...
 dpkg: error processing package deja-dup (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
DuplicateSignature:
 package:deja-dup:34.2-0ubuntu3.1
 Unpacking file-roller (3.22.1-0ubuntu1) over (3.22.0-1ubuntu1) ...
 dpkg: error processing package deja-dup (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
InstallationDate: Installed on 2017-04-10 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.4
SourcePackage: deja-dup
Title: package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

Question information

Naël (nathanael-naeri) said : #1

I'm converting this bug report to a question, as it doesn't appear to be a bug in Déjà-Dup (upstream or package), but a support request after an installation failure.

Please comment and/or convert the question back to a bug if more help is needed and/or more information can be provided and/or it turns out to be a bug.

Naël (nathanael-naeri) said : #2

@mohan:

Please close this question if the information provided in bug 1681679 comment 2 solves your issue.

Can you help with this problem?

Provide an answer of your own, or ask mohan for more information if necessary.

To post a message you must log in.