[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

[Balint Reczey]

I verified pkgbinarymangler/138.18.04.0 by rebuilding perl for i386.
perl_i386.build:
...
Unpacking linux-libc-dev:i386 (4.15.0-29.31) over (4.15.0-15.16) ...
Preparing to unpack .../8-pkgbinarymangler_138.18.04.0_all.deb ...
Unpacking pkgbinarymangler (138.18.04.0) over (138) ...
Setting up libapt-inst2.0:i386 (1.6.3) ...
Setting up pkgbinarymangler (138.18.04.0) ...
Setting up libpng16-16:i386 (1.6.34-1ubuntu0.18.04.1) ...
Setting up apt-utils (1.6.3) ...
...
pkgstripfiles: processing control file: 
debian/build/libperl5.26/DEBIAN/control, package libperl5.26, directory debi
an/build/libperl5.26
WARNING: pkgstripfiles: no lock file name available (libperl5.26)
Skipping perl-modules-5.26 because it is not to be built
pkgstripfiles: Truncating usr/share/doc/libperl5.26/changelog.Debian.gz to 
topmost ten records
...


$ dpkg-deb -c libperl5.26_5.26.1-6ubuntu0.1_i386.deb  | grep changelog
-rw-r--r-- root/root  1859 2018-06-12 19:32 
./usr/share/doc/libperl5.26/changelog.Debian.gz

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1574351

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  New
Status in pkgbinarymangler package in Ubuntu:
  Fix Released
Status in pkgbinarymangler source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Pkgstripfiles generates different stripped documentation for arch:any 
packages depending on if arch:all packages are built at the same time. In 
practice it means that amd64 packages may end up different file contents of doc 
files compared to other architectures making multiarch installation of the 
affected packages impossible without workarounds.
   
   * To fix affected packages by a rebuild the pkgbinarymangler package needs 
to be backported, too.

   * The fix in pkgstripfiles is skipping symlinking documentation to
  dependent packages with identical content when the dependent packages
  are not built.

  [Test Case]

   * To test pkgbinarymangler rebuild perl i386 packages without arch:all 
packages with the fixed pkgbinarymangler package and observe the following 
message in the build log:
  ...
  Skipping perl-modules-5.26 because it is not to be built
  ...
   * Note that PPA builds skip the mangling steps thus the package needs to be 
built in sbuild/pbuilder/in the official archive with pkgbinarymangler added as 
an extra package in case of a local build.
   * The resulting libperl5.2? package can also analyzed to see 
changelog.Debian.gz not symlinked to perl-modules-5.2?'s changelog.

  [Regression Potential]

   * The pkgbinarymangler fix may break the pkgstripfiles script causing
  FTBFS of unrelated packages or could cause building not stripped
  packages. The former problem would be caught early, while the latter
  can be avoided by checking the build logs of a few other packages
  rebuilt with the fixed pkgbinarymangler package.

  [Original Bug Text]

  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not

[Balint Reczey]

** Description changed:

  [Impact]
  
-  * Reports from u-u incorrectly list packages from non-upgradable
+  * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"
  
-  * The incorrectly the packages incorrectly is a result of
+  * The incorrectly the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.
  
-  * The fix is removing the side effect of is_pkgname_in_blacklist()
+  * The fix is removing the side effect of is_pkgname_in_blacklist()
  
  [Test Case]
  
-  * There is a build-time test in test/test_blacklisted_wrong_origin.py
-  * TODO copy test case here from GitHub report 
+  * There is a build-time test in test/test_blacklisted_wrong_origin.py
+  * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
+ $ sudo unattended-upgrade  --verbose
+ Initial blacklisted packages: 
+ Initial whitelisted packages: 
+ Starting unattended upgrades script
+ Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
+ No packages found that can be upgraded unattended and no pending auto-removals
+ $ sudo apt upgrade
+ Reading package lists... Done
+ Building dependency tree   
+ Reading state information... Done
+ Calculating upgrade... Done
+ The following packages will be upgraded:
+   apt apt-utils ebtables initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
+   liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io 
networkd-dispatcher nplan
+   python-apt-common python3 python3-apt python3-minimal 
python3-update-manager snapd squashfs-tools
+   unattended-upgrades update-manager-core update-notifier-common
+ 27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ Need to get 24.1 MB of archives.
+ After this operation, 1454 kB of additional disk space will be used.
+ Do you want to continue? [Y/n] n
+ Abort.
+ 
+ * blacklist ebtables, set up emails from u-u, then run u-u again:
+ $ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' > 
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
+ $ sudo echo 'Unattended-Upgrade::Mail "root";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-mail
+ $ sudo unattended-upgrade  --verbose
+ Initial blacklisted packages: ebtables
+ Initial whitelisted packages: 
+ Starting unattended upgrades script
+ Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
+ Packages that will be upgraded: 
+ 
+ * Observe ebtables listed as being kept back and having upgradable origin 
with buggy u-u:
+ $ sudo cat /var/mail/mail
+ ...
+ Packages with upgradable origin but kept back:
+  ebtables=20
+ ...
+ 
+ * Upgrade u-u to a fixed version and run it, observing ebtables to be
+ not listed as having upgradable origin
+ 
  
  [Regression Potential]
  
-  * Regressions may make packages incorrectly missing from u-u's report,
+  * Regressions may make packages incorrectly missing from u-u's report,
  but the autopkgtests also cover that to some extent.
  
  [Other Info]
-  
-  * Original report: https://github.com/mvo5/unattended-upgrades/issues/116
+ 
+  * Original report: https://github.com/mvo5/unattended-
+ upgrades/issues/116

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1781176

Title:
  Blacklisted packages are included in the "upgradable origin", while
  they should not

Status in unattended-upgrades:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"

   * The incorrectly the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.

   * The fix is removing the side effect of is_pkgname_in_blacklist()

  [Test Case]

   * There is a build-time test in test/test_blacklisted_wrong_origin.py
   * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading 

[Touch-packages] [Bug 1782466] Re: package binutils-common (not installed) failed to install/upgrade: 子进程 dpkg-deb --control 返回了错误号 2

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1782466

Title:
  package binutils-common (not installed) failed to install/upgrade: 子进程
  dpkg-deb --control 返回了错误号 2

Status in binutils package in Ubuntu:
  New

Bug description:
  dpkg-deb：错误：归档 /var/cache/apt/archives/binutils_2.30-20ubuntu2~18.04_i386.deb 
含有不合时宜的成员 control.tar.xz 于 control.tar.gz 之前，放弃操作
  dpkg: 处理归档 /var/cache/apt/archives/binutils_2.30-20ubuntu2~18.04_i386.deb 
(--unpack)时出错：
   子进程 dpkg-deb --control 返回了错误号 2

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: binutils-common (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  Date: Thu Jul 19 09:33:35 2018
  DuplicateSignature: package:binutils-common:(not installed):子进程 dpkg-deb 
--control 返回了错误号 2
  ErrorMessage: 子进程 dpkg-deb --control 返回了错误号 2
  InstallationDate: Installed on 2018-06-05 (44 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: binutils
  Title: package binutils-common (not installed) failed to install/upgrade: 子进程 
dpkg-deb --control 返回了错误号 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1782466/+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 1782450] [NEW] package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 with apt-get -f install

[lsutiger]

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

Public bug reported:

Why is the system attempting to remove sudo?

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.5
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Jul 18 18:44:19 2018
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
InstallationDate: Installed on 2018-07-18 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: sudo
Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sudo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1782450

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1 with apt-get
  -f install

Status in sudo package in Ubuntu:
  New

Bug description:
  Why is the system attempting to remove sudo?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Jul 18 18:44:19 2018
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2018-07-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1782450/+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 1782450] Re: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 with apt-get -f install

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1725628
   package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1782450

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1 with apt-get
  -f install

Status in sudo package in Ubuntu:
  New

Bug description:
  Why is the system attempting to remove sudo?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Jul 18 18:44:19 2018
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2018-07-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1782450/+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 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not

[Balint Reczey]

I tested 1.1ubuntu1.18.04.4 and found the problem not fixed here. The problem 
was fixed in u-u 1.3 but changes in 1.4 made the original fix incomplete.
The side-effect of is_pkgname_in_blacklist() is still removed, but assumptions 
broke at the place where the function is called and as a result the content of 
u-u's email is the same, listing blacklisted packages like they would have 
allowed origins.

I submitted a fix for the current code in https://github.com/mvo5
/unattended-upgrades/pull/137.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1781176

Title:
  Blacklisted packages are included in the "upgradable origin", while
  they should not

Status in unattended-upgrades:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"

   * Listing the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.

   * The fix is removing the side effect of is_pkgname_in_blacklist()

  [Test Case]

   * There is a build-time test in test/test_blacklisted_wrong_origin.py
   * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
    apt apt-utils ebtables initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
    liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io 
networkd-dispatcher nplan
    python-apt-common python3 python3-apt python3-minimal 
python3-update-manager snapd squashfs-tools
    unattended-upgrades update-manager-core update-notifier-common
  27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 24.1 MB of archives.
  After this operation, 1454 kB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.

  * blacklist ebtables, set up emails from u-u, then run u-u again:
  $ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' > 
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
  $ sudo echo 'Unattended-Upgrade::Mail "root";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-mail
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages: ebtables
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  Packages that will be upgraded:

  * Observe ebtables listed as being kept back and having upgradable origin 
with buggy u-u:
  $ sudo cat /var/mail/mail
  ...
  Packages with upgradable origin but kept back:
   ebtables=20
  ...

  * Upgrade u-u to a fixed version and run it, observing ebtables to be
  not listed as having upgradable origin

  [Regression Potential]

   * Regressions may make packages incorrectly missing from u-u's
  report, but the autopkgtests also cover that to some extent.

  [Other Info]

   * Original report: https://github.com/mvo5/unattended-
  upgrades/issues/116

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1781176/+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 1782450] Re: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 with apt-get -f install

[Seth Arnold]

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

Curious, the normal way people hit this is by installing poor third-
party software but your logs look pretty boring.

You ought to be able to fix this by:

apt-get install ubuntu-minimal sudo

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1782450

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1 with apt-get
  -f install

Status in sudo package in Ubuntu:
  New

Bug description:
  Why is the system attempting to remove sudo?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Jul 18 18:44:19 2018
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2018-07-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1782450/+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 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

[Balint Reczey]

** Description changed:

  [Impact]
  
-  * Pkgstripfiles generates different stripped documentation for arch:any 
packages depending on if arch:all packages are built at the same time. In 
practice it means that amd64 packages may end up different file contents of doc 
files compared to other architectures making multiarch installation of the 
affected packages impossible without workarounds.
-  
-  * To fix affected packages by a rebuild the pkgbinarymangler package needs 
to be backported, too.
+  * Pkgstripfiles generates different stripped documentation for arch:any
+ packages depending on if arch:all packages are built at the same time.
+ In practice it means that amd64 packages may end up different file
+ contents of doc files compared to other architectures making multiarch
+ installation of the affected packages impossible without workarounds.
  
-  * The fix in pkgstripfiles is skipping symlinking documentation to
+  * To fix affected packages by a rebuild the pkgbinarymangler package
+ needs to be backported, too.
+ 
+  * The fix in pkgstripfiles is skipping symlinking documentation to
  dependent packages with identical content when the dependent packages
  are not built.
  
  [Test Case]
  
-  * To test pkgbinarymangler rebuild perl i386 packages without arch:all 
packages with the fixed pkgbinarymangler package and observe the following 
message in the build log:
+  * To test pkgbinarymangler rebuild perl i386 packages without arch:all 
packages with the fixed pkgbinarymangler package and observe the following 
message in the build log:
  ...
  Skipping perl-modules-5.26 because it is not to be built
  ...
-  * Note that PPA builds skip the mangling steps thus the package needs to be 
built in sbuild/pbuilder/in the official archive with pkgbinarymangler added as 
an extra package in case of a local build.
-  * The resulting libperl5.2? package can also analyzed to see 
changelog.Debian.gz not symlinked to perl-modules-5.2?'s changelog.
+  * Note that PPA builds skip the mangling steps thus the package needs to be 
built in sbuild/pbuilder/in the official archive with pkgbinarymangler added as 
an extra package in case of a local build.
+  * The resulting libperl5.2? package can also be analyzed to see 
changelog.Debian.gz not symlinked to perl-modules-5.2?'s changelog, but to 
check if the original bug is fixed just install libperl5.26:amd64 and 
libperl5.26:i386 using multiarch (here we assume the current architecture is 
amd64):
+ $ sudo dpkg --add-architecture i386
+ $ sudo apt update
+ $ sudo apt install libperl5.26:i386
+ 
  
  [Regression Potential]
  
-  * The pkgbinarymangler fix may break the pkgstripfiles script causing
+  * The pkgbinarymangler fix may break the pkgstripfiles script causing
  FTBFS of unrelated packages or could cause building not stripped
  packages. The former problem would be caught early, while the latter can
  be avoided by checking the build logs of a few other packages rebuilt
  with the fixed pkgbinarymangler package.
  
  [Original Bug Text]
  
  Don't run aplication after upgrade from 14.04
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package libperl5.22:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1574351

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  

[Touch-packages] [Bug 1782470] [NEW] ubuntu 16.04 linux kernel 4.15.0-24-generic wireless

[Thammu]

Public bug reported:

I am not able to connect to wifi after update. Wireless connection is
misssing in network setting. My ubuntu version is 16.04. And the kernel
version is linux kernel 4.15.0-24-generic. I can connect to wifi when I
go back to my earlier kernel version of 4.13,0-45 generic

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1782470

Title:
  ubuntu 16.04 linux kernel 4.15.0-24-generic wireless

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am not able to connect to wifi after update. Wireless connection is
  misssing in network setting. My ubuntu version is 16.04. And the
  kernel version is linux kernel 4.15.0-24-generic. I can connect to
  wifi when I go back to my earlier kernel version of 4.13,0-45 generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1782470/+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 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not

[Balint Reczey]

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: Fix Committed => In Progress

** Changed in: unattended-upgrades (Ubuntu Bionic)
 Assignee: (unassigned) => Balint Reczey (rbalint)

** Description changed:

  [Impact]
  
   * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"
  
-  * The incorrectly the packages incorrectly is a result of
+  * Listing the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.
  
   * The fix is removing the side effect of is_pkgname_in_blacklist()
  
  [Test Case]
  
   * There is a build-time test in test/test_blacklisted_wrong_origin.py
   * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
  $ sudo unattended-upgrade  --verbose
- Initial blacklisted packages: 
- Initial whitelisted packages: 
+ Initial blacklisted packages:
+ Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals
  $ sudo apt upgrade
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
-   apt apt-utils ebtables initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
-   liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io 
networkd-dispatcher nplan
-   python-apt-common python3 python3-apt python3-minimal 
python3-update-manager snapd squashfs-tools
-   unattended-upgrades update-manager-core update-notifier-common
+   apt apt-utils ebtables initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
+   liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io 
networkd-dispatcher nplan
+   python-apt-common python3 python3-apt python3-minimal 
python3-update-manager snapd squashfs-tools
+   unattended-upgrades update-manager-core update-notifier-common
  27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 24.1 MB of archives.
  After this operation, 1454 kB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.
  
  * blacklist ebtables, set up emails from u-u, then run u-u again:
  $ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' > 
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
  $ sudo echo 'Unattended-Upgrade::Mail "root";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-mail
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages: ebtables
- Initial whitelisted packages: 
+ Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
- Packages that will be upgraded: 
+ Packages that will be upgraded:
  
  * Observe ebtables listed as being kept back and having upgradable origin 
with buggy u-u:
  $ sudo cat /var/mail/mail
  ...
  Packages with upgradable origin but kept back:
-  ebtables=20
+  ebtables=20
  ...
  
  * Upgrade u-u to a fixed version and run it, observing ebtables to be
  not listed as having upgradable origin
- 
  
  [Regression Potential]
  
   * Regressions may make packages incorrectly missing from u-u's report,
  but the autopkgtests also cover that to some extent.
  
  [Other Info]
  
   * Original report: https://github.com/mvo5/unattended-
  upgrades/issues/116

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1781176

Title:
  Blacklisted packages are included in the "upgradable origin", while
  they should not

Status in unattended-upgrades:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"

   * Listing the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.

   * The fix is removing the side effect of is_pkgname_in_blacklist()

  [Test Case]

   * There is a build-time test in test/test_blacklisted_wrong_origin.py
   * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages:
  Initial 

[Touch-packages] [Bug 1782466] [NEW] package binutils-common (not installed) failed to install/upgrade: 子进程 dpkg-deb --control 返回了错误号 2

[haiy]

Public bug reported:

dpkg-deb：错误：归档 /var/cache/apt/archives/binutils_2.30-20ubuntu2~18.04_i386.deb 
含有不合时宜的成员 control.tar.xz 于 control.tar.gz 之前，放弃操作
dpkg: 处理归档 /var/cache/apt/archives/binutils_2.30-20ubuntu2~18.04_i386.deb 
(--unpack)时出错：
 子进程 dpkg-deb --control 返回了错误号 2

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: binutils-common (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
Date: Thu Jul 19 09:33:35 2018
DuplicateSignature: package:binutils-common:(not installed):子进程 dpkg-deb 
--control 返回了错误号 2
ErrorMessage: 子进程 dpkg-deb --control 返回了错误号 2
InstallationDate: Installed on 2018-06-05 (44 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
SourcePackage: binutils
Title: package binutils-common (not installed) failed to install/upgrade: 子进程 
dpkg-deb --control 返回了错误号 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: binutils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 trusty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1782466

Title:
  package binutils-common (not installed) failed to install/upgrade: 子进程
  dpkg-deb --control 返回了错误号 2

Status in binutils package in Ubuntu:
  New

Bug description:
  dpkg-deb：错误：归档 /var/cache/apt/archives/binutils_2.30-20ubuntu2~18.04_i386.deb 
含有不合时宜的成员 control.tar.xz 于 control.tar.gz 之前，放弃操作
  dpkg: 处理归档 /var/cache/apt/archives/binutils_2.30-20ubuntu2~18.04_i386.deb 
(--unpack)时出错：
   子进程 dpkg-deb --control 返回了错误号 2

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: binutils-common (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  Date: Thu Jul 19 09:33:35 2018
  DuplicateSignature: package:binutils-common:(not installed):子进程 dpkg-deb 
--control 返回了错误号 2
  ErrorMessage: 子进程 dpkg-deb --control 返回了错误号 2
  InstallationDate: Installed on 2018-06-05 (44 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: binutils
  Title: package binutils-common (not installed) failed to install/upgrade: 子进程 
dpkg-deb --control 返回了错误号 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1782466/+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 1782470] Re: ubuntu 16.04 linux kernel 4.15.0-24-generic wireless

[Kai-Heng Feng]

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1782470

Title:
  ubuntu 16.04 linux kernel 4.15.0-24-generic wireless

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I am not able to connect to wifi after update. Wireless connection is
  misssing in network setting. My ubuntu version is 16.04. And the
  kernel version is linux kernel 4.15.0-24-generic. I can connect to
  wifi when I go back to my earlier kernel version of 4.13,0-45 generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782470/+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 1777579] Re: 18.04 Dekstop LTS DNS behavior (systemd-resolved)

[Ken Sharp]

You need to learn to use ubuntu-bug

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

-- 
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/1777579

Title:
  18.04 Dekstop LTS DNS behavior (systemd-resolved)

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues 
getting local DNS to work.
  In my network I maintain a central router instance that povides DHCP and DNS 
successfully over many years. The DHCP assigns a valid address and correct DNS 
information to my above mentioned network client. However DNS resolution does 
not work for DNS records maintained in my router for my local network.
  See here: (local DNS server on .3.1)

  uho@Asus:~/Schreibtisch$ systemd-resolve --status
  Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.3.1
  uho@Asus:~/Schreibtisch$ 

  uho@Asus:~/Schreibtisch$ nslookup filou
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find filou: SERVFAIL

  uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1
  Server:   192.168.3.1
  Address:  192.168.3.1#53

  Non-authoritative answer:
  Name: filou
  Address: 192.168.3.10

  uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10
  10.3.168.192.in-addr.arpa name = filou.

  Authoritative answers can be found from:

  uho@Asus:~/Schreibtisch$

  The example above shows that DNS forward lookup for "filou" does not work, 
only reverse lookup works.
  The same behavior with explicit DNS setting in network manager.

  Any idea what's wrong? To me this looks weirdly broken.

  BTW: Old school setting in /etc/resolv.conf works like a charm.

  BR
  Uwe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777579/+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 1779438] Re: Cannot resolve names using systemd-resolved stub resolver

[Ken Sharp]

What's in nsswitch.conf?
Have you install the relevant resolver libraries?

Better yet: use ubuntu-bug.

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

-- 
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/1779438

Title:
  Cannot resolve names using systemd-resolved stub resolver

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  I am running a clean install of Ubuntu 18.04.
  This bug was also present for me on a clean install of Ubuntu 17.10 and I had 
a solution, but it appears to no longer work.

  What I expect to happen: Ping other hosts on network by name

  What happened instead:
  I can't ping other machines on network via name.
  From my Ubuntu 18.04 machine, I `ping ubuntu-test-1` and `ping 
ubuntu-test-1.localdomain` but neither work. I can ping by IP address though.

  The other machines on the network are Ubuntu Server 16.04.3 machines
  and can ping each other by name also.

  All machines on network including problem one receive DHCP leases from
  same server (192.168.20.1)

  I believe the problem is systemd-resolved stub resolver.

  `cat /etc/resolv.conf`
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # This is a dynamic resolv.conf file for connecting local clients to the
  # internal DNS stub resolver of systemd-resolved. This file lists all
  # configured search domains.
  #
  # Run "systemd-resolve --status" to see details about the uplink DNS servers
  # currently in use.
  #
  # Third party programs must not access this file directly, but only through 
the
  # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different 
way,
  # replace this symlink by a static file or a different symlink.
  #
  # See man:systemd-resolved.service(8) for details about the supported modes of
  # operation for /etc/resolv.conf.

  nameserver 127.0.0.53
  search localdomain

  
  If I change the nameserver line to the IP of my nameserver, not the stub, 
resolution works.

  nameserver 192.168.20.1
  search localdomain

  Now I can ping hosts by name.

  I used to solve this problem like this...

  `sudo systemctl disable systemd-resolved.service`
  `echo "nameserver 192.168.20.1" | sudo tee -a 
/etc/resolvconf/resolv.conf.d/tail`
  `sudo reboot`

  But /etc/resolvconf/resolv.conf.d no longer exists, and it's about
  time this problem was fixed :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779438/+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 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not

[Balint Reczey]

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-failed verification-failed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1781176

Title:
  Blacklisted packages are included in the "upgradable origin", while
  they should not

Status in unattended-upgrades:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * Reports from u-u incorrectly list packages from non-upgradable
  origins as "Packages with upgradable origin but kept back"

   * The incorrectly the packages incorrectly is a result of
  is_pkgname_in_blacklist() having a side effect and removing the side
  effect is part of fixing LP: #1396787 which fix is also being SRU-d.

   * The fix is removing the side effect of is_pkgname_in_blacklist()

  [Test Case]

   * There is a build-time test in test/test_blacklisted_wrong_origin.py
   * To reproduce the original problem set up a system where all security 
updates are installed but ebtables (from bionic-updates) is not updated:
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be upgraded:
apt apt-utils ebtables initramfs-tools initramfs-tools-bin 
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io 
networkd-dispatcher nplan
python-apt-common python3 python3-apt python3-minimal 
python3-update-manager snapd squashfs-tools
unattended-upgrades update-manager-core update-notifier-common
  27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 24.1 MB of archives.
  After this operation, 1454 kB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.

  * blacklist ebtables, set up emails from u-u, then run u-u again:
  $ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' > 
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
  $ sudo echo 'Unattended-Upgrade::Mail "root";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-mail
  $ sudo unattended-upgrade  --verbose
  Initial blacklisted packages: ebtables
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  Packages that will be upgraded: 

  * Observe ebtables listed as being kept back and having upgradable origin 
with buggy u-u:
  $ sudo cat /var/mail/mail
  ...
  Packages with upgradable origin but kept back:
   ebtables=20
  ...

  * Upgrade u-u to a fixed version and run it, observing ebtables to be
  not listed as having upgradable origin

  
  [Regression Potential]

   * Regressions may make packages incorrectly missing from u-u's
  report, but the autopkgtests also cover that to some extent.

  [Other Info]

   * Original report: https://github.com/mvo5/unattended-
  upgrades/issues/116

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1781176/+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 1719302] Re: Please include mlx4 and mlx5 InfiniBand modules

[Bug Watch Updater]

** Changed in: initramfs-tools (Debian)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1719302

Title:
  Please include mlx4 and mlx5 InfiniBand modules

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Committed

Bug description:
  Mellanox ConnectX architecture is:  mlx4_core is the lower level PCI
  driver which register on the PCI id, and protocol specific drivers are
  depended on it: mlx4_en - for Ethernet and mlx4_ib for Infiniband. NIC
  could have multiple ports which can change their type dynamically. We
  use the request_module() call to load the relevant protocol driver
  when needed: on loading time or at port type change event.

  The mlx4_core and mlx5_core modules are included in the initrd, but
  not mlx4_ib and mlx5_ib. Thus the request_module() call will not find
  these modules and fail load them. The mlx*_ib module loading will not
  be retried.

  Therefore also include mlx4_ib and mlx5_ib in the initrd to make
  autoloading them work. A patch is attached to the related Debian bug
  report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1719302/+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 1782447] [NEW] If BROWSER isn't set, sensible-browser outputs: "usage: which [-as] program ..."

[Paulo Marcel Coelho Aragão]

Public bug reported:

If environment variable BROWSER isn't set, sensible-browser always shows
this error message:

usage: which [-as] program ...

even though it goes on and opens the browser.

It's easy to reproduce:

$ unset BROWSER
$ sensible-browser http://example.com

The bug is right at the beginning:

# Prevent recursive loops, where these values are set to this script
p="$(which sensible-browser)"
[ "$(which $BROWSER || true)" = "$p" ] && BROWSER=

It could be fixed with:

[ -n "$BROWSER" -a "$(which "$BROWSER")" = "$p" ] && BROWSER=

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: sensible-utils 0.0.12
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Jul 18 20:21:36 2018
Dependencies:
 
InstallationDate: Installed on 2018-04-28 (81 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: sensible-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sensible-utils (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 sensible-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1782447

Title:
  If BROWSER isn't set, sensible-browser outputs: "usage: which [-as]
  program ..."

Status in sensible-utils package in Ubuntu:
  New

Bug description:
  If environment variable BROWSER isn't set, sensible-browser always
  shows this error message:

  usage: which [-as] program ...

  even though it goes on and opens the browser.

  It's easy to reproduce:

  $ unset BROWSER
  $ sensible-browser http://example.com

  The bug is right at the beginning:

  # Prevent recursive loops, where these values are set to this script
  p="$(which sensible-browser)"
  [ "$(which $BROWSER || true)" = "$p" ] && BROWSER=

  It could be fixed with:

  [ -n "$BROWSER" -a "$(which "$BROWSER")" = "$p" ] && BROWSER=

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sensible-utils 0.0.12
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jul 18 20:21:36 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-04-28 (81 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: sensible-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1782447/+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 1782498] [NEW] Se tilda pantalla

[Juan Pablo Montiel]

Public bug reported:

Hola amigos!
El tema es que siempre y con versiones anteriores (además de con esta) se me 
tilda la pantalla y queda el SO totalmente inmovilizado, con la pantalla en 
algunos de los colores que estaba viendo. Nunca puedo encontrar el porqué, ya 
que el equipo se bloquea y no me deja entrar a las otras terminales como tty1, 
etc.
Siempre el sistema me dice que les avisará, pero la verdad es que nunca me ha 
llegado un mensaje al respecto.

Un gran saludo a todos desde Argentina, vivo en un pueblito de 1.500
habitantes y uso Ubunto hace aproximadamente unos 10 años. Los quiero
mucho y aprecio mucho lo que hacen por nosotros como usuarios. GRACIAS

Juan Pablo Montiel
6551 - Pirovano - Bs As - Argentina

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Jul 18 23:57:18 2018
DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
InstallationDate: Installed on 2017-04-10 (464 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=5ec15496-f7c3-4826-b449-502d83c3141c ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-07-18 (0 days ago)
dmi.bios.date: 05/04/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: ALiveNF6G-VSTA
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd05/04/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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
xserver.bootTime: Wed Jul 18 23:05:59 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical MouseMOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: nouveau

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic 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/1782498

Title:
  Se tilda pantalla

Status in xorg package in Ubuntu:
  New

Bug description:
  Hola amigos!
  El tema es que siempre y con versiones anteriores (además de con esta) se me 
tilda la pantalla y queda el SO totalmente inmovilizado, con la pantalla en 
algunos de los colores que estaba viendo. Nunca puedo encontrar el porqué, ya 
que el equipo se bloquea y no me deja entrar a las otras terminales como tty1, 
etc.
  Siempre el sistema me dice que les avisará, pero la verdad es que nunca me ha 
llegado un mensaje al respecto.

  Un gran saludo a todos desde Argentina, vivo en un pueblito de 1.500
  habitantes y uso Ubunto hace aproximadamente unos 10 años. Los quiero
  mucho y aprecio mucho lo que hacen por nosotros como usuarios. GRACIAS

  Juan Pablo Montiel
  6551 - Pirovano - Bs As - Argentina

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 

[Touch-packages] [Bug 1782190] Re: Set default interface font size to 11 for communitheme sessions

[Didier Roche]

** Also affects: ubuntu-settings (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1782190

Title:
  Set default interface font size to 11 for communitheme sessions

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Bionic:
  New

Bug description:
  [Impact]

   * communitheme snap users see the gnome shell overview window
  thumbnail labels cutted off

   * 18.04 users can install the communitheme snap from within gnome-
  software

   * To fix this the default font size of the interface needs to be
  switched to 11 (again)

  [Test Case]

   * Install ubuntu

   * install the communitheme snap

   * reboot

   * select the communitheme snap session and login

   * Open "activities" by clicking "activities" in the GNOME shell's
  upper left corner or by pressing the super/ubuntu/windows key

   * Each window thumbnail is labeled with a text which is now cut

   * This is caused by a bug in gnome-shell which can't handle any other
  font size than 11 for any other font beside cantarell

  * install the new ubuntu-settings version

  * open again activities

  * check that window thumbnails aren't cut anymore

  [Regression Potential]

   * It's affecting only the communitheme session, not available by
  default and reverting to the same default than ubuntu main session

  [Other Info]

   * Gitlab upstream issue: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/378

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1782190/+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 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install

[Balint Reczey]

The problem seems to be gone on errors.ubuntu.com.
There are a few errors falsely reported against the fixed version 
(1.1ubuntu1.18.04.4) but those are cases where the buggy version upgraded the 
package and afterwards apport collected the version of the fixed package, which 
did not run yet.

Also note that in the stack trace the u-u versions are mixed,
only 1.1ubuntu1.18.04.1 raises the error at line 1065 in do_install,
but the "if dpkg_log_content:" is from 1.1ubuntu1.18.04.4.

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1935, in 
  File "/usr/bin/unattended-upgrade", line 1790, in main
cache, auto_removable_kernel_pkgs,
  File "/usr/bin/unattended-upgrade", line 1065, in do_install
if dpkg_log_content:
AssertionError: Internal error. The following packages are marked for 
removal:linux-modules-extra-4.15.0-23-generic

(https://errors.ubuntu.com/oops/84855090-8807-11e8-b8b4-fa163e192766)


** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-needed-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1779157

Title:
  /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-
  upgrade@1927:main:do_install

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.1ubuntu1.18.04.1, the problem page at 
https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  Traceback

  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1927, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1782, in main
  logfile_dpkg)
    File "/usr/bin/unattended-upgrade", line 1057, in do_install
  "removal:%s" % "".join([pkg.name for pkg in marked_delete]))
  AssertionError: Internal error. The following packages are marked for 
removal:linux-headers-4.15.0-20-generic

  Also seen as:
  https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+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 1782190] Re: Set default interface font size to 11 for communitheme sessions

[Didier Roche]

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Didier Roche (didrocks)

** Changed in: ubuntu-settings (Ubuntu Bionic)
 Assignee: (unassigned) => Didier Roche (didrocks)

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-settings (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: ubuntu-settings (Ubuntu Bionic)
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1782190

Title:
  Set default interface font size to 11 for communitheme sessions

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Bionic:
  New

Bug description:
  [Impact]

   * communitheme snap users see the gnome shell overview window
  thumbnail labels cutted off

   * 18.04 users can install the communitheme snap from within gnome-
  software

   * To fix this the default font size of the interface needs to be
  switched to 11 (again)

  [Test Case]

   * Install ubuntu

   * install the communitheme snap

   * reboot

   * select the communitheme snap session and login

   * Open "activities" by clicking "activities" in the GNOME shell's
  upper left corner or by pressing the super/ubuntu/windows key

   * Each window thumbnail is labeled with a text which is now cut

   * This is caused by a bug in gnome-shell which can't handle any other
  font size than 11 for any other font beside cantarell

  * install the new ubuntu-settings version

  * open again activities

  * check that window thumbnails aren't cut anymore

  [Regression Potential]

   * It's affecting only the communitheme session, not available by
  default and reverting to the same default than ubuntu main session

  [Other Info]

   * Gitlab upstream issue: https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/378

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1782190/+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 1782362] [NEW] dnsmasq segfaults on cnames referring to themselves

[Frank Klaassen]

Public bug reported:

If one would add a CNAME-record that would point to itself like so:
CNAME=test.example.com,test.example.com

This will result in a segfault and crash of the dnsmasq process.

Segfault on 14.04 / dnsmasq 2.68:
dnsmasq[22762]: segfault at 7ffe1727dff8 ip 7f7c60cde755 sp 
7ffe1727dff0 error 6 in libc-2.19.so[7f7c60c5e000+1be000]

Segfault on 16.04 / dnsmasq 2.75:
dnsmasq[21097]: segfault at 7ffc4bf90ff8 ip 7f268bf7ebbc sp 
7ffc4bf90ff0 error 6 in libc-2.23.so[7f268befd000+1c]


Ubuntu versions affected: Ubuntu 14.04.5 LTS & Ubuntu 16.04.4 LTS

dnsmasq version (14.04) 2.68-1ubuntu0.2
dnsmasq version (16.04): 2.75-1ubuntu0.16.04.5

** Affects: dnsmasq (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1782362

Title:
  dnsmasq segfaults on cnames referring to themselves

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If one would add a CNAME-record that would point to itself like so:
  CNAME=test.example.com,test.example.com

  This will result in a segfault and crash of the dnsmasq process.

  Segfault on 14.04 / dnsmasq 2.68:
  dnsmasq[22762]: segfault at 7ffe1727dff8 ip 7f7c60cde755 sp 
7ffe1727dff0 error 6 in libc-2.19.so[7f7c60c5e000+1be000]

  Segfault on 16.04 / dnsmasq 2.75:
  dnsmasq[21097]: segfault at 7ffc4bf90ff8 ip 7f268bf7ebbc sp 
7ffc4bf90ff0 error 6 in libc-2.23.so[7f268befd000+1c]

  
  Ubuntu versions affected: Ubuntu 14.04.5 LTS & Ubuntu 16.04.4 LTS

  dnsmasq version (14.04) 2.68-1ubuntu0.2
  dnsmasq version (16.04): 2.75-1ubuntu0.16.04.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1782362/+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 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in

[Robie Basak]

Hello Lazar, or anyone else affected,

Accepted pkgbinarymangler into bionic-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/pkgbinarymangler/138.18.04.0 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: pkgbinarymangler (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1574351

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz',
  which is different from other instances of package libperl5.22:i386

Status in perl package in Ubuntu:
  New
Status in pkgbinarymangler package in Ubuntu:
  Fix Released
Status in pkgbinarymangler source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Pkgstripfiles generates different stripped documentation for arch:any 
packages depending on if arch:all packages are built at the same time. In 
practice it means that amd64 packages may end up different file contents of doc 
files compared to other architectures making multiarch installation of the 
affected packages impossible without workarounds.
   
   * To fix affected packages by a rebuild the pkgbinarymangler package needs 
to be backported, too.

   * The fix in pkgstripfiles is skipping symlinking documentation to
  dependent packages with identical content when the dependent packages
  are not built.

  [Test Case]

   * To test pkgbinarymangler rebuild perl i386 packages without arch:all 
packages with the fixed pkgbinarymangler package and observe the following 
message in the build log:
  ...
  Skipping perl-modules-5.26 because it is not to be built
  ...
   * Note that PPA builds skip the mangling steps thus the package needs to be 
built in sbuild/pbuilder/in the official archive with pkgbinarymangler added as 
an extra package in case of a local build.
   * The resulting libperl5.2? package can also analyzed to see 
changelog.Debian.gz not symlinked to perl-modules-5.2?'s changelog.

  [Regression Potential]

   * The pkgbinarymangler fix may break the pkgstripfiles script causing
  FTBFS of unrelated packages or could cause building not stripped
  packages. The former problem would be caught early, while the latter
  can be avoided by checking the build logs of a few other packages
  rebuilt with the fixed pkgbinarymangler package.

  [Original Bug Text]

  Don't run aplication after upgrade from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 21:08:20 2016
  DpkgTerminalLog:
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  DuplicateSignature:
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
    trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  InstallationDate: Installed on 2016-04-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is 
different from other instances of package 

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~canonical-desktop-team/ubuntu/+source/gdm3/+git/gdm3/+merge/349818

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421

Title:
  Error message for a faulty ~/.profile script

Status in gdm:
  Won't Fix
Status in gdm package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in gdm source package in Trusty:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Released
Status in gdm source package in Utopic:
  Fix Released
Status in lightdm source package in Utopic:
  Fix Released
Status in gdm package in Debian:
  New

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+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 1782310] [NEW] package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

[Yury Pershin]

Public bug reported:

Error emerge during startup

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-dev 3.6.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 chromium-codecs-ffmpeg-extra:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Jul 18 10:48:31 2018
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2018-05-10 (69 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.2
SourcePackage: python3-defaults
Title: package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3-defaults (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 python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1782310

Title:
  package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: проблемы
  зависимостей — оставляем не настроенным

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Error emerge during startup

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-dev 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   chromium-codecs-ffmpeg-extra:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jul 18 10:48:31 2018
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2018-05-10 (69 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: python3-defaults
  Title: package python3-dev 3.6.5-3ubuntu1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1782310/+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 1782101] Re: lightdm nonfunctional on active screen switch

[Pavel Melkozerov]

** Summary changed:

- gdm nonfunctional on active screen switch
+ lightdm  nonfunctional on active screen switch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1782101

Title:
  lightdm  nonfunctional on active screen switch

Status in lightdm package in Ubuntu:
  New

Bug description:
  I have double screen configuration (2 monitors). I face such issue:

  1. I lock computer by pressing (Win+L) or it lock itself by timer
  2. Mouse goes out of current monitor (password input field switches to second 
screen)
  3. Upper buttons becomes nonfunctional such as language selection button, 
power indicator, volume control button, logging control button.
  It happens to both screens.
  4. I cannot to unlock computer if language dosn't match language of password.
  The hard-reset is only option possible.

  I use Unity without switches to Gnome Shell.

  I tried to log gnome session (it's named Ubuntu) and I couldn't
  reproduce the issue. If lock computer I got completely different login
  page. There is no switch to the password input field if I move mouse
  pointer to the second screen. The password input field is fixed to the
  main screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.2-0ubuntu1.3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Jul 17 11:57:02 2018
  InstallationDate: Installed on 2017-04-03 (469 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (74 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2017-10-23T17:14:02.815788

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1782101/+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 1782301] [NEW] PCI/internal sound card not detected

[Mangala Dep]

Public bug reported:

1) the release of Ubunutu - Description:Ubuntu 16.04.4 LTS Release: 16.04
2) Unable to locate package pkgname


I have a HP laptop i3 7th gen. when i first installed Ubunutu 16.04 sounds 
worked like a charm. then recently sound was so bad i couldn't hear even with 
maximum volume. an today it won't work at all. pulseaudio shows dummy output. 
But when i connect my bluetooth speaker sound works.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Wed Jul 18 12:46:44 2018
InstallationDate: Installed on 2017-03-06 (498 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81ED
dmi.board.vendor: HP
dmi.board.version: 62.36
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81ED:rvr62.36:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1782301

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  1) the release of Ubunutu - Description:Ubuntu 16.04.4 LTS Release:   
16.04
  2) Unable to locate package pkgname

  
  I have a HP laptop i3 7th gen. when i first installed Ubunutu 16.04 sounds 
worked like a charm. then recently sound was so bad i couldn't hear even with 
maximum volume. an today it won't work at all. pulseaudio shows dummy output. 
But when i connect my bluetooth speaker sound works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Jul 18 12:46:44 2018
  InstallationDate: Installed on 2017-03-06 (498 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81ED
  dmi.board.vendor: HP
  dmi.board.version: 62.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81ED:rvr62.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1782301/+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 1616905] Re: lightdm install prompts about default dm even though debconf value set

[Daniel van Vugt]

** Tags added: xenial

** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1616905

Title:
  lightdm install prompts about default dm even though debconf value set

Status in gdm3 package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I've got gdm3-3.18.3-0ubuntu2 installed on a Xenial 16.04 system with
  apt. Now I need to install lightdm-1.18.2-0ubuntu2 as well and also
  need to avoid being asked any questions. But the system asks me, what
  default DM (display manager) to use.

  Copying from Bug #1020770, I set some values with debconf.

  $ echo "debconf debconf/priority select critical
  lightdm shared/default-x-display-manager select lightdm
  gdm3 shared/default-x-display-manager select lightdm" | sudo 
debconf-set-selections -v
  info: Trying to set 'debconf/priority' [select] to 'critical'
  info: Loading answer for 'debconf/priority'
  info: Trying to set 'shared/default-x-display-manager' [select] to 'lightdm'
  info: Loading answer for 'shared/default-x-display-manager'
  info: Trying to set 'shared/default-x-display-manager' [select] to 'lightdm'
  info: Loading answer for 'shared/default-x-display-manager'


  When I now install lightdm (or reconfigure it), it is ignoring that I
  set the value to "lightdm". I confirmed that by having a look at
  /etc/X11/default-display-manager:

  $ cat /etc/X11/default-display-manager
  /usr/sbin/gdm3

  When I manually answer the DM question and give "lightdm" as the
  answer, the file contains "/usr/sbin/lightdm".

  
  dpkg-reconfigure in non-interactive mode:

  $ sudo env DEBCONF_DEBUG=developer dpkg-reconfigure -fnoninteractive lightdm
  debconf (developer): starting /var/lib/dpkg/info/lightdm.prerm upgrade 
1.18.2-0ubuntu2
  debconf (developer): starting /var/lib/dpkg/info/lightdm.config reconfigure 
1.18.2-0ubuntu2
  debconf (developer): <-- METAGET shared/default-x-display-manager owners
  debconf (developer): --> 0 gdm, gdm3, lightdm, slim
  debconf (developer): <-- METAGET shared/default-x-display-manager choices
  debconf (developer): --> 0 gdm, gdm3, lightdm, slim
  debconf (developer): <-- SET shared/default-x-display-manager gdm3
  debconf (developer): --> 0 value set
  debconf (developer): <-- INPUT high shared/default-x-display-manager
  debconf (developer): --> 30 question skipped
  debconf (developer): <-- GO 
  debconf (developer): --> 0 ok
  debconf (developer): <-- GET shared/default-x-display-manager
  debconf (developer): --> 0 gdm3
  debconf (developer): starting /var/lib/dpkg/info/lightdm.postinst configure 
1.18.2-0ubuntu2
  debconf (developer): <-- STOP

  
  And in interactive mode:

  $ sudo env DEBCONF_DEBUG=developer dpkg-reconfigure lightdm
  debconf (developer): starting /var/lib/dpkg/info/lightdm.prerm upgrade 
1.18.2-0ubuntu2
  debconf (developer): starting /var/lib/dpkg/info/lightdm.config reconfigure 
1.18.2-0ubuntu2
  debconf (developer): <-- METAGET shared/default-x-display-manager owners
  debconf (developer): --> 0 gdm, gdm3, lightdm, slim
  debconf (developer): <-- METAGET shared/default-x-display-manager choices
  debconf (developer): --> 0 gdm, gdm3, lightdm, slim
  debconf (developer): <-- SET shared/default-x-display-manager gdm3
  debconf (developer): --> 0 value set
  debconf (developer): <-- INPUT high shared/default-x-display-manager
  debconf (developer): --> 0 question will be asked
  debconf (developer): <-- GO 
  debconf (developer): --> 0 ok
  debconf (developer): <-- GET shared/default-x-display-manager
  debconf (developer): --> 0 lightdm
  debconf (developer): starting /var/lib/dpkg/info/lightdm.postinst configure 
1.18.2-0ubuntu2
  debconf (developer): <-- GET shared/default-x-display-manager
  debconf (developer): --> 0 lightdm
  debconf (developer): <-- GET lightdm/daemon_name
  debconf (developer): --> 0 /usr/sbin/lightdm
  debconf (developer): <-- STOP



  To me, this is a bug in lightdm (or gdm3, which has the same code and
  problem), because it doesn't seem to honor the values set with debconf
  and thus makes it impossible to install without having to manually
  answer questions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1616905/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Łukasz Zemczak]

Hey Gunnar! The build just now succeeded after a re-run (?). Probably
some race-condition with the current package dependencies. Anyway, since
the package is built let's not re-upload for no reason. You can proceed
with testing!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1762952

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Bionic:
  Invalid

Bug description:
  [Impact]

  The keyboard-configuration package provides a tool for configuring the
  keyboard via /etc/default/keyboard. However, there are desktop GUIs
  which provide such tools as well, and in the case of gnome-control-
  center it has another idea of what /etc/default/keyboard should
  contain. In short: The different tools don't play well together.

  The proposed upload does not claim to fix all issues with this
  incompatibility. But one of the annoyances is that a pure upgrade of
  the keyboard-configuration package may result in a changed keyboard
  configuration without the user asking for it. The proposed upload does
  address that particular issue on desktop systems.

  [Test Case]

  1. On an Ubuntu 18.04 system, make sure that the contents of
 /etc/default/keyboard is 'the g-c-c style', for instance:

 XKBLAYOUT=se,us
 BACKSPACE=guess
 XKBVARIANT=,

  2. Reboot.

  3. Upgrade to the version of the keyboard-configuration package in
 bionic-proposed.

  => Find that /etc/default/keyboard was not changed through the
  upgrade.

  4. Run the command

 sudo dpkg-reconfigure keyboard-configuration

  => Find that you are now offered to change your keyboard
  configuration.

  [Regression Potential]

  As a result of this upload, and unlike before, no keyboard
  configuration will happen behind the scenes on a desktop system due to
  an upgrade of the keyboard-configuration package. This is the desired
  change, and I can't think of a case when a user would want the
  configuration to be changed without having asked for it.

  [Original description]

  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1781446] Re: Autopkgtest upgrade-all-security is failing due to apt printing to stderr in Bionic

[Balint Reczey]

Log of running autopkgtest with fixed version (1.1ubuntu1.18.04.4):
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20180713_124827_de117@/log.gz


** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1781446

Title:
  Autopkgtest upgrade-all-security is failing due to apt printing to
  stderr in Bionic

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed

Bug description:
  [Impact] 
   * The following error can be seen in autopkgtest, holding back u-u from 
migration:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20180712_151033_c44d8@/log.gz
 :
  ...
  Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-2) ...
  W: APT had planned for dpkg to do more than it reported back (2370 vs 2372).
 Affected packages: fuse:amd64
  Reading package lists...
  ...
  autopkgtest [14:17:33]: test upgrade-all-security:  - - - - - - - - - - 
results - - - - - - - - - -
  upgrade-all-security FAIL stderr: W: APT had planned for dpkg to do more than 
it reported back (2370 vs 2372).
  autopkgtest [14:17:34]: test upgrade-all-security:  - - - - - - - - - - 
stderr - - - - - - - - - -
  W: APT had planned for dpkg to do more than it reported back (2370 vs 2372).
 Affected packages: fuse:amd64
  autopkgtest [14:17:34]: test upgrade-between-snapshots: preparing testbed
  ...

  [Test Case]

   * upgrade-all-security autopkgtest

  [Regression Potential]

   * Valid errors manifesting themselves only as output from stderr may
  not fail the autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1781446/+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 1782167] Re: Computer won't suspend

[Launchpad Bug Tracker]

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

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
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/1782167

Title:
  Computer won't suspend

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After a fresh start, suspend works fine. However, after a day or two,
  the computer simply won't enter suspend state, with no error message;
  sometimes when I try several times in a row, I get a notification
  about DBus failing to suspend because it is already doing something...
  or something like this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul 17 16:08:35 2018
  MachineType: LENOVO 5474W9Y
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=1a87302c-9fb9-4110-99e5-2e0d44fec6b7 ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-06-19 (27 days ago)
  dmi.bios.date: 04/11/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5JKT55AUS
  dmi.board.vendor: LENOVO
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr5JKT55AUS:bd04/11/2011:svnLENOVO:pn5474W9Y:pvrThinkCentreM90:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 5474W9Y
  dmi.product.version: ThinkCentre M90
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782167/+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 1708326] Re: RM: obsolete product

[Gerry Boland]

Reopening as Mir has sufficiently good Wayland support to support Qt5.
qtubuntu can be removed from the archive

** Changed in: qtubuntu (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1708326

Title:
  RM: obsolete product

Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  qtubuntu was a component of Ubuntu Phone which is no longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:qtubuntu
  No reverse dependencies found

  $ reverse-depends -b src:qtubuntu
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1708326/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Gunnar Hjalmarsson]

Verified the test case by upgrading to version 1.178ubuntu2.1 of

- console-setup
- console-setup-linux
- keyboard-configuration

from bionic-proposed. Result as expected.

** 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 console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1762952

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

Status in console-setup package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Bionic:
  Invalid

Bug description:
  [Impact]

  The keyboard-configuration package provides a tool for configuring the
  keyboard via /etc/default/keyboard. However, there are desktop GUIs
  which provide such tools as well, and in the case of gnome-control-
  center it has another idea of what /etc/default/keyboard should
  contain. In short: The different tools don't play well together.

  The proposed upload does not claim to fix all issues with this
  incompatibility. But one of the annoyances is that a pure upgrade of
  the keyboard-configuration package may result in a changed keyboard
  configuration without the user asking for it. The proposed upload does
  address that particular issue on desktop systems.

  [Test Case]

  1. On an Ubuntu 18.04 system, make sure that the contents of
 /etc/default/keyboard is 'the g-c-c style', for instance:

 XKBLAYOUT=se,us
 BACKSPACE=guess
 XKBVARIANT=,

  2. Reboot.

  3. Upgrade to the version of the keyboard-configuration package in
 bionic-proposed.

  => Find that /etc/default/keyboard was not changed through the
  upgrade.

  4. Run the command

 sudo dpkg-reconfigure keyboard-configuration

  => Find that you are now offered to change your keyboard
  configuration.

  [Regression Potential]

  As a result of this upload, and unlike before, no keyboard
  configuration will happen behind the scenes on a desktop system due to
  an upgrade of the keyboard-configuration package. This is the desired
  change, and I can't think of a case when a user would want the
  configuration to be changed without having asked for it.

  [Original description]

  Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
  18.04

  Steps to reproduce:
  1. Define two keyboard input methods in Settings -> Region & Language -> 
Input Sources
  2. Open several applications
  3. Observe that application windows can be iterated with Alt + Tab
  4. Once application window iteration was begun with Alt + Tab, try to iterate 
backwards with Alt + Shift + Tab.
  5. Try to change keyboard input method switching hotkeys in Settings -> 
Region & Language -> Input Sources -> Options.
  6. Observe that Keyboard shortcut for "Alternative switch to next source" is 
set to "Alt + Shift" and that keyboard shortcuts can only be changed in 
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
  7. Observe that the shortcut for "Alternative switch to next source" is not 
available for configuration in Settings -> Devices -> Keyboard -> Keyboard 
Shortcuts.

  Actual state:
  * Performing step 4 does not select the previous app in application switcher 
but instead changes  keyboard input method.

  Expected state:
  * The shortcut for "Alternative switch to next source" can be changed and / 
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.

  Notes:
  * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to 
next source" did not exist in that version of Gnome Shell.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1708326] Re: RM: obsolete product

[Launchpad Bug Tracker]

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

** Changed in: qtubuntu (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1708326

Title:
  RM: obsolete product

Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  qtubuntu was a component of Ubuntu Phone which is no longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:qtubuntu
  No reverse dependencies found

  $ reverse-depends -b src:qtubuntu
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1708326/+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 1761771] Re: package unattended-upgrades (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[Balint Reczey]

Unattended-upgrades' postinst only triggered the problem which is in
monit/redis:

...
Purging configuration files for unattended-upgrades (0.90ubuntu0.9) ...
insserv: warning: script 'redis_6379' missing LSB tags and overrides
insserv: There is a loop between service monit and redis_6379 if stopped
insserv: loop involving service redis_6379 at depth 2
insserv: loop involving service monit at depth 1
insserv: Stopping redis_6379 depends on monit and therefore on system facility 
`$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package unattended-upgrades (--purge):
...

Please check the mentioned init.d scripts/services.


** Package changed: unattended-upgrades (Ubuntu) => redis (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1761771

Title:
  package unattended-upgrades (not installed) failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in redis package in Ubuntu:
  New

Bug description:
  shabeebk@shabeeb:~$ sudo apt --purge remove unattended-upgrades
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
unattended-upgrades*
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  11 not fully installed or removed.
  After this operation, 315 kB disk space will be freed.
  Do you want to continue? [Y/n] Y
  (Reading database ... 255908 files and directories currently installed.)
  Removing unattended-upgrades (0.90ubuntu0.9) ...
  Purging configuration files for unattended-upgrades (0.90ubuntu0.9) ...
  insserv: warning: script 'redis_6379' missing LSB tags and overrides
  insserv: There is a loop between service monit and redis_6379 if stopped
  insserv:  loop involving service redis_6379 at depth 2
  insserv:  loop involving service monit at depth 1
  insserv: Stopping redis_6379 depends on monit and therefore on system 
facility `$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package unattended-upgrades (--purge):
   subprocess installed post-removal script returned error exit status 1
  Processing triggers for man-db (2.7.5-1) ...
  Errors were encountered while processing:
   unattended-upgrades
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Apr  6 20:14:11 2018
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-08-22 (227 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades (not installed) failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1761771/+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 1708326] Re: RM: obsolete product

[Andy Whitcroft]

Not in use by anything either:

  $ seeded-in-ubuntu -b qtubuntu-android qtubuntu-desktop
  qtubuntu-android is not seeded (and may not exist).
  qtubuntu-desktop is not seeded (and may not exist).
  $ reverse-depends src:qtubuntu
  No reverse dependencies found

Removing:

$ remove-package -m 'Obselete product -- LP: #1708326' -s cosmic-proposed 
qtubuntu
Removing packages from cosmic-proposed:
qtubuntu 0.64+17.10.20170707-0ubuntu8 in cosmic
Comment: Obselete product -- LP: #1708326
1 package successfully removed.

$ remove-package -m 'Obselete product -- LP: #1708326' -s cosmic qtubuntu
Removing packages from cosmic:
qtubuntu 0.64+17.10.20170707-0ubuntu7 in cosmic
qtubuntu-android 0.64+17.10.20170707-0ubuntu7 in cosmic arm64
qtubuntu-android 0.64+17.10.20170707-0ubuntu7 in cosmic armhf
qtubuntu-desktop 0.64+17.10.20170707-0ubuntu7 in cosmic amd64
qtubuntu-desktop 0.64+17.10.20170707-0ubuntu7 in cosmic arm64
qtubuntu-desktop 0.64+17.10.20170707-0ubuntu7 in cosmic armhf
qtubuntu-desktop 0.64+17.10.20170707-0ubuntu7 in cosmic i386
qtubuntu-desktop 0.64+17.10.20170707-0ubuntu7 in cosmic ppc64el
qtubuntu-desktop 0.64+17.10.20170707-0ubuntu7 in cosmic s390x
Comment: Obselete product -- LP: #1708326
1 package successfully removed.


** Changed in: qtubuntu (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1708326

Title:
  RM: obsolete product

Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  qtubuntu was a component of Ubuntu Phone which is no longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:qtubuntu
  No reverse dependencies found

  $ reverse-depends -b src:qtubuntu
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1708326/+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 1708326] Re: RM: obsolete product

[Andy Whitcroft]

No longer seeded, and according to the project people is not needed in
cosmic as mir now can talk directly.

** Changed in: qtubuntu (Ubuntu)
   Importance: Undecided => Medium

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1708326

Title:
  RM: obsolete product

Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  qtubuntu was a component of Ubuntu Phone which is no longer developed.

  Please remove this package from the Ubuntu Archive.

  $ reverse-depends src:qtubuntu
  No reverse dependencies found

  $ reverse-depends -b src:qtubuntu
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1708326/+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 1780996] Re: Convert triggers to noawait

[Julian Andres Klode]

I'm not convinced that noawait is the right choice for libomxil-
bellagio-bin. The plugins are unusable without being registered. That
said, nothing depends on libomxil-bellagio-bin now, so the trigger might
never get run in the first place - switching to noawait does not make it
any more fragile:

Assuming a package that depends on a plugin and makes use of it in the
postinst, you currently do not get any guarantee that installing plugin
foo will make plugin foo usable, unless you also depend on -bin. But if
you depend on -bin anyway, the guarantee with noawait is the same, as
the trigger for bin will have been processed before your package is
configured.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1780996

Title:
  Convert triggers to noawait

Status in appstream package in Ubuntu:
  Fix Released
Status in bumblebee package in Ubuntu:
  Fix Released
Status in clutter-imcontext package in Ubuntu:
  Triaged
Status in django-countries package in Ubuntu:
  Fix Released
Status in dochelp package in Ubuntu:
  Fix Released
Status in dovecot package in Ubuntu:
  Fix Released
Status in fusiondirectory package in Ubuntu:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in gosa package in Ubuntu:
  Won't Fix
Status in guile-2.0 package in Ubuntu:
  Fix Released
Status in guile-2.2 package in Ubuntu:
  Fix Released
Status in hicolor-icon-theme package in Ubuntu:
  Fix Released
Status in libomxil-bellagio package in Ubuntu:
  Triaged
Status in libreoffice package in Ubuntu:
  Fix Released
Status in ltsp package in Ubuntu:
  Fix Released
Status in mate-icon-theme package in Ubuntu:
  Fix Released
Status in maxima package in Ubuntu:
  Fix Released
Status in neurodebian package in Ubuntu:
  Fix Released
Status in nevow package in Ubuntu:
  Fix Released
Status in octave package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Fix Released
Status in pike7.8 package in Ubuntu:
  Fix Released
Status in pike8.0 package in Ubuntu:
  Fix Released
Status in postgresql-common package in Ubuntu:
  Fix Released
Status in qgis package in Ubuntu:
  Fix Released
Status in reconf-inetd package in Ubuntu:
  Won't Fix
Status in shared-mime-info package in Ubuntu:
  Fix Released
Status in sphinx package in Ubuntu:
  Fix Released
Status in syslog-ng-incubator package in Ubuntu:
  Fix Released
Status in tex-common package in Ubuntu:
  Fix Released
Status in wokkel package in Ubuntu:
  Fix Released
Status in xpdf package in Ubuntu:
  Fix Released
Status in yorick package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Committed
Status in bumblebee source package in Xenial:
  Fix Committed
Status in clutter-imcontext source package in Xenial:
  Won't Fix
Status in django-countries source package in Xenial:
  Fix Committed
Status in dochelp source package in Xenial:
  Fix Committed
Status in dovecot source package in Xenial:
  Fix Committed
Status in fusiondirectory source package in Xenial:
  Fix Committed
Status in gdk-pixbuf source package in Xenial:
  Fix Committed
Status in glib2.0 source package in Xenial:
  Fix Committed
Status in gosa source package in Xenial:
  Won't Fix
Status in guile-2.0 source package in Xenial:
  Fix Committed
Status in hicolor-icon-theme source package in Xenial:
  Fix Committed
Status in libomxil-bellagio source package in Xenial:
  Triaged
Status in libreoffice source package in Xenial:
  Triaged
Status in ltsp source package in Xenial:
  Fix Committed
Status in mate-icon-theme source package in Xenial:
  Fix Committed
Status in maxima source package in Xenial:
  Fix Committed
Status in neurodebian source package in Xenial:
  Fix Committed
Status in nevow source package in Xenial:
  Fix Committed
Status in octave source package in Xenial:
  Fix Committed
Status in packagekit source package in Xenial:
  Fix Committed
Status in pike7.8 source package in Xenial:
  Fix Committed
Status in pike8.0 source package in Xenial:
  Fix Committed
Status in postgresql-common source package in Xenial:
  Fix Committed
Status in qgis source package in Xenial:
  Fix Committed
Status in reconf-inetd source package in Xenial:
  Won't Fix
Status in shared-mime-info source package in Xenial:
  Fix Committed
Status in sphinx source package in Xenial:
  Fix Committed
Status in syslog-ng-incubator source package in Xenial:
  In Progress
Status in tex-common source package in Xenial:
  Fix Committed
Status in wokkel source package in Xenial:
  Fix Committed
Status in xpdf source package in Xenial:
  Fix Committed
Status in yorick source package in Xenial:
  Fix Committed
Status in appstream source package in Bionic:
  Fix Released
Status in bumblebee source package in Bionic:
  Fix Released
Status in clutter-imcontext source package in Bionic:
  Won't Fix
Status in 

[Touch-packages] [Bug 1237042] Re: ureadahead source needs "tracing_enabled" changed to "tracing_on" for 12.04.3

[Lucas Magasweran]

The following error could also indicate that your kernel doesn't have
the required tracepoints.

ureadahead: Error while tracing: No such file or directory

If you're not running a stock Ubuntu kernel you will need a patch [1]
(worked on my 4.14 Debian kernel). Unfortunately, these trace events
will not be upstreamed [2].

[1] http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?h=hwe=7744c33fdad887074a481fd4d21ccb6670ac62e6

[2] https://patchwork.kernel.org/patch/9254717/

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1237042

Title:
  ureadahead source needs "tracing_enabled" changed to "tracing_on" for
  12.04.3

Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of Ubuntu 12.04.3 (64-bit), ureadahead was always
  exiting with status code 5.

  When manually run as:  sudo /sbin/ureadahead --force-trace --debug
  The output is:
  Counted 4 CPUs
  trace: Missing uselib tracing: No such file or directory
  ureadahead: Error while tracing: No such file or directory

  The uselib tracing notice is not important.  The "error while tracing" notice 
lead me to compare ureadahead sources between 12.04.3 and 13.04.  Note that 
ureadahead in 13.04 works.  I noticed this difference on lines 195 and 232:
if (set_value (dfd, "tracing_enabled",
  vs:
if (set_value (dfd, "tracing_on",

  This change is mentioned in the changelog as:

  ureadahead (0.100.0-13) raring; urgency=low
* src/trace.c: tracing_enabled is deprecated and gone, switch to tracing_on
  (LP: #1085766).
   -- Andy Whitcroft   Fri, 11 Jan 2013 12:05:17 +

  I suspect that this issue occurs in 12.04.3 because it is now using
  the newer raring kernel 3.8.0-31.  Previous flavors of 12.04 such as
  12.04.2 do not seem to exhibit this ureadahead issue, probably because
  the kernel is older 3.5.xx.

  As a proof-of-concept test, I hex edited the 12.04.3 /sbin/ureadahead
  to change "tracing_enabled" to "tracing_on".  Upon reboot, now
  ureadahead works, generates the /var/lib/ureadahead/pack file, and it
  does not report status code 5.

  Another workaround is to use the ureadahead binary from 13.04, but the
  updated /lib/x86_64-linux-gnu/libext2fs.so.2.4 is also required from
  13.04.

  
  $ lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

  $ apt-cache policy ureadahead
  ureadahead:
Installed: 0.100.0-12
Candidate: 0.100.0-12
Version table:
   *** 0.100.0-12 0
  500 http://mirror.peer1.net/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1237042/+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 1429098] Re: systemd[1]: ureadahead.service fails on vanilla kernels, needs Ubuntu kernel patch

[Lucas Magasweran]

A non-Ubuntu kernel doesn't have the required tracepoints and will
result in the following error.

ureadahead: Error while tracing: No such file or directory

If you're not running a stock Ubuntu kernel you will need a patch [1]
(worked on my 4.14 Debian kernel) or [2] (original patch).
Unfortunately, these trace events will never be upstreamed [3].

[1] 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=hwe=7744c33fdad887074a481fd4d21ccb6670ac62e6
 
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/462111
[3] https://patchwork.kernel.org/patch/9254717/

** Changed in: ureadahead (Ubuntu)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ureadahead in Ubuntu.
https://bugs.launchpad.net/bugs/1429098

Title:
  systemd[1]: ureadahead.service fails on vanilla kernels, needs Ubuntu
  kernel patch

Status in ureadahead package in Ubuntu:
  Invalid

Bug description:
  dmesg:
  [4.717252] systemd[1]: ureadahead.service failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-4ubuntu3
  Uname: Linux 4.0.0-04rc2-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  6 08:55:40 2015
  InstallationDate: Installed on 2014-09-25 (162 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.0.0-04rc2-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 init=/lib/systemd/systemd
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  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.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1429098/+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 1782395] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 "apareceu do nad

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1781849
   package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1782395

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4 "apareceu do nada"

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  apareceu isso do nada

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jul 15 21:42:36 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1782395/+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 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Viktor Nenadić]

I did like Dimitri wrote

sudo apt-get install --reinstall hplip hplip-data
sudo apt-get install --reinstall python3

and that seems to solve my problem.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1779237

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  Only Ubuntu Update

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jun 28 22:51:28 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-04-13 (76 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+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 1782395] [NEW] package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 "apareceu do n

[joao gabriel pacheco]

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

Public bug reported:

apareceu isso do nada

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3 3.6.5-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Jul 15 21:42:36 2018
ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.2
SourcePackage: python3-defaults
Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python3-defaults (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 python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1782395

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4 "apareceu do nada"

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  apareceu isso do nada

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jul 15 21:42:36 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1782395/+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 1765401] Re: gtk+ toolbar style setting ignored in bionic?

[Steve Dodd]

Linking Jonathan's mailing list thread for reference:
https://lists.gnucash.org/pipermail/gnucash-user/2018-April/076587.html

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1765401

Title:
  gtk+ toolbar style setting ignored in bionic?

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  I like big buttons with text labels below them in GnuCash toolbars.

  Fortunately, that's exactly what I had in Ubuntu 17.10.

  However, having upgraded to 18.04 this morning, suddenly the GnuCash
  toolbars are back to being small buttons with no text labels.

  There are SO MANY PLACES to set this preference, and yet, it's not
  working:

  $ gconftool-2 --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ gconftool --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ dconf  dump /org/gnome/desktop/interface/ | grep toolbar
  toolbar-style='both'
  $ gtk-query-settings | grep toolbar
  ! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ
  ! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR

  I have no idea why that last one says "both-horiz" rather than "both".
  I honestly have no idea where that setting is coming from and can't
  find any way to find out. (I even tried running strace on gtk-query-
  settings to see what it was reading, and that didn't help.)

  I can't find any way to change this setting in gnome-tweaks.

  Is the ability to have large icons with text below them simply gone in
  18.04, or has the setting migrated to yet another location that I have
  to set it in now (it seems like Ubuntu and/or GNOME decides to move
  settings to a completely new backend just for the heck of it every few
  releases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk2.0-bin 2.24.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 08:46:15 2018
  InstallationDate: Installed on 2016-01-16 (824 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+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 1765401] Re: gtk+ toolbar style setting ignored in bionic?

[Steve Dodd]

Another thread relevant, at least for the gnucash aspect of this bug:
https://lists.gnucash.org/pipermail/gnucash-user/2018-March/075769.html

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1765401

Title:
  gtk+ toolbar style setting ignored in bionic?

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  I like big buttons with text labels below them in GnuCash toolbars.

  Fortunately, that's exactly what I had in Ubuntu 17.10.

  However, having upgraded to 18.04 this morning, suddenly the GnuCash
  toolbars are back to being small buttons with no text labels.

  There are SO MANY PLACES to set this preference, and yet, it's not
  working:

  $ gconftool-2 --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ gconftool --search-key-regex toolbar
   /desktop/gnome/interface/toolbar_style = both
   /desktop/gnome/interface/toolbar_detachable = false
   /desktop/gnome/interface/toolbar_icons_size = large-toolbar
  $ dconf  dump /org/gnome/desktop/interface/ | grep toolbar
  toolbar-style='both'
  $ gtk-query-settings | grep toolbar
  ! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ
  ! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR

  I have no idea why that last one says "both-horiz" rather than "both".
  I honestly have no idea where that setting is coming from and can't
  find any way to find out. (I even tried running strace on gtk-query-
  settings to see what it was reading, and that didn't help.)

  I can't find any way to change this setting in gnome-tweaks.

  Is the ability to have large icons with text below them simply gone in
  18.04, or has the setting migrated to yet another location that I have
  to set it in now (it seems like Ubuntu and/or GNOME decides to move
  settings to a completely new backend just for the heck of it every few
  releases).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk2.0-bin 2.24.32-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 19 08:46:15 2018
  InstallationDate: Installed on 2016-01-16 (824 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+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 1644975] Re: Resume from disk (swapfile) fails

[Bug Watch Updater]

** Changed in: initramfs-tools (Debian)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1644975

Title:
  Resume from disk (swapfile) fails

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Debian:
  New

Bug description:
  Well, hibernation with swap file doesn't work while hibernation with
  swap partition works perfectly fine with the exactly same
  configuration and hardware.

  The reason is that when resuming from swap file, initramfs script
  can't correctly detect the machine are hibernated from the last shut
  down.

  And I investigated the issue and found this patch solved
  https://bugs.launchpad.net/ubuntu/+source/initramfs-
  tools/+bug/554009/+attachment/1366060/+files/resume.patch) for the
  hibernate to work.

  And it isn't applied to the package. I'd like to help this is really
  applied to the official package.

  In short, my setup is swapfile inside the system filesystem (LUKS +
  LVM2 + ext4).

  Also, I roughly followed this tutorial to prepare this configurartion
  that: https://ubuntuforums.org/showthread.php?t=1042946

  I've opening this bug because the original bug report is closed and
  getting no response...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1644975/+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 1782510] [NEW] lightdm automatically logs in after logout

[bastafidli]

Public bug reported:

Lightdm makes it impossible to logout. After I logout the lightdm logs
me automatically backs in.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Jul 19 01:18:52 2018
InstallationDate: Installed on 2016-04-26 (814 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1782510

Title:
  lightdm automatically logs in after logout

Status in lightdm package in Ubuntu:
  New

Bug description:
  Lightdm makes it impossible to logout. After I logout the lightdm logs
  me automatically backs in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jul 19 01:18:52 2018
  InstallationDate: Installed on 2016-04-26 (814 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1782510/+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 1782498] Re: Se tilda pantalla

[Daniel van Vugt]

Hello! Could you please take a photo of the problem?

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Tags added: nouveau

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- Se tilda pantalla
+ [nouveau] Se tilda pantalla

-- 
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/1782498

Title:
  [nouveau] Se tilda pantalla

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hola amigos!
  El tema es que siempre y con versiones anteriores (además de con esta) se me 
tilda la pantalla y queda el SO totalmente inmovilizado, con la pantalla en 
algunos de los colores que estaba viendo. Nunca puedo encontrar el porqué, ya 
que el equipo se bloquea y no me deja entrar a las otras terminales como tty1, 
etc.
  Siempre el sistema me dice que les avisará, pero la verdad es que nunca me ha 
llegado un mensaje al respecto.

  Un gran saludo a todos desde Argentina, vivo en un pueblito de 1.500
  habitantes y uso Ubunto hace aproximadamente unos 10 años. Los quiero
  mucho y aprecio mucho lo que hacen por nosotros como usuarios. GRACIAS

  Juan Pablo Montiel
  6551 - Pirovano - Bs As - Argentina

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jul 18 23:57:18 2018
  DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
  InstallationDate: Installed on 2017-04-10 (464 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=5ec15496-f7c3-4826-b449-502d83c3141c ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-07-18 (0 days ago)
  dmi.bios.date: 05/04/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: ALiveNF6G-VSTA
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd05/04/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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
  xserver.bootTime: Wed Jul 18 23:05:59 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1782498/+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 1782362] Re: dnsmasq segfaults on cnames referring to themselves

[ Christian Ehrhardt ]

** Also affects: dnsmasq (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: dnsmasq (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: dnsmasq (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1782362

Title:
  dnsmasq segfaults on cnames referring to themselves

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Trusty:
  New
Status in dnsmasq source package in Xenial:
  New

Bug description:
  If one would add a CNAME-record that would point to itself like so:
  CNAME=test.example.com,test.example.com

  This will result in a segfault and crash of the dnsmasq process.

  Segfault on 14.04 / dnsmasq 2.68:
  dnsmasq[22762]: segfault at 7ffe1727dff8 ip 7f7c60cde755 sp 
7ffe1727dff0 error 6 in libc-2.19.so[7f7c60c5e000+1be000]

  Segfault on 16.04 / dnsmasq 2.75:
  dnsmasq[21097]: segfault at 7ffc4bf90ff8 ip 7f268bf7ebbc sp 
7ffc4bf90ff0 error 6 in libc-2.23.so[7f268befd000+1c]

  
  Ubuntu versions affected: Ubuntu 14.04.5 LTS & Ubuntu 16.04.4 LTS

  dnsmasq version (14.04) 2.68-1ubuntu0.2
  dnsmasq version (16.04): 2.75-1ubuntu0.16.04.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1782362/+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 1782470] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1782470

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

** Tags added: bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1782470

Title:
  ubuntu 16.04 linux kernel 4.15.0-24-generic wireless

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I am not able to connect to wifi after update. Wireless connection is
  misssing in network setting. My ubuntu version is 16.04. And the
  kernel version is linux kernel 4.15.0-24-generic. I can connect to
  wifi when I go back to my earlier kernel version of 4.13,0-45 generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782470/+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 1782509] [NEW] package python-opencv 2.4.8+dfsg1-2ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[jiyeong]

Public bug reported:

i don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-opencv 2.4.8+dfsg1-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-130.156~14.04.1-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu Jul 19 13:34:38 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-11-10 (615 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: opencv
Title: package python-opencv 2.4.8+dfsg1-2ubuntu1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2018-07-11 (7 days ago)

** Affects: opencv (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1782509

Title:
  package python-opencv 2.4.8+dfsg1-2ubuntu1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in opencv package in Ubuntu:
  New

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-opencv 2.4.8+dfsg1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-130.156~14.04.1-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Jul 19 13:34:38 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-11-10 (615 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: opencv
  Title: package python-opencv 2.4.8+dfsg1-2ubuntu1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2018-07-11 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1782509/+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 1782470] Re: ubuntu 16.04 linux kernel 4.15.0-24-generic wireless

[Thammu]

As I am unable to connect to the net, obviously the command apport-
collect failed. The kernel response is given below:

cgmei@cgmei-Inspiron-5370:~$ apport-collect 1782470
ERROR: connecting to Launchpad failed: Unable to find the server at 
launchpad.net
You can reset the credentials by removing the file 
"/home/cgmei/.cache/apport/launchpad.credentials"

My network device as in lspci is below:

Network controller: Qualcomm Atheros Device 0042 (rev 31)
Subsystem: Dell Device 1810
Flags: fast devsel, IRQ 255
Memory at df00 (64-bit, non-prefetchable) [disabled] [size=2M]
Capabilities: 


** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1782470

Title:
  ubuntu 16.04 linux kernel 4.15.0-24-generic wireless

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I am not able to connect to wifi after update. Wireless connection is
  misssing in network setting. My ubuntu version is 16.04. And the
  kernel version is linux kernel 4.15.0-24-generic. I can connect to
  wifi when I go back to my earlier kernel version of 4.13,0-45 generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782470/+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 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system

[Bug Watch Updater]

** Changed in: initramfs-tools (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1667512

Title:
  update-initramfs hangs on upgrade, dpkg unusable, unbootable system

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  At least four users, including myself, are having an issue with
  update-initramfs hanging while updating ubuntu 16.04. The bug has been
  documented while attempting an update to multiple kernel versions (
  4.4.0-24, 4.4.0-62,  4.4.0-63). The bug causes any apt-get update or
  install to fail, and may also lead to an unbootable system.

  User #1 (me):
  $ uname -a
  Linux  4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  $ sudo apt-get upgrade
  Fetched 1,571 MB in 2min 9s (12.2 MB/s)   
  
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  (Reading database ... 344634 files and directories currently installed.)
  Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ...
  Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ...
  Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for cracklib-runtime (2.9.2-1build2) ...
  Processing triggers for install-info (6.1.0.dfsg.1-5) ...
  Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic

   Uh oh! Let's try to troubleshoot.

  $ sudo killall dpkg
  $ sudo dpkg --configure -a
  Setting up initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: deferring update (trigger activated)
  Setting up base-files (9.4ubuntu4.4) ...
  Installing new version of config file /etc/issue ...
  Installing new version of config file /etc/issue.net ...
  Installing new version of config file /etc/lsb-release ...
  Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  initrd.img(/boot/initrd.img-4.4.0-63-generic
  ) points to /boot/initrd.img-4.4.0-63-generic
   (/boot/initrd.img-4.4.0-63-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
  vmlinuz(/boot/vmlinuz-4.4.0-63-generic
  ) points to /boot/vmlinuz-4.4.0-63-generic
   (/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-63-generic 
/boot/vmlinuz-4.4.0-63-generic
  update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic
  ^CFailed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 1052.
  dpkg: error processing package linux-image-4.4.0-63-generic (--configure):
   subprocess installed post-installation script returned error exit status 2
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-4.4.0-63-generic; however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
linux-signed-image-4.4.0-63-generic:
   linux-signed-image-4.4.0-63-generic depends on linux-image-4.4.0-63-generic 
(= 4.4.0-63.84); however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-signed-image-4.4.0-63-generic 
(--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-signed-image-generic:
   linux-signed-image-generic depends on linux-signed-image-4.4.0-63-generic; 
however:
Package linux-signed-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-signed-image-generic (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of 
linux-image-extra-4.4.0-63-generic:
   linux-image-extra-4.4.0-63-generic depends on linux-image-4.4.0-63-generic; 
however:
Package linux-image-4.4.0-63-generic is not configured yet.

  dpkg: error processing package linux-image-extra-4.4.0-63-generic 
(--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic 

[Touch-packages] [Bug 1782511] [NEW] [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

[Salah Rifai]

Public bug reported:

none

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
 /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
 /dev/snd/controlC0:  ubuntu 2209 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 18 22:19:23 2018
InstallationDate: Installed on 2018-07-19 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
 /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
 /dev/snd/controlC0:  gdm 961 F pulseaudio
  ubuntu 2209 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX370UAR.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX370UAR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.303:bd11/16/2017:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX370UAR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1782511

Title:
  [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 2209 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 18 22:19:23 2018
  InstallationDate: Installed on 2018-07-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 2209 F...m pulseaudio
   /dev/snd/pcmC0D0p:   ubuntu 2209 F...m pulseaudio
   /dev/snd/controlC0:  gdm 961 F pulseaudio
ubuntu 2209 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX370UAR.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX370UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.303:bd11/16/2017:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX370UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1782511/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1396787] Re: checking trust of archives eats a lot of cpu

[Balint Reczey]

With 1.1ubuntu1.18.04.3 u-u runs in ~3s when no package should be
updated but there are upgradable  packages in -updates.

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20180713_084216_9f8ee@/log.gz
 :
...
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals
2.71user 0.12system 0:02.84elapsed 99%CPU (0avgtext+0avgdata 78924maxresident)k
0inputs+7736outputs (0major+22416minor)pagefaults 0swaps
...

The test for 1.1ubuntu1.18.04.4 was most likely run on a slower system
where the same run takes ~5s.

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20180713_124827_de117@/log.gz
 : 
...
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals
5.01user 0.14system 0:05.16elapsed 99%CPU (0avgtext+0avgdata 78992maxresident)k
0inputs+7736outputs (0major+22427minor)pagefaults 0swaps
...

** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1396787

Title:
  checking trust of archives eats a lot of cpu

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Unattended-upgrades consumes tens of seconds or even minutes of CPU
  time to verify the origin of the packages

   * Using excessive amount of CPU is unpleasant for desktop/laptop
  users and also wastes computation time on servers/cloud instances.

   * Unattended-upgrades' algorithm for checking and adjusting package
  origins is redesigned to visit and adjust less packages.

  [Test Case]

   * The added upgrade-all-security autopkgtest measure the time u-u needs for 
upgrading security updates on the tested release starting with no security 
updates applied to the point where all security updates are applied but all 
packages are left upgradable from -updates. The test also measures the 
time needed for --dry-run to find no updates to be installed unattended.
  * Please run autopkgtests and look for the to time results:
  ...
  All upgrades installed
  44.41user 3.06system 0:48.35elapsed 98%CPU (0avgtext+0avgdata 
164872maxresident)k
  208inputs+192376outputs (0major+642657minor)pagefaults 0swaps
  ...
  No packages found that can be upgraded unattended and no pending auto-removals
  2.83user 0.11system 0:02.98elapsed 98%CPU (0avgtext+0avgdata 
79308maxresident)k

  
  [Regression Potential] 

   * Due to algorithm redesign there is a risk that packages from
  allowed origins are not upgraded. There were unit tests for testing
  the selection of the right packages to upgrade already, but a new
  autopkgtest is also introduce to verify u-u's behavior on current
  real-life security-updates.

  
  [Original bug text]

  (System: Ubuntu 14.04, up to date packages)

  I noticed that unattended-upgrades spends a significant amount of time
  in phases where it runs at 100% cpu. On a slower machine (core 2 t7200
  2GHz) this goes on for minutes rather than seconds. This interferes
  with using the machine for other tasks.

  Using the --debug option to unattended-upgrades shows that the program
  outputs a lot of lines like the following during these 100% cpu
  phases:

  matching 'a'='trusty-updates' against '

  From this output I guess the operation executed is not so complicated
  that it should require so much cpu power. ??

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Wed Nov 26 21:53:57 2014
  InstallationDate: Installed on 2014-08-28 (90 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1396787/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1778800] Re: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error ex

[Balint Reczey]

Observing unattended-upgrades/1.1ubuntu1.18.04.4 maintainer scripts show
that the invoke-rc.d calls are indeed removed:

/var/lib/dpkg/info/unattended-upgrades.prerm:
...
# dh_installdeb will replace this with shell code automatically
# generated by other debhelper scripts.


exit 0
...

/var/lib/dpkg/info/unattended-upgrades.postinst:
...
# Automatically added by dh_installinit/11.1.6ubuntu2
if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove
" ] ; then
if [ -x "/etc/init.d/unattended-upgrades" ]; then
update-rc.d unattended-upgrades defaults >/dev/null || exit 1
fi
fi
# End automatically added section
...

** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1778800

Title:
  package unattended-upgrades 1.1ubuntu1.18.04.1 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess returned error exit status 1

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Upgrading unattended-upgrades during shutdown fails due to postinst
  trying to start the unattended-upgrades service. This can break
  installation of other security-fixes, too.

   * Unattended-upgrades is regularly SRU-d and this bug can break
  installing other important updates.

   * The fix is not starting/stopping the init.d script in postinst
  which is not useful during package installation anyway.

  [Test Case]

   * Check prerm that invoke-rc.d is not called:
  --- prerm.old 2018-06-07 01:30:55.0 +0200
  +++ /var/lib/dpkg/info/unattended-upgrades.prerm  2018-07-12 
14:04:12.294677476 +0200
  @@ -40,11 +40,6 @@
   # dh_installdeb will replace this with shell code automatically
   # generated by other debhelper scripts.
   
  -# Automatically added by dh_installinit/11.1.6ubuntu2
  -if [ -x "/etc/init.d/unattended-upgrades" ] && [ "$1" = remove ]; then
  - invoke-rc.d unattended-upgrades stop || exit 1
  -fi
  -# End automatically added section
   
   
   exit 0

  
   * Check postinst that invoke-rc.d is not called:
  --- postinst.old  2018-06-07 01:30:55.0 +0200
  +++ /var/lib/dpkg/info/unattended-upgrades.postinst   2018-07-12 
14:04:12.242676369 +0200
  @@ -108,8 +108,7 @@
   # Automatically added by dh_installinit/11.1.6ubuntu2
   if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then
if [ -x "/etc/init.d/unattended-upgrades" ]; then
  - update-rc.d unattended-upgrades defaults >/dev/null
  - invoke-rc.d unattended-upgrades start || exit 1
  + update-rc.d unattended-upgrades defaults >/dev/null || exit 1
fi
   fi
   # End automatically added section

  
  [Regression Potential] 

  * Unattended-upgrades.service may fail to start upon first
  installation. This is not an issue in default configuration since apt
  starts u-u based on timers and stops it gracefully upon shutdown.

  [Original Bug Text]

  update did not install.
  a similar thing has happened with several apps  have tried to download and 
the OS wont install them for some reason.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jun 26 22:26:14 2018
  ErrorMessage: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-08 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to 
install/upgrade: installed unattended-upgrades package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-09T09:48:10.967920

To manage 

[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal

[Brian Murray]

This is in cosmic-proposed, but hasn't migrated to -updates yet.

python3-defaults (3.6.6-1) unstable; urgency=medium

  [ Matthias Klose ]
  * Fix the idle desktop file. Closes: #901096.
  * Install the policy files in the python3 package. Closes: #901486.
  * python3-minimal: Pre-Depend on python3.6-minimal. Closes: #901001.
  * Bump version to 3.6.6.

  [ Scott Kitterman ]
  * Remove myself from uploaders

 -- Matthias Klose   Wed, 27 Jun 2018 18:18:20 +0200

** Changed in: python3-defaults (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1768379

Title:
  python3-minimal should predepend on versioned version of
  python3-minimal

Status in python3-defaults package in Ubuntu:
  Fix Committed
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in python3-defaults source package in Artful:
  Fix Released
Status in ubuntu-release-upgrader source package in Artful:
  Invalid
Status in python3-defaults source package in Bionic:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid
Status in python3-defaults package in Debian:
  Fix Released

Bug description:
  [Impact]
  Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 
LTS can fail if python3-minimial is unpacked before python3.x-minimal so a 
system won't have a usable python3 symlink. Then upgrades will fail because 
py3clean, used in prerm scripts of python3 packages, will fail with "not found".

  [Test Case]
  1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for 
Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt
  2) dpkg --unpack python3-minimal...
  3) dpkg --unpack python3-apt...

  Observe the following Traceback:

  Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ...
  /var/lib/dpkg/info/python3-apt.prerm: 6: 
/var/lib/dpkg/info/python3-apt.prerm: py3clean: not found
  dpkg: warning: subprocess old pre-removal script returned error exit status 
127
  dpkg: trying script from the new package instead ...
  /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found
  dpkg: error processing archive 
/home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack):
   subprocess new pre-removal script returned error exit status 127
  /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 127

  With the deb python3-minimal from -proposed you won't be able to
  unpack python3-minimal without first installing python3.6-minimal.
  While that may qualify as verification it'd still be good to test
  unpacking python3-apt. To do that you'll need to install
  python3.6-minimal from the target release by editing you
  /etc/apt/sources.list to the new release, running 'apt-get update',
  and then 'apt-get install python3.6-minimal'. After that's all done
  you can try steps 2 and 3 from the test case again and you should not
  receive a Traceback.

  [Regression Potential]
  Its possible this could cause or reveal different upgrade failures so some 
extensive (desktop, cloud, server) upgrade testing should be done.

  
  [A Portion of the Original Description (it was a huge blob of failure)]
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install 
failure:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+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 1773033] Re: unattended upgrade no longer actions on shutdown

[Balint Reczey]

Tested 1.1ubuntu1.18.04.4 and it worked as expected.

Log:
rbalint@yogi:~$ sudo unattended-upgrade --dry-run --verbose
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals

# here i put the laptop on battery

rbalint@yogi:~$ sudo unattended-upgrade --dry-run --verbose
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
System is on battery power, stopping
rbalint@yogi:~$ sudo vi /etc/apt/apt.conf.d/51unattended-upgrades-on-battery 
rbalint@yogi:~$  cat /etc/apt/apt.conf.d/51unattended-upgrades-on-battery
Unattended-Upgrade::OnlyOnACPower "false";
rbalint@yogi:~$ on_ac_power ; echo $?
1
rbalint@yogi:~$ sudo unattended-upgrade --dry-run --verbose
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals
rbalint@yogi:~$ dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.4 all  automatic installation 
of security upgrades


** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1773033

Title:
  unattended upgrade no longer actions on shutdown

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Unattended-upgrades does not install upgrades when it is configured
  to install updates on shutdown and when it the system is started on
  battery, but installs updates on battery in other cases.

   * This behaviour is unintended and confuses users, moreover
  installing updates on battery risks the system to be shut down in the
  middle of an upgrade due to depleting the battery.

   * This upload changes u-u to skip updates or gracefully stop when the
  system is switching to batter-powered state by default minimizing the
  risk of breaking the system.

  [Test Case]

   * Run "unattended-upgrade --dry-run --verbose" on battery and on AC
  power

   * With default configuration u-u should stop with the following message on 
battery:
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  System is on battery power, stopping

   * On AC power it should continue:
  $ sudo ./unattended-upgrade --dry-run --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals

   * Add the following configuration file and check u-u continuing even on 
battery:
  $ cat /etc/apt/apt.conf.d/51unattended-upgrades-on-battery 
  Unattended-Upgrade::OnlyOnACPower "false";
  rbalint@yogi:~/projects/deb/unattended-upgrades$ sudo ./unattended-upgrade 
--dry-run --verbose
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending auto-removals

  
  [Regression Potential] 

   * Unattended-upgrades may fail to install updates even on AC power,
  but this is unlikely to happen due to the code changed being fairly
  simple. on_ac_power may return 255 (false) Power status could not be
  determined, but this is mapped to being on AC power and installing the
  updates, only subprocess.call("on_ac_power") == 1 makes u-u skip
  updates.

  [Original Bug Text]

  Ubuntu 17.10 and 18.04 do not install updates with InstallOnShutdown
  flag set.

  post-install script on 14.04 and 16.04 would set options in
  /etc/apt/apt.conf.d/50unattended-upgrades and
  /etc/apt/apt.conf.d/10periodic to install updates on shutdown of
  ubuntu desktop. This worked on 17.10 also, until an update before the
  release of 

Re: [Touch-packages] [Bug 1782362] [NEW] dnsmasq segfaults on cnames referring to themselves

[Simon Kelley]

This was fixed upstream, in release 2.77.

Simon.


On 18/07/18 14:59, Frank Klaassen wrote:
> Public bug reported:
> 
> If one would add a CNAME-record that would point to itself like so:
> CNAME=test.example.com,test.example.com
> 
> This will result in a segfault and crash of the dnsmasq process.
> 
> Segfault on 14.04 / dnsmasq 2.68:
> dnsmasq[22762]: segfault at 7ffe1727dff8 ip 7f7c60cde755 sp 
> 7ffe1727dff0 error 6 in libc-2.19.so[7f7c60c5e000+1be000]
> 
> Segfault on 16.04 / dnsmasq 2.75:
> dnsmasq[21097]: segfault at 7ffc4bf90ff8 ip 7f268bf7ebbc sp 
> 7ffc4bf90ff0 error 6 in libc-2.23.so[7f268befd000+1c]
> 
> 
> Ubuntu versions affected: Ubuntu 14.04.5 LTS & Ubuntu 16.04.4 LTS
> 
> dnsmasq version (14.04) 2.68-1ubuntu0.2
> dnsmasq version (16.04): 2.75-1ubuntu0.16.04.5
> 
> ** Affects: dnsmasq (Ubuntu)
>  Importance: Undecided
>  Status: New
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1782362

Title:
  dnsmasq segfaults on cnames referring to themselves

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If one would add a CNAME-record that would point to itself like so:
  CNAME=test.example.com,test.example.com

  This will result in a segfault and crash of the dnsmasq process.

  Segfault on 14.04 / dnsmasq 2.68:
  dnsmasq[22762]: segfault at 7ffe1727dff8 ip 7f7c60cde755 sp 
7ffe1727dff0 error 6 in libc-2.19.so[7f7c60c5e000+1be000]

  Segfault on 16.04 / dnsmasq 2.75:
  dnsmasq[21097]: segfault at 7ffc4bf90ff8 ip 7f268bf7ebbc sp 
7ffc4bf90ff0 error 6 in libc-2.23.so[7f268befd000+1c]

  
  Ubuntu versions affected: Ubuntu 14.04.5 LTS & Ubuntu 16.04.4 LTS

  dnsmasq version (14.04) 2.68-1ubuntu0.2
  dnsmasq version (16.04): 2.75-1ubuntu0.16.04.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1782362/+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 1781183] Re: Skip updates on metered connections

[Balint Reczey]

Tested 1.1ubuntu1.18.04.4 and it worked as expected.

Log:

rbalint@yogi:~$ dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.4 all  automatic installation 
of security upgrades
rbalint@yogi:~$ sudo unattended-upgrade --dry-run --verbose
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
System is on metered connection, stopping
rbalint@yogi:~$  nmcli -t -f GENERAL.DEVICE,GENERAL.METERED dev show `ip route 
list 0/0 | sed -r 's/.*dev (\S*).*/\1/g'`
GENERAL.DEVICE:wlp4s0
GENERAL.METERED:yes (guessed)
rbalint@yogi:~$ lxc shell bb-uu11ubuntu118041 
mesg: ttyname failed: No such device
root@bb-uu11ubuntu118041:~# sudo apt install 
./unattended-upgrades_1.1ubuntu1.18.04.4_all.deb 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Note, selecting 'unattended-upgrades' instead of 
'./unattended-upgrades_1.1ubuntu1.18.04.4_all.deb'
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'sudo apt autoremove' to remove it.
Suggested packages:
  bsd-mailx default-mta | mail-transport-agent needrestart
The following packages will be upgraded:
  unattended-upgrades
1 upgraded, 0 newly installed, 0 to remove and 47 not upgraded.
Need to get 38.1 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
unattended-upgrades all 1.1ubuntu1.18.04.4 [38.1 kB]
Fetched 38.1 kB in 0s (107 kB/s)
Preconfiguring packages ...
(Reading database ... 28484 files and directories currently installed.)
Preparing to unpack .../unattended-upgrades_1.1ubuntu1.18.04.4_all.deb ...
Unpacking unattended-upgrades (1.1ubuntu1.18.04.4) over (1.1ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10) ...
Setting up unattended-upgrades (1.1ubuntu1.18.04.4) ...
Replacing config file /etc/apt/apt.conf.d/50unattended-upgrades with new version
Processing triggers for man-db (2.8.3-2) ...
root@bb-uu11ubuntu118041:~# sudo unattended-upgrade --dry-run --verbose
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals
root@bb-uu11ubuntu118041:~# logout
rbalint@yogi:~$ sudo vi /etc/apt/apt.conf.d/51unattended-upgrades-metered 
rbalint@yogi:~$ cat /etc/apt/apt.conf.d/51unattended-upgrades-metered
Unattended-Upgrade::Skip-Updates-On-Metered-Connections "false";
rbalint@yogi:~$ sudo unattended-upgrade --dry-run --verbose
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals


** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1781183

Title:
  Skip updates on metered connections

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Systems running unattended-upgrades may download updates over
  metered connections causing excessive data usage possibly making users
  being charged for the downloads.

   * Avoiding users being unexpectedly charged due to unattended-
  upgrades' activity warrants an SRU, IMO.

   * The fix uses
  NetworkMonitor.get_network_metered(NetworkMonitor.get_default()) for
  deciding if the connection is metered and skips or gracefully stops
  updates.

  [Test Case]

   * Run "unattended-upgrades --dry-run --verbose" on metered connection
 - The unfixed versions should provide the following output with default 
configuration:
  $ sudo unattended-upgrade --dry-run --verbose 
  Initial blacklisted packages: 
  Initial whitelisted packages: 
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
  No packages found that can be upgraded unattended and no pending 

[Touch-packages] [Bug 1782417] [NEW] package libperl5.26 5.26.2-6 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libper

[rinoux]

Public bug reported:

I dont know

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libperl5.26 5.26.2-6 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu5
Architecture: amd64
Date: Wed Jul 11 09:13:14 2018
DuplicateSignature:
 package:libperl5.26:5.26.2-6 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
 Unpacking libperl5.26:i386 (5.26.2-6) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-vRlw31/19-libperl5.26_5.26.2-6_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
InstallationDate: Installed on 2016-07-02 (746 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu3
 apt  1.7.0~alpha2
SourcePackage: perl
Title: package libperl5.26 5.26.2-6 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: perl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package cosmic package-conflict

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1782417

Title:
  package libperl5.26 5.26.2-6 [modified:
  usr/share/doc/libperl5.26/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  I dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libperl5.26 5.26.2-6 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  Date: Wed Jul 11 09:13:14 2018
  DuplicateSignature:
   package:libperl5.26:5.26.2-6 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
   Unpacking libperl5.26:i386 (5.26.2-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-vRlw31/19-libperl5.26_5.26.2-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2016-07-02 (746 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha2
  SourcePackage: perl
  Title: package libperl5.26 5.26.2-6 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1782417/+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 1782417] Re: package libperl5.26 5.26.2-6 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1782417

Title:
  package libperl5.26 5.26.2-6 [modified:
  usr/share/doc/libperl5.26/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  I dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libperl5.26 5.26.2-6 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  Date: Wed Jul 11 09:13:14 2018
  DuplicateSignature:
   package:libperl5.26:5.26.2-6 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
   Unpacking libperl5.26:i386 (5.26.2-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-vRlw31/19-libperl5.26_5.26.2-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2016-07-02 (746 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha2
  SourcePackage: perl
  Title: package libperl5.26 5.26.2-6 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1782417/+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 1782167] Re: Computer won't suspend

[A.Kromic]

Just a note, I'm not really sure this is indeed a *systemd* bug,
unfortunately I can't be sure yet I had to file it against a package. I
made an (un?)educated guess based on the DBus message (I know systemd is
intimately connected to DBus), on the fact systemd is connected to
device management (udev) and finally on the fact that systemd does
everything and the kitchen sink. It could also be X, kernel, something
else... Unfortunately there are no messages in the syslog to give any
clue...

-- 
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/1782167

Title:
  Computer won't suspend

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After a fresh start, suspend works fine. However, after a day or two,
  the computer simply won't enter suspend state, with no error message;
  sometimes when I try several times in a row, I get a notification
  about DBus failing to suspend because it is already doing something...
  or something like this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul 17 16:08:35 2018
  MachineType: LENOVO 5474W9Y
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=1a87302c-9fb9-4110-99e5-2e0d44fec6b7 ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-06-19 (27 days ago)
  dmi.bios.date: 04/11/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5JKT55AUS
  dmi.board.vendor: LENOVO
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr5JKT55AUS:bd04/11/2011:svnLENOVO:pn5474W9Y:pvrThinkCentreM90:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 5474W9Y
  dmi.product.version: ThinkCentre M90
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782167/+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 1537528] Re: byobu-config segfault with screen backend

[Robie Basak]

Hello Nick, or anyone else affected,

Accepted slang2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/slang2/2.3.0-2ubuntu1.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: slang2 (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to newt in Ubuntu.
https://bugs.launchpad.net/bugs/1537528

Title:
  byobu-config segfault with screen backend

Status in byobu package in Ubuntu:
  Invalid
Status in newt package in Ubuntu:
  Invalid
Status in slang2 package in Ubuntu:
  Fix Released
Status in slang2 source package in Xenial:
  Fix Committed
Status in byobu package in Debian:
  New

Bug description:
  [Impact]

   * Backport Debian fix for a crash in byobu due to libslang2

  [Test Case]

   * byobu-screen
   * in there hit F9 or start byobu-config
   * without the fix this crashes

  [Regression Potential]

   * This is changing a libs implementation and
  $ reverse-depends src:slang2 -r xenial
 is quite a long list. OTOH this is somewhat ok as the change is in 
 Debian and Ubuntu for more than three releases now and nothing around 
 it seems to have totally broken.
 Never the less the biggest risk I see is something unexpected in one of 
 the other libslang2 users.
 

  [Other Info]
   
   * n/a

  ---

  When running byobu with the screen backend byobu-config segfaults when
  trying to open it by pressing F9.

  Steps to reproduce.

  1. Configure byobu to use screen for the backend
  2. Press F9 to open the configuration menu
  3. The console flashes then returns to your shell window.

  Running byobu-config manually within a byobu screen session shows it's
  segfaulting. It does not crash running it outside of screen.

  byobu:
    Installed: 5.101-0ubuntu1~wily
    Candidate: 5.101-0ubuntu1~wily
    Version table:
   *** 5.101-0ubuntu1~wily 0
  500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.97-0ubuntu1 0
  500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[zanonmark]

Seems solved on Ubuntu 18.04.

-- 
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/1574667

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1782342] [NEW] mawk memory corruption on recent tzdb data

[Paul Eggert]

Public bug reported:

mawk corrupts memory and dumps core when processing recent tzdb
releases. Although Ubuntu users can work around the problem by using
'make AWK=gawk', it would be better if ordinary 'make' worked (where AWK
defaults to awk, and awk on Ubuntu defaults to mawk.

Since this is memory corruption there may well be a security
vulnerability in mawk. I have not checked for this, though.

A simple fix would be to upgrade mawk to the current upstream release. I
see that there's already a request to do that; see Bug#1332114. I don't
know why Debian and Ubuntu are wedged on an ancient upstream version.

To reproduce the problem, download the most recent tzdb release and run
'make AWK=mawk vanguard.zi'. A shell transcript follows. I ran this on
Ubuntu 16.04.4 LTS x86-64; 'dpkg -s mawk' reports 'Version:
1.3.3-17ubuntu2'. The shell commands I ran were:

wget https://www.iana.org/time-zones/repository/releases/tzdb-2018e.tar.lz
tar xf tzdb-2018e.tar.lz
cd tzdb-2018e
make AWK=mawk vanguard.zi

Here's the behavior I observed:

$ wget https://www.iana.org/time-zones/repository/releases/tzdb-2018e.tar.lz
--2018-07-18 04:09:59--  
https://www.iana.org/time-zones/repository/releases/tzdb-2018e.tar.lz
Resolving www.iana.org (www.iana.org)... 192.0.32.8, 2620:0:2d0:200::8
Connecting to www.iana.org (www.iana.org)|192.0.32.8|:443... connected.
HTTP request sent, awaiting response... 302 FOUND
Location: https://data.iana.org/time-zones/releases/tzdb-2018e.tar.lz 
[following]
--2018-07-18 04:10:00--  
https://data.iana.org/time-zones/releases/tzdb-2018e.tar.lz
Resolving data.iana.org (data.iana.org)... 72.21.81.189, 
2606:2800:11f:bb5:f27:227f:1bbf:a0e
Connecting to data.iana.org (data.iana.org)|72.21.81.189|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 437679 (427K) [application/x-tar]
Saving to: ‘tzdb-2018e.tar.lz’

tzdb-2018e.tar.lz   100%[===>] 427.42K  --.-KB/sin
0.06s

2018-07-18 04:10:00 (6.49 MB/s) - ‘tzdb-2018e.tar.lz’ saved
[437679/437679]

$ tar xf tzdb-2018e.tar.lz
$ cd tzdb-2018e
$ make AWK=mawk vanguard.zi
mawk -v DATAFORM=`expr vanguard.zi : '\(.*\).zi'` -f ziguard.awk \
  africa antarctica asia australasia europe northamerica southamerica 
etcetera systemv factory backward  >vanguard.zi.out
*** Error in `mawk': malloc(): memory corruption: 0x01ebc4f0 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7fb09870f7e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x8213e)[0x7fb09871a13e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x54)[0x7fb09871c184]
mawk[0x40ff0f]
mawk[0x405dff]
mawk[0x40e1e0]
mawk[0x406b6e]
mawk[0x40185d]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fb0986b8830]
mawk[0x40188d]
=== Memory map: 
0040-0041b000 r-xp  08:01 268
/usr/bin/mawk
0061a000-0061b000 r--p 0001a000 08:01 268
/usr/bin/mawk
0061b000-0061d000 rw-p 0001b000 08:01 268
/usr/bin/mawk
0061d000-00621000 rw-p  00:00 0 
01ea-01ec1000 rw-p  00:00 0  [heap]
7fb09400-7fb094021000 rw-p  00:00 0 
7fb094021000-7fb09800 ---p  00:00 0 
7fb098482000-7fb098498000 r-xp  08:01 3019293
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fb098498000-7fb098697000 ---p 00016000 08:01 3019293
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fb098697000-7fb098698000 rw-p 00015000 08:01 3019293
/lib/x86_64-linux-gnu/libgcc_s.so.1
7fb098698000-7fb098858000 r-xp  08:01 3018864
/lib/x86_64-linux-gnu/libc-2.23.so
7fb098858000-7fb098a58000 ---p 001c 08:01 3018864
/lib/x86_64-linux-gnu/libc-2.23.so
7fb098a58000-7fb098a5c000 r--p 001c 08:01 3018864
/lib/x86_64-linux-gnu/libc-2.23.so
7fb098a5c000-7fb098a5e000 rw-p 001c4000 08:01 3018864
/lib/x86_64-linux-gnu/libc-2.23.so
7fb098a5e000-7fb098a62000 rw-p  00:00 0 
7fb098a62000-7fb098b6a000 r-xp  08:01 3018856
/lib/x86_64-linux-gnu/libm-2.23.so
7fb098b6a000-7fb098d69000 ---p 00108000 08:01 3018856
/lib/x86_64-linux-gnu/libm-2.23.so
7fb098d69000-7fb098d6a000 r--p 00107000 08:01 3018856
/lib/x86_64-linux-gnu/libm-2.23.so
7fb098d6a000-7fb098d6b000 rw-p 00108000 08:01 3018856
/lib/x86_64-linux-gnu/libm-2.23.so
7fb098d6b000-7fb098d91000 r-xp  08:01 3018860
/lib/x86_64-linux-gnu/ld-2.23.so
7fb098f69000-7fb098f6d000 rw-p  00:00 0 
7fb098f8f000-7fb098f9 rw-p  00:00 0 
7fb098f9-7fb098f91000 r--p 00025000 08:01 3018860
/lib/x86_64-linux-gnu/ld-2.23.so
7fb098f91000-7fb098f92000 rw-p 00026000 08:01 3018860
/lib/x86_64-linux-gnu/ld-2.23.so
7fb098f92000-7fb098f93000 rw-p  00:00 0 

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Chandan Koppula]

Is it fixed or not?

If fixed, where is the update patch?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1563110

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1782326] [NEW] Please remove qtpim from Ubuntu

[Simon Quigley]

Public bug reported:

qtpim-opensource-src is an Ubuntu-only package that has never had an
upstream release and has no reverse dependencies:

$ reverse-depends src:qtpim-opensource-src
No reverse dependencies found
$ reverse-depends -b src:qtpim-opensource-src
No reverse dependencies found

Please remove it from Ubuntu.

** Affects: qtpim-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtpim-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1782326

Title:
  Please remove qtpim from Ubuntu

Status in qtpim-opensource-src package in Ubuntu:
  New

Bug description:
  qtpim-opensource-src is an Ubuntu-only package that has never had an
  upstream release and has no reverse dependencies:

  $ reverse-depends src:qtpim-opensource-src
  No reverse dependencies found
  $ reverse-depends -b src:qtpim-opensource-src
  No reverse dependencies found

  Please remove it from Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtpim-opensource-src/+bug/1782326/+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 1737441] Re: python-apt crashes if objects of one cache are passed to depcache belonging to another cache

[Launchpad Bug Tracker]

This bug was fixed in the package python-apt -
1.1.0~beta1ubuntu0.16.04.2

---
python-apt (1.1.0~beta1ubuntu0.16.04.2) xenial; urgency=medium

  * python/tag.cc: Fix invalid read in TagFileNext
  * DepCache: Check that candidate we are setting belongs to package
  * Raise CacheMismatchError if objects passed to DepCache are from different 
cache
(LP: #1737441); also includes the following regression fixes from bionic:
- apt.Cache: Remap objects when reopening cache (LP: 1773316 in bionic+), 
incl. regression fixes:
  + Add more extensive test cases for cache remapping
  + Regression fix: Do not override __hash__ in apt.package.Package (LP: 
1780099 in bionic+)
  * CI / pre-build / data changes:
- Replace broken travis CI integration with current docker-based one
- utils/get_debian_mirrors.py: Get data from salsa (for pre-build hook)
- debian/control: Point to salsa instead of anonscm
- debian/gbp.conf: Point to 1.1.y-xenial branch
- Updated mirror list

 -- Julian Andres Klode   Tue, 10 Jul 2018 12:47:50
+0200

** Changed in: python-apt (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1737441

Title:
  python-apt crashes if objects of one cache are passed to depcache
  belonging to another cache

Status in python-apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in python-apt source package in Trusty:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in python-apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Won't Fix
Status in python-apt source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

  APT relies on the ID of the package (it's position in the cache) for
  it's operation. So if a package has ID 0 in the old cache, and a
  different package has ID 0 in the new cache, performing operations on
  the old package would perform it on the new package. If the old
  package's ID is out of bounds in the new cache, the behavior is
  undefined - it's an out of bounds array access.

  [Test case]
  The attached test case has a list of packages 0-9, a-z; stores the package 
"z" into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.

  More test cases like this are in the autopkgtest.

  [Regression potential]
  The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.

  [Other info]
  The xenial SRU also includes the change "python/tag.cc: Fix invalid read in 
TagFileNext". We don't have any specific verification for it, as we just saw 
weird crashes on the error tracker, and this seemed like the culprit. We 
released bionic with it, and it seems fine.  The fix is fairly obvious: We were 
copying the char array "Start" which was not nul terminated in an odd way, 
without using the lenght.

  [Original bug report]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1737441/+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 1737441] Update Released

[Robie Basak]

The verification of the Stable Release Update for python-apt has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1737441

Title:
  python-apt crashes if objects of one cache are passed to depcache
  belonging to another cache

Status in python-apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in python-apt source package in Trusty:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in python-apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Won't Fix
Status in python-apt source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

  APT relies on the ID of the package (it's position in the cache) for
  it's operation. So if a package has ID 0 in the old cache, and a
  different package has ID 0 in the new cache, performing operations on
  the old package would perform it on the new package. If the old
  package's ID is out of bounds in the new cache, the behavior is
  undefined - it's an out of bounds array access.

  [Test case]
  The attached test case has a list of packages 0-9, a-z; stores the package 
"z" into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.

  More test cases like this are in the autopkgtest.

  [Regression potential]
  The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.

  [Other info]
  The xenial SRU also includes the change "python/tag.cc: Fix invalid read in 
TagFileNext". We don't have any specific verification for it, as we just saw 
weird crashes on the error tracker, and this seemed like the culprit. We 
released bionic with it, and it seems fine.  The fix is fairly obvious: We were 
copying the char array "Start" which was not nul terminated in an odd way, 
without using the lenght.

  [Original bug report]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1737441/+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 1737441] Re: python-apt crashes if objects of one cache are passed to depcache belonging to another cache

[Launchpad Bug Tracker]

This bug was fixed in the package python-apt - 0.9.3.5ubuntu3

---
python-apt (0.9.3.5ubuntu3) trusty-proposed; urgency=medium

  * DepCache: Check that candidate we are setting belongs to package
  * Raise CacheMismatchError if objects passed to DepCache are from different 
cache
(LP: #1737441); also includes the following regression fixes from bionic:
- apt.Cache: Remap objects when reopening cache (LP: 1773316 in bionic+), 
incl. regression fixes:
  + Add more extensive test cases for cache remapping
  + Regression fix: Do not override __hash__ in apt.package.Package (LP: 
1780099 in bionic+)
  * CI / pre-build / data changes:
- Replace broken travis CI integration with current docker-based one
- utils/get_debian_mirrors.py: Get data from salsa (for pre-build hook)
- debian/control: Point to salsa instead of anonscm
- debian/gbp.conf: Point to ubuntu/trusty branch
- Updated mirror list

 -- Julian Andres Klode   Tue, 10 Jul 2018 16:59:07
+0200

** Changed in: python-apt (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1737441

Title:
  python-apt crashes if objects of one cache are passed to depcache
  belonging to another cache

Status in python-apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in python-apt source package in Trusty:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in python-apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Won't Fix
Status in python-apt source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Some applications, like unattended-upgrades or update-manager, reopen the apt 
cache. They also keep around old apt.Package objects however, and operate on 
them after reopening. Under the hood, this means that apt_pkg.Package objects 
belonging to an old cache are passed to a new cache.

  APT relies on the ID of the package (it's position in the cache) for
  it's operation. So if a package has ID 0 in the old cache, and a
  different package has ID 0 in the new cache, performing operations on
  the old package would perform it on the new package. If the old
  package's ID is out of bounds in the new cache, the behavior is
  undefined - it's an out of bounds array access.

  [Test case]
  The attached test case has a list of packages 0-9, a-z; stores the package 
"z" into a variable, then reopens the cache. It then marks z for deletion. This 
either segfaults or does nothing; when it should mark z for deletion.

  More test cases like this are in the autopkgtest.

  [Regression potential]
  The initial fix introduced bug 1780099, there might be similar bugs lurking. 
However, these bugs would have been undefined behavior before and might have 
caused segmentation faults or did the wrong thing. It seems likely that any 
regression cannot possibly be worse than the current state.

  [Other info]
  The xenial SRU also includes the change "python/tag.cc: Fix invalid read in 
TagFileNext". We don't have any specific verification for it, as we just saw 
weird crashes on the error tracker, and this seemed like the culprit. We 
released bionic with it, and it seems fine.  The fix is fairly obvious: We were 
copying the char array "Start" which was not nul terminated in an odd way, 
without using the lenght.

  [Original bug report]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
0.98ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1737441/+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 1782326] Re: Please remove qtpim from Ubuntu

[Andy Whitcroft]

Removing packages from cosmic:  

 
qtpim-opensource-src 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 

 
libqt5contacts5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
amd64   
  
libqt5contacts5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
arm64   
  
libqt5contacts5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
armhf   
  
libqt5contacts5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
i386
  
libqt5contacts5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
ppc64el
libqt5contacts5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
s390x
libqt5organizer5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
amd64
libqt5organizer5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
arm64
libqt5organizer5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
armhf
libqt5organizer5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
i386
libqt5organizer5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
ppc64el
libqt5organizer5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
s390x
libqt5versit5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
amd64
libqt5versit5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
arm64
libqt5versit5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
armhf
libqt5versit5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
i386
libqt5versit5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
ppc64el
libqt5versit5 5.0~git20140515~29475884-0ubuntu24~7 in cosmic 
s390x
libqt5versitorganizer5 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic amd64
libqt5versitorganizer5 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic arm64
libqt5versitorganizer5 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic armhf
libqt5versitorganizer5 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic i386
libqt5versitorganizer5 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic ppc64el
libqt5versitorganizer5 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic s390x
qml-module-qtcontacts 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic amd64
qml-module-qtcontacts 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic arm64
qml-module-qtcontacts 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic armhf
qml-module-qtcontacts 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic i386
qml-module-qtcontacts 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic ppc64el
qml-module-qtcontacts 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic s390x
qml-module-qtorganizer 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic amd64
qml-module-qtorganizer 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic arm64
   qml-module-qtorganizer 
5.0~git20140515~29475884-0ubuntu24~7 in cosmic armhf
qml-module-qtorganizer 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic i386 
  
qml-module-qtorganizer 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic ppc64el
qml-module-qtorganizer 5.0~git20140515~29475884-0ubuntu24~7 in 
cosmic s390x
qtdeclarative5-qtcontacts-plugin 
5.0~git20140515~29475884-0ubuntu24~7 in cosmic amd64
qtdeclarative5-qtcontacts-plugin 
5.0~git20140515~29475884-0ubuntu24~7 in cosmic arm64
qtdeclarative5-qtcontacts-plugin 
5.0~git20140515~29475884-0ubuntu24~7 in cosmic armhf
qtdeclarative5-qtcontacts-plugin 
5.0~git20140515~29475884-0ubuntu24~7 in cosmic i386
qtdeclarative5-qtcontacts-plugin 
5.0~git20140515~29475884-0ubuntu24~7 in cosmic ppc64el
qtdeclarative5-qtcontacts-plugin 
5.0~git20140515~29475884-0ubuntu24~7 in cosmic s390x
qtdeclarative5-qtorganizer-plugin 
5.0~git20140515~29475884-0ubuntu24~7 in cosmic amd64
qtdeclarative5-qtorganizer-plugin 

[Touch-packages] [Bug 1782326] Re: Please remove qtpim from Ubuntu

[Andy Whitcroft]

Though all of that is true, that does not mean it is unused.  So it
likely makes more sense to demote it to -proposed in the interim.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtpim-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1782326

Title:
  Please remove qtpim from Ubuntu

Status in qtpim-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  qtpim-opensource-src is an Ubuntu-only package that has never had an
  upstream release and has no reverse dependencies:

  $ reverse-depends src:qtpim-opensource-src
  No reverse dependencies found
  $ reverse-depends -b src:qtpim-opensource-src
  No reverse dependencies found

  Please remove it from Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtpim-opensource-src/+bug/1782326/+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 1760106] Re: FFe: Enable configuring resume offset via sysfs

[Dimitri John Ledkov]

This patch set is still present, and is operating as expected in
237-3ubuntu10.2

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  FFe: Enable configuring resume offset via sysfs

Status in OEM Priority Project:
  Triaged
Status in klibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Committed
Status in klibc source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in klibc source package in Cosmic:
  New
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1760106/+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 1762385] Re: dell_wmi: Unknown key codes

[Dimitri John Ledkov]

This patch set is still present, and is operating as expected in
237-3ubuntu10.2

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1762385

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1771791] Re: Need to pre-depend on stuff used by systemctl, so systemctl works in other package's preinst

[Dimitri John Ledkov]

Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>=
2.27), libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>=
1.8.0), libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117),
liblz4-1 (>= 0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2
(>= 2.3.1), libselinux1 (>= 2.1.9)

This is in 237-3ubuntu10.2 thus still correctly listing the new ABIs of
all the libsystemd0 libraries.

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1771791

Title:
  Need to pre-depend on stuff used by systemctl, so systemctl works in
  other package's preinst

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  systemd used to pre-depend on the libraries used by systemctl or something, 
but now systemctl uses libsystemd-shared, and there are no pre-depends for 
that, meaning that systemctl fails in maintainer scripts of other packages.

  [Test case]
  Grab the apt-clone file from comment #20 in bug 1766890, and upgrade it to 
bionic with apt dist-upgrade -o APT::Immediate-Configure=0. Make sure to not 
see error about missing libraries in systemctl.

  [Regression potential]
  Installation ordering changes. Might make things harder for apt to solve.

  [Other info]
  Debian 897986

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771791/+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