date:20170627

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

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

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

Title:
  Scrolling + "Terminal bell" crashes pulseaudio

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  If "Terminal bell" is enabled (in "Profile Preferences" > "General"),
  and I scroll fast in the output of e.g less to cause the "alert sound"
  to be played repeatably very fast, pulseaudio crashes.

  From /var/log/syslog:
  May  9 15:05:13 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:05:15 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default 
sink
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default 
source
  May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Failed to connect 
context: Connection refused
  May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Failed to connect 
context: Connection refused
  May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Unable to find stream 
for bar '(null)'
  May  9 15:05:17 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
  May  9 15:06:01 ubuntu-laptop indicator-sound[2948]: message repeated 22 
times: [ volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue May  9 14:58:51 2017
  InstallationDate: Installed on 2017-05-01 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1689555/+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 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates

2017-06-27 Thread Yuan-Chen Cheng

** Changed in: oem-priority/xenial
   Importance: High => Critical

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

Title:
  No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1700872] [NEW] software update

2017-06-27 Thread emilram

Public bug reported:

failure to download repository information

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Jun 28 05:41:20 2017
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2017-06-27 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
MachineType: Gigabyte Technology Co., Ltd. 945GCMX-S2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=2370472e-b9a6-4cb1-b26e-385e3d2f83bd ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4
dmi.board.name: 945GCMX-S2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/24/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCMX-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCMX-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: 945GCMX-S2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Jun 28 05:28:50 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSEMICCHIP Usb Mouse  MOUSE, id 8
 inputWebcam C170  KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12309 
 vendor DEL
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: apport-bug i386 trusty 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/1700872

Title:
  software update

Status in xorg package in Ubuntu:
  New

Bug description:
  failure to download repository information

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun 28 05:41:20 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2017-06-27 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: Gigabyte Technology Co., Ltd. 945GCMX-S2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=2370472e-b9a6-4cb1-b26e-385e3d2f83bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: 945GCMX-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/24/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCMX-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCMX-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GCMX-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2017-06-27 Thread Shih-Yuan Lee

https://packages.debian.org/stretch/network-manager has contained those
fixes.

Could someone help to test
https://launchpad.net/~happyaron/+archive/ubuntu/nm-oem/+packages if it
can fix this bug?

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1674258] Re: lscpu crashs when /dev/mem is not stable to read

This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.3

---
util-linux (2.27.1-6ubuntu3.3) xenial; urgency=medium

  * Cherrypick upstream fix to prevent lscpu crash on arm64 by
accessing DMI in sysfs instead of /dev/mem. LP: #1674258

 -- Ike Panhc   Thu, 18 May 2017 10:49:34 +0800

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

Title:
  lscpu crashs when /dev/mem is not stable to read

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Yakkety:
  Fix Released
Status in util-linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is
  not stable to read, it will cause lscpu crash.

  [Test Case]

   * `sudo lscpu` shall not cause Segmentation fault (core dumped)

  [Regression Potential]

   * Reading from DMI tables is sysfs is more stable then reading from
  /dev/mem and if DMI tables is not available lscpu will use the old way
  to search in /dev/mem. I believe its low regression risk

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

2017-06-27 Thread Chris Halse Rogers

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

Title:
  lscpu crashs when /dev/mem is not stable to read

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Yakkety:
  Fix Released
Status in util-linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is
  not stable to read, it will cause lscpu crash.

  [Test Case]

   * `sudo lscpu` shall not cause Segmentation fault (core dumped)

  [Regression Potential]

   * Reading from DMI tables is sysfs is more stable then reading from
  /dev/mem and if DMI tables is not available lscpu will use the old way
  to search in /dev/mem. I believe its low regression risk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1674258/+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 1674258] Re: lscpu crashs when /dev/mem is not stable to read

This bug was fixed in the package util-linux - 2.29-1ubuntu2.1

---
util-linux (2.29-1ubuntu2.1) zesty; urgency=medium

  * Cherrypick upstream fix to prevent lscpu crash on arm64 by
accessing DMI in sysfs instead of /dev/mem. LP: #1674258

 -- Ike Panhc   Thu, 18 May 2017 10:49:34 +0800

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

Title:
  lscpu crashs when /dev/mem is not stable to read

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Yakkety:
  Fix Released
Status in util-linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is
  not stable to read, it will cause lscpu crash.

  [Test Case]

   * `sudo lscpu` shall not cause Segmentation fault (core dumped)

  [Regression Potential]

   * Reading from DMI tables is sysfs is more stable then reading from
  /dev/mem and if DMI tables is not available lscpu will use the old way
  to search in /dev/mem. I believe its low regression risk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1674258/+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 1674258] Re: lscpu crashs when /dev/mem is not stable to read

This bug was fixed in the package util-linux - 2.28.2-1ubuntu1.2

---
util-linux (2.28.2-1ubuntu1.2) yakkety; urgency=medium

  * Cherrypick upstream fix to prevent lscpu crash on arm64 by
accessing DMI in sysfs instead of /dev/mem. LP: #1674258

 -- Ike Panhc   Thu, 18 May 2017 10:49:34 +0800

** Changed in: util-linux (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

** Changed in: util-linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  lscpu crashs when /dev/mem is not stable to read

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Yakkety:
  Fix Released
Status in util-linux source package in Zesty:
  Fix Released

Bug description:
  [Impact]

   * Read from /dev/mem and scan DMI tables is dangerous, if /dev/mem is
  not stable to read, it will cause lscpu crash.

  [Test Case]

   * `sudo lscpu` shall not cause Segmentation fault (core dumped)

  [Regression Potential]

   * Reading from DMI tables is sysfs is more stable then reading from
  /dev/mem and if DMI tables is not available lscpu will use the old way
  to search in /dev/mem. I believe its low regression risk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1674258/+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 1688208] Re: gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city() from foreach_city() from foreach_city() from foreach_city()

This very common crash has not been reported to errors.ubuntu.com in
several weeks on artful. I verified that I could not reproduce the crash
at LP: #1695567 any more after updating libgweather to 3.24.1-0ubuntu0.1
on Ubuntu GNOME 17.04.

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

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

Title:
  gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city()
  from foreach_city() from foreach_city() from foreach_city()

Status in libgweather:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  Fix Committed

Bug description:
  Impact
  ==
  Memory corruption in libgweather caused gnome-shell to crash. This is 
particularly bad for GNOME on Wayland as a gnome-shell crash will causes the 
user to lose their sessions.

  (GNOME Shell 3.24 introduced a new weather feature in the clock menu.)

  This particular error has been reported over 1000 times to
  errors.ubuntu.com from Ubuntu GNOME 17.04 and was also a Fedora 26
  blocker bug.

  Test Case
  =
  The number of crashes reported on errors.ubuntu.com for gnome-shell should be 
significantly lower once this new version of libgweather rolls out.

  Because e.u.com links this issue with gnome-shell, this is difficult
  to verify except that if you run gnome-shell, it shouldn't crash so
  often especially when first logging in.

  Regression Potential
  
  The main new commit here had already been cherry-picked by Fedora and in 
Ubuntu 17.10 Alpha. Considering the previous 

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/39b6625ed47999dab38b064b2d91bde1e11dec62 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1688208/+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 1695567] Re: /usr/bin/gnome-shell:* Error in `/usr/bin/gnome-shell': double free or corruption (out): ADDR * in g_free() from gweather_location_unref()

Before applying this update, I was able to easily crash GNOME Shell in a
default clean updated Ubuntu GNOME 17.04. All I had to do with click the
system status menu in the top right and enable Location.

After updating to libgweather 3.24.1-0ubuntu0.1, I can't reproduce the
crash.

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

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

Title:
  /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free
  or corruption (out): ADDR *** in g_free() from
  gweather_location_unref()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  This error has been reported over 700 times on errors.ubuntu.com for
  Ubuntu GNOME 17.04.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.

  [Other Info]
  This updates libgweather from 3.24.0 to 3.24.1
  https://git.gnome.org/browse/libgweather/log

  The guard_against_segfault commit was already present in Ubuntu 17.04.

   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695567/+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 1684097] Re: Date format isn't good

2017-06-27 Thread Gunnar Hjalmarsson

In Xenial the translation template has 33 items, and in Zesty it only
has 13. I suspect that this bug was caused by this commit:

http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
datetime/trunk.16.10/revision/476

The missing translation, which Olivier mentioned in the bug description,
is a string in the file formatter-desktop.cpp. However, no strings from
that file is included in the Zesty translation template.

The file po/POTFILES.in, which was dropped through the commit, looked
like this:

src/formatter.cpp
src/formatter-desktop.cpp
src/menu.cpp
src/snap.cpp
src/utils.c

The Zesty translation template only has items from:

src/menu.cpp
src/snap.cpp

I think there is a need to create a proper translation template somehow
to fix this bug.

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

Title:
  Date format isn't good

Status in Ubuntu Translations:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Date format isn't good in date indicator whereas the translation
  format is good https://translations.launchpad.net/ubuntu/zesty/+source
  /indicator-datetime/+pots/indicator-datetime/fr/1/+translate

  In french, it should be displayed "mer. 19 avril" ; not "mer. avril
  19"

  I think it miss this translation witch was present on xenial:
  https://translations.launchpad.net/ubuntu/xenial/+source/indicator-
  datetime/+pots/indicator-datetime/fr/5/+translate

  See the attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1684097/+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 1700757] Re: Missing intermediate certificate from Digicert - "DigiCert Sha2 Secure Server CA"

2017-06-27 Thread Seth Arnold

Hello Darko,

This is a server misconfiguration. Servers need to supply the full
certificate chain to a trusted root certificate, not just their end
certificate. Qualys's excellent ssltest tool caps the grade for this
server at B as a result of this misconfiguration:

https://www.ssllabs.com/ssltest/analyze.html?d=harpers.org

"This server's certificate chain is incomplete. Grade capped to B. "

Thanks

** Changed in: ca-certificates (Ubuntu)
   Status: New => Invalid

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

Title:
  Missing intermediate certificate from Digicert - "DigiCert Sha2 Secure
  Server CA"

Status in ca-certificates package in Ubuntu:
  Invalid

Bug description:
  I think that package is missing the one intermediate certificate from
  DigiCert that is being used for websites.

  DigiCert Sha2 Secure Server CA
  Located at https://www.digicert.com/CACerts/DigiCertSHA2SecureServerCA.crt

  For example harpers.org uses that CA.

  If you execute this from cli:

  curl -v https://harpers.org/wp-
  content/themes/harpers/images/logoBlack.png

  This is the output

   * Hostname was NOT found in DNS cache
*   Trying 54.243.234.21...
* Connected to harpers.org (54.243.234.21) port 443 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS alert, Server hello (2):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate

  Workaround is this:

wget -P /tmp/ -nv 
https://www.digicert.com/CACerts/DigiCertSHA2SecureServerCA.crt
openssl x509 -in /tmp/DigiCertSHA2SecureServerCA.crt -inform DER \
 -out /tmp/DigiCertSHA2SecureServerCA.pem -outform PEM
sudo cp -uv /tmp/DigiCertSHA2SecureServerCA.pem /etc/ssl/certs
sudo c_rehash

  It affects all versions of Ubuntu starting from 14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1700757/+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 1700856] [NEW] /usr/lib/evolution/evolution-calendar-factory-subprocess:11:g_main_context_ref:soup_socket_set_property:object_set_property:g_object_new_internal:g_object_new_vali

2017-06-27 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evolution-data-server.  This problem was most recently seen with package 
version 3.22.7-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/5fbe24c6d9fbde80c0c8a6c0436da49809ae6515 
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 you can request it at 
http://forms.canonical.com/reports/.

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: wily xenial yakkety zesty

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

Title:
  /usr/lib/evolution/evolution-calendar-factory-
  
subprocess:11:g_main_context_ref:soup_socket_set_property:object_set_property:g_object_new_internal:g_object_new_valist

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evolution-data-server.  This problem was most recently seen with package 
version 3.22.7-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/5fbe24c6d9fbde80c0c8a6c0436da49809ae6515 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1700856/+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 1700854] Re: package software-properties-gtk 0.96.20.5 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-06-27 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package software-properties-gtk 0.96.20.5 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in software-properties package in Ubuntu:
  New

Bug description:
  The software app froze while updating, and now whenever I try to
  install or update anything I get a message saying I need to run dpkg
  --configure -a first, but terminal freezes when I try to run it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.20.5
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun 28 03:31:28 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-06-27 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: software-properties
  Title: package software-properties-gtk 0.96.20.5 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/software-properties/+bug/1700854/+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 1700854] [NEW] package software-properties-gtk 0.96.20.5 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-06-27 Thread Aidan Lloyd

Public bug reported:

The software app froze while updating, and now whenever I try to install
or update anything I get a message saying I need to run dpkg --configure
-a first, but terminal freezes when I try to run it.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: software-properties-gtk 0.96.20.5
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Wed Jun 28 03:31:28 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-06-27 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: software-properties
Title: package software-properties-gtk 0.96.20.5 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package software-properties-gtk 0.96.20.5 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in software-properties package in Ubuntu:
  New

Bug description:
  The software app froze while updating, and now whenever I try to
  install or update anything I get a message saying I need to run dpkg
  --configure -a first, but terminal freezes when I try to run it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.20.5
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun 28 03:31:28 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-06-27 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: software-properties
  Title: package software-properties-gtk 0.96.20.5 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/software-properties/+bug/1700854/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

Here's a request asking for gnome-control-center to warn somehow when
the Synaptics driver is in use:

https://bugzilla.gnome.org/show_bug.cgi?id=784266

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

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686081/+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 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution

This bug was fixed in the package cloud-init - 0.7.9-197-gebc9ecbc-
0ubuntu1

---
cloud-init (0.7.9-197-gebc9ecbc-0ubuntu1) artful; urgency=medium

  * debian/control: add build dependency python3-jsonschema (LP: #1695318)
  * New upstream snapshot.
- Azure: Add network-config, Refactor net layer to handle duplicate macs.
  [Ryan Harper]
- Tests: Simplify the check on ssh-import-id [Joshua Powers]
- tests: update ntp tests after sntp added [Joshua Powers]
- FreeBSD: Make freebsd a variant, fix unittests and
  tools/build-on-freebsd.
- FreeBSD: fix test failure
- FreeBSD: replace ifdown/ifup with "ifconfig down" and "ifconfig up".
  [Hongjiang Zhang] (LP: #1697815)
- FreeBSD: fix cdrom mounting failure if /mnt/cdrom/secure did not exist.
  [Hongjiang Zhang] (LP: #1696295)
- main: Don't use templater to format the welcome message
  [Andrew Jorgensen]
- docs: Automatically generate module docs form schema if present.
  [Chad Smith]
- debian: fix path comment in /etc/hosts template.
  [Jens Sandmann] (LP: #1606406)
- suse: add hostname and fully qualified domain to template.
  [Jens Sandmann]
- write_file(s): Print permissions as octal, not decimal [Andrew Jorgensen]
- ci deps: Add --test-distro to read-dependencies to install all deps
  [Chad Smith]
- tools/run-centos: cleanups and move to using read-dependencies
- pkg build ci: Add make ci-deps- target to install pkgs
  [Chad Smith]
- systemd: make cloud-final.service run before apt daily services.
  (LP: #1693361)
- selinux: Allow restorecon to be non-fatal. [Ryan Harper] (LP: #1686751)
- net: Allow netinfo subprocesses to return 0 or 1.
  [Ryan Harper] (LP: #1686751)
- net: Allow for NetworkManager configuration [Ryan McCabe] (LP: #1693251)
- Use distro release version to determine if we use systemd in redhat spec
  [Ryan Harper]
- net: normalize data in network_state object
- Integration Testing: tox env, pyxld 2.2.3, and revamp framework
  [Wesley Wiedenmeier]
- Chef: Update omnibus url to chef.io, minor doc changes. [JJ Asghar]
- tools: add centos scripts to build and test [Joshua Powers]
- Drop cheetah python module as it is not needed by trunk [Ryan Harper]
- rhel/centos spec cleanups.
- cloud.cfg: move to a template.  setup.py changes along the way.
- Makefile: add deb-src and srpm targets. use PYVER more places.
- makefile: fix python 2/3 detection in the Makefile [Chad Smith]
- snap: Removing snapcraft plug line [Joshua Powers] (LP: #1695333)
- RHEL/CentOS: Fix default routes for IPv4/IPv6 configuration.
  [Andreas Karis] (LP: #1696176)
- test: Fix pyflakes complaint of unused import.
  [Joshua Powers] (LP: #1695918)
- NoCloud: support seed of nocloud from smbios information
  [Vladimir Pouzanov] (LP: #1691772)
- net: when selecting a network device, use natural sort order
  [Marc-Aurèle Brothier]
- fix typos and remove whitespace in various docs [Stephan Telling]
- systemd: Fix typo in comment in cloud-init.target. [Chen-Han Hsiao]
- Tests: Skip jsonschema related unit tests when dependency is absent.
  [Chad Smith] (LP: #1695318)
- azure: remove accidental duplicate line in merge.
- azure: identify platform by well known value in chassis asset tag.
  [Chad Smith] (LP: #1693939)
- tools/net-convert.py: support old cloudinit versions by using kwargs.
- ntp: Add schema definition and passive schema validation.
  [Chad Smith] (LP: #1692916)
- Fix eni rendering for bridge params that require repeated key for values.
  [Ryan Harper]
- net: remove systemd link file writing from eni renderer [Ryan Harper]
- AliYun: Enable platform identification and enable by default.
  [Junjie Wang] (LP: #1638931)

 -- Scott Moser   Tue, 27 Jun 2017 17:18:24 -0400

** Changed in: cloud-init (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/1693361

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-
  daily.service execution

Status in APT:
  Confirmed
Status in cloud-init:
  Confirmed
Status in apt package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  apt-daily is now a systemd service rather than being invoked by
  cron.daily.  If one builds a custom AMI it is possible that the apt-
  daily.timer will fire during boot.  This can fire at the same time
  cloud-init is running and if cloud-init loses

[Touch-packages] [Bug 1700286] Re: package libqt5test5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar config

2017-06-27 Thread whysea

same here

Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
The following packages have been kept back:
  libmirclient9 libmirclient9:i386
The following packages will be upgraded:
  libqt5test5
1 to upgrade, 0 to newly install, 0 to remove and 2 not to upgrade.
Need to get 0 B/84.5 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 616616 files and directories currently installed.)
Preparing to unpack .../libqt5test5_5.5.1+dfsg-16ubuntu7.5_amd64.deb ...
dpkg: error processing archive 
/var/cache/apt/archives/libqt5test5_5.5.1+dfsg-16ubuntu7.5_amd64.deb (--unpack):
 read error in '/var/lib/dpkg/info/libqt5test5:amd64.triggers': Is a directory
Errors were encountered while processing:
 /var/cache/apt/archives/libqt5test5_5.5.1+dfsg-16ubuntu7.5_amd64.deb
E: Problem renaming the file /var/lib/apt/extended_states.2lovgO to 
/var/lib/apt/extended_states - rename (21: Is a directory)
E: Read error - read (21: Is a directory)
E: Read error - read (21: Is a directory)
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package libqt5test5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to
  install/upgrade: O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.

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

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqt5test5:amd64 5.5.1+dfsg-16ubuntu7.5
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 24 16:37:10 2017
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2017-06-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: qtbase-opensource-src
  Title: package libqt5test5:amd64 5.5.1+dfsg-16ubuntu7.5 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1700286/+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 1700848] [NEW] Install mesa-utils-extra by default

Public bug reported:

Since Ubuntu 16.10, mesa-utils has been installed by default (I think this is 
because libqt5gui5 Recommends: mesa-utils). mesa-utils provides these binaries:
glxdemo
glxgears
glxheads
glxinfo

For 17.10, Ubuntu plans to switch to GNOME on Wayland as default (or at least 
installed by default desktop). glxgears can run in GNOME on Wayland but it is 
running under XWayland instead of using native Wayland. mesa-utils-extras 
provides these binaries:
es2_info
es2gears_wayland
es2gears_x11
es2tri
(By the way, es2gears is symlinked to es2gears_x11).

So if a user wants to test whether Wayland is running successfully, they
can try to run es2gears_wayland. If Wayland is not running, the app will
not start.

Therefore, I propose that we install the minimal mesa-utils-extra by
default as a fun troubleshooting tool. mesa-utils-extra is built from
the same source as mesa-utils (mesa-demos) so all we need is to add this
as a Recommends from ubuntu-desktop.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: artful wayland

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

Title:
  Install mesa-utils-extra by default

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Since Ubuntu 16.10, mesa-utils has been installed by default (I think this is 
because libqt5gui5 Recommends: mesa-utils). mesa-utils provides these binaries:
  glxdemo
  glxgears
  glxheads
  glxinfo

  For 17.10, Ubuntu plans to switch to GNOME on Wayland as default (or at least 
installed by default desktop). glxgears can run in GNOME on Wayland but it is 
running under XWayland instead of using native Wayland. mesa-utils-extras 
provides these binaries:
  es2_info
  es2gears_wayland
  es2gears_x11
  es2tri
  (By the way, es2gears is symlinked to es2gears_x11).

  So if a user wants to test whether Wayland is running successfully,
  they can try to run es2gears_wayland. If Wayland is not running, the
  app will not start.

  Therefore, I propose that we install the minimal mesa-utils-extra by
  default as a fun troubleshooting tool. mesa-utils-extra is built from
  the same source as mesa-utils (mesa-demos) so all we need is to add
  this as a Recommends from ubuntu-desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700848/+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 1667407] Reminder of SRU verification policy change

Thank you for taking the time to verify this stable release fix.  We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags (i.e. verification-done-$RELEASE).  Please remove the
verification-done tag and add one for the release you have tested the
package in.  Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

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

Title:
   improve 2x-3x sha256sum performance on ppc64le due to current gcc
  optimization bug

Status in coreutils package in Ubuntu:
  Fix Released
Status in coreutils source package in Xenial:
  Fix Committed
Status in coreutils source package in Yakkety:
  Fix Released
Status in coreutils package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Performance drop of 2x-3x on ppc64le when using sha256sum

   * Please backport this bug to last LTS as this application is widely
  used.

   * This fix is due to a optimization issue found on gcc v4.9 to gcc
  v7.0.

  [Test Case]

   * Run sha256sum with a big file and measure the time it takes. The
  patch improves this timing up to 3 times faster.

  [Regression Potential]

   * This patch is specifically for the sha256.o object, affecting only
  this binary.

  [Other Info]

  Michael Stone's improved patch:

  Index: coreutils-8.26/Makefile.in
  ===
  --- coreutils-8.26.orig/Makefile.in 2016-11-30 13:34:55.0 -0500
  +++ coreutils-8.26/Makefile.in  2017-02-22 07:18:55.352394058 -0500
  @@ -14661,6 +14661,10 @@

  $(TEST_LOGS): $(PROGRAMS)

  +ifeq ($(DEB_TARGET_ARCH), ppc64el)
  +lib/sha256.o: CFLAGS+=-fno-schedule-insns
  +endif
  +
  # Tell versions [3.59,3.63) of GNU make to not export all variables.
  # Otherwise a system limit (for SysV at least) may be exceeded.
  .NOEXPORT:

  Original bug description:
   
  The sha256sum provided by coreutils (without openssl) is performing
  poorly with gcc versions >= 4.9 until 7.0 (currently under development).
  The reason for that is the -fschedule-insns optimization that is used
  with -O2. By simply deactivating it, there is a performance improvement
  of 2 to 3 times.

  I'm using Ubuntu 16.10 and the coreutils package version
  8.25-2ubuntu2.

  Please check the following closed debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854053

  Be aware of the following conditions that are required:
  * If ppc64le
  * If gcc being used is >= 4.9 and < 7.0

  Notes:
  1) gcc-7 is not affected by this bug (verified on 20170129 snapshot).
  2) clang is not affected by this bug (verified on v3.8 and v3.9).
  3) strangely the sha512 is not affected by this.

  Below a demonstration of how it performs on my POWER8 machine:

  ===
  $ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
  configure: WARNING: libacl development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without ACL support.
  configure: WARNING: libattr development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without xattr support.
  configure: WARNING: libcap library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without capability support.
  configure: WARNING: libgmp development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without GMP support.
  src/who.c: In function 'print_user':
  src/who.c:454:20: warning: initialization discards 'const' qualifier from 
pointer target type [-Wdiscarded-qualifiers]
   int   *a = utmp_ent->ut_addr_v6;
  ^~~~
  d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e  
/home/gut/ubuntu-16.10-server-ppc64el.iso

  real0m18.670s
  user0m16.566s
  sys 0m0.745s

  $ # now with the following patch: ## Check Michael Stone's patch for an 
improved version.
  $ diff Makefile.in ../Makefile.in
  8989c8989
  < @am__fastdepCC_TRUE@  $(COMPILE) -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ 
$< &&\
  ---
  > @am__fastdepCC_TRUE@  $(COMPILE) $$([ "$@" == "lib/sha256.o" ] && echo 
"-fno-schedule-insns") -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ $< &&\
  $ cp ../Makefile.in Makefile.in
  $ (./configure && make -j9) > /dev/null && time src/sha256sum 
~/ubuntu-16.10-server-ppc64el.iso
  configure: WARNING: libacl development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built without ACL support.
  configure: WARNING: libattr development library was not found or not usable.
  configure: WARNING: GNU coreutils will be built

[Touch-packages] [Bug 1700812] Re: pam_cap is provided by the libpam-cap package on x86_64 xenial

2017-06-27 Thread Serge Hallyn

@mattofak - thanks for filing the bug.  I've linked it to the manpage
project.  It'll get fixed.

** Also affects: ubuntu-manpage-repository
   Importance: Undecided
   Status: New

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

Title:
  pam_cap is provided by the libpam-cap package on x86_64 xenial

Status in Ubuntu Manpage Repository:
  New
Status in libcap2 package in Ubuntu:
  New

Bug description:
  The man page for pam_cap
  (http://manpages.ubuntu.com/manpages/xenial/man8/pam_cap.8.html)
  claims that it is provided by the libcap2-bin package. This is
  incorrect, it is actually provided by the libpam-cap package (which is
  recommended by libcap2-bin.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1700812/+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 1700812] Re: pam_cap is provided by the libpam-cap package on x86_64 xenial

2017-06-27 Thread Matthew Walker

"So if this is a bug, it is a bug against manpages.ubuntu.com."
Yes, I misspoke. To clarify I'm used to seeing the "provided by" link on 
manpages.ubuntu.com to link to the package I need to install to get the thing 
the man page references. That may just be a false association though.

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

Title:
  pam_cap is provided by the libpam-cap package on x86_64 xenial

Status in libcap2 package in Ubuntu:
  New

Bug description:
  The man page for pam_cap
  (http://manpages.ubuntu.com/manpages/xenial/man8/pam_cap.8.html)
  claims that it is provided by the libcap2-bin package. This is
  incorrect, it is actually provided by the libpam-cap package (which is
  recommended by libcap2-bin.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700812/+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 1692127] Please test proposed package

Hello Brian, or anyone else affected,

Accepted apport into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.5 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

Title:
  duplicate signature for Package problems can be too short

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

Bug description:
  [Impact]
  apport is creating a shorter than appropriate duplicate signature in 
apport-package bug reports which can lead to misconsolidation and confused 
developers.

  [Test Case]
  1) Boot a system with an old kernel installed or a freshly installed system
  2) edit /etc/default/grub and replace a ` with a '
  3) Upgrade the kernel, watch it crash
  4) Discover a crash report with a DuplicateSignature whose 2nd line starts 
with "Examining"

  With the version of the package from -proposed the DuplicateSignature
  in this case should really have a 2nd line that starts with 'Setting
  up linux-image* ...'. While in this particular case not much is lost
  in other cases valuable information will be missing.

  [Regression Potential]
  The code change is correct and has been tested in artful, additionally I'm 
using the same regular expression to clean up apport-package reports as they 
come in to LP. The only risk here is a typo in the patch that would cause the 
hook (the change is in the ubuntu general hook) to error out which apport would 
handle gracefully and we just wouldn't have a DuplicateSignature.

  [The Original Description]
  Steve brought up bug 1691983 and how it's duplicate signature is missing 
information.  It contains:

  package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Running in non-interactive mode, doing nothing.
  dpkg: error processing package shim-signed (--configure):
   subprocess installed post-installation script returned error exit status 1

  But is missing:

  Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  debconf: unable to initialize frontend: Passthrough
  debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket: 
Connection refused at (eval 18) line 3.)
  debconf: falling back to frontend: Noninteractive

  This is because of the following code in data/general-hooks/ubuntu.py:

  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 'Unpacking', 'Would remove')
  149 for line in termlog.split('\n'):
  150 if line.startswith(PKG_MSGS):
  151 dupe_sig = '%s\n' % line
  152 continue

  The shim-signed package prints a line starts with "Installing " and
  that matches PKG_MSGS so we reset the dupe_sig because that's a
  message we'd expect from a package manager.

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

Hello Brian, or anyone else affected,

Accepted apport into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.3 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

Title:
  duplicate signature for Package problems can be too short

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

Bug description:
  [Impact]
  apport is creating a shorter than appropriate duplicate signature in 
apport-package bug reports which can lead to misconsolidation and confused 
developers.

  [Test Case]
  1) Boot a system with an old kernel installed or a freshly installed system
  2) edit /etc/default/grub and replace a ` with a '
  3) Upgrade the kernel, watch it crash
  4) Discover a crash report with a DuplicateSignature whose 2nd line starts 
with "Examining"

  With the version of the package from -proposed the DuplicateSignature
  in this case should really have a 2nd line that starts with 'Setting
  up linux-image* ...'. While in this particular case not much is lost
  in other cases valuable information will be missing.

  [Regression Potential]
  The code change is correct and has been tested in artful, additionally I'm 
using the same regular expression to clean up apport-package reports as they 
come in to LP. The only risk here is a typo in the patch that would cause the 
hook (the change is in the ubuntu general hook) to error out which apport would 
handle gracefully and we just wouldn't have a DuplicateSignature.

  [The Original Description]
  Steve brought up bug 1691983 and how it's duplicate signature is missing 
information.  It contains:

  package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Running in non-interactive mode, doing nothing.
  dpkg: error processing package shim-signed (--configure):
   subprocess installed post-installation script returned error exit status 1

  But is missing:

  Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  debconf: unable to initialize frontend: Passthrough
  debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket: 
Connection refused at (eval 18) line 3.)
  debconf: falling back to frontend: Noninteractive

  This is because of the following code in data/general-hooks/ubuntu.py:

  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 'Unpacking', 'Would remove')
  149 for line in termlog.split('\n'):
  150 if line.startswith(PKG_MSGS):
  151 dupe_sig = '%s\n' % line
  152 continue

  The shim-signed package prints a line starts with "Installing " and
  that matches PKG_MSGS so we reset the dupe_sig because that's a
  message we'd expect from a package manager.

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

Hello Brian, or anyone else affected,

Accepted apport into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.1-0ubuntu2.8 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

Title:
  duplicate signature for Package problems can be too short

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

Bug description:
  [Impact]
  apport is creating a shorter than appropriate duplicate signature in 
apport-package bug reports which can lead to misconsolidation and confused 
developers.

  [Test Case]
  1) Boot a system with an old kernel installed or a freshly installed system
  2) edit /etc/default/grub and replace a ` with a '
  3) Upgrade the kernel, watch it crash
  4) Discover a crash report with a DuplicateSignature whose 2nd line starts 
with "Examining"

  With the version of the package from -proposed the DuplicateSignature
  in this case should really have a 2nd line that starts with 'Setting
  up linux-image* ...'. While in this particular case not much is lost
  in other cases valuable information will be missing.

  [Regression Potential]
  The code change is correct and has been tested in artful, additionally I'm 
using the same regular expression to clean up apport-package reports as they 
come in to LP. The only risk here is a typo in the patch that would cause the 
hook (the change is in the ubuntu general hook) to error out which apport would 
handle gracefully and we just wouldn't have a DuplicateSignature.

  [The Original Description]
  Steve brought up bug 1691983 and how it's duplicate signature is missing 
information.  It contains:

  package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Running in non-interactive mode, doing nothing.
  dpkg: error processing package shim-signed (--configure):
   subprocess installed post-installation script returned error exit status 1

  But is missing:

  Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  debconf: unable to initialize frontend: Passthrough
  debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket: 
Connection refused at (eval 18) line 3.)
  debconf: falling back to frontend: Noninteractive

  This is because of the following code in data/general-hooks/ubuntu.py:

  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 'Unpacking', 'Would remove')
  149 for line in termlog.split('\n'):
  150 if line.startswith(PKG_MSGS):
  151 dupe_sig = '%s\n' % line
  152 continue

  The shim-signed package prints a line starts with "Installing " and
  that matches PKG_MSGS so we reset the dupe_sig because that's a
  message we'd expect from a package manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1692127/+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 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just

Of course, this would be adding complexity instead of removing it, but
it might be worth doing an "ntpdate -q" first, parsing the output, and
if the offset is "large enough" (whatever that might be), do the
stop/ntpdate/start dance, else exit.

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

Title:
  ntpdate startup routine prevents ntp service from launching up on
  Ubuntu 16.04 server on system boot; manually starting ntp service
  works: [FIX in DESCRIPTION], just need to apply it and release a new
  version

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Trusty:
  In Progress
Status in ntp source package in Xenial:
  In Progress
Status in ntp source package in Yakkety:
  In Progress
Status in ntp source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * Fixes several broken cases, those are:
   * Case 1 - ntp configured to drift time slowly, but time jumping
   - ntp is running and drifts time towards a target being way off
   - an interface comes up
   - stop ntpd
   - warp time via ntpdate-debian (static interfaces will even set -b)
   - (re-)start ntpd
   - if users relied on non-time warp they are now in trouble

   * Case 2 - ntp start/stop storms
   - ntpd comes up normally
   - the admin brings interfaces up/down rather often
   - ntp is restarted very very often due to this for no reason
   => reason for bugs like debian 823533

   * Case 3 - unintentional enablement of ntp
   - ntpd is installed but disabled (for whatever reason)
   - all is fine on any ifup/down
   - one installs ntpdate, maybe even without realizing due to a depends
   - now on the next ifup ntpd (or openntpd) will be started

   * Solution, drop the broken Delta

  [Test Case]

   * Testing Case 2/3 as it is the easiest, case 1 needs a more complex 
 setup to cause the time drift but otherwise works the same way.
 - install ntp and ntpdate
 - stop ntp
 - ifup/ifdown an interface multiple times; as simplification you can 
   also call /etc/network/if-up.d/ntpdate directly (not that this 
   spawns the change asnchronous and locks concurrency, so do that a 
   few times over the time of a minute or so)
 - the service of ntp should still be stopped and not report plenty of 
   restarts

  
  [Regression Potential] 

   * It improves a lot of cases (otherwise we wouldn't SRU), but there is 
 one regression potential I can see:

 - users that relied on starting NTP later on after other interfaces 
   got up due to that code in ntpdate which did that as a side effect. 
   But that is outweigh by Case2/3 for the majority of users. And even 
   Case1 only hits this potential regression on e.g. late network 
   intialization, but in that case please remind that the default 
   (systemd timedatectl) would handle that.

 - Since most users of ntp do not install ntpdate (which doesn't work 
   when ntp is active) we should be rather safe to assume that almost 
   no one should rely on that side effect.

 - Furthermore this is a Ubuntu Delta for very long, cause issues (see 
   the references on the git commit) but never made it into Debian - 
   in that sense another indicator it isn't an important delta to 
   have.

  [Other Info]
   
   * The original intention "what if net is available too late" fixed 
 correctly would not be part of ntpdate, but ntp and additionally 
 check if it is actually meant to be enabled - but I never seen/heard 
 of any of it since systemd is around - maybe new ordering mostly 
 avoids the original issue.


  ---

  
  I've installed ntp service on the clean ubuntu 16.04 server system. 
Configured it. Checked that it works, but, after reboot, it doesn't start 
automatically.
  When I check: 'systemctl is-enabled ntp', it shows enabled.
  If I manually start it 'systemctl start ntp' it starts just fine and woks 
correctly,
  but until I manually start it, 'systemctl status ntp' shows:

  Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
  Active: inactive (deadi)

  Installed 1.29ubuntu2 version of init-systems-helper, but it didn't
  fix the problem.

  Found a bugreport on ntpd package:

  https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596

  led to solution that involves a change to be made in file:

  /etc/network/if-up.d/ntpdate

  of ntpdate package

  After changing from:
  __CODE_START__

  invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :

  invoke-rc.d --quiet $service start >/dev/null 2>&1 || true

  __CODE_END__

  to:

[Touch-packages] [Bug 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just

So, the one regression I see possible here is on machines with
lousy/broken clocks at boot time.  If you start ntpd with a clock too
far in the past/future, it'll either give up and exit (if VERY far off)
or start a drift that could take hours/days to correct.  If you remove
the restarting around ntpdate, ntpdate will refuse to fix the clock (due
to the socket being in use), and you're stuck either with a dead ntpd,
or a drift of doom.

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

Title:
  ntpdate startup routine prevents ntp service from launching up on
  Ubuntu 16.04 server on system boot; manually starting ntp service
  works: [FIX in DESCRIPTION], just need to apply it and release a new
  version

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Trusty:
  In Progress
Status in ntp source package in Xenial:
  In Progress
Status in ntp source package in Yakkety:
  In Progress
Status in ntp source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * Fixes several broken cases, those are:
   * Case 1 - ntp configured to drift time slowly, but time jumping
   - ntp is running and drifts time towards a target being way off
   - an interface comes up
   - stop ntpd
   - warp time via ntpdate-debian (static interfaces will even set -b)
   - (re-)start ntpd
   - if users relied on non-time warp they are now in trouble

   * Case 2 - ntp start/stop storms
   - ntpd comes up normally
   - the admin brings interfaces up/down rather often
   - ntp is restarted very very often due to this for no reason
   => reason for bugs like debian 823533

   * Case 3 - unintentional enablement of ntp
   - ntpd is installed but disabled (for whatever reason)
   - all is fine on any ifup/down
   - one installs ntpdate, maybe even without realizing due to a depends
   - now on the next ifup ntpd (or openntpd) will be started

   * Solution, drop the broken Delta

  [Test Case]

   * Testing Case 2/3 as it is the easiest, case 1 needs a more complex 
 setup to cause the time drift but otherwise works the same way.
 - install ntp and ntpdate
 - stop ntp
 - ifup/ifdown an interface multiple times; as simplification you can 
   also call /etc/network/if-up.d/ntpdate directly (not that this 
   spawns the change asnchronous and locks concurrency, so do that a 
   few times over the time of a minute or so)
 - the service of ntp should still be stopped and not report plenty of 
   restarts

  
  [Regression Potential] 

   * It improves a lot of cases (otherwise we wouldn't SRU), but there is 
 one regression potential I can see:

 - users that relied on starting NTP later on after other interfaces 
   got up due to that code in ntpdate which did that as a side effect. 
   But that is outweigh by Case2/3 for the majority of users. And even 
   Case1 only hits this potential regression on e.g. late network 
   intialization, but in that case please remind that the default 
   (systemd timedatectl) would handle that.

 - Since most users of ntp do not install ntpdate (which doesn't work 
   when ntp is active) we should be rather safe to assume that almost 
   no one should rely on that side effect.

 - Furthermore this is a Ubuntu Delta for very long, cause issues (see 
   the references on the git commit) but never made it into Debian - 
   in that sense another indicator it isn't an important delta to 
   have.

  [Other Info]
   
   * The original intention "what if net is available too late" fixed 
 correctly would not be part of ntpdate, but ntp and additionally 
 check if it is actually meant to be enabled - but I never seen/heard 
 of any of it since systemd is around - maybe new ordering mostly 
 avoids the original issue.


  ---

  
  I've installed ntp service on the clean ubuntu 16.04 server system. 
Configured it. Checked that it works, but, after reboot, it doesn't start 
automatically.
  When I check: 'systemctl is-enabled ntp', it shows enabled.
  If I manually start it 'systemctl start ntp' it starts just fine and woks 
correctly,
  but until I manually start it, 'systemctl status ntp' shows:

  Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
  Active: inactive (deadi)

  Installed 1.29ubuntu2 version of init-systems-helper, but it didn't
  fix the problem.

  Found a bugreport on ntpd package:

  https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596

  led to solution that involves a change to be made in file:

  /etc/network/if-up.d/ntpdate

  of ntpdate package

  After changing from:
  __CODE_START__

  invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock

[Touch-packages] [Bug 1700575] DuplicateSignature.txt

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

Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!

** Attachment added: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1700575/+attachment/4904249/+files/DuplicateSignature.txt

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

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in debconf package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-bug linux

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christian   1663 F pulseaudio
   /dev/snd/controlC0:  christian   1663 F pulseaudio
  Date: Mon Jun 26 09:28:06 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=da3b5f50-3a7e-40b3-b995-0381c39404e2
  InstallationDate: Installed on 2017-02-22 (124 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   enp8s1no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=36459dff-9f3e-4159-83fb-08a8d588af67 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0311
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55-M
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1700575/+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 1700659] DuplicateSignature.txt

Due to a bug in apport's method for creating a duplicate signature, the
DuplicateSignature in this report was incorrect. We are fixing that now,
sorry for the noise!

** Attachment added: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1700659/+attachment/4904250/+files/DuplicateSignature.txt

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

Title:
  package gtk-update-icon-cache (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 2

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  after upgrade system to ubuntu 17.x.x dpkg packs close with
  uncontables errors, after reboot system didn't started sucessfully.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gtk-update-icon-cache (not installed)
  Uname: Linux 4.11.7-041107-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon Jun 26 18:34:05 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  InstallationDate: Installed on 2016-10-05 (264 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gtk+3.0
  Title: package gtk-update-icon-cache (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1700659/+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 1700575] Re: package linux-image-4.4.0-81-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

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

** Attachment removed: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1700575/+attachment/4903626/+files/DuplicateSignature.txt

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

Title:
  package linux-image-4.4.0-81-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in debconf package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-bug linux

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-81-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christian   1663 F pulseaudio
   /dev/snd/controlC0:  christian   1663 F pulseaudio
  Date: Mon Jun 26 09:28:06 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=da3b5f50-3a7e-40b3-b995-0381c39404e2
  InstallationDate: Installed on 2017-02-22 (124 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   enp8s1no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic 
root=UUID=36459dff-9f3e-4159-83fb-08a8d588af67 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.11
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-81-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0311
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55-M
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0311:bd11/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1700575/+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 1700670] package systemd 229-4ubuntu4 failed to install/upgrade: unable to make backup link of './bin/journalctl' before installing new version: Input/output error

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

DuplicateSignature:
 Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
 Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
 dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
  unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error

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

Title:
  package systemd 229-4ubuntu4 failed to install/upgrade: unable to make
  backup link of './bin/journalctl' before installing new version:
  Input/output error

Status in systemd package in Ubuntu:
  New

Bug description:
  internal system error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Jun 26 22:58:19 2017
  DpkgTerminalLog:
   Preparing to unpack .../systemd_229-4ubuntu17_amd64.deb ...
   Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
  DuplicateSignature:
   Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
  ErrorMessage: unable to make backup link of './bin/journalctl' before 
installing new version: Input/output error
  JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', 
'--lines=1000'] failed with exit code -7:
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: Hewlett-Packard p6719c
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Title: package systemd 229-4ubuntu4 failed to install/upgrade: unable to make 
backup link of './bin/journalctl' before installing new version: Input/output 
error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.11
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: MXX1070J1T
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6719c:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6719c
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700670/+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 1700659] Re: package gtk-update-icon-cache (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 2

** Attachment removed: "DuplicateSignature.txt"
   
https://bugs.launchpad.net/bugs/1700659/+attachment/4903799/+files/DuplicateSignature.txt

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

Title:
  package gtk-update-icon-cache (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 2

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  after upgrade system to ubuntu 17.x.x dpkg packs close with
  uncontables errors, after reboot system didn't started sucessfully.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gtk-update-icon-cache (not installed)
  Uname: Linux 4.11.7-041107-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon Jun 26 18:34:05 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 2
  InstallationDate: Installed on 2016-10-05 (264 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gtk+3.0
  Title: package gtk-update-icon-cache (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1700659/+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 1700826] [NEW] please include numactl on the ubuntu-server iso

2017-06-27 Thread dann frazier

Public bug reported:

I've submitted an MIR for the numactl binary package at: LP: #1700824.
Assuming that is approved, please also include this on the server seed, which I 
believe is necessary for it to appear on the ubuntu-server ISOs.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-meta (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-meta (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-meta (Ubuntu Yakkety)

** No longer affects: ubuntu-meta (Ubuntu Xenial)

** No longer affects: ubuntu-meta (Ubuntu Zesty)

** Also affects: ubuntu-meta (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  please include numactl on the ubuntu-server iso

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Xenial:
  New

Bug description:
  I've submitted an MIR for the numactl binary package at: LP: #1700824.
  Assuming that is approved, please also include this on the server seed, which 
I believe is necessary for it to appear on the ubuntu-server ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+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 1673612] Re: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

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

** This bug has been marked a duplicate of bug 1693226
   Break the conflicts with click the optparser

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

Title:
  package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to
  install/upgrade: subprocess installed pre-removal script returned
  error exit status 1

Status in click package in Ubuntu:
  Confirmed

Bug description:
  This happened in the automatic package update initiated by the system.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar 16 14:08:31 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-04-05 (345 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: click
  Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: Upgraded to yakkety on 2017-03-09 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1673612/+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 1700211] Re: package linux-firmware 1.157.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-06-27 Thread Seth Forshee

E: /usr/share/initramfs-tools/hooks/casper-memdisk failed with return 1.

This seems to be related to an initramfs hook for casper, so marking
this bug as also affecting casper.

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

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

Title:
  package linux-firmware 1.157.11 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in casper package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Unable to upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.11
  ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 24 09:21:25 2017
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-19 (124 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.11 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-06-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1700211/+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 1700820] Re: package gstreamer1.0-plugins-base:i386 (not installed) failed to install/upgrade: no package named 'gstreamer1.0-plugins-base:i386' is installed, cannot configure

2017-06-27 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package gstreamer1.0-plugins-base:i386 (not installed) failed to
  install/upgrade: no package named 'gstreamer1.0-plugins-base:i386' is
  installed, cannot configure

Status in gst-plugins-base1.0 package in Ubuntu:
  New

Bug description:
  it happened after 14.04 to 16.04 upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gstreamer1.0-plugins-base:i386 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 27 21:21:17 2017
  DuplicateSignature:
   package:gstreamer1.0-plugins-base:i386:(not installed)
   Setting up libopus0:amd64 (1.1.2-1ubuntu1) ...
   dpkg: error processing package libopus0:i386 (--configure):
no package named 'libopus0:i386' is installed, cannot configure
  ErrorMessage: no package named 'gstreamer1.0-plugins-base:i386' is installed, 
cannot configure
  InstallationDate: Installed on 2013-08-26 (1400 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gst-plugins-base1.0
  Title: package gstreamer1.0-plugins-base:i386 (not installed) failed to 
install/upgrade: no package named 'gstreamer1.0-plugins-base:i386' is 
installed, cannot configure
  UpgradeStatus: Upgraded to xenial on 2017-06-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1700820/+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 1700820] [NEW] package gstreamer1.0-plugins-base:i386 (not installed) failed to install/upgrade: no package named 'gstreamer1.0-plugins-base:i386' is installed, cannot configure

2017-06-27 Thread Sezer Yalcin

Public bug reported:

it happened after 14.04 to 16.04 upgrade.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gstreamer1.0-plugins-base:i386 (not installed)
ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
Uname: Linux 4.4.0-81-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue Jun 27 21:21:17 2017
DuplicateSignature:
 package:gstreamer1.0-plugins-base:i386:(not installed)
 Setting up libopus0:amd64 (1.1.2-1ubuntu1) ...
 dpkg: error processing package libopus0:i386 (--configure):
  no package named 'libopus0:i386' is installed, cannot configure
ErrorMessage: no package named 'gstreamer1.0-plugins-base:i386' is installed, 
cannot configure
InstallationDate: Installed on 2013-08-26 (1400 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: gst-plugins-base1.0
Title: package gstreamer1.0-plugins-base:i386 (not installed) failed to 
install/upgrade: no package named 'gstreamer1.0-plugins-base:i386' is 
installed, cannot configure
UpgradeStatus: Upgraded to xenial on 2017-06-27 (0 days ago)

** Affects: gst-plugins-base1.0 (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 gst-plugins-base1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1700820

Title:
  package gstreamer1.0-plugins-base:i386 (not installed) failed to
  install/upgrade: no package named 'gstreamer1.0-plugins-base:i386' is
  installed, cannot configure

Status in gst-plugins-base1.0 package in Ubuntu:
  New

Bug description:
  it happened after 14.04 to 16.04 upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gstreamer1.0-plugins-base:i386 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 27 21:21:17 2017
  DuplicateSignature:
   package:gstreamer1.0-plugins-base:i386:(not installed)
   Setting up libopus0:amd64 (1.1.2-1ubuntu1) ...
   dpkg: error processing package libopus0:i386 (--configure):
no package named 'libopus0:i386' is installed, cannot configure
  ErrorMessage: no package named 'gstreamer1.0-plugins-base:i386' is installed, 
cannot configure
  InstallationDate: Installed on 2013-08-26 (1400 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gst-plugins-base1.0
  Title: package gstreamer1.0-plugins-base:i386 (not installed) failed to 
install/upgrade: no package named 'gstreamer1.0-plugins-base:i386' is 
installed, cannot configure
  UpgradeStatus: Upgraded to xenial on 2017-06-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1700820/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2017-06-27 Thread bagl0312

Actually it was solved on 17.04 :)

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/comments/82

Enjoy!

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1694730] Re: /etc/update-motd.d/50-motd-news calls home on each ssh connection

2017-06-27 Thread Dominique Belhachemi

Could you please explain why Canonical is tracking user hardware per
default without user consent?

See /etc/update-motd.d/50-motd-news

e.g.
platformn : GNU/Linux/4.4.0-81-generic/x86_64
lsb   : Ubuntu/16.04.2/LTS
arch  : x86_64
cpu   : Intel(R)/Xeon(R)/CPU/E5-2650/0/@/2.00GHz
uptime: 14507.03/14385.03


Why is this hidden behind useless messages like:

 * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
   Keras & React Native on Ubuntu
   - https://ubu.one/HBOubu

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

Title:
  /etc/update-motd.d/50-motd-news calls home on each ssh connection

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  This happens since Ubuntu 17.04 (Zesty)

  Why is /etc/update-motd.d/50-motd-news hitting https://motd.ubuntu.com
  each time I create a SSH connection?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1694730/+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 1699310] Re: Unmet dependancies on 16.04

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

** This bug has been marked a duplicate of bug 1693226
   Break the conflicts with click the optparser

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

Title:
  Unmet dependancies on 16.04

Status in click package in Ubuntu:
  Confirmed

Bug description:
  SInce today I can not install anything in 16.04 due to unmet dependencies 
with click. I'd like to remove it, but that fails: 
  ---
  The following packages will be REMOVED
click*
  0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade.
  3 not fully installed or removed.
  After this operation, 88.1 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 590359 files and directories currently installed.)
  Removing click (0.4.43+16.04.20160203-0ubuntu2) ...
  Traceback (most recent call last):
File "/usr/bin/click", line 37, in 
  import click
  ImportError: No module named 'click'
  dpkg: error processing package click (--purge):
   subprocess installed pre-removal script returned error exit status 1
  Job for click-system-hooks.service failed because the control process exited 
with error code. See "systemctl status click-system-hooks.service" and 
"journalctl -xe" for details.
  click-system-hooks.service couldn't start.
  Errors were encountered while processing:
   click
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ---
  I also often get the following error:
  ---
  The following packages have unmet dependencies.
   click : Depends: python3-click-package (= 0.4.43+16.04.20160203-0ubuntu2) 
but 0.4.43+16.04.20170613-0ubuntu1 is to be installed
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1699310/+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 1699283] Re: package click 0.4.43+16.04.20160203-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

It looks like you've installed click via pip or another python package
system.

Preparing to unpack .../click_0.4.43+16.04.20170613-0ubuntu1_amd64.deb ...
Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.

Please remove click and try the package operation again.

** Changed in: click (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package click 0.4.43+16.04.20160203-0ubuntu3 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  Incomplete

Bug description:
  An update that failed. Many thanks for your great contributions and
  efforts to improve a great product.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click 0.4.43+16.04.20160203-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 20 12:17:04 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-04-01 (445 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: click
  Title: package click 0.4.43+16.04.20160203-0ubuntu3 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/click/+bug/1699283/+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 1700812] [NEW] pam_cap is provided by the libpam-cap package on x86_64 xenial

2017-06-27 Thread Serge Hallyn

Note, the actual manpage makes no mention of the package.  Which is
how it should be, as the manpage comes from upstream and not from
Ubuntu.

So if this is a bug, it is a bug against manpages.ubuntu.com.

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

Title:
  pam_cap is provided by the libpam-cap package on x86_64 xenial

Status in libcap2 package in Ubuntu:
  New

Bug description:
  The man page for pam_cap
  (http://manpages.ubuntu.com/manpages/xenial/man8/pam_cap.8.html)
  claims that it is provided by the libcap2-bin package. This is
  incorrect, it is actually provided by the libpam-cap package (which is
  recommended by libcap2-bin.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700812/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2017-06-27 Thread Silas Brändlin

wow, this was opened in 2013...linux users are really patient! I will
restart my Ubuntu Mate and boot into Win10...where I can use openvpn
config files...pushed dns server...log verbosity...

Pls don't get me wrong...I love linux...but bugs like this one gets me
nuts...2013...wow...even I know to use the command line quite
well...this is not user friendly at all...

peace out!

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  [Triage Notes]

  This bug can no longer make progress. Please see comment 50 for
  details and further instructions.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1700814] [NEW] Default capability of cap_setfcap+i should be set on setcap

2017-06-27 Thread Matthew Walker

Public bug reported:

If I grant a user (via pam_cap) cap_setfcap+i, I would then expect them
to be able to use setcap without sudo. setcap is not provided with any
default file capabilities however, so either the user has to sudo, or I
have to grant the setfcap capability to setcap with setcap.

In my mind, it would be reasonable to grant setfcap+i to setcap by
default on installation.

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

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

Title:
  Default capability of cap_setfcap+i should be set on setcap

Status in libcap2 package in Ubuntu:
  New

Bug description:
  If I grant a user (via pam_cap) cap_setfcap+i, I would then expect
  them to be able to use setcap without sudo. setcap is not provided
  with any default file capabilities however, so either the user has to
  sudo, or I have to grant the setfcap capability to setcap with setcap.

  In my mind, it would be reasonable to grant setfcap+i to setcap by
  default on installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700814/+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 1700812] [NEW] pam_cap is provided by the libpam-cap package on x86_64 xenial

2017-06-27 Thread Matthew Walker

Public bug reported:

The man page for pam_cap
(http://manpages.ubuntu.com/manpages/xenial/man8/pam_cap.8.html) claims
that it is provided by the libcap2-bin package. This is incorrect, it is
actually provided by the libpam-cap package (which is recommended by
libcap2-bin.)

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

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

Title:
  pam_cap is provided by the libpam-cap package on x86_64 xenial

Status in libcap2 package in Ubuntu:
  New

Bug description:
  The man page for pam_cap
  (http://manpages.ubuntu.com/manpages/xenial/man8/pam_cap.8.html)
  claims that it is provided by the libcap2-bin package. This is
  incorrect, it is actually provided by the libpam-cap package (which is
  recommended by libcap2-bin.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1700812/+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 1689825] Re: gnome-keyring not unlocked on boot

2017-06-27 Thread 513G3

For reference... https://github.com/karma-runner/karma-chrome-
launcher/issues/76

** Bug watch added: github.com/karma-runner/karma-chrome-launcher/issues #76
   https://github.com/karma-runner/karma-chrome-launcher/issues/76

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

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

** Also affects: base-files (Ubuntu Artful)
   Importance: High
 Assignee: Dustin Kirkland  (kirkland)
   Status: In Progress

** Also affects: base-files (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: base-files (Ubuntu Zesty)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

** Changed in: base-files (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: base-files (Ubuntu Zesty)
   Importance: Undecided => High

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  In Progress
Status in base-files source package in Zesty:
  In Progress
Status in base-files source package in Artful:
  In Progress

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1691901/+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 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

** Changed in: base-files (Ubuntu)
 Assignee: (unassigned) => Dustin Kirkland  (kirkland)

** Changed in: base-files (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  In Progress
Status in base-files source package in Zesty:
  In Progress
Status in base-files source package in Artful:
  In Progress

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1691901/+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 1694730] Re: /etc/update-motd.d/50-motd-news calls home on each ssh connection

Hi there.  By design, it does not fetch motd.ubuntu.com with every ssh
session.

Rather, there's a systemd timer that runs, asynchronously once about a
minute after boot, and then every 12 hours (plus/minus a random interval
up to an hour).  That systemd timer updates a cache file,
/var/cache/motd, in the background.

At login, it just concatenates the /var/cache/motd file.

Note that it's easy to disable, or change to a different MOTD server, by
editing /etc/default/motd-news.

** Changed in: base-files (Ubuntu)
   Status: Triaged => Opinion

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

Title:
  /etc/update-motd.d/50-motd-news calls home on each ssh connection

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  This happens since Ubuntu 17.04 (Zesty)

  Why is /etc/update-motd.d/50-motd-news hitting https://motd.ubuntu.com
  each time I create a SSH connection?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1694730/+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 1700806] [NEW] systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

2017-06-27 Thread Seth Forshee

Public bug reported:

Testing failed on:
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+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 1589401] Re: cannot view wifi networks after re-enabling wifi

2017-06-27 Thread Douglas H. Silva

Using ath9k driver: no issues

My netbook running iwlwifi driver still has this bug. It's in Ubuntu,
because I'm running Debian Stretch just fine there.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

You can also edit /etc/default/motd-news and:

 a) set ENABLED=0

 b) changed the URL to a custom one that does resolve or work for you

 c) change the time to wait

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1691901/+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 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

By design, the cache file, /var/cache/motd-news, should be populated in
the background by a systemd timer that runs roughly once a day.

If that file is populated, then there should be zero impact on login.

Perhaps the background cache population should create an empty file, if
it can't reach the $URL?

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1691901/+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 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

2017-06-27 Thread Scott Moser

suggested fix is 
 http://paste.ubuntu.com/24964373/

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1691901/+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 1691901] Re: 50-motd-news costs 5 seconds every login on firewalled systems

** Changed in: base-files (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  I noticed quite a long time to login to some of my systems via ssh (or scp).
  Investigating lead me to find out that the '50-motd-news' file
  (/etc/update-motd.d/50-motd-news) was the primary cost.

  In line 108 [1] it does something like:
   curl --connect-timeout "5" --max-time "5" -A "..." -o - 
https://motd.ubuntu.com

  The systems I'm seeing this on are in a lab and do not have access to 
https://motd.ubuntu.com.
  The way the lab is configured, they just end up timing out.  So every scp or 
ssh connection
  or other path to trigger update-motd will cost 5 seconds.

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-motd.d.50-motd-news: 2017-05-19T01:10:25.572110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1691901/+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 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11

** Tags added: patch

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

Title:
  Regression tests cannot write to apparmor path_max module parameter in
  artful/4.11

Status in apparmor package in Ubuntu:
  New

Bug description:
  The longpath regression tests tries to write to
  /sys/module/apparmor/parameters/path_max, but this is read-only in
  artful/4.11:

  commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6
  Author: John Johansen 
  Date:   Thu Apr 6 05:14:20 2017 -0700

  apparmor: Make path_max parameter readonly

  This is causing ADT to fail.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful-canonical-kernel-team-
  ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz

running longpath
longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission 
denied
Fatal Error (longpath): Unexpected shell error. Run with -x to debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+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 1700789] [NEW] LightDM background has no tile effect

2017-06-27 Thread Tomás Antunes

Public bug reported:

I have desktop background set on tile mode but on lightdm login screen
the image is stretched and pixelated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
Uname: Linux 4.4.0-81-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jun 27 17:38:53 2017
InstallationDate: Installed on 2016-08-31 (300 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  LightDM background has no tile effect

Status in lightdm package in Ubuntu:
  New

Bug description:
  I have desktop background set on tile mode but on lightdm login screen
  the image is stretched and pixelated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 27 17:38:53 2017
  InstallationDate: Installed on 2016-08-31 (300 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1700789/+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 1700791] Re: package libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/

2017-06-27 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

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

Status in kmod package in Ubuntu:
  New

Bug description:
  crashes on startup

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libkmod2 22-1.1ubuntu1 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Jun 24 12:48:58 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
  DuplicateSignature:
   package:libkmod2:22-1.1ubuntu1 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
   Unpacking libkmod2:i386 (22-1.1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ObH3ht/10-libkmod2_22-1.1ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other 
instances of package libkmod2:i386
  InstallationDate: Installed on 2014-03-29 (1186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: kmod
  Title: package libkmod2 22-1.1ubuntu1 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is 
different from other instances of package libkmod2:i386
  UpgradeStatus: Upgraded to zesty on 2017-04-27 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1700791/+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 1700791] [NEW] package libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod

2017-06-27 Thread Bugston

Public bug reported:

crashes on startup

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libkmod2 22-1.1ubuntu1 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Sat Jun 24 12:48:58 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2.2
 libgcc1 1:6.3.0-12ubuntu2
DuplicateSignature:
 package:libkmod2:22-1.1ubuntu1 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
 Unpacking libkmod2:i386 (22-1.1ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-ObH3ht/10-libkmod2_22-1.1ubuntu1_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other 
instances of package libkmod2:i386
InstallationDate: Installed on 2014-03-29 (1186 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: kmod
Title: package libkmod2 22-1.1ubuntu1 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is 
different from other instances of package libkmod2:i386
UpgradeStatus: Upgraded to zesty on 2017-04-27 (61 days ago)

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


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

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

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

Status in kmod package in Ubuntu:
  New

Bug description:
  crashes on startup

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libkmod2 22-1.1ubuntu1 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Sat Jun 24 12:48:58 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
  DuplicateSignature:
   package:libkmod2:22-1.1ubuntu1 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
   Unpacking libkmod2:i386 (22-1.1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ObH3ht/10-libkmod2_22-1.1ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other 
instances of package libkmod2:i386
  InstallationDate: Installed on 2014-03-29 (1186 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: kmod
  Title: package libkmod2 22-1.1ubuntu1 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is 
different from other instances of package libkmod2:i386
  UpgradeStatus: Upgraded to zesty on 2017-04-27 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1700791/+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 1218442] Re: IPv6 addresses are lost when an interface is shortly down

2017-06-27 Thread Jan Baranowski

One final note: it seems that problem may be overcame by removing
contents of /run/network just before reboot/shutdown.

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

Title:
  IPv6 addresses are lost when an interface is shortly down

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  /etc/network/interfaces has been configured with IPv4 and IPv6
  addresses on an interface. There are two networks each:

  $ ip -4 addr show dev eth0
  2: eth0:  mtu 1500 qdisc mq state UP 
qlen 1000
  inet 10.1.1.51/24 brd 10.1.1.255 scope global eth0
  inet 10.2.1.51/24 brd 10.2.1.255 scope global eth0

  $ ip -6 addr show dev eth0
  2: eth0:  mtu 1500 qlen 1000
  inet6 :::201::33/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 :::101::33/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80:::aaff:febb:ccdd/64 scope link 
 valid_lft forever preferred_lft forever

  (Global addresses and MAC address anonymized)

  Both are configured within "manual" entries in
  /etc/network/interfaces.

  
  When I turn down eth0 and bring it up again, the result is:

  $ ip -4 addr show dev eth0
  2: eth0:  mtu 1500 qdisc mq state UP 
qlen 1000
  inet 10.1.1.51/24 brd 10.1.1.255 scope global eth0
  inet 10.2.1.51/24 brd 10.2.1.255 scope global eth0

  $ ip -6 addr show dev eth0
  2: eth0:  mtu 1500 qlen 1000
  inet6 fe80:::aaff:febb:ccdd/64 scope link 
 valid_lft forever preferred_lft forever

  That is, the global IPv6 addresses are lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ifupdown 0.7.5ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Thu Aug 29 16:28:46 2013
  InstallationDate: Installed on 2013-08-14 (14 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1218442/+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 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

2017-06-27 Thread spm2011

** Summary changed:

- [Latitude 3340, Realtek ALC3234, Headphone] Static in Headphones While on 
Battery Power
+ [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power

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

Title:
  [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery
  Power

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-06-27 Thread Olivier Tilloy

For future reference, this is the list of upstream commits corresponding
to Aaron's patches, in the order they are being applied:

312cea870dfbc363da44074bd6f56ccd283c5420
  shared: add nm_auto_close and nm_auto_fclose

ed299cc8605a8291a61b3a514f8dc20390b18c77
  device/wwan: use nm_auto_close instead of gs_fd_close

713c74f6e4a88f874cf3e9908b3fb153f2ea5b83
  platform: add a new function nmp_utils_open_sysctl()

e714a20bc2464dc97492731a0d656e8c6bab65aa
  platform: refactor wifi_utils_is_wifi() not to pass sysfs_path

b95556eb781a18ee1c96470f40b9e1e162b0ee60
  platform: wifi: use nmp_utils_open_sysctl() to check if device is wifi

76876e896c242fd82d048743ffcf2c0481442dc5
  platform: refactor nmp_utils_sysctl_open_netdir()

4bdee37771ae741f4f9548b52c1db53ddf080fe8
  all: use O_CLOEXEC for file descriptors

dcc8de16b2acc43b2a9155fcfb91fa2602f3a401
  core: add utils for file handling


As far as I can tell, none of them have been backported to the 1.2 branch of 
NetworkManager.

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project xenial series:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  HOW TO REPRODUCE:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  RESULT:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  WORKAROUND:
  
(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

  SYSTEM INFO:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+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 1646739] Re: "Use of uninitialized value" in debconf via update-manager

Actually, I'm not convinced that update-manager is the front end in use
here. If we look at the JournalErrors.txt file attached to this bug we
can see the following:

dic 02 09:33:40 hostname org.debian.apt[871]: 09:33:40 AptDaemon [INFO]: 
Initializing daemon
dic 02 09:33:40 hostname org.debian.apt[871]: 
/usr/lib/python3/dist-packages/aptdaemon/worker/pkworker.py:35: PyGIWarning: 
PackageKitGlib was imported without specifying a version first. Use 
gi.require_version('PackageKitGlib', '1.0') before import to ensure that the 
right version gets loaded.
dic 02 09:33:40 hostname org.debian.apt[871]:   from gi.repository import 
PackageKitGlib as pk

My testing indicates that these errors only appear in the journal when
gnome-software is being used and not update-manager.

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

Title:
  "Use of uninitialized value" in debconf via update-manager

Status in debconf package in Ubuntu:
  Confirmed
Status in php7.0 package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  During a software upgrade, process was stuck on php7.0-xml
  configuration for 20 minutes, after that I killed the process. I am
  not sure what additional info are required, will be happy to provide
  any.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Fri Dec  2 09:52:06 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-03-11 (265 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: php7.0
  Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1652348] Re: initrd dhcp fails / ignores valid response

This bug was fixed in the package klibc - 2.0.3-0ubuntu1.14.04.3

---
klibc (2.0.3-0ubuntu1.14.04.3) trusty; urgency=medium

  * debian/patches/dhcp-one-socket-per-interface.patch: Use separate
sockets for DHCP from multiple interfaces.  Thanks to Jay Vosburgh
. (LP: #1652348)

 -- Mathieu Trudel-Lapierre   Tue, 13 Jun 2017
11:11:44 -0400

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

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

Title:
  initrd dhcp fails / ignores valid response

Status in klibc package in Ubuntu:
  Fix Released
Status in klibc source package in Trusty:
  Fix Released
Status in klibc source package in Xenial:
  Fix Released
Status in klibc source package in Yakkety:
  Fix Released
Status in klibc source package in Zesty:
  Fix Released

Bug description:
  [SRU justification]
  Changes to ordering of kernel enumeration of network interfaces, which may 
happen in any release, can regress network configuration from an initramfs.  
Support for netbooting should not depend on interface order, it should work 
reliably on all systems.

  [Test case]
  Detailed reproducer described in 
  .

  [Regression potential]
  Moderate regression potential, because of a relatively large patch touching a 
not-widely-used but still critical piece of code.  Regression testing should 
include verifying that MAAS-booted cloud images still work as expected in a 
variety of environments.

  
  Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been (re?)introduced 
that is breaking dhcp booting in the initrd environment.  This is stopping 
instances that use iscsi storage from being able to connect.

  Over serial console it outputs:

  IP-Config: no response after 2 secs - giving up
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f1 hardware address 90:e2:ba:d1:36:39 mtu 1500 DHCP RARP
  IP-Config: no response after 3 secs - giving up

  with increasing delays until it fails.  At which point a simple
  ipconfig -t dhcp -d "ens2f0"  works.  The console output is slightly
  garbled but should give you an idea:

  (initramfs) ipconfig -t dhcp -[  728.379793] ixgbe :13:00.0 ens2f0: 
changing MTU from 1500 to 9000
  d "ens2f0"
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f0 guessed broadcast address 10.0.1.255
  IP-Config: ens2f0 complete (dhcp from 169.254.169.254):
   addres[  728.980448] ixgbe :13:00.0 ens2f0: detected SFP+: 3
  s: 10.0.1.56broadcast: 10.0.1.255   netmask: 255.255.255.0
   gateway: 10.0.1.1   [  729.148410] ixgbe :13:00.0 ens2f0: NIC Link is Up 
10 Gbps, Flow Control: RX/TX
    dns0 : 169.254.169.254  dns1   : 0.0.0.0
   rootserver: 169.254.169.254 rootpath:
   filename  : /ipxe.efi

  tcpdumps show that dhcp requests are being received from the host, and
  responses sent, but not accepted by the host.  When the ipconfig
  command is issued manually, an identical dhcp request and response
  happens, only this time it is accepted.  It doesn't appear to be that
  the messages are being sent and received incorrectly, just silently
  ignored by ipconfig.

  I was seeing this behaviour earlier this year, which I was able to fix
  by specifying "ip=dhcp" as a kernel parameter.  About a month ago that
  was identified as causing us other problems (long story) and we
  dropped it, at which point we discovered the original bug was no
  longer an issue.

  Putting "ip=dhcp" back on with this kernel no longer fixes the
  problem.

  I've compared the two initrds and effectively the only thing that has
  changed between the two is the kernel components.

  Ubuntu kernel bisect offending commit:
  # first bad commit: [fd4b5fa6e3487d15ede746f92601af008b2abbc0] mnt: Add a per 
mount namespace limit on the number of mounts

  Ubuntu kernel bisect offending commit submission:
  https://lkml.org/lkml/2016/10/5/308

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1652348/+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 1665088] Re: netplan bridge config doesn't support stp boolean

This bug was fixed in the package nplan - 0.23~16.10.1

---
nplan (0.23~16.10.1) yakkety; urgency=medium

  * Backport netplan 0.23 to 16.10. (LP: #1688632)

nplan (0.23) artful; urgency=medium

  * Do not unbind brcmfmac, interface will be gone. (LP: #1696162)

nplan (0.22) artful; urgency=medium

  * Add support for setting a custom MAC address on all device types.
(LP: #1690388)
  * Improved MAC/vlan integration tests; thanks for Dimitri John Ledkov for the
changes.

nplan (0.21) artful; urgency=medium

  [ Ryan Harper ]
  * Add support for setting MTU on a device. (LP: #1668693)

  [ Mathieu Trudel-Lapierre ]
  * Don't rebind Atheros AR9271; it would confuse the driver. (LP: #1672740)
  * debian/control: Add Conflicts: against netplan; the network 'plan' daemon.
Both ship the same /usr/sbin/netplan. (LP: #1665842)

nplan (0.20) zesty; urgency=medium

  * tests/integration.py: increase timeout for integration tests (networkd and
NetworkManager "wait-online" checks) to account for longer bring-up times
when dealing with stacked virtual devices.

nplan (0.19) zesty; urgency=medium

  * Add support for unordered definition of network devices: you can now
specify a virtual devices before their member devices. (LP: #1670495)
  * Allow setting up the STP state for a bridge. (LP: #1665088)
  * Document bond/bridge parameters support. (LP: #1664702)

nplan (0.18) zesty; urgency=medium

  * debian/tests/integration.py: in some cases 'iw reg get' may qualify the
reg domain results with 'global'; we must not let that trip up tests when
they are run on Ubuntu infrastructure vs. local tests.

nplan (0.17) zesty; urgency=medium

  * New release:
- Add support for configuring bonds.
- Add support for configuring bridges.

nplan (0.16) zesty; urgency=medium

  [ Martin Pitt ]
  * doc/example-config: Adjust "routes:" example.
It does not make sense to make "routes:" a global thing, they should be
tied to an interface so that the route is only set when the corresponding
interface exists and is up, and the config is not split in two parts.
  * doc/netplan.md: Point out that NM does not support globbing (LP: #1631018)

  [ Mathieu Trudel-Lapierre ]
  * Fix coverage for src/netplan to be 100%, and fail if coverage falls below
that mark again.
  * Add support for specifying routes.

nplan (0.15) zesty; urgency=medium

  * tests/generate.py: Fix PEP-8 error (newly detected by -proposed
pycodestyle).

nplan (0.14) zesty; urgency=medium

  * tests/generate.py: Introduce macros for commonly expected networkd output
  * networkd: Use NetworkManager compatible DHCP route metrics (LP: #1639754)
  * doc/netplan.md: Fix wrong wifi reference in "br0" example
  * doc/netplan.md: Clarify introduction
  * tests/integration.py: Fix race condition with waiting for networkd

nplan (0.13) zesty; urgency=medium

  [ Jonathan Cave ]
  * Blacklist mwifiex_pcie from rebinds (work around LP: #1630285)

  [ Martin Pitt ]
  * Add support for nameservers (LP: #1626617)

 -- Mathieu Trudel-Lapierre   Tue, 06 Jun 2017
17:25:57 -0700

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

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

Title:
  netplan bridge config doesn't support stp boolean

Status in netplan:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in nplan source package in Yakkety:
  Fix Released
Status in systemd source package in Yakkety:
  New
Status in nplan source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Users of netplan may wish to specify a custom MTU value for a device.

  [Test case]
  - Run nplan integration tests on the release
  - Validate that netplan generate && netplan apply alone, without config, 
behave as expected (no result)
  - Validate that netplan generate && netplan apply with minimal config writes 
/run/NetworkManager/conf.d/10-globally-managed-devices.conf
  - Validate that netplan generate && netplan apply works with any existing 
configuation.
  - Use the config below; ensure behavior is as expected (STP value is set on 
the interface; adjust device names as appropriate). There should be no errors 
at applying the requested configuration.
  - Use the config below with the 'stp' key; the device should be brought up 
and include the default value set for the kernel.

  [Regression potential]
  STP default value should continue to be used for the bridge configured using 
netplan if STP is unset in configuration.

  ---

  networkd supports setting STP value in Bridge type netdevs, but
  netplan does not

[Touch-packages] [Bug 1684097] Re: Date format isn't good

2017-06-27 Thread Gunnar Hjalmarsson

I see now that this issue is true for Swedish as well, so the issue is
not specific to French. Can it be that the translation template for
indicator-datetime needs to be updated?

** Changed in: ubuntu-translations
 Assignee: Ubuntu French Translators (ubuntu-l10n-fr) => (unassigned)

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

Title:
  Date format isn't good

Status in Ubuntu Translations:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Date format isn't good in date indicator whereas the translation
  format is good https://translations.launchpad.net/ubuntu/zesty/+source
  /indicator-datetime/+pots/indicator-datetime/fr/1/+translate

  In french, it should be displayed "mer. 19 avril" ; not "mer. avril
  19"

  I think it miss this translation witch was present on xenial:
  https://translations.launchpad.net/ubuntu/xenial/+source/indicator-
  datetime/+pots/indicator-datetime/fr/5/+translate

  See the attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1684097/+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 1700721] Re: Laser printer prints sheets of random ASCII characters

2017-06-27 Thread Till Kamppeter

These lines should work permanently, as the option setting changes are
permanently recorded in /etc/cups/printers.conf.

For making them getting applied automatically for everyone having this
printer a quirk rule has to be added to /usr/share/cups/usb/org.cups
.usb-quirks.

You can edit the file to find out what works for you, or tell us your
printer's USB vendor and product ideas to add a quirk rule according to
your reported option settings.

You find the needed vendor and product IDs by running the command
"lsusb". Please post the line of the output which corresponds to your
printer here.

If you edit /usr/share/cups/usb/org.cups.usb-quirks and find a way which
solves your problem, please post your changes here.


** Changed in: foomatic-db (Ubuntu)
   Status: New => Incomplete

** Package changed: foomatic-db (Ubuntu) => cups (Ubuntu)

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

Title:
  Laser printer prints sheets of random ASCII characters

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  When I print a PDF from my raspberry pi (raspbian jessie) through CUPS (
  CUPS 1.7.5) service the first job prints fine but after that any other job 
prints random set of characters at the top of the page. I run `CUPS error_log` 
but it has nearly 26,000 lines so I will attach the file. I also run `Capturing 
print job data` but there I had multiple 'd' files not a single one. I will 
attach `appout`, the document I'm printing and the result I get please let me 
know if I need to add anything else. The printer I'm using is 
`Lexmark_Lexmark_T652`. I want to print A5 paper. File `appout` returns PDF. I 
tried converting it to image but the problem still persists.

  Document to be printed: 
https://drive.google.com/file/d/0B2EOtXJyI9ICbi16TUpIaFBlOWc/view?usp=sharing
  Printout after first job: https://goo.gl/photos/RhEpqVZGgHESZN2W8

  error_log: 
https://drive.google.com/file/d/0B2EOtXJyI9ICYWw3LUo1SkYwSGs/view?usp=sharing
  appout: 
https://drive.google.com/file/d/0B2EOtXJyI9ICdkxRSUYwektOVzg/view?usp=sharing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1700721/+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 1218442] Re: IPv6 addresses are lost when an interface is shortly down

2017-06-27 Thread Jan Baranowski

I can also confirm that the issue exists.

I'm the administrator of 2 DNS nameservers (bind9) running Ubuntu
14.04.5 LTS with upgraded kernel (linux-image-generic-lts-xenial which
depends on linux-image-4.4.0-81-generic at this time).

root@ns2:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename:   trusty

root@ns2:~# uname -a
Linux ns2 4.4.0-81-generic #104~14.04.1-Ubuntu SMP Wed Jun 14 12:45:52 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

While one of nameservers behaves as expected, the other experiences the
issue described above:

It's dual stack setup, i.e. there is global IPv4 and IPv6 address on a
single interface. /etc/network/interfaces on failing machine is as
follows (IPs have been obfuscated):

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address XXX.XXX.XXX.34
netmask 255.255.255.224
network XXX.XXX.XXX.32
broadcast XXX.XXX.XXX.63
gateway XXX.XXX.XXX.33
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers XXX.XXX.XXX.35 XXX.XXX.XXX.3
dns-search X

iface eth0 inet6 static
address ::::2::1
netmask 64
gateway :::::1


The problem I'm experiencing is that there is no default IPv6 route set after 
reboot. Setting it manually temporarily fixes the problem.

Investigation:

1. ifconfig shows eth0 is up with 1 v4, 1 v6 link-local and 1 v6 global IP 
address (seems OK)
2. route -6 -n shows single v6 default route using link-local address of 
router's interface as nexthop
3. /etc/init.d/networking stop says: stop: job failed while stopping
4. by examining this initscript i established that it uses ifdown internally, 
ifdown -a --exclude=lo -v to be exact
5.

root@ns2:~# ifdown -a --exclude=lo -v
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/bind9
run-parts: executing /etc/network/if-down.d/resolvconf
run-parts: executing /etc/network/if-down.d/upstart
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/ip6tasave
run-parts: executing /etc/network/if-post-down.d/iptasave

root@ns2:~# echo $?
0

which is strange because SSH connectivity remains intact

6. 
root@ns2:~# ifdown eth0
ifdown: interface eth0 not configured

this makes more sense

7. there is --force switch to ifdown; lets try it

root@ns2:~# ifdown eth0 --force

finally brings eth0 down

moreover, subsequent:

root@ns2:~# ifup eth0

brings interface up and sets v6 gateway correctly

8. at this point I still cannot stop & start "networking" using
initscript, but ifdown && ifup work fine

9. soft reboot

10. v6 gateway is set up automatically after reboot (oO)

11. hard reboot

12. v6 gateway is set up automatically after reboot (expected behavior)

13. soft reboot

14. we're back in square one

15.

root@ns2:/run/network# ls -al
razem 12
drwxr-xr-x  3 root root 180 cze 27 17:24 .
drwxr-xr-x 19 root root 640 cze 27 17:26 ..
-rw-r--r--  1 root root   6 cze 27 17:24 ifstate
-rw-r--r--  1 root root   1 cze 27 17:24 ifstate.eth0
-rw-r--r--  1 root root   3 cze 27 17:24 ifstate.lo
-rw-r--r--  1 root root   0 cze 27 17:24 .ifstate.lock
-rw-r--r--  1 root root   0 cze 27 17:24 ifup.eth0
-rw-r--r--  1 root root   0 cze 27 17:24 ifup.lo
drwxr-xr-x  2 root root  40 cze 27 17:24 static-network-up-emitted
root@ns2:/run/network# cat ifstate
lo=lo
root@ns2:/run/network# cat ifstate.eth0

root@ns2:/run/network# cat ifstate.lo
lo
root@ns2:/run/network# cd static-network-up-emitted/
root@ns2:/run/network/static-network-up-emitted# ls -al
razem 0
drwxr-xr-x 2 root root  40 cze 27 17:24 .
drwxr-xr-x 3 root root 180 cze 27 17:24 ..

(sorry for polish locale)

16. ifdown eth0 --force and ifup eth0 solve the problem again

NOTE1: while ifdown & ifup seems to fail some time, ifconfig eth0 down &
ifconfig eth0 up seem to always work as expected

NOTE2: tried number of hard and soft resets before trying ifdown eth0
--force with no result

NOTE3: system runs on Xen 6.2 build 70446c

To sum up:
--
-quick, temporary fix: ifdown eth0 --force && ifup eth0
-in general it seems like some software is interfering with ifup/ifdown using 
interface state files in /run/network
--

N.B. list of installed packages:
$apt list --installed
Listing...
accountsservice/trusty-updates,now 0.6.35-0ubuntu7.3 amd64 [installed]
acpid/trusty,now 1:2.0.21-1ubuntu2 amd64 [installed]
adduser/trusty,now 3.113+nmu3ubuntu3 all [installed]
apparmor/trusty-updates,trusty-security,now 2.10.95-0ubuntu2.6~14.04.1 amd64 
[installed]
apport/trusty-updates,now 2.14.1-0ubuntu3.24 all [installed]
apport-symptoms/trusty,now 0.20 all [installed]

[Touch-packages] [Bug 1547647] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  [SRU] please remove libqt5webkit dependency

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  Fix Committed
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  This is an SRU request, based on the process documented at
  https://wiki.ubuntu.com/StableReleaseUpdates

  
  [Impact]

   * When declaring online accounts for use by Ubuntu, the system uses a
  webview to authenticate to online services like Facebook or Google.

   * On X11 desktops, that webview currently uses an old qt5webkit
  component that is now unmaintained

   * Backporting this fix will simplify the maintenance work, by
  removing the need for that old component, and will improve the
  coherence of the system by using a supported Oxide webview

  [Test Case]

  To verify the change:

   * Go to system settings > Online Accounts
   * Add account of type Google, Facebook or Twitter (which uses webview for 
authentication)
   * Verify that a webview opens to log onto the online service
   * Verify that the account is listed in the account list at the end of this 
process
   * Verify that the related apps and services can use the online account as 
before (ie Shotwell photo uploads, Photos scope, etc.)

  [Regression Potential]

   * On architectures not supported by Oxide, namely ppc64el and s390x,
  the change will trigger a runtime error when trying to use that part
  of signon-ui.

   * The problem affects users of Ubuntu desktop systems based on X11.
  The change is already in effect on Unity8/Mir devices for a few
  months.

  [Other Info]

   * signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11)
  depends on libqt5webkit5

   * See also: https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-
  security-updates/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1547647/+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 1576424] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  Gimp crashes with text tool & caps lock

Status in GTK+:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Xenial:
  Fix Committed
Status in gtk+2.0 source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  Gimp crashes with a segfault when I use caps lock while renaming a
  layer. It is possible Caps lock causes crashes in other events also.

  [Test Case]

  Steps to reproduce:

  1. Open a new blank gimp document
  2. select the text tool
  3. type a couple of words of text (gimp will create a text layer above the 
background layer)
  4. with the text tool still selected, click on the background layer (just to 
move away from the text layer)
  5. now double click on the text layer to rename the layer (layer name gets 
highlighted)
  6. press the caps lock key
  7. click on the background layer again (without renaming or doing anything to 
the text layer)
  Now repeat steps 5 and 6.
  Gimp crashes.

  [Regression Potential]

  None expected. The patch used has been taken from upstream
  development.

  
https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad

  Packages for Xenial and Yakkety have been built in a PPA and
  regression tested.

  [ Other Info ]

  I can force this to happen every time I launch Gimp. Rebooting makes
  no difference. It seems to be the second time I press caps lock that
  forces the crash. I tried launching Gimp with caps lock on vs caps
  lock off, but I don't believe it made any difference. I can force a
  crash every time following the above sequence.

  I deleted my gimp preferences folder then rebooted for good measure.
  Gimp created a fresh preferences folder, but it hasn't solved the
  problem. I was originally in single window mode, but the new
  preferences folder put me back to multi window, but it crashes either
  way.

  I ran dmesg | tail after the crash and got the following line:

  gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0
  error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000]

  I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
  (available from the Additional Drivers tab). In that same tab, I also
  have enabled Processor microcode firmware for Intel CPUs. Terminal
  tells me Gimp version is 2.8.16-1ubuntu1

  I'm not very experienced with bug reporting and not sure what other
  information I need to supply. Gimp was absolutely rock solid on this
  machine with 15.10, so it may be a Xubuntu issue.

  Hope someone can take a look at this. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1576424/+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 1591411] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Fix Released
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  Invalid

Bug description:
  [Impact]

  The bug affects multiple users and introduces an user visible delay
  (~25 seconds) on SSH connections after a large number of sessions have
  been processed. This has a serious impact on big systems and servers
  running our software.

  The currently proposed fix is actually a safe workaround for the bug
  as proposed by the dbus upstream. The workaround makes uid 0 immune to
  the pending_fd_timeout limit that kicks in and causes the original
  issue.

  [Test Case]

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  Then checking the log file if there are any ssh sessions that are
  taking 25+ seconds to complete.

  Multiple instances of the same script can be used at the same time.

  [Regression Potential]

  The fix has a rather low regression potential as the workaround is a
  very small change only affecting one particular case - handling of uid
  0. The fix has been tested by multiple users and has been around in
  zesty for a while, with multiple people involved in reviewing the
  change. It's also a change that has been proposed by upstream.

  [Original Description]

  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias:

[Touch-packages] [Bug 1598300] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1623418] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  gcc-as-needed.diff patch broke mpx support in GCC

Status in gcc:
  Unknown
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-6 package in Ubuntu:
  Fix Released
Status in binutils source package in Xenial:
  Fix Committed
Status in gcc-5 source package in Xenial:
  New
Status in binutils source package in Yakkety:
  Fix Committed
Status in gcc-5 source package in Yakkety:
  New
Status in gcc-6 source package in Yakkety:
  New

Bug description:
  [SRU Justification]
  gcc-5 from Ubuntu is configured with MPX support, but it is broken due
  to always-added linker option "-as-needed".

  [Test case]
  1. Pass -mmpx to gcc when building an arbitrary project on x86.
  2. Verify with ldd that the resulting executable is not linked against 
libmpx.so because the -as-needed flag has discarded the mpx library from being 
linked in.
  3. Install binutils and gcc-5 from -proposed.
  4. Rebuild the target, again with -mmpx.
  5. Verify with ldd that the new executable is linked against libmpx.so.
  6. Verify that there are no regressions in the binutils testsuite on any 
architectures, by manually checking the results in the build log.

  [Regression potential]
  This binutils patch implements new --push-state / --pop-state options which 
will not be used in the common case, only when -mmpx is passed.  When these 
flags are not in use, which is the default, it should have no effect on the 
behavior of the toolchain, so risk of regression is minimal.


  Here is the GCC upstream bug & fix

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267

  https://gcc.gnu.org/viewcvs/gcc?view=revision=240057

  Would it be possible to backport this fix to Ubuntu gcc-5 build?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1623418/+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 1642966] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Triaged
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1644323] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  Installing unity8-session-snap adversely effects unity7

Status in Canonical System Image:
  Confirmed
Status in dbus package in Ubuntu:
  Fix Released
Status in unity-gtk-module package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in unity-gtk-module source package in Xenial:
  Fix Committed

Bug description:
  [ Description ]

  In Xenial, when dbus-user-session is installed, dbus' upstart job
  still starts a new bus. Things get confused about which bus to talk
  to.

  [ Fix ]

  Already fixed in Yakkety. Cherry-pick the upstart job. On top of
  Yakkety's version, call `dbus-update-activation-environment --verbose
  --systemd GTK_MODULES', because Xenial does not have the change in
  upstart to automatically publish to the systemd activation
  environment.

  /etc/X11/Xsession.d/95dbus_update-activation-env is called too early -
  before unity-gtk-module.conf is started - so dbus activated services
  miss the GTK_MODULES environment variable. Update unity-gtk-
  module.conf to set it in the dbus activation environment.

  [ QA ]

  Install dbus-user-session, press print screen. It should be delayed if
  you are experiencing this bug, and not delayed otherwise.

  Remove dbus-user-session, make sure the session still works properly -
  the global menu works, everything launches properly, etc.

  Test that gnome-terminal has global menus in both situations.

  [ Regression potential ]

  This change alters the way that the session bus is launched, even if
  you aren't using dbus-user-session. Even though this same change is
  deployed in ≥ yakkety, be aware of this. In yakkety we have installed
  dbus-user-session by default, so the case where you don't have it
  isn't as well tested. I would suggest focusing some testing on the non
  dbus-user-session case.

  [ Original report ]

  After installing the deb (and then the snap), certain things in the
  unity7 session take a very long time (30 to 60 secs), such as
  launching chromium and ctrl-alt-t for a new terminal session.

  Removing both the deb and the snap followed by a reboot does not fix
  the symptoms.

  Xenial amd64 laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644323/+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 1700721] [NEW] Laser printer prints sheets of random ASCII characters

You have been subscribed to a public bug:

When I print a PDF from my raspberry pi (raspbian jessie) through CUPS (
CUPS 1.7.5) service the first job prints fine but after that any other job 
prints random set of characters at the top of the page. I run `CUPS error_log` 
but it has nearly 26,000 lines so I will attach the file. I also run `Capturing 
print job data` but there I had multiple 'd' files not a single one. I will 
attach `appout`, the document I'm printing and the result I get please let me 
know if I need to add anything else. The printer I'm using is 
`Lexmark_Lexmark_T652`. I want to print A5 paper. File `appout` returns PDF. I 
tried converting it to image but the problem still persists.

Document to be printed: 
https://drive.google.com/file/d/0B2EOtXJyI9ICbi16TUpIaFBlOWc/view?usp=sharing
Printout after first job: https://goo.gl/photos/RhEpqVZGgHESZN2W8

error_log: 
https://drive.google.com/file/d/0B2EOtXJyI9ICYWw3LUo1SkYwSGs/view?usp=sharing
appout: 
https://drive.google.com/file/d/0B2EOtXJyI9ICdkxRSUYwektOVzg/view?usp=sharing

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
Laser printer prints sheets of random ASCII characters
https://bugs.launchpad.net/bugs/1700721
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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

[Touch-packages] [Bug 1668724] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  fails to mount cgroupfs inside containers running on 16.04

Status in cgroup-lite package in Ubuntu:
  Fix Released
Status in cgroup-lite source package in Precise:
  Fix Committed
Status in cgroup-lite source package in Trusty:
  New
Status in cgroup-lite source package in Xenial:
  Fix Committed
Status in cgroup-lite source package in Yakkety:
  Fix Committed

Bug description:
  I need to run nested Ubuntu 12.04 and 14.04 containers on 16.04 hosts,
  and have noticed that the cgroups-mount script for mounting the
  cgroups inside the containers has stopped working. This is because
  systemd now comounts multiple controllers on a single hierarchy, which
  prevents mounting them individually inside the container.

  ===  SRU Justification 
  Impact: nested containers fail to start
  Reproduce:  create a root owned container;  install lxc and cgroup-lite;  
create a container, and try to start it.  Starting will fail if cgroup-lite is 
running in the first level container without this patch.
  Regression potential:  should be low, it's possible that the regexp is simply 
wrong for some cases.
  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1668724/+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 1673350] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  In Progress
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in multipath-tools source package in Xenial:
  Fix Committed
Status in hw-detect source package in Yakkety:
  In Progress
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released
Status in multipath-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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 1686344] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  Mesa 17.0.x stable release

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

  Mesa stable release for zesty & backport to xenial. Xenial needs newer
  libdrm from zesty. These are part of the hwe-16.04 stack refresh.

  [Test case]

  Install, run desktop session, test xonotic.

  the important hw drivers to test:
  - i965 (Intel)
  - radeonsi (AMD)

  [Regression potential]

  Spec compliance test suites are already run by Intel and others, so
  feature regressions should not be possible. GLESv1 support has been
  dropped from the packaging though, but packages that depend on
  libgles1-mesa have been pushed to proposed to drop the dependency, see
  bug 1676845 (applies to xenial).

  17.0.x has been available for xenial and yakkety users for a while,
  and so far no-one has complained about driver regressions.

  [Other info]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1686344/+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 1686618] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  In Progress
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS

[Touch-packages] [Bug 1687981] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  Fix Committed
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  Fix Committed
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xfonts-utils source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+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 1688208] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  gnome-shell crashed with SIGSEGV in foreach_city() from foreach_city()
  from foreach_city() from foreach_city() from foreach_city()

Status in libgweather:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  Fix Committed

Bug description:
  Impact
  ==
  Memory corruption in libgweather caused gnome-shell to crash. This is 
particularly bad for GNOME on Wayland as a gnome-shell crash will causes the 
user to lose their sessions.

  (GNOME Shell 3.24 introduced a new weather feature in the clock menu.)

  This particular error has been reported over 1000 times to
  errors.ubuntu.com from Ubuntu GNOME 17.04 and was also a Fedora 26
  blocker bug.

  Test Case
  =
  The number of crashes reported on errors.ubuntu.com for gnome-shell should be 
significantly lower once this new version of libgweather rolls out.

  Because e.u.com links this issue with gnome-shell, this is difficult
  to verify except that if you run gnome-shell, it shouldn't crash so
  often especially when first logging in.

  Regression Potential
  
  The main new commit here had already been cherry-picked by Fedora and in 
Ubuntu 17.10 Alpha. Considering the previous 

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/39b6625ed47999dab38b064b2d91bde1e11dec62 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1688208/+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 1692127] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  duplicate signature for Package problems can be too short

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

Bug description:
  [Impact]
  apport is creating a shorter than appropriate duplicate signature in 
apport-package bug reports which can lead to misconsolidation and confused 
developers.

  [Test Case]
  1) Boot a system with an old kernel installed or a freshly installed system
  2) edit /etc/default/grub and replace a ` with a '
  3) Upgrade the kernel, watch it crash
  4) Discover a crash report with a DuplicateSignature whose 2nd line starts 
with "Examining"

  With the version of the package from -proposed the DuplicateSignature
  in this case should really have a 2nd line that starts with 'Setting
  up linux-image* ...'. While in this particular case not much is lost
  in other cases valuable information will be missing.

  [Regression Potential]
  The code change is correct and has been tested in artful, additionally I'm 
using the same regular expression to clean up apport-package reports as they 
come in to LP. The only risk here is a typo in the patch that would cause the 
hook (the change is in the ubuntu general hook) to error out which apport would 
handle gracefully and we just wouldn't have a DuplicateSignature.

  [The Original Description]
  Steve brought up bug 1691983 and how it's duplicate signature is missing 
information.  It contains:

  package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
  Installing for x86_64-efi platform.
  Installation finished. No error reported.
  Running in non-interactive mode, doing nothing.
  dpkg: error processing package shim-signed (--configure):
   subprocess installed post-installation script returned error exit status 1

  But is missing:

  Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
  locale: Cannot set LC_CTYPE to default locale: No such file or directory
  locale: Cannot set LC_MESSAGES to default locale: No such file or directory
  locale: Cannot set LC_ALL to default locale: No such file or directory
  debconf: unable to initialize frontend: Passthrough
  debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket: 
Connection refused at (eval 18) line 3.)
  debconf: falling back to frontend: Noninteractive

  This is because of the following code in data/general-hooks/ubuntu.py:

  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 'Unpacking', 'Would remove')
  149 for line in termlog.split('\n'):
  150 if line.startswith(PKG_MSGS):
  151 dupe_sig = '%s\n' % line
  152 continue

  The shim-signed package prints a line starts with "Installing " and
  that matches PKG_MSGS so we reset the dupe_sig because that's a
  message we'd expect from a package manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1692127/+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 1695567] Change of SRU verification policy

As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g. verification-done-xenial). Please note that the global
'verification-done' tag can no longer be used for this purpose.

Thank you!

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

Title:
  /usr/bin/gnome-shell:*** Error in `/usr/bin/gnome-shell': double free
  or corruption (out): ADDR *** in g_free() from
  gweather_location_unref()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  This error has been reported over 700 times on errors.ubuntu.com for
  Ubuntu GNOME 17.04.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.

  [Other Info]
  This updates libgweather from 3.24.0 to 3.24.1
  https://git.gnome.org/browse/libgweather/log

  The guard_against_segfault commit was already present in Ubuntu 17.04.

   Original bug report 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.24.2-0ubuntu4, the problem page at 
https://errors.ubuntu.com/problem/06422e05faafe183b4cb70daa7306dcb4c08c97e 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1695567/+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 1695928] Re: Please remove obsolete UOA packages

Khurshi, thanks for your comment.

Shotwell was stuck on an old git snapshot for over a year (LP: #1581180)
because the UOA support was unmaintained and no one had the time or
ability to forward-port that support. That support has now been removed
and we'll finally get a supportable version of Shotwell in Ubuntu 17.10.

Empathy's UOA support was dropped about two months ago from 17.10.

Full removal of UOA means removal of Unity8. It does not mean removal of
Unity 7. The online support for some of the dash "lenses" has already
been removed as part of this effort.

This request is about removal, not demotion to universe.

"Ubuntu Online Accounts is no longer maintained. There is an
alternative, GNOME Online Accounts"

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

Title:
Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
New

Bug description:
Ubuntu Online Accounts is no longer maintained. There is an
alternative, GNOME Online Accounts for the GNOME desktop.

Also, Unity's Online Accounts settings panel does not currently work
without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

Please remove these source packages and their binaries:
=

Phase 1
---
gnome-control-center-signon
account-plugins
account-plugin-fitbit
account-polld
pay-service
qtpurchasing-opensource-src
storage-provider-webdav
sync-monitor
ubuntuone-credentials
ubuntu-push
unity-china-photo-scope
unity-scope-gdrive

By the way, gnome-control-center-signon fails to build with vala 0.36:

https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

Phase 2
---
ubuntu-system-settings-online-accounts
online-accounts-api
storage-framework
keeper
mcloud
address-book-app
address-book-service
dialer-app
messaging-app
telephony-service
tone-generator
ubuntu-system-settings
buteo-sync-plugins-contacts-google
camera-app
indicator-transfer
indicator-transfer-buteo
libertine
ubuntu-experience-tests
unity-scopes-shell
unity8

Other Notes
---
The Shotwell suggests have been dropped in artful-proposed. Shotwell is
temporarily stuck in -proposed because of an autopkgtest issue
https://bugzilla.gnome.org/781802

Kubuntu still uses signon-ui.

See also https://code.launchpad.net/~xnox/ubuntu-
seeds/unity8-removals/+merge/323615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+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 1700763] Re: I'm a noob, and i have a problem in my ubuntu, and i don't know how to fix it

2017-06-27 Thread Antonio Ze Silva

** Information type changed from Public to Public Security

** Information type changed from Public Security to Private

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

Title:
  I'm a noob, and i have a problem in my ubuntu, and i don't know how to
  fix it

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm a noob, and i have a problem in my ubuntu, and i don't know how to fix it.
  Can you help me? 
  Thanks for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jun 27 14:26:06 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.40, 4.8.0-56-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated 
Graphics Controller [1179:fa47]
 Subsystem: Toshiba America Info Systems GK208M [GeForce GT 740M] 
[1179:fa47]
  InstallationDate: Installed on 2017-06-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: TOSHIBA SATELLITE L50-A-18T
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic 
root=UUID=9737d1b0-5c2f-4b41-bb41-9bbe41d65fce ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.90
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSATELLITEL50-A-18T:pvrPSKK6E-02M06CEP:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: SATELLITE L50-A-18T
  dmi.product.version: PSKK6E-02M06CEP
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Jun 27 14:19:54 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1700763/+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 1700776] [NEW] Problem after a new install of Ubuntu 16.04.2 LTS

2017-06-27 Thread Antonio Ze Silva

Public bug reported:

After a new install of Ubuntu 16.04.2 LTS, i have some bugs. 
I'm new in the Ubuntu  world, but i would like to know more. 
I have install the OS with a pen and after i installed some apps from the 
"Ubuntu software" and i run the "software update". After  this i restart the pc 
and i have a notification saying i have a problem/bug. 
Can someone help me?
Thanks for your time.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Jun 27 16:32:01 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.40, 4.8.0-36-generic, x86_64: installed
 virtualbox, 5.0.40, 4.8.0-56-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems 4th Gen Core Processor Integrated 
Graphics Controller [1179:fa47]
   Subsystem: Toshiba America Info Systems GK208M [GeForce GT 740M] [1179:fa47]
InstallationDate: Installed on 2017-06-27 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: TOSHIBA SATELLITE L50-A-18T
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.90
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: VG10S
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.90:bd09/19/2014:svnTOSHIBA:pnSATELLITEL50-A-18T:pvrPSKK6E-02M06CEP:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: SATELLITE L50-A-18T
dmi.product.version: PSKK6E-02M06CEP
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Jun 27 16:13:09 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  Problem after a new install of Ubuntu 16.04.2 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  After a new install of Ubuntu 16.04.2 LTS, i have some bugs. 
  I'm new in the Ubuntu  world, but i would like to know more. 
  I have install the OS with a pen and after i installed some apps from the 
"Ubuntu software" and i run the "software update". After  this i restart the pc 
and i have a notification saying i have a problem/bug. 
  Can someone help me?
  Thanks for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jun 27 16:32:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu

[Touch-packages] [Bug 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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 pam in Ubuntu.
https://bugs.launchpad.net/bugs/1699360

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this all

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-systemd:amd64 232-21ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun 21 00:45:00 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-19 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1699360/+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 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

** Changed in: gnome-software (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this all

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-systemd:amd64 232-21ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun 21 00:45:00 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-19 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1699360/+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 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

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

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this all

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-systemd:amd64 232-21ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun 21 00:45:00 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-19 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1699360/+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 1699360] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

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

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

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

Title:
  package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in debconf package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this all

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libpam-systemd:amd64 232-21ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun 21 00:45:00 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-19 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  netplan bridge config doesn't support stp boolean

Status in netplan:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in nplan source package in Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  New
Status in nplan source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Users of netplan may wish to specify a custom MTU value for a device.

  [Test case]
  - Run nplan integration tests on the release
  - Validate that netplan generate && netplan apply alone, without config, 
behave as expected (no result)
  - Validate that netplan generate && netplan apply with minimal config writes 
/run/NetworkManager/conf.d/10-globally-managed-devices.conf
  - Validate that netplan generate && netplan apply works with any existing 
configuation.
  - Use the config below; ensure behavior is as expected (STP value is set on 
the interface; adjust device names as appropriate). There should be no errors 
at applying the requested configuration.
  - Use the config below with the 'stp' key; the device should be brought up 
and include the default value set for the kernel.

  [Regression potential]
  STP default value should continue to be used for the bridge configured using 
netplan if STP is unset in configuration.

  ---

  networkd supports setting STP value in Bridge type netdevs, but
  netplan does not accept the key.

  root@ubuntu:/etc/netplan# apt-cache policy nplan
  nplan:
    Installed: 0.18
    Candidate: 0.18
    Version table:
   *** 0.18 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:/etc/netplan# lsb_release -rd
  Description: Ubuntu Zesty Zapus (development branch)
  Release: 17.04

  root@ubuntu:/etc/netplan# cat 52-bridge.yaml
  network:
  ethernets:
  eth0:
  addresses:
  - 10.11.12.13/24
  match:
  macaddress: '52:54:00:12:34:00'
  set-name: foobar0
  eth1:
  match:
  macaddress: '52:54:00:12:34:02'
  set-name: eth1
  eth2:
  match:
  macaddress: '52:54:00:12:34:04'
  set-name: eth2
  bridges:
  br0:
  addresses:
  - 192.168.14.2/24
  interfaces:
  - eth1
  - eth2
  parameters:
  ageing-time: 250
  priority: 22
  forward-delay: 1
  hello-time: 1
  max-age: 10
  path-cost:
  eth1: 50
  eth2: 75
  stp: true
  version: 2

  root@ubuntu:/etc/netplan# netplan generate
  Error in network definition //etc/netplan/52-bridge.yaml line 24 column 16: 
unknown key stp

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1665088/+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 1665088] Re: netplan bridge config doesn't support stp boolean

This bug was fixed in the package nplan - 0.23~16.04.1

---
nplan (0.23~16.04.1) xenial; urgency=medium

  * Backport netplan 0.23 to 16.04. (LP: #1688632)

nplan (0.23) artful; urgency=medium

  * Do not unbind brcmfmac, interface will be gone. (LP: #1696162)

nplan (0.22) artful; urgency=medium

  * Add support for setting a custom MAC address on all device types.
(LP: #1690388)
  * Improved MAC/vlan integration tests; thanks for Dimitri John Ledkov for the
changes.

nplan (0.21) artful; urgency=medium

  [ Ryan Harper ]
  * Add support for setting MTU on a device. (LP: #1668693)

  [ Mathieu Trudel-Lapierre ]
  * Don't rebind Atheros AR9271; it would confuse the driver. (LP: #1672740)
  * debian/control: Add Conflicts: against netplan; the network 'plan' daemon.
Both ship the same /usr/sbin/netplan. (LP: #1665842)

nplan (0.20) zesty; urgency=medium

  * tests/integration.py: increase timeout for integration tests (networkd and
NetworkManager "wait-online" checks) to account for longer bring-up times
when dealing with stacked virtual devices.

nplan (0.19) zesty; urgency=medium

  * Add support for unordered definition of network devices: you can now
specify a virtual devices before their member devices. (LP: #1670495)
  * Allow setting up the STP state for a bridge. (LP: #1665088)
  * Document bond/bridge parameters support. (LP: #1664702)

nplan (0.18) zesty; urgency=medium

  * debian/tests/integration.py: in some cases 'iw reg get' may qualify the
reg domain results with 'global'; we must not let that trip up tests when
they are run on Ubuntu infrastructure vs. local tests.

nplan (0.17) zesty; urgency=medium

  * New release:
- Add support for configuring bonds.
- Add support for configuring bridges.

nplan (0.16) zesty; urgency=medium

  [ Martin Pitt ]
  * doc/example-config: Adjust "routes:" example.
It does not make sense to make "routes:" a global thing, they should be
tied to an interface so that the route is only set when the corresponding
interface exists and is up, and the config is not split in two parts.
  * doc/netplan.md: Point out that NM does not support globbing (LP: #1631018)

  [ Mathieu Trudel-Lapierre ]
  * Fix coverage for src/netplan to be 100%, and fail if coverage falls below
that mark again.
  * Add support for specifying routes.

nplan (0.15) zesty; urgency=medium

  * tests/generate.py: Fix PEP-8 error (newly detected by -proposed
pycodestyle).

 -- Mathieu Trudel-Lapierre   Tue, 06 Jun 2017
17:19:10 -0700

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

Title:
  netplan bridge config doesn't support stp boolean

Status in netplan:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in nplan source package in Yakkety:
  Fix Committed
Status in systemd source package in Yakkety:
  New
Status in nplan source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Users of netplan may wish to specify a custom MTU value for a device.

  [Test case]
  - Run nplan integration tests on the release
  - Validate that netplan generate && netplan apply alone, without config, 
behave as expected (no result)
  - Validate that netplan generate && netplan apply with minimal config writes 
/run/NetworkManager/conf.d/10-globally-managed-devices.conf
  - Validate that netplan generate && netplan apply works with any existing 
configuation.
  - Use the config below; ensure behavior is as expected (STP value is set on 
the interface; adjust device names as appropriate). There should be no errors 
at applying the requested configuration.
  - Use the config below with the 'stp' key; the device should be brought up 
and include the default value set for the kernel.

  [Regression potential]
  STP default value should continue to be used for the bridge configured using 
netplan if STP is unset in configuration.

  ---

  networkd supports setting STP value in Bridge type netdevs, but
  netplan does not accept the key.

  root@ubuntu:/etc/netplan# apt-cache policy nplan
  nplan:
    Installed: 0.18
    Candidate: 0.18
    Version table:
   *** 0.18 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:/etc/netplan# lsb_release -rd
  Description: Ubuntu Zesty Zapus (development branch)
  Release: 17.04

  root@ubuntu:/etc/netplan# cat 52-bridge.yaml
  network:
  ethernets:
  eth0:
  addresses:
  - 10.11.12.13/24
  match:

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

2017-06-27 Thread Khurshid Alam

Will these be available on universe? Because many little applications
still depends on them? Shotwell works with UOA and flickr. Same for
empathy. Removal of UOA basically means removal of Unity7.

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qtpurchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  address-book-app
  address-book-service
  dialer-app
  messaging-app
  telephony-service
  tone-generator
  ubuntu-system-settings
  buteo-sync-plugins-contacts-google
  camera-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  ubuntu-experience-tests
  unity-scopes-shell
  unity8

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+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 1692543] Re: Regression tests cannot write to apparmor path_max module parameter in artful/4.11

2017-06-27 Thread Seth Forshee

This patch fixes the tests for me. Turns out that we can't simply skip
writing to path_max as that seems to break the test case completely, so
I changed it to print an XFAIL message and abort the test.

** Patch added: "fix-longpath-test.patch"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+attachment/4904113/+files/fix-longpath-test.patch

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

Title:
  Regression tests cannot write to apparmor path_max module parameter in
  artful/4.11

Status in apparmor package in Ubuntu:
  New

Bug description:
  The longpath regression tests tries to write to
  /sys/module/apparmor/parameters/path_max, but this is read-only in
  artful/4.11:

  commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6
  Author: John Johansen 
  Date:   Thu Apr 6 05:14:20 2017 -0700

  apparmor: Make path_max parameter readonly

  This is causing ADT to fail.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful-canonical-kernel-team-
  ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz

running longpath
longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission 
denied
Fatal Error (longpath): Unexpected shell error. Run with -x to debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+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 1283003] Re: Bluetooth headset/speakers listed but not selectable in Sound settings

** Tags removed: verification-done
** Tags added: verification-done-xenial

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

Title:
  Bluetooth headset/speakers listed but not selectable in Sound settings

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in blueman source package in Xenial:
  New
Status in gnome-bluetooth source package in Xenial:
  New
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Bluetooth headset/speakers are listed but not selectable in Sound settings 
(the correct device's options don't appear in the right pane). Hence no 
Bluetooth audio is unusable.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and try to select the device.
  Expected: The Bluetooth audio device is selectable (its options appear in the 
right pane when clicked and the selection stays on that device).

  [Regression Potential]
  Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main 
area affected. A combination of related A2DP bugs in pulseaudio in xenial means 
it is difficult to get working at all without this patch. So highly unlikely 
Bluetooth audio support could get worse. Since pulseaudio itself is being 
modified there is always a regression potential in support for other audio 
devices, but several audio devices have been tested and all continue to work 
well with the patch.

  [Other notes]
  Related to bug 1438510 and bug 1582213. Possibly others too. The debdiff 
which fixes this is attached to bug 1582213.

  Please note that Bluetooth and Bluetooth audio support in xenial is
  still not perfect. This SRU only aims to address a few of the most
  troublesome issues. Please consider the fact that this is an
  incremental improvement and some people are still likely to experience
  some bugs related to pulseaudio and Bluetooth, even after this SRU.

  The patch was authored by Luke Yelavich with help from Konrad
  Zapałowicz. And it has received further testing over the past two
  months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed
  here only changes the changelog wording from Luke's original PPA.

  [Original Description]
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

To manage notifications about this bug go to:
https://bugs.launchpad.net/blueman/+bug/1283003/+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 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)