*** This bug is a duplicate of bug 948294 ***
    https://bugs.launchpad.net/bugs/948294

** This bug has been marked a duplicate of bug 948294
   package gconf2 3.2.3-3ubuntu1 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 250

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/952453

Title:
  package gconf2 3.2.4-0ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 250

Status in “gconf” package in Ubuntu:
  New

Bug description:
  first had a complaint during gconf upgrade that libgconf version would
  break gconf less than the version I was attempting to upgrade but the
  older version that should have been removed to make way for the newer
  version was being configured.

  Then purged gconf2 attempted 'apt-get install' and 'apt-get -f
  install' which then results in the following message

  GConf-CRITICAL **: No such file `/usr/lib/i386-linux-gnu/gconf/2
  /libgconfbackend-xml.so'

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: gconf2 3.2.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Sun Mar 11 11:37:53 2012
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 250
  SourcePackage: gconf
  Title: package gconf2 3.2.4-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 250
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/952453/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to