[Touch-packages] [Bug 1692345] Re: package libpcre3:i386 2:8.38-3.1 failed to install/upgrade: package libpcre3:i386 is not ready for configuration cannot configure (current status 'half-installed')

[Launchpad Bug Tracker]

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

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

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

Title:
  package libpcre3:i386 2:8.38-3.1 failed to install/upgrade: package
  libpcre3:i386 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in pcre3 package in Ubuntu:
  Confirmed

Bug description:
  I have this error after unsuccefuly install teamviewer via GDebi:

  ➜  ~ sudo apt-get install -f   
  [sudo] password for matjaz: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  2 not fully installed or removed.
  Need to get 0 B/223 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  dpkg: error processing package libpcre3:i386 (--configure):
   package libpcre3:i386 is not ready for configuration
   cannot configure (current status 'half-installed')
  dpkg: dependency problems prevent configuration of libselinux1:i386:
   libselinux1:i386 depends on libpcre3; however:
Package libpcre3:i386 is not installed.

  No apport report written because the error message indicates its a followup 
error from a previous failure.
dpkg: error processing package libselinux1:i386 
(--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   libpcre3:i386
   libselinux1:i386
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpcre3:i386 2:8.38-3.1
  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
  AptOrdering:
   libpcre3: Configure
   libselinux1: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun May 21 20:20:57 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu7
  ErrorMessage: package libpcre3:i386 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: pcre3
  Title: package libpcre3:i386 2:8.38-3.1 failed to install/upgrade: package 
libpcre3:i386 is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1692111] Re: Unable to configure raw.id_map with multiple entries

[Stéphane Graber]

Marking the LXD side invalid as this will be sorted out by a liblxc
change.

** Changed in: lxd (Ubuntu)
   Status: Fix Committed => Invalid

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

Title:
  Unable to configure raw.id_map with multiple entries

Status in lxc package in Ubuntu:
  Fix Committed
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  I am trying to map two users (999, 1001) to one of my containers. I
  added both IDs to /etc/subgid and /etc/subuid. I followed by setting
  raw.id_map property value (as instructed here
  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2017-March/013034.html):

  "echo -e "both 999 999\nboth 1001 1001" |  lxc config set mycontainer
  raw.idmap -"

  However upon starting the container, I get errors (log excerpt below).
  If, on the other hand, I set idmap to either "both 999 999" or "both
  1001 1001" only - i.e. if I map only one user at the time, the
  container starts just fine and the user is mapped as expected.

  My subgid and subuid look as follows:

  lxd:10:65536
  root:10:65536
  root:1001:1
  root:999:1

  Log excerpt:

  Name: mycontainer
  Remote: unix:/var/lib/lxd/unix.socket
  Architecture: x86_64
  Created: 2017/02/22 18:54 UTC
  Status: Stopped
  Type: persistent
  Profiles: default

  Log:

  lxc 20170519204102.895 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer" already existed.
  lxc 20170519204102.896 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-1" already existed.
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-1: No such file or directory
  lxc 20170519204102.897 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-2" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-2: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-3" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-3: No such file or directory
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-4" already existed.
  lxc 20170519204102.898 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-4: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-5" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-5: No such file or directory
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-6" already existed.
  lxc 20170519204102.899 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-6: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-7" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-7: No such file or directory
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:create_path_for_hierarchy:1306 - Path 
"/sys/fs/cgroup/systemd//lxc/mycontainer-8" already existed.
  lxc 20170519204102.900 ERRORlxc_cgfsng - 
cgroups/cgfsng.c:cgfsng_create:1363 - No such file or directory - Failed to 
create /sys/fs/cgroup/systemd//lxc/mycontainer-8: No such file or directory
  lxc 20170519204102.901 ERROR

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

[Launchpad Bug Tracker]

This bug was fixed in the package update-notifier - 3.181

---
update-notifier (3.181) artful; urgency=medium

  * Fix APT sandboxing for data downloads failing (LP: #1522675)

 -- Julian Andres Klode   Wed, 28 Jun 2017 22:25:25
+0200

** Changed in: update-notifier (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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: [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 9.6ubuntu101

---
base-files (9.6ubuntu101) artful; urgency=medium

  * update-motd.d/50-news: Fix LP: #1691901
- when the curl fails (perhaps due to a firewall issue), we should
  create an empty cache file, so that subsequent runs are not
  penalized; ensure that we *only* print when we're not forced

 -- Dustin Kirkland   Thu, 29 Jun 2017 10:35:06
-0500

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

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

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

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.

  === SRU ===

  [ IMPACT ]

  This bug affects Ubuntu 17.04 systems which cannot reach the internet
  (more specifically, https://motd.ubuntu.com).  There is a bug in the
  implementation of /etc/update-motd.d/50-news whereby the failure of
  the curl fetch of the motd news causes a 5-second delay.  This should
  not be the case.  By design, the motd is fetched in the background, by
  a systemd timer, and refreshed every ~12 hours, also in the
  background.  On login, the script should just cat the cache file.  If
  the cache file isn't found, then it will try to fetch a new motd.  In
  the firewalled system case, the background fetch failed, AND didn't
  create an empty file.  The fix as attached simply ensures that an
  empty file is created if the curl fetch fails.  This eliminates the
  login delay and solves the bug.  Every 12 hours, the curl will be
  retried, quietly in the background, so if the curl failure happened
  for temporary reasons, it'll recover, gracefully, eventually.

  [ TEST CASE ]

  You can either test this on a firewalled system.  Or, if you can hack
  an entry in your local /etc/hosts for motd.ubuntu.com for an invalid
  IP address.  Without the fix, you'll experience a 5 second delay on
  login.  With the fix, you'll login immediately.

  Failure case:

  $ lxc launch ubuntu:17.04 LP1691901
  $ lxc exec LP1691901 bash
  # ssh-import-id kirkland
  # echo 192.168.0.0 motd.ubuntu.com >> /etc/hosts
  # rm -f /var/cache/motd-news
  # exit
  $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
  real0m5.333s
  user0m0.016s
  sys 0m0.000s

  Apply the fix.

  $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
  real0m0.316s
  user0m0.008s
  sys 0m0.008s

  [ REGRESSION ]

  This is a simple, safe fix with minimal regression potential:

  diff -Nru base-files-9.6ubuntu13/update-motd.d/50-motd-news 
base-files-9.6ubuntu13.2/update-motd.d/50-motd-news
  --- base-files-9.6ubuntu13/update-motd.d/50-motd-news   2017-02-15 
13:54:04.0 -0600
  +++ base-files-9.6ubuntu13.2/update-motd.d/50-motd-news 2017-06-29 
10:43:05.0 -0500
  @@ -51,9 +51,13 @@
   # If we're not forcing an update, and we have a cached motd-news file,
   # then just print it and exit as quickly as possible, for login performance.
   # Note that systemd should keep this cache file up to date, asynchronously
  -if [ "$FORCED" != "1" ]  && [ -r $CACHE ]; then
  -   echo
  -   safe_print $CACHE
  +if [ "$FORCED" != "1" ]; then
  +   if [ -r $CACHE ]; then
  +   echo
  +   safe_print $CACHE
  +   else
  +   : > $CACHE
  +   fi
  exit 0
   fi
   
  @@ -111,7 +115,9 @@
  safe_print "$NEWS"
  # Try to update the cache
  safe_print "$NEWS" 2>/dev/null >$CACHE || true
  -   fi
  +   else
  +   : > "$CACHE"
  +   fi
   done
   rm -f "$NEWS" "$NEWS.err"
   exit 0

  --
  [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

[Touch-packages] [Bug 1698437] Re: Please upload libgdata 0.17.8

[Launchpad Bug Tracker]

This bug was fixed in the package libgdata - 0.17.8-0ubuntu1

---
libgdata (0.17.8-0ubuntu1) artful; urgency=medium

  * New upstream release (LP: #1698437)
  * debian/control.in:
- Bump minimum GLib to 2.38.0 and libsoup to 2.56

 -- Jeremy Bicha   Wed, 28 Jun 2017 09:39:31 -0400

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

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

Title:
  Please upload libgdata 0.17.8

Status in libgdata package in Ubuntu:
  Fix Released
Status in libgdata source package in Zesty:
  New

Bug description:
  libgdata 0.17.8 was released on April 20. Please upload the new
  version for Ubuntu. Once it gets into Artful, it can be uploaded into
  zesty as well as SRU

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

-- 
Mailing list: https://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 1701430] [NEW] [VPCEB23FM, Realtek ALC269, Black Headphone Out, Front] No sound at all

[Juan Mendez]

Public bug reported:

Headphones detected, however, no sound output.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  juan   1644 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jun 29 23:45:10 2017
InstallationDate: Installed on 2017-06-19 (10 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  juan   1644 F pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [VPCEB23FM, Realtek ALC269, Black Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/05/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0270Y8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0270Y8:bd05/05/2010:svnSonyCorporation:pnVPCEB23FM:pvrC605CG3Q:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCEB23FM
dmi.product.version: C605CG3Q
dmi.sys.vendor: Sony Corporation

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


** Tags: amd64 apport-bug xenial

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

Title:
  [VPCEB23FM, Realtek ALC269, Black Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Headphones detected, however, no sound output.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juan   1644 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 29 23:45:10 2017
  InstallationDate: Installed on 2017-06-19 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juan   1644 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [VPCEB23FM, Realtek ALC269, Black Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0270Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0270Y8:bd05/05/2010:svnSonyCorporation:pnVPCEB23FM:pvrC605CG3Q:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEB23FM
  dmi.product.version: C605CG3Q
  dmi.sys.vendor: Sony Corporation

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

-- 
Mailing list: https://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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

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

** Changed in: libva (Ubuntu)
   Importance: High => Medium

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

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  New

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libva/+bug/1698287/+subscriptions

-- 
Mailing list: https://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 1701297] Re: NTP reload failure (causing deployment failures with MAAS)

[Tyler Hicks]

AppArmor has difficulties mediating filesystem access when overlayfs is
involved. That's a known issue but isn't one that is easily solved due
to the internal design of overlayfs and its use of private vfsmounts. It
also isn't something that we're planning to fix for the 17.10 cycle.

I thought that we recently investigated a similar issue to this and
determined that MAAS wouldn't enable AppArmor when it is initially
provisioning a machine. I can't remember the exact details and I'm not
confident that was the final solution but maybe that rings some bells
for the others that were involved.

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

Title:
  NTP reload failure (causing deployment failures with MAAS)

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+subscriptions

-- 
Mailing list: https://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 1693155] Re: Distorted blurry battery indicator in gnome-shell (using ubuntu-mono icons at default low-DPI scale 1.0)

[Daniel van Vugt]

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Distorted blurry battery indicator in gnome-shell (using ubuntu-mono
  icons at default low-DPI scale 1.0)

Status in Ubuntu theme:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  My battery indicator looks blurry

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170518-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May 24 11:34:12 2017
  InstallationDate: Installed on 2017-04-28 (25 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170426)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1693155/+subscriptions

-- 
Mailing list: https://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 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Kai-Heng Feng]

Esokrates, 
Traditional Microphone can work while disabling the hiss. I'll build a new 
kernel for you to test.

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

-- 
Mailing list: https://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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

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

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

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  New

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libva/+bug/1698287/+subscriptions

-- 
Mailing list: https://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 1701392] Re: package ca-certificates 20160104ubuntu0.14.04.1 failed to install/upgrade: зацикливание триггеров, отмена работы

[Seth Arnold]

I subscribed apport because it appears there's a python2 -> python3
regression in here too, see the HookError_ubuntu.txt file.

Thanks

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

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

Title:
  package ca-certificates 20160104ubuntu0.14.04.1 failed to
  install/upgrade: зацикливание триггеров, отмена работы

Status in apport package in Ubuntu:
  New
Status in ca-certificates package in Ubuntu:
  New

Bug description:
  При обработке следующих пакетов произошли ошибки:
   ca-certificates
  Error in function:

  ...

  Cannot create report: [Errno 17] File exists: '/var/crash/ca-
  certificates.0.crash'

  ...

  .ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 66, in add_info
  check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 155, in 
check_attachment_for_errors
  trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 440, in trim_dpkg_log
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 440, in 
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 7166: 
invalid continuation byte
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-119-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jun 30 01:22:59 2017
  ErrorMessage: зацикливание триггеров, отмена работы
  InstallationDate: Installed on 2015-02-03 (877 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release 
amd64+mac (20140722.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu0.14.04.1 failed to 
install/upgrade: зацикливание триггеров, отмена работы
  UpgradeStatus: Upgraded to xenial on 2017-06-29 (0 days ago)

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

-- 
Mailing list: https://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 1701345] Re: package linux-image-4.8.0-58-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1701318
   package linux-image-4.8.0-58-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status.

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

Title:
  package linux-image-4.8.0-58-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-hwe package in Ubuntu:
  New

Bug description:
  installation stalled

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-58-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 00:48:24 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-29 (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: linux-hwe
  Title: package linux-image-4.8.0-58-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)

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

-- 
Mailing list: https://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 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Daniel van Vugt]

I haven't yet tested the latest test kernels but disagree with comment
#85.

As mentioned in comment #77:
"Although I can't help but think that we could still fix this by limiting the 
volume more (or finding some gain setting that is on but shouldn't be). Having 
headphone volume that doesn't go high enough is already a common problem plenty 
of people would be used to. But the important thing is they won't report that 
as a bug, so maybe that's better."

I think we might need more people testing the potential fix to gauge
whether or not a lower max volume is really worse than the hiss.

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

Title:
  XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

-- 
Mailing list: https://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 1701345] Re: package linux-image-4.8.0-58-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Seth Arnold]

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

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Title:
  package linux-image-4.8.0-58-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-hwe package in Ubuntu:
  New

Bug description:
  installation stalled

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-58-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 00:48:24 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-29 (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: linux-hwe
  Title: package linux-image-4.8.0-58-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)

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

-- 
Mailing list: https://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 1701297] Re: NTP reload failure (causing deployment failures with MAAS)

[Andres Rodriguez]

It seems that this only happens when using ga-16.04 and doesn't when
using hwe-16.04

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

Title:
  NTP reload failure (causing deployment failures with MAAS)

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+subscriptions

-- 
Mailing list: https://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 1701270] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: le paquet libssl1.0.0:amd64 n'est pas prêt pour la configuration configuration impossible (ét

[Seth Arnold]

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

** This bug has been marked a duplicate of bug 1692981
   package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  le paquet libssl1.0.0:amd64 n'est pas prêt pour la configuration
  configuration impossible (état actuel « half-installed »)

Status in openssl package in Ubuntu:
  New

Bug description:
  not install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  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.6
  Architecture: amd64
  Date: Thu Jun 29 15:38:13 2017
  ErrorMessage: le paquet libssl1.0.0:amd64 n'est pas prêt pour la 
configuration  configuration impossible (état actuel « half-installed »)
  InstallationDate: Installed on 2017-03-16 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
le paquet libssl1.0.0:amd64 n'est pas prêt pour la configuration  configuration 
impossible (état actuel « half-installed »)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1691225] Re: hud-service trying to output error messages using ncurses colours to syslog

[Launchpad Bug Tracker]

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

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

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

Title:
  hud-service trying to output error messages using ncurses colours to
  syslog

Status in hud package in Ubuntu:
  Confirmed

Bug description:
  Wherever hud-service is failing, it's trying to print using ncurses
  colour tags (m#NNN[NN) where syslog is text-only.

  example error message:

  May 16 14:11:02 eva hud-service[1967]: #033[31mvoid
  DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m:
  "No such interface 'com.canonical.dbusmenu' on object at path
  /org/ayatana/bamf/window/75498803"

  what this error message should probably be:
  May 16 14:11:02 eva hud-service[1967]: void 
DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*): "No such 
interface 'com.canonical.dbusmenu' on object at path 
/org/ayatana/bamf/window/75498803"

  Ubuntu 17.04 zesty
  hud: 14.10+17.04.20170106.1-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: hud 14.10+17.04.20170106.1-0ubuntu1
  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 16 14:10:55 2017
  InstallationDate: Installed on 2017-04-18 (27 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1701406] [NEW] failed to install steam installer, now incapable of uninstalling same

[Alex Laemmle]

Public bug reported:

When installing the Install steam app, the installer got stuck at around
50% (using the Software app), and eventually the computer went to sleep
and when I got back the installation had failed.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bash 4.4-2ubuntu1.1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Thu Jun 29 19:57:32 2017
DpkgTerminalLog:
 dpkg: error processing package bash (--configure):
  package bash is not ready for configuration
  cannot configure (current status 'triggers-awaited')
ErrorMessage: package bash is not ready for configuration  cannot configure 
(current status 'triggers-awaited')
InstallationDate: Installed on 2017-06-23 (6 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: bash
Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: package bash is 
not ready for configuration  cannot configure (current status 
'triggers-awaited')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  failed to install steam installer, now incapable of uninstalling same

Status in bash package in Ubuntu:
  New

Bug description:
  When installing the Install steam app, the installer got stuck at
  around 50% (using the Software app), and eventually the computer went
  to sleep and when I got back the installation had failed.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 29 19:57:32 2017
  DpkgTerminalLog:
   dpkg: error processing package bash (--configure):
package bash is not ready for configuration
cannot configure (current status 'triggers-awaited')
  ErrorMessage: package bash is not ready for configuration  cannot configure 
(current status 'triggers-awaited')
  InstallationDate: Installed on 2017-06-23 (6 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: package bash is 
not ready for configuration  cannot configure (current status 
'triggers-awaited')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Timothy R. Chavez]

@Dustin

Are we looking at the same USER_AGENT string? I ran the block of code
from `update-motd.d/50-motd-news` on my laptop that constructs the
USER_AGENT variable that's sent to motd.ubuntu.com and it looks like
this: "curl/7.47.0-1ubuntu2.2 Ubuntu/16.04.2/LTS
GNU/Linux/4.7.0-040700-generic/x86_64
Intel(R)/Core(TM)/i7-7500U/CPU/@/2.70GHz uptime/1499911.84/3827524.62"
not what's described at https://en.wikipedia.org/wiki/User_agent and not
what you pasted above. Reading the comments in the code, it's clear that
it's being used to craft the response, but what's not clear is if
Canonical is collecting the server information... If they are, I think
it's fair to make that apparent. That's all.

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1701403] [NEW] error

[nishant sikarwar]

Public bug reported:

error

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: Fri Jun 30 05:10:21 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:81ec]
   Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 
M330] [103c:81ec]
InstallationDate: Installed on 2017-05-28 (32 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
 Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Notebook
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic 
root=UUID=419c3361-cf40-477b-8f1d-775d45815526 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.09
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81EC
dmi.board.vendor: HP
dmi.board.version: 61.28
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.28:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
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: Fri Jun 30 04:39:45 2017
xserver.configfile: default
xserver.errors: RADEON(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/1701403

Title:
  error

Status in xorg package in Ubuntu:
  New

Bug description:
  error

  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: Fri Jun 30 05:10:21 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:81ec]
 Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / 
R5 M330] [103c:81ec]
  InstallationDate: Installed on 2017-05-28 (32 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  

[Touch-packages] [Bug 1701297] Re: NTP reload failure (causing deployment failures with MAAS)

[Launchpad Bug Tracker]

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

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

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

Title:
  NTP reload failure (causing deployment failures with MAAS)

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+subscriptions

-- 
Mailing list: https://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 1701297] Re: NTP reload failure (causing deployment failures with MAAS)

[Launchpad Bug Tracker]

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

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

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

Title:
  NTP reload failure (causing deployment failures with MAAS)

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+subscriptions

-- 
Mailing list: https://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 1690028] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from endpoint_handle

[Brian Murray]

** Tags added: regression-proposed

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

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  endpoint_set_configuration() from endpoint_handler() from
  _dbus_object_tree_dispatch_and_unlock()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a76b9eca937daf6dc05fd32a35fa50e58ccf8f5 
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/pulseaudio/+bug/1690028/+subscriptions

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Zachary Fouts]

Re: UserAgent
My UserAgent in Chrome|FireFox|Curl|wget|etc do not tell the remote server what 
the uptime of my host is.


Re: Fun Facts 
Fun facts are indeed fun, but this feature should be reserved for important 
information regarding EOL, Security Patches, etc. 
If the administrator of ${system} wants a fun fact, they can install something 
else. Cow Say, Fortune, whatever to display that.


Not trying to stir anything up, it's a great feature but that feature should be 
used wisely so people do not disable it.

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1701297] Re: NTP reload failure (causing deployment failures with MAAS)

[Andres Rodriguez]

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

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: apparmor (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  NTP reload failure (causing deployment failures with MAAS)

Status in cloud-init:
  Incomplete
Status in apparmor package in Ubuntu:
  Confirmed
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-init/0.7.9-153-g16a7302f-
  0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1701297/+subscriptions

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Dustin Kirkland ]

Regarding the "sometimes the news is just a fun fact"...

Do you get similarly annoyed when the Google logo on the homepage is
replaced with a Google Doodle?

https://www.google.com/doodles

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Dustin Kirkland ]

Regarding the User Agent -- this is exactly equivalent to the USER AGENT
string your browser (Chrome, Chromium, Firefox, Safari, curl, wget)
sends to every website in the world.  Curious?  Install apache2 on
localhost, tail -f /var/log/apache2/access.log, and hit
http://localhost/ with a web browser.  Here, I've just done it for you:

127.0.0.1 - - [29/Jun/2017:17:55:20 -0500] "GET / HTTP/1.1" 200 777 "-"
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/59.0.3071.104 Safari/537.36"

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Dustin Kirkland ]

This comment is mainly for Tim and Andrew (of Digital Ocean), who seem
offended by this behavior.

I just captured this snapshot in my Chrome browser, searching for
"Docker Cloud".  The top results of that search are not actually the
organic docker.com results, but rather a Google Ad for Digital Ocean
services.

Moreover, the HBO link wasn't even an advertisement!  It was an
interesting piece of news from this week, a blog post of an interesting
developer who did something fun on top of Ubuntu.  And we celebrated
that achievement.

** Attachment added: "Screenshot from 2017-06-29 17-36-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+attachment/4906069/+files/Screenshot%20from%202017-06-29%2017-36-58.png

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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] Re: Default capability of cap_setfcap+i should be set on setcap

[Serge Hallyn]

Indeed it should be reasonable to do so.  Note that there are cases,
including unprivileged containers, where file capabilities cannot be
set, so the packaging would have to gracefully handle (i.e. ignore) that
failure rather than fail the package install.

-- 
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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Timothy R. Chavez]

@Simos:

Not sure about the Twitter storm you're referring too. The http request
being sent to motd.ubuntu.com is embedding information like system
uptime in the user-agent header. That appears to be used to determine
which information to send back in the http response. What's not clear,
is if it's being collected or not. Also, while unattended-upgrades for
-security may be a default, it may also be disabled, so I don't think
you can assume that. That said, I do think it's a good point that if
you're automatically receiving security upgrades, how much the motd news
that covers such things actually matters. Is your recommendation to
disable motd-news by default and make it opt-in?

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1701392] [NEW] package ca-certificates 20160104ubuntu0.14.04.1 failed to install/upgrade: зацикливание триггеров, отмена работы

[Oleg Sapunov]

Public bug reported:

При обработке следующих пакетов произошли ошибки:
 ca-certificates
Error in function:

...

Cannot create report: [Errno 17] File exists: '/var/crash/ca-
certificates.0.crash'

...

.ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 66, in add_info
check_attachment_for_errors(report, attachment)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 155, in 
check_attachment_for_errors
trim_dpkg_log(report)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 440, in trim_dpkg_log
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
  File "/usr/share/apport/general-hooks/ubuntu.py", line 440, in 
report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 7166: 
invalid continuation byte
.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ca-certificates 20160104ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
Uname: Linux 3.13.0-119-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Fri Jun 30 01:22:59 2017
ErrorMessage: зацикливание триггеров, отмена работы
InstallationDate: Installed on 2015-02-03 (877 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.3)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: ca-certificates
Title: package ca-certificates 20160104ubuntu0.14.04.1 failed to 
install/upgrade: зацикливание триггеров, отмена работы
UpgradeStatus: Upgraded to xenial on 2017-06-29 (0 days ago)

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

Title:
  package ca-certificates 20160104ubuntu0.14.04.1 failed to
  install/upgrade: зацикливание триггеров, отмена работы

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  При обработке следующих пакетов произошли ошибки:
   ca-certificates
  Error in function:

  ...

  Cannot create report: [Errno 17] File exists: '/var/crash/ca-
  certificates.0.crash'

  ...

  .ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 66, in add_info
  check_attachment_for_errors(report, attachment)
File "/usr/share/apport/general-hooks/ubuntu.py", line 155, in 
check_attachment_for_errors
  trim_dpkg_log(report)
File "/usr/share/apport/general-hooks/ubuntu.py", line 440, in trim_dpkg_log
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
File "/usr/share/apport/general-hooks/ubuntu.py", line 440, in 
  report['DpkgTerminalLog'] = '\n'.join([str(line.decode('utf-8')) for line 
in lines])
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe2 in position 7166: 
invalid continuation byte
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20160104ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-119.166-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-119-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Fri Jun 30 01:22:59 2017
  ErrorMessage: зацикливание триггеров, отмена работы
  InstallationDate: Installed on 2015-02-03 (877 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release 
amd64+mac (20140722.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: ca-certificates
  Title: package ca-certificates 20160104ubuntu0.14.04.1 failed to 
install/upgrade: зацикливание триггеров, отмена работы
  UpgradeStatus: Upgraded to xenial on 2017-06-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1701392/+subscriptions

-- 
Mailing list: https://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] Update Released

[Steve Langasek]

The verification of the Stable Release Update for cloud-init 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 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:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Committed
Status in cloud-init source package in Zesty:
  Fix Committed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  A cloud-config that contains packages to install (see below) or
  'package_upgrade' will run 'apt-get update'.  That can sometimes fail as a
  result of contention with the apt-daily.service that updates that information.

  Cloud-config showing the problem is just like:

    $ cat my.yaml
    #cloud-config
    packages: ['hello']

  [Test Case]
  lxc-proposed-snapshot is
    
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot
  It publishes an image to lxd with proposed enabled and cloud-init upgraded.

  a.) launch an instance with proposed version of cloud-init and some user-data.
     This is platform independent.  The test case demonstrates lxd.
     $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \
     "package_upgrade: true" > config.yaml
     $ release=xenial
     $ ref=proposed-$release
     $ ./lxc-proposed-snapshot --proposed --publish $release $ref;

  b.) start the instance
     $ name=$release-1693361
     $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml)
     $ sleep 1
     $ lxc exec $name -- tail -f /var/log/cloud-init.log 
/var/log/cloud-init-output.log
     # watch this boot.

   c.) Look for evidence of systemd failure
     journalctl -o short-precise | grep -i break
     journalctl -o short-precise | grep -i order

  [Regression Potential]
  Regression chance here is low.  Its possible that ordering loops
  could occur.  When that does happen, journalctl will mention it.  
Unfortunately
  in such cases systemd somewhat randomly picks a service to kil so behavior
  is somewhat undefined.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=11121fe4

  === End SRU Template ===

  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 the race the invocation
  of apt (e.g. use of "packages:" in the config) will fail.

  There is a lot of discussion online about this change to apt-daily
  (e.g. unattended upgrades happening during business hours, delaying
  boot, etc.) and discussion of potential systemd changes regarding
  timers firing during boot (c.f.
  https://github.com/systemd/systemd/issues/5659).

  While it would be better to solve this in apt itself, I suggest that
  cloud-init be defensive when calling apt and implement some retry
  mechanism.

  Various instances of people running into this issue:

  https://github.com/chef/bento/issues/609
  https://clusterhq.atlassian.net/browse/FLOC-4486
  https://github.com/boxcutter/ubuntu/issues/73
  
https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions

-- 
Mailing list: https://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

[Launchpad Bug Tracker]

This bug was fixed in the package cloud-init - 0.7.9-153-g16a7302f-
0ubuntu1~16.04.2

---
cloud-init (0.7.9-153-g16a7302f-0ubuntu1~16.04.2) xenial-proposed; 
urgency=medium

  * debian/patches/ds-identify-behavior-xenial.patch: refresh patch.
  * cherry-pick 5fb49bac: azure: identify platform by well known value
in chassis asset (LP: #1693939)
  * cherry-pick 003c6678: net: remove systemd link file writing from eni
renderer
  * cherry-pick 1cd4323b: azure: remove accidental duplicate line in
merge.
  * cherry-pick ebc9ecbc: Azure: Add network-config, Refactor net layer
to handle duplicate macs. (LP: #1690430)
  * cherry-pick 11121fe4: systemd: make cloud-final.service run before
apt daily (LP: #1693361)

 -- Scott Moser   Wed, 28 Jun 2017 17:17:18 -0400

** Changed in: cloud-init (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 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:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Committed
Status in cloud-init source package in Zesty:
  Fix Committed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  A cloud-config that contains packages to install (see below) or
  'package_upgrade' will run 'apt-get update'.  That can sometimes fail as a
  result of contention with the apt-daily.service that updates that information.

  Cloud-config showing the problem is just like:

    $ cat my.yaml
    #cloud-config
    packages: ['hello']

  [Test Case]
  lxc-proposed-snapshot is
    
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot
  It publishes an image to lxd with proposed enabled and cloud-init upgraded.

  a.) launch an instance with proposed version of cloud-init and some user-data.
     This is platform independent.  The test case demonstrates lxd.
     $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \
     "package_upgrade: true" > config.yaml
     $ release=xenial
     $ ref=proposed-$release
     $ ./lxc-proposed-snapshot --proposed --publish $release $ref;

  b.) start the instance
     $ name=$release-1693361
     $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml)
     $ sleep 1
     $ lxc exec $name -- tail -f /var/log/cloud-init.log 
/var/log/cloud-init-output.log
     # watch this boot.

   c.) Look for evidence of systemd failure
     journalctl -o short-precise | grep -i break
     journalctl -o short-precise | grep -i order

  [Regression Potential]
  Regression chance here is low.  Its possible that ordering loops
  could occur.  When that does happen, journalctl will mention it.  
Unfortunately
  in such cases systemd somewhat randomly picks a service to kil so behavior
  is somewhat undefined.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=11121fe4

  === End SRU Template ===

  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 the race the invocation
  of apt (e.g. use of "packages:" in the config) will fail.

  There is a lot of discussion online about this change to apt-daily
  (e.g. unattended upgrades happening during business hours, delaying
  boot, etc.) and discussion of potential systemd changes regarding
  timers firing during boot (c.f.
  https://github.com/systemd/systemd/issues/5659).

  While it would be better to solve this in apt itself, I suggest that
  cloud-init be defensive when calling apt and implement some retry
  mechanism.

  Various instances of people running into this issue:

  https://github.com/chef/bento/issues/609
  https://clusterhq.atlassian.net/browse/FLOC-4486
  https://github.com/boxcutter/ubuntu/issues/73
  
https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions

-- 
Mailing list: https://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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[John Howard]

The below command (installing some dotnet framework dependencies) kicked
up this error (and "1 not fully installed or removed.").

Just prior to running this command the visual-studio-code editor had
unsuccessfully tried to download and install mono-related packages.

-

# sudo apt-get install dotnet-dev-1.0.4
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  guile-2.0-libs libv8-3.14.5 linux-image-4.4.0-83-generic weechat-core
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  dotnet-hostfxr-1.0.1 dotnet-hostfxr-1.1.0 
dotnet-sharedframework-microsoft.netcore.app-1.0.5
  dotnet-sharedframework-microsoft.netcore.app-1.1.2 
linux-image-4.4.0-83-generic
Suggested packages:
  fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-headers-4.4.0-83-generic
The following NEW packages will be installed:
  dotnet-dev-1.0.4 dotnet-hostfxr-1.0.1 dotnet-hostfxr-1.1.0 
dotnet-sharedframework-microsoft.netcore.app-1.0.5
  dotnet-sharedframework-microsoft.netcore.app-1.1.2
The following packages will be upgraded:
  linux-image-4.4.0-83-generic
1 upgraded, 5 newly installed, 0 to remove and 6 not upgraded.
1 not fully installed or removed.
Need to get 97.3 MB/119 MB of archives.
After this operation, 347 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 
dotnet-hostfxr-1.1.0 amd64 1.1.0-1 [124 kB]
Get:2 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 
dotnet-sharedframework-microsoft.netcore.app-1.1.2 amd64 1.1.2-1 [22.9 MB]
Get:3 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 
dotnet-hostfxr-1.0.1 amd64 1.0.1-1 [123 kB]
Get:4 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 
dotnet-sharedframework-microsoft.netcore.app-1.0.5 amd64 1.0.5-1 [22.6 MB]
Get:5 https://apt-mo.trafficmanager.net/repos/dotnet-release xenial/main amd64 
dotnet-dev-1.0.4 amd64 1.0.4-1 [51.5 MB]   
Fetched 97.3 MB in 27s (3,486 kB/s) 
  
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another 
process: Resource temporarily unavailable
(Reading database ... 210651 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-83-generic_4.4.0-83.106_amd64.deb ...
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another 
process: Resource temporarily unavailable
dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-83-generic_4.4.0-83.106_amd64.deb 
(--unpack):
 subprocess new pre-installation script returned error exit status 1
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-83-generic 
/boot/vmlinuz-4.4.0-83-generic
Selecting previously unselected package dotnet-hostfxr-1.1.0.
Preparing to unpack .../dotnet-hostfxr-1.1.0_1.1.0-1_amd64.deb ...
Unpacking dotnet-hostfxr-1.1.0 (1.1.0-1) ...
Selecting previously unselected package 
dotnet-sharedframework-microsoft.netcore.app-1.1.2.
Preparing to unpack 
.../dotnet-sharedframework-microsoft.netcore.app-1.1.2_1.1.2-1_amd64.deb ...
Unpacking dotnet-sharedframework-microsoft.netcore.app-1.1.2 (1.1.2-1) ...
Selecting previously unselected package dotnet-hostfxr-1.0.1.
Preparing to unpack .../dotnet-hostfxr-1.0.1_1.0.1-1_amd64.deb ...
Unpacking dotnet-hostfxr-1.0.1 (1.0.1-1) ...
Selecting previously unselected package 
dotnet-sharedframework-microsoft.netcore.app-1.0.5.
Preparing to unpack 
.../dotnet-sharedframework-microsoft.netcore.app-1.0.5_1.0.5-1_amd64.deb ...
Unpacking dotnet-sharedframework-microsoft.netcore.app-1.0.5 (1.0.5-1) ...
Selecting previously unselected package dotnet-dev-1.0.4.
Preparing to unpack .../dotnet-dev-1.0.4_1.0.4-1_amd64.deb ...
Unpacking dotnet-dev-1.0.4 (1.0.4-1) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-image-4.4.0-83-generic_4.4.0-83.106_amd64.deb
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 debconf in Ubuntu.
https://bugs.launchpad.net/bugs/349469

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Confirmed
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: 

[Touch-packages] [Bug 1701349] [NEW] Nvidia display is slow

[0Suffr1]

Public bug reported:

Applications display is slow, mouse movement is delayed and movies
cannot be played smoothly but frame by frame.

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
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Jun 29 21:53:50 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Skylake Integrated 
Graphics [1462:116b]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM107M [GeForce GTX 
960M] [1462:116b]
InstallationDate: Installed on 2017-04-12 (78 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 1770:ff00  
 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Micro-Star International Co., Ltd. GS60 6QC
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-56-generic 
root=UUID=4742493d-f9c1-4072-9d91-f07611aac5da ro nomodeset quiet splash 
vt.handoff=7
SourcePackage: xorg
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 5: Error: GLX is not available on the system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16H8IMS.111
dmi.board.asset.tag: Default string
dmi.board.name: MS-16H8
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16H8IMS.111:bd11/21/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS606QC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H8:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
dmi.product.name: GS60 6QC
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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: Thu Jun 29 21:20:46 2017
xserver.configfile: default
xserver.errors:
 [drm] Failed to open DRM device for (null): -22
 Screen 0 deleted because of no matching config section.
 Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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


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

Title:
  Nvidia display is slow

Status in xorg package in Ubuntu:
  New

Bug description:
  Applications display is slow, mouse movement is delayed and movies
  cannot be played smoothly but frame by frame.

  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  

[Touch-packages] [Bug 1696237] Re: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Just rebooted this evening and seen this error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun  6 20:17:09 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2015-10-09 (606 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2017-01-25 (131 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "1";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-04-24T10:11:39.287010

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

-- 
Mailing list: https://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 1697375] Re: crash reports are not uploaded automatically

[Brian Murray]

** Changed in: whoopsie (Ubuntu)
Milestone: ubuntu-17.06 => ubuntu-17.07

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

Title:
  crash reports are not uploaded automatically

Status in whoopsie package in Ubuntu:
  New

Bug description:
  On artful crash reports are not uploaded automatically (several .crash
  files in /var/crash and no corresponding upload or .uploaded files)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1701183] DuplicateSignature.txt

[Brian Murray]

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/1701183/+attachment/4905951/+files/DuplicateSignature.txt

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

Title:
  package libelf1:i386 0.166-2ubuntu1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in elfutils package in Ubuntu:
  New

Bug description:
  Get this error on auto-update.

  greg@greg-laptop-ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  greg@greg-laptop-ubuntu:~$ apt-cache policy elfutils
  elfutils:
Installed: (none)
Candidate: 0.166-2ubuntu1
Version table:
   0.166-2ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libelf1:i386 0.166-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Wed Jun 28 10:05:33 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   zlib1g 1:1.2.11.dfsg-0ubuntu1
  DuplicateSignature:
   package:libelf1:i386:0.166-2ubuntu1
   Installing from local file 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20170616.1.orig.tar.gz
   Flash Plugin installed.
   dpkg: error processing package libelf1:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-26 (33 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: elfutils
  Title: package libelf1:i386 0.166-2ubuntu1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-05-26 (33 days ago)

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

-- 
Mailing list: https://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 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
  2886: ordinal not in range(128)

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I got this in the mail:

  From: Cron Daemon 
  To: root@...
  Subject: Cron  test -x /usr/sbin/anacron || ( cd / && 
run-parts --report /etc/cron.daily )
  Date: Thu, 25 Feb 2016 02:11:47 +0200 (EET)

  /etc/cron.daily/apt:
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1255, in 
  main(options)
File "/usr/bin/unattended-upgrade", line 1205, in main
  pkgs, pkg_install_success, pkgs_kept_back, mem_log, logfile_dpkg)
File "/usr/bin/unattended-upgrade", line 752, in send_summary_mail
  body += fp.read()
File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
  return codecs.ascii_decode(input, self.errors)[0]
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 
2886: ordinal not in range(128)

  According to /var/log/apt/history.log.1.gz, the packages upgraded that
  day were

  Start-Date: 2016-02-25  02:06:22
  Upgrade: libgnutls-openssl27:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), libvirt0:amd64 (1.2.2-0ubuntu13.1.16, 
1.2.2-0ubuntu13.1.17), libssl-dev:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), ca-certificates:amd64 (20141019ubuntu0.14.04.1, 
20160104ubuntu0.14.04.1), libgnutls26:amd64 (2.12.23-12ubuntu2.4, 
2.12.23-12ubuntu2.5), libssl-doc:amd64 (1.0.1f-1ubuntu2.16, 
1.0.1f-1ubuntu2.17), openssl:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17)
  End-Date: 2016-02-25  02:06:36

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.4
  Uname: Linux 2.6.32-042stab108.8 x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue Mar  8 08:26:05 2016
  PackageArchitecture: all
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to trusty on 2016-02-06 (30 days ago)

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

-- 
Mailing list: https://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 1700526] Re: package uuid-runtime 2.27.1-6ubuntu3.2 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su conf

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.2 failed to install/upgrade: El
  paquete está en un estado grave de inconsistencia - debe reinstalarlo
  antes de intentar su configuración.

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  my computer its power off repently

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jun 25 10:47:38 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-08-27 (303 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.2 failed to install/upgrade: El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1700526] DuplicateSignature.txt

[Brian Murray]

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/1700526/+attachment/4905935/+files/DuplicateSignature.txt

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.2 failed to install/upgrade: El
  paquete está en un estado grave de inconsistencia - debe reinstalarlo
  antes de intentar su configuración.

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  my computer its power off repently

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jun 25 10:47:38 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-08-27 (303 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.2 failed to install/upgrade: El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Dustin Kirkland ]

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

** 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/1701068

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1701290] DuplicateSignature.txt

[Brian Murray]

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/1701290/+attachment/4905949/+files/DuplicateSignature.txt

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

Title:
  package libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in heimdal package in Ubuntu:
  New

Bug description:
  No idea what Im supposed to put here, Ubuntu asked me to report the
  error, so I did.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 29 15:48:29 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-17 (103 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: heimdal
  Title: package libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (76 days ago)

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

-- 
Mailing list: https://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 1701290] Re: package libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  package libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in heimdal package in Ubuntu:
  New

Bug description:
  No idea what Im supposed to put here, Ubuntu asked me to report the
  error, so I did.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 29 15:48:29 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-17 (103 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: heimdal
  Title: package libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (76 days ago)

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

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Simos Xenitellis ]

@Timothy:

There would not be much of a need to collect stats specifically from 
motd.ubuntu.com. The user-agent will just say 'curl' in all cases which is not 
that helpful. 
Also, each distro installation checks every day for security updates, so why 
would anyone bother with motd?

There has been a sad Twitter storm in a tea cup over this, and it makes
otherwise nice people to be negative about Ubuntu.

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1701242] Re: misleading error message if cifs-utils not installed

[Phillip Susi]

That's not something that mount is going to do.


** No longer affects: cifs-utils (Ubuntu)

** Changed in: util-linux (Ubuntu)
   Status: New => Won't Fix

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

Title:
  misleading error message if cifs-utils not installed

Status in util-linux package in Ubuntu:
  Won't Fix

Bug description:
  On Ubuntu 16.04.2: If cifs-utils is not installed the following
  command gives error messages making no sense:

  sudo mount -t cifs -o credentials=~/.credentials
  //192.168.1.2/austausch /media/austausch

  The message is:

  mount: wrong fs type, bad option, bad superblock on //192.168.1.2/austausch,
 missing codepage or helper program, or other error
 (for several filesystems (e.g. nfs, cifs) you might
 need a /sbin/mount. helper program)

 In some cases useful info is found in syslog - try
 dmesg | tail or so.

  The dmesg output is:

  [2408337.346794] CIFS VFS: No username specified

  But the username is specified in .credentials. It should better say:
  "cifs-utils needed, but not installed - Install it now? [Y/n]"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mount 2.27.1-6ubuntu3.2
  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: Thu Jun 29 13:25:41 2017
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701242/+subscriptions

-- 
Mailing list: https://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

[Scott Moser]

** Attachment added: "zesty results"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1693361/+attachment/4905924/+files/1693361-zesty.tar.gz

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

-- 
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:
  Fix Committed
Status in cloud-init source package in Yakkety:
  Fix Committed
Status in cloud-init source package in Zesty:
  Fix Committed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  A cloud-config that contains packages to install (see below) or
  'package_upgrade' will run 'apt-get update'.  That can sometimes fail as a
  result of contention with the apt-daily.service that updates that information.

  Cloud-config showing the problem is just like:

    $ cat my.yaml
    #cloud-config
    packages: ['hello']

  [Test Case]
  lxc-proposed-snapshot is
    
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot
  It publishes an image to lxd with proposed enabled and cloud-init upgraded.

  a.) launch an instance with proposed version of cloud-init and some user-data.
     This is platform independent.  The test case demonstrates lxd.
     $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \
     "package_upgrade: true" > config.yaml
     $ release=xenial
     $ ref=proposed-$release
     $ ./lxc-proposed-snapshot --proposed --publish $release $ref;

  b.) start the instance
     $ name=$release-1693361
     $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml)
     $ sleep 1
     $ lxc exec $name -- tail -f /var/log/cloud-init.log 
/var/log/cloud-init-output.log
     # watch this boot.

   c.) Look for evidence of systemd failure
     journalctl -o short-precise | grep -i break
     journalctl -o short-precise | grep -i order

  [Regression Potential]
  Regression chance here is low.  Its possible that ordering loops
  could occur.  When that does happen, journalctl will mention it.  
Unfortunately
  in such cases systemd somewhat randomly picks a service to kil so behavior
  is somewhat undefined.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=11121fe4

  === End SRU Template ===

  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 the race the invocation
  of apt (e.g. use of "packages:" in the config) will fail.

  There is a lot of discussion online about this change to apt-daily
  (e.g. unattended upgrades happening during business hours, delaying
  boot, etc.) and discussion of potential systemd changes regarding
  timers firing during boot (c.f.
  https://github.com/systemd/systemd/issues/5659).

  While it would be better to solve this in apt itself, I suggest that
  cloud-init be defensive when calling apt and implement some retry
  mechanism.

  Various instances of people running into this issue:

  https://github.com/chef/bento/issues/609
  https://clusterhq.atlassian.net/browse/FLOC-4486
  https://github.com/boxcutter/ubuntu/issues/73
  
https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions

-- 
Mailing list: https://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

[Scott Moser]

$ for rel in xenial yakkety zesty; do lxc-proposed-snapshot --proposed
$rel proposed-$rel --publish || break; done

$ for rel in xenial yakkety zesty; do lxc launch proposed-$rel "--
config=user.user-data=$(cat config.yaml)" test-$rel || break; done

$ sleep 2m

$ for rel in xenial yakkety zesty; do mkdir $rel && ( cd $rel && lxc
exec test-$rel -- journalctl -o short-precise > journal.log && lxc exec
test-$rel -- dpkg-query --show cloud-init > cloud-init-dpkg.txt && lxc
file pull test-$rel/var/log/cloud-init.log cloud-init.log && lxc file
pull test-$rel/var/log/cloud-init-output.log cloud-init-output.log ) ||
break; done

$ for rel in xenial yakkety zesty; do tar -czf /tmp/1693361-$rel.tar.gz
$rel; done


** Attachment added: "xenial results"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1693361/+attachment/4905922/+files/1693361-xenial.tar.gz

-- 
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:
  Fix Committed
Status in cloud-init source package in Yakkety:
  Fix Committed
Status in cloud-init source package in Zesty:
  Fix Committed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  A cloud-config that contains packages to install (see below) or
  'package_upgrade' will run 'apt-get update'.  That can sometimes fail as a
  result of contention with the apt-daily.service that updates that information.

  Cloud-config showing the problem is just like:

    $ cat my.yaml
    #cloud-config
    packages: ['hello']

  [Test Case]
  lxc-proposed-snapshot is
    
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot
  It publishes an image to lxd with proposed enabled and cloud-init upgraded.

  a.) launch an instance with proposed version of cloud-init and some user-data.
     This is platform independent.  The test case demonstrates lxd.
     $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \
     "package_upgrade: true" > config.yaml
     $ release=xenial
     $ ref=proposed-$release
     $ ./lxc-proposed-snapshot --proposed --publish $release $ref;

  b.) start the instance
     $ name=$release-1693361
     $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml)
     $ sleep 1
     $ lxc exec $name -- tail -f /var/log/cloud-init.log 
/var/log/cloud-init-output.log
     # watch this boot.

   c.) Look for evidence of systemd failure
     journalctl -o short-precise | grep -i break
     journalctl -o short-precise | grep -i order

  [Regression Potential]
  Regression chance here is low.  Its possible that ordering loops
  could occur.  When that does happen, journalctl will mention it.  
Unfortunately
  in such cases systemd somewhat randomly picks a service to kil so behavior
  is somewhat undefined.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=11121fe4

  === End SRU Template ===

  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 the race the invocation
  of apt (e.g. use of "packages:" in the config) will fail.

  There is a lot of discussion online about this change to apt-daily
  (e.g. unattended upgrades happening during business hours, delaying
  boot, etc.) and discussion of potential systemd changes regarding
  timers firing during boot (c.f.
  https://github.com/systemd/systemd/issues/5659).

  While it would be better to solve this in apt itself, I suggest that
  cloud-init be defensive when calling apt and implement some retry
  mechanism.

  Various instances of people running into this issue:

  https://github.com/chef/bento/issues/609
  https://clusterhq.atlassian.net/browse/FLOC-4486
  https://github.com/boxcutter/ubuntu/issues/73
  
https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions

-- 
Mailing list: https://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 1700743] Re: incorrect /etc/adjtime

[Jesse Massengill]

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

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

Title:
  incorrect /etc/adjtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.

  I ran hwclock to sync them and got:

  hwclock: Warning: unrecognized third line in adjtime file
  (Expected: `UTC' or `LOCAL' or nothing.)

  my system is running
  util-linux:
    Installed: 2.29-1ubuntu2
    Candidate: 2.29-1ubuntu2
    Version table:
   *** 2.29-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I looked in /etc/adjtime; it does have 'UTC' on the third line...

  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693

  This reporter believed that the problem was a missing newline on the
  end of the third line.

  -There is no newline after 'UTC' in /etc/adjtime on my system.
  -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report.
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.

  EDIT:
  And yet the faulty line in /etc/adjtime is still present.
  Apparently, this solution is not the entire answer.
  END EDIT.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  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
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1700743/+subscriptions

-- 
Mailing list: https://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

[Scott Moser]

** Attachment added: "yakkety results"
   
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1693361/+attachment/4905923/+files/1693361-yakkety.tar.gz

-- 
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:
  Fix Committed
Status in cloud-init source package in Yakkety:
  Fix Committed
Status in cloud-init source package in Zesty:
  Fix Committed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  A cloud-config that contains packages to install (see below) or
  'package_upgrade' will run 'apt-get update'.  That can sometimes fail as a
  result of contention with the apt-daily.service that updates that information.

  Cloud-config showing the problem is just like:

    $ cat my.yaml
    #cloud-config
    packages: ['hello']

  [Test Case]
  lxc-proposed-snapshot is
    
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot
  It publishes an image to lxd with proposed enabled and cloud-init upgraded.

  a.) launch an instance with proposed version of cloud-init and some user-data.
     This is platform independent.  The test case demonstrates lxd.
     $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \
     "package_upgrade: true" > config.yaml
     $ release=xenial
     $ ref=proposed-$release
     $ ./lxc-proposed-snapshot --proposed --publish $release $ref;

  b.) start the instance
     $ name=$release-1693361
     $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml)
     $ sleep 1
     $ lxc exec $name -- tail -f /var/log/cloud-init.log 
/var/log/cloud-init-output.log
     # watch this boot.

   c.) Look for evidence of systemd failure
     journalctl -o short-precise | grep -i break
     journalctl -o short-precise | grep -i order

  [Regression Potential]
  Regression chance here is low.  Its possible that ordering loops
  could occur.  When that does happen, journalctl will mention it.  
Unfortunately
  in such cases systemd somewhat randomly picks a service to kil so behavior
  is somewhat undefined.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=11121fe4

  === End SRU Template ===

  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 the race the invocation
  of apt (e.g. use of "packages:" in the config) will fail.

  There is a lot of discussion online about this change to apt-daily
  (e.g. unattended upgrades happening during business hours, delaying
  boot, etc.) and discussion of potential systemd changes regarding
  timers firing during boot (c.f.
  https://github.com/systemd/systemd/issues/5659).

  While it would be better to solve this in apt itself, I suggest that
  cloud-init be defensive when calling apt and implement some retry
  mechanism.

  Various instances of people running into this issue:

  https://github.com/chef/bento/issues/609
  https://clusterhq.atlassian.net/browse/FLOC-4486
  https://github.com/boxcutter/ubuntu/issues/73
  
https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Horatio Trobinson]

1) This is ideological content and it's not being used to disseminate
technical or factual knowledge that is useful to the user.

I would be less inclined to be critical if the non-relevant information
delivered was content that helped to amplify the work of a world-
renowned charity (say, MSF for example) butthe relevant news I've seen
are just part of a certain Silicon Valley-dominated ideology, and as
such it presents the potential of being inadvertently used as a
propaganda vehicle to advance particular interests of a specific group
of people.

2) It doean't seem that enough precautions have been taken to avoid
makibg motd a central point of failure. It doesn't seem to take into
accoubt that there's a potebtial for privacy and exploit problems
generated for desktop users, without offeribg a straightforward
opportunity to opt out. It's a practice that should at a minimum be part
of an optional and customisable policy kit in enterprise environments.

3) For technical reasons and other reasons explained above, I
respectfuly suggest that this practice should be completely reconsidered
in further detail or discontinued altogether.

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1701180] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le config

[Phillip Susi]

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

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

Title:
  package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet
  est dans un état vraiment incohérent; vous devriez  le réinstaller
  avant de tenter de le configurer.

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  unable to update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  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: Thu Jun 29 07:52:35 2017
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet bsdutils (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2016-06-27 (366 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: le paquet 
est dans un état vraiment incohérent; vous devriez  le réinstaller avant de 
tenter de le configurer.
  UpgradeStatus: Upgraded to zesty on 2017-06-10 (18 days ago)

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

-- 
Mailing list: https://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()

[Launchpad Bug Tracker]

This bug was fixed in the package libgweather - 3.24.1-0ubuntu0.1

---
libgweather (3.24.1-0ubuntu0.1) zesty; urgency=medium

  * New upstream bugfix release
- Fix memory corruption that crashes gnome-shell
  (LP: #1695567) (LP: #1688208) Thanks Tim Lunn for triaging!
  * Drop git_guard-against-segfault.patch, applied in new release

 -- Jeremy Bicha   Mon, 05 Jun 2017 23:06:59 -0400

** Changed in: libgweather (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 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 Released

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()

[Brian Murray]

I also utilized a database query for the bucket associated with this
crash to check the dependencies for the libgweather version of crashes
reported in June of 2017. This is the result:

1091 examined.
(u'3.18.2-0ubuntu0.1', 7)
(u'3.24.0-0ubuntu2', 1082)

So the new version does fix the linked crash.

-- 
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 Released

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 1688208] Update Released

[Brian Murray]

The verification of the Stable Release Update for libgweather 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 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 Released

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()

[Launchpad Bug Tracker]

This bug was fixed in the package libgweather - 3.24.1-0ubuntu0.1

---
libgweather (3.24.1-0ubuntu0.1) zesty; urgency=medium

  * New upstream bugfix release
- Fix memory corruption that crashes gnome-shell
  (LP: #1695567) (LP: #1688208) Thanks Tim Lunn for triaging!
  * Drop git_guard-against-segfault.patch, applied in new release

 -- Jeremy Bicha   Mon, 05 Jun 2017 23:06:59 -0400

** Changed in: libgweather (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 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 Released

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 1695567] Update Released

[Brian Murray]

The verification of the Stable Release Update for libgweather 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 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 Released

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 1700743] Re: incorrect /etc/adjtime

[Jesse Massengill]

** Description changed:

  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.
  
  I ran hwclock to sync them and got:
  
  hwclock: Warning: unrecognized third line in adjtime file
- (Expected: `UTC' or `LOCAL' or nothing.)
+ (Expected: `UTC' or `LOCAL' or nothing.)
  
  my system is running
  util-linux:
-   Installed: 2.29-1ubuntu2
-   Candidate: 2.29-1ubuntu2
-   Version table:
-  *** 2.29-1ubuntu2 500
- 500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 2.29-1ubuntu2
+   Candidate: 2.29-1ubuntu2
+   Version table:
+  *** 2.29-1ubuntu2 500
+ 500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  I looked in /etc/adjtime; it does have 'UTC' on the third line...
  
  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693
  
  This reporter believed that the problem was a missing newline on the end
  of the third line.
  
- -There is no newline after 'UTC' in /etc/adjtime on my system. 
- -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report. 
+ -There is no newline after 'UTC' in /etc/adjtime on my system.
+ -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report.
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.
+ 
+ EDIT:
+ And yet the faulty line in /etc/adjtime is still present.
+ Apparently, this solution is not the entire answer.
+ END EDIT.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  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
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

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

Title:
  incorrect /etc/adjtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.

  I ran hwclock to sync them and got:

  hwclock: Warning: unrecognized third line in adjtime file
  (Expected: `UTC' or `LOCAL' or nothing.)

  my system is running
  util-linux:
    Installed: 2.29-1ubuntu2
    Candidate: 2.29-1ubuntu2
    Version table:
   *** 2.29-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I looked in /etc/adjtime; it does have 'UTC' on the third line...

  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693

  This reporter believed that the problem was a missing newline on the
  end of the third line.

  -There is no newline after 'UTC' in /etc/adjtime on my system.
  -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report.
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.

  EDIT:
  And yet the faulty line in /etc/adjtime is still present.
  Apparently, this solution is not the entire answer.
  END EDIT.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  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
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1700743/+subscriptions

-- 
Mailing list: https://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()

[Brian Murray]

I also utilized a database query for the bucket associated with this
crash to check the dependencies for the libgweather version of crashes
reported in June of 2017.  This is the result:

1030 examined.
{u'3.24.0-0ubuntu2': 1029}

So the new version does seem to fix the linked crash.

-- 
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 1700743] Re: incorrect /etc/adjtime

[Jesse Massengill]

Obviously not, if it is still happening.

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

Title:
  incorrect /etc/adjtime

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.

  I ran hwclock to sync them and got:

  hwclock: Warning: unrecognized third line in adjtime file
  (Expected: `UTC' or `LOCAL' or nothing.)

  my system is running
  util-linux:
    Installed: 2.29-1ubuntu2
    Candidate: 2.29-1ubuntu2
    Version table:
   *** 2.29-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I looked in /etc/adjtime; it does have 'UTC' on the third line...

  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693

  This reporter believed that the problem was a missing newline on the
  end of the third line.

  -There is no newline after 'UTC' in /etc/adjtime on my system.
  -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report.
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.

  EDIT:
  And yet the faulty line in /etc/adjtime is still present.
  Apparently, this solution is not the entire answer.
  END EDIT.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  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
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1700743/+subscriptions

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Timothy R. Chavez]

I should walk back some of what I've said. I don't want to be
inflammatory. I implied Canonical was collecting this information when
they may only in fact be using it to decide which messages to send back
to the client. It's entirely possible that the information is being
"thrown away" after the http response is sent. If that's the case, it
would be great to state it somewhere. Ideally it would be nice to make
all those decisions locally, but I recognize the trade offs in terms of
payload size and complexity. My apologies

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1701162] Re: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed')

[Phillip Susi]

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

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

Title:
  package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount
  is not ready for configuration  cannot configure (current status
  'half-installed')

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  sudo apt upgrade fails. Output is as follows...

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/130 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  dpkg: error processing package mount (--configure):
   package mount is not ready for configuration
   cannot configure (current status 'half-installed')
  Errors were encountered while processing:
   mount
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  I've combed the web for a solution and tried all of the following.
  None of which have resolved the issue...

  sudo apt-get install -f
  sudo apt-get install --fix-broken --fix-missing
  sudo apt-get -f install
  sudo apt-get update –fix-missing
  sudo apt-get autoremove
  sudo apt-get -u dist-upgrade
  sudo apt --reinstall mount

  sudo dpkg –configure -a
  sudo dpkg -r -a

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  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
  AptOrdering:
   mount:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jun 29 00:16:17 2017
  DpkgTerminalLog:
   dpkg: error processing package mount (--configure):
package mount is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package mount is not ready for configuration  cannot configure 
(current status 'half-installed')
  InstallationDate: Installed on 2016-09-02 (300 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount 
is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to zesty on 2017-05-20 (39 days ago)

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

-- 
Mailing list: https://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 1701333] [NEW] building cups without systemd results in error due to 'IdleExitTimeout' undeclared

[Bo Kersey]

Public bug reported:

I'm backporting cups-2.1.3 to trusty and I found an ubuntu patch that
lets cups stop on 30 seconds idle time if it was started on demand by
upstart (ubuntu-cupsd-idleexittimeout-upstart.patch)

All other uses of IdleExitTimeout are enclosed in an a conditional so
that the code is masked if not build with launchd or systemd.  However,
this one is not

This results in the following build error:
cc  -Wall -Wno-format-y2k -Wunused -fPIC -g -fstack-protector 
-Wno-unused-result -Wsign-conversion -Wno-tautological-compare -D_GNU_SOURCE 
-I.. -D_CUPS_SOURCE -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-I/usr/include/libusb-1.0   -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include   -DDBUS_API_SUBJECT_TO_CHANGE 
-D_REENTRANT   -I/usr/include/p11-kit-1   -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT   -c -o main.o main.c
main.c: In function 'upstart_checkin':
main.c:1708:8: error: 'IdleExitTimeout' undeclared (first use in this function)
   if (!IdleExitTimeout)
^
main.c:1708:8: note: each undeclared identifier is reported only once for each 
function it appears in

I have added that conditional the the offending patch and I have
attached it to this bug

Thanks!

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


** Tags: backport

** Attachment added: "updated file 
debian/patches/ubuntu/ubuntu-cupsd-idleexittimeout-upstart.patch"
   
https://bugs.launchpad.net/bugs/1701333/+attachment/4905877/+files/ubuntu-cupsd-idleexittimeout-upstart.patch

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

Title:
  building cups without systemd results in error due to
  'IdleExitTimeout' undeclared

Status in cups package in Ubuntu:
  New

Bug description:
  I'm backporting cups-2.1.3 to trusty and I found an ubuntu patch that
  lets cups stop on 30 seconds idle time if it was started on demand by
  upstart (ubuntu-cupsd-idleexittimeout-upstart.patch)

  All other uses of IdleExitTimeout are enclosed in an a conditional so
  that the code is masked if not build with launchd or systemd.
  However, this one is not

  This results in the following build error:
  cc  -Wall -Wno-format-y2k -Wunused -fPIC -g -fstack-protector 
-Wno-unused-result -Wsign-conversion -Wno-tautological-compare -D_GNU_SOURCE 
-I.. -D_CUPS_SOURCE -D_FORTIFY_SOURCE=2  -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-I/usr/include/libusb-1.0   -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include   -DDBUS_API_SUBJECT_TO_CHANGE 
-D_REENTRANT   -I/usr/include/p11-kit-1   -D_LARGEFILE_SOURCE 
-D_LARGEFILE64_SOURCE -D_THREAD_SAFE -D_REENTRANT   -c -o main.o main.c
  main.c: In function 'upstart_checkin':
  main.c:1708:8: error: 'IdleExitTimeout' undeclared (first use in this 
function)
 if (!IdleExitTimeout)
  ^
  main.c:1708:8: note: each undeclared identifier is reported only once for 
each function it appears in

  I have added that conditional the the offending patch and I have
  attached it to this bug

  Thanks!

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

-- 
Mailing list: https://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 1700884] Re: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: paket util-linux belum siap dikonfigurasi tidak dapat dikonfigurasi (status sekarang 'half-installed'

[Phillip Susi]

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

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

Title:
  package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: paket
  util-linux belum siap dikonfigurasi   tidak dapat dikonfigurasi
  (status sekarang 'half-installed')

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  i dont know, but i can't install some programs

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.2
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun 28 10:58:43 2017
  DpkgTerminalLog:
   dpkg: error processing package util-linux (--configure):
paket util-linux belum siap dikonfigurasi
 tidak dapat dikonfigurasi (status sekarang 'half-installed')
  ErrorMessage: paket util-linux belum siap dikonfigurasi   tidak dapat 
dikonfigurasi (status sekarang 'half-installed')
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.21
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: paket 
util-linux belum siap dikonfigurasi   tidak dapat dikonfigurasi (status 
sekarang 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.3

---
pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

  [Luke Yelavich, Konrad Zapałowicz]
  * Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
where users would experience some combination of:
- Bluetooth headset/speakers listed but not selectable in Sound settings
  (LP: #1283003)
- [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode) (LP: #1438510)
- [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
  to HSP/HFP first (LP: #1582213)
  * Specific patches from upstream used to address the above problems:
- 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch
- 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
- 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
  . Backport from upstream to fix a bug in Xenial where an incorrect
audio profile is applied for a headset connected over Bluetooth
making using it impossible.
- 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch
  . Fix a crash that happens if the BT headset is the only non-monitor
source in the system and the last "phone" stream dies.
- 0700-pulsecore-add-new-card-profile-hook.patch
  . Backport from upstream (commit 7b6260140149) to allow for correct
profile selection.
- 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
  . Backport from upstream waiting for all profiles to connect before
creating a card.

 -- Daniel van Vugt   Tue, 23 May 2017
16:24:14 +0800

** Changed in: pulseaudio (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 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 Released

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 

[Touch-packages] [Bug 1438510] Update Released

[Brian Murray]

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [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 1283003 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]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions

-- 
Mailing list: https://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] Update Released

[Brian Murray]

The verification of the Stable Release Update for pulseaudio 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 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 Released

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)

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.3

---
pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

  [Luke Yelavich, Konrad Zapałowicz]
  * Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
where users would experience some combination of:
- Bluetooth headset/speakers listed but not selectable in Sound settings
  (LP: #1283003)
- [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode) (LP: #1438510)
- [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
  to HSP/HFP first (LP: #1582213)
  * Specific patches from upstream used to address the above problems:
- 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch
- 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
- 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
  . Backport from upstream to fix a bug in Xenial where an incorrect
audio profile is applied for a headset connected over Bluetooth
making using it impossible.
- 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch
  . Fix a crash that happens if the BT headset is the only non-monitor
source in the system and the last "phone" stream dies.
- 0700-pulsecore-add-new-card-profile-hook.patch
  . Backport from upstream (commit 7b6260140149) to allow for correct
profile selection.
- 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
  . Backport from upstream waiting for all profiles to connect before
creating a card.

 -- Daniel van Vugt   Tue, 23 May 2017
16:24:14 +0800

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

Title:
  [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode)

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). 
A2DP is the high quality profile used for Bluetooth speakers and music in 
general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Go to Sound settings and check the device's current "Mode".
  3. If the current Mode is not yet A2DP then try to set it to A2DP
  Expected: The mode is either A2DP by default or can be set to it.

  [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 1283003 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]
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions

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

[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.3

---
pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

  [Luke Yelavich, Konrad Zapałowicz]
  * Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
where users would experience some combination of:
- Bluetooth headset/speakers listed but not selectable in Sound settings
  (LP: #1283003)
- [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
  mode) (LP: #1438510)
- [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
  to HSP/HFP first (LP: #1582213)
  * Specific patches from upstream used to address the above problems:
- 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch
- 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
- 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
  . Backport from upstream to fix a bug in Xenial where an incorrect
audio profile is applied for a headset connected over Bluetooth
making using it impossible.
- 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch
  . Fix a crash that happens if the BT headset is the only non-monitor
source in the system and the last "phone" stream dies.
- 0700-pulsecore-add-new-card-profile-hook.patch
  . Backport from upstream (commit 7b6260140149) to allow for correct
profile selection.
- 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
  . Backport from upstream waiting for all profiles to connect before
creating a card.

 -- Daniel van Vugt   Tue, 23 May 2017
16:24:14 +0800

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth 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 1283003 and bug 1438510. Possibly others too.

  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]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID 

[Touch-packages] [Bug 1582213] Update Released

[Brian Murray]

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

Title:
  [xenial] Bluetooth device doesn't play any sound in A2DP mode unless
  set to HSP/HFP first

Status in bluez package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP 
first. A2DP is the high quality profile used for Bluetooth speakers and music 
in general.

  [Test Case]
  1. Pair a Bluetooth audio device with Ubuntu.
  2. Verify in Sound settings you have it set to A2DP mode.
  3. Turn off and then on the Bluetooth device.
  4. Verify the device has reconnected and if not, force it to in the Bluetooth 
indicator menu.
  5. Open Sound settings again, select the device and verify it's reappeared in 
A2DP mode.
  6. Click 'Test Sound'.
  Expected: Sound can be heard from the Bluetooth 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 1283003 and bug 1438510. Possibly others too.

  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]
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  myuser2936 F pulseaudio
   /dev/snd/controlC2:  myuser2936 F pulseaudio
   /dev/snd/controlC0:  myuser2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Touch-packages] [Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Timothy R. Chavez]

I don't know if this should be a separate issue, but while investigating
this issue and learning about motd-news, I stumbled across this in the
code https://gist.github.com/anonymous/fdc1cab8cb193ca19aa4c663c1ebd1f5
#file-gistfile1-txt-L245 -- While I applaud the creativity, I don't
think it's right for Canonical to be collecting server information into
the USER_AGENT and curl'ing it back to motd.ubuntu.com. First, it's
completely non-obvious. No one would be the wiser that Canonical is
collecting this information if they weren't actually looking at the
code. Second, you have to opt-out of it. Third, by opting out of it,
you're also forced to opt out of critical information about
vulnerabilities, distro EOL messages, etc. In this way, we're sort of
having to "buy" motd-news with information about our servers. That
should be spelled out somewhere, at the very least.

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1700743] Re: incorrect /etc/adjtime

[Phillip Susi]

Then it has already been fixed.


** Changed in: util-linux (Ubuntu)
   Status: New => 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/1700743

Title:
  incorrect /etc/adjtime

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 17.04 I noticed a variation between system time and hardware
  time.

  I ran hwclock to sync them and got:

  hwclock: Warning: unrecognized third line in adjtime file
  (Expected: `UTC' or `LOCAL' or nothing.)

  my system is running
  util-linux:
Installed: 2.29-1ubuntu2
Candidate: 2.29-1ubuntu2
Version table:
   *** 2.29-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  I looked in /etc/adjtime; it does have 'UTC' on the third line...

  There is a similar report and proposed solution at:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706693

  This reporter believed that the problem was a missing newline on the
  end of the third line.

  -There is no newline after 'UTC' in /etc/adjtime on my system. 
  -Manually adding a newline does make the warning not appear when invoking 
hwclock, as suggested by the above report. 
  -However, the proposed solution (adding a final \n to the printf line in 
hwclock.sh) is already present in my /etc/init.d/hwclock.sh.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  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
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1700743/+subscriptions

-- 
Mailing list: https://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 1700526] Re: package uuid-runtime 2.27.1-6ubuntu3.2 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su conf

[Phillip Susi]

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

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.2 failed to install/upgrade: El
  paquete está en un estado grave de inconsistencia - debe reinstalarlo
  antes de intentar su configuración.

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  my computer its power off repently

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jun 25 10:47:38 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-08-27 (303 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.2 failed to install/upgrade: El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 675565] Re: Provide a way to have a ReadOnly model

[Bryan Quigley]

** Changed in: unity-2d
   Status: Triaged => Invalid

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

Title:
  Provide a way to have a ReadOnly model

Status in dee:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in dee package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  It has been requested from various places that we have a way to make a
  Dee.Model read-only.

  My current idea is to provide this using a decorator style API, eg:

DeeModel* dee_read_only_model_new (DeeModel *model);

  Any other ideas welcome

To manage notifications about this bug go to:
https://bugs.launchpad.net/dee/+bug/675565/+subscriptions

-- 
Mailing list: https://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 706854] Re: Support named columns

[Bryan Quigley]

** Changed in: unity-2d
   Status: Triaged => Invalid

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

Title:
  Support named columns

Status in dee:
  Triaged
Status in Unity:
  Triaged
Status in unity-2d:
  Invalid
Status in dee package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Right now you can only access columns by index. It would be very nice
  for ORM-like bindings (fx. dee-qt with QML) to be able to access the
  columns with a human-readable identifier. Eg. instead of row.column_1
  they could do row.display_name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dee/+bug/706854/+subscriptions

-- 
Mailing list: https://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 711345] Re: Unify sound & message menus registration process

[Bryan Quigley]

** Changed in: unity-2d
   Status: Triaged => Invalid

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

Title:
  Unify sound & message menus registration process

Status in Messaging Menu:
  Won't Fix
Status in The Sound Menu:
  Won't Fix
Status in libunity:
  Triaged
Status in Unity:
  Triaged
Status in unity-2d:
  Invalid
Status in libunity package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I would like to propose the unification of the application registration 
process.
  AFAIK, at the moment there is a following situation with the registration 
process:
  1. Sound Menu. Every application registers itself after the first start 
(providing desktop-file location through the dbus). The only preregistered 
application is banshee.
  2. Messages menu. Every application registers itself, placing file with 
desktop-file location into the /usr/share/indicators/messages/applications/ 
folder (or user folder). Default launcher list (evolution, empathy and gwibber) 
is hardcoded, rather than stored in gconf scheme, as indicator-sound does.

  In fact, I see no united way to deal with all that stuff. I suppose, that 
indicator interaction API should be similar in most cases, however in this case 
they are absolutely different.
  First, messages-applications have no dbus-method to register themselves. Yep, 
that's not fatal, it only makes maintainers should care about indicator 
creation.
  And second, sound-applications are unable to preregister themselves during 
the installation. Yep, this is conflicts with SoundMenu spec, but really why 
it's stated in spec? And why it's different from Messages policy? The main 
problem are applications who don't provide any GUI and are not intended to be 
started as usual applications, but as something like user-session daemons. In 
fact I can name only one such application :) — my mpd-sound-menu, in most cases 
user wants it to be started with his session to display MPD status.

  Your suggestions?

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-messages/+bug/711345/+subscriptions

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Timothy R. Chavez]

Just my opinion here..

```
* Sometimes, there's critical information that either we, the distro, or 
perhaps even the local IT administrator of a fleet of systems needs to 
communicate to users at login. Think, "ShellShock", "Heartbleed", "StackClash". 
This seems to happen every few months, in the current state of the world.

* Other times, we need to communicate something about the distribution. EoL 
messages, new feature availability, etc.
```

^^^ Great use of motd-news

```
And sometimes, it's just a matter of presenting a fun fact.
```

^^^ Not a great use of motd-news

I wouldn't want to have to opt out of receiving critical information or
EOL messages just to avoid receiving fun facts. Can we maybe split off
the fun fact stuff into it's own motd-funfact script and have it
disabled by default on the server image?

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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 1628438] Re: seeing "Error reading chunk events: Operation not supported" on MAAS boot

[Launchpad Bug Tracker]

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

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

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

Title:
  seeing "Error reading chunk events: Operation not supported" on MAAS
  boot

Status in linux package in Ubuntu:
  Confirmed
Status in ureadahead package in Ubuntu:
  Confirmed

Bug description:
  Seeing chunk extent read failures on what I believe is a MAAS
  installer boot:

  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/datasource: Error retrieving chunk 
extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/data/previous-datasource: Error retrieving chunk 
extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/data/instance-id: Error retrieving chunk extents: 
Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/data/previous-instance-id: Error retrieving chunk 
extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instance/obj.pkl: Error retrieving chunk extents: 
Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/user-data.txt: Error retrieving 
chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/user-data.txt.i: Error retrieving 
chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/vendor-data.txt: Error retrieving 
chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/vendor-data.txt.i: Error retrieving 
chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/sem/consume_data: Error retrieving 
chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instance/scripts/user_data.sh: Error retrieving chunk 
extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/vendor-cloud-config.txt: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/sem/config_ubuntu_init_switch: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/sem/config_seed_random: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/sem/config_write_files: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/sem/config_set_hostname: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: ureadahead:/etc/hostname: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/data/previous-hostname: Error retrieving chunk 
extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/sem/config_ca_certs: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/sem/config_rsyslog: Error retrieving 
chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/etc/rsyslog.d/20-cloud-config.conf: Error retrieving chunk extents: 
Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/var/lib/cloud/instances/rs3me7/sem/config_users_groups: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: ureadahead:/etc/gshadow: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: ureadahead:/etc/shadow: Error 
retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/home/ubuntu/.profile: Error retrieving chunk extents: Operation not 
supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: 
ureadahead:/home/ubuntu/.bash_logout: Error retrieving chunk extents: Operation 
not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: ureadahead:/home/ubuntu/.bashrc: 
Error retrieving chunk extents: Operation not supported
  Sep 27 23:13:57 clear-teal ureadahead[1066]: ureadahead:/etc/passwd-: Error 
retrieving chunk extents: Operation not supported
  Sep 

[Touch-packages] [Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Zachary Fouts]

Dustin -- thank you for addressing the issue.

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  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
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://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

[ChristianEhrhardt]

As discussed on IRC:
- the default of -g is also going along with a default of jumping any time >a 
threshhold ONCE.
  -x can change that

To be sure I tested that on Xenial:
$ timedatectl 
  Local time: Thu 2017-06-29 15:58:29 UTC
  Universal time: Thu 2017-06-29 15:58:29 UTC
RTC time: Thu 2017-06-29 15:58:29
   Time zone: Etc/UTC (UTC, +)
 Network time on: yes
NTP synchronized: yes
 RTC in local TZ: no

ubuntu@x-ntp-skip-test:~$ sudo timedatectl set-ntp false
ubuntu@x-ntp-skip-test:~$ sudo timedatectl set-time 01:02:03
ubuntu@x-ntp-skip-test:~$ timedatectl 
  Local time: Thu 2017-06-29 01:02:05 UTC
  Universal time: Thu 2017-06-29 01:02:05 UTC
RTC time: Thu 2017-06-29 01:02:05
   Time zone: Etc/UTC (UTC, +)
 Network time on: no
NTP synchronized: no
 RTC in local TZ: no


$ sudo add-apt-repository ppa:ci-train-ppa-service/2828
[...]
$ sudo apt install ntp
[...]
$ systemctl status ntp
● ntp.service - LSB: Start NTP daemon
   Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
   Active: active (running) since Thu 2017-06-29 01:04:36 UTC; 14h ago
[...]
$ timedatectl 
  Local time: Thu 2017-06-29 16:02:50 UTC
  Universal time: Thu 2017-06-29 16:02:50 UTC
RTC time: Thu 2017-06-29 01:05:33

Watch the time the service was started and the time it has now.
It it did warp once initially as it is intended.

If I skew the time later it will not instant-reset again.

Then I dropped the -g from the options to be sure it is this what makes it work 
and it did not time warp anymore as expected - the offset is known but not 
solved.
$ ntpq -p
 remote   refid  st t when poll reach   delay   offset  jitter
==
[...]
 golf.zq1.de 192.53.103.103   2 u   51   641   13.436  5456358 5456358
And afterwards the service goes active (exited) as according to the -g doc the 
daemon gives up without -g on too big time deltas.

That said I summarize - good to go on sponsoring trusty and with the
SRUs in that regard.

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

[Touch-packages] [Bug 622443] Re: Implement a DeeScanIndex

[Bryan Quigley]

** Changed in: unity-2d
   Status: Triaged => Invalid

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

Title:
  Implement a DeeScanIndex

Status in dee:
  Triaged
Status in Unity:
  Triaged
Status in unity-2d:
  Invalid
Status in dee package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  It will be most handy to have a DeeScanIndex that does what would be
  similar to a table scan in SQL. It, not maintaining any state, but
  analyzing the entire model on each lookup.

  If used cleverly in conjunction with DeeFilterModel performance
  wouldn't necessarily be that bad.

  NOTE: This index type could easily support prefix queries as well (as
  opposed to the current DeeHashIndex)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dee/+bug/622443/+subscriptions

-- 
Mailing list: https://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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Dustin Kirkland ]

Howdy!  I'm the author of the motd-news code, as well as the story in
the subject of this bug.

Note that motd.ubuntu.com has been updated to say:

" * Ubuntu 16.10 will reach end of life on Wednesday, July 20th"

It may be useful to explain a bit of the design of motd-news.  Note that
much of this was copied over from my comment on the Hacker News thread:
https://news.ycombinator.com/edit?id=14663947

By design:

- Asynchronously, about 60 seconds after boot, a systemd timer fires
which runs "/etc/update-motd.d/50-motd-news --force"

- It sources 3 admin-editable config variables in /etc/default/motd-
news.  The defaults are: ENABLED=1, URLS="https://motd.ubuntu.com;,
WAIT="5"

- The admin can disable it entirely (ENABLED=0), change or add other
MOTD news sources (your corporate IT team could run its own), and change
the wait time in seconds

- If it's enabled, that systemd timer job will loop over each of the
URLS (note, that it's important that these should be https with valid
SSL certificates), trim them to 80 characters per line, and a maximum of
10 lines, and concatenate them to a cache file in /var/cache/motd-news

- Every ~12 hours thereafter (with a little bit of random timer
fuzzing), this systemd timer job will re-run and update the /var/cache
/motd-news

- Upon login, the contents of /var/cache/motd-news is just printed to
screen.  There was a bug (fixed now, working its way through the Ubuntu
update process), in that an empty cache file was not getting, if the
fetch failed, so the fetch was retried every time (and failed every
time, with the $WAIT delay of 5 seconds).  Obviously, it was a simple
fix.

As I am generally responsible for this feature in Ubuntu (as the Ubuntu
Product Manager for the design, and the Ubuntu Core Developer for the
implementation) I'll also respond to the discussion about this feature
being included in Ubuntu at all...

- Back in 2009, Ubuntu was the first distribution to add the concept of
a "dynamic MOTD", by introducing the /etc/update-motd.d/* structure of
scripts.  I originally implemented it for Landscape (a commercial
package management system by Canonical), but it has since also been
adopted by Debian, Amazon Linux, and others.

- It's a flexible framework that enables distro packages or
administrators to add executable scripts in /etc/update-motd.d/* to
generate informative, interesting messages displayed at login.

- This was quite interesting, in that for almost 40 years of Linux/UNIX,
the "Message of the Day" was anything but that...  It was a message that
was created at one point in time, when the distro released, and that's
about it.  And we managed to change that.

- If you look in your Ubuntu's /etc/update-motd.d/, you'll see a set of
scripts.  One prints the generic "welcome" banner.  The next one prints
3 links, as to where to find help.  You'll also find one that counts and
displays the number of package updates available for the local system.
Another tells you if a reboot is required.

- All of these are locally generated, based on local information
available on the system.

- In Ubuntu 17.04, we added /etc/update-motd.d/50-motd-news.  This is
the script who's design is described above.  The motivation is
threefold:

* Sometimes, there's critical information that either we, the distro, or
perhaps even the local IT administrator of a fleet of systems needs to
communicate to users at login.  Think, "ShellShock", "Heartbleed",
"StackClash".  This seems to happen every few months, in the current
state of the world.

* Other times, we need to communicate something about the distribution.
EoL messages, new feature availability, etc.

* And sometimes, it's just a matter of presenting a fun fact.  News from
the world of Ubuntu.  Or even your own IT department.  Such was the case
with the Silicon Valley / HBO message.  It was just an interesting
tidbit of potpourri from the world of Ubuntu.  Last week's message
actually announced an Ubuntu conference in Latin America.  The week
before, we linked to an article asking for feedback on Kubuntu.  Before
that, we announced the availability of Extended Security Maintenance
updates for 12.04.  And so on.

- There is a team of engineering managers at Canonical (the ~ubuntu-motd
team in Launchpad), all of who have shared write access to the source
code repository (lp:ubuntu-motd in Launchpad).  Going forward, we're
going to review one another's proposed message merges.  In fact, that's
an open source repository.  You're welcome to propose your own messages
for merging, if you have a well formatted, informative message for
Ubuntu users.  We'll be happy to review and include them in the future.

As always, I'm impressed with the critical analysis of the Ubuntu
community.  We, the Ubuntu ecosystem, are held by the Ubuntu community
to a very high standard, and we're quite humbled by that.  Thank you for
the continued feedback and response.

Cheers,
Dustin

-- 
You received this bug notification because you are a member 

[Touch-packages] [Bug 1701309] [NEW] package libglib2.0-dev 2.52.0-1 failed to install/upgrade: tentative de remplacement de « /usr/bin/gdbus-codegen », qui appartient aussi au paquet libglib2.0-dev-b

[dridri]

Public bug reported:

?

ProblemType: Package
DistroRelease: Kali 2017.1
Package: libglib2.0-dev 2.52.0-1
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.3
Architecture: amd64
Date: Thu Jun 29 17:45:50 2017
ErrorMessage: tentative de remplacement de « /usr/bin/gdbus-codegen », qui 
appartient aussi au paquet libglib2.0-dev-bin 2.52.0-1
InstallationDate: Installed on 2017-06-16 (13 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.23kali1
 apt  1.4
SourcePackage: glib2.0
Title: package libglib2.0-dev 2.52.0-1 failed to install/upgrade: tentative de 
remplacement de « /usr/bin/gdbus-codegen », qui appartient aussi au paquet 
libglib2.0-dev-bin 2.52.0-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package kali-rolling third-party-packages

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

Title:
  package libglib2.0-dev 2.52.0-1 failed to install/upgrade: tentative
  de remplacement de « /usr/bin/gdbus-codegen », qui appartient aussi au
  paquet libglib2.0-dev-bin 2.52.0-1

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Kali 2017.1
  Package: libglib2.0-dev 2.52.0-1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.3
  Architecture: amd64
  Date: Thu Jun 29 17:45:50 2017
  ErrorMessage: tentative de remplacement de « /usr/bin/gdbus-codegen », qui 
appartient aussi au paquet libglib2.0-dev-bin 2.52.0-1
  InstallationDate: Installed on 2017-06-16 (13 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.23kali1
   apt  1.4
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.52.0-1 failed to install/upgrade: tentative 
de remplacement de « /usr/bin/gdbus-codegen », qui appartient aussi au paquet 
libglib2.0-dev-bin 2.52.0-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1701309/+subscriptions

-- 
Mailing list: https://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 1701163] Re: package console-setup-linux 1.165 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-confi

[Hans Joachim Desserud]

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

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

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

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

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

Status in console-setup package in Ubuntu:
  New

Bug description:
  its corrupt many times so give us ubuntu which does not have graphics
  issues in the pc

  ProblemType: Package
  DistroRelease: Debian 9
  Package: console-setup-linux 1.165
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 24 10:52:56 2017
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  InstallationDate: Installed on 2017-06-23 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.24
   apt  1.2.20
  SourcePackage: console-setup
  Title: package console-setup-linux 1.165 failed to install/upgrade: trying to 
overwrite '/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1701163/+subscriptions

-- 
Mailing list: https://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 831850] Re: Hacky shared-library attribute on GIR

[Bryan Quigley]

** Changed in: unity-2d
   Status: Confirmed => Invalid

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

Title:
  Hacky shared-library attribute on GIR

Status in libunity:
  Confirmed
Status in Unity:
  Confirmed
Status in unity-2d:
  Invalid
Status in libunity package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  The shared-library attribute as added on the  element in
  the valac-generated GIR file by a nasty sed hack in the Makefile.am.
  We should use the --shared-library switch to g-ir-compiler instead, as
  mentioned on https://bugzilla.gnome.org/show_bug.cgi?id=642576#c1

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/831850/+subscriptions

-- 
Mailing list: https://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 844211] Re: It should be possible to check the visiliby of a LauncherEntry

[Bryan Quigley]

** Changed in: unity-2d
   Status: Confirmed => Invalid

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

Title:
  It should be possible to check the visiliby of a LauncherEntry

Status in libunity:
  Confirmed
Status in Unity:
  Confirmed
Status in unity-2d:
  Invalid
Status in libunity package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  An Unity.LauncherEntry should provide a method to get if the entry is
  actually shown on the panel and a signal to be notified about
  visbility changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/844211/+subscriptions

-- 
Mailing list: https://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 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install

[Steve Langasek]

** Changed in: python3.5 (Ubuntu Xenial)
 Assignee: (unassigned) => Matthias Klose (doko)

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

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Confirmed
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  New
Status in python3.5 source package in Xenial:
  New
Status in python2.7 source package in Yakkety:
  New
Status in python3.5 source package in Yakkety:
  New
Status in python2.7 source package in Zesty:
  New
Status in python3.5 source package in Zesty:
  New

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+subscriptions

-- 
Mailing list: https://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

[Gunnar Hjalmarsson]

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

@Sebastien: The POT file in that MP seems to cover it. Especially the
strings from formatter-desktop.cpp are included. So the commit ought to
be enough 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 1691901] Re: [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

[Dustin Kirkland ]

** Description changed:

  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.
- 
  
  === SRU ===
  
  [ IMPACT ]
  
  This bug affects Ubuntu 17.04 systems which cannot reach the internet
  (more specifically, https://motd.ubuntu.com).  There is a bug in the
  implementation of /etc/update-motd.d/50-news whereby the failure of the
  curl fetch of the motd news causes a 5-second delay.  This should not be
  the case.  By design, the motd is fetched in the background, by a
  systemd timer, and refreshed every ~12 hours, also in the background.
  On login, the script should just cat the cache file.  If the cache file
  isn't found, then it will try to fetch a new motd.  In the firewalled
  system case, the background fetch failed, AND didn't create an empty
  file.  The fix as attached simply ensures that an empty file is created
  if the curl fetch fails.  This eliminates the login delay and solves the
  bug.  Every 12 hours, the curl will be retried, quietly in the
  background, so if the curl failure happened for temporary reasons, it'll
  recover, gracefully, eventually.
  
  [ TEST CASE ]
  
  You can either test this on a firewalled system.  Or, if you can hack an
  entry in your local /etc/hosts for motd.ubuntu.com for an invalid IP
  address.  Without the fix, you'll experience a 5 second delay on login.
  With the fix, you'll login immediately.
  
  Failure case:
  
  $ lxc launch ubuntu:17.04 LP1691901
  $ lxc exec LP1691901 bash
  # ssh-import-id kirkland
  # echo 192.168.0.0 motd.ubuntu.com >> /etc/hosts
  # rm -f /var/cache/motd-news
  # exit
  $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
  real0m5.333s
  user0m0.016s
  sys 0m0.000s
  
- Apply the fix.  Note that it'll take one run (might be a login, a
- reboot, or the 12-hourly timer) to create the file:
+ Apply the fix.
  
- $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
- real0m5.357s
- user0m0.016s
- sys 0m0.004s
  $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
  real0m0.316s
  user0m0.008s
  sys 0m0.008s
  
  [ REGRESSION ]
  
- This is a super simple, safe, 2-line fix with minimal regression
- potential:
+ This is a simple, safe fix with minimal regression potential:
  
- diff -Nru base-files-9.6ubuntu13/update-motd.d/50-motd-news 
base-files-9.6ubuntu13.1/update-motd.d/50-motd-news
- --- base-files-9.6ubuntu13/update-motd.d/50-motd-news 2017-02-15 
13:54:04.0 -0600
- +++ base-files-9.6ubuntu13.1/update-motd.d/50-motd-news   2017-06-29 
09:22:31.0 -0500
- @@ -111,6 +111,8 @@
-   safe_print "$NEWS"
-   # Try to update the cache
-   safe_print "$NEWS" 2>/dev/null >$CACHE || true
- + else
- + : > "$CACHE"
-   fi
+ diff -Nru base-files-9.6ubuntu13/update-motd.d/50-motd-news 
base-files-9.6ubuntu13.2/update-motd.d/50-motd-news
+ --- base-files-9.6ubuntu13/update-motd.d/50-motd-news   2017-02-15 
13:54:04.0 -0600
+ +++ base-files-9.6ubuntu13.2/update-motd.d/50-motd-news 2017-06-29 
10:43:05.0 -0500
+ @@ -51,9 +51,13 @@
+  # If we're not forcing an update, and we have a cached motd-news file,
+  # then just print it and exit as quickly as possible, for login performance.
+  # Note that systemd should keep this cache file up to date, asynchronously
+ -if [ "$FORCED" != "1" ]  && [ -r $CACHE ]; then
+ -   echo
+ -   safe_print $CACHE
+ +if [ "$FORCED" != "1" ]; then
+ +   if [ -r $CACHE ]; then
+ +   echo
+ +   safe_print $CACHE
+ +   else
+ +   : > $CACHE
+ +   fi
+ exit 0
+  fi
+  
+ @@ -111,7 +115,9 @@
+ safe_print "$NEWS"
+ # Try to update the cache
+ safe_print "$NEWS" 2>/dev/null >$CACHE || true
+ -   fi
+ +   else
+ +   : > "$CACHE"
+ +   fi
   done
   rm -f "$NEWS" "$NEWS.err"
- 
+  exit 0
  
  --
  [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
  

[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Steve Langasek]

** Summary changed:

- No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates
+ unattended-upgrades does not block shutdown of system, as it is designed to

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

-- 
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:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

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 742732] Re: Add ability to query unity for capabilities/version

[Bryan Quigley]

** Changed in: unity-2d
   Status: Triaged => Invalid

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

Title:
  Add ability to query unity for capabilities/version

Status in libunity:
  Triaged
Status in Unity:
  Triaged
Status in unity-2d:
  Invalid
Status in libunity package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I develop deja-dup.  I currently use an appindicator to convey
  progress and to show a few menu items during a backup.  For natty, I
  was excited to port those over to the launcher icon support in
  libunity and do away with the appindicator.

  However, I now understand that dynamic QLs won't be available in time
  for natty (bug 729074).  So I may go back to appindicators for natty.

  But this got me thinking.  Imagine for oneiric, when QLs are fixed.
  And the same version of deja-dup could be run in both natty and
  oneiric.

  Ideally there would be a way to query version or (even more ideally)
  capabilities.  So that I could use either an appindicator or libunity
  depending on how capable the version of unity is.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libunity3 3.6.8-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
  Uname: Linux 2.6.38-7-generic x86_64
  Architecture: amd64
  Date: Fri Mar 25 15:55:57 2011
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_GB.utf8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: libunity
  UpgradeStatus: Upgraded to natty on 2010-09-28 (178 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity/+bug/742732/+subscriptions

-- 
Mailing list: https://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 747677] Re: [FFE] Need API to set urgency from background process

[Bryan Quigley]

** Changed in: unity-2d
   Status: Confirmed => Invalid

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

Title:
  [FFE] Need API to set urgency from background process

Status in Ayatana Design:
  Fix Released
Status in libunity:
  Fix Released
Status in Ubuntu One Client:
  Fix Released
Status in Ubuntu One Control Panel:
  Fix Released
Status in Unity:
  Fix Released
Status in unity-2d:
  Invalid
Status in Unity Foundations:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in ubuntuone-client package in Ubuntu:
  Fix Released
Status in ubuntuone-control-panel package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  We need to be able to set a launcher on the panel as urgent in some
  cases, from a background process which has no open windows or UI, such
  as ubuntuone-syncdaemon. Currently the only way to do this is to start
  the ubuntuone-control-panel-gtk application and then set its window to
  urgent, which is rather intrusive and annoying. It would be much
  better to just set the launcher as urgent instead, so the user can
  click on the icon to open the control panel when they decide to.

  This bug is tied deeply together with bug #747311 "Launcher - Remove
  the capability for Launcher icons to be overlaid with emblems" and for
  FFE they should be reviewed together.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/747677/+subscriptions

-- 
Mailing list: https://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 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install

[Steve Langasek]

** Also affects: python2.7 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: python3.5 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: python2.7 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: python3.5 (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: python2.7 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: python3.5 (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 python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1682934

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Confirmed
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  New
Status in python3.5 source package in Xenial:
  New
Status in python2.7 source package in Yakkety:
  New
Status in python3.5 source package in Yakkety:
  New
Status in python2.7 source package in Zesty:
  New
Status in python3.5 source package in Zesty:
  New

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+subscriptions

-- 
Mailing list: https://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 1701157] Re: package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

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

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

Title:
  package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  unknown the system want to send the bug report

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libpam-systemd:amd64 231-9ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Wed Jun 28 15:23:07 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-05-02 (422 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 231-9ubuntu5 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/systemd/+bug/1701157/+subscriptions

-- 
Mailing list: https://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: [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

[Robie Basak]

16:03  kirkland: ^ what happens on first login? That'll still be
delayed, right? So the bug is being reduced in scope, but not being
fixed entirely?

16:03  If the first login is before the timer has run for the
first time, that is, which seems likely.

16:04  rbasak: true

16:04  rbasak: that's an easy fix, though, just one more line
to add

16:05  rbasak: would you like me to fix that?

16:05  I think it would be a good idea, yeah

16:05  kirkland: yes please. Probably better for the SRU process
to do it fewer times :)

-- 
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:
  [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

Status in base-files package in Ubuntu:
  Fix Committed
Status in base-files source package in Zesty:
  Fix Committed
Status in base-files source package in Artful:
  Fix Committed

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.

  
  === SRU ===

  [ IMPACT ]

  This bug affects Ubuntu 17.04 systems which cannot reach the internet
  (more specifically, https://motd.ubuntu.com).  There is a bug in the
  implementation of /etc/update-motd.d/50-news whereby the failure of
  the curl fetch of the motd news causes a 5-second delay.  This should
  not be the case.  By design, the motd is fetched in the background, by
  a systemd timer, and refreshed every ~12 hours, also in the
  background.  On login, the script should just cat the cache file.  If
  the cache file isn't found, then it will try to fetch a new motd.  In
  the firewalled system case, the background fetch failed, AND didn't
  create an empty file.  The fix as attached simply ensures that an
  empty file is created if the curl fetch fails.  This eliminates the
  login delay and solves the bug.  Every 12 hours, the curl will be
  retried, quietly in the background, so if the curl failure happened
  for temporary reasons, it'll recover, gracefully, eventually.

  [ TEST CASE ]

  You can either test this on a firewalled system.  Or, if you can hack
  an entry in your local /etc/hosts for motd.ubuntu.com for an invalid
  IP address.  Without the fix, you'll experience a 5 second delay on
  login.  With the fix, you'll login immediately.

  Failure case:

  $ lxc launch ubuntu:17.04 LP1691901
  $ lxc exec LP1691901 bash
  # ssh-import-id kirkland
  # echo 192.168.0.0 motd.ubuntu.com >> /etc/hosts
  # rm -f /var/cache/motd-news
  # exit
  $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
  real0m5.333s
  user0m0.016s
  sys 0m0.000s

  Apply the fix.  Note that it'll take one run (might be a login, a
  reboot, or the 12-hourly timer) to create the file:

  $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
  real0m5.357s
  user0m0.016s
  sys 0m0.004s
  $ time ssh root@$(lxc list | grep LP1691901 | awk '{print $6}') true
  real0m0.316s
  user0m0.008s
  sys 0m0.008s

  [ REGRESSION ]

  This is a super simple, safe, 2-line fix with minimal regression
  potential:

  diff -Nru base-files-9.6ubuntu13/update-motd.d/50-motd-news 
base-files-9.6ubuntu13.1/update-motd.d/50-motd-news
  --- base-files-9.6ubuntu13/update-motd.d/50-motd-news 2017-02-15 
13:54:04.0 -0600
  +++ base-files-9.6ubuntu13.1/update-motd.d/50-motd-news   2017-06-29 
09:22:31.0 -0500
  @@ -111,6 +111,8 @@
safe_print "$NEWS"
# Try to update the cache
safe_print "$NEWS" 2>/dev/null >$CACHE || true
  + else
  + : > "$CACHE"
fi
   done
   rm -f "$NEWS" "$NEWS.err"

  
  --
  [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 

[Touch-packages] [Bug 953801] Re: Word order error in RTL language

[Bryan Quigley]

** Changed in: unity-2d (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Word order error in RTL language

Status in Ubuntu Translations:
  Triaged
Status in unity-2d:
  Fix Released
Status in pango1.0 package in Ubuntu:
  New
Status in unity-2d package in Ubuntu:
  Invalid

Bug description:
  Dear maintainer and developer:

  I am from Ubuntu Uyghur Translation group.
  When displaying strings which starts with English words, the position of the 
English word in not correct. 
  please look at attached sreenshot.
  Translation of the "Ubuntu Software Center" in Uyghur is not correctly 
displayed on right top corner. On the other two places is displayed correctly.

  This problem occured in Ubuntu, when translation starts whith English
  words(in Uyghur language).

  This is very seriues problem.
  Please fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/953801/+subscriptions

-- 
Mailing list: https://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 1701298] [NEW] ssh_config should include /etc/ssh/ssh_config.d/* by default

[Erich E. Hoover]

Public bug reported:

It is not currently possible to deploy packages with system-specific SSH 
configuration settings without modifying the ssh_config file.  Ideally the 
default ssh_config file would simply contain:
Include /etc/ssh/ssh_config.d/*
as this would allow packages to deploy such settings without tampering with the 
main ssh_config file.

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

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

Title:
  ssh_config should include /etc/ssh/ssh_config.d/* by default

Status in openssh package in Ubuntu:
  New

Bug description:
  It is not currently possible to deploy packages with system-specific SSH 
configuration settings without modifying the ssh_config file.  Ideally the 
default ssh_config file would simply contain:
  Include /etc/ssh/ssh_config.d/*
  as this would allow packages to deploy such settings without tampering with 
the main ssh_config file.

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

-- 
Mailing list: https://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 1664346] Re: Missing translatable strings in translation template

[Gunnar Hjalmarsson]

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

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

Title:
  Missing translatable strings in translation template

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

Bug description:
  Some of the translatable strings in indicator-datetime, particularly
  the strings from the GSettings schema file, and utils.c, are missing
  from the translation template. This is likely the reason for some of
  the existing issues related to time formats being wrong in some
  locales.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1664346/+subscriptions

-- 
Mailing list: https://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

[Gunnar Hjalmarsson]

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

Marking this bug as a duplicate, since there is an 'almost solution'
available for the other bug.

** This bug has been marked a duplicate of bug 1664346
   Missing translatable strings in translation template

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