package tex-common 3.15 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

Bug #1261083 reported by Peter Errity
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tex-common (Ubuntu)
New
Undecided
Unassigned

Bug Description

The error came up on first login after upgrading from 13.4 to 13.10

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
(After upgrade)
$ lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10

2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
$ apt-cache policy tex-common
tex-common:
  Installed: 3.15
  Candidate: 4.04
  Version table:
     4.04 0
        500 http://ie.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
 *** 3.15 0
        100 /var/lib/dpkg/status

3) What you expected to happen
Clean boot after upgrading the system

4) What happened instead
Got the error above on initial login

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: tex-common 3.15
ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
Uname: Linux 3.8.0-34-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: i386
Date: Sun Dec 15 03:12:32 2013
DuplicateSignature: package:tex-common:3.15:ErrorMessage: subprocess installed post-installation script returned error exit status 1
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2012-06-10 (552 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: tex-common
Title: package tex-common 3.15 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to saucy on 2013-12-15 (0 days ago)

Revision history for this message
Peter Errity (perrity) wrote :
Revision history for this message
Peter Errity (perrity) wrote :

update - I am guessing this is related because the file prefixes tha come up are nearly all 'tex.....'

I noticed a warning on the top taskbar and ended up running 'apt-get check'
qhxixh gave numerous dependencies errors and further suggested/led me to

$ sudo apt-get install tex-common -f (didn't fix the problem but suggested next)

$ sudo apt-get install -f (which has fixed something - see below)

sample output

Unpacking replacement texlive-lang-spanish ...
Processing triggers for man-db ...
Processing triggers for install-info ...
(Reading database ... 564819 files and directories currently installed.)
Removing texlive-lang-swedish ...
Removing texlive-lang-tibetan ...
...
(Reading database ... 564696 files and directories currently installed.)
Preparing to replace texlive-latex-base 2012.20120611-5 (using .../texlive-latex-base_2013.2013072$
Unpacking replacement texlive-latex-base ...
Preparing to replace texlive-latex-base-doc 2012.20120611-5 (using .../texlive-latex-base-doc_2013$
Unpacking replacement texlive-latex-base-doc ...
...
Warning: Old configuration style found in /etc/texmf/updmap.d
Warning: For now these files have been included,
Warning: but expect inconsistencies.
Warning: These packages should be rebuild with tex-common.
Warning: Please see /usr/share/doc/tex-common/NEWS.Debian.gz
Warning: found file: /etc/texmf/updmap.d/10lmodern.cfg
...

and eventually completed
now I get successful output from apt-get check

$ sudo apt-get check
Reading package lists... Done
Building dependency tree
Reading state information... Done

How can I know if the original problem is resolved?

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1241563, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
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.