[Touch-packages] [Bug 1702459] [NEW] Failed to send request: 'str' object has no attribute 'decode' on Ubuntu 16.04

[Erltoichi]

Public bug reported:

The code attached below generates an error on Ubuntu 16.04 LTS with
python3 default package installed (python3 --version returns 3.5.2).

The error message is:
«Failed to send request: 'str' object has no attribute 'decode'»

The code works fine on Ubuntu 17.04 and Fedora 25 (both python3 --version 
returning 3.5.3). The code also runs on Ubuntu 16.04 LTS with self-compiled 
from source python 3.6.1.
Also, the code has been running ok for over a year on Ubuntu 16.04 LTS - it 
only fails since mid June 2017.
Not sure where the issue is, probably in Ubuntu package for python or in python 
version 3.5.2.

from datetime import datetime,date,time,timezone
import tweepy as twitter


def sendToTwitter():
consumer_key='...'
consumer_secret='...'
access_token_key='...'
access_token_secret='..'
#connect to the twitter api
message = "tweet test"
print("trying to send the tweet...")
try:
auth = twitter.OAuthHandler(consumer_key, consumer_secret)
auth.set_access_token(access_token_key, access_token_secret)
api = twitter.API(auth)
status = api.update_status(status=message)
print("tweet sent")
except Exception as e:
print("error while tweeting. reason : " + str(e))
return
sendToTwitter()

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Failed to send request: 'str' object has no attribute 'decode' on
  Ubuntu 16.04

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  The code attached below generates an error on Ubuntu 16.04 LTS with
  python3 default package installed (python3 --version returns 3.5.2).

  The error message is:
  «Failed to send request: 'str' object has no attribute 'decode'»

  The code works fine on Ubuntu 17.04 and Fedora 25 (both python3 --version 
returning 3.5.3). The code also runs on Ubuntu 16.04 LTS with self-compiled 
from source python 3.6.1.
  Also, the code has been running ok for over a year on Ubuntu 16.04 LTS - it 
only fails since mid June 2017.
  Not sure where the issue is, probably in Ubuntu package for python or in 
python version 3.5.2.

  from datetime import datetime,date,time,timezone
  import tweepy as twitter

  
  def sendToTwitter():
  consumer_key='...'
  consumer_secret='...'
  access_token_key='...'
  access_token_secret='..'
  #connect to the twitter api
  message = "tweet test"
  print("trying to send the tweet...")
  try:
  auth = twitter.OAuthHandler(consumer_key, consumer_secret)
  auth.set_access_token(access_token_key, access_token_secret)
  api = twitter.API(auth)
  status = api.update_status(status=message)
  print("tweet sent")
  except Exception as e:
  print("error while tweeting. reason : " + str(e))
  return
  sendToTwitter()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1702459/+subscriptions

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

[Touch-packages] [Bug 1702474] [NEW] package openssl 1.0.2g-1ubuntu11 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[peter dirnberger]

Public bug reported:

I was trying to install google earth for linux debian 64 bit

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: openssl 1.0.2g-1ubuntu11
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.1
Architecture: amd64
Date: Wed Jul  5 22:15:03 2017
DuplicateSignature:
 package:openssl:1.0.2g-1ubuntu11
 Setting up automake (1:1.15-5ubuntu1) ...
 update-alternatives: using /usr/bin/automake-1.15 to provide /usr/bin/automake 
(automake) in auto mode
 dpkg: error processing package openssl (--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-06-01 (34 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: openssl
Title: package openssl 1.0.2g-1ubuntu11 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check zesty

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

Title:
  package openssl 1.0.2g-1ubuntu11 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in openssl package in Ubuntu:
  New

Bug description:
  I was trying to install google earth for linux debian 64 bit

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: openssl 1.0.2g-1ubuntu11
  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.1
  Architecture: amd64
  Date: Wed Jul  5 22:15:03 2017
  DuplicateSignature:
   package:openssl:1.0.2g-1ubuntu11
   Setting up automake (1:1.15-5ubuntu1) ...
   update-alternatives: using /usr/bin/automake-1.15 to provide 
/usr/bin/automake (automake) in auto mode
   dpkg: error processing package openssl (--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-06-01 (34 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: openssl
  Title: package openssl 1.0.2g-1ubuntu11 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Dimitri John Ledkov]

127.0.0.53 stub resolver was only introduced in v231, thus there is
nothing to fix in xenial.

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

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

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

[Touch-packages] [Bug 1681046] Re: package libuuid1:i386 2.27.1-6ubuntu3.2 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente

[Launchpad Bug Tracker]

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

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

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

Title:
  package libuuid1:i386 2.27.1-6ubuntu3.2 failed to install/upgrade: il
  pacchetto si trova in uno stato di inconsistenza critico: è
  consigliato  installarlo nuovamente prima di tentare la
  configurazione.

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libuuid1:i386 2.27.1-6ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Apr  6 22:30:09 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-06  22:29:37
   Commandline: /usr/bin/unattended-upgrade
   Install: linux-headers-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), 
linux-headers-4.4.0-72:amd64 (4.4.0-72.93, automatic), 
linux-image-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic), 
linux-image-extra-4.4.0-72-generic:amd64 (4.4.0-72.93, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), 
linux-libc-dev:amd64 (4.4.0-71.92, 4.4.0-72.93), linux-image-generic:amd64 
(4.4.0.71.77, 4.4.0.72.78), chromium-codecs-ffmpeg-extra:amd64 
(56.0.2924.76-0ubuntu0.16.04.1268, 57.0.2987.98-0ubuntu0.16.04.1276), 
linux-generic:amd64 (4.4.0.71.77, 4.4.0.72.78), lightdm:amd64 (1.18.3-0ubuntu1, 
1.18.3-0ubuntu1.1), liblightdm-gobject-1-0:amd64 (1.18.3-0ubuntu1, 
1.18.3-0ubuntu1.1)
  ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
  InstallationDate: Installed on 2016-05-22 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: util-linux
  Title: package libuuid1:i386 2.27.1-6ubuntu3.2 failed to install/upgrade: il 
pacchetto si trova in uno stato di inconsistenza critico: è consigliato  
installarlo nuovamente prima di tentare la configurazione.
  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/1681046/+subscriptions

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

[Touch-packages] [Bug 1604497] Re: Pulseaudio does not start

[Rkimber]

I'm now using 17.04 and no longer have the problem

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

Title:
  Pulseaudio does not start

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu Mate 16.04 with the current updates.

  When I start the computer, pulseaudio is not working after I've logged
  in.

  If I type:
   start-pulseaudio-x11
  from the command line, I get
  "Connection failure: Connection refused
  pa_context_connect() failed: Connection refused"
  and I cannot play any sound.

  If I type pulseaudio& on the command line, I can get sound in some
  applications (e.g. Audacity) but not others (e.g. Firefox or other
  browsers).  At some point a command line message appears that says:
  "E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
  causes include: the remote application did not send a reply, the
  message bus security policy blocked the reply, the reply timeout
  expired, or the network connection was broken."

  I'm not clear why there's a reference to bluez5-util, since I don't
  have bluetooth on my machine.

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Jul 19 17:43:11 2016
  InstallationDate: Installed on 2016-05-10 (70 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Z97X-UD3H, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD3H-CF
  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: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-UD3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Dimitri John Ledkov]

** Changed in: systemd (Ubuntu Xenial)
Milestone: ubuntu-16.04.3 => None

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

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

[Touch-packages] [Bug 1367028] Re: [MIR] system-image

[Łukasz Zemczak]

** Changed in: system-image (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  [MIR] system-image

Status in system-image package in Ubuntu:
  Won't Fix
Status in system-image-snappy package in Ubuntu:
  Won't Fix

Bug description:
  Availability: universe

  Rationale: system-image is the client for image based upgrades.  It is
  a core component and thus seeded in Ubuntu Touch.

  Security: No known issues.

  QA: Well supported upstream and in Ubuntu.  Package has build-time
  unittests and DEP-8 tests.

  UI standards: n/a

  Dependencies: All non-main build- and run-time dependencies already or
  will soon have MIRs.

  Standards compliance: No known issues.

  Maintenance: No known issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1367028/+subscriptions

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

[Touch-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

[Daniel van Vugt]

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Touch-packages] [Bug 1701852] Re: (xenial+) apt-cache fails to run if a single sources.list.d entry is not readable

[Julian Andres Klode]

I'm not yet sure about how to deal with this bug, but non-world-readable
files are generally considered unsupported by the apt team, they cause
errors everywhere in the package management stack.

** Changed in: apt (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  (xenial+) apt-cache fails to run if a single sources.list.d entry is
  not readable

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When evaluating:

  https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
  tools/+bug/1700611

  On 16.04 and greater, apt-cache fails to run if a single
  sources.list.d is not readable (by the current user).  On Trusty, the
  behavior was a bit more friendly in that it would run and just not
  show results from the file that cannot be read.

  My expectation is that when run it would warn if any .list file could
  not be read, but show results for everything it can see.

  This terminal interaction shows the problem (trusty and precise behave
  the same here):

  ubuntu@precise-esm:~$ ll 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list
  -rw--- 1 root root 200 Jun 7 18:35 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list

  ubuntu@precise-esm:~$ apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu0.12.04
Version table:
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@precise-esm:~$ sudo apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu5.12.04
Version table:
   14.12-0ubuntu5.12.04 0
  500 https://extended.security.staging.ubuntu.com/ubuntu/ precise/main 
amd64 Packages
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@xenial-test:~$ apt-cache search juju
  E: Opening /etc/apt/sources.list.d/juju-ubuntu-stable-xenial.list - 
ifstream::ifstream (13: Permission denied)
  E: The list of sources could not be read.
  ubuntu@xenial-test:~$

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

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

[Touch-packages] [Bug 1702429] [NEW] Please remove system-image from Ubuntu Artful

[Łukasz Zemczak]

Public bug reported:

I would like to request the removal of source and binaries of the
system-image in artful. The rationale is that the package no longer has
any active maintainer and doesn't have any consumers since vivid. With
the incoming Python 3.6 transition, system-image will just cause
unneeded delays.

There are no reverse dependencies in artful:

sil2100@ideamatsu:~$ reverse-depends system-image-cli
No reverse dependencies found
sil2100@ideamatsu:~$ reverse-depends system-image-dbus
No reverse dependencies found
sil2100@ideamatsu:~$ reverse-depends -b system-image-dev
No reverse dependencies found

Thank you!

** Affects: system-image (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please remove system-image from Ubuntu Artful

Status in system-image package in Ubuntu:
  New

Bug description:
  I would like to request the removal of source and binaries of the
  system-image in artful. The rationale is that the package no longer
  has any active maintainer and doesn't have any consumers since vivid.
  With the incoming Python 3.6 transition, system-image will just cause
  unneeded delays.

  There are no reverse dependencies in artful:

  sil2100@ideamatsu:~$ reverse-depends system-image-cli
  No reverse dependencies found
  sil2100@ideamatsu:~$ reverse-depends system-image-dbus
  No reverse dependencies found
  sil2100@ideamatsu:~$ reverse-depends -b system-image-dev
  No reverse dependencies found

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1702429/+subscriptions

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

[Touch-packages] [Bug 1639203] Re: mouse cursor flashing on laptop screen after adding second monitor through usb 3.0 displaylink monitor

[Michał Skrzypczak]

I confirm that the bug is still there!

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

Title:
  mouse cursor flashing on laptop screen after adding second monitor
  through usb 3.0 displaylink monitor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Mouse cursor flashes when moved on the laptop screen after connecting
  a second monitor via DisplayLink USB 3.0 interface. The cursor flashes
  both when connecting the screen via VGA and HDMI.

  However, when the screen is connected directly to the VGA or HDMI
  ports on laptop, bypassing the DisplayLink adapter, the flashing does
  not occur. Similarly, the cursor never flashes on the second screen.

  The system is Ubuntu 16.04 LTS on Dell Latitude E5470 with integrated
  Intel graphic card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  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
  CurrentDesktop: Unity
  Date: Fri Nov  4 11:40:32 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: Dell Skylake Integrated Graphics [1028:06de]
  InstallationDate: Installed on 2016-08-22 (74 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=6b6cd5e0-5e92-462d-b229-6e50476e309d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0C8FKJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0C8FKJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Nov  4 11:38:14 2016
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   61460
   vendor DEL
  xserver.version: 2:1.18.3-1ubuntu2.3

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

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

[Touch-packages] [Bug 1701688] Re: Remove patch that disables Cork plugin

[Daniel van Vugt]

Now available for testing:
https://launchpad.net/~vanvugt/+archive/ubuntu/pulseaudio

I am testing it on artful right now. A straight copy for zesty is
pending (which should work too?).

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

Title:
  Remove patch that disables Cork plugin

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  According to the patch comment, the cork module is disabled to serve
  the phone. It should now be enabled by removing the patch, 0005-dont-
  load-cork-music-on-phone.patch.

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

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

[Touch-packages] [Bug 1562817] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_write_volume_cb() from source_set_port_cb() from pa_source_process_msg() from source_process

[Daniel van Vugt]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_write_volume_cb() from source_set_port_cb() from
  pa_source_process_msg() from source_process_msg()

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

  ---

  This error is there when i get back to the computer after a while of
  no use, and at login after restart. haven't seen this error while the
  system is "active"/in use.

  I have been unable to provoke the error to come.

  I'm not sure it is related, but when i plug in a headset, the audio volume 
goes through the roof, and a loud (painfully so) scratching sound is coming 
from the headset until i press Vol+. Vol- does nothing till i have pressed up 
at least once.
  But the bug report thing does not pop up when the sound issue is there.

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  pulseaudio:
    Installed: 1:8.0-0ubuntu2
    Candidate: 1:8.0-0ubuntu2
    Version table:
   *** 1:8.0-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbs   22776 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar 28 12:39:45 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-14 (73 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   pa_source_process_msg () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-03-19 (8 days ago)
  UserGroups: adm cdrom dialout dip lp lpadmin plugdev root sambashare sudo 
vboxusers
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 244743G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA3WW(2.63):bd09/18/2015:svnLENOVO:pn244743G:pvrThinkPadW530:rvnLENOVO:rn244743G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 244743G
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-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]

** Description changed:

  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
  
  WORKAROUNDS:
  
   * Use weston instead of gnome-shell; or
-  * $ env -uDISPLAY totem ...# but see bug 1701463
+  * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
+  * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ mpv --hwdec --opengl-backend=wayland ...
  
  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)

** Also affects: gst-plugins-base1.0 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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 Totem:
  Confirmed
Status in gst-plugins-base1.0 package in Ubuntu:
  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

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ mpv --hwdec --opengl-backend=wayland ...

  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 1687981] Please test proposed package

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.0.7-0ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in libinput source package in Xenial:
  Fix Committed
Status in libwacom source package in Xenial:
  Fix Committed
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in vulkan source package in Xenial:
  Fix Committed
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xfonts-utils source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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

[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in libinput source package in Xenial:
  Fix Committed
Status in libwacom source package in Xenial:
  Fix Committed
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in vulkan source package in Xenial:
  Fix Committed
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xfonts-utils source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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

[Touch-packages] [Bug 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]

On Wed, Jul 5, 2017 at 7:19 PM, Nish Aravamudan  
wrote:
> Sponsored the upload to Trusty.

Thanks but just as of tonight it seems a security update burned all my uploads 
versions.
This seems to have waited too long in SRU-review, need to reroll and 
ping here again then.

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

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

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

Bug description:
  [Impact]

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

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

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

   * Solution, drop the broken Delta

  [Test Case]

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

  
  [Regression Potential] 

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

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

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

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

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


  ---

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

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

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

  Found a bugreport on ntpd package:

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

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

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

  of ntpdate package

  After changing from:
  __CODE_START__

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

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

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

[Touch-packages] [Bug 1702606] [NEW] package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет iproute2 не готов к настройке настройка невозможна (текущее состояние: «half-installed»)

[Nikc]

Public bug reported:

1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: iproute2 4.3.0-1ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Jul  5 08:04:21 2017
ErrorMessage: пакет iproute2 не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
InstallationDate: Installed on 2017-07-03 (2 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: iproute2
Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет 
iproute2 не готов к настройке  настройка невозможна (текущее состояние: 
«half-installed»)
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет
  iproute2 не готов к настройке  настройка невозможна (текущее
  состояние: «half-installed»)

Status in iproute2 package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: iproute2 4.3.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jul  5 08:04:21 2017
  ErrorMessage: пакет iproute2 не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
  InstallationDate: Installed on 2017-07-03 (2 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: iproute2
  Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: пакет 
iproute2 не готов к настройке  настройка невозможна (текущее состояние: 
«half-installed»)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1690966] Re: Gnome Shell elements (power menu, launcher etc) are the wrong colour when using Ambiance (wrong grey, and blue highlights)

[Treviño]

I would do that, but I was waiting for some word about what's the GNOME
preferred way of theming the shell nowadays.

As per Jeremy comment.

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

Title:
  Gnome Shell elements (power menu, launcher etc) are the wrong colour
  when using Ambiance (wrong grey, and blue highlights)

Status in gnome-shell package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  In artful, Gnome Shell elements (power menu, launcher etc) are the
  wrong colour when using Ambiance (wrong grey, and blue highlights)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1690966/+subscriptions

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

[Touch-packages] [Bug 1702495] [NEW] touchpad too sensitive

[Digjam Sarma]

Public bug reported:

The mouse cursor moves even when i move my fingers over the touchpad in
the air(without touching it) but doesnt move at all when i use the
touchpad.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jul  5 20:00:11 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1854]
InstallationDate: Installed on 2017-06-27 (8 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2)
MachineType: Hewlett-Packard HP 450 Notebook PC
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=159622e6-6a00-43f4-baad-7b2d60cb8bd8 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.3C
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1854
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 64.2A
dmi.chassis.asset.tag: 5CG347B4F2
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.3C:bd10/11/2013:svnHewlett-Packard:pnHP450NotebookPC:pvr088612005B1600010:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 450 Notebook PC
dmi.product.version: 088612005B1600010
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
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: Wed Jul  5 19:48:09 2017
xserver.configfile: default
xserver.errors:
 
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: apport-bug compiz-0.9 i386 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/1702495

Title:
  touchpad too sensitive

Status in xorg package in Ubuntu:
  New

Bug description:
  The mouse cursor moves even when i move my fingers over the touchpad
  in the air(without touching it) but doesnt move at all when i use the
  touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul  5 20:00:11 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:1854]
  InstallationDate: Installed on 2017-06-27 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  MachineType: Hewlett-Packard HP 450 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 

[Touch-packages] [Bug 1604235] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all, mic does not record any sound tried almost all ways to fix it, but nothing worked.

[MIFAS]

This issue has been fixed on latest kernel version 4.12.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all, mic does not
  record any sound tried almost all ways to fix it, but nothing worked.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Even headphones does not automatically detect in this laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yashwanth   3716 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jul 19 10:04:49 2016
  InstallationDate: Installed on 2016-07-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yashwanth   3716 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[Timo Aaltonen]

Hmm, I don't think xorg-server needs to be rebuilt against libxfont1-dev
at this point.. if there's a need for SRU then this change could be done
at the same time

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

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  Fix Committed
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  Fix Committed
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xfonts-utils source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  Invalid
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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

[Touch-packages] [Bug 1702477] [NEW] crash in/under dbus_realloc

[RJVB]

Public bug reported:

I have installed Qt 5.8.0 and a number of KF5 projects built as much as
possible against the packages provided by/for an up-to-date Kubuntu
14.04LTS system. Just now I got a crash that reflects a bug either in
DBus or in the memory allocation routines it uses. I wasn't interacting
with the machine when the crash occurred so I can only provide the
backtrace below.

Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff88dbe1880 (LWP 28796))]

[Snipped irrelevant threads]

Thread 1 (Thread 0x7ff88dbe1880 (LWP 28796)):
[KCrash Handler]
#6  0x7ff888f85809 in malloc_consolidate (av=av@entry=0x7ff85820) at 
malloc.c:4159
#7  0x7ff888f878b8 in _int_malloc (av=av@entry=0x7ff85820, 
bytes=bytes@entry=9425) at malloc.c:3425
#8  0x7ff888f89311 in _int_realloc (av=0x7ff85820, oldp=0x7ff858063130, 
oldsize=288, nb=9440) at malloc.c:4288
#9  0x7ff888f8a2f9 in __GI___libc_realloc (oldmem=0x7ff858063140, 
bytes=9420) at malloc.c:3031
#10 0x7ff87aa56f9a in dbus_realloc (memory=, 
bytes=) at ../../dbus/dbus-memory.c:677
#11 0x7ff87aa5737f in reallocate_for_length (new_length=9412, 
real=0x7ff8580fda30) at ../../dbus/dbus-string.c:352
#12 set_length (real=real@entry=0x7ff8580fda30, new_length=9412) at 
../../dbus/dbus-string.c:393
#13 0x7ff87aa57466 in open_gap (len=9216, dest=0x7ff8580fda30, 
insert_at=196) at ../../dbus/dbus-string.c:414
#14 0x7ff87aa575ab in copy (start=start@entry=0, len=len@entry=9216, 
dest=dest@entry=0x7ff8580fda30, insert_at=insert_at@entry=196, 
source=0x7ffe958253b0) at ../../dbus/dbus-string.c:1221
#15 0x7ff87aa57dd5 in _dbus_string_copy_len 
(source=source@entry=0x7ffe958253b0, start=start@entry=0, len=len@entry=9216, 
dest=dest@entry=0x7ff8580fda30, insert_at=insert_at@entry=196) at 
../../dbus/dbus-string.c:1391
#16 0x7ff87aa56969 in marshal_1_octets_array (byte_order=, 
pos_after=0x7ffe95825480, n_elements=9216, value=, 
insert_at=196, str=0x7ff8580fda30) at ../../dbus/dbus-marshal-basic.c:929
#17 _dbus_marshal_write_fixed_multi (str=0x7ff8580fda30, insert_at=196, 
element_type=element_type@entry=121, value=value@entry=0x7ffe95825448, 
n_elements=n_elements@entry=9216, byte_order=, 
pos_after=pos_after@entry=0x7ffe95825480) at 
../../dbus/dbus-marshal-basic.c:1106
#18 0x7ff87aa44ce5 in _dbus_type_writer_write_fixed_multi 
(writer=writer@entry=0x7ffe95825460, element_type=element_type@entry=121, 
value=value@entry=0x7ffe95825448, n_elements=9216) at 
../../dbus/dbus-marshal-recursive.c:2376
#19 0x7ff87aa48466 in dbus_message_iter_append_fixed_array 
(iter=iter@entry=0x7ffe95825450, element_type=element_type@entry=121, 
value=value@entry=0x7ffe95825448, n_elements=) at 
../../dbus/dbus-message.c:2745
#20 0x7ff8860068e6 in q_dbus_message_iter_append_fixed_array 
(n_elements=, value=0x7ffe95825448, element_type=121, 
iter=0x7ffe95825450) at 
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/dbus/qdbus_symbols_p.h:303
#21 append (arg=..., this=0x458cd70) at 
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/dbus/qdbusmarshaller.cpp:179
#22 QDBusArgument::operator<< (this=0x7ffe95825530, arg=...) at 
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/dbus/qdbusargument.cpp:547
#23 0x7ff88234be6f in operator<< (image=..., argument=...) at 
/opt/local/var/lnxports/build/_opt_local_site-ports_kf5_KF5-Frameworks/kf5-knotifications/work/knotifications-5.35.0/src/imageconverter.cpp:42
#24 qDBusMarshallHelper (arg=..., t=0x1b300a0) at 
/opt/local/include/qt5/QtDBus/qdbusmetatype.h:68
#25 0x7ff88600cb28 in QDBusMetaType::marshall (arg=..., id=, 
data=data@entry=0x1b300a0) at 
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/dbus/qdbusmetatype.cpp:256
#26 0x7ff886007abb in QDBusMarshaller::appendRegisteredType 
(this=this@entry=0x7ffe958256c0, arg=...) at 
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/dbus/qdbusmarshaller.cpp:531
#27 0x7ff8860092c6 in QDBusMarshaller::appendVariantInternal 
(this=this@entry=0x7ffe958256c0, arg=...) at 
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/dbus/qdbusmarshaller.cpp:504
#28 0x7ff88600b724 in QDBusMarshaller::append (this=0x5625b40, arg=...) at 
/opt/local/var/lnxports/build/_opt_local_site-ports_aqua_qt5-kde-devel/qt5-kde-devel/work/qt-everywhere-opensource-src-5.8.0/qtbase/src/dbus/qdbusmarshaller.cpp:221
#29 0x7ff88600a670 in 

[Touch-packages] [Bug 1702497] [NEW] printer

[P.Schulte]

Public bug reported:

cannot use printer

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins:
 ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
 No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist:
 ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
 '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW:
 ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
 true
Date: Wed Jul  5 16:39:21 2017
DistUpgraded:
 ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
 2017-06-09 17:51:47,626 DEBUG icon theme changed, re-reading
DistroCodename:
 ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
 xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GconfCompiz: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload 
cannot be preloaded (cannot open shared object file): ignored.
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
   Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
InstallationDate: Installed on 2017-06-09 (26 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP Compaq 6000 Pro SFF PC
PccardctlIdent: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload 
cannot be preloaded (cannot open shared object file): ignored.
PccardctlStatus: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload 
cannot be preloaded (cannot open shared object file): ignored.
ProcEnviron:
 LANGUAGE=nl
 PATH=(custom, no user)
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=/dev/sda6 ro 
quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-06-09 (25 days ago)
dmi.bios.date: 10/19/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G2 v02.03
dmi.board.asset.tag: CZC0193HJ4
dmi.board.name: 3048h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC0193HJ4
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G2v02.03:bd10/19/2015:svnHewlett-Packard:pnHPCompaq6000ProSFFPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.name: HP Compaq 6000 Pro SFF PC
dmi.sys.vendor: Hewlett-Packard
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 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Jul  5 08:51:52 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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

Title:
  printer

Status in xorg package in Ubuntu:
  New

Bug description:
  cannot use printer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot 

[Touch-packages] [Bug 1701852] Re: (xenial+) apt-cache fails to run if a single sources.list.d entry is not readable

[Julian Andres Klode]

Not really, we told everyone years ago to use the netrc for that.

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

Title:
  (xenial+) apt-cache fails to run if a single sources.list.d entry is
  not readable

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When evaluating:

  https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
  tools/+bug/1700611

  On 16.04 and greater, apt-cache fails to run if a single
  sources.list.d is not readable (by the current user).  On Trusty, the
  behavior was a bit more friendly in that it would run and just not
  show results from the file that cannot be read.

  My expectation is that when run it would warn if any .list file could
  not be read, but show results for everything it can see.

  This terminal interaction shows the problem (trusty and precise behave
  the same here):

  ubuntu@precise-esm:~$ ll 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list
  -rw--- 1 root root 200 Jun 7 18:35 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list

  ubuntu@precise-esm:~$ apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu0.12.04
Version table:
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@precise-esm:~$ sudo apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu5.12.04
Version table:
   14.12-0ubuntu5.12.04 0
  500 https://extended.security.staging.ubuntu.com/ubuntu/ precise/main 
amd64 Packages
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@xenial-test:~$ apt-cache search juju
  E: Opening /etc/apt/sources.list.d/juju-ubuntu-stable-xenial.list - 
ifstream::ifstream (13: Permission denied)
  E: The list of sources could not be read.
  ubuntu@xenial-test:~$

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

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

[Touch-packages] [Bug 1702497] Re: printer

[Paul White]

** Package changed: xorg (Ubuntu) => cups (Ubuntu)

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

Title:
  printer

Status in cups package in Ubuntu:
  New

Bug description:
  cannot use printer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   true
  Date: Wed Jul  5 16:39:21 2017
  DistUpgraded:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   2017-06-09 17:51:47,626 DEBUG icon theme changed, re-reading
  DistroCodename:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GconfCompiz: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload 
cannot be preloaded (cannot open shared object file): ignored.
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
  InstallationDate: Installed on 2017-06-09 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Compaq 6000 Pro SFF PC
  PccardctlIdent: ERROR: ld.so: object 'libesets_pac.so' from 
/etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.
  PccardctlStatus: ERROR: ld.so: object 'libesets_pac.so' from 
/etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.
  ProcEnviron:
   LANGUAGE=nl
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=/dev/sda6 
ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-06-09 (25 days ago)
  dmi.bios.date: 10/19/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G2 v02.03
  dmi.board.asset.tag: CZC0193HJ4
  dmi.board.name: 3048h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC0193HJ4
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G2v02.03:bd10/19/2015:svnHewlett-Packard:pnHPCompaq6000ProSFFPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq 6000 Pro SFF PC
  dmi.sys.vendor: Hewlett-Packard
  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 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul  5 08:51:52 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[Thorsten Glaser]

“The default configuration is that this "motd-news" feature is enabled
and that it will check https://motd.ubuntu.com for updates.” is called
“a useful feature” by the author of the LWN article, and in this
bugreport.

In the Debian world, we call this a phone-home privacy violation which
is a security-relevant release-critical bug and an absolute MUST NOT.

-- 
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 1604497] Re: Pulseaudio does not start

[Sebastien Bacher]

thanks for the update, let's close the report then

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

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

** Changed in: pulseaudio (Ubuntu)
 Assignee: Luke Yelavich (themuso) => (unassigned)

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

Title:
  Pulseaudio does not start

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I'm using Ubuntu Mate 16.04 with the current updates.

  When I start the computer, pulseaudio is not working after I've logged
  in.

  If I type:
   start-pulseaudio-x11
  from the command line, I get
  "Connection failure: Connection refused
  pa_context_connect() failed: Connection refused"
  and I cannot play any sound.

  If I type pulseaudio& on the command line, I can get sound in some
  applications (e.g. Audacity) but not others (e.g. Firefox or other
  browsers).  At some point a command line message appears that says:
  "E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed:
  org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
  causes include: the remote application did not send a reply, the
  message bus security policy blocked the reply, the reply timeout
  expired, or the network connection was broken."

  I'm not clear why there's a reference to bluez5-util, since I don't
  have bluetooth on my machine.

  pulseaudio:
Installed: 1:8.0-0ubuntu3
Candidate: 1:8.0-0ubuntu3
Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Jul 19 17:43:11 2016
  InstallationDate: Installed on 2016-05-10 (70 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Z97X-UD3H, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97X-UD3H-CF
  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: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z97X-UD3H
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1701852] Re: (xenial+) apt-cache fails to run if a single sources.list.d entry is not readable

[Steve Langasek]

So apt does not support being used on a system where a given
sources.list entry might be marked root-only to conceal HTTP
username/password?

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

Title:
  (xenial+) apt-cache fails to run if a single sources.list.d entry is
  not readable

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When evaluating:

  https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
  tools/+bug/1700611

  On 16.04 and greater, apt-cache fails to run if a single
  sources.list.d is not readable (by the current user).  On Trusty, the
  behavior was a bit more friendly in that it would run and just not
  show results from the file that cannot be read.

  My expectation is that when run it would warn if any .list file could
  not be read, but show results for everything it can see.

  This terminal interaction shows the problem (trusty and precise behave
  the same here):

  ubuntu@precise-esm:~$ ll 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list
  -rw--- 1 root root 200 Jun 7 18:35 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list

  ubuntu@precise-esm:~$ apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu0.12.04
Version table:
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@precise-esm:~$ sudo apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu5.12.04
Version table:
   14.12-0ubuntu5.12.04 0
  500 https://extended.security.staging.ubuntu.com/ubuntu/ precise/main 
amd64 Packages
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@xenial-test:~$ apt-cache search juju
  E: Opening /etc/apt/sources.list.d/juju-ubuntu-stable-xenial.list - 
ifstream::ifstream (13: Permission denied)
  E: The list of sources could not be read.
  ubuntu@xenial-test:~$

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

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

[Touch-packages] [Bug 1702502] [NEW] many messages

[Paulo Carrillo]

Public bug reported:

there are many messages of sending errors report when ubuntu starts

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CasperVersion: 1.376.2
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jul  5 15:07:25 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:1477]
   Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 740M] [1043:1477]
LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
MachineType: ASUSTeK COMPUTER INC. N46VB
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N46VB.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N46VB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN46VB.204:bd01/31/2013:svnASUSTeKCOMPUTERINC.:pnN46VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN46VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N46VB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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: Wed Jul  5 15:02:52 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  many messages

Status in xorg package in Ubuntu:
  New

Bug description:
  there are many messages of sending errors report when ubuntu starts

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul  5 15:07:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1477]
 Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 740M] [1043:1477]
  LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
  MachineType: ASUSTeK COMPUTER INC. N46VB
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: American Megatrends 

[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in network-manager package in Ubuntu:
  New

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs

  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-04 (214 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  IpRoute:
   

[Touch-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock

[Jean-Baptiste Lallement]

SRU verification for Xenial:
I have reproduced the problem with gtk+2.0 2.24.30-1ubuntu1 in xenial and have 
verified that the version of gtk+2.0 2.24.30-1ubuntu1.16.04.1 in -proposed 
fixes the issue.

Marking as verification-done

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

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

Title:
  Gimp crashes with text tool & caps lock

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

Bug description:
  [Impact]

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

  [Test Case]

  Steps to reproduce:

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

  [Regression Potential]

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

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

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

  [ Other Info ]

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

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

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

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

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

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

  Hope someone can take a look at this. Thanks.

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

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

Re: [Touch-packages] [Bug 1701852] Re: (xenial+) apt-cache fails to run if a single sources.list.d entry is not readable

[Steve Langasek]

On Wed, Jul 05, 2017 at 04:05:43PM -, Julian Andres Klode wrote:
> Not really, we told everyone years ago to use the netrc for that.

Sorry, what is 'netrc'?  I've never heard of this, and while I'm not closely
involved in apt development, I don't find any reference to 'netrc' in the
apt.conf or sources.list manpages.  I manage to find
,
but Dir::Etc::netrc is not documented in apt-config(8) nor do I find
documentation for format.  This seems like a good enhancement to apt, but it
seems to be underdocumented and there are lots of downstream integration
points with sources.list which have never been updated to know about this?

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

Title:
  (xenial+) apt-cache fails to run if a single sources.list.d entry is
  not readable

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When evaluating:

  https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
  tools/+bug/1700611

  On 16.04 and greater, apt-cache fails to run if a single
  sources.list.d is not readable (by the current user).  On Trusty, the
  behavior was a bit more friendly in that it would run and just not
  show results from the file that cannot be read.

  My expectation is that when run it would warn if any .list file could
  not be read, but show results for everything it can see.

  This terminal interaction shows the problem (trusty and precise behave
  the same here):

  ubuntu@precise-esm:~$ ll 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list
  -rw--- 1 root root 200 Jun 7 18:35 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list

  ubuntu@precise-esm:~$ apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu0.12.04
Version table:
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@precise-esm:~$ sudo apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu5.12.04
Version table:
   14.12-0ubuntu5.12.04 0
  500 https://extended.security.staging.ubuntu.com/ubuntu/ precise/main 
amd64 Packages
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@xenial-test:~$ apt-cache search juju
  E: Opening /etc/apt/sources.list.d/juju-ubuntu-stable-xenial.list - 
ifstream::ifstream (13: Permission denied)
  E: The list of sources could not be read.
  ubuntu@xenial-test:~$

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

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

[Touch-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[MIFAS]

This issue has been fixed on latest kernel version 4.12.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Nish Aravamudan]

Sponsored the upload to Trusty.

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

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

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

Bug description:
  [Impact]

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

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

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

   * Solution, drop the broken Delta

  [Test Case]

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

  
  [Regression Potential] 

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

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

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

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

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


  ---

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

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

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

  Found a bugreport on ntpd package:

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

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

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

  of ntpdate package

  After changing from:
  __CODE_START__

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

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

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

  __CODE_END__

  to:
  __CODE_START__

  systemctl --quiet stop $service.service >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s 

[Touch-packages] [Bug 1702497] Re: printer

[Till Kamppeter]

Please create a new bug report following the instructions on

https://wiki.ubuntu.com/DebuggingPrintingProblems

Thanks.

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

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

Title:
  printer

Status in cups package in Ubuntu:
  Invalid

Bug description:
  cannot use printer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   true
  Date: Wed Jul  5 16:39:21 2017
  DistUpgraded:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   2017-06-09 17:51:47,626 DEBUG icon theme changed, re-reading
  DistroCodename:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
   xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GconfCompiz: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload 
cannot be preloaded (cannot open shared object file): ignored.
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e12] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
 Subsystem: Hewlett-Packard Company 4 Series Chipset Integrated Graphics 
Controller [103c:3048]
  InstallationDate: Installed on 2017-06-09 (26 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Compaq 6000 Pro SFF PC
  PccardctlIdent: ERROR: ld.so: object 'libesets_pac.so' from 
/etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.
  PccardctlStatus: ERROR: ld.so: object 'libesets_pac.so' from 
/etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.
  ProcEnviron:
   LANGUAGE=nl
   PATH=(custom, no user)
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=/dev/sda6 
ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-06-09 (25 days ago)
  dmi.bios.date: 10/19/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G2 v02.03
  dmi.board.asset.tag: CZC0193HJ4
  dmi.board.name: 3048h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC0193HJ4
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G2v02.03:bd10/19/2015:svnHewlett-Packard:pnHPCompaq6000ProSFFPC:pvr:rvnHewlett-Packard:rn3048h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq 6000 Pro SFF PC
  dmi.sys.vendor: Hewlett-Packard
  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 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul  5 08:51:52 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1702347] Re: Graphical glitches in screen by default

[pavel bursa]

Ubuntu 17.10, daily build 5 July 2017
System:Host: artberg Kernel: 4.10.0-26-generic x86_64 (64 bit) Desktop: 
Gnome 3.24.2
   Distro: Ubuntu Artful Aardvark (development branch)
Graphics:  Card: NVIDIA GK107 [GeForce GT 640]
   Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: 
modesetting,fbdev,vesa)
   Resolution: 2560x1440@59.95hz
   GLX Renderer: Gallium 0.4 on NVE7 GLX Version: 3.0 Mesa 17.1.2

dmesg output follows: 
nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with 
error -2
nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with 
error -2
nouveau :01:00.0: msvld: unable to load firmware data
nouveau :01:00.0: msvld: init failed, -19

FYI: I have found in synaptic, that the package "nouveau-firmware" was not 
installed by default. 
I have installed the package and will restart...

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

Title:
  Graphical glitches in screen by default

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 development branch

  updated and dist-upgraded on 4 july 2017

  Im having weird glitches in screen when scrolling or switching windows
  by default

  Graphics:  Card: NVIDIA C77 [GeForce 9100M G]
 Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: 
modesetting,fbdev,vesa)
 Resolution: 1440x900@60.00hz
 GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2

  installing nvidia-340 resulted in a black screen after login, so i had to 
purge nvidia* to get
  back to desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jul  4 20:59:21 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d]
  InstallationDate: Installed on 2017-06-13 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612)
  MachineType: Acer, inc. Aspire 7530
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3342
  dmi.board.name: EI Capitan
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 7530
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Jul  4 20:45:53 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   event6  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump 
detected and discarded.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH

[Edwin Khoo]

Looks like this patch didn't make it to Ubuntu 17.04?

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

Title:
  Please add ~/.local/bin to the default $PATH

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Xenial:
  Fix Released
Status in bash package in Debian:
  Fix Released

Bug description:
  Starting in Xenial, 'pip install' by default places executables into
  ~/.local/bin. This is the de-facto standard place to put per-user
  executables -- for example, Fedora/Redhat puts it on the $PATH by
  default, and PEP 370 makes it the standard place for unprivileged
  installs of Python packages to put their scripts.

  But unfortunately, Ubuntu's does *not* add this directory to $PATH by
  default, which means that 'pip install' doesn't actually work -- any
  scripts that are installed are inaccessible, and every user has to
  manually add this to their PATH.

  Ubuntu should put ~/.local/bin onto PATH by default.

  Minor details (discussed with @doko at the PyCon sprints):

  - this should go at the beginning of PATH rather than the end, in accordance 
with Debian policy saying that more-local paths go before more-upstream paths. 
(This is inconsistent with how Fedora/RH do it, but consistent with how Python 
itself searches for packages.)
  - this will be added to /etc/skel/profile, so that it won't change any 
existing user accounts; it will only be applied to user accounts created 
*after* this change lands
  - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be 
added to PATH unconditionally, even if the directory doesn't exist. This is 
important to avoid a nasty trap for new users, where the first time they try to 
install a Python package they have to restart their shell. Since this only 
applies to new accounts, the directory will always start out nonexistent/empty, 
so having it in $PATH won't cause any unexpected changes in behavior.
  - possibly it would make sense to set this in /etc/environment or 
/etc/skel/.gnomerc or similar, so that it would also apply to non-shell 
processes (e.g. if the user wants to add a global key-binding to launch a 
Python program, then generally ~/.profile *doesn't* affect the environment 
where this command gets executed, and that can frustrate and confuse users if a 
command works fine from the terminal but not from a keybinding). But we should 
defer this discussion for the future, because even if this is a good idea, it 
isn't a good idea in a Xenial stable update.

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856

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

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

[Touch-packages] [Bug 1702525] [NEW] package ca-certificates 20161130 failed to install/upgrade: triggers looping, abandoned

[Etienne Papegnies]

Public bug reported:

Lots of similar bugs, but for other versions of the same package, not
sure if I should have marked this as duplicate. :/

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: ca-certificates 20161130
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.1
Architecture: amd64
Date: Thu Jun  1 22:46:05 2017
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-06-01 (33 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: ca-certificates
Title: package ca-certificates 20161130 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check zesty

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

Title:
  package ca-certificates 20161130 failed to install/upgrade: triggers
  looping, abandoned

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  Lots of similar bugs, but for other versions of the same package, not
  sure if I should have marked this as duplicate. :/

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: ca-certificates 20161130
  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.1
  Architecture: amd64
  Date: Thu Jun  1 22:46:05 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-06-01 (33 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: ca-certificates
  Title: package ca-certificates 20161130 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1534946] Re: pcimodules: broken; 'kmod' depmod doesn't generate a modules.pcimap

[Jeremy Bicha]

> Is this perhaps fixed via bug #1516095?

No, the 'pcimodules' command still doesn't work in Ubuntu 17.10 Alpha.

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

Title:
  pcimodules: broken; 'kmod' depmod doesn't generate a modules.pcimap

Status in kmod package in Ubuntu:
  Triaged
Status in pciutils package in Ubuntu:
  Triaged

Bug description:
  pciutils->pcimodules relies on /lib/modules/$(uname -r)/modules.pcimap
  and its man-page claims this file is created by kmod->depmod.

  However, since at least 14.04 trusty, this is not the case.
  Consequently pcimodules is broken on all releases since 14.04.

  In 12.04 depmod still supported the "-m" option to generate
  modules.pcimap.

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

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

[Touch-packages] [Bug 1702326] Re: New microrelease 1.4.7 for zesty

[Bug Watch Updater]

** Changed in: apt (Debian)
   Status: New => Incomplete

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

Title:
  New microrelease 1.4.7 for zesty

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Zesty:
  Triaged
Status in apt package in Debian:
  Incomplete

Bug description:
  [Impact]
  This is a new upstream micro release for the first point release of Debian 
stretch.

  apt (1.4.7) stretch; urgency=medium

[ Robert Luberda ]
* fix a "critical" typo in old changelog entry (Closes: 866358)
  => Remove a letter, and fixes some tool

[ David Kalnischkies ]
* use port from SRV record instead of initial port
  => Might have picked the wrong port

[ Julian Andres Klode ]
* Reset failure reason when connection was successful
  => Some failures were only treated as warnings, not errors

* debian/gbp.conf: Set debian-branch to 1.4.y
  => Building ...

* http: A response with Content-Length: 0 has no content

  => Downloading failed if server responded with Content-Length: 0, as
 APT was waiting for content to read.

   -- Julian Andres Klode   Tue, 04 Jul 2017 17:11:59
  +0200

  [Test case]
  We don't really have any yet, they require DNS servers and http servers, so 
it's not really easy to test.

  [Regression potential]
  We basically changed just the code used in the http method, and the changes 
are both very obvious and very small. I reproduced the http change with the tls 
support from 1.5, because launchpad was causing issues with that.

  With the failure reason reset, some errors might not be wrongly
  considered as transient connection errors and now cause scripts to
  fail. But that's how it should be, really.

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

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

[Touch-packages] [Bug 1295969] Re: Forgotten png files in python 2.7 idle

[Hans Joachim Desserud]

** Changed in: hundredpapercuts
   Status: Confirmed => Fix Released

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

Title:
  Forgotten png files in python 2.7 idle

Status in One Hundred Papercuts:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released

Bug description:
  idle-python2.7

  Traceback (most recent call last):
File "/usr/bin/idle-python2.7", line 5, in 
  main()
File "/usr/lib/python2.7/idlelib/PyShell.py", line 1548, in main
  icons = [PhotoImage(file=iconfile) for iconfile in iconfiles]
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 3329, in __init__
  Image.__init__(self, 'photo', name, cnf, master, **kw)
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 3285, in __init__
  self.tk.call(('image', 'create', imgtype, name,) + options)
  _tkinter.TclError: couldn't open 
"/usr/lib/python2.7/idlelib/Icons/idle_16.png": no such file or directory

  Temporary workaround:
  sudo cp /usr/lib/python3.4/idlelib/Icons/idle_*.png 
/usr/lib/python2.7/idlelib/Icons/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: idle-python2.7 2.7.6-7
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 21 23:58:15 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-16 (6 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227)
  PackageArchitecture: all
  SourcePackage: python2.7
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1280374] Re: Missing build dependency: cython

[Adrian Bunk]

This was fixed in 1.8-2, included in quantal and later.

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

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

Title:
  Missing build dependency: cython

Status in libplist package in Ubuntu:
  Fix Released

Bug description:
  ...

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

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

[Touch-packages] [Bug 1701806] 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/1701806

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:
  no 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: Sat Jul  1 10:45:47 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 (106 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/1701806/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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)

[Nish Aravamudan]

@zwets: agreed, I see that as well. I assume the server side of
motd.ubuntu.com is not using the USER_AGENT lsb value correctly?

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

[Nish Aravamudan]

@zwets, would you be willing to file a new bug? It's basically a clarity
issue on the messsage itself. It isn't actually saying you are running
16.10 or 17.04 or anything else. It's just letting you know that 16.10
goes EOL soon. So update your machines. But not necessarily that this
particular machine needs updating. It's confusing and I think deserves a
bit of rewriting to be clearer (maybe using the lsb user_agent to change
the exact text of the message).

-- 
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 1702484] [NEW] package sudo 1.8.16-0ubuntu1.4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Farigoule]

Public bug reported:

impossible d'installer Guitar Pro6 à partir du DVD : report "problème de
logiciel détecté

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.4
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Wed Jul  5 15:32:57 2017
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
InstallationDate: Installed on 2017-04-30 (66 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: sudo
Title: package sudo 1.8.16-0ubuntu1.4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers : analyse grammaticale réussie
 /etc/sudoers.d/README : analyse grammaticale réussie

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

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

Status in sudo package in Ubuntu:
  New

Bug description:
  impossible d'installer Guitar Pro6 à partir du DVD : report "problème
  de logiciel détecté

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.4
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jul  5 15:32:57 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-04-30 (66 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers : analyse grammaticale réussie
   /etc/sudoers.d/README : analyse grammaticale réussie

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Sampo Savola]

Will this fix be released for 17.04 ?

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed
Status in systemd source package in Artful:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1556713] Re: systemd-tmpfiles [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.

[Michael Heuberger]

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

Still happening here on Ubuntu 17

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

Title:
  systemd-tmpfiles [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for
  path "/var/log", ignoring.

Status in systemd package in Ubuntu:
  New

Bug description:
  In /var/log/syslog

  systemd-tmpfiles [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for
  path "/var/log", ignoring.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Mar 13 21:07:01 2016
  InstallationDate: Installed on 2014-03-23 (721 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318)
  MachineType: Dell Inc. Inspiron N7010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=9f1341c7-2522-4643-86be-b9c020215429 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (10 days ago)
  dmi.bios.date: 09/13/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 08VFX1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/13/2010:svnDellInc.:pnInspironN7010:pvrA07:rvnDellInc.:rn08VFX1:rvrA07:cvnDellInc.:ct8:cvrA07:
  dmi.product.name: Inspiron N7010
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1701880] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 usr/lib/x86_64-linux-gnu/openssl-

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: el paquete libssl1.0.0:amd64 no está listo para
  configurarse  no se puede configurar (estado actual `half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  I don't know details.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jul  2 10:37:22 2017
  ErrorMessage: el paquete libssl1.0.0:amd64 no está listo para configurarse  
no se puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2016-12-13 (200 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1687507] Re: Memory leak (/run file system filling up)

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Memory leak (/run file system filling up)

Status in snapd:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  (see also related discussion on forum:
  
https://forum.snapcraft.io/t/memory-run-memory-file-system-leaking-with-snap-install-remove/429
 )

  I have a CI system which tests my snap and does a lot install/remove of snap 
packages as part
  of the operation on some small virtual systems. My /tmp is 200MB

  This is on latest Ubuntu Server 16.04 (all packages updated), with the 
alternative 4.8 kernel
  from the Ubuntu Repo)

  At this time, all packages are updated to latest version. I have this bug for 
a long time (since I've started building up a CI infrastructure for the Snap - 
approx 6 months ago), so this is
  not a new bug, but only the more frequent snap testing made it obvious.

  In my system the /tmp filesystem fills up - within approx 2..7 days I'm out 
of space on it.
  All the space is used up under /run/udev/data/  and approx 95% of the files 
(around 45'000)
  start with +cgroup prefix

  I can provide access to a VM in this state if requested (IPv6 only,
  contact me with SSH key)

  Here is some current output (not yet out of space... may need another
  day)

  root@ci-comp17-dut:~# df
  Filesystem 1K-blocksUsed Available Use% Mounted on
  udev 1002892   0   1002892   0% /dev
  tmpfs 204796  148196 56600  73% /run
  /dev/vda16060608 3462628   2267076  61% /
  tmpfs1023976   0   1023976   0% /dev/shm
  tmpfs   5120   0  5120   0% /run/lock
  tmpfs1023976   0   1023976   0% /sys/fs/cgroup
  /dev/loop0 80256   80256 0 100% /snap/core/1577
  /dev/loop1 77056   77056 0 100% /snap/core/1337
  /dev/loop2 80256   80256 0 100% /snap/core/1441
  tmpfs 204796   0204796   0% /run/user/0
  /dev/loop3 14592   14592 0 100% /snap/frr/x1

  Attached is a full dir output of /run/udev/data
  (ls_run_udev_data.log)

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

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

[Touch-packages] [Bug 1687507] Re: Memory leak (/run file system filling up)

[Launchpad Bug Tracker]

[Expired for snapd because there has been no activity for 60 days.]

** Changed in: snapd
   Status: Incomplete => Expired

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

Title:
  Memory leak (/run file system filling up)

Status in snapd:
  Expired
Status in systemd package in Ubuntu:
  Expired

Bug description:
  (see also related discussion on forum:
  
https://forum.snapcraft.io/t/memory-run-memory-file-system-leaking-with-snap-install-remove/429
 )

  I have a CI system which tests my snap and does a lot install/remove of snap 
packages as part
  of the operation on some small virtual systems. My /tmp is 200MB

  This is on latest Ubuntu Server 16.04 (all packages updated), with the 
alternative 4.8 kernel
  from the Ubuntu Repo)

  At this time, all packages are updated to latest version. I have this bug for 
a long time (since I've started building up a CI infrastructure for the Snap - 
approx 6 months ago), so this is
  not a new bug, but only the more frequent snap testing made it obvious.

  In my system the /tmp filesystem fills up - within approx 2..7 days I'm out 
of space on it.
  All the space is used up under /run/udev/data/  and approx 95% of the files 
(around 45'000)
  start with +cgroup prefix

  I can provide access to a VM in this state if requested (IPv6 only,
  contact me with SSH key)

  Here is some current output (not yet out of space... may need another
  day)

  root@ci-comp17-dut:~# df
  Filesystem 1K-blocksUsed Available Use% Mounted on
  udev 1002892   0   1002892   0% /dev
  tmpfs 204796  148196 56600  73% /run
  /dev/vda16060608 3462628   2267076  61% /
  tmpfs1023976   0   1023976   0% /dev/shm
  tmpfs   5120   0  5120   0% /run/lock
  tmpfs1023976   0   1023976   0% /sys/fs/cgroup
  /dev/loop0 80256   80256 0 100% /snap/core/1577
  /dev/loop1 77056   77056 0 100% /snap/core/1337
  /dev/loop2 80256   80256 0 100% /snap/core/1441
  tmpfs 204796   0204796   0% /run/user/0
  /dev/loop3 14592   14592 0 100% /snap/frr/x1

  Attached is a full dir output of /run/udev/data
  (ls_run_udev_data.log)

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

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

[Touch-packages] [Bug 1504659] Re: Duplicate line for path "/var/log" warning is shown when rsyslog is installed

[Michael Heuberger]

still happening on ubuntu 17 :( ... what's the official fix?

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

Title:
  Duplicate line for path "/var/log" warning is shown when rsyslog is
  installed

Status in systemd package in Ubuntu:
  Opinion

Bug description:
  On an snappy 15.04 stable system I see in the logs:
  systemd-tmpfiles[958]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for 
path "/var/log", ignoring.

  Bug 1434295 mentions this, but reports that systemd fails to start.
  This bug is about preventing systemd from displaying this in the logs.
  Looking at the snappy system, I'm not sure why it is doing that:

  $ cat /usr/lib/tmpfiles.d/var.conf
  #  This file is part of systemd.
  #
  #  systemd is free software; you can redistribute it and/or modify it
  #  under the terms of the GNU Lesser General Public License as published by
  #  the Free Software Foundation; either version 2.1 of the License, or
  #  (at your option) any later version.

  # See tmpfiles.d(5) for details

  d /var 0755 - - -

  L /var/run - - - - ../run

  d /var/log 0755 - - -
  f /var/log/wtmp 0664 root utmp -
  f /var/log/btmp 0600 root utmp -

  d /var/cache 0755 - - -

  d /var/lib 0755 - - -
  v /var/lib/machines 0700 - - -

  d /var/spool 0755 - - -

  Perhaps this is a bug in systemd?

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

-- 
Mailing list: https://launchpad.net/~touch-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 (unable to read library) on overlayfs

[Daniel Axtens]

Hi Tyler,

Do you know what the changes between the ga-16.04 and hwe-16.04 kernel
are that make apparmor+overlayfs work? I'm worried we might hit this
problem elsewhere...

Regards,
Daniel

-- 
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 (unable to read library) on overlayfs

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 1701884] Re: package isc-dhcp-client 4.3.3-5ubuntu12 [modified: sbin/dhclient sbin/dhclient-script usr/share/doc/isc-dhcp-client/changelog.Debian.gz] failed to install/upgrade: p

[Seth Arnold]

This may be a duplicate of bug 1692981.

** Information type changed from Private Security to Public

** 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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1701884

Title:
  package isc-dhcp-client 4.3.3-5ubuntu12 [modified: sbin/dhclient sbin
  /dhclient-script usr/share/doc/isc-dhcp-client/changelog.Debian.gz]
  failed to install/upgrade: package isc-dhcp-client is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in dpkg package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  software install crashed with a fault
  Software: Firmware and 3.20.1+git20170524.0.ea2fe2b0

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12 [modified: sbin/dhclient 
sbin/dhclient-script usr/share/doc/isc-dhcp-client/changelog.Debian.gz]
  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
  AptOrdering:
   nautilus: Install
   isc-dhcp-client: Configure
   nautilus: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jul  2 11:50:36 2017
  DhclientLeases:
   
  DpkgHistoryLog:
   Start-Date: 2017-07-02  11:50:32
   Commandline: aptdaemon role='role-upgrade-packages' sender=':1.80'
   Upgrade: nautilus:amd64 (1:3.18.4.is.3.14.3-0ubuntu5, 
1:3.18.4.is.3.14.3-0ubuntu6)
  DuplicateSignature:
   package:isc-dhcp-client:4.3.3-5ubuntu12 [modified: sbin/dhclient 
sbin/dhclient-script usr/share/doc/isc-dhcp-client/changelog.Debian.gz]
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package isc-dhcp-client (--configure):
package isc-dhcp-client is not ready for configuration
  ErrorMessage: package isc-dhcp-client is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2016-09-28 (276 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=d8effb5b-1ede-4553-bc26-537b116c0fcc ro quiet splash vt.handoff=7
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.3.3-5ubuntu12 [modified: sbin/dhclient 
sbin/dhclient-script usr/share/doc/isc-dhcp-client/changelog.Debian.gz] failed 
to install/upgrade: package isc-dhcp-client 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/dpkg/+bug/1701884/+subscriptions

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

[Touch-packages] [Bug 1658358] Re: Monospace 10 (DejaVuSansMono) in freetype >= 2.6 has invalid size

[Adolfo Jayme]

** Changed in: freetype (Ubuntu)
   Status: Confirmed => Opinion

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

Title:
  Monospace 10 (DejaVuSansMono) in freetype >= 2.6 has invalid size

Status in freetype package in Ubuntu:
  Opinion

Bug description:
  In freetype 2.6 from ubuntu 16.10 missed patch
  "revert_scalable_fonts_metric.patch"

  https://bugs.launchpad.net/freetype/+bug/972223
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636776

  This produces font size bug:
  "p" in "Monospace 10" has height 10px - too small
  "p" in "Monospace 11" has height 12px - too big

  Expected:
  "p" in "Monospace 10" has height 11px - normal
  "p" in "Monospace 11" has height 12px - normal

  See screenshot:
  
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1658358/+attachment/4807239/+files/freetype_fix.png

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

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

[Touch-packages] [Bug 1702347] Re: Graphical glitches in screen by default

[pavel bursa]

... the problem persists, however, I have OK picture on the screen, no 
glitches, etc.
There is just the reported annoying warning in dmesg output.

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

Title:
  Graphical glitches in screen by default

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 development branch

  updated and dist-upgraded on 4 july 2017

  Im having weird glitches in screen when scrolling or switching windows
  by default

  Graphics:  Card: NVIDIA C77 [GeForce 9100M G]
 Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: 
modesetting,fbdev,vesa)
 Resolution: 1440x900@60.00hz
 GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2

  installing nvidia-340 resulted in a black screen after login, so i had to 
purge nvidia* to get
  back to desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Jul  4 20:59:21 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d]
  InstallationDate: Installed on 2017-06-13 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612)
  MachineType: Acer, inc. Aspire 7530
  ProcEnviron:
   LANGUAGE=nl_BE:nl
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=nl_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3342
  dmi.board.name: EI Capitan
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 7530
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Jul  4 20:45:53 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   event6  - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump 
detected and discarded.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu2
  xserver.video_driver: nouveau

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

-- 
Mailing list: https://launchpad.net/~touch-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)

[Marco van Zwetselaar]

I actually spent time tracking down this 'bug' because on my upgrade
17.04 servers I kept seeing:

  * Ubuntu 16.10 will reach end of life on Thursday, July 20, 2017
 How to upgrade from 16.10 to 17.04:
 - https://ubu.one/upgY2Z

making me wonder if my upgrade was botched or something.  I have little
against the feature in general (though I would certainly make it opt-in
rather than opt-out), but this motd is confusing.

-- 
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 1574746] Re: Enable support for libsoxr

[Lastique]

I've created a MIR ticket for libsoxr:
https://bugs.launchpad.net/ubuntu/+source/libsoxr/+bug/1702558

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

Title:
  Enable support for libsoxr

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'd like to ask to enable support for libsoxr-based resamplers in the 
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr 
and automatically detects its availability, so the only change really needed is 
to add the build dependency to debian/control.
   
  The resamplers based in libsoxr offer better quality and better performace 
while introducing more delay compared to the speex resamplers that are used by 
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu 
16.04 but unfortunately are not enabled at build time ('pulseaudio 
--dump-resample-methods' doesn't list them). I've built local packages with 
libsoxr and verified that the resampler works as expected.

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

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

[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support

[Jérôme Martinez]

There is no ABI impacting, as it is only internal (communication between the 
lib and libc API). libzen API uses 64-bit integers whatever is the presence of 
the flag, the flag is only for libc.
And actually, the ABI break would have been seen previously, when the 
compilation flag was removed (switch from Automake to CMake), as the flag was 
present in previous versions, and it was not the case.

In
https://sourceforge.net/p/mediainfo/discussion/297610/thread/8893b38f/#4075
you can see that a user backported himself the new binary to an old
platform of Debian without API break.

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

Title:
  libzen wasn't compiled with large file support

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

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

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

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

[Touch-packages] [Bug 1701852] Re: (xenial+) apt-cache fails to run if a single sources.list.d entry is not readable

[David Kalnischkies]

Regarding the bug itself: I wouldn't exactly call it a regression, but
it wasn't a super-intended change either. If I see it right I "broke" it
in 2015 by fixing a compiler warning, which indicated that a check which
should have been since ever never applied. So, that it worked before was
just as well a bug… long story short I guess we can make that a warning.

Why an error/warning? Having a different view on what packages are
available depending on if you are root or not is a cause for confusion
by users and tools alike as you confirm the non-root view, but the root
view is applied, which might include additional packages, different
versions or even (additional) unauthenticated packages you haven't
approved… (but the tools think you have). Similar things happen for non-
root preferences/configs and are hence discouraged.


For netrc/auth.conf documentation we have e.g. Debian bug #811181 tracking it. 
It is just that nobody has written documentation yet. I assume it is waiting 
for someone who actually wants that feature to write a few sentences about it.

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

Title:
  (xenial+) apt-cache fails to run if a single sources.list.d entry is
  not readable

Status in apt package in Ubuntu:
  Triaged

Bug description:
  When evaluating:

  https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
  tools/+bug/1700611

  On 16.04 and greater, apt-cache fails to run if a single
  sources.list.d is not readable (by the current user).  On Trusty, the
  behavior was a bit more friendly in that it would run and just not
  show results from the file that cannot be read.

  My expectation is that when run it would warn if any .list file could
  not be read, but show results for everything it can see.

  This terminal interaction shows the problem (trusty and precise behave
  the same here):

  ubuntu@precise-esm:~$ ll 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list
  -rw--- 1 root root 200 Jun 7 18:35 
/etc/apt/sources.list.d/staging-ubuntu-esm-precise.list

  ubuntu@precise-esm:~$ apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu0.12.04
Version table:
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@precise-esm:~$ sudo apt-cache policy landscape-client
  landscape-client:
Installed: (none)
Candidate: 14.12-0ubuntu5.12.04
Version table:
   14.12-0ubuntu5.12.04 0
  500 https://extended.security.staging.ubuntu.com/ubuntu/ precise/main 
amd64 Packages
   14.12-0ubuntu0.12.04 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.04.3-0ubuntu1 0
  500 http://br.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  ubuntu@xenial-test:~$ apt-cache search juju
  E: Opening /etc/apt/sources.list.d/juju-ubuntu-stable-xenial.list - 
ifstream::ifstream (13: Permission denied)
  E: The list of sources could not be read.
  ubuntu@xenial-test:~$

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

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

[Touch-packages] [Bug 1702544] [NEW] Merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

[Amr Ibrahim]

Public bug reported:

Please merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

I cannot work on this merge myself. I am reporting this for reference.

Explanation of the Ubuntu delta:
  * SECURITY UPDATE: double free when handling cache files
- debian/patches/CVE-2016-5384.patch: properly validate offsets in
  cache files in src/fccache.c.
- CVE-2016-5384
  * New upstream release (LP: #1556457)
- Fixes blurry fonts regression from previous upload (LP: #1566651)
  * d/p/0001-Revert-Bug-73291-poppler-does-not-show-fl-ligature.patch,
d/p/0002-demilight.patch:
- Dropped, applied in new release
  * Bump freetype build dep to 2.5.1 as per configure.ac.
  * Drop gperf build dep again, not necessary any more.
  * debian/control:
- Add gperf to build dependencies
- Bump FreeType build dependency version to 2.5.1
  [ Mingye Wang ]
  * debian/patches/0002-demilight.patch:
- Handle Demilight sensibly (LP: #1556457)
  * Make things depend on ≥ version-of-libfontconfig1-they-were-built-with, so
that on new releases the library is upgraded before its rdeps. (LP:
#1540591)
  * debian/source_fontconfig.py:
- include fontconfig.log in the bug reports to try to get more info
  on some of the xenial upgrade issues
  * 0001-Revert-Bug-73291-poppler-does-not-show-fl-ligature.patch: Now poppler
is fixed, revert the alias of TeX Gyre Termes to Times. (LP: #1379375)
  * Merge changes from Debian 2.11.0-6.1 and 2.11.0-6.2:
  [ Don Armstrong ]
  * Switch to noawait triggers to allow self-triggering; will still need
Breaks from dpkg to resolve this (closes: #768599)
  * Add Pre-Depends on dpkg to allow for noawait just in case this gets
backported to squeeze.
  [ Andreas Barth ]
  * Add dh-autoreconf to support ppc64el. Closes: #748378
  * No change rebuild to get debug symbols on all architectures.
  * Merge from Debian 2.11.0-2:
- 03_locale_c.utf8.patch: based on a patch from Martin Dickopp. Treat
  C.UTF-8 and C.utf8 locales as built in the C library.
  Closes: #717423.
  * Merge from Debian 2.11.0-2:
- 03_locale_c.utf8.patch: based on a patch from Martin Dickopp. Treat
  C.UTF-8 and C.utf8 locales as built in the C library.
  Closes: #717423.
  * Make libfontconfig1-dev Multi-Arch: same.
  * New upstream release
  * Pass --enable-static to continue building the static library since the
default changed in this release.
  * 0001-Bug-73291-poppler-does-not-show-fl-ligature.patch: Drop, applied
upstream in this release.
  * 0001-Bug-73291-poppler-does-not-show-fl-ligature.patch: Don't alias TeX
Gyre Termes to Times as it has a broken 'fi' ligature. (LP: #1325230)
  * debian/rules:
- don't add /usr/X11R6/lib/X11/fonts to the fonts path, that's a
  deprecated location and it leads to polling on the directory,
  which means wakeups and extra power usage (lp: #1266873)
  * Build using dh-autoreconf.
  * Update font dependencies (ttf-dejavu-core -> fonts-dejavu-core and
ttf-freefont -> fonts-freefont-ttf).
  * New upstream version
  * Refresh debian patches
  * git_obtain_fonts_via_FT-face.patch:
- dropped, included in the new version
  * debian/patches/series: list the patch from the previous revision...
(lp: #1177995)
  * New upstream version
  * Refreshed patches
  * debian/patches/git_obtain_fonts_via_FT-face.patch
- cherrypick patch from git to fix webfonts (LP: #1177995) (Thanks Tim)
  * Remove versioned build dependency on binutils.
  * New upstream version:
- includes the typo fixes for lp: #1037509
  * Fix fontconfig-config postinst to ignore rmdir failures when removing
/var/lib/defoma/fontconfig.d/ as some systems have files in there.
(LP: #1039828)
  * debian/control: build-depends on pkg-config
  * Cherry pick from Debian experimental: Remove defoma support.
Closes: #651493.
  * Drop 08_ug_us_orth.patch again, as per Eagle Burkut. (Locale was renamed
to ug_CN@latin).
  * Add 08_ug_us_orth.patch: Add ug_US orthography.
  * Add 00git_ughur_orthography.patch: Complete Uighur orthography. Patch
taken from upstream git head. (LP: #736413)
  * debian/patches/01_fonts_nanum.patch: Fix typo, thanks Felix Geyer for
spotting!
  * debian/patches/01_fonts_nanum.patch
- Restore Baekmuk fonts because it's still in precise repository
- Remove UnBatang, Baekmuk Batang from monospace because these are serif
  fonts.
  * debian/patches/01_fonts_nanum.patch:
Changes due to Korean migration to fonts-nanum (LP: #792471).
  * Remove /usr/share/doc/$pkg in preinst if it's a symlink for packages
fontconfig, fontconfig-config, libfontconfig1-dev and libfontconfig1-dbg;
fixes upgrades from older borken packages; LP: #828014.  This can be
dropped after oneiric, as noted in the preinst snippets.
  * Restore Debian delta, mistakenly dropped in the previous sync
(LP: #804249):
- fix buildd bustage by ignoring errors in postinst and prerm (taken
  

[Touch-packages] [Bug 1702543] [NEW] package keyboard-configuration 1.142ubuntu5 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Abbaoui]

Public bug reported:

When i press any key on the keyboard all it does is display the console
for locking, suspending, restarting and shutting down the computer, how
to fix this problem

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: keyboard-configuration 1.142ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.3
Architecture: amd64
Date: Wed Jul  5 20:58:26 2017
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 127
InstallationDate: Installed on 2017-07-04 (1 days ago)
InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: console-setup
Title: package keyboard-configuration 1.142ubuntu5 failed to install/upgrade: 
le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 127
UpgradeStatus: Upgraded to yakkety on 2017-07-05 (0 days ago)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

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

Title:
  package keyboard-configuration 1.142ubuntu5 failed to install/upgrade:
  le sous-processus script post-installation installé a retourné une
  erreur de sortie d'état 127

Status in console-setup package in Ubuntu:
  New

Bug description:
  When i press any key on the keyboard all it does is display the
  console for locking, suspending, restarting and shutting down the
  computer, how to fix this problem

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: keyboard-configuration 1.142ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Wed Jul  5 20:58:26 2017
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 127
  InstallationDate: Installed on 2017-07-04 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.142ubuntu5 failed to install/upgrade: 
le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 127
  UpgradeStatus: Upgraded to yakkety on 2017-07-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1702543/+subscriptions

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

[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support

[Robie Basak]

Do we know that this change won't be ABI impacting? Is this known, or
has anybody looked into this?

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

Title:
  libzen wasn't compiled with large file support

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

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

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

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

[Touch-packages] [Bug 1702502] Re: many messages

[Amr Ibrahim]

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

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

Title:
  many messages

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  there are many messages of sending errors report when ubuntu starts

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CasperVersion: 1.376.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul  5 15:07:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1477]
 Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 740M] [1043:1477]
  LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
  MachineType: ASUSTeK COMPUTER INC. N46VB
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N46VB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N46VB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN46VB.204:bd01/31/2013:svnASUSTeKCOMPUTERINC.:pnN46VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN46VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N46VB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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: Wed Jul  5 15:02:52 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1702551] [NEW] Install hung halfway and got stuck there - package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should rei

[James Holden]

Public bug reported:

Crash report happened on re boot.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bsdutils 1:2.29-1ubuntu2
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.1
AptOrdering:
 bsdutils:amd64: Configure
 libgcrypt20:amd64: Install
 libgcrypt20:amd64: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Jul  5 20:32:34 2017
DpkgTerminalLog:
 dpkg: error processing package bsdutils (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-19 (47 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: util-linux
Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Install hung halfway and got stuck there - package bsdutils
  1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad
  inconsistent state; you should  reinstall it before attempting
  configuration

Status in util-linux package in Ubuntu:
  New

Bug description:
  Crash report happened on re boot.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bsdutils 1:2.29-1ubuntu2
  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.1
  AptOrdering:
   bsdutils:amd64: Configure
   libgcrypt20:amd64: Install
   libgcrypt20:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jul  5 20:32:34 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-19 (47 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  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/1702551/+subscriptions

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

[Touch-packages] [Bug 1689033] Re: A few missing icons in version 2.4.3

[James Cowgill]

It appears this is a GTK+ bug, and not a gdk-pixbuf bug (see the 2 GNOME
bugs liked to this bugreport).

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

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

** Tags removed: packaging

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Invalid

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

Title:
  A few missing icons in version 2.4.3

Status in gdk-pixbuf:
  Incomplete
Status in GTK+:
  Unknown
Status in easytag package in Ubuntu:
  Confirmed
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  A few icons are missing in version 2.4.3 for zesty (and probably
  artful), see https://i.imgur.com/Cl4o36Sr.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1689033/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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)

[Nish Aravamudan]

@zwets, to be clear, file the bug at: https://bugs.launchpad.net
/~ubuntu-motd

-- 
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 1689033] Re: A few missing icons in version 2.4.3

[Bug Watch Updater]

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

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

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

Title:
  A few missing icons in version 2.4.3

Status in gdk-pixbuf:
  Incomplete
Status in GTK+:
  Confirmed
Status in easytag package in Ubuntu:
  Confirmed
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  A few icons are missing in version 2.4.3 for zesty (and probably
  artful), see https://i.imgur.com/Cl4o36Sr.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1689033/+subscriptions

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

[Touch-packages] [Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn

[Bug Watch Updater]

** Changed in: glibc
   Status: Confirmed => Incomplete

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

Title:
  Use the modern English name Bangla instead of Bengali for the language
  code bn

Status in CLDR:
  Fix Released
Status in GLibC:
  Incomplete
Status in gnome-control-center:
  Confirmed
Status in xkeyboard-config:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in iso-codes package in Ubuntu:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in localechooser package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in iso-codes package in Debian:
  Fix Released
Status in xkeyboard-config package in Debian:
  Fix Released

Bug description:
  The official name for the state language for Bangladesh is Bangla, as
  detailed on section 3, part 1 of the Bangladesh constitution
  (http://www1.umn.edu/humanrts/research/bangladesh-constitution.pdf).
  However, language selector continues to refer to this language as
  Bengali (Bangladeh). While Bengali has been historically used as the
  english name for the language during colonial periods, the name
  'Bangla' is more widely used nowadays. It is also the name with which
  native speakers identify the language.

  This package uses Bengali(Bangladesh) as the identifier for language
  code bn-BD. Please change the name to Bangla(Bangladesh).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: language-selector-gnome 0.79
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Sun Apr 29 16:14:25 2012
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=bn_BD:bn:en_IN:en_GB:en
   PATH=(custom, no user)
   LANG=bn_BD.UTF-8
   SHELL=/bin/bash
  SourcePackage: language-selector
  UpgradeStatus: Upgraded to precise on 2012-03-19 (41 days ago)

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

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