[Touch-packages] [Bug 1674653] Re: package libnss3:i386 2:3.26.2-0ubuntu0.16.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con

[Launchpad Bug Tracker]

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

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

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

Title:
  package libnss3:i386 2:3.26.2-0ubuntu0.16.04.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in nss package in Ubuntu:
  Expired

Bug description:
  Lo mismo que el anterior

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnss3:i386 2:3.26.2-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-66.87-lowlatency 4.4.44
  Uname: Linux 4.4.0-66-lowlatency i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Tue Mar 21 11:54:23 2017
  DuplicateSignature:
   package:libnss3:i386:2:3.26.2-0ubuntu0.16.04.2
   Setting up libfreetype6:i386 (2.6.1-0.1ubuntu2.1) ...
   dpkg: error processing package libnss3:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-10-27 (144 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: nss
  Title: package libnss3:i386 2:3.26.2-0ubuntu0.16.04.2 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/nss/+bug/1674653/+subscriptions

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

[Touch-packages] [Bug 718635] Re: Error message "Your computer does not have enough free memory" when core dump or stacktrace failed to be created is misleading

[themusicgod1]

** Tags added: zesty

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

Title:
  Error message "Your computer does not have enough free memory" when
  core dump or stacktrace failed to be created is misleading

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apport

  On Unity fully updated, when I login there is a X crash (attached), an apport 
dialog is displayed but complains about:
  ---
  Sorry, the program "Xorg" closed unexpectedly

  Your computer does not have enough free memory to automatically analyze the 
problem and send a report to the developers.
  ---

  You can only close and the report is canceled.

  Of course there's enough memory

  This message is displayed when the core dump or stacktrace can't be
  attached to the report. This should be changed to something closer to
  the real issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: apport 1.17.2-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
  Uname: Linux 2.6.38-3-generic i686
  ApportLog:
   ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: called for pid 741, 
signal 6
   ERROR: apport (pid 8213) Mon Feb 14 10:17:49 2011: executable: /usr/bin/Xorg 
(command line "/usr/bin/X :0 -br -verbose -auth 
/var/run/gdm/auth-for-gdm-ics1IG/database -nolisten tcp vt7")
  Architecture: i386
  Date: Mon Feb 14 10:54:38 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US.UTF-8:en
   LANG=en_US.UTF-8
   LC_MESSAGES=en_AG.utf8
   SHELL=/bin/bash
  SourcePackage: apport

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

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

[Touch-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

[NJ]

I am on Mint 18.1. This problem affects me too. Is anyone working on it,
please?

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in notification-daemon:
  New
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

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

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

[Touch-packages] [Bug 1693953] Re: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

[Seth Arnold]

mktemp: 无法通过模板"/tmp/tmp.XX" 创建文件: 没有那个文件或目录
dpkg: 处理软件包 apparmor (--configure)时出错：
 子进程 已安装 post-installation 脚本 返回错误状态 1

Google translate suggests 没有那个文件或目录 is "There is no file or directory".

Does /tmp exist? Is it writable?

Thanks

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

Title:
  package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in apparmor package in Ubuntu:
  New

Bug description:
  actually i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.6
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri May 26 21:16:27 2017
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2017-05-24 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-52-generic 
root=UUID=93c22d02-44b9-4230-9b85-44a45f7234cf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: apparmor
  Title: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693953] [NEW] package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

[张欣]

Public bug reported:

actually i don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apparmor 2.10.95-0ubuntu2.6
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri May 26 21:16:27 2017
ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
InstallationDate: Installed on 2017-05-24 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-52-generic 
root=UUID=93c22d02-44b9-4230-9b85-44a45f7234cf ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: apparmor
Title: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in apparmor package in Ubuntu:
  New

Bug description:
  actually i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.6
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri May 26 21:16:27 2017
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2017-05-24 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-52-generic 
root=UUID=93c22d02-44b9-4230-9b85-44a45f7234cf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: apparmor
  Title: package apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693944] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Seth Arnold]

Hello, one of your logs indicates a problem:

/etc/ssh/sshd_config line 64: miss...

Sadly the actual error has been left out of the logs. But hopefully you
can spot what's wrong on line 64.

Thanks

** Attachment removed: "DpkgTerminalLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1693944/+attachment/4884332/+files/DpkgTerminalLog.txt

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I was doing a normal update and got this error message at the end.

  I'm new to Ubuntu and I honestly don't know what the problem could be.
  I've not had problems with OpenSSH before

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri May 26 18:39:19 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-06 (232 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693948] [NEW] useless diagnostics from journalctl due to ellipses

[Seth Arnold]

Public bug reported:

Many of the apport hooks try to include some information about why a
service didn't start correctly. One recent report included the
following:

May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell serv
May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/sshd_config line 64: miss
May 26 18:39:19 ux305ua-linux systemd[1]: ssh.service: Main process 
exited, ...a
May 26 18:39:19 ux305ua-linux systemd[1]: Failed to start OpenBSD 
Secure She
May 26 18:39:19 ux305ua-linux systemd[1]: ssh.service: Unit entered 
failed s
May 26 18:39:19 ux305ua-linux systemd[1]: ssh.service: Failed with 
result 'e
Hint: Some lines were ellipsized, use -l to show in full.


The actual error information is this:

/etc/ssh/sshd_config line 64: miss
and
Failed with result 'e

This is very nearly useless.

We should include the -l parameter as suggested so that we stand a
chance of seeing an error that doesn't occur in the first twenty
characters of program output.

Thanks

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

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

Title:
  useless diagnostics from journalctl due to ellipses

Status in apport package in Ubuntu:
  New

Bug description:
  Many of the apport hooks try to include some information about why a
  service didn't start correctly. One recent report included the
  following:

  May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell 
serv
  May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/sshd_config line 64: 
miss
  May 26 18:39:19 ux305ua-linux systemd[1]: ssh.service: Main process 
exited, ...a
  May 26 18:39:19 ux305ua-linux systemd[1]: Failed to start OpenBSD 
Secure She
  May 26 18:39:19 ux305ua-linux systemd[1]: ssh.service: Unit entered 
failed s
  May 26 18:39:19 ux305ua-linux systemd[1]: ssh.service: Failed with 
result 'e
  Hint: Some lines were ellipsized, use -l to show in full.

  
  The actual error information is this:

  /etc/ssh/sshd_config line 64: miss
  and
  Failed with result 'e

  This is very nearly useless.

  We should include the -l parameter as suggested so that we stand a
  chance of seeing an error that doesn't occur in the first twenty
  characters of program output.

  Thanks

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

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

[Touch-packages] [Bug 1693944] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I was doing a normal update and got this error message at the end.

  I'm new to Ubuntu and I honestly don't know what the problem could be.
  I've not had problems with OpenSSH before

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri May 26 18:39:19 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-06 (232 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 ***

[Jeremy Bicha]

** No longer affects: gnome-shell (Ubuntu Zesty)

** Changed in: libgweather (Ubuntu Zesty)
   Status: New => In Progress

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

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

** Changed in: ubuntu-gnome
   Status: New => Fix Committed

** Changed in: ubuntu-gnome
   Importance: Undecided => High

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  free(): invalid pointer: 0x082dcf30 ***

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

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

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

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

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
   
  === original bug report 
  This happened while installing Xfce with Synaptic.

  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  chris@localhost:~$ apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.1
    Candidate: 3.18.5-0ubuntu0.1
    Version table:
   *** 3.18.5-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid 
pointer: 0x082dcf30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug 24 16:21:37 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (670 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3868
   __GI___libc_free (mem=) at malloc.c:2969
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
free(): invalid pointer: 0x082dcf30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

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

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

[Touch-packages] [Bug 1693941] [NEW] passing an absolute path for sources_list to cache.update does not work

[Bryan Seitz]

Public bug reported:

Using python-apt 1.1.0~beta1build1.

Calling cache like such:

cache = apt.Cache(memonly=True, rootdir='/home/seitz/tmp/apt_root')
cache.update(sources_list='/home/seitz/tmp/apt_root/etc/apt/sources-zesty.list')

Would produce an empty cache :(  If I copy the contents of sources-
zesty.list to sources.list in that same directory and pass that path as
an argument, it functions properly.  I am looping over several Ubuntu
releases as including them all in one sources.list caused conflicts.

Please advise.

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  passing an absolute path for sources_list to cache.update does not
  work

Status in python-apt package in Ubuntu:
  New

Bug description:
  Using python-apt 1.1.0~beta1build1.

  Calling cache like such:

  cache = apt.Cache(memonly=True, rootdir='/home/seitz/tmp/apt_root')
  
cache.update(sources_list='/home/seitz/tmp/apt_root/etc/apt/sources-zesty.list')

  Would produce an empty cache :(  If I copy the contents of sources-
  zesty.list to sources.list in that same directory and pass that path
  as an argument, it functions properly.  I am looping over several
  Ubuntu releases as including them all in one sources.list caused
  conflicts.

  Please advise.

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

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

[Touch-packages] [Bug 1693944] [NEW] package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Emily]

Public bug reported:

I was doing a normal update and got this error message at the end.

I'm new to Ubuntu and I honestly don't know what the problem could be.
I've not had problems with OpenSSH before

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
Uname: Linux 4.4.0-77-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri May 26 18:39:19 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-10-06 (232 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I was doing a normal update and got this error message at the end.

  I'm new to Ubuntu and I honestly don't know what the problem could be.
  I've not had problems with OpenSSH before

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri May 26 18:39:19 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-06 (232 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691880] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Emily]

Nick, what was the error in your ssh config file? I had this problem but
I'm not sure what I need to change in /etc/ssh/sshd_config

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  was trying the update and upgrade command. suddenly got the below error 
message.
  Errors were encountered while processing:
   openssh-server
   unattended-upgrades
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  Uname: Linux 4.1.19-v7+ armv7l
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: armhf
  Date: Thu May 18 19:08:41 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 ***

[Tim]

** Description changed:

+ 
+ [Impact] 
+ Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions
+ 
+ I believe this should also fix bug 1688208 and potentially a couple of
+ other high ranking crashes on errors.ubuntu.com. I have not however
+ found reliable reproducers for those other bugs.
+ 
+ [Test Case]
+ After update of libgweather
+ 1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
+ 2. Disable Location Services
+ 3. gnome-shell should not crash
+ 
+ [Regression Potential]
+ Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
+  
+ === original bug report 
  This happened while installing Xfce with Synaptic.
  
  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  chris@localhost:~$ apt-cache policy gnome-shell
  gnome-shell:
-   Installed: 3.18.5-0ubuntu0.1
-   Candidate: 3.18.5-0ubuntu0.1
-   Version table:
-  *** 3.18.5-0ubuntu0.1 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.18.4-0ubuntu3 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+   Installed: 3.18.5-0ubuntu0.1
+   Candidate: 3.18.5-0ubuntu0.1
+   Version table:
+  *** 3.18.5-0ubuntu0.1 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.18.4-0ubuntu3 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  
- ProblemType: Crash
- DistroRelease: Ubuntu 16.04
+ ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid 
pointer: 0x082dcf30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug 24 16:21:37 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (670 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- Signal: 6
- SourcePackage: gnome-shell
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
-  __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
-  malloc_printerr (ar_ptr=, ptr=, 
str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007
-  _int_free (av=, p=, have_lock=0) at 
malloc.c:3868
-  __GI___libc_free (mem=) at malloc.c:2969
-  g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
+  malloc_printerr (ar_ptr=, ptr=, 
str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007
+  _int_free (av=, p=, have_lock=0) at 
malloc.c:3868
+  __GI___libc_free (mem=) at malloc.c:2969
+  g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
free(): invalid pointer: 0x082dcf30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
-  x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
-  x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
-  x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
+  x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
+  x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
+  x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  free(): invalid pointer: 0x082dcf30 ***

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

Bug description:
  
  [Impact] 
  Backport git patch that 

[Touch-packages] [Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 ***

[Tim]

** Also affects: libgweather (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  free(): invalid pointer: 0x082dcf30 ***

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

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

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

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

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
   
  === original bug report 
  This happened while installing Xfce with Synaptic.

  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  chris@localhost:~$ apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.1
    Candidate: 3.18.5-0ubuntu0.1
    Version table:
   *** 3.18.5-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid 
pointer: 0x082dcf30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug 24 16:21:37 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (670 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7fabad1dd48f "free(): invalid pointer", action=3) at malloc.c:5007
   _int_free (av=, p=, have_lock=0) at 
malloc.c:3868
   __GI___libc_free (mem=) at malloc.c:2969
   g_strfreev () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': 
free(): invalid pointer: 0x082dcf30 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   x-session-manager[7610]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[14832]: CRITICAL: We failed, but the fail whale is dead. 
Sorry
   x-session-manager[5188]: CRITICAL: We failed, but the fail whale is dead. 
Sorry

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

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

[Touch-packages] [Bug 1657296] Re: Need two commits cherry-picked from Mesa main into 16.04

[Timo Aaltonen]

17.0.x will be backported to xenial

** Changed in: mesa (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  Need two commits cherry-picked from Mesa main into 16.04

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  In Progress

Bug description:
  Hi,

  On Ubuntu 16.04,  VMWare customers are running into a couple of issues:
   1.  Any app that uses glGenMipmap command will not work properly or crash
   (https://communities.vmware.com/thread/537924)
   2.  vmwgfx_dri.so is sending provoking vertex command when it is not 
supposed to.

  I have contacted the Mesa maintainer, but unfortunately 11.2.x is no
  longer being actively supported, and so I couldn't get the fixes
  cherry-picked over.

  Is there an internal process in Canonical to cherry-pick fixes over?

  To fix the two defects above, please cherry pick the following two commits 
from Mesa main:
7988513ac3d86ba367fbe44e73fe483ff96aaa29
ca531aeeb120cdd

  ---

  1)  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  2)  libgl1-mesa-dri:
  Installed: 11.2.0-1ubuntu2.2
  Candidate: 11.2.0-1ubuntu2.2
  Version table:
  *** 11.2.0-1ubuntu2.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   11.2.0-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3)  Google Earth will run into the glGenMipmap issue, i.e. dmesg will
  show "Unsupported command"  I'm not sure if the 2nd issue is
  observable without a debug build of VMWare software...

  4)  Through internal testing, the two commits above should the issues
  mentioned.

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

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

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Derek Chafin]

I use KeePass 2 on Mono so I'm not too bothered by this. Wifi and
NetworkManager still have problems though.

On Google Chrome and likely Chromium I fixed the 2 minute start wait by
adding --password-store=basic the command line. You can add it the Exec
entry in your desktop file or by editing the menu entry with menu-libre
or equivalent.

You will have to sign in to Chrome again if you use their syncing
functionality. I like syncing because I can see history and open tabs
from my phone on my desktop and vice versa.

It seems Chromium uses a plain text password store with the basic option
so you may not prefer this option. I don't use Chromium password storage
since I use KeePass so it works for me.

https://chromium.googlesource.com/chromium/src/+/lkcr/docs/linux_password_storage.md

I have read that PAM is supposed to unlock the keyring as configured in
LightDM (My current display manager) but that's not being done
apparently.

There is alot of garbage on Google about incompatibilities with
autologin. My account is not set to autologin and requires a password to
login.

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1693021] Re: Need two commits cherry-picked from Mesa main into 16.10

[Timo Aaltonen]

no, 16.10 will be EOL soon enough to not bother

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Need two commits cherry-picked from Mesa main into 16.10

Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  Hi,

  Can we get Mesa patch (ca531aeeb120cdd) reported here ported to 16.10?

  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1657296

  I verified that on 16.10, Mesa-12.0.6, the provoking vertex fix is not
  there.

  thanks

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

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

[Touch-packages] [Bug 1693930] [NEW] python-apt complains even if trusted=yes in sources.list

[Bryan Seitz]

Public bug reported:

Any help would be appreciated.

python-apt - 1.1.0~beta1build1

--- Python Code ---

import apt
import re
import sys
from distutils.version import LooseVersion

cache = apt.Cache(memonly=True, rootdir='/home/seitz/tmp/apt_root')
try:
cache.update(sources_list='/home/seitz/tmp/apt_root/etc/apt/sources.list', 
raise_on_error=False)
except Exception as e:
print e
pass
cache.open(None)

kernel_versions = {}
for pkg_name in cache.keys():
kernel_version = re.search(r'linux-image-([\d\-\.]+)-generic', pkg_name)
if kernel_version:
distro_re = re.search(r'^([A-Za-z]+)-?', 
cache[pkg_name].candidate.origins[0].archive)
if distro_re:
distro = distro_re.group(1)
else:
distro = 'custom'

major_minor = re.search(r'^(\d+.\d+)', kernel_version.group(1))
kernel_versions.setdefault(distro, {})
kernel_versions[distro].setdefault(major_minor.group(1), [])

kernel_versions[distro][major_minor.group(1)].append(kernel_version.group(1))

for distro in sorted(kernel_versions):
print "{}:".format(distro)
for major_minor in sorted(kernel_versions[distro], key=lambda s: map(int, 
s.split('.')), reverse=True):
kernel_versions[distro][major_minor].sort(key=LooseVersion)
print "\t{}:".format(major_minor)
print "\t\t{}".format(kernel_versions[distro][major_minor].pop())

--- Output ---
seitz@host ~ % python apt-get-latest.py
W:GPG error: http://infra-mirror/ubuntu artful-backports InRelease: The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 3B4FE6ACC0B21F32, W:GPG error: http://infra-mirror/ubuntu 
artful InRelease: The following signatures couldn't be verified because the 
public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32, W:GPG error: 
http://infra-mirror/ubuntu artful-security InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
3B4FE6ACC0B21F32, W:GPG error: http://infra-mirror/ubuntu artful-updates 
InRelease: The following signatures couldn't be verified because the public key 
is not available: NO_PUBKEY 3B4FE6ACC0B21F32, W:GPG error: 
http://infra-mirror/ubuntu zesty-backports InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
3B4FE6ACC0B21F32, W:GPG error: http://infra-mirror/ubuntu zesty InRelease: The 
following signatures couldn't be ver
 ified because the public key is not available: NO_PUBKEY 3B4FE6ACC0B21F32, 
W:http://host/annex-apt-precise/apt/precise/dists/precise/Release.gpg: 
Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest 
algorithm (SHA1), W:GPG error: http://infra-mirror/ubuntu zesty-security 
InRelease: The following signatures couldn't be verified because the public key 
is not available: NO_PUBKEY 3B4FE6ACC0B21F32, W:GPG error: 
http://infra-mirror/ubuntu zesty-updates InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
3B4FE6ACC0B21F32, 
W:http://host/annex-apt-precise/apt/precise/dists/precise-backports/Release.gpg:
 Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest 
algorithm (SHA1), 
W:http://host/annex-apt-precise/apt/precise/dists/precise-security/Release.gpg: 
Signature by key 630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest 
algorithm (SHA1), W:http://host/annex-apt-precise/apt/precise/dists/
 precise-updates/Release.gpg: Signature by key 
630239CC130E1A7FD81A27B140976EAF437D05B5 uses weak digest algorithm (SHA1), 
E:Failed to fetch 
http://host/annex-apt-precise/apt/precise/dists/precise-backports/main/i18n/Translation-en
  404  Not Found [IP: 10.40.25.157 80], E:Failed to fetch 
http://host/annex-apt-precise/apt/precise/dists/precise-security/main/i18n/Translation-en
  404  Not Found [IP: 10.40.25.157 80], E:Failed to fetch 
http://host/annex-apt-precise/apt/precise/dists/precise-updates/main/i18n/Translation-en
  404  Not Found [IP: 10.40.25.157 80], E:Some index files failed to download. 
They have been ignored, or old ones used instead.
artful:
4.10:
4.10.0-21
custom:
3.16:
3.16.0-77
precise:
3.2:
3.2.0-23
xenial:
4.10:
4.10.0-14
4.8:
4.8.0-36
4.4:
4.4.0-78
yakkety:
4.8:
4.8.0-53
zesty:
4.10:
4.10.0-20

--- Sources.list ---
deb [arch=amd64 trusted=yes] http://infra-mirror/ubuntu artful-backports main 
universe restricted
deb [arch=amd64 trusted=yes] http://infra-mirror/ubuntu artful main universe 
restricted
deb [arch=amd64 trusted=yes] http://infra-mirror/ubuntu artful-security main 
universe restricted
deb [arch=amd64 trusted=yes] http://infra-mirror/ubuntu artful-updates main 
universe restricted

deb [arch=amd64 trusted=yes] http://host/apt-kernel/apt/3.16.0-77 3.16.0-77 

[Touch-packages] [Bug 1679569] Re: badurl

[Andreas Moog]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

** Changed in: gallery-app (Ubuntu)
   Status: New => Incomplete

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

Title:
  badurl

Status in gallery-app package in Ubuntu:
  Incomplete

Bug description:
  badurl

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: gallery-app 0.0.67+17.04.20161213-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  BadURL: appid://com.ubuntu.camera/camera/current-user-version
  CurrentDesktop: Unity:Unity8
  Date: Tue Apr  4 11:13:44 2017
  DuplicateSignature: /usr/bin/gallery-app:url-dispatcher-bad-url
  ExecutablePath: /usr/bin/gallery-app
  InstallationDate: Installed on 2016-12-12 (112 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: gallery-app
  SourcePackage: gallery-app
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1679569/+subscriptions

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Ubuntu Foundations Team Bug Bot]

The attachment "lp1693819-trusty.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New
Status in isc-dhcp package in Debian:
  Unknown

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1693921] [NEW] package initramfs-tools 0.125ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[alan winn]

Public bug reported:

occurred after first boot and update

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: initramfs-tools 0.125ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Fri May 26 21:21:07 2017
DuplicateSignature:
 package:initramfs-tools:0.125ubuntu9
 Processing triggers for initramfs-tools (0.125ubuntu9) ...
 /var/lib/dpkg/info/initramfs-tools.postinst: 19: 
/var/lib/dpkg/info/initramfs-tools.postinst: update-initramfs: not found
 dpkg: error processing package initramfs-tools (--configure):
  subprocess installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2017-05-26 (0 days ago)
InstallationMedia: Systemback Live (ulinux17) - Release amd64
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package initramfs-tools 0.125ubuntu9 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  occurred after first boot and update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri May 26 21:21:07 2017
  DuplicateSignature:
   package:initramfs-tools:0.125ubuntu9
   Processing triggers for initramfs-tools (0.125ubuntu9) ...
   /var/lib/dpkg/info/initramfs-tools.postinst: 19: 
/var/lib/dpkg/info/initramfs-tools.postinst: update-initramfs: not found
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2017-05-26 (0 days ago)
  InstallationMedia: Systemback Live (ulinux17) - Release amd64
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1693921/+subscriptions

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

[Touch-packages] [Bug 1693921] Re: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.125ubuntu9 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  occurred after first boot and update

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: initramfs-tools 0.125ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri May 26 21:21:07 2017
  DuplicateSignature:
   package:initramfs-tools:0.125ubuntu9
   Processing triggers for initramfs-tools (0.125ubuntu9) ...
   /var/lib/dpkg/info/initramfs-tools.postinst: 19: 
/var/lib/dpkg/info/initramfs-tools.postinst: update-initramfs: not found
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2017-05-26 (0 days ago)
  InstallationMedia: Systemback Live (ulinux17) - Release amd64
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1693921/+subscriptions

-- 
Mailing list: https://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 1605798] Re: Unity + Skylake + Hyper-V xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)

[Mark Harris]

Sorry for the delay.. Yes, I just built a new VM using 16.04.2 and it
seems to be fine.

Thanks!

Mark

-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Joseph 
Salisbury
Sent: Thursday, May 18, 2017 12:45 PM
To: Mark Harris 
Subject: [Bug 1605798] Re: Unity + Skylake + Hyper-V xf86EnableIOPorts: failed 
to set IOPL for I/O (Operation not permitted)

@Mark Harris,  it's been a while since the last comment.  Does this bug
still exist with the lastest updates?

** Tags added: kernel-da-key

--
You received this bug notification because you are subscribed to the bug report.
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fbugs%2F1605798=02%7C01%7Cmark.d.harris%40microsoft.com%7C5b109efd696a4cb1165208d49e0e90e9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636307232777628818=aTamibhsahF%2Bt2WQZF43sTMhaCX23%2FDjdl1h81co8Y8%3D=0

Title:
  Unity + Skylake + Hyper-V xf86EnableIOPorts: failed to set IOPL for
  I/O (Operation not permitted)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Customer using Lenovo P50 (Skylake) and Surface Book (Skylake) laptops
  tried to start unity in a guest VM on Hyper-V. Kernel 4.4.0-31 started
  as expected, Hyper-V drivers loaded as expected including the
  framebuffer driver, plenty of memory and vCPUs allocated, but x.org
  fails with xf86EnableIOPorts: failed to set IOPL for I/O (Operation
  not permitted), resulting in "no screens found".

  However, when customer used KDE (kubuntu 16.04 with similar kernel) on
  these same systems got a UI as expected. Customer also has no issues
  on non-skylake laptop.

  No unexpected messages seen in dmesg and syslog.

To manage notifications about this bug go to:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.launchpad.net%2Fubuntu%2F%2Bsource%2Fxorg%2F%2Bbug%2F1605798%2F%2Bsubscriptions=02%7C01%7Cmark.d.harris%40microsoft.com%7C5b109efd696a4cb1165208d49e0e90e9%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636307232777628818=BKjEnVGJMmj8wOtrF2UPygODliANcM0K4PkurhADnnI%3D=0

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

Title:
  Unity + Skylake + Hyper-V xf86EnableIOPorts: failed to set IOPL for
  I/O (Operation not permitted)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Customer using Lenovo P50 (Skylake) and Surface Book (Skylake) laptops
  tried to start unity in a guest VM on Hyper-V. Kernel 4.4.0-31 started
  as expected, Hyper-V drivers loaded as expected including the
  framebuffer driver, plenty of memory and vCPUs allocated, but x.org
  fails with xf86EnableIOPorts: failed to set IOPL for I/O (Operation
  not permitted), resulting in "no screens found".

  However, when customer used KDE (kubuntu 16.04 with similar kernel) on
  these same systems got a UI as expected. Customer also has no issues
  on non-skylake laptop.

  No unexpected messages seen in dmesg and syslog.

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

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

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Rodney Beede]

Verified works on trusty as desired.  No more extra ports.

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With isc-dhcp-client:
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  With isc-dhcp-client-noddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Xenial also has both distinct dhclient binary package but in the
  opposite way. We have decided to use the opposite way approach for not
  impacting actual Trusty users by changing the nature of isc-dhcp-
  client itself.

  Caribou and I, slashd, have also tested a couple of release upgrades from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns"

  and both scenarios worked as expected for caribou and I. (See comment
  #42)

  Results :
  ===
  ** Upgrade tested with isc-dhcp-client **

  # dpkg -l
  ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
  ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient

  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient

  ** Upgrade tested with isc-dhcp-noddns (4.2.4-7ubuntu12.9) **

  # dpkg -l
  ii  isc-dhcp-client-noddns   4.2.4-7ubuntu12.9
  amd64   

[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports

[Rodney Beede]

Can confirm for xenial installing the isc-dhcp-client-ddns also works as
expected.   This package enables ddns ports.

When not using this package no random ddns ports as desired.

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

Title:
  isc-dhcp dhclient listens on extra random ports

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  In trusty, there is only 1 version of dhclient, including #define NSUPDATE, 
which introduce DDNS functionnality.
  The DDNS functionnality, generate 2 random extra ports between 1024-65535.

  Impact reported by users :

  "One impact of these random ports is that security hardening becomes more 
difficult. The purpose of these random ports and security implications are 
unknown."
  "We have software that was using one of the lower udp ports but it happened 
to collide with dhclient which seems to allocate 2 random ports."

  There is a randomization mechanism in libdns that prevent dhclient to
  take the sysctl values into account (net.ipv4.ip_local_port_range &
  net.ipv4.ip_local_reserved_ports) to workaround this, and after
  discussion isc-dhcp upstream doesn't want to rely on kernel for
  randomization.

  There is no realtime configuration to disable the feature or
  workaround this. The only possible way is at compile time.

  I also talk with upstream maintainers, and there is no way they will
  accept to reduce the range (1024-65535) for security reason. Reducing
  the port range may facilitate the spoofing.

  Xenial has separated dhclient in two packages :

  isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random 
extra ports)
  isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random 
extra ports)

  The goal here is to reproduce the same situation in Trusty, for this
  bug to be less painful for at least users that doesn't require DDNS
  functionnality.

  [Test Case]

  Run a Trusty image with following package :
  isc-dhcp-client
  isc-dhcp-common

  ```
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port
  ```

  [Regression Potential]

  I did the split such that Trusty users will automatically get "isc-
  dhcp-client-ddns" installed but users bothered by this bug will have
  the option to switch to "isc-dhcp-client-noddns".

  Existing Trusty users can continue to use this DDNS functionality
  after the SRU without any necessary intervention.

  With isc-dhcp-client:
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc
  dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random 
port
  dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749  # <--- extra random 
port

  With isc-dhcp-client-noddns :
  dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc

  Xenial also has both distinct dhclient binary package but in the
  opposite way. We have decided to use the opposite way approach for not
  impacting actual Trusty users by changing the nature of isc-dhcp-
  client itself.

  Caribou and I, slashd, have also tested a couple of release upgrades from 
Trusty to Xenial with both scenarios :
  1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns"
  2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns"

  and both scenarios worked as expected for caribou and I. (See comment
  #42)

  Results :
  ===
  ** Upgrade tested with isc-dhcp-client **

  # dpkg -l
  ii  isc-dhcp-client  4.2.4-7ubuntu12.8
  amd64ISC DHCP client
  ii  isc-dhcp-common  4.2.4-7ubuntu12.8
  amd64common files used by all the isc-dhcp* packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:20114   0.0.0.0:* 
  632/dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  632/dhclient
  udp6   0  0 :::52249:::*  
  632/dhclient

  After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2)
  ii  isc-dhcp-client  4.3.3-5ubuntu12.7
  amd64DHCP client for automatically obtaining an IP address
  ii  isc-dhcp-common  4.3.3-5ubuntu12.7
  amd64common files used by all of the isc-dhcp packages

  # netstat -anputa | grep -i dhclient
  udp0  0 0.0.0.0:68  0.0.0.0:* 
  633/dhclient

  ** Upgrade tested with isc-dhcp-noddns 

[Touch-packages] [Bug 1693915] [NEW] e2fsprogs: ext(2, 3, 4) manpage typo

[Quanah]

Public bug reported:

When running: man ext4

There is an obvious typo at the top:

NAME
   ext2 - the second extended file system
   ext2 - the third extended file system
   ext4 - the fourth extended file system


Clearly, the "third" extended filesystem should be "ext3" not "ext2"

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

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

Title:
  e2fsprogs: ext(2,3,4) manpage typo

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  When running: man ext4

  There is an obvious typo at the top:

  NAME
 ext2 - the second extended file system
 ext2 - the third extended file system
 ext4 - the fourth extended file system

  
  Clearly, the "third" extended filesystem should be "ext3" not "ext2"

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

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

[Touch-packages] [Bug 1693119] Re: package linux-image-extra-4.4.0-66-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-extra-4.4.0-66-generic (not installed) failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I have no additional details.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-66-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kajic  2117 F pulseaudio
  Date: Mon May 22 14:01:17 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=990d601a-911a-40a5-8b0b-401062d17914
  InstallationDate: Installed on 2016-10-06 (229 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-78-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
acpi_sleep=nonvs vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-66-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.name: 09JHRY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1693119/+subscriptions

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

[Touch-packages] [Bug 1608054] Re: IPv6 static addresses in multiple interfaces can't be configured thru interfaces file

[William Atwood]

I also have this same bug.  Details are in a posting in the forum with
title "Three-interface system fails to add one IPv6 address", located at
https://answers.launchpad.net/ubuntu/+question/632391.

The systems are all running Ubuntu 16.04 LTS, with all updates applied.

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

Title:
  IPv6 static addresses in multiple interfaces can't be configured thru
  interfaces file

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Just installed 16.04 over a 14 version. I discovered that the actual
  interfaces file is not working correctly. Tried many choices, even
  using pre-up sleep 10 before configuring the IPv6 manual addresses,
  but didn't worked. This is the example file:

  auto lo
  iface lo inet loopback

  allow-hotplug eth0
  iface eth0 inet static
   mtu 9000
   address 172.16.0.7
   netmask 255.255.255.0
   dns-nameservers 10.10.10.3 80.58.61.250 80.58.61.254 8.8.8.8 8.8.4.4 
2001:470:1f09:495::3 2001:470:20::2

  iface eth0 inet6 auto

  allow-hotplug eth1
  iface eth1 inet static
   mtu 9000
   address 10.10.10.7
   netmask 255.255.255.0

  iface eth1 inet6 static
   autoconf 0
   accept_ra 0
   address 2001:470:1f09:495::7
   netmask 64

  allow-hotplug eth2
  iface eth2 inet static
   mtu 9000
   address 10.10.9.7
   netmask 255.255.255.0
   gateway 10.10.9.1

  iface eth2 inet6 static
   autoconf 0
   accept_ra 0
   address 2001:470:1f1d:275::7
   netmask 64
   gateway fe80::1

  As you can see, both, eth1 and eth2 have manual/static IPv6 addresses.
  Each one is in a different router. Only eth2 is the default gateway
  (eth1 is usen only for internal communication with another LAN).
  However, after reboot, the ifconfig shows:

  eth0  Link encap:Ethernet  direcciónHW 00:0c:29:64:c6:32  
Direc. inet:172.16.0.7  Difus.:172.16.0.255  Másc:255.255.255.0
Dirección inet6: fe80::20c:29ff:fe64:c632/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST  MTU:9000  Métrica:1
Paquetes RX:17 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:32 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000 
Bytes RX:1500 (1.5 KB)  TX bytes:3805 (3.8 KB)

  eth1  Link encap:Ethernet  direcciónHW 00:0c:29:64:c6:3c  
Direc. inet:10.10.10.7  Difus.:10.10.10.255  Másc:255.255.255.0
Dirección inet6: 2001:470:1f09:495::7/64 Alcance:Global
Dirección inet6: fe80::20c:29ff:fe64:c63c/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST  MTU:9000  Métrica:1
Paquetes RX:291 errores:0 perdidos:2 overruns:0 frame:0
Paquetes TX:144 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000 
Bytes RX:34692 (34.6 KB)  TX bytes:16360 (16.3 KB)

  eth2  Link encap:Ethernet  direcciónHW 00:0c:29:64:c6:46  
Direc. inet:10.10.9.7  Difus.:10.10.9.255  Másc:255.255.255.0
Dirección inet6: fe80::20c:29ff:fe64:c646/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST  MTU:9000  Métrica:1
Paquetes RX:1281 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:755 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000 
Bytes RX:105008 (105.0 KB)  TX bytes:1554705 (1.5 MB)

  loLink encap:Bucle local  
Direc. inet:127.0.0.1  Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO  MTU:65536  Métrica:1
Paquetes RX:818 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:818 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1 
Bytes RX:136866 (136.8 KB)  TX bytes:136866 (136.8 KB)

  All what I tried fails. If I issue a manual:
  ip -6 addr add 2001:470:1f1d:275::7/64 dev eth2

  it works.

  I've noticed not sure if this is relevant, that the file
  /etc/network/run/ifstate.eth2 is empty, and /etc/network/run/ifstate
  only contains the other interfaces, but not eth2:

  eth1=eth1
  eth0=eth0
  lo=lo

  Before the upgrade it contained all the interfaces.

  I've used GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0", to keep
  the original interface names, not sure if that's relevant, just in
  case.

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

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

[Touch-packages] [Bug 1674399] [openssl/zesty] possible regression found

[Ubuntu Foundations Team Bug Bot]

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of openssl from zesty-proposed
was performed and bug 1692981 was found.  Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed"
tag from this bug report and add the tag "bot-stop-nagging" to bug
1692981 (not this bug). Thanks!

** Tags added: verification-failed

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

Title:
  OpenSSL CPU detection for AMD Ryzen CPUs

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

Bug description:
  [Impact]

  * Context:

  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
  64bit only (Confirmed with AMD representative). Current OpenSSL
  version in Ryzens still calls SHA for SSSE3 routine as result a number
  of extensions were effectively masked on Ryzen and shows no
  improvement.

  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold

  [2] - sha_ni: SHA1/SHA256 Instruction Extensions

  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...

  * Program to performs the CPUID check:

  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions

  ... Availability of the Intel® SHA Extensions on a particular
  processor can be determined by checking the SHA CPUID bit in
  CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
  using inline assembly, performs the CPUID check:

  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;

     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;

     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );

     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --

  On CPU with sha_ni the program return "1". Otherwise it return "0".

  [Test Case]

   * Reproducible with Xenial/Zesty/Artful release.

   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s

  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55

  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)

  [Regression Potential]

   * Note : IRC discussion with infinity :
  

[Touch-packages] [Bug 1693900] [NEW] apt-get update should return exit code != 0 on error

[Jens Elkner]

Public bug reported:

When running 'apt-get update' (e.g. on a container install post-install
script), apt-get return with exit code 0, even so it wasn't able to
"update" properly. E.g.:

+ apt-get update
Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
  Temporary failure resolving 'de.archive.ubuntu.com'
Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Temporary failure resolving 'security.ubuntu.com'
Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Temporary failure resolving 'de.archive.ubuntu.com'
Reading package lists... Done
W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'de.archive.ubuntu.com'
W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
W: Some index files failed to download. They have been ignored, or old ones 
used instead.

It should be corrected to return useful exit code, so that scripts can
take the appropriate actions ...

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

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  New

Bug description:
  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

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

[Touch-packages] [Bug 1693897] [NEW] It seems like sometimes 'archive' can't be found for a package

[Bryan Seitz]

Public bug reported:

This is for: python-apt 1.4.0~beta2

I wrote a script to find the latest kernel available for each
major.minor, per Ubuntu release (that I configure) and sometimes it
spits out:

Unknown distro for package: linux-image-3.2.0-23-generic - []
precise:
3.13:
3.13.0-117
3.11:
3.11.0-26
3.8:
3.8.0-44
3.5:
3.5.0-54
3.2:
3.2.0-126
xenial:
4.10:
4.10.0-14
4.8:
4.8.0-53
4.4:
4.4.0-78
zesty:
4.10:
4.10.0-21

Where archive is blank.  Other times it works...

Please advise.

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  It seems like sometimes 'archive' can't be found for a package

Status in python-apt package in Ubuntu:
  New

Bug description:
  This is for: python-apt 1.4.0~beta2

  I wrote a script to find the latest kernel available for each
  major.minor, per Ubuntu release (that I configure) and sometimes it
  spits out:

  Unknown distro for package: linux-image-3.2.0-23-generic - []
  precise:
  3.13:
  3.13.0-117
  3.11:
  3.11.0-26
  3.8:
  3.8.0-44
  3.5:
  3.5.0-54
  3.2:
  3.2.0-126
  xenial:
  4.10:
  4.10.0-14
  4.8:
  4.8.0-53
  4.4:
  4.4.0-78
  zesty:
  4.10:
  4.10.0-21

  Where archive is blank.  Other times it works...

  Please advise.

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

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

[Touch-packages] [Bug 1693895] [NEW] ubuntu budgie suspend to ram fails on Macbook Pro Ret

[Wolf Rogner]

Public bug reported:

A default installation of Ubuntu Budgie fails to suspend to RAM.

Workaround:
sudo apt-get install pm-utils

=> Suspend works

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-21ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Fri May 26 20:13:16 2017
InstallationDate: Installed on 2017-05-25 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Apple Inc. MacBookPro10,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug zesty

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

Title:
  ubuntu budgie suspend to ram fails on Macbook Pro Ret

Status in systemd package in Ubuntu:
  New

Bug description:
  A default installation of Ubuntu Budgie fails to suspend to RAM.

  Workaround:
  sudo apt-get install pm-utils

  => Suspend works

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri May 26 20:13:16 2017
  InstallationDate: Installed on 2017-05-25 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=873566f9-4c01-4dae-8ca9-99c95dfbe269 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1608054] Re: IPv6 static addresses in multiple interfaces can't be configured thru interfaces file

[Launchpad Bug Tracker]

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

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

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

Title:
  IPv6 static addresses in multiple interfaces can't be configured thru
  interfaces file

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  Just installed 16.04 over a 14 version. I discovered that the actual
  interfaces file is not working correctly. Tried many choices, even
  using pre-up sleep 10 before configuring the IPv6 manual addresses,
  but didn't worked. This is the example file:

  auto lo
  iface lo inet loopback

  allow-hotplug eth0
  iface eth0 inet static
   mtu 9000
   address 172.16.0.7
   netmask 255.255.255.0
   dns-nameservers 10.10.10.3 80.58.61.250 80.58.61.254 8.8.8.8 8.8.4.4 
2001:470:1f09:495::3 2001:470:20::2

  iface eth0 inet6 auto

  allow-hotplug eth1
  iface eth1 inet static
   mtu 9000
   address 10.10.10.7
   netmask 255.255.255.0

  iface eth1 inet6 static
   autoconf 0
   accept_ra 0
   address 2001:470:1f09:495::7
   netmask 64

  allow-hotplug eth2
  iface eth2 inet static
   mtu 9000
   address 10.10.9.7
   netmask 255.255.255.0
   gateway 10.10.9.1

  iface eth2 inet6 static
   autoconf 0
   accept_ra 0
   address 2001:470:1f1d:275::7
   netmask 64
   gateway fe80::1

  As you can see, both, eth1 and eth2 have manual/static IPv6 addresses.
  Each one is in a different router. Only eth2 is the default gateway
  (eth1 is usen only for internal communication with another LAN).
  However, after reboot, the ifconfig shows:

  eth0  Link encap:Ethernet  direcciónHW 00:0c:29:64:c6:32  
Direc. inet:172.16.0.7  Difus.:172.16.0.255  Másc:255.255.255.0
Dirección inet6: fe80::20c:29ff:fe64:c632/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST  MTU:9000  Métrica:1
Paquetes RX:17 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:32 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000 
Bytes RX:1500 (1.5 KB)  TX bytes:3805 (3.8 KB)

  eth1  Link encap:Ethernet  direcciónHW 00:0c:29:64:c6:3c  
Direc. inet:10.10.10.7  Difus.:10.10.10.255  Másc:255.255.255.0
Dirección inet6: 2001:470:1f09:495::7/64 Alcance:Global
Dirección inet6: fe80::20c:29ff:fe64:c63c/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST  MTU:9000  Métrica:1
Paquetes RX:291 errores:0 perdidos:2 overruns:0 frame:0
Paquetes TX:144 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000 
Bytes RX:34692 (34.6 KB)  TX bytes:16360 (16.3 KB)

  eth2  Link encap:Ethernet  direcciónHW 00:0c:29:64:c6:46  
Direc. inet:10.10.9.7  Difus.:10.10.9.255  Másc:255.255.255.0
Dirección inet6: fe80::20c:29ff:fe64:c646/64 Alcance:Enlace
ACTIVO DIFUSIÓN FUNCIONANDO MULTICAST  MTU:9000  Métrica:1
Paquetes RX:1281 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:755 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1000 
Bytes RX:105008 (105.0 KB)  TX bytes:1554705 (1.5 MB)

  loLink encap:Bucle local  
Direc. inet:127.0.0.1  Másc:255.0.0.0
Dirección inet6: ::1/128 Alcance:Anfitrión
ACTIVO BUCLE FUNCIONANDO  MTU:65536  Métrica:1
Paquetes RX:818 errores:0 perdidos:0 overruns:0 frame:0
Paquetes TX:818 errores:0 perdidos:0 overruns:0 carrier:0
colisiones:0 long.colaTX:1 
Bytes RX:136866 (136.8 KB)  TX bytes:136866 (136.8 KB)

  All what I tried fails. If I issue a manual:
  ip -6 addr add 2001:470:1f1d:275::7/64 dev eth2

  it works.

  I've noticed not sure if this is relevant, that the file
  /etc/network/run/ifstate.eth2 is empty, and /etc/network/run/ifstate
  only contains the other interfaces, but not eth2:

  eth1=eth1
  eth0=eth0
  lo=lo

  Before the upgrade it contained all the interfaces.

  I've used GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0", to keep
  the original interface names, not sure if that's relevant, just in
  case.

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

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

[Touch-packages] [Bug 1610565] Re: package winbind 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

[Andreas Hasenack]

This is a bug in insserv, and there are many similar reports about this
over there.

** Summary changed:

- package winbind 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
+ update-rc.d: error: insserv rejected the script header

** Package changed: samba (Ubuntu) => insserv (Ubuntu)

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

Title:
  update-rc.d: error: insserv rejected the script header

Status in insserv package in Ubuntu:
  New

Bug description:
  Happened on startup.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: winbind 2:4.3.9+dfsg-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug  2 19:43:10 2016
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-07-30 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   nautilus 1:3.18.4.is.3.14.3-0ubuntu4
   gvfs 1.28.2-1ubuntu1~16.04.1
  SambaClientRegression: Yes
  SourcePackage: samba
  Title: package winbind 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to 
install/upgrade: subprocess installed post-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Chow Loong Jin]

** Also affects: libzen (Ubuntu Artful)
   Importance: Undecided
 Assignee: Chow Loong Jin (hyperair)
   Status: Fix Released

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

** Also affects: libzen (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: libzen (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

-- 
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:
  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. This affects the following reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

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

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 1610565] [NEW] update-rc.d: error: insserv rejected the script header

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Happened on startup.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: winbind 2:4.3.9+dfsg-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Tue Aug  2 19:43:10 2016
ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
InstallationDate: Installed on 2016-07-30 (6 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 nautilus 1:3.18.4.is.3.14.3-0ubuntu4
 gvfs 1.28.2-1ubuntu1~16.04.1
SambaClientRegression: Yes
SourcePackage: samba
Title: package winbind 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial
-- 
update-rc.d: error: insserv rejected the script header
https://bugs.launchpad.net/bugs/1610565
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to insserv in Ubuntu.

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

[Touch-packages] [Bug 1670059] Re: [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot

[spm2011]

See also https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1583801

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

Title:
  [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in
  before Boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When (re)booting with headphones in, audio won't play. Once the headphones 
are unplugged, it will start to come through the speakers and will work with 
the headphones when they are plugged back in.
  Expected headphones to be detected automatically even if plugged in before 
boot.

  This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64).
  ALSA Info attached.

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

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

This has been assigned upstream ISC bug: ISC-Bugs #45294

ISC's bug tracking is not public, so there is no way to track any
upstream progress in fixing this.

** Bug watch added: Debian Bug tracker #863426
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863426

** Also affects: isc-dhcp (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863426
   Importance: Unknown
   Status: Unknown

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New
Status in isc-dhcp package in Debian:
  Unknown

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Chow Loong Jin]

This bug was fixed in the package libzen - 0.4.35-1

---
libzen (0.4.35-1) experimental; urgency=medium

  * [015b0fa] Imported Upstream version 0.4.35

 -- Chow Loong Jin   Tue, 04 Apr 2017 00:39:46
+0800

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

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

Bug description:
  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. This affects the following reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

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

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 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

Test packages available in this PPA
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1693819

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

This is specifically important for any configuration that wants to have
both a IPv4 address and DHCPv6 IPv6 address on a single interface, and
uses ifupdown for interface management, and wants independent control of
the 4 and 6 address.  Meaning, to be able to add or remove an
interface's IPv6 DHCPv6 address, while leaving the interface up and
still configured with its IPv4 address.  The ifupdown program does not
have any mechanism for controlling IPv4 and IPv6 addresses on a single
interface separately, so interface aliases are the most convenient way
to keep using ifupdown and be able to control the addresses separately.
An example ifupdown configuration might be:

auto eth0
iface eth0 inet manual
  pre-down ifdown eth0:1
  pre-down ifdown eth0:2

auto eth0:1
iface eth0:1 inet dhcp

auto eth0:2
iface eth0:2 inet6 dhcp


That configuration will start dhcp for both IPv4 and IPv6 addresses on eth0 at 
boot, and will allow running 'sudo ifdown eth0:1' to remove the IPv4 address 
only, while leaving the IPv6 address, or 'sudo ifdown eth0:2' to remove the 
IPv6 address only, while leaving the IPv4 address.  Or, 'sudo ifdown eth0' will 
remove both addresses and take down the physical interface.  Since this 
configuration uses an interface alias for DHCPv6, the current isc-dhcp-client 
fails, and requires the patch from the attached debdiffs to work.

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] [NEW] libzen wasn't compiled with large file support

[Chow Loong Jin]

Public bug reported:

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. This affects the following reverse-dependencies:

 - libmediainfo
 - mediainfo
 - mediaconch

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

** Affects: libzen (Ubuntu)
 Importance: Undecided
 Assignee: Chow Loong Jin (hyperair)
 Status: Fix Released


** Tags: patch

** Description changed:

- The switch to cmake caused two compilation flags to be accidentally
- dropped: -D_LARGE_FILES -D_FILE_OFFSET_BITS=64
+ 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. This affects the following reverse-dependencies:
  
-  - libmediainfo
-  - mediainfo
-  - mediaconch
+  - libmediainfo
+  - mediainfo
+  - mediaconch
  
  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

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

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

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

Bug description:
  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. This affects the following reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

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

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 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

** Changed in: isc-dhcp (Ubuntu Zesty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: isc-dhcp (Ubuntu Yakkety)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: isc-dhcp (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: isc-dhcp (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: isc-dhcp (Ubuntu Zesty)
   Importance: Undecided => Low

** Changed in: isc-dhcp (Ubuntu Yakkety)
   Importance: Undecided => Low

** Changed in: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: isc-dhcp (Ubuntu Trusty)
   Importance: Undecided => Low

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1299838] Re: [Radiance] Selection points next to menu items disappear when highlighted

[Amr Ibrahim]

I'll try to explain the bug in steps. I reported it against Trusty.
1. Change the theme to Radiance
2. Start Libreoffice Writer
3. Open the View menu and hover the mouse pointer over the first item 'Normal' 
and notice that the selection point disappears
4. This also happens outside applications
5. Hover over the keyboard indicator (if you have multiple input languages)

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => New

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

Title:
  [Radiance] Selection points next to menu items disappear when
  highlighted

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When using the Radiance theme, the selection points, which are next to
  menu items, disappear when highlighted. See the attached screen-cast
  which describes the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-themes 14.04+14.04.20140327-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 30 19:05:08 2014
  InstallationDate: Installed on 2014-03-08 (22 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140304)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1299838] Re: [Radiance] Selection points next to menu items disappear when highlighted

[Amr Ibrahim]

I'll try to explain the bug in steps. I reported it against Trusty.
1. Change the theme to Radiance
2. Start Libreoffice Writer
3. Open the View menu and hover the mouse pointer over the first item 'Normal' 
and notice that the selection point disappears
4. This also happens outside applications
5. Hover over the keyboard indicator (if you have multiple input languages)

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

Title:
  [Radiance] Selection points next to menu items disappear when
  highlighted

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When using the Radiance theme, the selection points, which are next to
  menu items, disappear when highlighted. See the attached screen-cast
  which describes the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: light-themes 14.04+14.04.20140327-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 30 19:05:08 2014
  InstallationDate: Installed on 2014-03-08 (22 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140304)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Kai-Heng Feng]

Great, Kailiang has Launchpad account =)

@Kailiang
I personally cannot reproduce the issue on my $10 Logitech headphone, maybe 
this bug can only be reproduced on more beefy headphone.

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

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

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

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1627769] Re: limits.conf not applied

[Adam Dingle]

OK - I was finally able to get this working in 17.04 after more
experimentation, which revealed the following caveats:

- Ubuntu will respect limits you put in /etc/security/limits.conf (or
/etc/security/limits.d/audio.conf), but **only after a reboot**.
Logging out and back in are not sufficient to trigger a change.  I
suspect that rebooting only became necessary after the recent transition
to systemd.

- Limits in /etc/systemd/user.conf are applied after logging out and in.

- I've only been able to change NOFILE (the max number of open files) by
editing /etc/systemd/system.conf and then rebooting (logging out/in is
not enough).  Setting this value in user.conf or limits.conf seems to
have no effect.

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

Title:
  limits.conf not applied

Status in jackd2 package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgraded to 16.10 Yakkety, modifications in
  /etc/security/limits.conf are not taken into consideration when
  logging in the graphical interface.

  
  /etc/security/limits.conf:
  @audio   -  rtprio 99
  @audio   -  memlockunlimited

  I tried the same settings in /etc/security/limits.d/audio.conf, to the
  same results.

  
  After logging in Unity, opening a console, the limits are not set:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0

  
  Reloging to my user via bash DOES apply the limits:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0
  blablack@ideaon:~$ su blablack
  Password: 
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) unlimited
  real-time priority  (-r) 95

  
  Switching to a console (ctrl+alt+f1) and logging in would apply the limits as 
well.



  The exact same setup used to work fine on Xenial 16.04 before upgrade.

  
  If you need any more information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 17:27:10 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Kai-Heng Feng]

Sorry, my bad, ALC256 doesn't have aaloop at first place, so my kernel
does nothing =(

I'll ask Realtek codec guy about this issue.

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

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

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

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Eric Desrochers]

** Also affects: isc-dhcp (Ubuntu Artful)
   Importance: Low
 Assignee: Dan Streetman (ddstreet)
   Status: New

** Also affects: isc-dhcp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Zesty)
   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/1693819

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

** Patch added: "lp1693819-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884176/+files/lp1693819-artful.debdiff

** Changed in: isc-dhcp (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => Low

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

** Patch added: "lp1693819-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884175/+files/lp1693819-zesty.debdiff

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

** Patch added: "lp1693819-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884174/+files/lp1693819-yakkety.debdiff

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

** Patch added: "lp1693819-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884173/+files/lp1693819-xenial.debdiff

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

** Patch added: "lp1693819-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+attachment/4884172/+files/lp1693819-trusty.debdiff

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New
Status in isc-dhcp source package in Trusty:
  New
Status in isc-dhcp source package in Xenial:
  New
Status in isc-dhcp source package in Yakkety:
  New
Status in isc-dhcp source package in Zesty:
  New
Status in isc-dhcp source package in Artful:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1447099] Re: /sbin/upstart:indicator-session-unknown-user-error

[Chuck Ritola]

Still getting the error.
xubuntu 16.04, x86-64, last updated 05-25-2017.

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

Title:
  /sbin/upstart:indicator-session-unknown-user-error

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Fix Released
Status in upstart source package in Vivid:
  Confirmed
Status in upstart source package in Wily:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding upstart.  This problem was most recently seen with version
  1.13.2-0ubuntu13, the problem page at
  https://errors.ubuntu.com/problem/09ab1b2ed4cff7556ed135307deb9f99c107193a
  contains more details.

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

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

[Touch-packages] [Bug 1520615] Re: Use of Ubuntu logo as default app icon dilutes the brand

[Matthew Paul Thomas]

** Attachment added: "screenshot of the problem"
   
https://bugs.launchpad.net/snapstore/+bug/1520615/+attachment/4884155/+files/1520615-Ubuntu-logo-as-app-icon.cropped.png

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

Title:
  Use of Ubuntu logo as default app icon dilutes the brand

Status in Canonical System Image:
  Confirmed
Status in Click Package Index:
  Invalid
Status in Snap Store:
  Triaged
Status in Software Center Agent:
  Invalid
Status in ubuntu-sdk-ide package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Incomplete
Status in ubuntu-touch-meta package in Ubuntu:
  New

Bug description:
  Currently, MyApps and CPI are using the "placeholder-app-icon.png"
  from the Suru theme, which is a basic greyscale image, including a
  version of the Ubuntu logo. Showing this logo as the app icon for apps
  which have no icon, implies they are officially supported apps by
  Ubuntu, and dilutes the brand and trademark, when they are not
  actually such apps, particularly when they have no function directly
  linked to any part of Ubuntu.

  Instead, a better representation would be a generic representation of
  an app window or similar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1520615/+subscriptions

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

[Touch-packages] [Bug 1520615] Re: Use of Ubuntu logo as default app icon dilutes the brand

[Matthew Paul Thomas]

This is still a problem with snapstore, the sequel to MyApps.

** Project changed: ubuntu-ux => snapstore

** Changed in: snapstore
 Assignee: Matthieu James (tiheum) => (unassigned)

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

Title:
  Use of Ubuntu logo as default app icon dilutes the brand

Status in Canonical System Image:
  Confirmed
Status in Click Package Index:
  Invalid
Status in Snap Store:
  Triaged
Status in Software Center Agent:
  Invalid
Status in ubuntu-sdk-ide package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Incomplete
Status in ubuntu-touch-meta package in Ubuntu:
  New

Bug description:
  Currently, MyApps and CPI are using the "placeholder-app-icon.png"
  from the Suru theme, which is a basic greyscale image, including a
  version of the Ubuntu logo. Showing this logo as the app icon for apps
  which have no icon, implies they are officially supported apps by
  Ubuntu, and dilutes the brand and trademark, when they are not
  actually such apps, particularly when they have no function directly
  linked to any part of Ubuntu.

  Instead, a better representation would be a generic representation of
  an app window or similar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1520615/+subscriptions

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

[Touch-packages] [Bug 1627769] Re: limits.conf not applied

[Adam Dingle]

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

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

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

Title:
  limits.conf not applied

Status in jackd2 package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgraded to 16.10 Yakkety, modifications in
  /etc/security/limits.conf are not taken into consideration when
  logging in the graphical interface.

  
  /etc/security/limits.conf:
  @audio   -  rtprio 99
  @audio   -  memlockunlimited

  I tried the same settings in /etc/security/limits.d/audio.conf, to the
  same results.

  
  After logging in Unity, opening a console, the limits are not set:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0

  
  Reloging to my user via bash DOES apply the limits:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0
  blablack@ideaon:~$ su blablack
  Password: 
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) unlimited
  real-time priority  (-r) 95

  
  Switching to a console (ctrl+alt+f1) and logging in would apply the limits as 
well.



  The exact same setup used to work fine on Xenial 16.04 before upgrade.

  
  If you need any more information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 17:27:10 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1627769] Re: limits.conf not applied

[Adam Dingle]

Artful (17.10) has systemd 233.  I just ran the Artful daily build in
VirtualBox and tried this there.  I see the same problem in Artful:
neither a change to /etc/security/limits.conf nor /etc/systemd/user.conf
affects the limits I see when I run 'prlimit' in a terminal window.

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

Title:
  limits.conf not applied

Status in jackd2 package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgraded to 16.10 Yakkety, modifications in
  /etc/security/limits.conf are not taken into consideration when
  logging in the graphical interface.

  
  /etc/security/limits.conf:
  @audio   -  rtprio 99
  @audio   -  memlockunlimited

  I tried the same settings in /etc/security/limits.d/audio.conf, to the
  same results.

  
  After logging in Unity, opening a console, the limits are not set:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0

  
  Reloging to my user via bash DOES apply the limits:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0
  blablack@ideaon:~$ su blablack
  Password: 
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) unlimited
  real-time priority  (-r) 95

  
  Switching to a console (ctrl+alt+f1) and logging in would apply the limits as 
well.



  The exact same setup used to work fine on Xenial 16.04 before upgrade.

  
  If you need any more information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 17:27:10 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

This problem is because isc-dhcp strips the interface alias when it
enumerates the system interfaces, i.e. in common/discover.c function
next_iface():

/* interface aliases look like "eth0:1" or "wlan1:3" */ 

s = strchr(info->name, ':');

if (s != NULL) {

*s = '\0';  

}   


However when later searching the previously-enumerated list for the
matching interface for the cmdline interface parameter name, it does not
strip the interface alias from the cmdline interface name, i.e. in
common/discover.c function discover_interfaces():

/* Cycle through the list of interfaces looking for IP addresses. */

while (next_iface(, , )) {  



/* See if we've seen an interface that matches this one. */ 

for (tmp = interfaces; tmp; tmp = tmp->next) {  

if (!strcmp(tmp->name, info.name))  

break;  

}   



The 'info' interface will always have its info.name set to the actual interface 
name, without any alias extension, while the 'tmp' interface (from the cmdline) 
will have its tmp->name set to the interface including alias extension; the 
strcmp then never matches, so isc-dhcp is not able to correctly match the 
requested interface with the actual system interface.

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1693819] [NEW] dhclient DHCPv6 does not work with interface alias

[Dan Streetman]

Public bug reported:

[Impact]

The isc-dhcp-client dhclient program does not work with interface alias
names, e.g. eth0:1.  It fails immediately.

[Test Case]

On trusty through artful, find an interface that is connected to a
network that has a DHCPv6 server on it.  First verify it can get a
DHCPv6 address, e.g.:

$ sudo dhclient -6 -v ens7

that should successfully set up a DHCPv6 address on the interface.  Then
release the interface:

$ sudo dhclient -6 -v -r ens7

Now, try again but use the interface alias, e.g.:

$ sudo dhclient -6 -v ens7:1

It should succeed, but it will fail with:

no link-local IPv6 address for ens7:1

[Regression Potential]

Changing how isc-dhcp handles (enumerates/lists/compares) interface
names may lead to isc-dhcp using the wrong interface or failing to find
the correct interface to use.  However, if the only change is to strip
the alias part from the interface during comparison, the possibility of
error should be small, since all interface aliases point back to the
same physical interface.

[Other Info]

This bug exists in the upstream isc-dhcp; the ISC has no public bug
tracker, and only accepts bug reports via private email, which has been
sent.

** Affects: isc-dhcp (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/1693819

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1317013] Re: Network indicator has mysterious "R" triangle icon

[Matthew Paul Thomas]

Since Ubuntu Phone has been retired, whether it was fixed is moot, in
both senses of the word.

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

Title:
  Network indicator has mysterious "R" triangle icon

Status in indicator-network package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Unicorn r13

  1. Flash the phone.
  2. Start up the phone.
  3. Look at the top of the screen.

  What you see: A mysterious "R" in a triangle.

  What you should see: No such icon.

  This is not in the spec and I don't know what it's for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1317013/+subscriptions

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

[Touch-packages] [Bug 1186754] Re: Use icon theme for starred icons

[Matthew Paul Thomas]

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

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

Title:
  Use icon theme for starred icons

Status in Ubuntu theme:
  Incomplete
Status in software-center package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  As of GNOME 3.8 in Saucy, the gnome icons themes ('gnome', symbolic,
  and HighContrast) provide star icons. If Software Center would use
  these theme icons, it would provide more consistency with other apps
  that use starred rankings and should simplify the code
  (softwarecenter/ui/gtk3/widgets/stars.py).

  The icon names are
  starred
  semi-starred
  semi-starred-rtl
  non-starred

  (Although we may need to backport the semi-starred icons for the
  'gnome' theme since those are missing:
  https://bugzilla.gnome.org/689098)

  I'm adding a ubuntu-themes task to this bug as you may want to move
  the existing star icons from softwarecenter/ui/qml/ to that package.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: software-center 5.6.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sun Jun 2 11:11:51 2013
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (25 days ago)

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

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

[Touch-packages] [Bug 1146045] Re: Merge in and replace branding-ubuntu package

[Jeremy Bicha]

Oops, branding-ubuntu is the name. It's still part of the default
ubuntu-desktop install.

** Summary changed:

- Merge in and replace ubuntu-branding package
+ Merge in and replace branding-ubuntu package

** Description changed:

  Since ubuntu-themes is the new Raring package containing the contents of
  the former light-themes, ubuntu-artwork, ubuntu-mono packages, I think
- it would make sense for ubuntu-branding to be included too. ubuntu-
- branding simply contains Ubuntu-themed art for Aisleriot & Mahjongg.
+ it would make sense for branding-ubuntu to be included too. branding-
+ ubuntu simply contains Ubuntu-themed art for Aisleriot & Mahjongg.

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => New

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

Title:
  Merge in and replace branding-ubuntu package

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Since ubuntu-themes is the new Raring package containing the contents
  of the former light-themes, ubuntu-artwork, ubuntu-mono packages, I
  think it would make sense for branding-ubuntu to be included too.
  branding-ubuntu simply contains Ubuntu-themed art for Aisleriot &
  Mahjongg.

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

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

[Touch-packages] [Bug 1628474] Re: keyboard keys in GtkShortcuts should have different color than background

[Jeremy Bicha]

Daniel, could you look again? I'm still able to reproduce this in Ubuntu
17.10 Alpha "Artful", running GNOME Shell with Ambiance.

** Changed in: ubuntu-themes (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  keyboard keys in GtkShortcuts should have different color than
  background

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Many GNOME apps have a new Keyboard Shortcuts popup window available
  in their app menu (this feature was introduced in GTK 3.20).

  Ambiance and Radiance don't style this window correctly - there's no
  contrast between the displayed keyboard keys and the background.

  I'm attaching screenshots of evince's Keyboard Shortcuts popup
  (available in Help > Keyboard Shortcuts) with Ambiance and Adwaita.

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

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

[Touch-packages] [Bug 1693796] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128. fail to install chrome

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128. fail to install chrome browser

Status in gconf package in Ubuntu:
  New

Bug description:
  Fail to install Chrome web browser

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri May 26 15:21:34 2017
  Df:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-25 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693796] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128. fail to install chrom

[Pier Luigi Bonucci]

Public bug reported:

Fail to install Chrome web browser

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Fri May 26 15:21:34 2017
Df:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-25 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128. fail to install chrome browser

Status in gconf package in Ubuntu:
  New

Bug description:
  Fail to install Chrome web browser

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri May 26 15:21:34 2017
  Df:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-25 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems

[Dustin Kirkland ]

This is great, Trent!

Andres, could you get someone to look at this and merge it upstream?

Thanks!
Dustin

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

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

Title:
  maas install fails inside of a 16.04 lxd container due to avahi
  problems

Status in MAAS:
  Invalid
Status in avahi package in Ubuntu:
  In Progress
Status in lxd package in Ubuntu:
  Invalid

Bug description:
  The bug, and workaround, are clearly described in this mailing list
  thread:

  https://lists.linuxcontainers.org/pipermail/lxc-
  users/2016-January/010791.html

  I'm trying to install MAAS in a LXD container, but that's failing due
  to avahi package install problems.  I'm tagging all packages here.

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

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

[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Esokrates]

Confirming Daniel van Vugt: The kernel
http://people.canonical.com/~khfeng/lp1654448/ does not improve the
situation.

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

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

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

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1186754] Re: Use icon theme for starred icons

[Matthew Paul Thomas]

Still the case in 14.04: the USC star icons are different from the
standard ones seen in Rhythmbox (for example), but the standard ones are
too nasty to use.

** Changed in: software-center (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Use icon theme for starred icons

Status in Ubuntu theme:
  Incomplete
Status in software-center package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  As of GNOME 3.8 in Saucy, the gnome icons themes ('gnome', symbolic,
  and HighContrast) provide star icons. If Software Center would use
  these theme icons, it would provide more consistency with other apps
  that use starred rankings and should simplify the code
  (softwarecenter/ui/gtk3/widgets/stars.py).

  The icon names are
  starred
  semi-starred
  semi-starred-rtl
  non-starred

  (Although we may need to backport the semi-starred icons for the
  'gnome' theme since those are missing:
  https://bugzilla.gnome.org/689098)

  I'm adding a ubuntu-themes task to this bug as you may want to move
  the existing star icons from softwarecenter/ui/qml/ to that package.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: software-center 5.6.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Sun Jun 2 11:11:51 2013
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: Upgraded to saucy on 2013-05-07 (25 days ago)

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

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

[Touch-packages] [Bug 1456670] Re: debootstrap failure: insserv: Service mountdevsubfs has to be enabled to start service hwclock

[Audun Gangsto]

I also encountered this on a xenial machine where the upgrade somehow
was broken, and 'apt install' would give the following errors:

Preconfiguring packages ...
Setting up util-linux (2.27.1-6ubuntu3.2) ...
insserv: Service mountdevsubfs has to be enabled to start service hwclock
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package util-linux (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 util-linux
E: Sub-process /usr/bin/dpkg returned an error code (1)

The solution for us was to run

'dpkg-reconfigure initscripts'

and

'apt install'

to configure the large amount of unconfigured remaining packages.

Not sure why it happened, but i am guessing something was upgraded and
configured in the wrong order.

It works fine again after our solution.

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

Title:
  debootstrap failure: insserv: Service mountdevsubfs has to be enabled
  to start service hwclock

Status in sysvinit package in Ubuntu:
  Fix Released
Status in sysvinit source package in Wily:
  Fix Released

Bug description:
  Since today, debootstrap'ing wily is broken:

  W: Failure while configuring required packages.
  W: See /tmp/wily/debootstrap/debootstrap.log for details (possibly the 
package util-linux is at fault)

  Setting up util-linux (2.26.2-3ubuntu1) ...
  update-alternatives: using /bin/more to provide /usr/bin/pager (pager) in 
auto mode
  insserv: Service mountdevsubfs has to be enabled to start service hwclock
  insserv: exiting now!
  update-rc.d: error: insserv rejected the script header
  dpkg: error processing package util-linux (--configure):
   subprocess installed post-installation script returned error exit status 1

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

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

[Touch-packages] [Bug 1693779] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Crash

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri May 26 09:32:54 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-11 (14 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1693779] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Ivo Xavier]

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

Public bug reported:

Crash

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Fri May 26 09:32:54 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-11 (14 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Crash

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri May 26 09:32:54 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-11 (14 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Daniel van Vugt]

** Also affects: dell-sputnik
   Importance: Undecided
   Status: New

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

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

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

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1646739] Re: "Use of uninitialized value" in debconf via update-manager

[Colin Watson]

** Changed in: php7.0 (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: update-manager (Ubuntu)
   Status: Fix Released => Confirmed

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1675357] Re: Mir sending key repeat events continually to nested shell after VT switch (causes Unity8 lockup for a while)

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2778

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

Title:
  Mir sending key repeat events continually to nested shell after VT
  switch (causes Unity8 lockup for a while)

Status in Canonical System Image:
  In Progress
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in qtmir source package in Xenial:
  Invalid
Status in unity8 source package in Xenial:
  Invalid

Bug description:
  Steps:
  * log in to unity8
  * Ctrl+Alt+F* to a different vt, or log in to a different user session
  * go back to the unity8 vt

  Expected:
  * session is locked, but working

  Current:
  * unity8 starts spinning for a time proportional to the period it was inactive
  * if it was inactive long enough, it doesn't seem to recover at all

  It seems it's "catching up" in some way, maybe with input, maybe
  frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2555]
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Mar 23 11:36:39 2017
  InstallationDate: Installed on 2016-05-06 (320 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (120 days ago)

  Causes:
  The mir::input::KeyRepeatDispatcher is running inside the nested mirserver 
even though there is another instance running inside the host server. A few 
months ago qtmir used to replace the key repeater by replacing mirs  
dispatcher. And key repeat is not disabled within the nested server. So both 
the host and the nested server are producing repeat events.
    Now due to a logic error inside mirserver the key repeat dispatcher is not 
hooked up to the input device hub when running inside the nested server. The 
input device hub would tell the key repeater when devices get removed - i.e. 
due to vt switching. So it never notices that the devices go away continues to 
produce those events indefinitely.

  This applies to all currently pressed buttons. I.e. you can open an
  edit field and press 'w' while simultaneously pressing Ctrl+Alt+FX to
  switch to another VT. On return 'w' will be repeated indefinitely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675357/+subscriptions

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

[Touch-packages] [Bug 1677239] Re: mir_demo_standalone_render_overlays fails to link

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2778

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

Title:
  mir_demo_standalone_render_overlays fails to link

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in mir source package in Xenial:
  Fix Committed

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console

  11:41:20 [ 52%] Linking CXX executable 
../../../../bin/mir_demo_standalone_render_overlays.bin
  11:41:20 cd 
/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1
  11:41:20 /usr/lib/ccache/c++ -g -O2 
-fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o 
../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic 
../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 
../../../capnproto/libmircapnproto.a -lkj -lcapnp 
../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system 
-lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 
-L/lib/x86_64-linux-gnu -ludev -ludev
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, 
unsigned long) const@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE'

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

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

[Touch-packages] [Bug 1675138] Re: Please transition to Boost 1.62

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2778

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

Title:
  Please transition to Boost 1.62

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Fix Released
Status in mir source package in Xenial:
  Fix Committed

Bug description:
  There is an ongoing transition to Boost 1.62 and mir is one of the last 
affected packages:
  http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html

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

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

[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Esokrates]

@vanvugt: The earphones I tested (Bose Soundtrue Ultra) are Android
ones. I have also tested headphones with no microphone (Sennheiser
HD202).

@kaihengfeng: I will install Ubuntu from scratch in order to test your
kernelsl

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2778

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

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available() from
  libinput_device_config_accel_set_speed() from
  mir::input::evdev::LibInputDevice::apply_settings()

Status in Canonical System Image:
  Fix Committed
Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in Unity System Compositor:
  Invalid
Status in mir package in Ubuntu:
  Triaged
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in mir source package in Xenial:
  Fix Committed
Status in unity-system-compositor source package in Xenial:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-system-compositor.  This problem was most recently seen with package 
version 0.9.1+17.04.20170216-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/. 

  It seems that the configuration change is requested just a moment
  before the device gets removed. The change actions are serialized,
  depending on where there memory of mir::input::DefaultDevice is
  allocated the segfault either occurs inside the lambda or inside
  underlying mir::input::LibInputDevice in the platform. The activities
  on input dispatch device removal and reconfiguration are serialized
  inside the input thread, so we just need to clean the action queue (or
  have multiple queues) before removing the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions

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

[Touch-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

[Ben]

Just a few updates which may be of use to anyone else having the same
issues...

1). As this issue persists without a truly good solution, it may be a
good idea to simply replace the wifi card with, say, an Atheros one
which works better. You can find them relatively cheaply on ebay.

2). One of the major issues that I was having was that my main Wifi
would crash internally, then whenever I tried to plug in a USB Wifi
adapter they wouldn't work either, leaving me literally without any
method of getting (wireless) internet. I assumed these two issues were
connected, however, further research has led me to believe otherwise.

I tried entirely removing the internal wifi card to see if that would
make a difference on the USB wifi cards, yet still neither of mine
worked. Further looking revealed one or two strange oddities...

phy#1
Interface wlx000f6001cb1f
ifindex 3
wdev 0x10001
addr 00:0f:60:01:cb:1f
type managed
txpower 20.00 dBm

The interface is WAY out of convention. As explained here
(https://superuser.com/questions/1086632/wlan1-showing-as-weird-
characters#1086705), interface names are limited to 16 bytes. My theory
is that when network-manager tries to connect with this interface, it
breaks that limit. The solution suggested in that thread works, append
net.ifnames=0 to the kernel parameters in grub and suddenly all of my
USB wifi adapters work fantastically.

I have a feeling this itself may warrant a separate bug report, I'll do
some looking and see if anyone else is having the same issue/if
someone's already reported it.

TL;DR: If your USB wifi doesn't work and you get weird/long interface
names from "iw dev", use "net.ifnames=0" to fix the interface name and
take back your wifi.

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

Title:
  Intel Wireless 7260 often crashes

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

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 

[Touch-packages] [Bug 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2778

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

Title:
  [SRU] Mir needs to be updated to 0.26 in 16.04LTS

Status in mir package in Ubuntu:
  In Progress
Status in mir source package in Xenial:
  Incomplete

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client apps don't start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 Unity8 and unity-system-compositor "server" packages
    2 toolkits and other "clients" of Mir

  "Server" packages from the archive will stop working in the LTS as
  they will continue using the earlier libmirserver.so.38 (from Mir
  0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26.
  This is unimportant as these packages were provided as an "early
  experience", not for serious use.

  "Client" packages are dependent only on libmirclient.so.9 which is ABI
  stable. The principle type of regression would be FTBFS where APIs
  have been deprecated in 0.26. The linked 0.26.3 release has these
  deprecations disabled for 16.04.

  The packages are available in silo:
  https://bileto.ubuntu.com/#/ticket/2736

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

  Anyone wanting these packages should switch to the "unity8-desktop-
  session" preview package in 17.04 where they are far more functional.

  [Alternatives]
  If we want to keep everything working in Xenial, we *could* bump the 
libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 
being NBS, but continuing to work against the Mir servers available in 16.04[*] 
(until and unless they are rebuilt).

  However, this does not enable the desired result for IoT deployments
  of toolkits (GTK, Qt etc) and other clients working against servers
  (specifically miral-kiosk) built against the updated libraries.

  To work for IoT these would need to rebuilt from source - at which
  point they (and their dependencies) would stop working against the
  servers in category 1.

  [*] with the exception of the servers provided in mir-examples, these
  would only work with clients linking against libmirclient.so.10.

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

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

[Touch-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Alex Tu]

** Tags added: 1677955

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
- but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
- libmbim-glib4_1.14.0-1_amd64.deb
- libmbim-glib-dev_1.14.0-1_amd64.deb
- libmbim-proxy_1.14.0-1_amd64.deb
- libmbim-utils_1.14.0-1_amd64.deb
- libqmi-glib5_1.16.0-1_amd64.deb
- libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
 - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
- the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

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

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

[Touch-packages] [Bug 1664818] Re: Not possible to render pre-up, pre-down, post-up, or post-down snippets

[Dimitri John Ledkov]

I'm kind of concerned about any non-declarative functionality here. For
example, DHCP client and receiving/updating routes are all handled by
netwokrd already.

You can bind a systemd unit to e.g. sys-subsystem-net-devices-
eth0.device and then any number of systemd units should be started and
stopped in concert.

One can also block and wait until the relevant interface is up with
/lib/systemd/systemd-networkd-wait-online --help

However, I'd rather avoid running arbitrary code as all the examples
provided at the moment can be achieve as specifications to the networkd
units. (either as generated by netplan, or as drop-in snippets in /etc
or /run).

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

Title:
  Not possible to render pre-up, pre-down, post-up, or post-down
  snippets

Status in netplan:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Many configurations require scripts to run before or after an
  interface comes up or down.

  Example: I had a situation where I needed to render a post-up script
  to monitor an interface with ifupdown (and with the interface set to
  manual mode, because if the link was down I didn't want to require
  DHCP to run before the system continued booting). This is similar to
  what NetworkManager does in order to launch (or kill) a DHCP client.

  Other use cases involve setting up custom routes (such as when complex
  logic involving metrics or source routing is required) or anything
  else the designers of the netplan rendering engine didn't think of,
  such as invoking workarounds or special settings required for a
  particular NIC or environment, iptables rules that should be added or
  removed, etc.

  A follow-on issue is, it should be possible to ask that custom scripts
  run if the *link* is detected to come up or down. But I'll be happy if
  netplan first can simply replicate the custom-script-invoking behavior
  of ifupdown.

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

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

[Touch-packages] [Bug 1664067] Re: indicator-datetime swaps date and month around when adding year option in non-english locale

[Martijn]

** Package changed: unity (Ubuntu) => indicator-datetime (Ubuntu)

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

Title:
  indicator-datetime swaps date and month around when adding year option
  in non-english locale

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  This bug is observed in Ubuntu 16.10.

  When one changes the settings for the time indicator, sometimes the
  locale order of displaying the date is not adhered.

  Steps to reproduce:

  - Set a locale that places the date number before the month, for example 
Dutch.
  - Set the option in unity-control-center, time menu, to show the date and 
month.
  -- See that the date is correctly placed before the month
  - Now set the show year option.
  -- See that the date is now shown after the month instead. The abbreviated 
month is translated correctly though.

  
  package version: 15.10+16.10.20160820.1-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity 7.5.0+16.10.20161112-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  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: Sun Feb 12 22:39:28 2017
  DistUpgraded: 2016-10-14 17:47:08,404 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-37-generic, x86_64: installed
   nvidia-367, 367.57, 4.8.0-34-generic, x86_64: installed
   nvidia-367, 367.57, 4.8.0-37-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF116 [GeForce GTX 550 Ti] [1043:83be]
  InstallationDate: Installed on 2014-04-21 (1028 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic 
root=UUID=a5d5e69f-3e89-4d6a-9804-5ba00dafb9bd ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (121 days ago)
  dmi.bios.date: 04/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: H61DEL
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd04/25/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61DEL:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Sun Feb 12 17:32:53 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button 

[Touch-packages] [Bug 1693613] Re: Ambiance headerbar has more padding on top than on bottom

[Treviño]

Yeah, I noticed this since the first moment actually, but I wasn't able
to find a rule covering all the cases of decorations we have...

By the way I'd prefer to reduce the headerbar height by reducing the
padding of the headerbar elements, so that we can save some vertical
space.

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

Title:
  Ambiance headerbar has more padding on top than on bottom

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  If you look at the attached screenshots, Adwaita has equal padding on
  the top and bottom of the headerbar. Ambiance has more padding on top
  than on the bottom.

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

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

[Touch-packages] [Bug 1664067] [NEW] indicator-datetime swaps date and month around when adding year option in non-english locale

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This bug is observed in Ubuntu 16.10.

When one changes the settings for the time indicator, sometimes the
locale order of displaying the date is not adhered.

Steps to reproduce:

- Set a locale that places the date number before the month, for example Dutch.
- Set the option in unity-control-center, time menu, to show the date and month.
-- See that the date is correctly placed before the month
- Now set the show year option.
-- See that the date is now shown after the month instead. The abbreviated 
month is translated correctly though.


package version: 15.10+16.10.20160820.1-0ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unity 7.5.0+16.10.20161112-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
 GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
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: Sun Feb 12 22:39:28 2017
DistUpgraded: 2016-10-14 17:47:08,404 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
 bbswitch, 0.8, 4.8.0-37-generic, x86_64: installed
 nvidia-367, 367.57, 4.8.0-34-generic, x86_64: installed
 nvidia-367, 367.57, 4.8.0-37-generic, x86_64: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF116 [GeForce GTX 550 Ti] [1043:83be]
InstallationDate: Installed on 2014-04-21 (1028 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic 
root=UUID=a5d5e69f-3e89-4d6a-9804-5ba00dafb9bd ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (121 days ago)
dmi.bios.date: 04/25/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: H61DEL
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd04/25/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61DEL:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Sun Feb 12 17:32:53 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputHoltek USB Gaming Mouse KEYBOARD, id 8
 inputHoltek USB Gaming Mouse KEYBOARD, id 9
 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6.1

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety
-- 
indicator-datetime swaps date and month around when adding year option 

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Hassan Williamson]

I was wondering if there is anything I can to help regress the issue?
Even if it is just trying to load various different older versions?

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Daniel van Vugt]

^^^
Confirmed on an XPS 13 9350 too. And the 'Headphone Mic Boost' workaround 
works. Although like others, I find that concerning since it should in theory 
make the problem worse or make no difference.

Also confirmed the problem persists with:
 * 3-contact earphones (Sony)
 * 4-contact Apple Earpods
 * 4-contact Bose AE2 headphones (Apple-compatible cable)

All of these experience the hiss, but the Bose almost none (much harder
to notice). I think the most interesting test should be to try some
proper Android/Samsung/Nokia wired headphones/earphones  in future.

If it turns out there's nothing wrong with the physical connection then
this sounds like a kernel problem still.

kaihengfeng: I have just tested your kernel on zesty and it made no
difference. The problem remains and the same old amixer workaround is
required.

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1693756] [NEW] [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Alex Tu]

Public bug reported:

# issue:
 * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
  - but works well on on Yakkety.

# investgation:
 * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
  - libmbim-glib4_1.14.0-1_amd64.deb
  - libmbim-glib-dev_1.14.0-1_amd64.deb
  - libmbim-proxy_1.14.0-1_amd64.deb
  - libmbim-utils_1.14.0-1_amd64.deb
  - libqmi-glib5_1.16.0-1_amd64.deb
  - libqmi-proxy_1.16.0-1_amd64.deb

 * different from ModemManager --debug
   - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
 - passed case: http://paste.ubuntu.com/24664908/
 - failed case: http://paste.ubuntu.com/24664910/

# Plan:
 * let the newer version packages could also works well on Xenial.
 * find out needed patches on newer version packages.
 * packport needed patches to older version packages on Xenial.

# environment information:

 * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
  - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 4.4.0 
and yakkety kernel 4.8.0.

 * uname -r: 4.4.0-73-generic

 * lsusb -v: http://paste.ubuntu.com/24662332/

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

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
- but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
- libmbim-glib4_1.14.0-1_amd64.deb
- libmbim-glib-dev_1.14.0-1_amd64.deb
- libmbim-proxy_1.14.0-1_amd64.deb
- libmbim-utils_1.14.0-1_amd64.deb
- libqmi-glib5_1.16.0-1_amd64.deb
- libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
 - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
- the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

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

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

[Touch-packages] [Bug 1692996] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

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

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

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I tried to install the following updates:
  apport 2.20.4-0ubuntu4.1
  apport-gtk 2.20-4-0ubuntu4.1
  unattended-upgrades 0.93.1ubuntu2.2
  these upgrades failed to install and produced a system error.

  I then tried to update an application, indicator-kdeconnect which then
  produced the apport error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   indicator-kdeconnect:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   600:110:117:0:2017-05-17 16:02:54.202140415 -0400:2017-05-12 
10:15:15.548592471 -0400:/var/crash/_opt_google_chrome_chrome.1000.uploaded
   640:1000:117:8425789:2017-05-17 16:02:51.106106996 -0400:2017-05-17 
16:02:52.106106996 -0400:/var/crash/_opt_google_chrome_chrome.1000.crash
   664:1000:117:0:2017-05-17 16:02:52.110107045 -0400:2017-05-17 
16:02:52.110107045 -0400:/var/crash/_opt_google_chrome_chrome.1000.upload
   640:1000:117:7647277:2017-05-22 15:31:16.909297466 -0400:2017-05-22 
15:31:17.909297466 -0400:/var/crash/_usr_bin_compiz.1000.crash
   600:0:117:204585:2017-05-23 14:09:48.879699707 -0400:2017-05-23 
14:09:49.879699707 -0400:/var/crash/apport.0.crash
  Date: Tue May 23 14:09:49 2017
  DuplicateSignature:
   package:apport:2.20.4-0ubuntu4
   Processing triggers for bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package apport (--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 2014-11-19 (916 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (39 days ago)

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

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

[Touch-packages] [Bug 1693749] Re: package mesa-vdpau-drivers:amd64 12.0.6-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package mesa-vdpau-drivers:amd64 12.0.6-0ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in mesa package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: mesa-vdpau-drivers:amd64 12.0.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri May 19 09:40:13 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgTerminalLog:
   Preparing to unpack 
.../chromium-codecs-ffmpeg-extra_58.0.3029.110-0ubuntu0.16.04.1281_amd64.deb ...
   Unpacking chromium-codecs-ffmpeg-extra (58.0.3029.110-0ubuntu0.16.04.1281) 
over (58.0.3029.96-0ubuntu0.16.04.1279) ...
   dpkg: error processing package mesa-vdpau-drivers:amd64 (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature:
   package:mesa-vdpau-drivers:amd64:12.0.6-0ubuntu0.16.04.1
   Unpacking chromium-codecs-ffmpeg-extra (58.0.3029.110-0ubuntu0.16.04.1281) 
over (58.0.3029.96-0ubuntu0.16.04.1279) ...
   dpkg: error processing package mesa-vdpau-drivers:amd64 (--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
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:15ad]
 Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:15ad]
  InstallationDate: Installed on 2016-11-13 (194 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X751LD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=96bf48a0-5869-47ea-a52f-064db693f87f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: mesa
  Title: package mesa-vdpau-drivers:amd64 12.0.6-0ubuntu0.16.04.1 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)
  dmi.bios.date: 02/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X751LD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X751LD
  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.:bvrX751LD.302:bd02/07/2014:svnASUSTeKCOMPUTERINC.:pnX751LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X751LD
  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 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: Fri May 26 12:16:44 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.outputs:
   product id 912 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:

[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[Bernhard]

Hi,

I just upgraded from Ubuntu 16.10 to 17.04 and observed the following
systemd-resolve behaviour that might be related to this bug:

--> Any domain listed after the "search" keyword in /etc/resolv.conf
stops being resolved by systemd-resolve.

respectively

--> Any domain listed as "DNS Domain:" when querying "systemd-resolve
--status" stops being resolved by systemd-resolve

I confirmed with tcpdump that systemd-resolve will not query my local or
any dnsserver for any subdomains for any domain listed under the
"search" keyword.

Changing the domains after the search keyword in /erc/resolv.conf
immediately changes which domains systemd-resolve will ignore and not
resolve.

The search domain is normally automatically set in response to receiving
an "option domain-name" from the local dhcp server and normally used to
translate requests for www to e.g. www.localdomain.at if localdomain.at
was the domain-name sent by the DHCP server.

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

[Daniel van Vugt]

** Summary changed:

- XPS 13 9360, Realtek ALC3246, Headphone audio hiss
+ XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1693749] [NEW] package mesa-vdpau-drivers:amd64 12.0.6-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

[Ark]

Public bug reported:

-

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mesa-vdpau-drivers:amd64 12.0.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri May 19 09:40:13 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgTerminalLog:
 Preparing to unpack 
.../chromium-codecs-ffmpeg-extra_58.0.3029.110-0ubuntu0.16.04.1281_amd64.deb ...
 Unpacking chromium-codecs-ffmpeg-extra (58.0.3029.110-0ubuntu0.16.04.1281) 
over (58.0.3029.96-0ubuntu0.16.04.1279) ...
 dpkg: error processing package mesa-vdpau-drivers:amd64 (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
DuplicateSignature:
 package:mesa-vdpau-drivers:amd64:12.0.6-0ubuntu0.16.04.1
 Unpacking chromium-codecs-ffmpeg-extra (58.0.3029.110-0ubuntu0.16.04.1281) 
over (58.0.3029.96-0ubuntu0.16.04.1279) ...
 dpkg: error processing package mesa-vdpau-drivers:amd64 (--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
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller 
[1043:15ad]
   Subsystem: ASUSTeK Computer Inc. GeForce 820M [1043:15ad]
InstallationDate: Installed on 2016-11-13 (194 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUSTeK COMPUTER INC. X751LD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed 
root=UUID=96bf48a0-5869-47ea-a52f-064db693f87f ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: mesa
Title: package mesa-vdpau-drivers:amd64 12.0.6-0ubuntu0.16.04.1 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)
dmi.bios.date: 02/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X751LD.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X751LD
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.:bvrX751LD.302:bd02/07/2014:svnASUSTeKCOMPUTERINC.:pnX751LD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751LD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X751LD
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 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: Fri May 26 12:16:44 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.outputs:
 product id 912 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  package mesa-vdpau-drivers:amd64 12.0.6-0ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in mesa package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: mesa-vdpau-drivers:amd64 12.0.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 

[Touch-packages] [Bug 1693724] [NEW] Context menus have no animation/fade-in under Gnome Shell

[Daniel van Vugt]

Public bug reported:

Context menus have no animation/fade-in under Gnome Shell. The
transitions under Unity7 for context menus look nicer, less abrupt.

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

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


** Tags: artful

** Tags added: artful

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

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

Title:
  Context menus have no animation/fade-in under Gnome Shell

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

Bug description:
  Context menus have no animation/fade-in under Gnome Shell. The
  transitions under Unity7 for context menus look nicer, less abrupt.

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

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

[Touch-packages] [Bug 1173950] Re: with Ambiance, progress bar is invisible in gitg

[Adam Dingle]

This bug is obsolete: the progress bar looks fine in gitg in Zesty.
Marking invalid.

** Changed in: ubuntu-themes
   Status: Incomplete => Invalid

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  with Ambiance, progress bar is invisible in gitg

Status in Ubuntu theme:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  The very latest gitg (in git master) displays a progress bar while
  cloning a repository.  This progress bar is visible in Adwaita but
  invisible in Ambiance.

  See the upstream bug at
  https://bugzilla.gnome.org/show_bug.cgi?id=699130 .  We may need to
  merge style changes including this one into Ambiance:

  https://git.gnome.org/browse/gitg/tree/gitg/resources/ui/style.css#n89

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

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

[Touch-packages] [Bug 1628474] Re: keyboard keys in GtkShortcuts should have different color than background

[Daniel van Vugt]

Looks fixed (and quite different) in artful.

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  keyboard keys in GtkShortcuts should have different color than
  background

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Many GNOME apps have a new Keyboard Shortcuts popup window available
  in their app menu (this feature was introduced in GTK 3.20).

  Ambiance and Radiance don't style this window correctly - there's no
  contrast between the displayed keyboard keys and the background.

  I'm attaching screenshots of evince's Keyboard Shortcuts popup
  (available in Help > Keyboard Shortcuts) with Ambiance and Adwaita.

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

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

[Touch-packages] [Bug 1665338] Re: [enhancement] Re-theme GTK under Unity8 to look more like Unity8

[Daniel van Vugt]

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

** Changed in: canonical-devices-system-image
   Status: New => Won't Fix

** Tags added: ubuntu-touch

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

Title:
  [enhancement] Re-theme GTK under Unity8 to look more like Unity8

Status in Canonical System Image:
  Won't Fix
Status in Ubuntu UX:
  New
Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  gtk apps with ambiance theme look weird, out of place on unity8

  launch some gtk apps, the ambiance theme is not consistent with unity8
  "theme", diff style etc, it just looks ewww eww ew

  see attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1665338/+subscriptions

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

[Touch-packages] [Bug 1630338] Re: Bluetooth Handsfree Broken Icon in Sound System Setting

[Daniel van Vugt]

I've been using this settings dialog a lot recently and have never seen
this bug.

Please let us know what Ubuntu release you see the problem on.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Incomplete

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

Title:
  Bluetooth Handsfree Broken Icon in Sound System Setting

Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Please find  the attached screenshot

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

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