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

Bug #1746865 reported by Ravindra Gullapalli
268
This bug affects 29 people
Affects Status Importance Assigned to Milestone
tex-common (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I was updating the packages provided by the software updater.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: tex-common 6.09
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.8-0ubuntu7
Architecture: amd64
Date: Thu Feb 1 15:31:53 2018
ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.4ubuntu1
 apt 1.6~alpha7ubuntu1
SourcePackage: tex-common
Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Ravindra Gullapalli (sharewithravig) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in tex-common (Ubuntu):
status: New → Confirmed
Revision history for this message
David Hansen (dchansen) wrote :
Download full text (4.9 KiB)

My apologies, I did not see this report when I created a duplicate issue (https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1781002 Bug #1781002 ).

I encountered this bug three days ago when I performed a fresh 16.04 install and then immediately upgraded to 18.04 via "do-release-upgrade -d". I will paste the info below but in summary, generating the en_DK.UTF-8 locale seems to be what was needed.

The error occurred during a "do-release-upgrade -d" on a fresh v16.04 installation to bring it up to v18.04.

Errors were encountered while processing:
 tex-common
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: tex-common 6.09
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jul 10 10:44:28 2018
ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.2
SourcePackage: tex-common
Title: package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-07-10 (0 days ago)

Choices:
  1: Launch a browser now
  C: Cancel
Please choose (1/C): c

Could not install the upgrades

The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).

Setting up tex-common (6.09) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
        This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.UIihIvhv
Please include this file if you report a bug.

dpkg: error processing package tex-common (--configure):
 installed tex-common package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 tex-common

Upgrade complete

The upgrade has completed but there were errors during the upgrade
process.

To continue please press [ENTER]
=== Command detached from window (Tue Jul 10 11:42:28 2018) ===
=== Command terminated with exit status 1 (Tue Jul 10 11:42:38 2018) ===
[screen is terminating]

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic

apt-cache policy tex-common
tex-common:
  Installed: 6.09
  Candidate: 6.09
  Version table:
 *** 6.09 500
        500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages
        100 /var/lib/dpkg/status

apt-get --reinstall install tex-common
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
1 not fully in...

Read more...

Revision history for this message
Thomas Templin (coastgnu) wrote :
Download full text (3.6 KiB)

Same here.
Also after a dist-upgrade from 16.04 to 18.04:

moved all entries in /var/lib/locales/supported.d to dot-files:
--8<--
$ ls -al /var/lib/locales/supported.d
insgesamt 24
drwxr-xr-x 2 root root 4096 Jul 24 05:02 .
drwxr-xr-x 3 root root 4096 Dez 18 2010 ..
-rw-r--r-- 1 root root 126 Jul 17 10:35 .de
-rw-r--r-- 1 root root 294 Jul 17 10:28 .en
-rw-r--r-- 1 root root 26 Okt 12 2017 .nds
-rw-r--r-- 1 root root 48 Jul 17 10:44 .nl
-->8--

set locales to:
--8<--
$ grep -v \# /etc/locale.gen
de_DE.UTF-8 UTF-8
en_US.UTF-8 UTF-8
-->8--

regenerated locales:
--8<--
$ sudo locale-gen --purge
Generating locales (this might take a while)...
  de_DE.UTF-8... done
  en_US.UTF-8... done
Generation complete.
-->8--

tex-common is stil broken:
--8<--
$ sudo dpkg --configure -a
tex-common (6.09) wird eingerichtet ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... done.
Running mktexlsr /var/lib/texmf ... done.
Building format(s) --all.
 This may take some time...
fmtutil failed. Output has been stored in
/tmp/fmtutil.iBipwgIc
Please include this file if you report a bug.

dpkg: Fehler beim Bearbeiten des Paketes tex-common (--configure):
 Unterprozess installed tex-common package post-installation script gab den Fehler-Ausgangsstatus 1 zurück
Fehler traten auf beim Bearbeiten von:
 tex-common
-->8--

File /tmp/fmtutil.iBipwgIc has two emergency stops:
--8<-- 1st stop --8<--
fmtutil: running `luatex -ini -jobname=lualatex -progname=lualatex lualatex.ini' ...
This is LuaTeX, Version 1.0.4 (TeX Live 2017/Debian) (INITEX)
 restricted system commands enabled.
(/usr/share/texlive/texmf-dist/tex/latex/zxjatype/latexconfig/lualatex.ini
(/var/lib/texmf/tex/generic/config/pdftexconfig.tex
! Undefined control sequence.
l.6 \pdfoutput
                       = 1
?
! Emergency stop.
l.6 \pdfoutput
                       = 1
! ==> Fatal error occurred, bad output DVI file produced!
No pages of output.
Transcript written on lualatex.log.
-->8--

--8<--2nd stop --8<--
fmtutil: running `luatex -ini -jobname=dvilualatex -progname=dvilualatex dvilualatex.ini' ...
This is LuaTeX, Version 1.0.4 (TeX Live 2017/Debian) (INITEX)
 restricted system commands enabled.
(/usr/share/texlive/texmf-dist/tex/generic/tex-ini-files/dvilualatex.ini
(/usr/share/texlive/texmf-dist/tex/latex/zxjatype/latexconfig/lualatex.ini
(/var/lib/texmf/tex/generic/config/pdftexconfig.tex
! Undefined control sequence.
l.6 \pdfoutput
                       = 1
?
! Emergency stop.
l.6 \pdfoutput
                       = 1
! ==> Fatal error occurred, bad output DVI file produced!
No pages of output.
Transcript written on dvilualatex.log
-->8--

There is no lualatex.log only a dvilualatex.log exists:
--8<--
$ sudo find / -type f -iname "*lualatex.log*"
/root/dvilualatex.log
-->8--

so the log says:
--8<--
$ sudo cat /root/dvilualatex.log
This is LuaTeX, Version 0.95.0 (TeX Live 2016/Debian) (INITEX) 9 SEP 2017 14:17
 restricted system commands enabled.
**dvilualatex.ini
(/usr/share/texlive/texmf-dist/tex/generic/tex-ini-files/dvilualatex.ini
(/usr/share/texlive/texmf-dist/tex/latex/zxjatype/latexconfig/lualatex.ini
! I can't find f...

Read more...

To post a comment you must log in.