[Touch-packages] [Bug 1843658] Re: package zlib1g 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: zlib (Ubuntu) Importance: Undecided => Low ** Changed in: zlib (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1843658 Title: package zlib1g 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 Status in zlib package in Ubuntu: Invalid Bug description: (Reading database ... 603754 files and directories currently installed.) Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb ... Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 Processing triggers for libc-bin (2.23-0ubuntu10) ... Errors were encountered while processing: /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zlib1g 1:1.2.8.dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptOrdering: zlib1g: Install zlib1g: Configure zlib1g: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 12 08:47:03 2019 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2019-09-12 08:46:40 Commandline: apt-get -f install Requested-By: seisinv (1000) Upgrade: zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4, 1:1.2.8.dfsg-2ubuntu4.1) DpkgTerminalLog: Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb ... Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 DuplicateSignature: package:zlib1g:1:1.2.8.dfsg-2ubuntu4 Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 InstallationDate: Installed on 2017-06-02 (831 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.29ubuntu0.1 SourcePackage: zlib Title: package zlib1g 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1843658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453580] Re: package libgsm1:amd64 1.0.13-4 failed to install/upgrade: package libgsm1:amd64 is already installed and configured
I am the Debian maintainer of this package and believe the issue was resolved. Closing this bug. ** Changed in: libgsm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgsm in Ubuntu. https://bugs.launchpad.net/bugs/1453580 Title: package libgsm1:amd64 1.0.13-4 failed to install/upgrade: package libgsm1:amd64 is already installed and configured Status in libgsm package in Ubuntu: Fix Released Bug description: when starting computer there is message in desktop ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgsm1:amd64 1.0.13-4 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Sun May 3 19:00:39 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libgsm1:amd64:1.0.13-4:package libgsm1:amd64 is already installed and configured ErrorMessage: package libgsm1:amd64 is already installed and configured InstallationDate: Installed on 2015-05-01 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: libgsm Title: package libgsm1:amd64 1.0.13-4 failed to install/upgrade: package libgsm1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgsm/+bug/1453580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 672485] Re: package libgsm1 1.0.13-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
I am the Debian maintainer of this package and believe the issue was resolved. Closing this bug. ** Changed in: libgsm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgsm in Ubuntu. https://bugs.launchpad.net/bugs/672485 Title: package libgsm1 1.0.13-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in libgsm package in Ubuntu: Fix Released Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libgsm1 1.0.13-3 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Mon Nov 8 15:04:31 2010 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) SourcePackage: libgsm Title: package libgsm1 1.0.13-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgsm/+bug/672485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1517363] Re: package libgsm1 (not installed) failed to install/upgrade: unable to stat `./usr/share/doc/libgsm1' (which I was about to install): Input/output error
I am the Debian maintainer of this package and believe the issue was resolved. Closing this bug. ** Changed in: libgsm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgsm in Ubuntu. https://bugs.launchpad.net/bugs/1517363 Title: package libgsm1 (not installed) failed to install/upgrade: unable to stat `./usr/share/doc/libgsm1' (which I was about to install): Input/output error Status in libgsm package in Ubuntu: Fix Released Bug description: Brand new installation of Ubuntu 14.04 with loads of problems popping up ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgsm1 (not installed) ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 Date: Wed Nov 18 09:38:20 2015 DuplicateSignature: package:libgsm1:(not installed):unable to stat `./usr/share/doc/libgsm1' (which I was about to install): Input/output error ErrorMessage: unable to stat `./usr/share/doc/libgsm1' (which I was about to install): Input/output error InstallationDate: Installed on 2015-11-18 (0 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) SourcePackage: libgsm Title: package libgsm1 (not installed) failed to install/upgrade: unable to stat `./usr/share/doc/libgsm1' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgsm/+bug/1517363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270629] Re: the 32bit version of libgsm1 package is broken on Ubuntu 12.04 64bit
I am the Debian maintainer of this package and believe the issue was resolved. Closing this bug. ** Changed in: libgsm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgsm in Ubuntu. https://bugs.launchpad.net/bugs/1270629 Title: the 32bit version of libgsm1 package is broken on Ubuntu 12.04 64bit Status in libgsm package in Ubuntu: Fix Released Bug description: Hello Some software, like CrossOver relies of 32bit version of various libs to provide various functionality that Windows applications require. Upon attempting to install libgsm1:i386 two things might happen: 1) the package manager will try to uninstall the 64bit version of this lib and others 2) a message like this gets printed on screen: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgsm1 : Conflicts: libgsm1:i386 but 1.0.13-3 is to be installed libgsm1:i386 : Conflicts: libgsm1 but 1.0.13-3 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. This does not happen on 64 bit versions of Ubuntu 13.10 and 14.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgsm1:i386 (not installed) ProcVersionSignature: Ubuntu 3.11.0-15.23~precise1-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Jan 19 21:29:48 2014 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libgsm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgsm/+bug/1270629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 992933] Re: package libgsm1 1.0.13-3 failed to install/upgrade: libgsm1:i386 1.0.13-3 (Multi-Arch
I am the Debian maintainer of this package and believe the issue was resolved. Closing this bug. ** Changed in: libgsm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgsm in Ubuntu. https://bugs.launchpad.net/bugs/992933 Title: package libgsm1 1.0.13-3 failed to install/upgrade: libgsm1:i386 1.0.13-3 (Multi-Arch Status in libgsm package in Ubuntu: Fix Released Bug description: I just updated ubuntu ppassando relase from 11.10 to 12.04. I ran an update request and tried to install the proposed updates updates from management, but there was this bag described. What can I do? ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libgsm1 1.0.13-3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 2 00:35:54 2012 DpkgTerminalLog: dpkg: errore nell'elaborare /var/cache/apt/archives/libgsm1_1.0.13-3_i386.deb (--unpack): libgsm1:i386 1.0.13-3 (Multi-Arch: no) is not co-installable with libgsm1:amd64 1.0.13-3 (Multi-Arch: no) which is currently installed ErrorMessage: libgsm1:i386 1.0.13-3 (Multi-Arch InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: libgsm Title: package libgsm1 1.0.13-3 failed to install/upgrade: libgsm1:i386 1.0.13-3 (Multi-Arch UpgradeStatus: Upgraded to precise on 2012-05-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgsm/+bug/992933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832787] Re: fontconfig 2.12 in 18.04 causes firefox to freeze when launching chrome
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1832787 Title: fontconfig 2.12 in 18.04 causes firefox to freeze when launching chrome Status in fontconfig package in Ubuntu: Confirmed Bug description: fontconfig version: 2.12.6-0ubuntu2 Related: https://askubuntu.com/questions/1076412/firefox-freezing-with-100-cpu- usage-for-30-seconds-when-launching-chromium https://bugzilla.mozilla.org/show_bug.cgi?id=1495900 https://bugzilla.mozilla.org/show_bug.cgi?id=1411338 Steps to reproduce: 1) Launch firefox, open a few tabs 2) Launch chrome 3) Go back to firefox, and notice it starts being very slow, switching tabs do nothing (the content area remains blank). 4) Backport fontconfig 2.13 from cosmic to bionic 5) Try to reproduce 1-3, be happy because it is now working fine! I backported 2.13.0-5ubuntu3 from cosmic to bionic, if that helps. I don't have the right setup right now to do a bisect from upstream or from debian patches sadly. ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1832787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843658] Re: package zlib1g 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1843658 Title: package zlib1g 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 Status in zlib package in Ubuntu: New Bug description: (Reading database ... 603754 files and directories currently installed.) Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb ... Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 Processing triggers for libc-bin (2.23-0ubuntu10) ... Errors were encountered while processing: /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zlib1g 1:1.2.8.dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptOrdering: zlib1g: Install zlib1g: Configure zlib1g: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 12 08:47:03 2019 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2019-09-12 08:46:40 Commandline: apt-get -f install Requested-By: seisinv (1000) Upgrade: zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4, 1:1.2.8.dfsg-2ubuntu4.1) DpkgTerminalLog: Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb ... Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 DuplicateSignature: package:zlib1g:1:1.2.8.dfsg-2ubuntu4 Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 InstallationDate: Installed on 2017-06-02 (831 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.29ubuntu0.1 SourcePackage: zlib Title: package zlib1g 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1843658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843658] [NEW] package zlib1g 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from oth
Public bug reported: (Reading database ... 603754 files and directories currently installed.) Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb ... Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 Processing triggers for libc-bin (2.23-0ubuntu10) ... Errors were encountered while processing: /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zlib1g 1:1.2.8.dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptOrdering: zlib1g: Install zlib1g: Configure zlib1g: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 12 08:47:03 2019 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2019-09-12 08:46:40 Commandline: apt-get -f install Requested-By: seisinv (1000) Upgrade: zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4, 1:1.2.8.dfsg-2ubuntu4.1) DpkgTerminalLog: Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb ... Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 DuplicateSignature: package:zlib1g:1:1.2.8.dfsg-2ubuntu4 Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 InstallationDate: Installed on 2017-06-02 (831 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.29ubuntu0.1 SourcePackage: zlib Title: package zlib1g 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zlib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1843658 Title: package zlib1g 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 Status in zlib package in Ubuntu: New Bug description: (Reading database ... 603754 files and directories currently installed.) Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb ... Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/zlib1g/changelog.Debian.gz', which is different from other instances of package zlib1g:amd64 Processing triggers for libc-bin (2.23-0ubuntu10) ... Errors were encountered while processing: /var/cache/apt/archives/zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zlib1g 1:1.2.8.dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptOrdering: zlib1g: Install zlib1g: Configure zlib1g: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Sep 12 08:47:03 2019 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2019-09-12 08:46:40 Commandline: apt-get -f install Requested-By: seisinv (1000) Upgrade: zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4, 1:1.2.8.dfsg-2ubuntu4.1) DpkgTerminalLog: Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_amd64.deb ... Unpacking zlib1g:amd64 (1:1.2.8.dfsg-2ubuntu4.1) over (1:1.2.8.dfsg-2ubuntu4) ...
[Touch-packages] [Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
** Changed in: evolution-data-server Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1843627 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() Status in evolution-data-server: New Status in evolution-data-server package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evolution/issues/616 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:41:26 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi PC (0x7f36355653ae) ok source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: tcache_get (tc_idx=) at malloc.c:2937 __GI___libc_malloc (bytes=32) at malloc.c:3051 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes
@xnox Your updated patch (https://github.com/systemd/systemd/commit/50b9974aee29efb8118a20360b0d521f58110afd) on the GH issue fixes this issue AFAICT. Can we have the patch updated in Ubuntu? I'm happy to make a debdiff.. but it is all your patches.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1796501 Title: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: In Progress Bug description: I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the following steps: 1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size. 2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit. 3. Ask upstream for SOA of test.asdf. with EDNS0. 4. Ask upstream for SOA of test.asdf. without EDNS0. 5. Repeat 1-4 for DS of test.asdf. 6. Repeat 1-5 for asdf. 7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size. 8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size. The upstream returns an unfragmented NXDOMAIN response for steps 1-6, an unfragmented NOERROR response for step 7 and a fragmented NOERROR response for step 8 which is the correct behaviour. DNSSEC records are included in the response if the DO-bit in the request was set. systemd-resolved should take the response from step 1 and start with validation instead of starting useless retries with reduced feture set. Step 3 and 4 are completely useless and probably lead to the SERVFAIL because I have configured it with DNSSEC=yes to prevent downgrade attacks. This regression seems to be caused by the patch resolved-Mitigate- DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic should only be executed if it is configured as DNSSEC=allow-downgrade or DNSSEC=no. See also https://github.com/systemd/systemd/pull/8608#issuecomment-396927885. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome
I can't say for certain if the issue resides with ssh-askpass-fullscreen or is a UI usability issue in unity, gnome, or elsewhere, however this UI is not driven by OpenSSH itself, so I'll retarget this bugtask to ssh-askpass-fullscreen as a slightly more likely candidate. ** Package changed: openssh (Ubuntu) => ssh-askpass-fullscreen (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1843201 Title: Unity in Wayland prompts for keyboard focus on each run of ssh- askpass-gnome Status in gnome-desktop package in Ubuntu: New Status in ssh-askpass-fullscreen package in Ubuntu: Incomplete Status in unity package in Ubuntu: New Bug description: When using a Wayland-based Unity session on Ubuntu 19.04: 1. Have ssh-askpass-gnome as your askpass program. 2. ssh-add -c 3. `ssh` to a host Each time, before the ssh-askpass prompt is shown, Unity shows this dialog: +-+ | | | ssh-askpass wants to inhibit shortcuts | | | | You can restore Shortcuts by pressing | | Super+Escape. | | | |_| | Deny | Allow | +-+ This is mildly distracting, and it means that you need to hit , answer, , instead of just answer . ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ssh-askpass-gnome 1:7.9p1-10 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 15:04:25 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1843201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional
Retriaging these down to Medium. People worked around this in different ways and High was obviously inflated since it isn't fixed yet (I just verified with 5.0.0-25.26-generic and apparmor 2.13.2-9ubuntu6.1). ** Changed in: apparmor Importance: High => Medium ** Changed in: apparmor (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1620635 Title: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional Status in AppArmor: Triaged Status in Snappy: Won't Fix Status in apparmor package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Download and compile the following sample C app that calls aa_query_label wget https://launchpadlibrarian.net/207629699/query_file.c gcc -o query_file query_file.c -l apparmor 2. Install a snap that uses the home interface, for example demo-wget: snap install demo-wget 3. Create a file in your home: touch /home/USERNAME/testfile 4. Ask apparmor if demo-wget can read that file with query_file: ./query_file snap.demo-wget.wget /home/USERNAME/testfile Expected result: output of ./query_file command is read '/home/kaleo/toto' allowed Current result: output of ./query_file command is read '/home/kaleo/toto' denied To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1620635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
https://gitlab.gnome.org/GNOME/evolution/issues/616 ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/evolution/issues/616 + + --- + I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:41:26 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SegvAnalysis: - Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi - PC (0x7f36355653ae) ok - source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! - destination "%rsi" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi + PC (0x7f36355653ae) ok + source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! + destination "%rsi" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: - tcache_get (tc_idx=) at malloc.c:2937 - __GI___libc_malloc (bytes=32) at malloc.c:3051 - g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + tcache_get (tc_idx=) at malloc.c:2937 + __GI___libc_malloc (bytes=32) at malloc.c:3051 + g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: gitlab.gnome.org/GNOME/evolution/issues #616 https://gitlab.gnome.org/GNOME/evolution/issues/616 ** Also affects: evolution-data-server via https://gitlab.gnome.org/GNOME/evolution/issues/616 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1843627 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() Status in evolution-data-server: Unknown Status in evolution-data-server package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evolution/issues/616 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evolution-data-server 3.33.91-3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:41:26 2019 ExecutablePath: /usr/libexec/evolution-calendar-factory InstallationDate: Installed on 2018-12-02 (282 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/libexec/evolution-calendar-factory ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>: mov (%r8),%rsi PC (0x7f36355653ae) ok source "(%r8)" (0x7f36) not located in a known VMA region (needed readable region)! destination "%rsi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: tcache_get (tc_idx=) at malloc.c:2937 __GI___libc_malloc (bytes=32) at malloc.c:3051 g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get() UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+subscriptions --
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
I tried comparing the binaries with diffoscope, and one difference which jumped out at me is the .plt.sec section which is present in the Eoan binary. This presumably comes from CET (gcc -fcf-protection). There are other differences, less significant IMO; .plt.sec is a likely candidate for something WSL1 might not support. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in gzip package in Ubuntu: Confirmed Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843630] [NEW] ubuntu-bug not opening anything in the browser
Public bug reported: Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to the developers?" with the "Don't send" and "Send" buttons, but when I click on "Send" nothing happens. I have the "problem_types" line commented out in /etc/apport/crashdb.conf, though I don't know if that's relevant when I'm trying to report a bug, not a crash. I have no idea how to troubleshoot this further. Please advise. The same problem occurs for "ubuntu-bug needrestart". ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Package changed: linphone (Ubuntu) => apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1843630 Title: ubuntu-bug not opening anything in the browser Status in apport package in Ubuntu: New Bug description: Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to the developers?" with the "Don't send" and "Send" buttons, but when I click on "Send" nothing happens. I have the "problem_types" line commented out in /etc/apport/crashdb.conf, though I don't know if that's relevant when I'm trying to report a bug, not a crash. I have no idea how to troubleshoot this further. Please advise. The same problem occurs for "ubuntu-bug needrestart". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843630] [NEW] ubuntu-bug not opening anything in the browser
You have been subscribed to a public bug: Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to the developers?" with the "Don't send" and "Send" buttons, but when I click on "Send" nothing happens. I have the "problem_types" line commented out in /etc/apport/crashdb.conf, though I don't know if that's relevant when I'm trying to report a bug, not a crash. I have no idea how to troubleshoot this further. Please advise. The same problem occurs for "ubuntu-bug needrestart". ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- ubuntu-bug not opening anything in the browser https://bugs.launchpad.net/bugs/1843630 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS
In case this might be relevant: - /var is a separate partition (/dev/md1) - /var/cache is a separate partition (an LVM volume) - /tmp is a separate partition (an LVM volume) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1843623 Title: LVM volumes not activated during boot after upgrade to 18.04 LTS Status in lvm2 package in Ubuntu: New Bug description: I've upgraded a server from Ubuntu 16.04 LTS to 18.04 LTS and now it fails to activate LVM volumes during boot (which causes systemd to stop in the middle of the boot process and ask me to fix this on the console without starting up services like SSH). The root partition, which is also on LVM, gets activated (by the initramfs I assume), but none of the other ones are. Everything worked fine on xenial, so I don't think this is a duplicate of 1573982? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Sep 11 19:34:53 2019 ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: Upgraded to bionic on 2019-09-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1843623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS
FWIW journalctl -b is showing a bunch of Sep 11 19:16:30 fridge lvmetad[457]: WARNING: Ignoring unsupported value for cmd. Sep 11 19:16:30 fridge lvmetad[457]: WARNING: Ignoring unsupported value for cmd. before systemd unit timeouts that are about those missing partitions failing to mount. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1843623 Title: LVM volumes not activated during boot after upgrade to 18.04 LTS Status in lvm2 package in Ubuntu: New Bug description: I've upgraded a server from Ubuntu 16.04 LTS to 18.04 LTS and now it fails to activate LVM volumes during boot (which causes systemd to stop in the middle of the boot process and ask me to fix this on the console without starting up services like SSH). The root partition, which is also on LVM, gets activated (by the initramfs I assume), but none of the other ones are. Everything worked fine on xenial, so I don't think this is a duplicate of 1573982? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Sep 11 19:34:53 2019 ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: Upgraded to bionic on 2019-09-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1843623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
@Daniel van, Do you know how to "reupload to bionic-proposed queue in such a fashion that 1556439 will appear in Launchpad-Bugs-Fixed"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Incomplete Status in pulseaudio source package in Disco: Fix Committed Status in pulseaudio source package in Eoan: Fix Released Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] Low, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. For the Bionic, This SRU also includes the fix of LP: #1556439, this fix is safe and is very low possible to introduce any regression too, because it just adds a sink-input/source-output state checking, if the sink-input/source-output is unlinking or unlinked, it is useless to move it to a new sink/source, furthermore it will trigger an assertion that make the pulseaudio crash, adding this check can fix this problem (LP: #1556439). [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843623] Re: LVM volumes not activated during boot after upgrade to 18.04 LTS
If I run pvscan --cache -aay in the systemd emergency console, all logical volumes get activated and the system then proceeds to boot normally. It seems like for some reason udev is not running pvscan for me? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1843623 Title: LVM volumes not activated during boot after upgrade to 18.04 LTS Status in lvm2 package in Ubuntu: New Bug description: I've upgraded a server from Ubuntu 16.04 LTS to 18.04 LTS and now it fails to activate LVM volumes during boot (which causes systemd to stop in the middle of the boot process and ask me to fix this on the console without starting up services like SSH). The root partition, which is also on LVM, gets activated (by the initramfs I assume), but none of the other ones are. Everything worked fine on xenial, so I don't think this is a duplicate of 1573982? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Sep 11 19:34:53 2019 ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: Upgraded to bionic on 2019-09-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1843623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843623] [NEW] LVM volumes not activated during boot after upgrade to 18.04 LTS
Public bug reported: I've upgraded a server from Ubuntu 16.04 LTS to 18.04 LTS and now it fails to activate LVM volumes during boot (which causes systemd to stop in the middle of the boot process and ask me to fix this on the console without starting up services like SSH). The root partition, which is also on LVM, gets activated (by the initramfs I assume), but none of the other ones are. Everything worked fine on xenial, so I don't think this is a duplicate of 1573982? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Sep 11 19:34:53 2019 ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: Upgraded to bionic on 2019-09-11 (0 days ago) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1843623 Title: LVM volumes not activated during boot after upgrade to 18.04 LTS Status in lvm2 package in Ubuntu: New Bug description: I've upgraded a server from Ubuntu 16.04 LTS to 18.04 LTS and now it fails to activate LVM volumes during boot (which causes systemd to stop in the middle of the boot process and ask me to fix this on the console without starting up services like SSH). The root partition, which is also on LVM, gets activated (by the initramfs I assume), but none of the other ones are. Everything worked fine on xenial, so I don't think this is a duplicate of 1573982? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Sep 11 19:34:53 2019 ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: Upgraded to bionic on 2019-09-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1843623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
> Additionally, I think this should be reuploaded to bionic-proposed queue in such a fashion that 1556439 will appear in Launchpad-Bugs-Fixed so that we reverify the fix for that bug when verifying the new pulseaudio upload. I don't see any change in the upload. Please could you address Brian's comment? If it is no longer relevant, an explanation would be helpful. ** Changed in: pulseaudio (Ubuntu Bionic) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Incomplete Status in pulseaudio source package in Disco: Fix Committed Status in pulseaudio source package in Eoan: Fix Released Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] Low, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. For the Bionic, This SRU also includes the fix of LP: #1556439, this fix is safe and is very low possible to introduce any regression too, because it just adds a sink-input/source-output state checking, if the sink-input/source-output is unlinking or unlinked, it is useless to move it to a new sink/source, furthermore it will trigger an assertion that make the pulseaudio crash, adding this check can fix this problem (LP: #1556439). [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842643] Re: [ffe] Update to 1.44.6
It's more like issues with differences in rendering, e.g.: - https://github.com/harfbuzz/harfbuzz/issues/1892 - https://gitlab.com/inkscape/inkscape/issues/364 I'm a bit clueless here, would be happy for someone else to weigh in :-) ** Bug watch added: github.com/harfbuzz/harfbuzz/issues #1892 https://github.com/harfbuzz/harfbuzz/issues/1892 ** Bug watch added: gitlab.com/inkscape/inkscape/issues #364 https://gitlab.com/inkscape/inkscape/issues/364 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: [ffe] Update to 1.44.6 Status in pango1.0 package in Ubuntu: New Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843607] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
So I see Setting up ca-certificates (20180409) ... Updating certificates in /etc/ssl/certs... rehash: error: skipping dovecot.pem, cannot open file rehash: warning: skipping duplicate certificate in AlphaSSL_root.crt dpkg: error processing package ca-certificates (--configure): installed ca-certificates package post-installation script subprocess returned error exit status 1 and I can tell you that (back in 2015) I did run wget -O /etc/ssl/certs/AlphaSSL_root.crt https://www.alphassl.com/support/roots/root.txt when I was trying to make my dovecot use a wildcard certificate bought from AlphaSSL. Seems a bit harsh to fail the entire OS upgrade because I downloaded an extra file into /etc/ssl/certs/. Meanwhile dpkg --configure -a that do-release-upgrade ran for me completed without errors and apt upgrade shows no packages needing upgrades (just a bunch expecting autoremovals). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1843607 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: I was upgrading an Ubuntu 16.04 LTS server to 18.04 with sudo do- release-upgrade and it crashed. I did not see where the error was because etckeeper's messages made them scroll too far back, and do-release-upgrade sets up screen in a way that makes it impossible for me to see terminal scrollback. I expect apport attached all the relevant logs to this bug. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-161.189-generic 4.4.186 Uname: Linux 4.4.0-161-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Sep 11 18:19:10 2019 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.2 apt 1.6.11 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2019-09-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1843607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843607] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
Public bug reported: I was upgrading an Ubuntu 16.04 LTS server to 18.04 with sudo do- release-upgrade and it crashed. I did not see where the error was because etckeeper's messages made them scroll too far back, and do-release-upgrade sets up screen in a way that makes it impossible for me to see terminal scrollback. I expect apport attached all the relevant logs to this bug. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-161.189-generic 4.4.186 Uname: Linux 4.4.0-161-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Sep 11 18:19:10 2019 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.2 apt 1.6.11 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2019-09-11 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1843607 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: I was upgrading an Ubuntu 16.04 LTS server to 18.04 with sudo do- release-upgrade and it crashed. I did not see where the error was because etckeeper's messages made them scroll too far back, and do-release-upgrade sets up screen in a way that makes it impossible for me to see terminal scrollback. I expect apport attached all the relevant logs to this bug. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-161.189-generic 4.4.186 Uname: Linux 4.4.0-161-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Sep 11 18:19:10 2019 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.2 apt 1.6.11 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2019-09-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1843607/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842643] Re: [ffe] Update to 1.44.6
I installed the ppa version on my eoan system, works fine, including french accents ;-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: [ffe] Update to 1.44.6 Status in pango1.0 package in Ubuntu: New Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785629] Re: [MIR] gupnp-av
+1 on the MIR side ** Changed in: gupnp-av (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp-av in Ubuntu. https://bugs.launchpad.net/bugs/1785629 Title: [MIR] gupnp-av Status in gupnp-av package in Ubuntu: Fix Committed Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries, including the gupnp-dlna one * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is not being used during build, we are going to look at changing that * Dependendies The package uses standard desktop libraries that are already in main (gstreamer, glib) * Standards compliance the package is using standard packaging (dh10), the standards-version is 3.9.8, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843600] [NEW] system became too slow and some applications may crash during work
Public bug reported: am working on you tube channel and creating a video is a big task with this system. its too slow and working performance is not great since i have installed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Sep 11 20:24:15 2019 DistUpgraded: 2019-04-13 17:46:44,751 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2019-04-07 (157 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Dell Inc. Inspiron 3521 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=df0b088a-b8bd-4a72-a111-5f3fd1798a2e ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-04-13 (151 days ago) dmi.bios.date: 07/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 06RYX8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A14 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron3521:pvrA14:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA14: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.version: A14 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1843600 Title: system became too slow and some applications may crash during work Status in xorg package in Ubuntu: New Bug description: am working on you tube channel and creating a video is a big task with this system. its too slow and working performance is not great since i have installed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Sep 11 20:24:15 2019 DistUpgraded: 2019-04-13 17:46:44,751 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2019-04-07 (157 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Dell Inc. Inspiron 3521 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=df0b088a-b8bd-4a72-a111-5f3fd1798a2e ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-04-13 (151 days ago) dmi.bios.date: 07/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 06RYX8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A14 dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron3521:pvrA14:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA14: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.version: A14 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Touch-packages] [Bug 1525310] Re: virsh with apparmor misconfigures libvirt-UUID files during snapshot
Hi, I was asked about a very similar case and needed to debug it. So I thought I give the issue reported here a try how it looks like today. virt install creates a guest with a command like: -drive file=/dev/LVMpool/test-snapshot-virtinst,format=raw,if=none,id=drive-virtio-disk0,cache=none,aio=native ## Solved - confusion of pre-existing other apparmor rules as pools are unsupported by libvirt/apparmor ## In this case virt-inst pre-creates a VG of a given size and passes the guest just that. This is the different to using the actual pool feature. With that I'm "ok" that it doesn't need a special apparmor rule already. >From the guest/apparmor point of view when the guest starts the path is known >and added to the guests profile. (With a pool ref in the guest that would not have worked) ## experiments - setup ## Lets define a guest which has a qcow and a lvm disk that we can snapshot for experiments. We will use the disk created in the test above, but in a uvtool guest to get rid of all virt-install special quirks. The other disk is just a qcow file. $ sudo qemu-img create -f qcow2 /var/lib/uvtool/libvirt/images/eoan-snapshot-test.qcow 1G Formatting '/var/lib/uvtool/libvirt/images/eoan-snapshot-test.qcow', fmt=qcow2 size=1073741824 cluster_size=65536 lazy_refcounts=off refcount_bits=16 The config for those looks like: qcow: CMD: -drive file=/var/lib/uvtool/libvirt/images/eoan-snapshot-test.qcow,format=qcow2,if=none,id=drive-virtio-disk2 apparmor: "/var/lib/uvtool/libvirt/images/eoan-snapshot-test.qcow" rwk, disk: CMD: -drive file=/dev/LVMpool/test-snapshot-virtinst,format=raw,if=none,id=drive-virtio-disk3 apparmor: "/dev/dm-11" rwk, which is a match as $ ll /dev/LVMpool/test-snapshot-virtinst lrwxrwxrwx 1 root root 8 Sep 11 05:14 /dev/LVMpool/test-snapshot-virtinst -> ../dm-11 ## experiments - snapshotting ## Details of the spec see: https://libvirt.org/formatdomain.html Snapshot of just the qcow file: $ virsh snapshot-create-as --print-xml --domain eoan-snapshot --disk-only --atomic --diskspec vda,snapshot=no --diskspec vdb,snapshot=no --diskspec vdc,file=/var/lib/libvirt/images/eoan-snapshot-test.thesnapshot.qcow,snapshot=external --diskspec vdd,snapshot=no $ virsh snapshot-list eoan-snapshot Name Creation Time State 1568196836 2019-09-11 06:13:56 -0400 disk-snapshot The snapshot got added to the apparmor profile: "/var/lib/libvirt/images/eoan-snapshot-test.thesnapshot.qcow" rwk, The position shows that this was done with the "append" feature of virt-aa-helper. So it did not re-parse the guest but just add one more entry (as it would do on hotplug). I'm not trying to LVM-snapshot as that seems not what was asked for. And further LVM would have own capabilties to do so. ## check status after snapshot ## The guest now has the new snapshot as main file and the old one as backing file (COW-chain) Please do mind that this is the "runtime view", once shut down you'll only see the new snapshot. This is confirmed by the metadata in the qcow file. $ sudo qemu-img info /var/lib/libvirt/images/eoan-snapshot-test.thesnapshot.qcow image: /var/lib/libvirt/images/eoan-snapshot-test.thesnapshot.qcow file format: qcow2 virtual size: 1.0G (1073741824 bytes) disk size: 196K cluster_size: 65536 backing file: /var/lib/uvtool/libvirt/images/eoan-snapshot-test.qcow backing file format: qcow2 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false ## restart guest ## XML of inactive guest as expected: The guest starts just fine (with still all 4 disk entries): ../dm-11 lrwxrwxrwx 1 root root8 Sep 11 06:44 test-snapshot-virtinst-snap -> ../dm-14 Still dm-11 that matches apparmor "/dev/dm-11" rwk, Checking if it is an issue to restart the guest with the LVM snapshot attached. No, shutdown and start work fine still. With that said I think we can close this old bug nowadays. P.S. There is a case a friend of mine reported with qcow snapshots on LVM which sounds odd and is broken. This I'll track down in another place as it has nothing to do with the issue that was reported here. ** Changed in: apparmor (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu.
[Touch-packages] [Bug 1843468] Re: nftables based iptables wrapper break userspace
** Changed in: iptables (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1843468 Title: nftables based iptables wrapper break userspace Status in iptables package in Ubuntu: Fix Committed Bug description: iptables just got replaced by the nftables wrappers, effectively changing all Ubuntu systems to using nftables rather than regular iptables/ip6tables/ebtables. Unfortunately those wrappers aren't perfect and don't convert every option properly, nor know about some of the available plugins for those commands. This means that unless the software using those commands are aware that those are wrappers and adapt their use, they may break at some random point in time. While nftables is clearly the way forward, just silently switching the existing native tools with the compat wrappers will lead to widespread breakage both from packages in the archive, snaps and a variety of scripts our users may be running. So far, looking around, known breakages post-nft are expected with at least Docker, Kubernetes and LXD but the same may be true with the many other packages we have that call iptables, ip6tables, ebtables or arptables today. A migration should include a proper audit of all in-archive users, see if they have a plan/patch for native nft interaction and if not, validate their use of the tools is compatible with the wrappers. We should also extend that to popular snaps / those we ship by default. Snaps make things worse as they use the tools from their base snap, which in LXD's case is currently 16.04 (soon to switch to 18.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1843468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843468] Re: nftables based iptables wrapper break userspace
** Changed in: iptables (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1843468 Title: nftables based iptables wrapper break userspace Status in iptables package in Ubuntu: Triaged Bug description: iptables just got replaced by the nftables wrappers, effectively changing all Ubuntu systems to using nftables rather than regular iptables/ip6tables/ebtables. Unfortunately those wrappers aren't perfect and don't convert every option properly, nor know about some of the available plugins for those commands. This means that unless the software using those commands are aware that those are wrappers and adapt their use, they may break at some random point in time. While nftables is clearly the way forward, just silently switching the existing native tools with the compat wrappers will lead to widespread breakage both from packages in the archive, snaps and a variety of scripts our users may be running. So far, looking around, known breakages post-nft are expected with at least Docker, Kubernetes and LXD but the same may be true with the many other packages we have that call iptables, ip6tables, ebtables or arptables today. A migration should include a proper audit of all in-archive users, see if they have a plan/patch for native nft interaction and if not, validate their use of the tools is compatible with the wrappers. We should also extend that to popular snaps / those we ship by default. Snaps make things worse as they use the tools from their base snap, which in LXD's case is currently 16.04 (soon to switch to 18.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1843468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843468] Re: nftables based iptables wrapper break userspace
** Tags added: id-5d784b79b60ef9779cc530ed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1843468 Title: nftables based iptables wrapper break userspace Status in iptables package in Ubuntu: Triaged Bug description: iptables just got replaced by the nftables wrappers, effectively changing all Ubuntu systems to using nftables rather than regular iptables/ip6tables/ebtables. Unfortunately those wrappers aren't perfect and don't convert every option properly, nor know about some of the available plugins for those commands. This means that unless the software using those commands are aware that those are wrappers and adapt their use, they may break at some random point in time. While nftables is clearly the way forward, just silently switching the existing native tools with the compat wrappers will lead to widespread breakage both from packages in the archive, snaps and a variety of scripts our users may be running. So far, looking around, known breakages post-nft are expected with at least Docker, Kubernetes and LXD but the same may be true with the many other packages we have that call iptables, ip6tables, ebtables or arptables today. A migration should include a proper audit of all in-archive users, see if they have a plan/patch for native nft interaction and if not, validate their use of the tools is compatible with the wrappers. We should also extend that to popular snaps / those we ship by default. Snaps make things worse as they use the tools from their base snap, which in LXD's case is currently 16.04 (soon to switch to 18.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1843468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843565] Re: External USB mouse middle button SCROLL stoped work since kernel x86_64 Linux 4.15.0-60-generic
** Description changed: Hello, Devs! I found since kernel x86_64 Linux 4.15.0-60-generic at Ubuntu 18.04 my external USB mouse in Samsung ultrabook (NP900X4C) scroll not working! (with weel at middle mouse button) With touchpad scroll works fine. This is cat /proc/bus/input/devices info from 3 latest kernels (I have managed to boot different kernels thru Grub2 menu): - Case - kernel: x86_64 Linux 4.15.0-58-generic (external USB mouse middle scroll button works well) # cat /proc/bus/input/devices [...] I: Bus=0003 Vendor=09da Product=000a Version=0110 N: Name="A4Tech PS/2+USB Mouse" P: Phys=usb-:00:1d.0-1.2/input0 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:09DA:000A.0002/input/input12 U: Uniq= H: Handlers=mouse1 event6 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=343 B: MSC=10 - Kernel: x86_64 Linux 4.15.0-60-generic (scroll not working with external mouse; touchpad scroll ok) # cat /proc/bus/input/devices [...] I: Bus=0003 Vendor=09da Product=000a Version=0110 N: Name="A4Tech PS/2+USB Mouse" P: Phys=usb-:00:1d.0-1.2/input0 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:09DA:000A.0002/input/input12 U: Uniq= H: Handlers=mouse1 event5 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=143 B: MSC=10 - Kernel: x86_64 Linux 4.15.0-62-generic (scroll not working with external mouse; touchpad scroll ok) # cat /proc/bus/input/devices [...] I: Bus=0003 Vendor=09da Product=000a Version=0110 N: Name="A4Tech PS/2+USB Mouse" P: Phys=usb-:00:1d.0-1.2/input0 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:09DA:000A.0002/input/input12 U: Uniq= H: Handlers=mouse1 event6 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=143 B: MSC=10 - - And evtest /dev/input/event6 not shows any mouse scroll events (If I don't move mouse) + And evtest /dev/input/event6 not shows any mouse scroll events (If I + don't move mouse) But just PRESSING middle mouse button is OK: # evtest /dev/input/event6 [...] Event: time 1568199190.499958, -- SYN_REPORT Event: time 1568199190.587896, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003 Event: time 1568199190.587896, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 This is my first bugreport, I hope additional info of my system setup is attached... + + I forgot to mention that if I log into fresh Ubuntu account in case of + booting x86_64 Linux 4.15.0-62-generic it doesn't helps - mouse scroll + still not work. + + Scroll works only on x86_64 Linux 4.15.0-58-generic ;( + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:20:43 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: - virtualbox, 5.2.32, 4.15.0-58-generic, x86_64: installed - virtualbox, 5.2.32, 4.15.0-60-generic, x86_64: installed - virtualbox, 5.2.32, 4.15.0-62-generic, x86_64: installed + virtualbox, 5.2.32, 4.15.0-58-generic, x86_64: installed + virtualbox, 5.2.32, 4.15.0-60-generic, x86_64: installed + virtualbox, 5.2.32, 4.15.0-62-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0d3] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0d3] InstallationDate: Installed on 2018-08-08 (398 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=6a8333d8-3e2a-4733-8f27-919b24d7586e ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P07AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias:
[Touch-packages] [Bug 1843565] [NEW] External USB mouse middle button SCROLL stoped work since kernel x86_64 Linux 4.15.0-60-generic
Public bug reported: Hello, Devs! I found since kernel x86_64 Linux 4.15.0-60-generic at Ubuntu 18.04 my external USB mouse in Samsung ultrabook (NP900X4C) scroll not working! (with weel at middle mouse button) With touchpad scroll works fine. This is cat /proc/bus/input/devices info from 3 latest kernels (I have managed to boot different kernels thru Grub2 menu): Case - kernel: x86_64 Linux 4.15.0-58-generic (external USB mouse middle scroll button works well) # cat /proc/bus/input/devices [...] I: Bus=0003 Vendor=09da Product=000a Version=0110 N: Name="A4Tech PS/2+USB Mouse" P: Phys=usb-:00:1d.0-1.2/input0 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:09DA:000A.0002/input/input12 U: Uniq= H: Handlers=mouse1 event6 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=343 B: MSC=10 Kernel: x86_64 Linux 4.15.0-60-generic (scroll not working with external mouse; touchpad scroll ok) # cat /proc/bus/input/devices [...] I: Bus=0003 Vendor=09da Product=000a Version=0110 N: Name="A4Tech PS/2+USB Mouse" P: Phys=usb-:00:1d.0-1.2/input0 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:09DA:000A.0002/input/input12 U: Uniq= H: Handlers=mouse1 event5 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=143 B: MSC=10 Kernel: x86_64 Linux 4.15.0-62-generic (scroll not working with external mouse; touchpad scroll ok) # cat /proc/bus/input/devices [...] I: Bus=0003 Vendor=09da Product=000a Version=0110 N: Name="A4Tech PS/2+USB Mouse" P: Phys=usb-:00:1d.0-1.2/input0 S: Sysfs=/devices/pci:00/:00:1d.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:09DA:000A.0002/input/input12 U: Uniq= H: Handlers=mouse1 event6 B: PROP=0 B: EV=17 B: KEY=ff 0 0 0 0 B: REL=143 B: MSC=10 And evtest /dev/input/event6 not shows any mouse scroll events (If I don't move mouse) But just PRESSING middle mouse button is OK: # evtest /dev/input/event6 [...] Event: time 1568199190.499958, -- SYN_REPORT Event: time 1568199190.587896, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003 Event: time 1568199190.587896, type 1 (EV_KEY), code 274 (BTN_MIDDLE), value 0 This is my first bugreport, I hope additional info of my system setup is attached... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 13:20:43 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32, 4.15.0-58-generic, x86_64: installed virtualbox, 5.2.32, 4.15.0-60-generic, x86_64: installed virtualbox, 5.2.32, 4.15.0-62-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0d3] InstallationDate: Installed on 2018-08-08 (398 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=6a8333d8-3e2a-4733-8f27-919b24d7586e ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P07AAC dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP07AAC:bd11/18/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 900X3C/900X3D/900X4C/900X4D dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided
[Touch-packages] [Bug 1843554] Re: apt update is trying to use IPv6 for some reason, which does not work
It tried both IPv4 and IPv6; the IPv4 mirror is down. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1843554 Title: apt update is trying to use IPv6 for some reason, which does not work Status in apt package in Ubuntu: Invalid Bug description: Today I've discovered that I cannot use apt-get any more: apt update Hit:1 http://ppa.launchpad.net/mgedmin/ppa/ubuntu disco InRelease Ign:2 http://ddebs.ubuntu.com disco InRelease Ign:3 http://ddebs.ubuntu.com disco-updates InRelease Hit:4 http://ppa.launchpad.net/pov/ppa/ubuntu disco InRelease Hit:5 http://ddebs.ubuntu.com disco Release Hit:6 http://security.ubuntu.com/ubuntu disco-security InRelease Hit:7 http://ddebs.ubuntu.com disco-updates Release 0% [Connecting to lt.archive.ubuntu.com (2001:778:1::d)] and there it stalls for about 30 seconds, after which Err:10 http://lt.archive.ubuntu.com/ubuntu disco InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Could not connect to lt.archive.ubuntu.com:80 (83.171.20.4), connection timed out Err:11 http://lt.archive.ubuntu.com/ubuntu disco-updates InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Err:12 http://lt.archive.ubuntu.com/ubuntu disco-backports InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Reading package lists... Done Building dependency tree Reading state information... Done 16 packages can be upgraded. Run 'apt list --upgradable' to see them. W: Failed to fetch http://lt.archive.ubuntu.com/ubuntu/dists/disco/InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Could not connect to lt.archive.ubuntu.com:80 (83.171.20.4), connection timed out W: Failed to fetch http://lt.archive.ubuntu.com/ubuntu/dists/disco-updates/InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) W: Failed to fetch http://lt.archive.ubuntu.com/ubuntu/dists/disco-backports/InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) W: Some index files failed to download. They have been ignored, or old ones used instead. I don't know why it's trying to connect to my Ubuntu mirror over IPv6. There's no IPv6 in Lithuania (I'm exaggerating a bit, but my ISP -- the largest ISP in the country -- does not support IPv6). I've never had working IPv6 connectivity in my life. apt-get used to work before today. I've no idea what changed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apt 1.8.1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 11:46:28 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (90 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1843554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
** Changed in: linux (Ubuntu Bionic) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756595] Re: disk space info inadvertently provides all installed snaps
I started some multipass VMs, installed the core snap in there, checked that the snap was mounted in df. To verify the bug, I installed hello, added a prerm to fail removal, and then investigated the crash file: == bionic 1.6.12: == === normal df output === Filesystem 1K-blocksUsed Available Use% Mounted on udev 491808 0491808 0% /dev tmpfs 100908 868100040 1% /run /dev/sda14901996 1264364 3621248 26% / tmpfs 504524 0504524 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 504524 0504524 0% /sys/fs/cgroup /dev/sda151068583668103190 4% /boot/efi tmpfs 100904 0100904 0% /run/user/1000 /dev/loop0 90880 90880 0 100% /snap/core/7396 === crash file === Df: Filesystem 1K-blocksUsed Available Use% Mounted on udev 491808 0491808 0% /dev tmpfs 100908 872100036 1% /run /dev/sda14901996 1264372 3621240 26% / tmpfs 504524 0504524 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 504524 0504524 0% /sys/fs/cgroup /dev/sda151068583668103190 4% /boot/efi tmpfs 100904 0100904 0% /run/user/1000 == disco 1.8.3 == multipass@disco:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on /dev/root4901996 1323952 3561660 28% / devtmpfs 499036 0499036 0% /dev tmpfs 503272 0503272 0% /dev/shm tmpfs 100656 864 99792 1% /run tmpfs 5120 0 5120 0% /run/lock tmpfs 503272 0503272 0% /sys/fs/cgroup /dev/sda151068583686103172 4% /boot/efi tmpfs 100652 0100652 0% /run/user/1000 /dev/loop0 90880 90880 0 100% /snap/core/7396 /dev/loop1 55808 55808 0 100% /snap/lxd/11595 multipass@disco:~$ sudo tail /var/crash/hello.0.crash Df: Filesystem 1K-blocksUsed Available Use% Mounted on /dev/root4901996 1323956 3561656 28% / devtmpfs 499036 0499036 0% /dev tmpfs 503272 0503272 0% /dev/shm tmpfs 100656 868 99788 1% /run tmpfs 5120 0 5120 0% /run/lock tmpfs 503272 0503272 0% /sys/fs/cgroup /dev/sda151068583686103172 4% /boot/efi tmpfs 100652 0100652 0% /run/user/1000 --> both are fine ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1756595 Title: disk space info inadvertently provides all installed snaps Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Disco: Fix Committed Status in apt source package in Eoan: Fix Released Bug description: [Impact] When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home 430651264 67584 430583680 1% /home nsn7/var/cache 430653312 69632 430583680 1% /var/cache nsn7/var/mail 430583808 128 430583680 1% /var/mail nsn7/var/spool 430583808 128 430583680 1% /var/spool tmpfs 1630152 16 1630136 1% /run/user/120 tmpfs 100 0 100 0% /var/lib/lxd/shmounts tmpfs
[Touch-packages] [Bug 1756595] Re: disk space info inadvertently provides all installed snaps
Oh, as I wrote on the other bug, autopkgtest regressions all went away, except for apport, which had the usual random failure also present in earlier failures. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1756595 Title: disk space info inadvertently provides all installed snaps Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Committed Status in apt source package in Disco: Fix Committed Status in apt source package in Eoan: Fix Released Bug description: [Impact] When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home 430651264 67584 430583680 1% /home nsn7/var/cache 430653312 69632 430583680 1% /var/cache nsn7/var/mail 430583808 128 430583680 1% /var/mail nsn7/var/spool 430583808 128 430583680 1% /var/spool tmpfs 1630152 16 1630136 1% /run/user/120 tmpfs 100 0 100 0% /var/lib/lxd/shmounts tmpfs 100 0 100 0% /var/lib/lxd/devlxd tmpfs 1630152 36 1630116 1% /run/user/1000 nsn7/lxd/containers/squid-ds216 431444096 860416 430583680 1% /var/lib/lxd/storage-pools/default/containers/squid-ds216 /dev/loop0 83712 83712 0 100% /snap/core/4206 /dev/loop1 102144 102144 0 100% /snap/git-ubuntu/402 You can see I have the core snap at revision 4206, and git-ubuntu at revision 402. There are already many bug reports in launchpad where one can see this information. Granted, the user can review it, refuse to send this data, etc. This bug is about the unexpectedness of having that information in the disk space data. If the user sees a prompt like "Would you like to include disk free space information in your report?", or "Would you like to include the output of the df(1) command in your report?", that doesn't immediately translate to "Would you like to include disk free space information and a list of all installed snaps and their revision numbers in your report?". [Test case] Do something that triggers the apport hook and make sure you don't see snaps in there. For example, install xterm, then add exit 1 to the start of the prerm, then run apt remove xterm, and investigate /var/crash/xterm.0.crash after that (delete before running apt). [Regression potential] Fix consists of adding -x squashfs to df output, so might hide other non-snap squashfs images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1756595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
** Changed in: oem-priority
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Bug description:
[Impact]
* Many server users upgraded from previous Ubuntu LTS series, such as
14.04 and 16.04, will be affected by this regression.
* Because there is /etc/udev/rules/70-persistent-network.rules or
/etc/udev/rules.d/70-persistent-net.rules generated by
/lib/udev/write_net_rules left.
* The previous SRU commit of LP: #1837700 doesn't cover this
persistent network rule.
[Test Case]
* It needs to have two Ethernet devices and provides
/etc/udev/rules.d/70-persistent-net.rules as below.
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
[Regression Potential]
* When users upgrade to next LTS 20.04, they may also encounter this
issue because Debian has dropped the same patch.
* We need to figure another way to avoid this regression for next LTS
20.04.
* Adding back the origial patch from Debian will casue another issue.
(LP: #1837700)
[Other Info]
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks
Oh, as I wrote on the other bugs, autopkgtest regressions all went away, except for apport, which had the usual random failure also present in earlier failures. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1829860 Title: APT unlocks in same order as it locks Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in apt source package in Disco: Fix Committed Bug description: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend. [Test case] Watch lock release with strace and see that it unlocks the right way. [Regression potential] Some other locking races or something? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks
Same for bionic 1.6.12:
openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW,
0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
fcntl(5, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
end of run:
close(5) = 0
close(4) = 0
close(3) = 0
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1829860
Title:
APT unlocks in same order as it locks
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
New
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Disco:
Fix Committed
Bug description:
[Impact]
APT releases the locks in the same order it acquires them, rather than
reverse order. Given that we have no waiting for locks, this is not _super_
problematic, but it might be wrong: You'd get a lock failure on dpkg's lock,
rather than lock-frontend.
[Test case]
Watch lock release with strace and see that it unlocks the right way.
[Regression potential]
Some other locking races or something?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks
So disco, 1.8.3:
at the start:
openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW,
0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
fcntl(5, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
end of run:
close(5)= 0
close(4)= 0
close(3)= 0
=> we unlock in reverse as we want.
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1829860
Title:
APT unlocks in same order as it locks
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
New
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Disco:
Fix Committed
Bug description:
[Impact]
APT releases the locks in the same order it acquires them, rather than
reverse order. Given that we have no waiting for locks, this is not _super_
problematic, but it might be wrong: You'd get a lock failure on dpkg's lock,
rather than lock-frontend.
[Test case]
Watch lock release with strace and see that it unlocks the right way.
[Regression potential]
Some other locking races or something?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1829860/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
Ok working, my problem was not directly related to this bug. Sorry,
please forget my comment #20 and #21!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Bug description:
[Impact]
* Many server users upgraded from previous Ubuntu LTS series, such as
14.04 and 16.04, will be affected by this regression.
* Because there is /etc/udev/rules/70-persistent-network.rules or
/etc/udev/rules.d/70-persistent-net.rules generated by
/lib/udev/write_net_rules left.
* The previous SRU commit of LP: #1837700 doesn't cover this
persistent network rule.
[Test Case]
* It needs to have two Ethernet devices and provides
/etc/udev/rules.d/70-persistent-net.rules as below.
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
[Regression Potential]
* When users upgrade to next LTS 20.04, they may also encounter this
issue because Debian has dropped the same patch.
* We need to figure another way to avoid this regression for next LTS
20.04.
* Adding back the origial patch from Debian will casue another issue.
(LP: #1837700)
[Other Info]
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
Same again today. I will need to create some countermeasure, e.g. after every unattended upgrade a script that brings down and up the interfaces, otherwise I will not be able to keep my services availability. Kind of disappointed in this, but at least it will be a solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Confirmed Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843554] [NEW] apt update is trying to use IPv6 for some reason, which does not work
Public bug reported: Today I've discovered that I cannot use apt-get any more: apt update Hit:1 http://ppa.launchpad.net/mgedmin/ppa/ubuntu disco InRelease Ign:2 http://ddebs.ubuntu.com disco InRelease Ign:3 http://ddebs.ubuntu.com disco-updates InRelease Hit:4 http://ppa.launchpad.net/pov/ppa/ubuntu disco InRelease Hit:5 http://ddebs.ubuntu.com disco Release Hit:6 http://security.ubuntu.com/ubuntu disco-security InRelease Hit:7 http://ddebs.ubuntu.com disco-updates Release 0% [Connecting to lt.archive.ubuntu.com (2001:778:1::d)] and there it stalls for about 30 seconds, after which Err:10 http://lt.archive.ubuntu.com/ubuntu disco InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Could not connect to lt.archive.ubuntu.com:80 (83.171.20.4), connection timed out Err:11 http://lt.archive.ubuntu.com/ubuntu disco-updates InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Err:12 http://lt.archive.ubuntu.com/ubuntu disco-backports InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Reading package lists... Done Building dependency tree Reading state information... Done 16 packages can be upgraded. Run 'apt list --upgradable' to see them. W: Failed to fetch http://lt.archive.ubuntu.com/ubuntu/dists/disco/InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Could not connect to lt.archive.ubuntu.com:80 (83.171.20.4), connection timed out W: Failed to fetch http://lt.archive.ubuntu.com/ubuntu/dists/disco-updates/InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) W: Failed to fetch http://lt.archive.ubuntu.com/ubuntu/dists/disco-backports/InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) W: Some index files failed to download. They have been ignored, or old ones used instead. I don't know why it's trying to connect to my Ubuntu mirror over IPv6. There's no IPv6 in Lithuania (I'm exaggerating a bit, but my ISP -- the largest ISP in the country -- does not support IPv6). I've never had working IPv6 connectivity in my life. apt-get used to work before today. I've no idea what changed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apt 1.8.1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 11:46:28 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (90 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1843554 Title: apt update is trying to use IPv6 for some reason, which does not work Status in apt package in Ubuntu: New Bug description: Today I've discovered that I cannot use apt-get any more: apt update Hit:1 http://ppa.launchpad.net/mgedmin/ppa/ubuntu disco InRelease Ign:2 http://ddebs.ubuntu.com disco InRelease Ign:3 http://ddebs.ubuntu.com disco-updates InRelease Hit:4 http://ppa.launchpad.net/pov/ppa/ubuntu disco InRelease Hit:5 http://ddebs.ubuntu.com disco Release Hit:6 http://security.ubuntu.com/ubuntu disco-security InRelease Hit:7 http://ddebs.ubuntu.com disco-updates Release 0% [Connecting to lt.archive.ubuntu.com (2001:778:1::d)] and there it stalls for about 30 seconds, after which Err:10 http://lt.archive.ubuntu.com/ubuntu disco InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Could not connect to lt.archive.ubuntu.com:80 (83.171.20.4), connection timed out Err:11 http://lt.archive.ubuntu.com/ubuntu disco-updates InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Err:12 http://lt.archive.ubuntu.com/ubuntu disco-backports InRelease Cannot initiate the connection to lt.archive.ubuntu.com:80 (2001:778:1::d). - connect (101: Network is unreachable) Reading package lists... Done Building dependency tree Reading state information... Done 16
[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
See my attachment please. System stuck on boot.
** Attachment added: "console detail on boot"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651/+attachment/5287976/+files/bug.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Bug description:
[Impact]
* Many server users upgraded from previous Ubuntu LTS series, such as
14.04 and 16.04, will be affected by this regression.
* Because there is /etc/udev/rules/70-persistent-network.rules or
/etc/udev/rules.d/70-persistent-net.rules generated by
/lib/udev/write_net_rules left.
* The previous SRU commit of LP: #1837700 doesn't cover this
persistent network rule.
[Test Case]
* It needs to have two Ethernet devices and provides
/etc/udev/rules.d/70-persistent-net.rules as below.
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
[Regression Potential]
* When users upgrade to next LTS 20.04, they may also encounter this
issue because Debian has dropped the same patch.
* We need to figure another way to avoid this regression for next LTS
20.04.
* Adding back the origial patch from Debian will casue another issue.
(LP: #1837700)
[Other Info]
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules
Hi,
After this update (237-3ubuntu10.29) on this morning (11 sept.) my system no
more booting!
Black screen after grub, select other kernel but nothing works. I suppose it is
linked with this update...
...
Failed to start Network Manager
Dependency failed for Network Manager Wait Online
...
237-3ubuntu10.28 (ok) -> 237-3ubuntu10.29 (fail)
How to resolve that? I have no more network.. and my system is blocked.
Thanks for your help.
Ubuntu 18.04.3 LTS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651
Title:
Regression: after Uprade from udev_237-3ubuntu10.25 to
udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
-persistent-network.rules
Status in OEM Priority Project:
In Progress
Status in systemd package in Ubuntu:
Fix Released
Bug description:
[Impact]
* Many server users upgraded from previous Ubuntu LTS series, such as
14.04 and 16.04, will be affected by this regression.
* Because there is /etc/udev/rules/70-persistent-network.rules or
/etc/udev/rules.d/70-persistent-net.rules generated by
/lib/udev/write_net_rules left.
* The previous SRU commit of LP: #1837700 doesn't cover this
persistent network rule.
[Test Case]
* It needs to have two Ethernet devices and provides
/etc/udev/rules.d/70-persistent-net.rules as below.
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
[Regression Potential]
* When users upgrade to next LTS 20.04, they may also encounter this
issue because Debian has dropped the same patch.
* We need to figure another way to avoid this regression for next LTS
20.04.
* Adding back the origial patch from Debian will casue another issue.
(LP: #1837700)
[Other Info]
Since the latest update from udev_237-3ubuntu10.25 and
systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
systemd_237-3ubuntu10.26 the renaming of network interfaces by
/etc/udev/rules/70-persistent-network.rules does not work.
/etc/udev/rules/70-persistent-network.rules:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56",
NAME="eth1"
/var/log/syslog:
systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File
exists
When I downgrade the packages to the version with 237-3ubuntu10.25 the
following messages are in /var/log/syslog:
Sep 4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2:
renamed from eth0
Sep 4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed
from eth1
The latest version does not rename the interfaces temporary if there
is a conflict!
Manually installing the old packages with
dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
did fix the problem temporary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657646] Re: [20.04] Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation
Ok, it got spotted and became a component mismatch as expected in the tool run tonight. All is fine again, sorry for the noise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: [20.04] Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation Status in The Ubuntu-power-systems project: Triaged Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 package in Debian: New Bug description: Creating a thin pool LV is allowed even when thin-provisioning-tools is not installed. But deactivating or activating that VG fails. Since deactivating the VG usually only happens at reboot, the user might fail to notice this big problem until then. I think the lvconvert tool, used to combine the two "thin LVs" into a thin pool LV, should refuse to run if thin-provisioning-tools, or the needed scripts, aren't installed. Steps to reproduce: root@15-89:~# vgcreate vg /dev/vdb1 Volume group "vg" successfully created root@15-89:~# vgs VG #PV #LV #SN Attr VSize VFree vg 1 0 0 wz--n- 40.00g 40.00g root@15-89:~# lvcreate -n pool0 -l 90%VG vg Logical volume "pool0" created. root@15-89:~# lvcreate -n pool0meta -l 5%VG vg Logical volume "pool0meta" created. root@15-89:~# lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert pool0 vg -wi-a- 36.00g pool0meta vg -wi-a- 2.00g root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 100 Jun 21 14:15 ./ drwxr-xr-x 20 root root3820 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:14 vg-pool0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0meta -> ../dm-1 root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0 WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data and metadata volumes. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y Converted vg/pool0 to thin pool. root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 120 Jun 21 14:15 ./ drwxr-xr-x 20 root root3840 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0 root@15-89:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%S ync Convert [lvol0_pmspare] vg ewi--- 2.00g pool0 vg twi-a-tz-- 36.00g 0.00 0.01 [pool0_tdata] vg Twi-ao 36.00g [pool0_tmeta] vg ewi-ao 2.00g If you now reboot the system, all that is gone: root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:28 ./ drwxr-xr-x 19 root root3760 Jun 21 14:28 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control The same happens if you deactivate the VG (which the reboot undoubtedly triggers). It fails because of a missing /usr/sbin/thin_check which is provided by the thin-provisioning-tools package: root@15-89:~# vgchange -a n /usr/sbin/thin_check: execvp failed: No such file or directory WARNING: Integrity check of metadata for pool vg/pool0 failed. 0 logical volume(s) in volume group "vg" now active root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:29 ./ drwxr-xr-x 19 root root3760 Jun 21 14:29 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1657646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
** Changed in: gzip (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in gzip package in Ubuntu: Confirmed Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
** Tags added: wsl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in gzip package in Ubuntu: Confirmed Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gzip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1843479 Title: gzip in Ubuntu Eoan results in Exec format error on WSL1 Status in gzip package in Ubuntu: Confirmed Bug description: Summary: Running gzip on WSL1 results in the following error: $ gzip -bash: /bin/gzip: cannot execute binary file: Exec format error What I expect to happen: gzip executes correctly on WSL1. What happens instead: gzip fails with an Exec format error. Notes: I suspect a change in how gzip is being built for Eoan is causing issues with ELF parsing on the WSL1 translation layer. For example: On Disco with gzip 1.9-3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped On Eoan with gzip 1.10-0ubuntu3: $ file /bin/gzip /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, stripped Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do not believe this is an issue in 1.10 because this error does not occur when building gzip from GNU project source on Ubuntu Eoan. Justifications: WSL1 will need to be patched in future Windows builds for this change in ELF. However that patch will likely not be backported to older builds of Windows, including Windows Enterprise/Server 2019. To ensure Eoan can run on current and older builds of Windows Ubuntu should consider looking at how it's building gzip and see if it can be made to 'play nice' until WSL1 can be updated. This was originally reported here: https://github.com/microsoft/WSL/issues/4461 Details: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 gzip: Installed: 1.10-0ubuntu3 Candidate: 1.10-0ubuntu3 Version table: *** 1.10-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1843479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843508] Re: Apt erases console output from commands that were run prior to it.
We actually do not erase the previous content, and I'm not going to run that fio command to see what that does. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1843508 Title: Apt erases console output from commands that were run prior to it. Status in apt package in Ubuntu: Invalid Bug description: Apt is erasing the previous contents of my terminal window. The output from commands that had been run prior to running apt were entirely erased from the terminal's historical record. This is seriously bad etiquette, you should not ever take a dump all over the historical record of a terminal's output. The scroll-back feature is intentionally there so you can show a linear sequence of events. Back in the day consoles were connected directly to printers, and in fact some companies still do this for security auditing purposes, so you have to presume the terminal can only be written to... this is why it's called standard out. Overwriting is a serious no no. Also I'm not happy about apt breaking scripted execution (wtf were you thinking?), but this overwriting of the console record is a flagrant violation of proper etiquette. Please do the needful! Steps to reproduce: fio --randrepeat=1 --ioengine=libaio --direct=0 --gtod_reduce=1 --name=test --filename=test -iodepth=32 --size=32G --readwrite=randrw --rwmixread=60 --bsrange=4k-1024k --numjobs=6 --group_reporting=1 -random_distribution=zipf:0.5 --loops 3 --norandommap=1 --random_generator=lfsr --unified_rw_reporting=1 apt install --reinstall zfs-dkms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.11 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-lowlatency 5.0.21 Uname: Linux 5.0.0-27-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zlua zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Tue Sep 10 16:58:22 2019 InstallationDate: Installed on 2019-05-23 (110 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1843508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
