date:20170519

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

Title:
  do-release-upgrade from 12.04 failed

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Just followed the procedure until I got a failure.
  (sudo bash
  do-release-upgrade
  answered any questions received
  crashed)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-119-generic 3.13.0-119.166
  ProcVersionSignature: Ubuntu 3.2.0-63.95-generic 3.2.57
  Uname: Linux 3.2.0-63-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm2846 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Sat May 20 07:49:13 2017
  DuplicateSignature: 
package:linux-image-extra-3.13.0-119-generic:3.13.0-119.166:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=4cf7104a-4cf5-47da-b664-a906b8a2e7f5
  InstallationDate: Installed on 2012-10-01 (1691 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-63-generic 
root=UUID=8e2e6575-72d0-42b3-810e-531406a252ac ro reboot=b quiet splash 
vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.13.0-119-generic 3.13.0-119.166 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to trusty on 2017-05-20 (0 days ago)
  dmi.bios.date: 05/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.30
  dmi.board.name: 960GM-GS3 FX
  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.30:bd05/21/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM-GS3FX: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.

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

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

[Touch-packages] [Bug 1692172] [NEW] do-release-upgrade from 12.04 failed

2017-05-19 Thread Ιωάννης Χαριτάκης

Public bug reported:

Just followed the procedure until I got a failure.
(sudo bash
do-release-upgrade
answered any questions received
crashed)

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-119-generic 3.13.0-119.166
ProcVersionSignature: Ubuntu 3.2.0-63.95-generic 3.2.57
Uname: Linux 3.2.0-63-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lightdm2846 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Sat May 20 07:49:13 2017
DuplicateSignature: 
package:linux-image-extra-3.13.0-119-generic:3.13.0-119.166:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=4cf7104a-4cf5-47da-b664-a906b8a2e7f5
InstallationDate: Installed on 2012-10-01 (1691 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
IwConfig:
 lono wireless extensions.
 
 eth2  no wireless extensions.
 
 eth1  no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-63-generic 
root=UUID=8e2e6575-72d0-42b3-810e-531406a252ac ro reboot=b quiet splash 
vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-extra-3.13.0-119-generic 3.13.0-119.166 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to trusty on 2017-05-20 (0 days ago)
dmi.bios.date: 05/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: 960GM-GS3 FX
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.30:bd05/21/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM-GS3FX: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.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade trusty

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

Title:
  do-release-upgrade from 12.04 failed

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Just followed the procedure until I got a failure.
  (sudo bash
  do-release-upgrade
  answered any questions received
  crashed)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-119-generic 3.13.0-119.166
  ProcVersionSignature: Ubuntu 3.2.0-63.95-generic 3.2.57
  Uname: Linux 3.2.0-63-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm2846 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Sat May 20 07:49:13 2017
  DuplicateSignature: 
package:linux-image-extra-3.13.0-119-generic:3.13.0-119.166:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=4cf7104a-4cf5-47da-b664-a906b8a2e7f5
  InstallationDate: Installed on 2012-10-01 (1691 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  IwConfig:
   lono wireless extensions.
   
   eth2  no wireless extensions.
   
   eth1  no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-63-generic 
root=UUID=8e2e6575-72d0-42b3-810e-531406a252ac ro reboot=b quiet splash 
vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.12
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.13.0-119-generic 3.13.0-119.166 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to trusty on 2017-05-20 (0 days ago)
  dmi.bios.date: 05/21/2012

[Touch-packages] [Bug 1615209] Re: ip crashes after a few times adding and removing network namespaces

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

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

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

Title:
  ip crashes after a few times adding and removing network namespaces

Status in iproute2 package in Ubuntu:
  Expired

Bug description:
  # which ip
  /sbin/ip
  # valgrind ip netns add black2
  ==22804== Memcheck, a memory error detector
  ==22804== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
  ==22804== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
  ==22804== Command: ip netns add black2
  ==22804== 
  ==22804== Invalid write of size 1
  ==22804==at 0x4031F43: memcpy (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C83: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804==  Address 0x4227094 is 0 bytes after a block of size 28 alloc'd
  ==22804==at 0x402D17C: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==22804==by 0x8059C5E: ??? (in /bin/ip)
  ==22804==by 0x805AF9A: netns_map_init (in /bin/ip)
  ==22804==by 0x805B01F: do_netns (in /bin/ip)
  ==22804==by 0x804DF67: ??? (in /bin/ip)
  ==22804==by 0x804DA11: main (in /bin/ip)
  ==22804== 
  Cannot create namespace file "/var/run/netns/black2": File exists
  ==22804== 
  ==22804== HEAP SUMMARY:
  ==22804== in use at exit: 28 bytes in 1 blocks
  ==22804==   total heap usage: 2 allocs, 1 frees, 32,824 bytes allocated
  ==22804== 
  ==22804== LEAK SUMMARY:
  ==22804==definitely lost: 0 bytes in 0 blocks
  ==22804==indirectly lost: 0 bytes in 0 blocks
  ==22804==  possibly lost: 0 bytes in 0 blocks
  ==22804==still reachable: 28 bytes in 1 blocks
  ==22804== suppressed: 0 bytes in 0 blocks
  ==22804== Rerun with --leak-check=full to see details of leaked memory
  ==22804== 
  ==22804== For counts of detected and suppressed errors, rerun with: -v
  ==22804== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

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

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

[Touch-packages] [Bug 1674012] Re: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to install/upgrade: EOF sur l'entrée standard à l'invite de configuration

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

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

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

Title:
  package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to
  install/upgrade: EOF sur l'entrée standard à l'invite de configuration

Status in ntp package in Ubuntu:
  Expired

Bug description:
  I don't know what it is but my computer said it to me everytime.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10
  ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-68-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  AptOrdering:
   firefox-locale-en: Install
   ntpdate: Configure
   firefox-locale-en: Configure
  Architecture: amd64
  Date: Wed Mar 15 21:02:13 2017
  ErrorMessage: EOF sur l'entrée standard à l'invite de configuration
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.17
  SourcePackage: ntp
  Title: package ntpdate 1:4.2.6.p5+dfsg-3ubuntu2.14.04.10 failed to 
install/upgrade: EOF sur l'entrée standard à l'invite de configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1674058] Re: package util-linux 2.27.1-6ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** Changed in: util-linux (Ubuntu)
   Status: Incomplete => Expired

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

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

Status in util-linux package in Ubuntu:
  Expired

Bug description:
  I tried to install updates for the system upgrades. It doesn't seem to
  be installing properly.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Mar 18 23:05:35 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-05-26 (297 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.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/util-linux/+bug/1674058/+subscriptions

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

2017-05-19 Thread Nick Breen

I can confirm that in my case it was due to an error 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 1692109] Re: mount is broken/misbehaving

2017-05-19 Thread Jens Elkner

AFAICS the problem is libmount/src/context_mount.c:exec_helper() which
is uses operands in a wrong/not posixly incorrect way. See also
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html

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

Title:
  mount is broken/misbehaving

Status in util-linux package in Ubuntu:
  New

Bug description:
  "/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil 
rpool/zones/bla /zones/bla"
  fails, if env var POSIXLY_CORRECT is set, because it calls
  "/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is 
obviously a bug. Options should always come first and operands last ...

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

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

[Touch-packages] [Bug 1692145] [NEW] package bash 4.4-2ubuntu1.1 failed to install/upgrade: el paquete bash no está listo para configurarse no se puede configurar (estado actual `half-installed')

2017-05-19 Thread Pastor Benavides

Public bug reported:

Aparece mensaje de error

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: bash 4.4-2ubuntu1.1
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
Architecture: amd64
Date: Wed May 17 14:55:23 2017
DpkgTerminalLog:
 [1mdpkg:[0m error al procesar el paquete bash (--configure):
  el paquete bash no está listo para configurarse
  no se puede configurar (estado actual `half-installed')
ErrorMessage: el paquete bash no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
InstallationDate: Installed on 2016-06-26 (327 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: bash
Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: el paquete bash 
no está listo para configurarse  no se puede configurar (estado actual 
`half-installed')
UpgradeStatus: Upgraded to zesty on 2017-04-24 (25 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package bash 4.4-2ubuntu1.1 failed to install/upgrade: el paquete bash
  no está listo para configurarse  no se puede configurar (estado actual
  `half-installed')

Status in bash package in Ubuntu:
  New

Bug description:
  Aparece mensaje de error

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bash 4.4-2ubuntu1.1
  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
  Architecture: amd64
  Date: Wed May 17 14:55:23 2017
  DpkgTerminalLog:
   [1mdpkg:[0m error al procesar el paquete bash (--configure):
el paquete bash no está listo para configurarse
no se puede configurar (estado actual `half-installed')
  ErrorMessage: el paquete bash no está listo para configurarse  no se puede 
configurar (estado actual `half-installed')
  InstallationDate: Installed on 2016-06-26 (327 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: el paquete bash 
no está listo para configurarse  no se puede configurar (estado actual 
`half-installed')
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (25 days ago)

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

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

[Touch-packages] [Bug 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".

2017-05-19 Thread Dimitri John Ledkov

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

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

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

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

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

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

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

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

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

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

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Yakkety)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Zesty)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  Backport "core/timer: downgrade message about random time addition
  (#5229)".

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

Bug description:
  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade
  message about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

  This removes "random time" messages flooding dmesg.

  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

  trusty based off v204 is not affected.

  xenial based off v229, yakkety based off v231, and zesty based off
  v232 need this fix.

  artful based off v233 has the fix.

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

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

[Touch-packages] [Bug 1692139] [NEW] package resolvconf 1.78ubuntu2 failed to install/upgrade: pacote resolvconf não está pronto para configuração não posso configurar (estado atual 'half-installed')

2017-05-19 Thread Gustavo Marques

Public bug reported:

I was trying to install wine in terminal, and other programs, but all
return that message. :/

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri May 19 20:32:26 2017
ErrorMessage: pacote resolvconf não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
InstallationDate: Installed on 2017-05-17 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: resolvconf
Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: pacote 
resolvconf não está pronto para configuração  não posso configurar (estado 
atual 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package resolvconf 1.78ubuntu2 failed to install/upgrade: pacote
  resolvconf não está pronto para configuração  não posso configurar
  (estado atual 'half-installed')

Status in resolvconf package in Ubuntu:
  New

Bug description:
  I was trying to install wine in terminal, and other programs, but all
  return that message. :/

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Fri May 19 20:32:26 2017
  ErrorMessage: pacote resolvconf não está pronto para configuração  não posso 
configurar (estado atual 'half-installed')
  InstallationDate: Installed on 2017-05-17 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: resolvconf
  Title: package resolvconf 1.78ubuntu2 failed to install/upgrade: pacote 
resolvconf não está pronto para configuração  não posso configurar (estado 
atual 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692127] Re: duplicate signature for Package problems can be too short

2017-05-19 Thread Steve Langasek

When each of these messages are output by dpkg, they also match the
pattern '\.\.\.[[:space:]]*$'.  So perhaps that should be included as
part of the filter?

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

Title:
  duplicate signature for Package problems can be too short

Status in apport package in Ubuntu:
  New
Status in apport source package in Artful:
  New

Bug description:
  Steve brought up bug 1691983 and how it's duplicate signature is
  missing information.  It contains:

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

  But is missing:

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

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

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

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

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

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

[Touch-packages] [Bug 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".

2017-05-19 Thread Bug Watch Updater

** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  Backport "core/timer: downgrade message about random time addition
  (#5229)".

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  New

Bug description:
  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade
  message about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

  This removes "random time" messages flooding dmesg.

  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

  trusty based off v204 is not affected.

  xenial based off v229, yakkety based off v231, and zesty based off
  v232 need this fix.

  artful based off v233 has the fix.

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

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

[Touch-packages] [Bug 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".

2017-05-19 Thread Vinson Lee

** Bug watch added: github.com/systemd/systemd/issues #5228
   https://github.com/systemd/systemd/issues/5228

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/5228
   Importance: Unknown
   Status: Unknown

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

Title:
  Backport "core/timer: downgrade message about random time addition
  (#5229)".

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade
  message about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

  This removes "random time" messages flooding dmesg.

  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

  trusty based off v204 is not affected.

  xenial based off v229, yakkety based off v231, and zesty based off
  v232 need this fix.

  artful based off v233 has the fix.

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

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

[Touch-packages] [Bug 1692136] [NEW] Backport "core/timer: downgrade message about random time addition (#5229)".

2017-05-19 Thread Vinson Lee

Public bug reported:

Please backport upstream systemd v233 commit
382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade message
about random time addition (#5229)".
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

This removes "random time" messages flooding dmesg.

The spew was introduced with v229 commit "core: add new RandomSec=
setting for time units".
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

trusty based off v204 is not affected.

xenial based off v229, yakkety based off v231, and zesty based off v232
need this fix.

artful based off v233 has the fix.

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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


** Tags: xenial yakkety 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/1692136

Title:
  Backport "core/timer: downgrade message about random time addition
  (#5229)".

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade
  message about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

  This removes "random time" messages flooding dmesg.

  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

  trusty based off v204 is not affected.

  xenial based off v229, yakkety based off v231, and zesty based off
  v232 need this fix.

  artful based off v233 has the fix.

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

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

[Touch-packages] [Bug 1692127] Re: duplicate signature for Package problems can be too short

We could continue if the line equals "Installing for x86_64-efi
platform." but that would only work for shim-signed and seems fragile.

** Also affects: apport (Ubuntu Artful)
   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/1692127

Title:
  duplicate signature for Package problems can be too short

Status in apport package in Ubuntu:
  New
Status in apport source package in Artful:
  New

Bug description:
  Steve brought up bug 1691983 and how it's duplicate signature is
  missing information.  It contains:

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

  But is missing:

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

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

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

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

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

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

[Touch-packages] [Bug 1692127] [NEW] duplicate signature for Package problems can be too short

Public bug reported:

Steve brought up bug 1691983 and how it's duplicate signature is missing
information.  It contains:

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

But is missing:

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

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

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

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

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

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


** Tags: artful xenial yakkety zesty

** Tags added: artful xenial yakkety 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/1692127

Title:
  duplicate signature for Package problems can be too short

Status in apport package in Ubuntu:
  New
Status in apport source package in Artful:
  New

Bug description:
  Steve brought up bug 1691983 and how it's duplicate signature is
  missing information.  It contains:

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

  But is missing:

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

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

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

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

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

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

[Touch-packages] [Bug 1690861] Re: typo of descripiton in README

** Summary changed:

- descripiton in README
+ typo of descripiton in README

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

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

Title:
  typo of descripiton in README

Status in Patch:
  Unknown
Status in patch package in Ubuntu:
  Confirmed

Bug description:
  Line 19 of /usr/share/doc/patch/README contains "descripiton".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: patch 2.7.1-4ubuntu2.3
  Uname: Linux 3.4.0+ x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Mon May 15 18:40:47 2017
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.11
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.11
  ProcEnviron: Error: [Errno 2] No such file or directory: '/proc/62/environ'
  SourcePackage: patch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1689495] Re: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' object has no attribute 'write'

** Tags added: rls-aa-incoming

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

Title:
  unattended-upgrade crashed with AttributeError in _write(): 'NoneType'
  object has no attribute 'write'

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  This happened after upgrading it to Artful.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: unattended-upgrades 0.93.1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  Date: Tue May  9 08:20:24 2017
  ExecutablePath: /usr/bin/unattended-upgrade
  InstallationDate: Installed on 2017-05-05 (3 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/unattended-upgrade -d 3
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   LANG=en_IE.UTF-8
  PythonArgs: ['/usr/bin/unattended-upgrade', '-d', '3']
  SourcePackage: unattended-upgrades
  Title: unattended-upgrade crashed with AttributeError in _write(): 'NoneType' 
object has no attribute 'write'
  UpgradeStatus: Upgraded to artful on 2017-05-05 (3 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1687981] Please test proposed package

2017-05-19 Thread Steve Langasek

Hello Timo, or anyone else affected,

Accepted libxfont2 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libxfont2/1:2.0.1-3~ubuntu16.04.1
in a few hours, and then in the -proposed repository.

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

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

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

** Package changed: libxfont1 (Ubuntu Xenial) => libxfont2 (Ubuntu
Xenial)

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

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

Title:
  Backport packages for 16.04.3 HWE stack

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

Bug description:
  [Impact]

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

  Revert changes to use debhelper10.

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

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

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

  [Test case]

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

  [Regression potential]

  zesty hasn't blown up

  [Other information]

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

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

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

[Touch-packages] [Bug 1691096] Re: mysql in lxd fails to start with systemd 233: failed at step KEYRING

** Also affects: systemd (Ubuntu Artful)
   Importance: High
   Status: New

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

Title:
  mysql in lxd fails to start with systemd 233: failed at step KEYRING

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Artful:
  New

Bug description:
  artful unprivileged container on a xenial host

  xnox hinted that
  
https://github.com/systemd/systemd/commit/b3415f5daef49642be3d5f417b8880c078420ff7
  might be related

  With systemd 233, mysql-server-5.7 in an artful lxd unprivileged
  container fails to start:

    Process: 6460 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
  (code=exited, status=237/KEYRING)

  May 16 12:20:08 artful-mysql systemd[1]: mysql.service: Failed to set 
invocation ID on control group /system.slice/mysql.service, ignoring: Operation 
not permitted
  (...)
  May 16 12:20:08 artful-mysql systemd[6460]: mysql.service: Failed at step 
KEYRING spawning /usr/share/mysql/mysql-systemd-start: Permission denied

  Reproducing it on a fresh xenial kvm as host, fresh artful lxd image. We 
start with systemd-232 in the artful lxd:
  ubuntu@intense-sunbeam:~$ apt-cache policy systemd
  systemd:
    Installed: 232-21ubuntu3
    Candidate: 233-6ubuntu1
    Version table:
   233-6ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu artful/main amd64 Packages
   *** 232-21ubuntu3 100
  100 /var/lib/dpkg/status

  Then we install mysql-server-5.7:
  ubuntu@intense-sunbeam:~$ sudo apt install mysql-server-5.7
  ...
  Setting up mysql-server-5.7 (5.7.17-0ubuntu1) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf 
(my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → 
/lib/systemd/system/mysql.service.
  Processing triggers for libc-bin (2.24-9ubuntu2) ...
  Processing triggers for systemd (232-21ubuntu3) ...

  Which starts just fine:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  ...

  We then upgrade systemd:
  ubuntu@intense-sunbeam:~$ sudo apt install systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    libpam-systemd libsystemd0
  (...)
  Setting up libpam-systemd:amd64 (233-6ubuntu1) ...

  mysql is still running:
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  Welcome to the MySQL monitor.  Commands end with ; or \g.
  (...)

  But restarting mysql fails:
  ubuntu@intense-sunbeam:~$ sudo service mysql restart
  Job for mysql.service failed because the control process exited with error 
code.
  See "systemctl  status mysql.service" and "journalctl  -xe" for details.
  ubuntu@intense-sunbeam:~$ mysql -uroot -psecret
  mysql: [Warning] Using a password on the command line interface can be 
insecure.
  ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)

  More logs attached.

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

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

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

2017-05-19 Thread Jarno Suni

** Description changed:

  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space in
  /boot temporarily. But there is no space left, if /boot is full.
  
  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.
  
  Alternatively the init script should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  
  Related question: http://askubuntu.com/q/898499/21005
+ The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools:
  New
Status in dpkg package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init script should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1426471] Re: Guideline/documentation has no layout recommendation for buttons in dialogs

2017-05-19 Thread Inayaili de León

Marking this issue as Won't Fix as these guidelines will not be
maintained anymore. Their archive has been moved to
https://docs.ubuntu.com/phone/en/

** Changed in: ubuntu-brand-guidelines
   Status: In Progress => Won't Fix

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

Title:
  Guideline/documentation has no layout recommendation for buttons in
  dialogs

Status in Ubuntu Brand Guidelines website:
  Won't Fix
Status in Ubuntu UX:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Reading the current documentation there is no real guidance on how to
  layout buttons in Dialogs.

  The "design vision" section 4. [1] mentions "Positive actions always
  go on the right, negative on the left", which suggests an horizontal
  alignment for the buttons, but the building blocks section [2] doesn't
  mention the topic and the uitk defaults to stacking things vertically,
  including the API example [3], while the uitk-gallery example program
  does show an horizontal layout by stacking its button in a row (if
  that's recommended way, the API example should perhaps reflect that?)

  Those lacks lead our applications to be inconsistant, e.g the delete
  confirmations actions in gallery or camera have there delete/don't
  button vertically stacked, is that the correct way?

  http://design.ubuntu.com/apps/getting-started/design-vision
  http://design.ubuntu.com/apps/building-blocks/dialog
  
https://developer.ubuntu.com/api/qml/sdk-14.04/Ubuntu.Components.Popups.Dialog/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-brand-guidelines/+bug/1426471/+subscriptions

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

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

2017-05-19 Thread Timo Aaltonen

xfonts-utils needs to build-depend on libxfont1-dev now that libxfont*
have been accepted

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

Title:
  Backport packages for 16.04.3 HWE stack

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

Bug description:
  [Impact]

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

  Revert changes to use debhelper10.

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

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

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

  [Test case]

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

  [Regression potential]

  zesty hasn't blown up

  [Other information]

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

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

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

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

2017-05-19 Thread Steve Langasek

Hello Timo, or anyone else affected,

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

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

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

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

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

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

Title:
  Backport packages for 16.04.3 HWE stack

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

Bug description:
  [Impact]

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

  Revert changes to use debhelper10.

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

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

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

  [Test case]

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

  [Regression potential]

  zesty hasn't blown up

  [Other information]

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

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

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

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

2017-05-19 Thread Timo Aaltonen

and test build of mtools against libxfont-dev is needed

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

Title:
  Backport packages for 16.04.3 HWE stack

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

Bug description:
  [Impact]

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

  Revert changes to use debhelper10.

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

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

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

  [Test case]

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

  [Regression potential]

  zesty hasn't blown up

  [Other information]

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

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

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

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

2017-05-19 Thread Timo Aaltonen

** Also affects: xfonts-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Backport packages for 16.04.3 HWE stack

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

Bug description:
  [Impact]

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

  Revert changes to use debhelper10.

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

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

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

  [Test case]

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

  [Regression potential]

  zesty hasn't blown up

  [Other information]

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

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

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

[Touch-packages] [Bug 1692109] Re: mount is broken/misbehaving

2017-05-19 Thread Jens Elkner

mount from util-linux 2.27.1 (libmount 2.27.0: selinux, assert, debug)
Description:Ubuntu 16.04.2 LTS

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

Title:
  mount is broken/misbehaving

Status in util-linux package in Ubuntu:
  New

Bug description:
  "/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil 
rpool/zones/bla /zones/bla"
  fails, if env var POSIXLY_CORRECT is set, because it calls
  "/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is 
obviously a bug. Options should always come first and operands last ...

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

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

[Touch-packages] [Bug 1692109] [NEW] mount is broken/misbehaving

2017-05-19 Thread Jens Elkner

Public bug reported:

"/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil 
rpool/zones/bla /zones/bla"
fails, if env var POSIXLY_CORRECT is set, because it calls
"/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is obviously 
a bug. Options should always come first and operands last ...

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  mount is broken/misbehaving

Status in util-linux package in Ubuntu:
  New

Bug description:
  "/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil 
rpool/zones/bla /zones/bla"
  fails, if env var POSIXLY_CORRECT is set, because it calls
  "/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is 
obviously a bug. Options should always come first and operands last ...

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

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

[Touch-packages] [Bug 1692066] Re: [Request] Libreswan plugin for Network Manager

2017-05-19 Thread elegos

** Description changed:

  Hello!
  
  I have the need to use Libreswan instead of strongswan to connect to an
  IPSec IKEv1 XAuth VPN in main mode without a group. Thing is strongswan
  doesn't support this configuration, so I explicitally need it.
  Nonetheless, libreswan is as developed as strongswan and it's widely
  used.
  
  using config files in /etc (ipsec.conf and .secrets) it's possible to
  correctly configure ipsec/libreswan, but needlessly to say, having the
  possibility to manage it via a GUI is 100 times better (and easier for
  "normal" users).
  
  In the current repositories (Zesty) I only found the libreswan's ipsec
  binaries (package libreswan), but not the network manager plugin
  (sources are available on github).
  
  I've tried to compile them, but I'm afraid they use a different path
  pattern than Ubuntu, so without making changes it's not possible to
  succesfully install it from sources.
  
  Thanks
+ 
+ LibreSwan NetworkManager plugin sources:
+ https://github.com/NetworkManager/network-manager-libreswan

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [Request] Libreswan plugin for Network Manager

Status in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello!

  I have the need to use Libreswan instead of strongswan to connect to
  an IPSec IKEv1 XAuth VPN in main mode without a group. Thing is
  strongswan doesn't support this configuration, so I explicitally need
  it. Nonetheless, libreswan is as developed as strongswan and it's
  widely used.

  using config files in /etc (ipsec.conf and .secrets) it's possible to
  correctly configure ipsec/libreswan, but needlessly to say, having the
  possibility to manage it via a GUI is 100 times better (and easier for
  "normal" users).

  In the current repositories (Zesty) I only found the libreswan's ipsec
  binaries (package libreswan), but not the network manager plugin
  (sources are available on github).

  I've tried to compile them, but I'm afraid they use a different path
  pattern than Ubuntu, so without making changes it's not possible to
  succesfully install it from sources.

  Thanks

  LibreSwan NetworkManager plugin sources:
  https://github.com/NetworkManager/network-manager-libreswan

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

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

[Touch-packages] [Bug 1692100] [NEW] Xorg crash

2017-05-19 Thread johnny lee

Public bug reported:

every time i login, cpu runs at 100% because of many apport-gtk
processes

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.6.4-040604-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri May 19 15:00:39 2017
InstallationDate: Installed on 2015-03-01 (810 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to xenial on 2016-07-22 (301 days ago)

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


** Tags: amd64 apport-bug crash xenial

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  every time i login, cpu runs at 100% because of many apport-gtk
  processes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.6.4-040604-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 19 15:00:39 2017
  InstallationDate: Installed on 2015-03-01 (810 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to xenial on 2016-07-22 (301 days ago)

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

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

[Touch-packages] [Bug 1692098] [NEW] ERROR path: usr/bin/compiz

2017-05-19 Thread Ralph Gilbert

Public bug reported:

package: compiz-core 1:0.9.13.1+17.04.20170109-0ubuntu1
problem type: crash
Title: compiz crashed with SIGABRT
...

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
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:Unity7
Date: Fri May 19 12:41:48 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company RS480M [Mobility Radeon Xpress 200] 
[103c:3085]
InstallationDate: Installed on 2016-08-17 (275 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
Lsusb:
 Protocol spec without prior Class and Subclass spec at line 13605
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 15ca:00c3 Textech International Ltd. Mini Optical Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Presario R4000 (PN495AV)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=f8380f61-e531-4d20-86e8-0e76c6c99841 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1C
dmi.board.name: 3085
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 42.3B
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1C:bd08/24/2006:svnHewlett-Packard:pnPresarioR4000(PN495AV):pvrF.1C:rvnHewlett-Packard:rn3085:rvr42.3B:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Presario R4000 (PN495AV)
dmi.product.version: F.1C
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.6-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.6-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Fri May 19 11:19:02 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: radeon

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu zesty

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

Title:
  ERROR path: usr/bin/compiz

Status in xorg package in Ubuntu:
  New

Bug description:
  package: compiz-core 1:0.9.13.1+17.04.20170109-0ubuntu1
  problem type: crash
  Title: compiz crashed with SIGABRT
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  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:Unity7
  Date: Fri May 19 12:41:48 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS480M [Mobility Radeon Xpress 200] 
[103c:3085]
  InstallationDate: Installed on 2016-08-17 (275 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lsusb:
   Protocol spec without prior Class and Subclass spec at line 13605
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device

[Touch-packages] [Bug 1691848] Re: Python not compiled with -fexceptions in ppc64le

2017-05-19 Thread Bruno Rosa

** Description changed:

  Pytorch (https://github.com/pytorch/pytorch) is an application that is
  written in python, C and C++. There's high interoperalibity between code
  written in these languages therex.
  
  The issue is that there are cases when an exception is thrown by C++
  code that subsequentely calls some C code before being caught.
  
  In ppc64le builds, without the -fexceptions gcc flag, such exceptions
  are not caught when the execution returns to C++ code from C code. This
  makes some Pytorch tests fail.
  
  Compiling CPython with -fexceptions seems to solve this issue.
  
+ This was also reported to Debian: https://bugs.debian.org/cgi-
+ bin/bugreport.cgi?bug=862925
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: python2.7 2.7.13-2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: ppc64el
  Date: Thu May 18 15:35:54 2017
  InstallationDate: Installed on 2015-11-05 (560 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release ppc64el 
(20150422)
  JournalErrors:
-  Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
-Users in the 'systemd-journal' group can see all messages. Pass -q to
-turn off this notice.
-  No journal files were opened due to insufficient permissions.
+  Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
+    Users in the 'systemd-journal' group can see all messages. Pass -q to
+    turn off this notice.
+  No journal files were opened due to insufficient permissions.
  ProcLoadAvg: 0.07 0.33 0.43 1/348 20166
  ProcSwaps: Filename   TypeSizeUsed
Priority
  ProcVersion: Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) (gcc 
version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 
17:03:05 UTC 2017
  SourcePackage: python2.7
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (30 days ago)
  cpu_cores: Number of cores present = 2
  cpu_coreson: Number of cores online = 2
  cpu_smt: SMT=8

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

Title:
  Python not compiled with -fexceptions in ppc64le

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Pytorch (https://github.com/pytorch/pytorch) is an application that is
  written in python, C and C++. There's high interoperalibity between
  code written in these languages therex.

  The issue is that there are cases when an exception is thrown by C++
  code that subsequentely calls some C code before being caught.

  In ppc64le builds, without the -fexceptions gcc flag, such exceptions
  are not caught when the execution returns to C++ code from C code.
  This makes some Pytorch tests fail.

  Compiling CPython with -fexceptions seems to solve this issue.

  This was also reported to Debian: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=862925

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: python2.7 2.7.13-2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic ppc64le
  .var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: ppc64el
  Date: Thu May 18 15:35:54 2017
  InstallationDate: Installed on 2015-11-05 (560 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release ppc64el 
(20150422)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
     Users in the 'systemd-journal' group can see all messages. Pass -q to
     turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcLoadAvg: 0.07 0.33 0.43 1/348 20166
  ProcSwaps: Filename   TypeSizeUsed
Priority
  ProcVersion: Linux version 4.10.0-19-generic (buildd@bos01-ppc64el-009) (gcc 
version 6.3.0 20170321 (Ubuntu 6.3.0-10ubuntu1) ) #21-Ubuntu SMP Thu Apr 6 
17:03:05 UTC 2017
  SourcePackage: python2.7
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (30 days ago)
  cpu_cores: Number of cores present = 2
  cpu_coreson: Number of cores online = 2
  cpu_smt: SMT=8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1691848/+subscriptions

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

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

2017-05-19 Thread themusicgod1

( It's not marked on this ticket/updating the status on launchpad but
the freedesktop.org ticket merged a fix yesterday, those affected may
want to pull that fix )

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

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

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Appears randomly.

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

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

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

[Touch-packages] [Bug 1691092] Re: outdated timezone information for Mongolia

2017-05-19 Thread Hans Joachim Desserud

** Tags added: artful trusty xenial yakkety zesty

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

Title:
  outdated timezone information for Mongolia

Status in tzdata package in Ubuntu:
  Confirmed

Bug description:
  Mongolia stopped following DST this year. The timezone information in
  Ubuntu 16.04.2 LTS is outdated:

  $ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M
  21:15

  The correct output is '20:15'.

  This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is
  using 2016j. I guess the previous LTS versions are also affected.

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

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

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

*** 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
   package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

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:
  I was installing atom code editor on ubuntu 17.04 gnome 3.24 when it
  stuck installation on 51% and gave me this error

  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
  Architecture: amd64
  Date: Sat May 20 00:03:01 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 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/1692083/+subscriptions

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

[Touch-packages] [Bug 1692082] [NEW] bug

2017-05-19 Thread Agustin

Public bug reported:

after instaler and using disk analizer

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri May 19 15:30:30 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.40, 4.8.0-36-generic, x86_64: installed
 virtualbox, 5.0.40, 4.8.0-52-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:81db]
InstallationDate: Installed on 2017-05-19 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 04f2:b56c Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP 240 G5 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-52-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.17
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81DB
dmi.board.vendor: HP
dmi.board.version: KBC Version 68.14
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.17:bd09/01/2016:svnHP:pnHP240G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81DB:rvrKBCVersion68.14:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP 240 G5 Notebook PC
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  bug

Status in xorg package in Ubuntu:
  New

Bug description:
  after instaler and using disk analizer

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri May 19 15:30:30 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.8.0-36-generic, x86_64: installed
   virtualbox, 5.0.40, 4.8.0-52-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:81db]
  InstallationDate: Installed on 2017-05-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 04f2:b56c Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 240 G5 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-52-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.17
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81DB
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 68.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.17:bd09/01/2016:svnHP:pnHP240G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81DB:rvrKBCVersion68.14:cvnHP:ct10:cvrChassisVersion:

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

2017-05-19 Thread Meet Divecha

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

Public bug reported:

I was installing atom code editor on ubuntu 17.04 gnome 3.24 when it
stuck installation on 51% and gave me this error

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
Architecture: amd64
Date: Sat May 20 00:03:01 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-19 (0 days ago)
InstallationMedia: Ubuntu-GNOME 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/1692083

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:
  I was installing atom code editor on ubuntu 17.04 gnome 3.24 when it
  stuck installation on 51% and gave me this error

  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
  Architecture: amd64
  Date: Sat May 20 00:03:01 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 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/1692083/+subscriptions

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

[Touch-packages] [Bug 1692055] Re: Printer not printing even though it is installed but printing in my windows system

2017-05-19 Thread Till Kamppeter

Were you able to print on an earlier Linux version?

Please follow the instructions in the sections "USB printer" and "CUPS
error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems

Thanks.

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

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

Title:
  Printer not printing even though it is installed but printing in my
  windows system

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Printer not printing even though it is installed but printer is
  printing in my windows system

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 3.13.0-36.63+hwe3-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 19 21:27:17 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-06-09 (710 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A2A3MD8h
  MachineType: Dell Inc. Latitude 3450
  PpdFiles: Canon-LBP2900: Canon LBP-3360 - CUPS+Gutenprint v5.2.10-pre2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=f8fb5d2a-2608-412d-bd82-e59860e815c2 ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PW7C8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd04/15/2015:svnDellInc.:pnLatitude3450:pvr01:rvnDellInc.:rn0PW7C8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1691092] Re: outdated timezone information for Mongolia

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

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

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

Title:
  outdated timezone information for Mongolia

Status in tzdata package in Ubuntu:
  Confirmed

Bug description:
  Mongolia stopped following DST this year. The timezone information in
  Ubuntu 16.04.2 LTS is outdated:

  $ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M
  21:15

  The correct output is '20:15'.

  This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is
  using 2016j. I guess the previous LTS versions are also affected.

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

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

[Touch-packages] [Bug 1691909] Re: Mongolia no longer observes DST

2017-05-19 Thread Pablo Palomero

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

** This bug has been marked a duplicate of bug 1691092
   outdated timezone information for Mongolia

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

Title:
  Mongolia no longer observes DST

Status in tzdata package in Ubuntu:
  New

Bug description:
  More Info here:
  http://mm.icann.org/pipermail/tz/2017-February/024811.html

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

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

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2017-05-19 Thread Ubuntu Foundations Team Bug Bot

The attachment "pulse.patch" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues 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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1152137

Title:
  Pulseaudio won't start when home directory not owned by user

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have an NFS mounted home directory on a dedicated fileserver which is
  shared with Windows PCs via SMB.

  The home directory is not owned by me.  ACLs are set on it to allow me 
  full control of the contents but prevent me from changing its permissions.
  This means any files or directories created in the home directory are owned
  by me even though the top level is not.

  Pulseaudio checks the home directory is owned by the user at startup and
  exits if it isn't.  This stops it running on my system.

  I have recompiled pulseaudio without this check and it works fine.

  Please either remove or modify the following startup check:

  pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415:

  if (st.st_uid != getuid()) {
  pa_log_error("Home directory %s not ours.", h);
  errno = EACCES;
  goto finish;
  }

  A better check would be for pulseaudio to try and create the files/folders it
  needs and fail if it cannot.

  I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2.

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

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

[Touch-packages] [Bug 1463332] Re: zeitgeist-datahub.vala:229: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!

2017-05-19 Thread Antonios Hadjigeorgalis

I tried deleting the directory ~/.local/share/zeitgeist/fts.index/ and
the error still shows up on 16.04.2

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

Title:
   zeitgeist-datahub.vala:229: Unable to get name
  "org.gnome.zeitgeist.datahub" on the bus!

Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  get that error logged into journalctl:

  org.gnome.zeitgeist.Engine[1675]: ** (zeitgeist-datahub:2083): WARNING
  **: zeitgeist-datahub.vala:229: Unable to get name
  "org.gnome.zeitgeist.datahub" on the bus!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: zeitgeist-datahub 0.9.14-2.2ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Jun  9 11:32:35 2015
  SourcePackage: zeitgeist
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692055] [NEW] Printer not printing even though it is installed but printing in my windows system

2017-05-19 Thread BIRAJA PRASAD NAYAK

Public bug reported:

Printer not printing even though it is installed but printer is printing
in my windows system

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.8
ProcVersionSignature: Ubuntu 3.13.0-36.63+hwe3-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CurrentDesktop: Unity
Date: Fri May 19 21:27:17 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2015-06-09 (710 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A2A3MD8h
MachineType: Dell Inc. Latitude 3450
PpdFiles: Canon-LBP2900: Canon LBP-3360 - CUPS+Gutenprint v5.2.10-pre2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=f8fb5d2a-2608-412d-bd82-e59860e815c2 ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0PW7C8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd04/15/2015:svnDellInc.:pnLatitude3450:pvr01:rvnDellInc.:rn0PW7C8:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude 3450
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  Printer not printing even though it is installed but printing in my
  windows system

Status in cups package in Ubuntu:
  New

Bug description:
  Printer not printing even though it is installed but printer is
  printing in my windows system

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 3.13.0-36.63+hwe3-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 19 21:27:17 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2015-06-09 (710 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A2A3MD8h
  MachineType: Dell Inc. Latitude 3450
  PpdFiles: Canon-LBP2900: Canon LBP-3360 - CUPS+Gutenprint v5.2.10-pre2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=f8fb5d2a-2608-412d-bd82-e59860e815c2 ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0PW7C8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd04/15/2015:svnDellInc.:pnLatitude3450:pvr01:rvnDellInc.:rn0PW7C8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1691847] Re: * broken

This looks like it may still be an issue in the pam from artful
(1.1.8-3.2ubuntu3). Would you mind taking this to the upstream pam
developers?

** Tags added: xenial

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

Title:
  *broken

Status in pam package in Ubuntu:
  New

Bug description:
  I identified a bug in the pam_limits.c source code for Ubuntu
  16.04LTS, as follows:

  It appears that I managed to modify/"fix" the '*' unlimited memlock
  error in pam_limits.c.

  After compiling and running the modified code with the
  /etc/security/limits.conf line of '*   -memlock  unlimited', I am
  getting my user limits setting as 'ulimit -l unlimited'.

  After studying the code more carefully, I found that the C function,
  parse _config_file was first gathering the domain entry for the
  user/group/everyone in an sscanf function.  Using the domain result, a
  second function was called from within a loop, parse_uid_range.  A
  range_type value, an integer reflecting the set range of users was to
  be returned to the parse_config_file function.  However, in the case
  of '*' (Kleene star), no range_type was ever returned.  Further down
  in parse_config_file, the range_type was checked for a
  LIMIT_RANGE_NONE value and '*' (the Kleene star).  Because range_type
  did not hold the LIMIT_RANGE_NONE value, the process_limit function
  call was never made for '*' and instead a line break occurred that by-
  passed the execution of putting in universal limits.

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

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

[Touch-packages] [Bug 1691695] Re: package bash 4.3-14ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2017-05-19 Thread Tyler Hicks

** Information type changed from Private Security to Public

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

Title:
  package bash 4.3-14ubuntu1.2 failed to install/upgrade: package is in
  a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in bash package in Ubuntu:
  New

Bug description:
  the problem appeared when i tried to install the latest updates.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu May 18 11:35:37 2017
  DpkgTerminalLog:
   dpkg: error processing package bash (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-10-17 (212 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: bash
  Title: package bash 4.3-14ubuntu1.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/bash/+bug/1691695/+subscriptions

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

[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates

The description of the bug contains the following:

$ apt-cache policy unattended-upgrades
unattended-upgrades:
  Installed: 0.90
  Candidate: 0.90ubuntu0.5

Additionally, we can see in the unattended-upgrades.log file that
unattended-upgrades will be upgraded.  Please run the test again with
unattended-upgrades version 0.90ubuntu0.5 on a xenial system. My testing
has indicated that there may have been an issue with installing updates
and shutting down but this should be resolved with the version of the
package in -updates.

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

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

[Touch-packages] [Bug 1691826] Re: systemd script for sshd allows it to start too early should wait for authentication services...

2017-05-19 Thread Jonathan Gutow

I recreated the sshd account locally on the machine and it now starts
the sshd daemon correctly using the default ssh.service file. I am
withdrawing this bug report. If I see the sshd account disappear again,
I will open another bug report on that.

** No longer affects: cloud-init (Ubuntu)

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

Title:
  systemd script for sshd allows it to start too early should wait for
  authentication services...

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  After the most recent update to 16.04 I found that sshd failed to
  launch on bootup. On my particular system this is because it was not
  able to authenticate the user 'sshd'. It appears to be because it is
  starting before authentication services are completely available on my
  system. A simple fix was to make the following change to
  /lib/systemd/system/ssh.service:

  --After=network.target auditd.service
  ++After=network.target auditd.service accounts-daemon.service

  Starting too early might be a security issue, but I do not have the
  expertise to make that judgment. This may also be related to and solve
  this bug #1024475 as I am also serving some of my accounts from ldap.

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

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

[Touch-packages] [Bug 1691826] Re: systemd script for sshd allows it to start too early should wait for authentication services...

2017-05-19 Thread Colin Watson

Right, sshd really must be a local user, so if it's currently in LDAP
then that would indeed be the problem.

I don't think this is a bug in openssh, so I'm marking this Invalid for
now, but feel free to reopen if new information arises.

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

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

Title:
  systemd script for sshd allows it to start too early should wait for
  authentication services...

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  After the most recent update to 16.04 I found that sshd failed to
  launch on bootup. On my particular system this is because it was not
  able to authenticate the user 'sshd'. It appears to be because it is
  starting before authentication services are completely available on my
  system. A simple fix was to make the following change to
  /lib/systemd/system/ssh.service:

  --After=network.target auditd.service
  ++After=network.target auditd.service accounts-daemon.service

  Starting too early might be a security issue, but I do not have the
  expertise to make that judgment. This may also be related to and solve
  this bug #1024475 as I am also serving some of my accounts from ldap.

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

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

[Touch-packages] [Bug 1692036] [NEW] Xorg crash after HWE update on Ubuntu 16.04 LTS

2017-05-19 Thread Str3tLeer

Public bug reported:

Seems to be related to Bug #1509622

I installed HWE kernel on Ubuntu 16.04 LTS laptop and now it crashes
after every reboot and it fails to send crash report to Ubuntu.

Hopefully this info will help you troubleshoot the issue.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
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 22:30:10 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.40, 4.4.0-78-generic, x86_64: installed
 virtualbox, 5.0.40, 4.8.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer 3rd Gen Core processor Graphics Controller 
[1558:2702]
MachineType: System76, Inc. Gazelle Professional
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=f6494394-e52a-4bfd-89e7-d5d1450baa8f ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: Gazelle Professional
dmi.board.vendor: System76, Inc.
dmi.board.version: gazp7
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/16/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp7:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp7:cvnNoEnclosure:ct9:cvrN/A:
dmi.product.name: Gazelle Professional
dmi.product.version: gazp7
dmi.sys.vendor: System76, Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri May 19 22:08:35 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  Xorg crash after HWE update on Ubuntu 16.04 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  Seems to be related to Bug #1509622

  I installed HWE kernel on Ubuntu 16.04 LTS laptop and now it crashes
  after every reboot and it fails to send crash report to Ubuntu.

  Hopefully this info will help you troubleshoot the issue.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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 22:30:10 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-78-generic, x86_64: installed
   virtualbox, 5.0.40, 4.8.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 3rd Gen Core processor Graphics Controller 
[1558:2702]
  MachineType: System76, Inc. Gazelle Professional
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic

[Touch-packages] [Bug 1643959] Re: Unused parameter 'deterministic'

2017-05-19 Thread Kai Mast

This is still a problem in artful. Can be please fix this?

gnome-shell depends on protobuf so its kind of a pain to install two
different versions.

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

Title:
  Unused parameter 'deterministic'

Status in protobuf package in Ubuntu:
  Confirmed

Bug description:
  The current version of protbuf in the Ubuntu 16.10 Repository 
(3.0.0-7ubuntu3) includes this bug:
  https://github.com/google/protobuf/issues/2032

  "Every message generates an unused parameter warning for bool
  deterministic in ::google::protobuf::uint8*
  ::InternalSerializeWithCachedSizesToArray( bool
  deterministic, ::google::protobuf::uint8* target) const. "

  My project uses -Werror, and thus does not compile in current Ubuntu
  because of messages like this:

  NSMessage.pb.cc: In member function ‘virtual google::protobuf::uint8* 
NS_Message::InternalSerializeWithCachedSizesToArray(bool, 
google::protobuf::uint8*) const’:
  wifi/NSMessage.pb.cc:338:10: error: unused parameter ‘deterministic’ 
[-Werror=unused-parameter]
   bool deterministic, ::google::protobuf::uint8* target) const {
^
  cc1plus: all warnings being treated as errors

  I would expect code being created by protobuf does not cause any
  warnings or errors.

  This issue is fixed in protobuf's git repository with the following commit:
  
https://github.com/google/protobuf/commit/08b1c718e437041bfe0e6a28611621896e4fe904

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

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

[Touch-packages] [Bug 1591548] Re: Bug report corrupted and broken?

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

Title:
  Bug report corrupted and broken?

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I tried to search from the Ubuntu Software Center, and USC quit on its
  own, and Ubuntu asked me to report the bug. When I tried to collect
  and send the report, this is the error code I got, telling me the bug
  report was "corrupted":

  OSError('Invalid core dump: BFD: Warning: /tmp/apport_core_k0d_6whr is
  truncated: expected core file size >= 244244480, found: 133234688.',)

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

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

[Touch-packages] [Bug 1591548] Re: Bug report corrupted and broken?

2017-05-19 Thread Str3tLeer

I'm using Ubuntu 16.04 LTS and I'm seeing the same thing.

ProcCmdline
/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch

UnreportableReason:
This problem report is damaged and cannot be processed.
OSError('Invalid core dump: BFD: Warning: /tmp/apport_core_k0d5b924 is 
truncated: expected core file size >=72568832, found: 23134208.')


I started getting this only after upgrading kernel to HWE (kernel 4.8). Before 
there were no issues.

Hope this helps iron out the bug.

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

Title:
  Bug report corrupted and broken?

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I tried to search from the Ubuntu Software Center, and USC quit on its
  own, and Ubuntu asked me to report the bug. When I tried to collect
  and send the report, this is the error code I got, telling me the bug
  report was "corrupted":

  OSError('Invalid core dump: BFD: Warning: /tmp/apport_core_k0d_6whr is
  truncated: expected core file size >= 244244480, found: 133234688.',)

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

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

[Touch-packages] [Bug 1643959] Re: Unused parameter 'deterministic'

2017-05-19 Thread Kai Mast

This is still a problem in artful. Can be please fix this?

gnome-shell depends on protobuf so its kind of a pain to install two
different versions.

** Tags added: artful zesty

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

Title:
  Unused parameter 'deterministic'

Status in protobuf package in Ubuntu:
  Confirmed

Bug description:
  The current version of protbuf in the Ubuntu 16.10 Repository 
(3.0.0-7ubuntu3) includes this bug:
  https://github.com/google/protobuf/issues/2032

  "Every message generates an unused parameter warning for bool
  deterministic in ::google::protobuf::uint8*
  ::InternalSerializeWithCachedSizesToArray( bool
  deterministic, ::google::protobuf::uint8* target) const. "

  My project uses -Werror, and thus does not compile in current Ubuntu
  because of messages like this:

  NSMessage.pb.cc: In member function ‘virtual google::protobuf::uint8* 
NS_Message::InternalSerializeWithCachedSizesToArray(bool, 
google::protobuf::uint8*) const’:
  wifi/NSMessage.pb.cc:338:10: error: unused parameter ‘deterministic’ 
[-Werror=unused-parameter]
   bool deterministic, ::google::protobuf::uint8* target) const {
^
  cc1plus: all warnings being treated as errors

  I would expect code being created by protobuf does not cause any
  warnings or errors.

  This issue is fixed in protobuf's git repository with the following commit:
  
https://github.com/google/protobuf/commit/08b1c718e437041bfe0e6a28611621896e4fe904

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

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

[Touch-packages] [Bug 1643959] Re: Unused parameter 'deterministic'

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

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

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

Title:
  Unused parameter 'deterministic'

Status in protobuf package in Ubuntu:
  Confirmed

Bug description:
  The current version of protbuf in the Ubuntu 16.10 Repository 
(3.0.0-7ubuntu3) includes this bug:
  https://github.com/google/protobuf/issues/2032

  "Every message generates an unused parameter warning for bool
  deterministic in ::google::protobuf::uint8*
  ::InternalSerializeWithCachedSizesToArray( bool
  deterministic, ::google::protobuf::uint8* target) const. "

  My project uses -Werror, and thus does not compile in current Ubuntu
  because of messages like this:

  NSMessage.pb.cc: In member function ‘virtual google::protobuf::uint8* 
NS_Message::InternalSerializeWithCachedSizesToArray(bool, 
google::protobuf::uint8*) const’:
  wifi/NSMessage.pb.cc:338:10: error: unused parameter ‘deterministic’ 
[-Werror=unused-parameter]
   bool deterministic, ::google::protobuf::uint8* target) const {
^
  cc1plus: all warnings being treated as errors

  I would expect code being created by protobuf does not cause any
  warnings or errors.

  This issue is fixed in protobuf's git repository with the following commit:
  
https://github.com/google/protobuf/commit/08b1c718e437041bfe0e6a28611621896e4fe904

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

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

2017-05-19 Thread Łukasz Zemczak

Hello Eric, or anyone else affected,

Accepted openssl into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openssl/1.0.2g-
1ubuntu4.8 in a few hours, and then in the -proposed repository.

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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

[Touch-packages] [Bug 1674399] Please test proposed package

2017-05-19 Thread Łukasz Zemczak

Hello Eric, or anyone else affected,

Accepted openssl into yakkety-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/openssl/1.0.2g-
1ubuntu9.3 in a few hours, and then in the -proposed repository.

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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

[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-05-19 Thread Łukasz Zemczak

Hello Eric, or anyone else affected,

Accepted openssl into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openssl/1.0.2g-
1ubuntu11.2 in a few hours, and then in the -proposed repository.

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

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

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

** Tags removed: verification-failed

** Tags added: verification-needed

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

[Touch-packages] [Bug 1691826] Re: systemd script for sshd allows it to start too early should wait for authentication services...

2017-05-19 Thread Jonathan Gutow

1. I did not intend to set it up as cloud-init. I assumed it got flagged
because I tagged it with systemd-boot. Sorry if that messed things up.
I'm not even sure what packages cloud-init covers. If it is not
appropriate, it should be deleted.

2. The system this resides on is part of a cluster used for quantum
computations. It is usually isolated from the networks. With minimum
luck I will have time to transfer over the nss_ldap config and the
requested logs today. However, your last question suggests what is
probably the issue. I did not intentionally move sshd to ldap, but when
this problem occurred I found that that is where it now resides. I am
quite suspicious that is the actual problem. The other nodes on my
system have a local sshd user. They are still running 14.0.4 rather than
16.04. The node I am having issues with is not used for computations, so
gets used for initial upgrade testing.

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

Title:
  systemd script for sshd allows it to start too early should wait for
  authentication services...

Status in cloud-init package in Ubuntu:
  Incomplete
Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  After the most recent update to 16.04 I found that sshd failed to
  launch on bootup. On my particular system this is because it was not
  able to authenticate the user 'sshd'. It appears to be because it is
  starting before authentication services are completely available on my
  system. A simple fix was to make the following change to
  /lib/systemd/system/ssh.service:

  --After=network.target auditd.service
  ++After=network.target auditd.service accounts-daemon.service

  Starting too early might be a security issue, but I do not have the
  expertise to make that judgment. This may also be related to and solve
  this bug #1024475 as I am also serving some of my accounts from ldap.

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

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

[Touch-packages] [Bug 1692029] Re: Ubuntu After Install apparently failed to install properly from Fan Club site package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed po

*** 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
   package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  Ubuntu After Install apparently failed to install properly from Fan
  Club site 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:
  Install hung up at 51%, then window wouldn't close. Later attempt appeared to 
install, but I still got an error report.
  Ubuntu 17.04
  New user. Just installed OS yesterday.

  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
  Architecture: amd64
  Date: Fri May 19 09:36:06 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-18 (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/1692029/+subscriptions

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

[Touch-packages] [Bug 1692029] [NEW] Ubuntu After Install apparently failed to install properly from Fan Club site package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed

2017-05-19 Thread Steve McBride

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

Public bug reported:

Install hung up at 51%, then window wouldn't close. Later attempt appeared to 
install, but I still got an error report.
Ubuntu 17.04
New user. Just installed OS yesterday.

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
Architecture: amd64
Date: Fri May 19 09:36:06 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-18 (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 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/1692029

Title:
  Ubuntu After Install apparently failed to install properly from Fan
  Club site 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:
  Install hung up at 51%, then window wouldn't close. Later attempt appeared to 
install, but I still got an error report.
  Ubuntu 17.04
  New user. Just installed OS yesterday.

  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
  Architecture: amd64
  Date: Fri May 19 09:36:06 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-18 (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/1692029/+subscriptions

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

[Touch-packages] [Bug 1692024] [NEW] package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libjasper.so.1.0.0 usr/share/doc/libjasper1/changelog.Debian.gz] failed to

2017-05-19 Thread Frank Ernst

Public bug reported:

License has already been accepted.
Entpacken von virtualbox-ext-pack (5.0.40-0ubuntu1.16.04.1) ...
dpkg: Fehler beim Bearbeiten des Paketes libjasper1:amd64 (--configure):
 Paket libjasper1:amd64 ist nicht bereit zur Konfiguration
 kann nicht konfiguriert werden (momentaner Status »half-installed«)
virtualbox-ext-pack (5.0.40-0ubuntu1.16.04.1) wird eingerichtet ...
virtualbox-ext-pack: downloading: 
http://download.virtualbox.org/virtualbox/5.0.40/Oracle_VM_VirtualBox_Extension_Pack-5.0.40.vbox-extpack
The file will be downloaded into /usr/share/virtualbox-ext-pack
License accepted.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Successfully installed "Oracle VM VirtualBox Extension Pack".
Fehler traten auf beim Bearbeiten von:
 libjasper1:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjasper1:amd64 1.900.1-debian1-2.4ubuntu1 [modified: 
usr/lib/x86_64-linux-gnu/libjasper.so.1.0.0 
usr/share/doc/libjasper1/changelog.Debian.gz]
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
AptOrdering:
 virtualbox-ext-pack: Install
 libjasper1: Configure
 virtualbox-ext-pack: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri May 19 15:01:54 2017
ErrorMessage: Paket libjasper1:amd64 ist nicht bereit zur Konfiguration  kann 
nicht konfiguriert werden (momentaner Status »half-installed«)
InstallationDate: Installed on 2017-05-18 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: jasper
Title: package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1 [modified: 
usr/lib/x86_64-linux-gnu/libjasper.so.1.0.0 
usr/share/doc/libjasper1/changelog.Debian.gz] failed to install/upgrade: Paket 
libjasper1:amd64 ist nicht bereit zur Konfiguration  kann nicht konfiguriert 
werden (momentaner Status »half-installed«)
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1 [modified:
  usr/lib/x86_64-linux-gnu/libjasper.so.1.0.0
  usr/share/doc/libjasper1/changelog.Debian.gz] failed to
  install/upgrade: Paket libjasper1:amd64 ist nicht bereit zur
  Konfiguration  kann nicht konfiguriert werden (momentaner Status
  »half-installed«)

Status in jasper package in Ubuntu:
  New

Bug description:
  License has already been accepted.
  Entpacken von virtualbox-ext-pack (5.0.40-0ubuntu1.16.04.1) ...
  dpkg: Fehler beim Bearbeiten des Paketes libjasper1:amd64 (--configure):
   Paket libjasper1:amd64 ist nicht bereit zur Konfiguration
   kann nicht konfiguriert werden (momentaner Status »half-installed«)
  virtualbox-ext-pack (5.0.40-0ubuntu1.16.04.1) wird eingerichtet ...
  virtualbox-ext-pack: downloading: 
http://download.virtualbox.org/virtualbox/5.0.40/Oracle_VM_VirtualBox_Extension_Pack-5.0.40.vbox-extpack
  The file will be downloaded into /usr/share/virtualbox-ext-pack
  License accepted.
  0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
  Successfully installed "Oracle VM VirtualBox Extension Pack".
  Fehler traten auf beim Bearbeiten von:
   libjasper1:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjasper1:amd64 1.900.1-debian1-2.4ubuntu1 [modified: 
usr/lib/x86_64-linux-gnu/libjasper.so.1.0.0 
usr/share/doc/libjasper1/changelog.Debian.gz]
  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
  AptOrdering:
   virtualbox-ext-pack: Install
   libjasper1: Configure
   virtualbox-ext-pack: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri May 19 15:01:54 2017
  ErrorMessage: Paket libjasper1:amd64 ist nicht bereit zur Konfiguration  kann 
nicht konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2017-05-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: jasper
  Title: package libjasper1:amd64 1.900.1-debian1-2.4ubuntu1 [modified: 
usr/lib/x86_64-linux-gnu/libjasper.so.1.0.0 
usr/share/doc/libjasper1/changelog.Debian.gz] failed to install/upgrade: Paket 
libjasper1:amd64 ist nicht bereit zur Konfiguration  kann nicht konfiguriert 
werden (momentaner Status »half-installed«)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1152137] Re: Pulseaudio won't start when home directory not owned by user

2017-05-19 Thread Nick Moriarty

Hi,

This still affects both 14.04 and 16.04 (and probably affects the newer
non-LTS releases). We apply a patch downstream, which I've attached.

Regards

** Patch added: "pulse.patch"

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1152137/+attachment/4879559/+files/pulse.patch

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

Title:
Pulseaudio won't start when home directory not owned by user

Status in pulseaudio package in Ubuntu:
Incomplete

Bug description:
I have an NFS mounted home directory on a dedicated fileserver which is
shared with Windows PCs via SMB.

The home directory is not owned by me. ACLs are set on it to allow me
full control of the contents but prevent me from changing its permissions.
This means any files or directories created in the home directory are owned
by me even though the top level is not.

Pulseaudio checks the home directory is owned by the user at startup and
exits if it isn't. This stops it running on my system.

I have recompiled pulseaudio without this check and it works fine.

Please either remove or modify the following startup check:

pulseaudio-1.1/src/pulsecore/src/pulsecore/core-util.c line 1415:

if (st.st_uid != getuid()) {
pa_log_error("Home directory %s not ours.", h);
errno = EACCES;
goto finish;
}

A better check would be for pulseaudio to try and create the files/folders it
needs and fail if it cannot.

I am using Ubuntu 12.04 and pulseaudio 1:1.1-0ubuntu15.2.

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

--
Mailing list: https://launchpad.net/~touch-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] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-05-19 Thread Eric Desrochers

William, as per our IRC conversation, we have decided that you will do
the upload for this specific fix for the 4 releases.

Thanks for your collaboration.

- Eric

-- 
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 :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8

   * Note from irc discussion with apw and rbasak :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2

   * It basically allow openssl to take benefit of sha extension
  potential (mostly performance-wise) now that new AMD cpu starting  to
  have the capability.

  * The

[Touch-packages] [Bug 1691826] Re: systemd script for sshd allows it to start too early should wait for authentication services...

2017-05-19 Thread Andreas Hasenack

Can you share your nss_ldap configuration, as well as /var/log/syslog
and /var/log/auth.log? And, just to confirm, your sshd user is NOT in
ldap, right?

** Changed in: cloud-init (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  systemd script for sshd allows it to start too early should wait for
  authentication services...

Status in cloud-init package in Ubuntu:
  Incomplete
Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  After the most recent update to 16.04 I found that sshd failed to
  launch on bootup. On my particular system this is because it was not
  able to authenticate the user 'sshd'. It appears to be because it is
  starting before authentication services are completely available on my
  system. A simple fix was to make the following change to
  /lib/systemd/system/ssh.service:

  --After=network.target auditd.service
  ++After=network.target auditd.service accounts-daemon.service

  Starting too early might be a security issue, but I do not have the
  expertise to make that judgment. This may also be related to and solve
  this bug #1024475 as I am also serving some of my accounts from ldap.

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

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

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-05-19 Thread Andrei Aldea

Hey Akli, please try to run it again, should work now. Sorry for the
delay but I had to have another user report this for me to see it. In
the future please e-mail me or send an issue request on the Github repo.

Also, nice username ;)

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-05-19 Thread Eric Desrochers

Thanks William, I'll set the proposed pkg as verification-failed, and
will work on backporting the patch[1] you are suggesting and that has
been proven to fix the issue.


[1] - 
https://github.com/openssl/openssl/commit/08d09628d2c9f3ef599399d8cad021a07ab98347
 

Eric

** Tags removed: verification-done-xenial verification-done-yakkety 
verification-done-zesty
** 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 :
  
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8

   * Note from irc discussion with apw and rbasak :

[Touch-packages] [Bug 1691836] Re: lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

2017-05-19 Thread Seth Forshee

I can't retry myself (ppa kernel, apw is able to make tests run
somehow). I'll be uploading a new kernel in the near future for the
iptables thing anyway, so I'll mark this invalid.

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

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

Title:
  lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/ppc64el/l/lxc/20170517_145323_cd88a@/log.gz

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

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

[Touch-packages] [Bug 1691836] Re: lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

2017-05-19 Thread Seth Forshee

I can't retry myself (ppa kernel, apw is able to make tests run
somehow). I'll be uploading a new kernel in the near future for the
iptables thing anyway, so I'll mark this invalid.

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

Title:
  lxc 2.0.8-0ubuntu1 ADT test failure with linux 4.11.0-3.8

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-ppa/artful/ppc64el/l/lxc/20170517_145323_cd88a@/log.gz

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

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

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

2017-05-19 Thread Juhani Korhonen

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

** This bug has been marked a duplicate of bug 1688721
   package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

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

Bug description:
  problem

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 12 01:18:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-04-30 (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/1690621/+subscriptions

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

[Touch-packages] [Bug 1692001] Re: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20170503-

** Tags removed: need-duplicate-check

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

Title:
  package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade:
  trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is
  also in package vim 20170503-1

Status in vim package in Ubuntu:
  New

Bug description:
  When I update using apt update, these errors started to come.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: vim-common 2:7.4.1689-3ubuntu1.2
  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
  Date: Fri May 19 15:24:50 2017
  DuplicateSignature:
   package:vim-common:2:7.4.1689-3ubuntu1.2
   Unpacking vim-common (2:7.4.1689-3ubuntu1.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/vim-common_2%3a7.4.1689-3ubuntu1.2_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in 
package vim 20170503-1
  ErrorMessage: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', 
which is also in package vim 20170503-1
  InstallationDate: Installed on 2017-02-01 (107 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: vim
  Title: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: 
trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in 
package vim 20170503-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1692001] [NEW] package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 2017050

2017-05-19 Thread Vivek Kumar

Public bug reported:

When I update using apt update, these errors started to come.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: vim-common 2:7.4.1689-3ubuntu1.2
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
Date: Fri May 19 15:24:50 2017
DuplicateSignature:
 package:vim-common:2:7.4.1689-3ubuntu1.2
 Unpacking vim-common (2:7.4.1689-3ubuntu1.2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/vim-common_2%3a7.4.1689-3ubuntu1.2_amd64.deb (--unpack):
  trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in 
package vim 20170503-1
ErrorMessage: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which 
is also in package vim 20170503-1
InstallationDate: Installed on 2017-02-01 (107 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: vim
Title: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: 
trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in 
package vim 20170503-1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade:
  trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is
  also in package vim 20170503-1

Status in vim package in Ubuntu:
  New

Bug description:
  When I update using apt update, these errors started to come.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: vim-common 2:7.4.1689-3ubuntu1.2
  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
  Date: Fri May 19 15:24:50 2017
  DuplicateSignature:
   package:vim-common:2:7.4.1689-3ubuntu1.2
   Unpacking vim-common (2:7.4.1689-3ubuntu1.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/vim-common_2%3a7.4.1689-3ubuntu1.2_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in 
package vim 20170503-1
  ErrorMessage: trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', 
which is also in package vim 20170503-1
  InstallationDate: Installed on 2017-02-01 (107 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: vim
  Title: package vim-common 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: 
trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in 
package vim 20170503-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691996] [NEW] DNS and search domain is not pushed to systemd-resolved sometimes

2017-05-19 Thread Lastique

Public bug reported:

I have an OpenVPN connection with statically configured DNS server
address and the search domain. When this connection is established,
there is a high chance that the DNS address and the search domain are
not pushed to systemd-resolved for this connection. The problem does not
reproduce reliably, sometimes the parameters are pushed. When the
parameters are not pushed, 'systemd-resolve --status' reports no DNS
servers or DNS domain for the VPN connection, and name resolution does
not work.

This bug has been reportedly fixed upstream in NetworkManager 1.8. The
upstream bug reports are:

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

Please, update NetworkManager shipped with Ubuntu or backport the fix.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
Uname: Linux 4.10.0-16.1-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Fri May 19 13:35:42 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-05-01 (748 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
IpRoute:
 default via 192.168.1.1 dev eth0 proto static metric 100 
 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 100 
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-05-11T15:26:12.449289
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 virbr0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/2  
virbr0  a80bff56-e5d6-4fa4-b544-89cb3c389e3b  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  44a70bab-e44e-3942-8259-e96eb6f3fe5b  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----   
  
 virbr0-nic  tun   unmanaged  /org/freedesktop/NetworkManager/Devices/3  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages zesty

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

Title:
  DNS and search domain is not pushed to systemd-resolved sometimes

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have an OpenVPN connection with statically configured DNS server
  address and the search domain. When this connection is established,
  there is a high chance that the DNS address and the search domain are
  not pushed to systemd-resolved for this connection. The problem does
  not reproduce reliably, sometimes the parameters are pushed. When the
  parameters are not pushed, 'systemd-resolve --status' reports no DNS
  servers or DNS domain for the VPN connection, and name resolution does
  not work.

  This bug has been reportedly fixed upstream in NetworkManager 1.8. The
  upstream bug reports are:

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

  Please, update NetworkManager shipped with Ubuntu or backport the fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.10.0-16.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri May 19 13:35:42 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-01 (748 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.1.1 dev eth0 proto static metric 100 
   169.254.0.0/16 dev

[Touch-packages] [Bug 1458947] Re: QinHeng Electronics CH345 MIDI adapter triggers error

2017-05-19 Thread Andras Muranyi

In Xenial, the error message is still there, however the behavior has
improved and only 1 MIDI out and 1 MIDI in ports are registered.

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

Title:
  QinHeng Electronics CH345 MIDI adapter triggers error

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Cheap oriental MIDI adapter starts up with the following error, but
  works as expected.*

  E: [pulseaudio] module.c: Failed to load module "module-alsa-card"
  (argument: "device_id="1" name="usb-1a86_USB2.0-MIDI-00-USB20MIDI"
  card_name="alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI"
  namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no
  deferred_volume=yes use_ucm=yes card_properties="module-udev-
  detect.discovered=1""): initialization failed.

  The device:
  1a86:752d QinHeng Electronics CH345 MIDI adapter

  Of course i'm not sure whether this is a PA problem or an ALSA or UDEV
  bug.

  Ubuntu 14.04.2 LTS
  Pulseaudio 1:4.0-0ubuntu11.1

  *  works almost as expected: there is one physical input and one
  output, but in ALSA one input and two outputs appear.

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

** Attachment added: "core dump of xorg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4879486/+files/_usr_lib_xorg_Xorg.0.crash

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4879487/+files/Xorg.0.log

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

** Attachment added: "ubuntu-bug xorg report file"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+attachment/4879485/+files/ubuntu-bug_xorg_d05_0519.txt

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 1691991] [NEW] Xorg Segmentation fault on Hisilicon D05 board (arm64)

Public bug reported:

ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
[sudo] password for ubuntu: 

X.Org X Server 1.18.4
Release Date: 2016-07-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
Current Operating System: Linux ubuntu 4.10.0-20.22-generic #22+pearl.2-Ubuntu 
SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
Build Date: 02 November 2016  10:05:28PM
xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
pci id for fd 10: 19e5:1711, driver (null)
EGL_MESA_drm_image required.
(EE) 
(EE) Backtrace:
(EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
(EE) 
(EE) Segmentation fault at address 0xa0
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
Aborted (core dumped)
ubuntu@ubuntu:~$

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

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-05-19 Thread William Grant

Fortunately the OpenSSL test suite also fails when run during the build
on Ryzen. It turns out that the AES-NI+SHA-NI AES-CBC+SHA{1,256}
implementations are both broken, so
https://github.com/openssl/openssl/commit/08d09628d2c9f3ef599399d8cad021a07ab98347
needs to be backported too. I guess nobody's seriously used Ubuntu on
Goldmont.

I've uploaded fixed SRU test builds to
https://launchpad.net/~wgrant/+archive/ubuntu/experimental/+packages?field.name_filter=openssl,
and they all build and test successfully on i386 and amd64 on Ryzen. At
least 9.3~ppa1 even lets OpenVPN connect, with accelerated hashing. I
don't think we really need to dig up a Goldmont device from somewhere,
but if someone has one handy...

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

[Touch-packages] [Bug 1691961] Re: Ubuntu 16.04 freezes

2017-05-19 Thread inhouse-support

** Package changed: alsa-driver (Ubuntu) => ubuntu

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

Title:
  Ubuntu 16.04 freezes

Status in Ubuntu:
  New

Bug description:
  I've two machines with a
  Asus Z170M-PLUS
  Core i5 6600
  Samsung SSD 850 Pro 

  Both systems suffer from the same problem:

  Installation works fine. After having the system idling around for a while 
the system freezes or behaves strange. It looks like as if the SSD becomes 
inaccessible.
  I had cases where the whole GUI was frozen or situations where the terminal 
showed "I/O errors".

  I also tried different SSD (Samsung SSD pro with 256GB and 512GB) and
  updated the BIOS on one of the systems.

  Problem happens with stock Ubuntu 16.04 LTS install.

  Attached is a syslog from the rare cases where the system is able to
  somehow operate.

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

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

To start you could run like:
$ dpkg -S /etc/init.d/cups /etc/init.d/plymouth /etc/init.d/procps 
/etc/init.d/hwclock /etc/init.d/urandom /etc/init.d/mountdevsubfs

-- 
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 1691880] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Step 1 - are all from packages
Step 2 - from which source are those packages
Step 3 - try to rename them one by one and see what combination of packages 
needs to be installed to trigger this.

-- 
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 1691880] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it
helpful to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
explain why you believe this is a bug in Ubuntu rather than a problem
specific to your system, and then change the bug status back to New.

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

-- 
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 1691880] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Hi,
thank you for your report, from the logs I see:

insserv: warning: script 'K36cups' missing LSB tags and overrides
insserv: warning: script 'cups' missing LSB tags and overrides
insserv: There is a loop between service plymouth and procps if started
insserv:  loop involving service procps at depth 2
insserv:  loop involving service udev at depth 1
insserv: Starting cups depends on plymouth and therefore on system facility 
`$all' which can not be true!
[...]
insserv: There is a loop between service cups and hwclock if started
insserv:  loop involving service hwclock at depth 1
insserv: Starting cups depends on plymouth and therefore on system facility 
`$all' which can not be true!
insserv: There is a loop at service cups if started
[...]
insserv: There is a loop between service plymouth and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service mountdevsubfs at depth 2
insserv: Starting cups depends on plymouth and therefore on system facility 
`$all' which can not be true!
insserv: Starting cups depends on plymouth and therefore on system facility 
`$all' which can not be true!
insserv:  loop involving service checkroot at depth 4
[...]
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header


Mostly this is due to third party packages or scripts not palying nice with the 
packaged content form the archive.
You could start checking if all those files are actually from packages from the 
Ubuntu Archive - or if there are any external files involved.

-- 
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 1641919] Re: hibernation has stopped working in 16.10 Yakkety Yak

@mprotic - be careful
xserver-xorg-video-nouveau is the Xorg driver for it
While the kernel module you unload is from linux-image-extra

None of it is safe to uninstall, the former will due to dependencies take xorg 
away and the latter holds much more kernel modules.
If you have a setup without nouveau at all and want to avoid it loading you 
should follow [1].

[1]: https://wiki.debian.org/KernelModuleBlacklisting

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

Title:
  hibernation has stopped working in 16.10 Yakkety Yak

Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.10 (from 16.04) hibernation has stopped working.
  I've been using hibernation for years already without problems (with
  some initial tuning).

  I am talking about using "pm-hibernate"

  There is a workaround to make it work I've described here:
  http://askubuntu.com/a/849679/208566

  Also, there are some warnings while updating initramfs, which had not been 
present before:
  
  sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-4.8.0-27-generic
  W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
  W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915
  

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.8
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Tue Nov 15 12:19:19 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (374 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to yakkety on 2016-11-12 (3 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1691826] Re: systemd script for sshd allows it to start too early should wait for authentication services...

Hi Jonathan,
shouldn't that be an ssh bug then?

Was there any reason to flag cloud-init - maybe you used cloud-init to
set that up?

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

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

Title:
  systemd script for sshd allows it to start too early should wait for
  authentication services...

Status in cloud-init package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New

Bug description:
  After the most recent update to 16.04 I found that sshd failed to
  launch on bootup. On my particular system this is because it was not
  able to authenticate the user 'sshd'. It appears to be because it is
  starting before authentication services are completely available on my
  system. A simple fix was to make the following change to
  /lib/systemd/system/ssh.service:

  --After=network.target auditd.service
  ++After=network.target auditd.service accounts-daemon.service

  Starting too early might be a security issue, but I do not have the
  expertise to make that judgment. This may also be related to and solve
  this bug #1024475 as I am also serving some of my accounts from ldap.

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

-- 
Mailing list: https://launchpad.net/~touch-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, Realtek ALC3246, Headphone audio hiss

2017-05-19 Thread Daniel van Vugt

Comment #12 suggests the fix is already released (a kernel fix). However
that also suggests the fix was released before the bug was reported :)
So logic says that first fix didn't work(?).

Andrew: as original reporter can you please update your system and
retest?

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

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

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

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

-- 
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, 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 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-05-19 Thread William Grant

libssl1.0.0 1.0.2g-1ubuntu9.2 breaks OpenVPN (2.4.0-5ubuntu1 or
2.3.11-1ubuntu2) connections to Canonical's VPN on my Ryzen 7 1700X
desktop running Linux 4.10.0-21-generic. In UDP mode the server stops
responding during TLS negotiation, and in TCP mode the server closes the
connection at the same stage. Downgrading to ubuntu9.1 fixes it.
artful's 1.0.2g-1ubuntu12 is broken in the same way. The HMAC in use by
the VPN is SHA-1.

>From the server log:

ovpn-tcp[30227]: TCP connection established with [AF_INET]:44544
ovpn-tcp[30227]: :44544 TCP connection established with 
[AF_INET]:47753
ovpn-tcp[30227]: :44544 TLS_ERROR: BIO read tls_read_plaintext error: 
error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac
ovpn-tcp[30227]: :44544 TLS Error: TLS object -> incoming plaintext 
read error
ovpn-tcp[30227]: :44544 TLS Error: TLS handshake failed
ovpn-tcp[30227]: :44544 Fatal TLS error (check_tls_errors_co), 
restarting

The start of a client log is at http://paste.ubuntu.com/24603459/. Until
the connection is closed by the server, it differs from a successful
connection only in its keys and session IDs.

** Tags added: regression-proposed

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

[Touch-packages] [Bug 1691961] [NEW] Ubuntu 16.04 freezes

2017-05-19 Thread inhouse-support

Public bug reported:

I've two machines with a
Asus Z170M-PLUS
Core i5 6600
Samsung SSD 850 Pro

Both systems suffer from the same problem:

Installation works fine. After having the system idling around for a while the
system freezes or behaves strange. It looks like as if the SSD becomes
inaccessible.
I had cases where the whole GUI was frozen or situations where the terminal
showed "I/O errors".

I also tried different SSD (Samsung SSD pro with 256GB and 512GB) and
updated the BIOS on one of the systems.

Problem happens with stock Ubuntu 16.04 LTS install.

Attached is a syslog from the rare cases where the system is able to
somehow operate.

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

** Attachment added: "culd-test02-syslog.txt.gz"

https://bugs.launchpad.net/bugs/1691961/+attachment/4879409/+files/culd-test02-syslog.txt.gz

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

Title:
Ubuntu 16.04 freezes

Status in alsa-driver package in Ubuntu:
New

Bug description:
I've two machines with a
Asus Z170M-PLUS
Core i5 6600
Samsung SSD 850 Pro

Both systems suffer from the same problem:

Installation works fine. After having the system idling around for a while
the system freezes or behaves strange. It looks like as if the SSD becomes
inaccessible.
I had cases where the whole GUI was frozen or situations where the terminal
showed "I/O errors".

I also tried different SSD (Samsung SSD pro with 256GB and 512GB) and
updated the BIOS on one of the systems.

Problem happens with stock Ubuntu 16.04 LTS install.

Attached is a syslog from the rare cases where the system is able to
somehow operate.

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

--
Mailing list: https://launchpad.net/~touch-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, Realtek ALC3246, Headphone audio hiss

2017-05-19 Thread Kai-Heng Feng

I can't hear the hiss sound... either I am getting old or my headset is
choppy.

Can you test the latest mainline linux kernel [1] to see if it helps?

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc1/

-- 
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, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver 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 1689239] Re: Headerbar used as toolbars in unity are missing proper css classes