date:20180412

This bug was fixed in the package budgie-artwork - 0.8.3ubuntu1

---
budgie-artwork (0.8.3ubuntu1) artful; urgency=medium

  * Bug fix release
- Make the lsb-release triggers interest-noawait, so that we don't block
  configuration of an Essential: yes package during upgrades
  (LP: #1750465)

 -- David Mohammed   Fri, 30 Mar 2018 11:57:04
+0100

** Changed in: budgie-artwork (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  upgrade attempting to process triggers out of order (package plymouth-
  theme-ubuntu-text 0.9.2-3ubuntu17 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed)

Status in apt package in Ubuntu:
  Confirmed
Status in budgie-artwork package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in ubuntu-gnome-default-settings package in Ubuntu:
  Fix Released
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in kubuntu-settings source package in Xenial:
  Confirmed
Status in plymouth source package in Xenial:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Xenial:
  Confirmed
Status in ubuntu-mate-artwork source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Confirmed
Status in budgie-artwork source package in Artful:
  Fix Released
Status in kubuntu-settings source package in Artful:
  Confirmed
Status in plymouth source package in Artful:
  Fix Released
Status in ubuntu-gnome-default-settings source package in Artful:
  Confirmed
Status in ubuntu-mate-artwork source package in Artful:
  Confirmed

Bug description:
  [SRU Justification]
  A package manager bug can cause dist-upgrades from 17.10 to 18.04 to fail 
because of trying to process triggers out of order.  Since the trigger being 
run is that of the currently-installed plymouth package, it is not guaranteed 
to be sufficient to fix the version of the package in 18.04.

  [Test case]
  1. Install plymouth-themes-ubuntu-text from -proposed.
  2. Run a release upgrade with each of update-manager -d, do-release-upgrade 
-d, and apt-get dist-upgrade (the last after manually changing sources.list).
  3. Verify that in each case, the upgrade completes successfully, with no 
errors about out-of-order trigger configuration.

  [Regression potential]
  noawait triggers have been supported in dpkg since 1.16.1, which is older 
than the version in precise 
(https://manpages.debian.org/jessie/dpkg-dev/deb-triggers.5.en.html).  A 
noawait trigger is considered appropriate whenever the triggered package does 
not need to block the triggering package.  There is no reason for a plymouth 
theme package to need to block configuration of an essential package in this 
case.  noawait triggers are well-exercised in the distro now, so the risk of 
regression from this change should be low.

  There is unfortunately not a known reproducer for the original bug, so
  the test case, while it should guard against regressions, is not
  strong confirmation that the bug is fixed.

  [Original description]
  Failure during upgrade attempt from Xubuntu 17.10 to Xubuntu 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: plymouth-theme-ubuntu-text 0.9.2-3ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Feb 18 23:41:49 2018
  DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-24 (118 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp.
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 1bcf:2c01 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5567
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=d2256612-d86a-469b-be01-94e1fdcca333 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.5.1
  SourcePackage: plymouth
  TextPlym

[Touch-packages] [Bug 1738581] Update Released

The verification of the Stable Release Update for apport 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1738581

Title:
  apport attachment JounralErrors should only be included for crash
  reports which are private

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Artful:
  Fix Released

Bug description:
  [Impact]
  apport includes an attachment called JournalErrors which includes warnings 
and errors in journalctl output. This can in rare circumstances include private 
information.

  [Test Case]
  1) Run ubuntu-bug apport
  2) Observe JournalErrors attachment in the .crash file

  With the version of apport from -proposed JournalErrors will only be
  included in crash reports not regular bug reports. So follow the same
  test case and ensure JournalErrors is not included then run:

  1) d-feet
  2) pkill -11 d-feet
  3) Observe JournalErrors in the d-feet .crash file

  [Regression Potential]
  Its possible my code is bad and then apport would crash when collecting 
journal errors. However, apport will just carry on and not include that 
attachment which would still be an improvement as there wouldn't be any private 
information included.

  See the bug report 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
  created with ubuntu-bug.

  Original Description
  

  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting 
MPD_HOST=...@.xxx.org

  Normally it would be not problem that gdm-x-session write this to the
  journal, because the journal is not intended to be published on the
  internet.

  Setting confidential informations via environment is maybe not the
  best idea, but a legal procedure and for `mpc` the only way to set
  this information.

  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.

  Note: I manually delete the attachment in the mentioned bug report.
  But how can I sure that a web crawlser hasn't read/preserved that
  attachment?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738581/+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 1738581] Re: apport attachment JounralErrors should only be included for crash reports which are private

This bug was fixed in the package apport - 2.20.7-0ubuntu3.8

---
apport (2.20.7-0ubuntu3.8) artful; urgency=medium

  * data/general-hooks/generic.py: Only include JournalErrors for apport-crash
reports which are private by default. (LP: #1738581)

 -- Brian Murray   Fri, 30 Mar 2018 09:43:05 -0700

** Changed in: apport (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  apport attachment JounralErrors should only be included for crash
  reports which are private

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Artful:
  Fix Released

Bug description:
  [Impact]
  apport includes an attachment called JournalErrors which includes warnings 
and errors in journalctl output. This can in rare circumstances include private 
information.

  [Test Case]
  1) Run ubuntu-bug apport
  2) Observe JournalErrors attachment in the .crash file

  With the version of apport from -proposed JournalErrors will only be
  included in crash reports not regular bug reports. So follow the same
  test case and ensure JournalErrors is not included then run:

  1) d-feet
  2) pkill -11 d-feet
  3) Observe JournalErrors in the d-feet .crash file

  [Regression Potential]
  Its possible my code is bad and then apport would crash when collecting 
journal errors. However, apport will just carry on and not include that 
attachment which would still be an improvement as there wouldn't be any private 
information included.

  See the bug report 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
  created with ubuntu-bug.

  Original Description
  

  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting 
MPD_HOST=...@.xxx.org

  Normally it would be not problem that gdm-x-session write this to the
  journal, because the journal is not intended to be published on the
  internet.

  Setting confidential informations via environment is maybe not the
  best idea, but a legal procedure and for `mpc` the only way to set
  this information.

  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.

  Note: I manually delete the attachment in the mentioned bug report.
  But how can I sure that a web crawlser hasn't read/preserved that
  attachment?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738581/+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: /usr/bin/unattended-upgrade:11:GI_libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

This is a problem in unattended-upgrades reusing apt.Version objects
after reopening the cache.

python-apt does not verify that objects like versions passed to
apt_pkg.DepCache belong to the same cache. Hence we get out of bounds
writes and memory corruption if these reference cache objects with IDs
outside of the cache range (like dependency 1024 in a cache with 100
dependencies), or, maybe even worse, we mark the wrong things (like set
the candidate for an entirely different package). Hence this was not
detected. I added checks to python-apt now to detect this situation
where possible, and will release that shortly.


** Changed in: unattended-upgrades (Ubuntu Bionic)
   Status: Invalid => Triaged

-- 
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:
  /usr/bin/unattended-
  
upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

Status in python-apt package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  Triaged
Status in python-apt source package in Bionic:
  In Progress
Status in unattended-upgrades source package in Bionic:
  Triaged

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 
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 1738581] Re: apport attachment JounralErrors should only be included for crash reports which are private

This bug was fixed in the package apport - 2.20.1-0ubuntu2.16

---
apport (2.20.1-0ubuntu2.16) xenial; urgency=medium

  * data/general-hooks/generic.py: Only include JournalErrors for apport-crash
reports which are private by default. (LP: #1738581)

 -- Brian Murray   Fri, 30 Mar 2018 09:53:05 -0700

** Changed in: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1738581

Title:
  apport attachment JounralErrors should only be included for crash
  reports which are private

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Artful:
  Fix Released

Bug description:
  [Impact]
  apport includes an attachment called JournalErrors which includes warnings 
and errors in journalctl output. This can in rare circumstances include private 
information.

  [Test Case]
  1) Run ubuntu-bug apport
  2) Observe JournalErrors attachment in the .crash file

  With the version of apport from -proposed JournalErrors will only be
  included in crash reports not regular bug reports. So follow the same
  test case and ensure JournalErrors is not included then run:

  1) d-feet
  2) pkill -11 d-feet
  3) Observe JournalErrors in the d-feet .crash file

  [Regression Potential]
  Its possible my code is bad and then apport would crash when collecting 
journal errors. However, apport will just carry on and not include that 
attachment which would still be an improvement as there wouldn't be any private 
information included.

  See the bug report 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
  created with ubuntu-bug.

  Original Description
  

  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting 
MPD_HOST=...@.xxx.org

  Normally it would be not problem that gdm-x-session write this to the
  journal, because the journal is not intended to be published on the
  internet.

  Setting confidential informations via environment is maybe not the
  best idea, but a legal procedure and for `mpc` the only way to set
  this information.

  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.

  Note: I manually delete the attachment in the mentioned bug report.
  But how can I sure that a web crawlser hasn't read/preserved that
  attachment?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738581/+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: /usr/bin/unattended-upgrade:11:GI_libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

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

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

-- 
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:
  /usr/bin/unattended-
  
upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

Status in python-apt package in Ubuntu:
  Fix Committed
Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in python-apt source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  In Progress

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 
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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

I will be accepting this upload, but for future reference: in the
regression potential field please also include an assessment where
possible regressions can appear. This should be mostly hypothetical, but
think of this section as a hint for testers who'd like to know what to
test to see if anything isn't broken. Also, this section should give us,
the SRU team, a good understanding of how badly broken other things can
get in the worst-case scenario if this upload gets approved. Usually
this involves looking at the patch and checking which other use-cases it
can effect and, in some bizarre circumstance, break those by accident.

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: Confirmed => 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1750947

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1750947] Please test proposed package

Hello Hui, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.9 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, without details of
your testing we will not be able to proceed.

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

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1762807] Re: gnome-session-bin installed on Ubuntu MATE

This bug was fixed in the package software-properties - 0.96.24.28

---
software-properties (0.96.24.28) bionic; urgency=medium

  [ Martin Wimpress ]
  * Allow mate-session-manager to fulfill the gnome-session-bin Recommends
(LP: #1762807)

  [ Jeremy Bicha ]
  * Add Appstream metadata with compulsory_for_desktop fields to prevent
the accidental uninstallation of ubuntu-desktop in GNOME Software.
ubuntu-desktop depends on software-properties-gtk.
  * Build-Depend on dh-python

 -- Jeremy Bicha   Tue, 10 Apr 2018 17:12:59 -0400

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-session-bin installed on Ubuntu MATE

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu MATE seeds software-properties-gtk which causes gnome-session-
  bin to be pulled into the Ubuntu MATE image. This issue arises because
  debian/control doesn't Recommends: mate-session-manager for software-
  properties-gtk.

  To resolve this issue debian/control for software-properties-gtk
  should be updated to:

  Recommends: gnome-session-bin | xfce4-session | lubuntu-default-
  settings | lxqt-session | mate-session-manager, gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1762807/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

Hello Guilherme, or anyone else affected,

Accepted systemd into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.28 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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

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

** Tags added: verification-needed verification-needed-trusty

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Below the SRU request form. Please refer to the Original Description
  to a more comprehensive explanation of the problem observed.

  
  [Impact] 

   * systemd-logind tool is leaking memory at each session connected. The 
   issues happens in systemd from Trusty (14.04) only.

   * Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not 
  feeed after they're closed. In order to fix that, we proactively add 
  the sessions to systemd garbage collector (gc) when they are closed. 
  Also, part of the fix is to make cgmanager package a dependency. Refer 
  to comment #1 to a more thorough explanation of the issue and the fix.

- a small memory leak was observed in the session creation logic of 
  systemd-logind. The fix for that is the addition of an appropriate 
  free() call. Refer to comment #2 to more details on the issue and fix.

- another small memory leak was observed in the cgmanager glue code of 
  systemd-logind - this code is only present in this specific Ubuntu 
  release of the package, due to necessary compatibility layer with 
  upstart init system. The fix is to properly call free() in 2 
  functions. Refer to comment #3 to a deep exposition of the issue and 
  the fix.

  
  [Test Case]

   * The basic test-case is to run the following loop from a remote machine:
 while true; do ssh  "whoami"; done

   * It's possible to watch the increase in memory consumption from 
 "systemd-logind" process in the target machine. One can use the
 "ps uax" command to verify the RSS of the process, or count its 
 anonymous pages from /proc//smaps.

  
  [Regression Potential] 

   * Since the fixes are small and not intrusive, the potential for 
 regressions are low. More regression considerations on comments #1, #2 
 and #3 for each fix.

   * A potential small regressson is performance-wise, since now we add 
 sessions to garbage collector proactively.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1332440] Re: apt-get update very slow when ulimit -n is big

** Description changed:

  [Impact]
  apt is slow at spawning subprocesses, as it calls fcntl() on each file 
descriptor, causing significant slowdown. On my container:
  
  0.71user 1.26system 0:01.98elapsed 99%CPU (0avgtext+0avgdata
  34164maxresident)k
  
  0.14user 0.05system 0:00.20elapsed 99%CPU (0avgtext+0avgdata
  34428maxresident)k
  
  - a 10 times difference.
  
  [Test case]
  (1) Run strace -f -c apt-cache search test >/dev/null, count getrlimit() and 
fcntl() calls
  (2) Upgrade libapt-pkg4.12 to proposed
  (3) Run (1) again, make sure it's significantly lower.
+ 
+ 
+ [Regression potential]
+ Isolated fix in closing "unwanted" file descriptors. Has been in use for 
years now, but if there were a regression it would probably be an fd leak.
  
  [Original bug report]
  I use strace to see why apt-get update is too slow,
  finally I found apt-get loop 3~n to '(? , F_SETFD, FD_CLOEXEC) = 0'
  
  ubuntu 14.04
  
  root@dev2:/tmp/apt-1.0.1ubuntu2.1# apt-cache show apt
  Package: apt
  Priority: important
  Section: admin
  Installed-Size: 3576
  Maintainer: Ubuntu Developers 
  Original-Maintainer: APT Development Team 
  Architecture: amd64
  Version: 1.0.1ubuntu2.1
  Replaces: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), 
openjdk-6-jdk (<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 
0)
  Depends: libapt-pkg4.12 (>= 0.9.16), libc6 (>= 2.15), libgcc1 (>= 1:4.1.1), 
libstdc++6 (>= 4.6), ubuntu-keyring, gnupg
  Suggests: aptitude | synaptic | wajig, dpkg-dev (>= 1.17.2), apt-doc, 
python-apt
  Conflicts: python-apt (<< 0.7.93.2~)
  Breaks: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), openjdk-6-jdk 
(<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 0)
  Filename: pool/main/a/apt/apt_1.0.1ubuntu2.1_amd64.deb
  Size: 952374
  
  [pid 20525] 
stat("/var/lib/apt/lists/mirrors.163.com_ubuntu_dists_trusty-updates_universe_i18n_Translation-en%5fUS",
 0x7fffaabe5b30) = -1 ENOENT (No such file or directory)
  [pid 20525] stat("/usr/lib/apt/methods/bzip2", {st_mode=S_IFREG|0755, 
st_size=23056, ...}) = 0
  [pid 20525] pipe([9, 11])   = 0
  [pid 20525] pipe([13, 14])  = 0
  [pid 20525] fcntl(9, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(11, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(13, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(14, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] clone(child_stack=0, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0x7f99f1ea9a50) = 20538
  Process 20538 attached
  [pid 20525] fcntl(9, F_GETFL)   = 0 (flags O_RDONLY)
  [pid 20525] fcntl(9, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
  [pid 20538] rt_sigaction(SIGPIPE, {SIG_DFL, [PIPE], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_GETFL 
  [pid 20538] <... rt_sigaction resumed> {SIG_IGN, [PIPE], 
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0x1 (flags O_WRONLY)
  [pid 20538] rt_sigaction(SIGQUIT, {SIG_DFL, [QUIT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_SETFL, O_WRONLY|O_NONBLOCK 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0
  [pid 20538] rt_sigaction(SIGINT, {SIG_DFL, [INT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] close(11 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... close resumed> )   = 0
  [pid 20538] rt_sigaction(SIGWINCH, {SIG_DFL, [WINCH], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] close(13 
  [pid 20538] <... rt_sigaction resumed> {0x409140, [WINCH], 
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
  [pid 20525] <... close resumed> )   = 0
  [pid 20538] rt_sigaction(SIGCONT, {SIG_DFL, [CONT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] select(10, [9], NULL, NULL, NULL 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20538] rt_sigaction(SIGTSTP, {SIG_DFL, [TSTP], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0}, {SIG_DFL, [], 0}, 8) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(3, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(4, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(5, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(6, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(7, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(8, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(9, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538

[Touch-packages] [Bug 1332440] Re: apt-get update very slow when ulimit -n is big

Hello tom916, or anyone else affected,

Accepted apt into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.18 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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: apt (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-trusty

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

Title:
  apt-get update very slow when ulimit -n is big

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  apt is slow at spawning subprocesses, as it calls fcntl() on each file 
descriptor, causing significant slowdown. On my container:

  0.71user 1.26system 0:01.98elapsed 99%CPU (0avgtext+0avgdata
  34164maxresident)k

  0.14user 0.05system 0:00.20elapsed 99%CPU (0avgtext+0avgdata
  34428maxresident)k

  - a 10 times difference.

  [Test case]
  (1) Run strace -f -c apt-cache search test >/dev/null, count getrlimit() and 
fcntl() calls
  (2) Upgrade libapt-pkg4.12 to proposed
  (3) Run (1) again, make sure it's significantly lower.

  
  [Regression potential]
  Isolated fix in closing "unwanted" file descriptors. Has been in use for 
years now, but if there were a regression it would probably be an fd leak.

  [Original bug report]
  I use strace to see why apt-get update is too slow,
  finally I found apt-get loop 3~n to '(? , F_SETFD, FD_CLOEXEC) = 0'

  ubuntu 14.04

  root@dev2:/tmp/apt-1.0.1ubuntu2.1# apt-cache show apt
  Package: apt
  Priority: important
  Section: admin
  Installed-Size: 3576
  Maintainer: Ubuntu Developers 
  Original-Maintainer: APT Development Team 
  Architecture: amd64
  Version: 1.0.1ubuntu2.1
  Replaces: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), 
openjdk-6-jdk (<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 
0)
  Depends: libapt-pkg4.12 (>= 0.9.16), libc6 (>= 2.15), libgcc1 (>= 1:4.1.1), 
libstdc++6 (>= 4.6), ubuntu-keyring, gnupg
  Suggests: aptitude | synaptic | wajig, dpkg-dev (>= 1.17.2), apt-doc, 
python-apt
  Conflicts: python-apt (<< 0.7.93.2~)
  Breaks: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), openjdk-6-jdk 
(<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 0)
  Filename: pool/main/a/apt/apt_1.0.1ubuntu2.1_amd64.deb
  Size: 952374

  [pid 20525] 
stat("/var/lib/apt/lists/mirrors.163.com_ubuntu_dists_trusty-updates_universe_i18n_Translation-en%5fUS",
 0x7fffaabe5b30) = -1 ENOENT (No such file or directory)
  [pid 20525] stat("/usr/lib/apt/methods/bzip2", {st_mode=S_IFREG|0755, 
st_size=23056, ...}) = 0
  [pid 20525] pipe([9, 11])   = 0
  [pid 20525] pipe([13, 14])  = 0
  [pid 20525] fcntl(9, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(11, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(13, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(14, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] clone(child_stack=0, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0x7f99f1ea9a50) = 20538
  Process 20538 attached
  [pid 20525] fcntl(9, F_GETFL)   = 0 (flags O_RDONLY)
  [pid 20525] fcntl(9, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
  [pid 20538] rt_sigaction(SIGPIPE, {SIG_DFL, [PIPE], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_GETFL 
  [pid 20538] <... rt_sigaction resumed> {SIG_IGN, [PIPE], 
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0x1 (flags O_WRONLY)
  [pid 20538] rt_sigaction(SIGQUIT, {SIG_DFL, [QUIT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_SETFL, O_WRONLY|O_NONBLOCK 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0
  [pid 20538] rt_sigaction(SIGINT, {SIG_DFL, [INT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] close(11 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... close resumed> )   = 0
  [pid 20538] rt_sigaction(SIGWINCH, {SIG_DFL, [WINCH], SA_RESTORER|SA_REST

[Touch-packages] [Bug 1164016] Re: restore type-ahead find

2018-04-12 Thread Maxim Berman

Very often files many subfolders contain files with the same name as in
the folder you are browsing. Example: Makefiles, .git folders, etc. With
recursive search these files all show up without a clear way to
distinguish them. :(

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1747411] Re: Change of default database file format to SQL

2018-04-12 Thread Timo Aaltonen

dogtag-pki 10.6.0~beta2 landed in bionic

** Changed in: dogtag-pki (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Change of default database file format to SQL

Status in certmonger package in Ubuntu:
  Fix Released
Status in corosync package in Ubuntu:
  New
Status in dogtag-pki package in Ubuntu:
  Fix Released
Status in freeipa package in Ubuntu:
  New
Status in libapache2-mod-nss package in Ubuntu:
  New
Status in nss package in Ubuntu:
  New

Bug description:
  nss in version 3.35 in upstream changed [2] the default file format [1] (if 
no explicit one is specified).
  For now we reverted that change in bug 1746947 until all packages depending 
on it are ready to work with that correctly.

  This bug here is about to track when the revert can be dropped.
  Therefore we list all known-to-be-affected packages and once all are resolved 
this can be dropped.

  [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
  [2]: 
https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/certmonger/+bug/1747411/+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 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

Progress! I think...
https://bugzilla.gnome.org/show_bug.cgi?id=795195

** Also affects: gstreamer-vaapi (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: GNOME Bug Tracker #795195
   https://bugzilla.gnome.org/show_bug.cgi?id=795195

** Also affects: gstreamer via
   https://bugzilla.gnome.org/show_bug.cgi?id=795195
   Importance: Unknown
   Status: Unknown

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GStreamer:
  Unknown
Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1698270/+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 1763108] Re: xenial2bionic release upgrade loses DNS: empty resolv.conf

2018-04-12 Thread Dimitri John Ledkov

** Package changed: systemd (Ubuntu) => resolvconf (Ubuntu)

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

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

Title:
  xenial2bionic release upgrade loses DNS: empty resolv.conf

Status in resolvconf package in Ubuntu:
  Fix Committed

Bug description:
  Note: I'm not sure which package better represents this bug, so I used
  systemd, because /etc/resolv.conf had no "nameserver 127.0.0.53" entry
  after the upgrade.

  
  I did a plain standard lxd deploy of xenial, using the default images. 
Upgraded it to the latest xenial packages, and then issued a release upgrade to 
bionic.

  At the end of the upgrade process, rebooted, and when the system came
  back up, /etc/resolv.conf had no nameserver entries:

  root@xenial2bionic:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  That was its whole content. Before the upgrade, in xenial, it had:
  root@xenial2bionic:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.0.100.1
  search lxd

  systemd-resolve in the system after the upgrade to bionic was working just 
fine:
  root@xenial2bionic:~# systemd-resolve --status
  Global
   DNS Servers: 10.0.100.1
    DNS Domain: lxd
    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 34 (eth0)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: no
  DNSSEC supported: no

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 11 17:31:08 2018
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=ZFS=nsnx/ROOT/ubuntu ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)
  dmi.bios.date: 11/09/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET41W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET41W(1.26):bd11/09/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1763108/+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 1762899] Re: /etc/resolv.conf empty after upgrading from 16.04 to 18.40

2018-04-12 Thread Francis Ginther

** Tags added: id-5acd885138c94c5bb1f96431

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

Title:
  /etc/resolv.conf empty after upgrading from 16.04 to 18.40

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Bionic:
  Triaged

Bug description:
  I just upgraded one of my LXC containers to 18.04 and after rebooting,
  the /etc/resolv.conf contains no nameservers. systemd-resolve,
  however, resolves fine and the --status returns the DNS server details
  as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 22:53:30 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1762899/+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 1756006] Re: FFe: Support suspend-then-hibernate

2018-04-12 Thread Jeremy Bicha

Resetting to New since the g-s-d commits have been accepted upstream.
They are the first 4 commits for 12 Apr, 2018.

https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commits/master

See also
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/13
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Incomplete => New

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

Title:
  FFe: Support suspend-then-hibernate

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2018-04-12 Thread Francis Ginther

** Tags added: id-5acd885138c94c5bb1f96431

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

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

Status in resolvconf package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  To reproduce, mask resolved:
  sudo systemctl mask systemd-resolved.service

  ...then disable network-manager for ifupdown interfaces:
  $cat /etc/NetworkManager/NetworkManager.conf  
  [main]
  plugins=ifupdown,keyfile
  dns=default
  rc-manager=resolvconf

  [ifupdown]
  managed=false

  [device]
  wifi.scan-rand-mac-address=no

  ...and reboot.

  You'll note that resolvconf integration with dhclient is now broken.
  Interfaces listed in /etc/network/interfaces or
  /etc/network/interfaces.d/* will not provide DNS configuration in
  /etc/resolv.conf and /run/resolvconf/interfaces/.

  This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines
  "make_resolv_conf()" as a valid function for the BOUND case, but
  /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty
  now, eh?) even though resolved is masked.

  The file existence check in the beginning of /etc/dhcp/dhclient-enter-
  hooks.d/resolved should be more thorough, i.e. it should ensure that
  resolved is enabled, rather than simply look for the existence of
  /lib/systemd/systemd-resolved. This works for me:

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled 
systemd-resolved ; then

  Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement
  a similar check, looking for /run/resolvconf/enable-updates as a
  condition for meddling with DNS settings. If desired, I'll file a
  separate bug for that package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+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 1332440] Re: apt-get update very slow when ulimit -n is big

Verified. (BTW, I aborted the initial run as it simply took too long so
actual numbers would have been much higher)

root@t:~# apt-cache  policy libapt-pkg4.12
libapt-pkg4.12:
  Installed: 1.0.1ubuntu2.17
  Candidate: 1.0.1ubuntu2.18
  Version table:
 1.0.1ubuntu2.18 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
 *** 1.0.1ubuntu2.17 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
100 /var/lib/dpkg/status
 1.0.1ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@t:~# strace -f -c apt-cache search test >/dev/null
Process 2338 attached
^CProcess 2337 detached
Process 2338 detached
% time seconds  usecs/call callserrors syscall
-- --- --- - - 
 50.320.827909   3329234   getrlimit
 49.550.815234   2329234329227 fcntl
  0.030.000510  1050   mmap
  0.020.000407  1040   open
  0.010.000225  1023   mprotect
  0.010.000212   634   read
  0.010.000209   540   close
  0.010.000202   729   fstat
  0.010.000167  131313 access
  0.000.44   6 8 2 stat
  0.000.27  14 2   getdents
  0.000.18   9 2   munmap
  0.000.18   6 3   brk
  0.000.16  16 1   execve
  0.000.08   8 1   pipe
  0.000.07   7 1   openat
  0.000.04   4 1 1 lseek
  0.000.04   4 1   clone
  0.000.03   3 1 1 ioctl
  0.000.03   3 1   arch_prctl
  0.000.00   0 6   rt_sigaction
-- --- --- - - 
100.001.645227658725329244 total
root@t:~# apt install libapt-pkg4.12
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libfreetype6 os-prober
Use 'apt-get autoremove' to remove them.
The following packages will be upgraded:
  libapt-pkg4.12
1 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.
Need to get 638 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libapt-pkg4.12 
amd64 1.0.1ubuntu2.18 [638 kB]
Fetched 638 kB in 0s (687 kB/s) 
(Reading database ... 25096 files and directories currently installed.)
Preparing to unpack .../libapt-pkg4.12_1.0.1ubuntu2.18_amd64.deb ...
Unpacking libapt-pkg4.12:amd64 (1.0.1ubuntu2.18) over (1.0.1ubuntu2.17) ...
Setting up libapt-pkg4.12:amd64 (1.0.1ubuntu2.18) ...
Processing triggers for libc-bin (2.19-0ubuntu6.14) ...
# strace -f -c apt-cache search test >/dev/null
Process 2389 attached
Process 2390 attached
Process 2391 attached
% time seconds  usecs/call callserrors syscall
-- --- --- - - 
 21.800.002285  10   22524 stat
 14.360.001505  6822   munmap
 13.310.001395   8   16924 open
  9.960.001044   2   644   read
  9.440.000990   6   162   close
  9.210.000966   6   154   mmap
  5.690.000597   6   103   fstat
  3.820.000401  1822   getdents
  2.410.000253   553   mprotect
  1.640.000172  57 3   wait4
  1.250.000131  1211   openat
  1.170.000123  21 6 6 statfs
  1.130.000118   255   fcntl
  1.120.000117   43231 access
  0.730.77   323   brk
  0.540.57   149 3 lseek
  0.530.56  19 3   pipe
  0.400.42   154   write
  0.350.37   167   umask
  0.310.32   4 9   dup2
  0.270.28   6 5 5 ioctl
  0.250.26   9 3   clone
  0.170.18   5 4   arch_prctl
  0.130.14   4 4   execve
  0.000.00   018   rt_sigaction
  0.000.00   0 1   msync
-- --- -

[Touch-packages] [Bug 1332440] Re: apt-get update very slow when ulimit -n is big

Time for apt-cache policy apt also decreased from 1.86 seconds to 0.04
seconds :)

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

Title:
  apt-get update very slow when ulimit -n is big

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  apt is slow at spawning subprocesses, as it calls fcntl() on each file 
descriptor, causing significant slowdown. On my container:

  0.71user 1.26system 0:01.98elapsed 99%CPU (0avgtext+0avgdata
  34164maxresident)k

  0.14user 0.05system 0:00.20elapsed 99%CPU (0avgtext+0avgdata
  34428maxresident)k

  - a 10 times difference.

  [Test case]
  (1) Run strace -f -c apt-cache search test >/dev/null, count getrlimit() and 
fcntl() calls
  (2) Upgrade libapt-pkg4.12 to proposed
  (3) Run (1) again, make sure it's significantly lower.

  
  [Regression potential]
  Isolated fix in closing "unwanted" file descriptors. Has been in use for 
years now, but if there were a regression it would probably be an fd leak.

  [Original bug report]
  I use strace to see why apt-get update is too slow,
  finally I found apt-get loop 3~n to '(? , F_SETFD, FD_CLOEXEC) = 0'

  ubuntu 14.04

  root@dev2:/tmp/apt-1.0.1ubuntu2.1# apt-cache show apt
  Package: apt
  Priority: important
  Section: admin
  Installed-Size: 3576
  Maintainer: Ubuntu Developers 
  Original-Maintainer: APT Development Team 
  Architecture: amd64
  Version: 1.0.1ubuntu2.1
  Replaces: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), 
openjdk-6-jdk (<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 
0)
  Depends: libapt-pkg4.12 (>= 0.9.16), libc6 (>= 2.15), libgcc1 (>= 1:4.1.1), 
libstdc++6 (>= 4.6), ubuntu-keyring, gnupg
  Suggests: aptitude | synaptic | wajig, dpkg-dev (>= 1.17.2), apt-doc, 
python-apt
  Conflicts: python-apt (<< 0.7.93.2~)
  Breaks: manpages-it (<< 2.80-4~), manpages-pl (<< 20060617-3~), openjdk-6-jdk 
(<< 6b24-1.11-0ubuntu1~), sun-java5-jdk (>> 0), sun-java6-jdk (>> 0)
  Filename: pool/main/a/apt/apt_1.0.1ubuntu2.1_amd64.deb
  Size: 952374

  [pid 20525] 
stat("/var/lib/apt/lists/mirrors.163.com_ubuntu_dists_trusty-updates_universe_i18n_Translation-en%5fUS",
 0x7fffaabe5b30) = -1 ENOENT (No such file or directory)
  [pid 20525] stat("/usr/lib/apt/methods/bzip2", {st_mode=S_IFREG|0755, 
st_size=23056, ...}) = 0
  [pid 20525] pipe([9, 11])   = 0
  [pid 20525] pipe([13, 14])  = 0
  [pid 20525] fcntl(9, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(11, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(13, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] fcntl(14, F_SETFD, FD_CLOEXEC) = 0
  [pid 20525] clone(child_stack=0, 
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, 
child_tidptr=0x7f99f1ea9a50) = 20538
  Process 20538 attached
  [pid 20525] fcntl(9, F_GETFL)   = 0 (flags O_RDONLY)
  [pid 20525] fcntl(9, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
  [pid 20538] rt_sigaction(SIGPIPE, {SIG_DFL, [PIPE], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_GETFL 
  [pid 20538] <... rt_sigaction resumed> {SIG_IGN, [PIPE], 
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0x1 (flags O_WRONLY)
  [pid 20538] rt_sigaction(SIGQUIT, {SIG_DFL, [QUIT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] fcntl(14, F_SETFL, O_WRONLY|O_NONBLOCK 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... fcntl resumed> )   = 0
  [pid 20538] rt_sigaction(SIGINT, {SIG_DFL, [INT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] close(11 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20525] <... close resumed> )   = 0
  [pid 20538] rt_sigaction(SIGWINCH, {SIG_DFL, [WINCH], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] close(13 
  [pid 20538] <... rt_sigaction resumed> {0x409140, [WINCH], 
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
  [pid 20525] <... close resumed> )   = 0
  [pid 20538] rt_sigaction(SIGCONT, {SIG_DFL, [CONT], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0},  
  [pid 20525] select(10, [9], NULL, NULL, NULL 
  [pid 20538] <... rt_sigaction resumed> {SIG_DFL, [], 0}, 8) = 0
  [pid 20538] rt_sigaction(SIGTSTP, {SIG_DFL, [TSTP], SA_RESTORER|SA_RESTART, 
0x7f99f0e72ff0}, {SIG_DFL, [], 0}, 8) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(3, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(4, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(5, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
  [pid 20538] fcntl(6, F_SETFD, FD_CLOEXEC) = 0
  [pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100,

[Touch-packages] [Bug 1763108] Re: xenial2bionic release upgrade loses DNS: empty resolv.conf

This bug was fixed in the package resolvconf - 1.79ubuntu10

---
resolvconf (1.79ubuntu10) bionic; urgency=medium

  * Fix race of not injecting resolved config into resolvconf on LXD
container boot. LP: #1763108

 -- Dimitri John Ledkov   Thu, 12 Apr 2018 12:46:24
+0100

** Changed in: resolvconf (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  xenial2bionic release upgrade loses DNS: empty resolv.conf

Status in resolvconf package in Ubuntu:
  Fix Released

Bug description:
  Note: I'm not sure which package better represents this bug, so I used
  systemd, because /etc/resolv.conf had no "nameserver 127.0.0.53" entry
  after the upgrade.

  
  I did a plain standard lxd deploy of xenial, using the default images. 
Upgraded it to the latest xenial packages, and then issued a release upgrade to 
bionic.

  At the end of the upgrade process, rebooted, and when the system came
  back up, /etc/resolv.conf had no nameserver entries:

  root@xenial2bionic:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  That was its whole content. Before the upgrade, in xenial, it had:
  root@xenial2bionic:~# cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.0.100.1
  search lxd

  systemd-resolve in the system after the upgrade to bionic was working just 
fine:
  root@xenial2bionic:~# systemd-resolve --status
  Global
   DNS Servers: 10.0.100.1
    DNS Domain: lxd
    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 34 (eth0)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: no
  DNSSEC supported: no

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 11 17:31:08 2018
  MachineType: LENOVO 20HRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=ZFS=nsnx/ROOT/ubuntu ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)
  dmi.bios.date: 11/09/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET41W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET41W(1.26):bd11/09/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1763108/+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 1247803] Re: dnsmasq temporarily breaks DNS resolution when starting for the first time

2018-04-12 Thread Alexander

I've had this problem on Trusty (14.04).

After installing Xenial (16.04) I cannot reproduce this issue. That's
not 100% evidence that it's gone, but looks like it might be.

Could be the move from upstart to systemd, that solved this
automatically.

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

Title:
  dnsmasq temporarily breaks DNS resolution when starting for the first
  time

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in dnsmasq package in Debian:
  New

Bug description:
  The first time that dnsmasq is started, DNS resolution is broken for a
  few seconds. You can see this on initial installation:

  root@phil-test-1:~# apt-get install dnsmasq ; dig github.com
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following NEW packages will be installed:
dnsmasq
  0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded.
  Need to get 0 B/15.1 kB of archives.
  After this operation, 111 kB of additional disk space will be used.
  Selecting previously unselected package dnsmasq.
  (Reading database ... 92556 files and directories currently installed.)
  Unpacking dnsmasq (from .../dnsmasq_2.59-4ubuntu0.1_all.deb) ...
  Processing triggers for ureadahead ...
  Setting up dnsmasq (2.59-4ubuntu0.1) ...
   * Starting DNS forwarder and DHCP server dnsmasq 

   [ OK ]

  ; <<>> DiG 9.8.1-P1 <<>> github.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 56221
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;github.com.  IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)
  ;; WHEN: Mon Nov  4 11:29:16 2013
  ;; MSG SIZE  rcvd: 28

  
  Or you can recreate the problem on an existing installation by removing 
/var/run/dnsmasq/resolv.conf:

  root@phil-test-1:~# service dnsmasq stop
   * Stopping DNS forwarder and DHCP server dnsmasq 

   [ OK ]
  root@phil-test-1:~# rm /var/run/dnsmasq/resolv.conf
  root@phil-test-1:~# service dnsmasq start; dig github.com
   * Starting DNS forwarder and DHCP server dnsmasq 

   [ OK ]

  ; <<>> DiG 9.8.1-P1 <<>> github.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 10196
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;github.com.  IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)
  ;; WHEN: Mon Nov  4 11:31:21 2013
  ;; MSG SIZE  rcvd: 28


  The REFUSED status line shows that dns resolution has failed in both
  cases. I expect that if `apt-get install dnsmasq` or `service dnsmasq
  start` has returned successfully, and resolvconf has had dnsmasq
  registered as the sole resolver for lo.dnsmasq, then dnsmasq is ready
  to respond to DNS requests. Therefore, the REFUSED response from dig
  is the opposite of what I expect to happen.

  In both cases, resolution works again after a few seconds, once
  resolvconf generates the /var/run/dnsmasq/resolv.conf file and dnsmasq
  polls for and finds it.

  Even though the window is short (syslog reports ~ 4 seconds of
  unavailability), this causes me pain because I am doing a lot of
  automated installations using puppet; immediately after installing
  dnsmasq, any other package installations or apt-get update runs fail.

  
  I believe the problem is that the init.d script assumes that 
/var/run/dnsmasq/resolv.conf is already in place, but it may not be because 
nothing has caused resolvconf to refresh itself since 
/etc/resolvconf/update.d/dnsmasq was put in place. One solution would be to get 
the init.d script to run resolvconf -u if it decided to use 
/var/run/dnsmasq/resolv.conf. I am happy to submit a patch based on this.

  This was on Ubuntu 12.04.3 LTS, using dnsmasq 2.59-4ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1247803/+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 1763417] [NEW] thin red lines around "Format" button in gnome-disk-utility

2018-04-12 Thread Jean-Baptiste Lallement

Public bug reported:

There are thin red lines around the format button of gnome-disks.
Screenshot attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180328-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 12 17:20:11 2018
InstallationDate: Installed on 2014-07-15 (1367 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

** Affects: gnome-disk-utility (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-themes (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 ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1763417

Title:
  thin red lines around "Format" button in gnome-disk-utility

Status in gnome-disk-utility package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1763417/+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 1763417] Re: thin red lines around "Format" button in gnome-disks

2018-04-12 Thread Jean-Baptiste Lallement

** Attachment added: "Selection_119.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1763417/+attachment/5112357/+files/Selection_119.png

** Also affects: gnome-disk-utility (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- thin red lines around "Format" button in gnome-disks
+ thin red lines around "Format" button in gnome-disk-utility

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

Title:
  thin red lines around "Format" button in gnome-disk-utility

Status in gnome-disk-utility package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1763417/+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 1763417] Re: thin red lines around "Format" button in gnome-disks

2018-04-12 Thread Jean-Baptiste Lallement

** Summary changed:

- thin red lines around "Format" button in gnome-disk-utility
+ thin red lines around "Format" button in gnome-disks

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

Title:
  thin red lines around "Format" button in gnome-disks

Status in gnome-disk-utility package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1763417/+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 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

2018-04-12 Thread Bug Watch Updater

** Changed in: gstreamer
   Status: Unknown => Confirmed

** Changed in: gstreamer
   Importance: Unknown => Medium

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GStreamer:
  Confirmed
Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1698270/+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 1759573] Re: vlan on top of untagged network won't start

2018-04-12 Thread Tom Verdaat

Been doing some troubleshooting and we think we've found the fix for
this issue:

The script /etc/network/if-pre-up.d/vlan contains the following section
of code starting at line 62:

if [ ! -e "/sys/class/net/$IFACE" ]; then
# Try ifup for the raw device, if it fails then bring it up directly
# this is required e.g. there is no configuration for the raw device
ifup $IF_VLAN_RAW_DEVICE || ip link set up dev $IF_VLAN_RAW_DEVICE
vconfig add $IF_VLAN_RAW_DEVICE $VLANID
fi

In this case it's trying to bring up a raw device that has already been
brought up, causing it to wait forever for the lock on the raw interface
to be released. It is however lacking a check on the status of the raw
interface, which it shouldn't have to bring up if it already exists. So
this problem goes away when we put an if-statement around that section
of the code:

if [ ! -e "/sys/class/net/$IFACE" ]; then
if ! `cat /sys/class/net/$IF_VLAN_RAW_DEVICE/operstate 2> /dev/null | grep 
-q "up"`; then
# Try ifup for the raw device, if it fails then bring it up directly
# this is required e.g. there is no configuration for the raw device
ifup $IF_VLAN_RAW_DEVICE || ip link set up dev $IF_VLAN_RAW_DEVICE
fi
vconfig add $IF_VLAN_RAW_DEVICE $VLANID
fi

It seems to work perfectly, tested on these cases:
1) a vlan on top of a single enp0sX interface without untagged network 
configuration
2) a vlan on top of a single enp0sX interface with its own untagged network 
configuration
3) a vlan on top of a bond of two enp0sX interfaces, without the bond having 
its own untagged network configuration
4) a vlan on top of a bond of two enp0sX interfaces, with the bond having its 
own untagged network configuration

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

Title:
  vlan on top of untagged network won't start

Status in ifupdown package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  New

Bug description:

  Due to an upgrade (of probably of the ifupdown or vlan package), this 
specific network configuration no longer comes up automatically:
  1) Two or more network interfaces bonded
  2) An untagged network configured on that bond
  3) A vlan on top of that untagged network

  What does come up automatically:
  1) A single (e.g. unbonded) network interface with an untagged network 
configured and a vlan on top of that network
  2) Two or more network interfaces bonded with a vlan on top of that untagged 
bond

  An exact example of the configuration that doesn't work is provided
  below. It fails to come up correctly, both during boot and manually.
  The problem seems to be a blocking dependency loop between the bond
  and the vlan.

  As recommended in
  https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/comments/13
  we added dependency ordering using ifup@.service systemd units for all
  4 interfaces, but this did not affect the behaviour in any way.

  Perhaps related to LP bug 1573272 or bug 1636708 ?

  ==
  Interface configuration
  ==

  auto eno1
  iface eno1 inet manual
 mtu 1500
 bond-master bond1
 bond-primary eno1

  auto eno2
  iface eno2 inet manual
 mtu 1500
 bond-master bond1

  auto bond1
  iface bond1 inet static
 mtu 1500
 address 10.10.10.3
 bond-miimon 100
 bond-mode active-backup
 bond-slaves none
 bond-downdelay 0
 bond-updelay 0
 dns-nameservers 10.10.10.1
 gateway 10.10.10.1
 netmask 255.255.0.0

  auto bond1.2
  iface bond1.2 inet static
 mtu 1500
 address 10.11.10.3
 netmask 255.255.0.0
 vlan-raw-device bond1

  ==
  When bringing up the bond
  ==

  # ifup bond1 &
  Waiting for a slave to join bond1 (will timeout after 60s)
  # ps afx
  (...)
  ifup bond1
   \_ /bin/sh -c /bin/run-parts --exit-on-error /etc/network/if-pre-up.d
   \_ /bin/run-parts --exit-on-error /etc/network/if-pre-up.d
   \_ /bin/sh /etc/network/if-pre-up.d/ifenslave
  (...)
  /lib/systemd/systemd-udevd
   \_ /lib/systemd/systemd-udevd
   \_ /bin/sh /lib/udev/vlan-network-interface
   \_ /bin/sh /etc/network/if-pre-up.d/vlan
   \_ ifup bond1
  (...)

  ==> After waiting 60 seconds:

  # ip link | grep -E 'eno[1|2]|bond1*'
  eno1:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
  eno2:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
  bond1:  mtu 1500 qdisc noqueue 
state DOWN mode DEFAULT group default qlen 1000
  bond1.2@bond1:  mtu 1500 qdisc noqueue 
state LOWERLAYERDOWN mode DEFAULT group default qlen 1000

  ==
  When bringing

[Touch-packages] [Bug 1763435] [NEW] dbus tests time out

2018-04-12 Thread Jeremy Bicha

Public bug reported:

The dbus tests for software-properties time out.

Because of how python-distutils-extra works, one way to disable the test
is to rename tests/test_dbus.py or move it somewhere else.

Instead, I'm just ignoring the build test failures for now. Until my
proposed 0.96.24.29, these tests were not even being run at build time.

I tried multiple things to get the build tests to work but I couldn't
figure it out.

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Status: New


** Tags: bionic

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

Title:
  dbus tests time out

Status in software-properties package in Ubuntu:
  New

Bug description:
  The dbus tests for software-properties time out.

  Because of how python-distutils-extra works, one way to disable the
  test is to rename tests/test_dbus.py or move it somewhere else.

  Instead, I'm just ignoring the build test failures for now. Until my
  proposed 0.96.24.29, these tests were not even being run at build
  time.

  I tried multiple things to get the build tests to work but I couldn't
  figure it out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763435/+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 1759573] Re: vlan on top of untagged network won't start

2018-04-12 Thread Dan Streetman

Yep, I think this is similar or the same as bug 1701023, the original
vlan-ordering-ifup-call that i had to add for bug 1573272 is sometimes
causing ifupdown locking issues, although ifupdown is supposed to do
separate locking for each device.

Anyway, I have a test fix that's similar to yours - but uses ifquery --state 
instead - at this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023

Could you give that vlan pkg a try to see if it fixes this for you?

I still need to really look at and think about the locking inter-
dependencies of this before trying to sru the patch, because the real
question here is, will the pre-up vlan script ever get called where ifup
*does* need to be run on the vlan raw-device, but the lock for that
device is already held and waiting for the caller's device to come up?

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

Title:
  vlan on top of untagged network won't start

Status in ifupdown package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  New

Bug description:

  Due to an upgrade (of probably of the ifupdown or vlan package), this 
specific network configuration no longer comes up automatically:
  1) Two or more network interfaces bonded
  2) An untagged network configured on that bond
  3) A vlan on top of that untagged network

  What does come up automatically:
  1) A single (e.g. unbonded) network interface with an untagged network 
configured and a vlan on top of that network
  2) Two or more network interfaces bonded with a vlan on top of that untagged 
bond

  An exact example of the configuration that doesn't work is provided
  below. It fails to come up correctly, both during boot and manually.
  The problem seems to be a blocking dependency loop between the bond
  and the vlan.

  As recommended in
  https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/comments/13
  we added dependency ordering using ifup@.service systemd units for all
  4 interfaces, but this did not affect the behaviour in any way.

  Perhaps related to LP bug 1573272 or bug 1636708 ?

  ==
  Interface configuration
  ==

  auto eno1
  iface eno1 inet manual
 mtu 1500
 bond-master bond1
 bond-primary eno1

  auto eno2
  iface eno2 inet manual
 mtu 1500
 bond-master bond1

  auto bond1
  iface bond1 inet static
 mtu 1500
 address 10.10.10.3
 bond-miimon 100
 bond-mode active-backup
 bond-slaves none
 bond-downdelay 0
 bond-updelay 0
 dns-nameservers 10.10.10.1
 gateway 10.10.10.1
 netmask 255.255.0.0

  auto bond1.2
  iface bond1.2 inet static
 mtu 1500
 address 10.11.10.3
 netmask 255.255.0.0
 vlan-raw-device bond1

  ==
  When bringing up the bond
  ==

  # ifup bond1 &
  Waiting for a slave to join bond1 (will timeout after 60s)
  # ps afx
  (...)
  ifup bond1
   \_ /bin/sh -c /bin/run-parts --exit-on-error /etc/network/if-pre-up.d
   \_ /bin/run-parts --exit-on-error /etc/network/if-pre-up.d
   \_ /bin/sh /etc/network/if-pre-up.d/ifenslave
  (...)
  /lib/systemd/systemd-udevd
   \_ /lib/systemd/systemd-udevd
   \_ /bin/sh /lib/udev/vlan-network-interface
   \_ /bin/sh /etc/network/if-pre-up.d/vlan
   \_ ifup bond1
  (...)

  ==> After waiting 60 seconds:

  # ip link | grep -E 'eno[1|2]|bond1*'
  eno1:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
  eno2:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
  bond1:  mtu 1500 qdisc noqueue 
state DOWN mode DEFAULT group default qlen 1000
  bond1.2@bond1:  mtu 1500 qdisc noqueue 
state LOWERLAYERDOWN mode DEFAULT group default qlen 1000

  ==
  When bringing up a slave
  ==

  # ifup eno1
  Waiting for bond master bond1 to be ready
  # ps afx
  (...)
  /lib/systemd/systemd-udevd
   \_ /lib/systemd/systemd-udevd
   \_ /bin/sh /lib/udev/vlan-network-interface
   \_ /bin/sh /etc/network/if-pre-up.d/vlan
   \_ ifup bond1
   \_ /bin/sh -c /bin/run-parts --exit-on-error 
/etc/network/if-pre-up.d
   \_ /bin/run-parts --exit-on-error 
/etc/network/if-pre-up.d
   \_ /bin/sh /etc/network/if-pre-up.d/ifenslave
   \_ /bin/sh /lib/udev/vlan-network-interface
   \_ /bin/sh /etc/network/if-pre-up.d/vlan
   \_ ifup bond1
  (...)
  # ip link | grep -E 'eno[1|2]|bond1*'
  eno1:  mtu 1500 qdisc mq master bond1 
state UP mode DEFAULT group default ql

[Touch-packages] [Bug 1763446] [NEW] LIvepatch says I need to sign in after completing Ubuntu Welcome

2018-04-12 Thread Jeremy Bicha

Public bug reported:

Test Case
=
>From a clean Ubuntu 18.04 install,

1. Install gnome-initial-setup
2. Log out then log back in.
3. Complete the Welcome to Ubuntu wizard, making sure to enable Livepatch.
4. Afterwards, run the Software & Updates app (software-properties-gtk).
5. Switch to the Updates tab.

The page says "To use Livepatch you need to sign in."

Workaround
==
Click Sign In and then click your Ubuntu One account to get Software & Updates
to correctly recognize your account.

Screenshot attached. (Sorry about the blue colors; that should be fixed
in mutter 3.28.1 available in Ubuntu 18.04 "soon".)

Other Info
==
gnome-initial-setup 3.28.0-2ubuntu3

** Affects: software-properties (Ubuntu)
Importance: Low
Assignee: Andrea Azzarone (azzar1)
Status: Triaged

** Tags: bionic

** Attachment added: "software-properties-livepatch-half-on.png"

https://bugs.launchpad.net/bugs/1763446/+attachment/5112523/+files/software-properties-livepatch-half-on.png

** Description changed:

Test Case
=
From a clean Ubuntu 18.04 install,

The page says "To use Livepatch you need to sign in."

Workaround
==
Click Sign In and then click your Ubuntu One account to get Software &
Updates to correctly recognize your account.

Screenshot attached. (Sorry about the blue colors; that should be fixed
in mutter 3.28.1 available in Ubuntu 18.04 "soon".)
+
+ Other Info
+ ==
+ gnome-initial-setup 3.28.0-2ubuntu3

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

Title:
LIvepatch says I need to sign in after completing Ubuntu Welcome

Status in software-properties package in Ubuntu:
Triaged

Bug description:
Test Case
=
From a clean Ubuntu 18.04 install,

The page says "To use Livepatch you need to sign in."

Workaround
==
Click Sign In and then click your Ubuntu One account to get Software &
Updates to correctly recognize your account.

Screenshot attached. (Sorry about the blue colors; that should be
fixed in mutter 3.28.1 available in Ubuntu 18.04 "soon".)

Other Info
==
gnome-initial-setup 3.28.0-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763446/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)

2018-04-12 Thread Guilherme G. Piccoli

Hi Łukasz, thanks for the heads-up.

I just tested systemd from -proposed, version 204-5ubuntu20.28 and it
fixes the issue reported in this LP.

The test consists in doing multiple SSHs in a loop (better explained in
the description). I've run the test with and without cgmanager
installed, in kernels 4.4.0-119 and 3.13.0-145, no memory leaks
observed.

Important to notice, I wasn't able to observe any constant increase in
CPU utilization from both binaries (logind and cgm); I kept monitoring
and didn't notice anything abnormal.

I'll mark this as verified.
Cheers,


Guilherme

** Tags removed: sts-sru-needed verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty

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

Title:
  systemd-logind: memory leaks on session's connections (trusty-only)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Below the SRU request form. Please refer to the Original Description
  to a more comprehensive explanation of the problem observed.

  
  [Impact] 

   * systemd-logind tool is leaking memory at each session connected. The 
   issues happens in systemd from Trusty (14.04) only.

   * Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not 
  feeed after they're closed. In order to fix that, we proactively add 
  the sessions to systemd garbage collector (gc) when they are closed. 
  Also, part of the fix is to make cgmanager package a dependency. Refer 
  to comment #1 to a more thorough explanation of the issue and the fix.

- a small memory leak was observed in the session creation logic of 
  systemd-logind. The fix for that is the addition of an appropriate 
  free() call. Refer to comment #2 to more details on the issue and fix.

- another small memory leak was observed in the cgmanager glue code of 
  systemd-logind - this code is only present in this specific Ubuntu 
  release of the package, due to necessary compatibility layer with 
  upstart init system. The fix is to properly call free() in 2 
  functions. Refer to comment #3 to a deep exposition of the issue and 
  the fix.

  
  [Test Case]

   * The basic test-case is to run the following loop from a remote machine:
 while true; do ssh  "whoami"; done

   * It's possible to watch the increase in memory consumption from 
 "systemd-logind" process in the target machine. One can use the
 "ps uax" command to verify the RSS of the process, or count its 
 anonymous pages from /proc//smaps.

  
  [Regression Potential] 

   * Since the fixes are small and not intrusive, the potential for 
 regressions are low. More regression considerations on comments #1, #2 
 and #3 for each fix.

   * A potential small regressson is performance-wise, since now we add 
 sessions to garbage collector proactively.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1303649] Re: systemd-logind spins in cgmanager_ping_sync()

2018-04-12 Thread Guilherme G. Piccoli

For the folks that observed the recent cgmanager issue with logind:
there's a new systemd version in -proposed; it's version
"204-5ubuntu20.28". I've just tested it with and without cgmanager, in
kernels 4.4.0-119 and 3.13.0-145 (according to LP #1750013), and didn't
observe any constant CPU utilization increase.

Important to notice this new version of systemd ("204-5ubuntu20.28")
_does not depend_ on cgmanager, so it's not mandatory to have cgmanager
installed.

Tests with the new version are welcome, with and without cgmanager. I'd
like to ask, if possible, that anyone that observes the issue again to
test with and without cgmanager, and if possible, in kernels 4.4.0 and
3.13.0, so we have a better idea of the environments reproducing the
issue.

Thanks in advance,


Guilherme

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

Title:
  systemd-logind spins in cgmanager_ping_sync()

Status in cgmanager package in Ubuntu:
  Invalid
Status in libnih package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd-logind is consuming a high level of cpu on a continual basis:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
 
676 root  20   0   43644   2144   1568 R 100.0  0.0  74:43.77 
systemd-logind

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu17
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 09:09:37 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-23 (348 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+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 1763461] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2018-04-12 Thread Antonio F. Ottoneleonard8

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

Public bug reported:

solo dispuse actualizar el sistema.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu Apr 12 14:18:46 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2018-03-13 (29 days ago)
InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  solo dispuse actualizar el sistema.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 12 14:18:46 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2018-03-13 (29 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new 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/avahi/+bug/1763461/+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 1763461] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

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 #1760128, 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 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new 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 avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1763461

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  solo dispuse actualizar el sistema.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 12 14:18:46 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2018-03-13 (29 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new 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/avahi/+bug/1763461/+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 1753532] Comment bridged from LTC Bugzilla

2018-04-12 Thread bugproxy

--- Comment From heinz-werner_se...@de.ibm.com 2018-04-12 13:23 EDT---
IBM bugzilla status -> closed ; Environment reinstalled. Therefore this problem 
will not be tracked further..

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

Title:
  apt-get update doesn't get new packages

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  apt-get update and upgrade do not upgrade the system
   
  --Steps to Reproduce---
   apt-get update and apt-get upgrade.  It shows nothing to upgrade. But the 
kernel level is in an old version. 
   
  New kernel packages are not shown in apt-cache. Somehow, the new packages are 
not being got from repo server when do apt-get update.

  Executed on 16.04.3

  Btw, not all the Ubuntu servers have that issues. I crossed check the
  sources.list among the servers, there is no difference. So don't know
  what caused some of them cannot get any update from ubuntu repo.
  However, I can install individual packages via apt-get install
  command.

  There is not any error during the apt-get update && apt-get upgrade.
  It showed nothing to upgrade.

  Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
  Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease
  Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease
  Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  The servers were able to manually upgrade for a long time. But all the
  sudden, they are not upgradable. It looks it can not retrieve new
  kernel level packages during the apt-get update. The highest kernel
  level can be installed is 4.4.0-97.. not more higher..


  HWS: I mirrored this problem description, to be able to get support
  for getting this fixed. Even it seems to be an environment problem.
  But direct Q&A will probably help

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1753532/+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 1753532] Re: apt-get update doesn't get new packages

2018-04-12 Thread Frank Heimes

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: apt (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: ubuntu-z-systems
   Status: New => Invalid

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

Title:
  apt-get update doesn't get new packages

Status in Ubuntu on IBM z Systems:
  Invalid
Status in apt package in Ubuntu:
  Invalid

Bug description:
  apt-get update and upgrade do not upgrade the system
   
  --Steps to Reproduce---
   apt-get update and apt-get upgrade.  It shows nothing to upgrade. But the 
kernel level is in an old version. 
   
  New kernel packages are not shown in apt-cache. Somehow, the new packages are 
not being got from repo server when do apt-get update.

  Executed on 16.04.3

  Btw, not all the Ubuntu servers have that issues. I crossed check the
  sources.list among the servers, there is no difference. So don't know
  what caused some of them cannot get any update from ubuntu repo.
  However, I can install individual packages via apt-get install
  command.

  There is not any error during the apt-get update && apt-get upgrade.
  It showed nothing to upgrade.

  Hit:1 http://ports.ubuntu.com/ubuntu-ports xenial InRelease
  Hit:2 http://ports.ubuntu.com/ubuntu-ports xenial-updates InRelease
  Hit:3 http://ports.ubuntu.com/ubuntu-ports xenial-backports InRelease
  Hit:4 http://ports.ubuntu.com/ubuntu-ports xenial-security InRelease
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  The servers were able to manually upgrade for a long time. But all the
  sudden, they are not upgradable. It looks it can not retrieve new
  kernel level packages during the apt-get update. The highest kernel
  level can be installed is 4.4.0-97.. not more higher..


  HWS: I mirrored this problem description, to be able to get support
  for getting this fixed. Even it seems to be an environment problem.
  But direct Q&A will probably help

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1753532/+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 1763203] Re: package console-setup-hostname 1.108ubuntu15.3 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package k

2018-04-12 Thread Hans Joachim Desserud

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1588998, so it 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. Feel free to continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1588998
   [master] package console-setup-linux 1.108ubuntu15 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15

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

Title:
  package console-setup-hostname 1.108ubuntu15.3 failed to
  install/upgrade: trying to overwrite '/lib/systemd/system/console-
  setup.service', which is also in package keyboard-configuration
  1.108ubuntu15.3

Status in console-setup package in Ubuntu:
  New

Bug description:
  i upgraded my system.but it said an error

  ProblemType: Package
  DistroRelease: Kali 2018.2
  Package: console-setup-linux 1.108ubuntu15.3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Apr 12 04:52:24 2018
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2018-04-11 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.19.0.5kali1
   apt  1.2.25
  SourcePackage: console-setup
  Title: package console-setup-hostname 1.108ubuntu15.3 failed to 
install/upgrade: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1763203/+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 1763473] [NEW] package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-04-12 Thread shamitbagchi

Public bug reported:

COMMAND GIVEN WAS: sudo apt-get -y dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.4
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Apr 12 23:46:46 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-12-11 (122 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.24
SourcePackage: util-linux
Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (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 util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763473

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  COMMAND GIVEN WAS: sudo apt-get -y dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Apr 12 23:46:46 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-12-11 (122 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.24
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation 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/util-linux/+bug/1763473/+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: /usr/bin/unattended-upgrade:11:GI_libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

This bug was fixed in the package python-apt - 1.6.0~rc2ubuntu2

---
python-apt (1.6.0~rc2ubuntu2) bionic; urgency=medium

  * apt/auth.py: Protect against race with gpg when removing tmpdir
(Closes: #871585)
  * Document Architecture: all handling in Package.{fullname,architecture()}
(Closes: #863193)
  * python/tag.cc: Fix invalid read in TagFileNext
  * Raise ValueError if objects passed to DepCache are from different cache
(LP: #1737441)

 -- Julian Andres Klode   Thu, 12 Apr 2018 11:22:27
+0200

** Changed in: python-apt (Ubuntu Bionic)
   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:
  /usr/bin/unattended-
  
upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

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

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 
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 1763473] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  COMMAND GIVEN WAS: sudo apt-get -y dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Apr 12 23:46:46 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-12-11 (122 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.24
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation 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/util-linux/+bug/1763473/+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 1763478] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2018-04-12 Thread Marcos K

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

Public bug reported:

Happens after first boot of fresh new Ubuntu Mate 16.04 installation.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Thu Apr 12 14:52:41 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2018-04-12 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Happens after first boot of fresh new Ubuntu Mate 16.04 installation.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Apr 12 14:52:41 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2018-04-12 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new 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/avahi/+bug/1763478/+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 1763476] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

2018-04-12 Thread marcelo

Public bug reported:

Se encontraron errores al procesar:
 /var/cache/apt/archives/avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu2.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: i386
Date: Thu Apr 12 15:32:28 2018
ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
InstallationDate: Installed on 2017-05-28 (319 days ago)
InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: el subproceso script pre-removal nuevo devolvió el
  código de salida de error 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Se encontraron errores al procesar:
   /var/cache/apt/archives/avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu2.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  Date: Thu Apr 12 15:32:28 2018
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2017-05-28 (319 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1763476/+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 1763478] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

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 #1760128, 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 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new 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 avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1763478

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Happens after first boot of fresh new Ubuntu Mate 16.04 installation.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Apr 12 14:52:41 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2018-04-12 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new 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/avahi/+bug/1763478/+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 1763487] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2018-04-12 Thread Kishansingh Rajput

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

Public bug reported:

Libre Office writer and Firefox
unexpectedly crashes

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Fri Apr 13 00:35:22 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2018-02-27 (43 days ago)
InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Libre Office writer and Firefox
  unexpectedly crashes

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Fri Apr 13 00:35:22 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2018-02-27 (43 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new 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/avahi/+bug/1763487/+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 1761867] Re: Can not remove nvidia-390.x drivers

2018-04-12 Thread Kev Bowring

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

** This bug has been marked a duplicate of bug 1761593
   Uninstall left nouveau blacklisted

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

Title:
  Can not remove nvidia-390.x drivers

Status in software-properties package in Ubuntu:
  New

Bug description:
  What additional drivers does do is to remove the nvidia-driver-390
  metapackage. This has no practical effect in removing the driver & lib
  packages other than having them marked for autoremove

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.25
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr  6 16:42:17 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1761867/+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 1763487] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

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

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 #1760128, 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 1760128
   package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: 
subprocess new 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 avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1763487

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Libre Office writer and Firefox
  unexpectedly crashes

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Fri Apr 13 00:35:22 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2018-02-27 (43 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new 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/avahi/+bug/1763487/+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 1763492] Re: Update page - Sign In is in German, unable to proceed

2018-04-12 Thread Kev Bowring

** Attachment added: "Anmelden !!!"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763492/+attachment/5112753/+files/Screenshot_2018-04-12_20-22-38.png

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

Title:
  Update page - Sign In is in German, unable to proceed

Status in software-properties package in Ubuntu:
  New

Bug description:
  On a system setup for English, UK English keyboard - Sign In on the
  update page is in German not English.

  Further - following click on the first Anmelden - I get a dialogue
  that seems to get no further.

  Can I take it from the second issue that LivePatch is only available
  to Ubuntu and not flavours?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.28
  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
  CurrentDesktop: XFCE
  Date: Thu Apr 12 20:22:13 2018
  InstallationDate: Installed on 2017-09-02 (222 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763492/+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 1763492] [NEW] Update page - Sign In is in German, unable to proceed

2018-04-12 Thread Kev Bowring

Public bug reported:

On a system setup for English, UK English keyboard - Sign In on the
update page is in German not English.

Further - following click on the first Anmelden - I get a dialogue that
seems to get no further.

Can I take it from the second issue that LivePatch is only available to
Ubuntu and not flavours?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: software-properties-gtk 0.96.24.28
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
CurrentDesktop: XFCE
Date: Thu Apr 12 20:22:13 2018
InstallationDate: Installed on 2017-09-02 (222 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1763492

Title:
  Update page - Sign In is in German, unable to proceed

Status in software-properties package in Ubuntu:
  New

Bug description:
  On a system setup for English, UK English keyboard - Sign In on the
  update page is in German not English.

  Further - following click on the first Anmelden - I get a dialogue
  that seems to get no further.

  Can I take it from the second issue that LivePatch is only available
  to Ubuntu and not flavours?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.28
  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
  CurrentDesktop: XFCE
  Date: Thu Apr 12 20:22:13 2018
  InstallationDate: Installed on 2017-09-02 (222 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1763492/+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 1749722] Re: NTP: take into account systemd-timesyncd where present

2018-04-12 Thread Scott Moser

An upstream commit landed for this bug.

To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=c6dff581


** Changed in: cloud-init
   Status: In Progress => Fix Committed

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

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  Fix Committed
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently, the NTP module configures ntpd during cloud-init install by
  installing and configuring ntpd.

  ntpd competes with systemd-timesyncd on systemd distros like Ubuntu
  Xenial.

  Ideally the NTP module should configure systemd-timesyncd where
  present, falling back to ntpd where not present.

  This stops two separate daemons (ntpd and systemd-timesyncd) competing
  with each other to set the time, where systemd-timesyncd (on Ubuntu at
  least) has an internal hardcoded compiled in timeserver to fall back
  on if no timeserver is configured (which is bad, but what can you do).

  The competing timeserver behaviour is invisible when the machine can
  see the net, but logs this error constantly when the machine cannot
  see the net:

  systemd-timesyncd[527]: Timed out waiting for reply from
  91.189.94.4:123 (ntp.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+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 1759573] Re: vlan on top of untagged network won't start

2018-04-12 Thread Tom Verdaat

Got right on it! Tested your PPA version on the same testcases and it
works perfectly. Indeed the same issue and the same type of resolution.
Your ifquery is more elegant though, so definitely go with that!

Would love to see this released and pushed a.s.a.p. because this is
breaking our production systems!

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

Title:
  vlan on top of untagged network won't start

Status in ifupdown package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  New

Bug description:

  Due to an upgrade (of probably of the ifupdown or vlan package), this 
specific network configuration no longer comes up automatically:
  1) Two or more network interfaces bonded
  2) An untagged network configured on that bond
  3) A vlan on top of that untagged network

  What does come up automatically:
  1) A single (e.g. unbonded) network interface with an untagged network 
configured and a vlan on top of that network
  2) Two or more network interfaces bonded with a vlan on top of that untagged 
bond

  An exact example of the configuration that doesn't work is provided
  below. It fails to come up correctly, both during boot and manually.
  The problem seems to be a blocking dependency loop between the bond
  and the vlan.

  As recommended in
  https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/comments/13
  we added dependency ordering using ifup@.service systemd units for all
  4 interfaces, but this did not affect the behaviour in any way.

  Perhaps related to LP bug 1573272 or bug 1636708 ?

  ==
  Interface configuration
  ==

  auto eno1
  iface eno1 inet manual
 mtu 1500
 bond-master bond1
 bond-primary eno1

  auto eno2
  iface eno2 inet manual
 mtu 1500
 bond-master bond1

  auto bond1
  iface bond1 inet static
 mtu 1500
 address 10.10.10.3
 bond-miimon 100
 bond-mode active-backup
 bond-slaves none
 bond-downdelay 0
 bond-updelay 0
 dns-nameservers 10.10.10.1
 gateway 10.10.10.1
 netmask 255.255.0.0

  auto bond1.2
  iface bond1.2 inet static
 mtu 1500
 address 10.11.10.3
 netmask 255.255.0.0
 vlan-raw-device bond1

  ==
  When bringing up the bond
  ==

  # ifup bond1 &
  Waiting for a slave to join bond1 (will timeout after 60s)
  # ps afx
  (...)
  ifup bond1
   \_ /bin/sh -c /bin/run-parts --exit-on-error /etc/network/if-pre-up.d
   \_ /bin/run-parts --exit-on-error /etc/network/if-pre-up.d
   \_ /bin/sh /etc/network/if-pre-up.d/ifenslave
  (...)
  /lib/systemd/systemd-udevd
   \_ /lib/systemd/systemd-udevd
   \_ /bin/sh /lib/udev/vlan-network-interface
   \_ /bin/sh /etc/network/if-pre-up.d/vlan
   \_ ifup bond1
  (...)

  ==> After waiting 60 seconds:

  # ip link | grep -E 'eno[1|2]|bond1*'
  eno1:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
  eno2:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
  bond1:  mtu 1500 qdisc noqueue 
state DOWN mode DEFAULT group default qlen 1000
  bond1.2@bond1:  mtu 1500 qdisc noqueue 
state LOWERLAYERDOWN mode DEFAULT group default qlen 1000

  ==
  When bringing up a slave
  ==

  # ifup eno1
  Waiting for bond master bond1 to be ready
  # ps afx
  (...)
  /lib/systemd/systemd-udevd
   \_ /lib/systemd/systemd-udevd
   \_ /bin/sh /lib/udev/vlan-network-interface
   \_ /bin/sh /etc/network/if-pre-up.d/vlan
   \_ ifup bond1
   \_ /bin/sh -c /bin/run-parts --exit-on-error 
/etc/network/if-pre-up.d
   \_ /bin/run-parts --exit-on-error 
/etc/network/if-pre-up.d
   \_ /bin/sh /etc/network/if-pre-up.d/ifenslave
   \_ /bin/sh /lib/udev/vlan-network-interface
   \_ /bin/sh /etc/network/if-pre-up.d/vlan
   \_ ifup bond1
  (...)
  # ip link | grep -E 'eno[1|2]|bond1*'
  eno1:  mtu 1500 qdisc mq master bond1 
state UP mode DEFAULT group default qlen 1000
  eno2:  mtu 1500 qdisc mq state DOWN mode DEFAULT group 
default qlen 1000
  bond1:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000

  ==
  Only workaround that works
  ==

  # ifup eno1
  Waiting for bond master bond1 to be ready
  # kill $(ps -ef | grep 'ifup bond1' | sed -n 2p | awk '{ print $2}')
  # ifup eno2

  # ip link | grep -E 'eno[1|2]|bond1*'
  eno1:  mtu

[Touch-packages] [Bug 1761708] Re: QWebEngineView crashes

2018-04-12 Thread Simon Quigley

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

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

Title:
  QWebEngineView crashes

Status in qtbase-opensource-src package in Ubuntu:
  Triaged

Bug description:
  I have KUbuntu 18.04 with the latest updates. I installed all pyqt3
  stuff plus python3-pyqt5.qtwebengine and tried to execute a tiny
  webengine demo (attached):

  $ python3 browser.py
  Segmentation fault (core dumped)
  [1:1:0100/00.971262:ERROR:broker_posix.cc(41)] Invalid node channel 
message

  Please see the attached core file & gdb bt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1761708/+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 1727237] Re: systemd-resolved is not finding a domain

Dimitri, can you please confirm what the effect of this patch is when a
user has manually reconfigured resolved to enable DNSSEC?  Does this do
the right thing, or does it become a downgrade attack?

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  
  [Impact] 

   * Certain WiFi captive portals do not support EDNS0 queries, as per RFC.
   * Instead of responding with the captive portal IP address, they resond with 
domain not found
   * This prevents the user from hitting the captive portal login page, able to 
authenticate, and gain access to the internets.

  [The Fix]

   * As per tcp dumps, the problem arrises from receiving NXDOMAIN when queried 
with EDNS0
   * And receiving the right response without EDNS0
   * The solution was to downgrade transactions, and retry EDNS0 + NXDOMAIN 
result without EDNS0 with a hope of getting the right answer.

  [Test Case]

  * systemd-resolve securelogin.example.com
  * journalctl -b -u systemd-resolve | grep DVE-2018

  You should obverse that a warning message that transaction was retried
  with a reduced feature level e.g. UDP or TCP.

  After this test case is performed the result will be cached, therefore
  to revert to pristine state perform

  * systemd-resolve --flush-caches

  [Regression Potential]

   * The code retries, and then caches, NXDOMAIN results for certain
  queries (those that have 'secure' in them) with and without EDNS0.

   * Thus initial query for these domains may take longer, but hopefully
  will manage to receive the correct response.

   * Manufacturers are encouraged to correctly support EDNS0 queries,
  with flag D0 set to zero.

  [Other Info]
   
   * This issue is tracked as a dns-violation at
  
https://github.com/dns-violations/dns-violations/blob/master/2018/DVE-2018-0001.md

  [Original Bug report]

  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$

  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+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 1749722] Re: NTP: take into account systemd-timesyncd where present

** Merge proposal linked:
   
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/343136

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

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  Fix Committed
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently, the NTP module configures ntpd during cloud-init install by
  installing and configuring ntpd.

  ntpd competes with systemd-timesyncd on systemd distros like Ubuntu
  Xenial.

  Ideally the NTP module should configure systemd-timesyncd where
  present, falling back to ntpd where not present.

  This stops two separate daemons (ntpd and systemd-timesyncd) competing
  with each other to set the time, where systemd-timesyncd (on Ubuntu at
  least) has an internal hardcoded compiled in timeserver to fall back
  on if no timeserver is configured (which is bad, but what can you do).

  The competing timeserver behaviour is invisible when the machine can
  see the net, but logs this error constantly when the machine cannot
  see the net:

  systemd-timesyncd[527]: Timed out waiting for reply from
  91.189.94.4:123 (ntp.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+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 1763520] [NEW] after upgrade to bionic, printing fails without explanation / logs / debuggability

Public bug reported:

I am unable to print to my network-attached printer after upgrade to
bionic.  ps shows:

lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

Note the un-reaped gs process.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 12 15:07:49 2018
InstallationDate: Installed on 2010-09-24 (2757 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: LENOVO 2306CTO
Papersize: letter
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET97WW (2.57 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2306CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

** Affects: cups (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apparmor apport-bug bionic

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups package in Ubuntu:
  New

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  r

[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability

The particular printer instance showing this failure is one that I've
set up specifically in the course of trying to debug this (hence, '-new'
in the queue name), but the problem exists also with my previously-
existing queue.

** Changed in: cups (Ubuntu)
   Importance: Undecided => High

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

Title:
  after upgrade to bionic, printing fails without explanation / logs /
  debuggability

Status in cups package in Ubuntu:
  New

Bug description:
  I am unable to print to my network-attached printer after upgrade to
  bionic.  ps shows:

  lp   26047  0.0  0.0  91668  5756 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  lp   26050  0.1  0.0  0 0 ?Z15:06   0:00  |   \_ [gs] 

  lp   26048  0.0  0.0  79908  3836 ?S15:06   0:00  \_ 
HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto 
print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery 
noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB 
Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4
  root 26049  0.0  0.0  84388  6192 ?S15:06   0:00  \_ 
ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 
print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 
number-up=1 MediaType=Stationery noCollate print-scaling=auto 
PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble 
job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1523570792 
time-at-processing=1523570792 print-quality=4

  Note the un-reaped gs process.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 15:07:49 2018
  InstallationDate: Installed on 2010-09-24 (2757 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: '/etc/cups/cupsd.conf']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1763520/+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 1763522] Re: systemd-logind crashed with SIGABRT in log_assert_failed_realm()

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

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 #1710498, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1763522/+attachment/5112946/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1763522/+attachment/5112949/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1763522/+attachment/5112955/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1763522/+attachment/5112957/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1763522/+attachment/5112958/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1763522/+attachment/5112959/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1763522/+attachment/5112961/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1710498

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-logind crashed with SIGABRT in log_assert_failed_realm()

Status in systemd package in Ubuntu:
  New

Bug description:
  just booted

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Wed Apr 11 08:34:05 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-02-08 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180207)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 0d8c:0201 C-Media Electronics, Inc. CM6501
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 046a:b091 Cherry GmbH 
   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.
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=c1f64b0e-823f-4082-b3b1-727a6ac5effa ro plymouth:debug drm.debug=0xe 
text
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed_realm () from /lib/systemd/libsystemd-shared-237.so
   close_nointr () from /lib/systemd/libsystemd-shared-237.so
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in log_assert_failed_realm()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.30
  dmi.board.name: AM2NF3-VSTA
  dmi.board.vendor: ASRock
  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.:bvrP3.30:bd02/22/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF3-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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1763522/+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 1744333] Re: Looping too fast. Throttling execution a little

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

Title:
  Looping too fast. Throttling execution a little

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Looks like I have the same issue described here:
  https://github.com/systemd/systemd/issues/719

  root@xxx:~# lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04


  
  root@xxx:~# dpkg -l | grep systemd
  ii  libpam-systemd:amd64229-4ubuntu21 
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64   229-4ubuntu21 
 amd64systemd utility library
  ii  systemd 229-4ubuntu21 
 amd64system and service manager
  ii  systemd-sysv229-4ubuntu21 
 amd64system and service manager - SysV links

  
  As a workaround, I would need to reboot the server.
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1744333/+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 1763534] [NEW] ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

2018-04-12 Thread Andres Rodriguez

Public bug reported:

When executing ifconfig, it outputs the whole 10 characters of the
interface name. However, when using ifconfig -s (or ifconfig -a -s) it
doesn't include all the name of the interface (or 10+ characters).
Instead, it outputs only 8 characters of the interface.

ubuntu@dradis:~$ ifconfig -a
enP2p1s0f0: flags=4163  mtu 1500
inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
RX packets 154570  bytes 229998298 (229.9 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 61080  bytes 6131460 (6.1 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enP2p1s0f1: flags=4098  mtu 1500
ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


ubuntu@dradis:~$ ifconfig -a -s
Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
enP2p1s0  1500   154607  0  0 0 61101  0  0  0 BMRU
enP2p1s0  15000  0  0 0 0  0  0  0 BM

** Affects: net-tools (Ubuntu)
 Importance: Critical
 Status: New

** Affects: net-tools (Ubuntu Bionic)
 Importance: Critical
 Status: New

** Description changed:

  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.
  
- ubuntu@dradis:~$ ifconfig
+ ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
- RX packets 154396  bytes 229982516 (229.9 MB)
+ RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
- TX packets 60547  bytes 6062897 (6.0 MB)
+ TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  
- ubuntu@dradis:~$ ifconfig -s
+ enP2p1s0f1: flags=4098  mtu 1500
+ ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
+ RX packets 0  bytes 0 (0.0 B)
+ RX errors 0  dropped 0  overruns 0  frame 0
+ TX packets 0  bytes 0 (0.0 B)
+ TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
+ 
+ 
+ ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
- enP2p1s0  1500   154538  0  0 0 61063  0  0  0 
BMRU
- lo   65536  118  0  0 0   118  0  0  0 LRU
+ enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
+ enP2p1s0  15000  0  0 0 0  0  0  0 BM

** Changed in: net-tools (Ubuntu)
   Importance: Undecided => Critical

** Summary changed:

- ifconfig -s (or -a -s) doesn't output the full name of the interface
+ ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when 
interfaces are 10+ characters.

** Also affects: net-tools (Ubuntu Bionic)
   Importance: Critical
   Status: New

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  New
Status in net-tools source package in Bionic:
  New

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes

[Touch-packages] [Bug 1763537] [NEW] libpulse-dev don't provide the required files to build static programs

2018-04-12 Thread Leonardo Müller

Public bug reported:

The package libpulse-dev don't provide the static libraries files
required to build static programs using libpulse-dev but, when building
pulseaudio, there is a option to build static libraries. Could they be
added to the package libpulse-dev?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpulse-dev 1:11.1-1ubuntu7
Uname: Linux 4.16.1-041601-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   usuario1945 F...m pulseaudio
 /dev/snd/controlC0:  usuario1945 F pulseaudio
 /dev/snd/seq:usuario1926 F timidity
CurrentDesktop: XFCE
Date: Thu Apr 12 20:13:18 2018
InstallationDate: Installed on 2017-06-13 (303 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2017-10-20 (174 days ago)
dmi.bios.date: 07/10/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN43WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO

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

Title:
  libpulse-dev don't provide the required files to build static programs

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The package libpulse-dev don't provide the static libraries files
  required to build static programs using libpulse-dev but, when
  building pulseaudio, there is a option to build static libraries.
  Could they be added to the package libpulse-dev?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libpulse-dev 1:11.1-1ubuntu7
  Uname: Linux 4.16.1-041601-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   usuario1945 F...m pulseaudio
   /dev/snd/controlC0:  usuario1945 F pulseaudio
   /dev/snd/seq:usuario1926 F timidity
  CurrentDesktop: XFCE
  Date: Thu Apr 12 20:13:18 2018
  InstallationDate: Installed on 2017-06-13 (303 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (174 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1763537/+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 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

2018-04-12 Thread Manoj Iyer

** Changed in: net-tools (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools source package in Bionic:
  Confirmed

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
  enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
  enP2p1s0  15000  0  0 0 0  0  0  0 BM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+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 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

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

** Changed in: net-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools source package in Bionic:
  Confirmed

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
  enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
  enP2p1s0  15000  0  0 0 0  0  0  0 BM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+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 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

net-tools is deprecated in favor of iproute2, and is only included in
the server seed in 18.04 because there wasn't time in the 18.04 cycle to
verify the effects of its removal.  What depends on the behavior of
'ifconfig -s' (which I've never once in 20 years of Linux seen before)
that makes this 'critical'?

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools source package in Bionic:
  Confirmed

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
  enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
  enP2p1s0  15000  0  0 0 0  0  0  0 BM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+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 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

2018-04-12 Thread Manoj Iyer

Because this bug causes the following to happen:
https://bugs.launchpad.net/maas/+bug/1759284

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools source package in Bionic:
  Confirmed

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
  enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
  enP2p1s0  15000  0  0 0 0  0  0  0 BM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+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 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

Ok; that seems like something that should be fixed in maas by making it
not parse the output of deprecated tools with buggy interfaces?

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools source package in Bionic:
  Confirmed

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
  enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
  enP2p1s0  15000  0  0 0 0  0  0  0 BM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+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 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

That said, this does appear to be a change in behavior between net-tools
1.60 in xenial and net-tools 1.60+git20161116.90da8a0 in bionic.

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools source package in Bionic:
  Confirmed

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
  enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
  enP2p1s0  15000  0  0 0 0  0  0  0 BM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+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 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

OTOH, it's also been this way since zesty and no one else seems to have
cared until now that it regressed.  I think the effort is better spent
fixing maas to not depend on deprecated tools.

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools source package in Bionic:
  Confirmed

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
  enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
  enP2p1s0  15000  0  0 0 0  0  0  0 BM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+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 1763537] Re: libpulse-dev don't provide the required files to build static programs

Yes it's probably possible. Although unusual to want a statically linked
PulseAudio.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Triaged

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Low

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

Title:
  libpulse-dev don't provide the required files to build static programs

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  The package libpulse-dev don't provide the static libraries files
  required to build static programs using libpulse-dev but, when
  building pulseaudio, there is a option to build static libraries.
  Could they be added to the package libpulse-dev?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libpulse-dev 1:11.1-1ubuntu7
  Uname: Linux 4.16.1-041601-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   usuario1945 F...m pulseaudio
   /dev/snd/controlC0:  usuario1945 F pulseaudio
   /dev/snd/seq:usuario1926 F timidity
  CurrentDesktop: XFCE
  Date: Thu Apr 12 20:13:18 2018
  InstallationDate: Installed on 2017-06-13 (303 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (174 days ago)
  dmi.bios.date: 07/10/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1763537/+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 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: New => In Progress

** Changed in: gstreamer-vaapi (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gstreamer-vaapi (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** No longer affects: totem (Ubuntu)

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GStreamer:
  Confirmed
Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Won't Fix
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Re: [Touch-packages] [Bug 1763534] Re: ifconfig -s (or -a -s) only outputs 8 characters of the interface name, when interfaces are 10+ characters.

2018-04-12 Thread Andres Rodriguez

Maas is being fixed to use “ip” instead of ifconfig. The reason why it
wasn’t noticed before is because MAAS does only use LTS releases for
commissioning. Since we only run ifconfig -a during commissioning, then the
regression wasn’t found till recently.

On Thu, Apr 12, 2018 at 9:10 PM Steve Langasek 
wrote:

> OTOH, it's also been this way since zesty and no one else seems to have
> cared until now that it regressed.  I think the effort is better spent
> fixing maas to not depend on deprecated tools.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1763534
>
> Title:
>   ifconfig -s (or -a -s) only outputs 8 characters of the interface
>   name, when interfaces are 10+ characters.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=net-tools;
> component=main; status=Confirmed; importance=Critical;
> assignee=canonical-foundations;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic;
> sourcepackage=net-tools; component=main; status=Confirmed;
> importance=Critical; assignee=canonical-foundations;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl janitor manjo vorlon
> Launchpad-Bug-Reporter: Andres Rodriguez (andreserl)
> Launchpad-Bug-Modifier: Steve Langasek (vorlon)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: andreserl
>
-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

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

Title:
  ifconfig -s (or -a -s) only outputs 8 characters of the interface
  name, when interfaces are 10+ characters.

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools source package in Bionic:
  Confirmed

Bug description:
  When executing ifconfig, it outputs the whole 10 characters of the
  interface name. However, when using ifconfig -s (or ifconfig -a -s) it
  doesn't include all the name of the interface (or 10+ characters).
  Instead, it outputs only 8 characters of the interface.

  ubuntu@dradis:~$ ifconfig -a
  enP2p1s0f0: flags=4163  mtu 1500
  inet 10.245.71.108  netmask 255.255.248.0  broadcast 10.245.71.255
  inet6 fe80::ae1f:6bff:fe09:c052  prefixlen 64  scopeid 0x20
  ether ac:1f:6b:09:c0:52  txqueuelen 1000  (Ethernet)
  RX packets 154570  bytes 229998298 (229.9 MB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 61080  bytes 6131460 (6.1 MB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enP2p1s0f1: flags=4098  mtu 1500
  ether ac:1f:6b:09:c0:53  txqueuelen 1000  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  
  ubuntu@dradis:~$ ifconfig -a -s
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR Flg
  enP2p1s0  1500   154607  0  0 0 61101  0  0  0 
BMRU
  enP2p1s0  15000  0  0 0 0  0  0  0 BM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/1763534/+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 1763417] Re: thin red lines around "Format" button in gnome-disks

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

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

Title:
  thin red lines around "Format" button in gnome-disks

Status in Ubuntu theme:
  New
Status in gnome-disk-utility package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1763417/+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 1762899] Re: /etc/resolv.conf empty after upgrading from 16.04 to 18.40

2018-04-12 Thread Dimitri John Ledkov

resolvconf (1.79ubuntu10) bionic; urgency=medium

  * Fix race of not injecting resolved config into resolvconf on LXD
container boot. LP: #1763108

 -- Dimitri John Ledkov   Thu, 12 Apr 2018 12:46:24
+0100

** Changed in: systemd (Ubuntu Bionic)
   Status: Triaged => Fix Released

** Package changed: systemd (Ubuntu Bionic) => resolvconf (Ubuntu
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/1762899

Title:
  /etc/resolv.conf empty after upgrading from 16.04 to 18.40

Status in resolvconf package in Ubuntu:
  Fix Released
Status in resolvconf source package in Bionic:
  Fix Released

Bug description:
  I just upgraded one of my LXC containers to 18.04 and after rebooting,
  the /etc/resolv.conf contains no nameservers. systemd-resolve,
  however, resolves fine and the --status returns the DNS server details
  as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 22:53:30 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to bionic on 2018-04-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1762899/+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 1763570] [NEW] file does not fully recognize ISO images

2018-04-12 Thread halogen2

Public bug reported:

Environment:

Xubuntu 18.04

$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

$ apt-cache policy file
file:
  Installed: 1:5.32-2
  Candidate: 1:5.32-2
  Version table:
 *** 1:5.32-2 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


Steps-to-reproduce:

1) Download Xubuntu 16.04 ISO from
http://cdimages.ubuntu.com/xubuntu/releases/16.04/release/xubuntu-16.04
-desktop-amd64.iso

2) run: file --mime-type xubuntu-16.04-desktop-amd64.iso

3) run: file xubuntu-16.04-desktop-amd64.iso


Expected results:

Result of (2) should be:
$ file --mime-type xubuntu-16.04-desktop-amd64.iso
xubuntu-16.04-desktop-amd64.iso: application/x-iso9660-image

... and result of (3) should be:
$ file xubuntu-16.04-desktop-amd64.iso
xubuntu-16.04-desktop-amd64.iso: DOS/MBR boot sector ISO 9660 CD-ROM filesystem 
data (DOS/MBR boot sector) 'Xubuntu 16.04 LTS amd64' (bootable); partition 2 : 
ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 2410708, 
4736 sectors


Actual results:

$ file --mime-type xubuntu-16.04-desktop-amd64.iso
xubuntu-16.04-desktop-amd64.iso: application/octet-stream

$ file xubuntu-16.04-desktop-amd64.iso
xubuntu-16.04-desktop-amd64.iso: DOS/MBR boot sector; partition 2 : ID=0xef, 
start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 2410708, 4736 
sectors


ubuntuforums thread: https://ubuntuforums.org/showthread.php?t=2388736

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


** Tags: bionic

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

Title:
  file does not fully recognize ISO images

Status in file package in Ubuntu:
  New

Bug description:
  Environment:

  Xubuntu 18.04

  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ apt-cache policy file
  file:
Installed: 1:5.32-2
Candidate: 1:5.32-2
Version table:
   *** 1:5.32-2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Steps-to-reproduce:

  1) Download Xubuntu 16.04 ISO from
  http://cdimages.ubuntu.com/xubuntu/releases/16.04/release/xubuntu-16.04
  -desktop-amd64.iso

  2) run: file --mime-type xubuntu-16.04-desktop-amd64.iso

  3) run: file xubuntu-16.04-desktop-amd64.iso

  
  Expected results:

  Result of (2) should be:
  $ file --mime-type xubuntu-16.04-desktop-amd64.iso
  xubuntu-16.04-desktop-amd64.iso: application/x-iso9660-image

  ... and result of (3) should be:
  $ file xubuntu-16.04-desktop-amd64.iso
  xubuntu-16.04-desktop-amd64.iso: DOS/MBR boot sector ISO 9660 CD-ROM 
filesystem data (DOS/MBR boot sector) 'Xubuntu 16.04 LTS amd64' (bootable); 
partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), 
startsector 2410708, 4736 sectors

  
  Actual results:

  $ file --mime-type xubuntu-16.04-desktop-amd64.iso
  xubuntu-16.04-desktop-amd64.iso: application/octet-stream

  $ file xubuntu-16.04-desktop-amd64.iso
  xubuntu-16.04-desktop-amd64.iso: DOS/MBR boot sector; partition 2 : ID=0xef, 
start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 2410708, 4736 
sectors

  
  ubuntuforums thread: https://ubuntuforums.org/showthread.php?t=2388736

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1763570/+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 1748812] Re: cannot view wifi networks after resume from suspend

2018-04-12 Thread Kai-Heng Feng

I got XPS 9360 at hand, but unfortunately I can't reproduce the issue.

Can you try the latest Xenial (16.04) image here?
http://cdimages.ubuntu.com/xenial/daily-live/current/

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+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 1763575] [NEW] link_config: autonegotiation is unset or enabled

2018-04-12 Thread dino99

Public bug reported:

Get that message logged:

systemd-udevd[401]: link_config: autonegotiation is unset or enabled,
the speed and duplex are not writable.

and system settings showing 'wired unmanaged'; that makes network speed
slowing by 50 %

Please check that fix has been really merged:

https://unix.stackexchange.com/questions/413187/is-systemd-links-handling-of-auto-negotiation-broken
https://github.com/systemd/systemd/pull/7808/files

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu8
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
CurrentDesktop: GNOME
Date: Fri Apr 13 07:11:23 2018
EcryptfsInUse: Yes
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.30
dmi.board.name: B150M-HDV
dmi.board.vendor: ASRock
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.:bvrP7.30:bd01/23/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV: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.
modified.conffile..etc.systemd.journald.conf: [modified]
mtime.conffile..etc.systemd.journald.conf: 2018-01-03T11:19:10.780935

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


** Tags: amd64 apport-bug bionic package-from-proposed

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

Title:
  link_config: autonegotiation is unset or enabled

Status in systemd package in Ubuntu:
  New

Bug description:
  Get that message logged:

  systemd-udevd[401]: link_config: autonegotiation is unset or enabled,
  the speed and duplex are not writable.

  and system settings showing 'wired unmanaged'; that makes network
  speed slowing by 50 %

  Please check that fix has been really merged:

  
https://unix.stackexchange.com/questions/413187/is-systemd-links-handling-of-auto-negotiation-broken
  https://github.com/systemd/systemd/pull/7808/files

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu8
  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
  CurrentDesktop: GNOME
  Date: Fri Apr 13 07:11:23 2018
  EcryptfsInUse: Yes
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P7.30
  dmi.board.name: B150M-HDV
  dmi.board.vendor: ASRock
  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.:bvrP7.30:bd01/23/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV: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.
  modified.conffile..etc.systemd.journald.conf: [modified]
  mtime.conffile..etc.systemd.journald.conf: 2018-01-03T11:19:10.780935

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1763575/+subscriptions

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

[Touch-packages] [Bug 1761746] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: підпроцес новий pre-removal сценарій повернув статус помилку 1

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

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

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: підпроцес новий pre-removal сценарій повернув статус
  помилку 1

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  1) Description:   Ubuntu 16.04.4 LTS Release: 16.04
  2) Встановлено: 0.6.32~rc+dfsg-1ubuntu2
Кандидат:0.6.32~rc+dfsg-1ubuntu2.1
Таблиця версій:
   0.6.32~rc+dfsg-1ubuntu2.1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
   *** 0.6.32~rc+dfsg-1ubuntu2 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  Failed when upgrade package. The subprocess of the new pre-removal
  script returned the status of the error 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Apr  6 15:59:47 2018
  ErrorMessage: підпроцес новий pre-removal сценарій повернув статус помилку 1
  InstallationDate: Installed on 2017-12-18 (109 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: підпроцес новий pre-removal сценарій повернув статус помилку 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1761746/+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 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-04-12 Thread Shih-Yuan Lee

I have checked pulseaudio/1:8.0-0ubuntu3.9 on xenial and it does fix the
problem.

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

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1750947/+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 1763580] [NEW] Xorg crash

2018-04-12 Thread elcomandantetibi

Public bug reported:

Crash occurs every time when booting from Xubuntu 18.04 installation
stick and choosing "Install Xubuntu". Shortly after selecting "Install
Xubuntu", the installer is started, the installation screen is visible
for a few seconds, then the display quickly blanks and drops the user
into a frozen view of the virtual terminal. Shortly thereafter, a
Xubuntu session is automatically started, similarly to having chosen
"Try Xubuntu without installing". Executing "Install Xubuntu" from the
desktop does successfully start the ubiquity installer.

Verifying the installation logs under /var/log/installer shows Xorg as
having crashed with error:

xf860OpenConsole: Switching VT failed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperVersion: 1.393
CompositorRunning: None
CurrentDesktop: XFCE
Date: Fri Apr 13 05:42:46 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2063]
LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180411)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
 Bus 001 Device 003: ID 04f2:0408 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Intel Corp.
dmi.board.vendor: Intel corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Crash occurs every time when booting from Xubuntu 18.04 installation
  stick and choosing "Install Xubuntu". Shortly after selecting "Install
  Xubuntu", the installer is started, the installation screen is visible
  for a few seconds, then the display quickly blanks and drops the user
  into a frozen view of the virtual terminal. Shortly thereafter, a
  Xubuntu session is automatically started, similarly to having chosen
  "Try Xubuntu without installing". Executing "Install Xubuntu" from the
  desktop does successfully start the ubiquity installer.

  Verifying the installation logs under /var/log/installer shows Xorg as
  having crashed with error:

  xf860OpenConsole: Switching VT failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.393
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Apr 13 05:42:46 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2063]
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180411)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 003: ID 04f2:0408 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TER

[Touch-packages] [Bug 50093] Re: Some sysctls are ignored on boot

2018-04-12 Thread Paul Gear

** Summary changed:

- Some sysctl's are ignored on boot
+ Some sysctls are ignored on boot

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

Title:
  Some sysctls are ignored on boot

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: procps

  /etc/init.d/procps.sh comes too early in the boot process to apply a
  lot of sysctl's. As it runs before networking modules are loaded and
  filesystems are mounted, there are quite a lot of commonly-used
  sysctl's which are simply ignored on boot and produce errors to the
  console.

  Simply renaming the symlink from S17 to > S40 probably isn't a great
  solution, as there are probably folk who want and expect some sysctl's
  to be applied before filesystems are mounted and so on. However,
  simply ugnoring something as important as sysctl settings isn't really
  on. Administrators expect the settings in /etc/sysctl.conf to take
  effect.

  One sto-gap solution would be to run sysctl -p twice; once at S17 and once at 
S41. There may still be some warnings and errors, but everything would be 
applied. A different, more complex approach might be to re-architect the sysctl 
configuration into something like;
   
  /etc/sysctl.d/$modulename

  and have the userland module-loading binaries take care of applying
  them after modules are loaded. Though this may take care of explicitly
  loaded modules only, I'm not sure.

  Incidentally, /etc/sysctl.conf still refers to
  /etc/networking/options, but hasn't that been deprecated?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 1763584] [NEW] ureadahead service fails with error Error while tracing: No such file or directory

2018-04-12 Thread Dmitriy Geels

Public bug reported:

I'm reporting this as duplicate of #1176536 to provide more info.

dmig@dmig-Inspiron-5379:~$ systemctl status ureadahead.service 
● ureadahead.service - Read required files in advance
   Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-04-13 13:09:41 +07; 10min 
ago
 Main PID: 379 (code=exited, status=5)

Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: ureadahead: Error while 
tracing: No such file or directory
Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: Counted 8 CPUs

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ureadahead 0.100.0-20
Uname: Linux 4.16.2-041602-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 13 13:13:26 2018
InstallationDate: Installed on 2018-03-27 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
SourcePackage: ureadahead
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ureadahead service fails with error Error while tracing: No such file
  or directory

Status in ureadahead package in Ubuntu:
  New

Bug description:
  I'm reporting this as duplicate of #1176536 to provide more info.

  dmig@dmig-Inspiron-5379:~$ systemctl status ureadahead.service 
  ● ureadahead.service - Read required files in advance
 Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Fri 2018-04-13 13:09:41 +07; 
10min ago
   Main PID: 379 (code=exited, status=5)

  Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: ureadahead: Error while 
tracing: No such file or directory
  Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: Counted 8 CPUs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ureadahead 0.100.0-20
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 13:13:26 2018
  InstallationDate: Installed on 2018-03-27 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  SourcePackage: ureadahead
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1763584/+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 1698282] Re: Totem uses dramatically higher CPU than any other video player