[Bug 1940993] [NEW] package tex-common 6.09 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
Public bug reported: I was just upgrading from 16 LTS to 18 LTS to 20 LTS and this popped up. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: tex-common 6.09 ProcVersionSignature: Ubuntu 4.15.0-154.161-generic 4.15.18 Uname: Linux 4.15.0-154-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Tue Aug 24 12:49:22 2021 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-02-13 (2749 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.14 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 2021-08-24 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940993 Title: package tex-common 6.09 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1940993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695557] [NEW] emacs failed during upgrade
Public bug reported: Setting up emacs24 (24.5+1-6ubuntu1) ... Install emacsen-common for emacs24 emacsen-common: Handling install of emacsen flavor emacs24 emacs24: relocation error: /usr/lib/x86_64-linux-gnu/libboost_system.so.1.58.0: symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEED1Ev, version GLIBCXX_3.4.21 not defined in file libstdc++.so.6 with link time reference ERROR: install script from emacsen-common package failed dpkg: error processing package emacs24 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of emacs: emacs depends on emacs24 | emacs24-lucid | emacs24-nox; however: Package emacs24 is not configured yet. Package emacs24-lucid is not installed. Package emacs24-nox is not installed. dpkg: error processing package emacs (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: emacs24 emacs ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gzip'ed tar of /var/log/dist-upgrade/" https://bugs.launchpad.net/bugs/1695557/+attachment/4888123/+files/dist-upgrade.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695557 Title: emacs failed during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1695557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1442674] Re: sysstat log corruption, time isn't changing
Oh okay, I didn't know about -L being hard coded in there, missed that. I just ended up making sure the two cron jobs won't conflict with each other, which is why I was saying it was a configuration error on my part. I did have: */5 * * * * root command -v debian-sa1 > /dev/null && debian-sa1 -L 1 1 59 23 * * * root command -v debian-sa1 > /dev/null && debian-sa1 -L 60 2 But I've gone to: 2-58/2 * * * * root command -v debian-sa1 > /dev/null && debian-sa1 -L 1 1 59 23 * * * root command -v debian-sa1 > /dev/null && debian-sa1 -L 60 2 I'm pretty sure the two were conflicting. I haven't seen any problems since making that change. On Wed, Aug 19, 2015 at 8:39 PM, Bill Cole wrote: > Note that the "-L" flag is hardcoded in the sa1 calls of sadc, so > whatever locking that does is not fixing the issue. Seems like a > possible upstream bug? > > I've had this issue in sysstat data files generated on machines ( n=9 > out of 48 sa?? files from 3 different machines) where the sysstat > resolution has been changed to every 2 minutes by changing this line in > /etc/cron.d/sysstat: > > 5-55/10 * * * * root command -v debian-sa1 > /dev/null && debian- > sa1 1 1 > > To: > > */2 * * * * root command -v debian-sa1 > /dev/null && debian-sa1 1 1 > > I've been able to salvage the files by looking for repeating binary > patterns to figure out the size and offsets of sadc records, finding the > one which is a runt, and rebuilding the file by splicing together the > sections before and after it, making sure the resulting file is > identical in size to the other full-day files that are parseable. This > is not an easily documented process, as it requires eyeballing hexdump > output and making educated guesses, but there are useful tips: > > 1. With "-S XALL" in SADC_OPTIONS, each record is 8-9KB, and for some reason > they seem to alternate between 2 sizes (!) 16 bytes different, e.g. 8528 > bytes & 8544 bytes. > 2. There is a header in the file between 850-900 bytes, so a good place to > start looking for patterns at the end of records (useful!) is ~9K. > 3. EVERY time I've had this problem, the 2nd record has been a runt, 500-1500 > bytes shorter than the normal records. > > Because excising the runt record yields what seems to be a perfectly > good file, my guess is that the root cause is collision between the > 23:59 run and the 00:00 run, with the sadc -L flag for some reason > failing to do its job. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1442674 > > Title: > sysstat log corruption, time isn't changing > > Status in sysstat package in Ubuntu: > Invalid > > Bug description: > I'm seeing some log file corruption in sysstat, the time stamp > occasionally just stops changing. So the output I typically see is > like: > > > # sar > > 12:00:00 AM all 0.00 0.00 0.00 0.00 0.00 > 0.00 > 12:00:00 AM all 0.00 0.00 0.00 0.00 0.00 > 0.00 > 12:00:00 AM all 0.00 0.00 0.00 0.00 0.00 > 0.00 > End of system activity file unexpected > > Typical output should be something like: > > 11:58:01 PM all 0.11 0.00 0.02 0.00 0.00 > 99.87 > 11:59:01 PM all 0.06 0.00 0.02 0.00 0.00 > 99.92 > 12:00:01 AM all 0.03 0.00 0.02 0.00 0.00 > 99.95 > Average:all 0.10 0.00 0.04 0.00 0.00 > 99.86 > > > I'm attaching some example logs files, sa09 is good, sa10 is corrupted. > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: sysstat 10.2.0-1 > ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 > Uname: Linux 3.13.0-46-generic x86_64 > ApportVersion: 2.14.1-0ubuntu3.8 > Architecture: amd64 > Date: Fri Apr 10 14:44:10 2015 > SourcePackage: sysstat > UpgradeStatus: No upgrade log present (probably fresh install) > mtime.conffile..etc.cron.d.sysstat: 2015-03-25T18:44:29.274292 > mtime.conffile..etc.sysstat.sysstat: 2015-03-25T18:44:29.198292 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- Dale Harris rod...@maybe.org rod...@gmail.com /.-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442674] Re: sysstat log corruption, time isn't changing
Yeah, I think is mostly a misconfiguration on my part. You can't overlap the execution of those two crontab lines without having problems, even with the -L flag. I saw some weirdness even with the file locking in place on some of my systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442674] Re: sysstat log corruption, time isn't changing
I finally noticed that sadc has optional file locking with the -L flag, so I suspect that will likely fix my problems. Just going to add -L to the debian-sa1 lines in the /etc/cron.d/sysstat. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103044] Re: outdated version of nodejs (ubuntu 12.04 / 12.10 / 13.04 / 14.04 /14.10/15.04)
Latest stable nodejs version is 0.12.4, seems like it would be better to aim for that in 14.04 LTS and later. But obviously Debian hasn't upgraded anything from upstream in a long time, either. I guess I'll just use the PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103044 Title: outdated version of nodejs (ubuntu 12.04 / 12.10 / 13.04 / 14.04 /14.10/15.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1103044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1442674] Re: sysstat log corruption, time isn't changing
This continues to happen, I did increase the interval of the "debian-sa1 1 1" line in /etc/cron.d/sysstat to */5, but this problem still pops up occasionally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1442674 Title: sysstat log corruption, time isn't changing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1442674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346646] Re: init-functions: status_of_proc has incorrect call to pidofproc
Nevermind this is in error, I just noticed the: if [ -n "$pidfile" ]; then pidfile="-p $pidfile" fi bit in there. So there is no bug. You can close this, if I can't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346646 Title: init-functions: status_of_proc has incorrect call to pidofproc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346646] Re: init-functions: status_of_proc has incorrect call to pidofproc
I removed "A proposed patch", it was bad. ** Patch removed: "A proposed patch" https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+attachment/4159596/+files/init-functions.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346646 Title: init-functions: status_of_proc has incorrect call to pidofproc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346646] Re: init-functions: status_of_proc has incorrect call to pidofproc
I had a copy paste error with that patch. Adding another. ** Patch added: "init-functions.patch" https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+attachment/4159603/+files/init-functions.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346646 Title: init-functions: status_of_proc has incorrect call to pidofproc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346646] [NEW] init-functions: status_of_proc has incorrect call to pidofproc
Public bug reported: Description:Ubuntu 12.04.4 LTS Release:12.04 lsb-base: Installed: 4.0-0ubuntu20.3 Candidate: 4.0-0ubuntu20.3 Version table: *** 4.0-0ubuntu20.3 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 4.0-0ubuntu20 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Appears that the status_of_proc() function in /lib/lsb/init-functions incorrectly calls pidofproc. pidofproc requires a -p switch to specify a pidfile. ** Affects: lsb (Ubuntu) Importance: Undecided Status: New ** Patch added: "A proposed patch" https://bugs.launchpad.net/bugs/1346646/+attachment/4159596/+files/init-functions.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346646 Title: init-functions: status_of_proc has incorrect call to pidofproc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333368] [NEW] man page for rtpproxy is not up to date
Public bug reported: The current man page packaged with rtpproxy doesn't document several of the features available. In particular -m and -M, not mentioned at all in the man page. I'm going to attach the man page from http://www.rtpproxy.org/ ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rtpproxy 1.2.1-1.1 [modified: usr/share/man/man8/rtpproxy.8.gz] ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Jun 23 10:32:43 2014 InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) MarkForUpload: True ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtpproxy UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rtpproxy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ** Attachment added: "man page from http://www.rtpproxy.org/"; https://bugs.launchpad.net/bugs/168/+attachment/4137622/+files/rtpproxy.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/168 Title: man page for rtpproxy is not up to date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtpproxy/+bug/168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
