[Touch-packages] [Bug 1701776] [NEW] package qml-module-qtquick-controls:amd64 5.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at

[suryadev bandari]

Public bug reported:

I DONT KNOW MUCH DETAILS AS I AM NEW TO LINUX

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: qml-module-qtquick-controls:amd64 5.5.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sat Jul  1 10:47:38 2017
DpkgHistoryLog:
 Start-Date: 2017-07-01  10:47:29
 Commandline: aptdaemon role='role-install-file' sender=':1.98'
 Install: libwxgtk-media2.8-0:amd64 (2.8.12.1+dfsg2-2ubuntu2+1~webupd8~xenial0, 
automatic), python-wxgtk2.8:amd64 (2.8.12.1+dfsg2-2ubuntu2+1~webupd8~xenial0, 
automatic), libwxgtk2.8-0:amd64 (2.8.12.1+dfsg2-2ubuntu2+1~webupd8~xenial0, 
automatic), p7zip-full:amd64 (9.20.1~dfsg.1-4.2, automatic), 
libwxbase2.8-0:amd64 (2.8.12.1+dfsg2-2ubuntu2+1~webupd8~xenial0, automatic), 
curl:amd64 (7.47.0-1ubuntu2.2, automatic), python-wxversion:amd64 
(3.0.2.0+dfsg-1build1, automatic)
DuplicateSignature:
 package:qml-module-qtquick-controls:amd64:5.5.1-1ubuntu1
 Processing triggers for libc-bin (2.23-0ubuntu9) ...
 dpkg: error processing package qml-module-qtquick-controls:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-06-29 (1 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: qtquickcontrols-opensource-src
Title: package qml-module-qtquick-controls:amd64 5.5.1-1ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtquickcontrols-opensource-src (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 qtquickcontrols-
opensource-src in Ubuntu.
Matching subscriptions: touch
https://bugs.launchpad.net/bugs/1701776

Title:
  package qml-module-qtquick-controls:amd64 5.5.1-1ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

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

Bug description:
  I DONT KNOW MUCH DETAILS AS I AM NEW TO LINUX

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: qml-module-qtquick-controls:amd64 5.5.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jul  1 10:47:38 2017
  DpkgHistoryLog:
   Start-Date: 2017-07-01  10:47:29
   Commandline: aptdaemon role='role-install-file' sender=':1.98'
   Install: libwxgtk-media2.8-0:amd64 
(2.8.12.1+dfsg2-2ubuntu2+1~webupd8~xenial0, automatic), python-wxgtk2.8:amd64 
(2.8.12.1+dfsg2-2ubuntu2+1~webupd8~xenial0, automatic), libwxgtk2.8-0:amd64 
(2.8.12.1+dfsg2-2ubuntu2+1~webupd8~xenial0, automatic), p7zip-full:amd64 
(9.20.1~dfsg.1-4.2, automatic), libwxbase2.8-0:amd64 
(2.8.12.1+dfsg2-2ubuntu2+1~webupd8~xenial0, automatic), curl:amd64 
(7.47.0-1ubuntu2.2, automatic), python-wxversion:amd64 (3.0.2.0+dfsg-1build1, 
automatic)
  DuplicateSignature:
   package:qml-module-qtquick-controls:amd64:5.5.1-1ubuntu1
   Processing triggers for libc-bin (2.23-0ubuntu9) ...
   dpkg: error processing package qml-module-qtquick-controls:amd64 
(--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-29 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: qtquickcontrols-opensource-src
  Title: package qml-module-qtquick-controls:amd64 5.5.1-1ubuntu1 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/qtquickcontrols-opensource-src/+bug/1701776/+subscriptions

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

[Touch-packages] [Bug 715765] Re: Can't change kerberos password

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't change kerberos password

Status in krb5 package in Ubuntu:
  Expired

Bug description:
  $ kpasswd
  Password for u...@example.com: 
  Enter new password: 
  Enter it again: 
  Server error: Failed decrypting request

  Trying with passwd:
  $ passwd
  Ändern des Passworts für user.
  (aktuelles) UNIX-Passwort: 
  passwd: Fehler beim Ändern des Authentifizierungstoken
  passwd: password unchanged

  It is impossible to change the password. /etc/krb5.conf:
  [libdefaults]
  default_realm = EXAMPLE.COM
  dns_lookup_kdc = false
  dns_lookup_realm = false
  kdc_timesync = 1
  ccache_type = 4
  no-addresses = true
  forwardable = true
  proxiable = true

  [realms]
  EXAMPLE.COM = {
  kdc = 192.168.1.4
  admin_server = 192.168.1.4
  default_domain = example.com
  }

  [domain_realm]
  .example.com = EXAMPLE.COM
  example.com = EXAMPLE.COM

  [login]
  krb4_convert = true
  krb4_get_tickets = false

  [logging]
  default = FILE:/var/log/kerberos/krb5lib.log

  
  I'll handed a tgt login in:
  $ klist -f5
  Ticket cache: FILE:/tmp/krb5cc_2023
  Default principal: u...@example.com

  Valid starting ExpiresService principal
  02/07/11 14:49:30  02/08/11 00:49:30  krbtgt/example@example.com
  renew until 02/08/11 14:49:31, Flags: FPRIA
  02/07/11 18:28:29  02/08/11 00:49:30  host/srv.example@example.com
  renew until 02/08/11 14:49:31, Flags: FPRAT
  $

  I can call kadmin:
  $ kadmin
  Authenticating as principal user/ad...@example.com with password.
  Password for user/ad...@example.com: 
  kadmin:  

  It is no problem to change the password then.
  None of the hosts has IPv6-Addresses. There all at IPv4.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: krb5-user 1.8.1+dfsg-5ubuntu0.2
  Uname: Linux 2.6.36.3 x86_64
  Architecture: amd64
  Date: Wed Feb  9 14:24:46 2011
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.utf8
   SHELL=/bin/bash
  SourcePackage: krb5

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

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

[Touch-packages] [Bug 1701770] Status changed to Confirmed

[Joseph Salisbury]

This change was made by a bot.

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

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

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

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

Bug description:
  I restarted my laptop, after installed kodi addons, it stopped working
  as soon after

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-26-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic i686
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mini   1467 F...m pulseaudio
   /dev/snd/pcmC0D0p:   mini   1467 F...m pulseaudio
   /dev/snd/controlC0:  mini   1467 F pulseaudio
  Date: Fri Jun 30 20:34:04 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=7603218f-01d9-4f9e-90db-5728572b9933
  InstallationDate: Installed on 2017-06-16 (14 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: TOSHIBA Satellite A135
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-24-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-26-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.90
  dmi.board.name: IAKAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.90:bd01/12/2009:svnTOSHIBA:pnSatelliteA135:pvrPSAD0U-05400P:rvnTOSHIBA:rnIAKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite A135
  dmi.product.version: PSAD0U-05400P
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1701770] Re: package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Seth Arnold]

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

** Information type changed from Private Security to Public

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

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

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

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

Bug description:
  I restarted my laptop, after installed kodi addons, it stopped working
  as soon after

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-26-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic i686
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   mini   1467 F...m pulseaudio
   /dev/snd/pcmC0D0p:   mini   1467 F...m pulseaudio
   /dev/snd/controlC0:  mini   1467 F pulseaudio
  Date: Fri Jun 30 20:34:04 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=7603218f-01d9-4f9e-90db-5728572b9933
  InstallationDate: Installed on 2017-06-16 (14 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  MachineType: TOSHIBA Satellite A135
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-24-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-26-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.90
  dmi.board.name: IAKAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.90:bd01/12/2009:svnTOSHIBA:pnSatelliteA135:pvrPSAD0U-05400P:rvnTOSHIBA:rnIAKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite A135
  dmi.product.version: PSAD0U-05400P
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1385414] Re: provide systemd compatible cache loading library

[Seth Arnold]

Sigh. https://xkcd.com/386/ on myself.

The parser just checks for mtime newer than the cache, not changes.

Thanks

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

Title:
  provide systemd compatible cache loading library

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This tracks the work related to moving AppArmor to systemd in support
  of bug 1379542.

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

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

[Touch-packages] [Bug 1385414] Re: provide systemd compatible cache loading library

[Seth Arnold]

Hello intrigeri, this one is a bit involved.

As it is systemd's support for AppArmor is to issue a change_profile
call before executing a unit's executable. This requires the profile to
already be loaded, which currently means a pre-task that calls
apparmor_parser on the profile or waiting to run until after an apparmor
unit file completes loading all profiles.

The parser currently knows how to drive the cache, invalidate it if any
of the files involved in defining the profile are modified, etc. But
it'd be nice if this functionality were exposed via a library that
systemd could use so that it could compile (and cache) the policy if
needed, it could load a cached policy if one exists and isn't stale.

Since different tools own different AppArmor policies (init scripts own
/etc/apparmor.d/, snapd owns snapd policy, libvirt owns libvirt policy,
docker owns docker policy, etc) this may need some effort to determine
what we really want it to do.

I hope this helps. Thanks.

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

Title:
  provide systemd compatible cache loading library

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This tracks the work related to moving AppArmor to systemd in support
  of bug 1379542.

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

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

[Touch-packages] [Bug 1701764] Re: package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Seth Arnold]

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

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

** 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 xz-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1701764

Title:
  package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in xz-utils package in Ubuntu:
  New

Bug description:
  nao atualiza

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: liblzma5:i386 5.1.1alpha+20120614-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 22:22:24 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu9
  DuplicateSignature:
   package:liblzma5:i386:5.1.1alpha+20120614-2ubuntu2
   Setting up libc6-i386 (2.23-0ubuntu9) ...
   dpkg: error processing package liblzma5:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-03 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: xz-utils
  Title: package liblzma5:i386 5.1.1alpha+20120614-2ubuntu2 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/xz-utils/+bug/1701764/+subscriptions

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

[Touch-packages] [Bug 1701676] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione impossibile configurarlo (s

[Seth Arnold]

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

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

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione
  impossibile configurarlo (stato corrente "half-installed")

Status in openssl package in Ubuntu:
  New

Bug description:
  I get a window with this error as ubuntu boot

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 29 19:03:11 2017
  ErrorMessage: il pacchetto libssl1.0.0:amd64 non è pronto per la 
configurazione  impossibile configurarlo (stato corrente "half-installed")
  InstallationDate: Installed on 2016-07-14 (351 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione  impossibile 
configurarlo (stato corrente "half-installed")
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

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

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

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:
  This occurred when I restarted my computer after some updates.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri Jun 30 19:03:57 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-20 (10 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/1701768/+subscriptions

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

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

[Logan Rosen]

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

Public bug reported:

This occurred when I restarted my computer after some updates.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Fri Jun 30 19:03:57 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-20 (10 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/1701768

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:
  This occurred when I restarted my computer after some updates.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri Jun 30 19:03:57 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-20 (10 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/1701768/+subscriptions

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

[Touch-packages] [Bug 1701766] Re: package evolution-data-server-online-accounts 3.18.5-1ubuntu1 failed to install/upgrade: package evolution-data-server-online-accounts is not ready for configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package evolution-data-server-online-accounts 3.18.5-1ubuntu1 failed
  to install/upgrade: package evolution-data-server-online-accounts is
  not ready for configuration  cannot configure (current status 'half-
  installed')

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

Bug description:
  Occurred during upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: evolution-data-server-online-accounts 3.18.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 21:31:01 2017
  DuplicateSignature:
   package:evolution-data-server-online-accounts:3.18.5-1ubuntu1
   Setting up libc6-dev:amd64 (2.23-0ubuntu9) ...
   dpkg: error processing package evolution-data-server-online-accounts 
(--configure):
package evolution-data-server-online-accounts is not ready for configuration
  ErrorMessage: package evolution-data-server-online-accounts is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-11-27 (215 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: evolution-data-server
  Title: package evolution-data-server-online-accounts 3.18.5-1ubuntu1 failed 
to install/upgrade: package evolution-data-server-online-accounts is not ready 
for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1701766/+subscriptions

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

[Touch-packages] [Bug 1701766] [NEW] package evolution-data-server-online-accounts 3.18.5-1ubuntu1 failed to install/upgrade: package evolution-data-server-online-accounts is not ready for configurati

[Eric Paulson]

Public bug reported:

Occurred during upgrade.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: evolution-data-server-online-accounts 3.18.5-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun 30 21:31:01 2017
DuplicateSignature:
 package:evolution-data-server-online-accounts:3.18.5-1ubuntu1
 Setting up libc6-dev:amd64 (2.23-0ubuntu9) ...
 dpkg: error processing package evolution-data-server-online-accounts 
(--configure):
  package evolution-data-server-online-accounts is not ready for configuration
ErrorMessage: package evolution-data-server-online-accounts is not ready for 
configuration  cannot configure (current status 'half-installed')
InstallationDate: Installed on 2016-11-27 (215 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: evolution-data-server
Title: package evolution-data-server-online-accounts 3.18.5-1ubuntu1 failed to 
install/upgrade: package evolution-data-server-online-accounts is not ready for 
configuration  cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution-data-server (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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1701766

Title:
  package evolution-data-server-online-accounts 3.18.5-1ubuntu1 failed
  to install/upgrade: package evolution-data-server-online-accounts is
  not ready for configuration  cannot configure (current status 'half-
  installed')

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

Bug description:
  Occurred during upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: evolution-data-server-online-accounts 3.18.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 21:31:01 2017
  DuplicateSignature:
   package:evolution-data-server-online-accounts:3.18.5-1ubuntu1
   Setting up libc6-dev:amd64 (2.23-0ubuntu9) ...
   dpkg: error processing package evolution-data-server-online-accounts 
(--configure):
package evolution-data-server-online-accounts is not ready for configuration
  ErrorMessage: package evolution-data-server-online-accounts is not ready for 
configuration  cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2016-11-27 (215 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: evolution-data-server
  Title: package evolution-data-server-online-accounts 3.18.5-1ubuntu1 failed 
to install/upgrade: package evolution-data-server-online-accounts is not ready 
for configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1701766/+subscriptions

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

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

[Seth Arnold]

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

Hey Orkhan, we still haven't figured out why this is happening.

Since I haven't seen this mistake in person I'm also not sure how to fix
it. Are you willing to try some back-and-forth to try to work this out?

Try:

sudo apt-get update
sudo apt-get install --reinstall libssl1.0.0

If the first two worked, try also running:
sudo apt-get -u dist-upgrade

Can you please paste back the full output from running these commands?

Thanks

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: package libssl1.0.0:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Again.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 17:59:34 2017
  ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-03 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1701560] Re: package linux-image-4.8.0-58-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

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

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

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

Status in debconf package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-58-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 15:41:05 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-22 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-hwe
  Title: package linux-image-4.8.0-58-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1701560] Re: package linux-image-4.8.0-58-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Seth Arnold]

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

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

** Information type changed from Private Security to Public

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

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

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

Status in debconf package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-58-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 15:41:05 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-06-22 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-hwe
  Title: package linux-image-4.8.0-58-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Seth Arnold]

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

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

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: package libssl1.0.0:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Again.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 17:59:34 2017
  ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-03 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Seth Arnold]

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

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

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: пакет libssl1.0.0:amd64 не готов к настройке
  настройка невозможна (текущее состояние: «half-installed»)

Status in openssl package in Ubuntu:
  New

Bug description:
  Problem after sleep mode.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 12:09:51 2017
  ErrorMessage: пакет libssl1.0.0:amd64 не готов к настройке  настройка 
невозможна (текущее состояние: «half-installed»)
  InstallationDate: Installed on 2017-06-03 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1701493] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: Paket libssl1.0.0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (mome

[Seth Arnold]

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

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

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  Paket libssl1.0.0:i386 ist nicht bereit zur Konfiguration  kann nicht
  konfiguriert werden (momentaner Status »half-installed«)

Status in openssl package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  paul@paul-desktop:~$ apt-cache policy libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  libssl1.0.0:i386:
Installiert:   1.0.2g-1ubuntu4.6
Installationskandidat: 1.0.2g-1ubuntu4.8
Versionstabelle:
   1.0.2g-1ubuntu4.8 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
   *** 1.0.2g-1ubuntu4.6 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.0.2g-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  N: Paket 1.0.2g-1ubuntu4.6 kann nicht gefunden werden.
  N: Mittels des Musters »1.0.2g-1ubuntu4.6« konnte kein Paket gefunden werden.
  N: Mittels regulärem Ausdruck »1.0.2g-1ubuntu4.6« konnte kein Paket gefunden 
werden.

  
  I'm not able to install any update via the softwareupdater

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 29 13:44:22 2017
  ErrorMessage: Paket libssl1.0.0:i386 ist nicht bereit zur Konfiguration  kann 
nicht konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2016-10-28 (245 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
Paket libssl1.0.0:i386 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:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1701493/+subscriptions

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

[Touch-packages] [Bug 1101298] Re: More resources must be added into Chromium profile

[Ubuntu Foundations Team Bug Bot]

The attachment "apparmor.diff" 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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1101298

Title:
  More resources must be added into Chromium profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  When I install apparmor-profiles package and set Chromium AppArmor
  profile to enforce mode,  Chromium cannot detect the default browser
  and claims that it is not the default browser even though I set so.
  And I see this line in dmesg:

  ... type=1400 audit(1358526376.204:84): apparmor="DENIED"
  operation="exec" parent=6216 profile="/usr/lib/chromium-browser
  /chromium-browser//xdgsettings" name="/usr/bin/gawk" pid=6220 comm
  ="xdg-mime" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  Now, there is only /usr/bin/mawk line in Chromium apparmor profile but
  users may use a different implementation thanks to the alternatives
  system.

  In addition, my dmesg is flooded by these lines:

  ... type=1400 audit(1358527121.548:197): apparmor="DENIED"
  operation="open" parent=6072 profile="/usr/lib/chromium-browser
  /chromium-browser"
  name="/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq" pid=8984
  comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  It would be nice to see
  "/sys/devices/system/**/cpufreq/cpuinfo_max_freq r," added to the
  profile.

  My patch regarding the issue is attached.

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

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

[Touch-packages] [Bug 1681528] Re: Include information about python versions

[Brian Murray]

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

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

Title:
  Include information about python versions

Status in apport package in Ubuntu:
  New

Bug description:
  We are see lots of package installation failures that look like:

  package:apport:2.20.3-0ubuntu8
  Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ...
    File "/usr/bin/pyclean", line 63
  except (IOError, OSError), e:
   ^
  SyntaxError: invalid syntax

  One explanation for this is that pyclean is actually be run by python3
  instead of python2.7. To confirm and invalidate reports like this
  apport should check to see what /usr/bin/python and /usr/bin/python3
  are symlinks to or double check the versions of /usr/bin/python and
  /usr/bin/python3.

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

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

[Touch-packages] [Bug 1701753] [NEW] package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar conf

[Ana Paula Da Silva Moreira Bertante]

Public bug reported:

Por favor eunão entendo o que esta de errado com este sistema, eu sou nova no 
linux, por isso por favor peço sua compreenção pra me ajudar a resolver os 
problemas 
obrigada

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.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.1
Architecture: amd64
Date: Fri Jun 30 19:54:04 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2.2
 libgcc1 1:6.3.0-12ubuntu2
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
InstallationDate: Installed on 2017-05-06 (55 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: nspr
Title: package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 failed to
  install/upgrade: O pacote está num mau estado de inconsistência; deve
  reinstala-lo antes de tentar configura-lo.

Status in nspr package in Ubuntu:
  New

Bug description:
  Por favor eunão entendo o que esta de errado com este sistema, eu sou nova no 
linux, por isso por favor peço sua compreenção pra me ajudar a resolver os 
problemas 
  obrigada

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.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.1
  Architecture: amd64
  Date: Fri Jun 30 19:54:04 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2017-05-06 (55 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: nspr
  Title: package libnspr4:amd64 2:4.13.1-0ubuntu0.17.04.1 failed to 
install/upgrade: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1701750] Re: package libdrm-intel1:amd64 2.4.56-1~ubuntu2 failed to install/upgrade: package libdrm-intel1:amd64 is not ready for configuration cannot configure (current status `

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libdrm-intel1:amd64 2.4.56-1~ubuntu2 failed to
  install/upgrade: package libdrm-intel1:amd64 is not ready for
  configuration  cannot configure (current status `half-installed')

Status in libdrm package in Ubuntu:
  New

Bug description:
  when i'm updating, ubuntu crashed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libdrm-intel1:amd64 2.4.56-1~ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  Uname: Linux 3.16.0-38-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  AptOrdering:
   p7zip-full: Install
   libdrm-intel1: Configure
   p7zip-full: Configure
  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: Sat Jul  1 02:01:23 2017
  DistUpgraded: 2017-07-01 02:00:40,362 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:libdrm-intel1:amd64:2.4.56-1~ubuntu2:package 
libdrm-intel1:amd64 is not ready for configuration  cannot configure (current 
status `half-installed')
  ErrorMessage: package libdrm-intel1:amd64 is not ready for configuration  
cannot configure (current status `half-installed')
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103]
   NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103]
  InstallationDate: Installed on 2015-05-26 (766 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. N56VZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic.efi.signed 
root=UUID=b3547f2f-bb5b-4ced-a0b3-09a217747d64 ro quiet splash vt.handoff=7
  SourcePackage: libdrm
  Title: package libdrm-intel1:amd64 2.4.56-1~ubuntu2 failed to 
install/upgrade: package libdrm-intel1:amd64 is not ready for configuration  
cannot configure (current status `half-installed')
  UpgradeStatus: Upgraded to trusty on 2017-06-30 (0 days ago)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Jul  1 01:50:49 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12620 
   vendor SEC
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1701750] [NEW] package libdrm-intel1:amd64 2.4.56-1~ubuntu2 failed to install/upgrade: package libdrm-intel1:amd64 is not ready for configuration cannot configure (current status

[Ayhan Yüce]

Public bug reported:

when i'm updating, ubuntu crashed

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libdrm-intel1:amd64 2.4.56-1~ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
Uname: Linux 3.16.0-38-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
AptOrdering:
 p7zip-full: Install
 libdrm-intel1: Configure
 p7zip-full: Configure
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: Sat Jul  1 02:01:23 2017
DistUpgraded: 2017-07-01 02:00:40,362 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DuplicateSignature: package:libdrm-intel1:amd64:2.4.56-1~ubuntu2:package 
libdrm-intel1:amd64 is not ready for configuration  cannot configure (current 
status `half-installed')
ErrorMessage: package libdrm-intel1:amd64 is not ready for configuration  
cannot configure (current status `half-installed')
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103]
 NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103]
InstallationDate: Installed on 2015-05-26 (766 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: ASUSTeK COMPUTER INC. N56VZ
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic.efi.signed 
root=UUID=b3547f2f-bb5b-4ced-a0b3-09a217747d64 ro quiet splash vt.handoff=7
SourcePackage: libdrm
Title: package libdrm-intel1:amd64 2.4.56-1~ubuntu2 failed to install/upgrade: 
package libdrm-intel1:amd64 is not ready for configuration  cannot configure 
(current status `half-installed')
UpgradeStatus: Upgraded to trusty on 2017-06-30 (0 days ago)
dmi.bios.date: 11/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VZ.215
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VZ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N56VZ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Jul  1 01:50:49 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12620 
 vendor SEC
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: amd64 apport-package compiz-0.9 trusty ubuntu

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

Title:
  package libdrm-intel1:amd64 2.4.56-1~ubuntu2 failed to
  install/upgrade: package libdrm-intel1:amd64 is not ready for
  configuration  cannot configure (current status `half-installed')

Status in libdrm package in Ubuntu:
  New

Bug description:
  when i'm updating, ubuntu crashed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libdrm-intel1:amd64 2.4.56-1~ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  Uname: Linux 3.16.0-38-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  AptOrdering:
   p7zip-full: Install
   libdrm-intel1: Configure
   p7zip-full: Configure
  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: Sat Jul  1 02:01:23 2017
  DistUpgraded: 2017-07-01 02:00:40,362 DEBUG 

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

[Brian Murray]

This also works for me on xenial with apport version 2.20.1-0ubuntu2.9:

== DuplicateSignature =
package:linux-image-4.4.0-84-generic:4.4.0-84.107
Setting up linux-image-4.4.0-84-generic (4.4.0-84.107) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-84-generic 
/boot/vmlinuz-4.4.0-84-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-84-generic 
/boot/vmlinuz-4.4.0-84-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-84-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-84-generic 
/boot/vmlinuz-4.4.0-84-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-84-generic /boot/vmlinuz-4.4.0-84-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-84-generic 
/boot/vmlinuz-4.4.0-84-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-84-generic 
/boot/vmlinuz-4.4.0-84-generic
/usr/sbin/grub-mkconfig: 15: /etc/default/grub: Syntax error: Unterminated 
quoted string
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 2
Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.4.0-84-generic.postinst line 1052.
dpkg: error processing package linux-image-4.4.0-84-generic (--configure):
 subprocess installed post-installation script returned error exit status 2


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

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

Title:
  duplicate signature for Package problems can be too short

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

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

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

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

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

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

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

  But is missing:

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

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

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

  The shim-signed package prints a line starts with "Installing " and
  that matches PKG_MSGS so we reset the dupe_sig because 

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

[Brian Murray]

This also works for me on yakkety with apport version 2.20.3-0ubuntu8.6:

Setting up linux-image-4.8.0-58-generic (4.8.0-58.63) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.8.0-58-generic 
/boot/vmlinuz-4.8.0-58-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.8.0-58-generic 
/boot/vmlinuz-4.8.0-58-generic
update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.8.0-58-generic 
/boot/vmlinuz-4.8.0-58-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.8.0-58-generic /boot/vmlinuz-4.8.0-58-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.8.0-58-generic 
/boot/vmlinuz-4.8.0-58-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.8.0-58-generic 
/boot/vmlinuz-4.8.0-58-generic
/usr/sbin/grub-mkconfig: 15: /etc/default/grub: Syntax error: Unterminated 
quoted string
run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 2
Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.8.0-58-generic.postinst line 1052.
dpkg: error processing package linux-image-4.8.0-58-generic (--configure):
 subprocess installed post-installation script returned error exit status 2


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

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

Title:
  duplicate signature for Package problems can be too short

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

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

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

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

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

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

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

  But is missing:

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

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

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

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

To manage notifications about this bug go to:

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

[Brian Murray]

This worked for me in zesty with apport version 2.20.4-0ubuntu4.4:

DuplicateSignature:
 package:linux-image-4.10.0-22-generic:4.10.0-22.24
 Setting up linux-image-4.10.0-22-generic (4.10.0-22.24) ...
 Running depmod.
 update-initramfs: deferring update (hook will be called later)
 Not updating initrd symbolic links since we are being updated/reinstalled 
 (4.10.0-22.24 was configured last, according to dpkg) 
 Not updating image symbolic links since we are being updated/reinstalled 
 (4.10.0-22.24 was configured last, according to dpkg) 
 Examining /etc/kernel/postinst.d.
 run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
 run-parts: executing /etc/kernel/postinst.d/dkms 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
 update-initramfs: Generating /boot/initrd.img-4.10.0-22-generic
 run-parts: executing /etc/kernel/postinst.d/pm-utils 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
 run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.10.0-22-generic /boot/vmlinuz-4.10.0-22-generic
 run-parts: executing /etc/kernel/postinst.d/update-notifier 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
 run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
 /usr/sbin/grub-mkconfig: 15: /etc/default/grub: Syntax error: Unterminated 
quoted string
 run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 2
 Failed to process /etc/kernel/postinst.d at 
/var/lib/dpkg/info/linux-image-4.10.0-22-generic.postinst line 1052. 
 dpkg: error processing package linux-image-4.10.0-22-generic (--configure):
  subprocess installed post-installation script returned error exit status 2


** Tags removed: verification-needed-zesty
** Tags added: verification-done-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:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed
Status in apport source package in Yakkety:
  Fix Committed
Status in apport source package in Zesty:
  Fix Committed
Status in apport source package in Artful:
  Fix Released

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

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

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

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

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

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

  But is missing:

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

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

  145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
  146 'Installing ', 'Preparing', 'Processing 
triggers', 'Purging',
  147 'Removing', 'Replaced', 'Replacing', 'Setting up',
  148 

[Touch-packages] [Bug 1652131] Re: Putting Apparmor profile usr.lib.dovecot.auth into enforce mode blocks access to /var/spool/private/auth for Dovecot

[Launchpad Bug Tracker]

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

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

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

Title:
  Putting Apparmor profile usr.lib.dovecot.auth into enforce mode blocks
  access to /var/spool/private/auth for Dovecot

Status in AppArmor:
  Fix Released
Status in AppArmor 2.10 series:
  Fix Released
Status in AppArmor 2.9 series:
  Fix Released
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  Installing Postfix and Dovecot and setting them up as explained at
  https://help.ubuntu.com/lts/serverguide/postfix.html

  Then setting all apparmor profiles including Postfix and Dovecot to
  enforce mode.

  Postfix fails to send a TLS protected email because Dovecot can't
  connect to /var/spool/postfix/auth/private because when Dovecot's
  apparmor profile is set to enforce mode, apparmor denies Dovecot
  access to /var/spool/postfix/auth/private.

  Syslog
  apparmor="DENIED" operation="connect" profile="/usr/lib/dovecot/auth" 
name="/run/dovecot/anvil-auth-penalty" pid=8251 comm="auth" requested_mask="wr" 
denied_mask="wr" fsuid=0 ouid=0

  apparmor="DENIED" operation="open" profile="/usr/lib/dovecot/auth"
  name="/run/dovecot/stats-user" pid=8251 comm="auth" requested_mask="w"
  denied_mask="w" fsuid=0 ouid=0

  apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
  disconnected path" error=-13 profile="/usr/lib/dovecot/log"
  name="run/systemd/journal/dev-log" pid=8093 comm="log"
  requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
  disconnected path" error=-13 profile="/usr/lib/dovecot/log"
  name="run/systemd/journal/dev-log" pid=8093 comm="log"
  requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  apparmor="DENIED" operation="file_perm"
  profile="/usr/lib/dovecot/auth" name="/var/spool/postfix/private/auth"
  pid=8251 comm="auth" requested_mask="w" denied_mask="w" fsuid=129
  ouid=130

  apparmor="DENIED" operation="file_perm"
  profile="/usr/lib/dovecot/auth" name="/var/spool/postfix/private/auth"
  pid=8251 comm="auth" requested_mask="w" denied_mask="w" fsuid=129
  ouid=130

  Dec 22 10:38:20 frontier postfix/master[1516]: warning: process
  /usr/lib/postfix/sbin/smtpd pid 8248 exit status 1

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

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

[Touch-packages] [Bug 1331856] Re: apparmor-utils don't work when defining a variable on

[intrigeri]

Anyone interested in moving this forward: please send a merge request.
We're apparently not very good at tracking patches attached to bug
reports, sorry!

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

Title:
  apparmor-utils don't work when defining a variable on
  

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  New

Bug description:
  When a variable is set in tunables/home.d/ the apparmor-utils programs
  don't work and return this error messages:

  root@ws24:~# aa-logprof 
  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.loadincludes()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 4643, in 
loadincludes
  load_include(fi)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 4520, in 
load_include
  incdata = parse_profile_data(data, incfile, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2839, in 
parse_profile_data
  store_list_var(profile_data[profile]['lvar'], list_var, value, 
var_operation)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3279, in 
store_list_var
  raise AppArmorException(_('Values added to a non-existing variable: %s') 
% list_var)
  apparmor.common.AppArmorException: 'Values added to a non-existing variable: 
@{HOMEDIRS}'
  root@ws24:~#

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

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

[Touch-packages] [Bug 1385414] Re: provide systemd compatible cache loading library

[intrigeri]

I could ask for help to the person who implemented the initial AppArmor
support in systemd. But first I would need a clearer task description
than "Add systemd task since it needs an update to make it use the cache
loading library". What exactly do we need systemd to do?

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

Title:
  provide systemd compatible cache loading library

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This tracks the work related to moving AppArmor to systemd in support
  of bug 1379542.

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

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

[Touch-packages] [Bug 1507469] Re: Evince's AppArmor profile prevents opening docs from other apps under Wayland

[intrigeri]

This was fixed in 2.11.0 so it's fixed in zesty.

** Summary changed:

- Evince's Apparmour profile prevents opening docs from other apps under Wayland
+ Evince's AppArmor profile prevents opening docs from other apps under Wayland

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

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

Title:
  Evince's AppArmor profile prevents opening docs from other apps under
  Wayland

Status in AppArmor:
  Fix Released
Status in AppArmor 2.10 series:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  Evince fails to run when launched from another app (Nautilus, Ephy,
  etc) and running under Wayland. For example, nothing appears to happen
  when double-clicking on a PDF file in Nautilus. Evince is launched,
  but its Apparmour profile is preventing access to a Wayland socket,
  hence it immediately exits.

  The following is typical of the reported error:

  > Oct 19 15:06:40 payens kernel: audit: type=1400
  audit(1445227600.333:26): apparmor="DENIED" operation="connect"
  profile="/usr/bin/evince" name="/run/user/1000/wayland-0" pid=12956
  comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000
  ouid=1000

  Adding the following lines to it's local Apparmour config and
  reloading Apparmour fixes the problem:

  >  owner /run/user/*/wayland-* rw,
  >  owner /run/user/*/weston-shared-* rw,

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: evince 3.16.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 19 17:49:19 2015
  InstallationDate: Installed on 2015-07-22 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: evince
  UpgradeStatus: Upgraded to wily on 2015-08-27 (52 days ago)

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

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

[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal

[David Britton]

I have a candidate for this to be submitted into artful, and then we can
work on the SRU back to trusty after it's accepted.  As this one went a
bit out of order (precise first after it EOLed!), I'll just attach the
git tag in upstream:

https://github.com/CanonicalLtd/ubuntu-advantage-script/releases/tag/v2

Currently the script does nothing for newer releases of Ubuntu.  Once
those release go EOL and an ESM product is available for them, we will
request an SRU with new bits.  But, that will be a while.

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

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  New
Status in ubuntu-meta source package in Trusty:
  New
Status in ubuntu-advantage-tools source package in Xenial:
  New
Status in ubuntu-meta source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Yakkety:
  New
Status in ubuntu-meta source package in Yakkety:
  New
Status in ubuntu-advantage-tools source package in Zesty:
  New
Status in ubuntu-meta source package in Zesty:
  New
Status in ubuntu-advantage-tools source package in Artful:
  New
Status in ubuntu-meta source package in Artful:
  New

Bug description:
  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help
   * Run sudo ubuntu-advantage enable  (without sudo it will warn you), 
but you need to be an ubuntu-advantage customer to get that token.  In the end, 
the script simply adds and removes an /etc/apt/sources.list.d entry.
   * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

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

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

[Touch-packages] [Bug 740510] Re: multiarch paths in abstractions should not be Linux-specific

[intrigeri]

FWIW Stretch was released for Linux architectures only, and I doubt
it'll change any time soon. I believe the Debian landscape looked
different when Steve filed this bug in 2011. Nowadays I'm not sure
what's the value of keeping this bug open.

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

Title:
  multiarch paths in abstractions should not be Linux-specific

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apparmor

  The latest changes in natty to allow multiarch paths for apparmor use
  /lib/*-linux-gnu/ in their paths.  This is sufficient for all the
  architectures Ubuntu supports, and it's sufficient for native binaries
  on these architectures, but multiarch is intended to be fully cross-
  platform and be usable for binaries for other kernels.  Even if
  apparmor itself doesn't run on BSD, Hurd kernels, Debian builds
  packages for these architectures and these will be cross-installable
  on multiarch systems... and some of them may even run, by way of
  kernel syscall emulation layers (in-kernel, qemu, etc).  So the
  apparmor abstractions should account for this and not be limited to
  linux-gnu triplets.

  (This is obviously a low-priority edge case.)

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

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

[Touch-packages] [Bug 776648] Re: apparmor profile for chromium browser

[intrigeri]

This bug report is about the custom profile shipped by Ubuntu in their
apparmor-profiles package (and nowhere else AFAIK), not about the
apparmor-profiles project (yeah, it's confusing, I know).

** Changed in: apparmor-profiles
   Status: Triaged => Invalid

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

Title:
  apparmor profile for chromium browser

Status in AppArmor Profiles:
  Invalid
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  Packages: apparmor 2.6.1-0ubuntu3 + apparmor-profiles 2.6.1-0ubuntu3
  installed on natty.

  I would like to thank first of all that is made ​​of the Chromium browser 
apparmor profile. 
  We are delighted to have found that it works perfectly. 
  First installation of the profile works well. 
  After software update, the Chromium browser "11.0.696.057 (82,915) 11.4 
Ubuntu" no longer starts. 
  Only "complain" mode in the / etc / apparmor.d / usr.bin.chromium rule used 
by the browser. 
  Read permissions to the request 
  / sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq 
  and 
  / sys/devices/pci: 00/: 00:00.0 / resource access. 

  The "aa-logprof" command I can not be improved.

  Thank you in advance for your help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/776648/+subscriptions

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

[Touch-packages] [Bug 1101298] Re: More resources must be added into Chromium profile

[intrigeri]

This bug report is about the custom profile shipped by Ubuntu in their
apparmor-profiles package (and nowhere else AFAIK), not about the
apparmor-profiles project (yeah, it's confusing, I know).

** Project changed: apparmor-profiles => apparmor (Ubuntu)

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

Title:
  More resources must be added into Chromium profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  When I install apparmor-profiles package and set Chromium AppArmor
  profile to enforce mode,  Chromium cannot detect the default browser
  and claims that it is not the default browser even though I set so.
  And I see this line in dmesg:

  ... type=1400 audit(1358526376.204:84): apparmor="DENIED"
  operation="exec" parent=6216 profile="/usr/lib/chromium-browser
  /chromium-browser//xdgsettings" name="/usr/bin/gawk" pid=6220 comm
  ="xdg-mime" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  Now, there is only /usr/bin/mawk line in Chromium apparmor profile but
  users may use a different implementation thanks to the alternatives
  system.

  In addition, my dmesg is flooded by these lines:

  ... type=1400 audit(1358527121.548:197): apparmor="DENIED"
  operation="open" parent=6072 profile="/usr/lib/chromium-browser
  /chromium-browser"
  name="/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq" pid=8984
  comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  It would be nice to see
  "/sys/devices/system/**/cpufreq/cpuinfo_max_freq r," added to the
  profile.

  My patch regarding the issue is attached.

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

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[MF]

Have the same issue with 17.04. Especially then qBittorent starting.
Also huge lag with apt update resolve servers.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 

[Touch-packages] [Bug 1101298] [NEW] More resources must be added into Chromium profile

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I install apparmor-profiles package and set Chromium AppArmor
profile to enforce mode,  Chromium cannot detect the default browser and
claims that it is not the default browser even though I set so. And I
see this line in dmesg:

... type=1400 audit(1358526376.204:84): apparmor="DENIED"
operation="exec" parent=6216 profile="/usr/lib/chromium-browser
/chromium-browser//xdgsettings" name="/usr/bin/gawk" pid=6220 comm="xdg-
mime" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

Now, there is only /usr/bin/mawk line in Chromium apparmor profile but
users may use a different implementation thanks to the alternatives
system.

In addition, my dmesg is flooded by these lines:

... type=1400 audit(1358527121.548:197): apparmor="DENIED"
operation="open" parent=6072 profile="/usr/lib/chromium-browser
/chromium-browser"
name="/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq" pid=8984
comm="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0

It would be nice to see "/sys/devices/system/**/cpufreq/cpuinfo_max_freq
r," added to the profile.

My patch regarding the issue is attached.

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

-- 
More resources must be added into Chromium profile
https://bugs.launchpad.net/bugs/1101298
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apparmor in Ubuntu.

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

[Touch-packages] [Bug 1701726] Re: unattended upgrades removing kerberos and breaking system

[Launchpad Bug Tracker]

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

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

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

Title:
  unattended upgrades removing kerberos and breaking system

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Ok, so this may not be a bug specifically in unattended-upgrades, but
  I can't determine where else it would be.

  Having my server broken by unattended upgrades removing the primary
  login system (kerberos) once might be considered unlucky, or perhaps a
  typo - but now that it has happened twice it looks like a bug.

  The problem seems to be that several krb related packages were removed, along 
with puppet packages which we use to help maintain the system.
  The result was all remote logins (ssh/http/smtp/imap/etc) were broken and 
serial console had to be used to recover the sysem

  
  Pulling from logs from today:
  ```Start-Date: 2017-06-30  15:22:20
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7)
  Remove: ubuntu-standard:amd64 (1.361), host:amd64 
(1:9.10.3.dfsg.P4-8ubuntu1.6), librarian-puppet:amd64 (2.2.1-2), 
libapache2-mod-auth-kerb:amd64 (5.4-2.2), krb5-admin-server:amd64 
(1.13.2+dfsg-5ubuntu2), krb5-user:amd64 (1.13.2+dfsg-5ubuntu2), 
libpam-krb5:amd64 (4.7-2), facter:amd64 (2.4.6-1), krb5-kdc:amd64 
(1.13.2+dfsg-5ubuntu2), krb5-config:amd64 (2.3), puppet:amd64 
(3.8.5-2ubuntu0.1), puppet-common:amd64 (3.8.5-2ubuntu0.1)
  End-Date: 2017-06-30  15:22:27

  Start-Date: 2017-06-30  15:22:32
  Commandline: /usr/bin/unattended-upgrade
  Remove: libaugeas0:amd64 (1.4.0-0ubuntu1), libverto-libevent1:amd64 
(0.2.4-2.1ubuntu2), virt-what:amd64 (1.14-1), libkadm5clnt-mit9:amd64 
(1.13.2+dfsg-5ubuntu2), javascript-common:amd64 (11), ruby-multipart-post:amd64 
(1.2.0-2), ruby2.3:amd64 (2.3.1-2~16.04), ruby-safe-yaml:amd64 (1.0.4-1), 
rake:amd64 (10.5.0-2), ruby-net-telnet:amd64 (0.1.1-2), ruby-thor:amd64 
(0.19.1-2), ruby-librarian:amd64 (0.6.3-1), ruby-highline:amd64 (1.7.2-1), 
augeas-lenses:amd64 (1.4.0-0ubuntu1), ruby-minitar:amd64 (0.5.4-3), 
libkdb5-8:amd64 (1.13.2+dfsg-5ubuntu2), libjs-jquery:amd64 (1.11.3+dfsg-4), 
ruby-json:amd64 (1.8.3-1build4), ruby-augeas:amd64 (1:0.5.0-3build4), 
ruby-shadow:amd64 (2.4.1-1build4), ruby-minitest:amd64 (5.8.4-2), hiera:amd64 
(2.0.0-2), ruby-deep-merge:amd64 (1.0.1+gitf9df6fdb-1), libruby2.3:amd64 
(2.3.1-2~16.04), ruby-selinux:amd64 (2.4-3build2), ruby:amd64 (1:2.3.0+1), 
libgssrpc4:amd64 (1.13.2+dfsg-5ubuntu2), libverto1:amd64 (0.2.4-2.1ubuntu2), 
ruby-rsync:amd64 (1.0.9-1), ruby-faraday
 -middleware:amd64 (0.10.0-1), ruby-power-assert:amd64 (0.2.7-1), unzip:amd64 
(6.0-20ubuntu1), zip:amd64 (3.0-11), ruby-semantic-puppet:amd64 (0.1.1-1), 
ruby-rgen:amd64 (0.7.0-2), rubygems-integration:amd64 (1.10), fonts-lato:amd64 
(2.0-1), ruby-faraday:amd64 (0.9.2-3), ruby-nokogiri:amd64 (1.6.7.2-3build1), 
libkadm5srv-mit9:amd64 (1.13.2+dfsg-5ubuntu2), ruby-test-unit:amd64 (3.1.7-2), 
libyaml-0-2:amd64 (0.1.6-3), ruby-puppet-forge:amd64 (2.1.3-1), 
ruby-did-you-mean:amd64 (1.0.0-2)
  End-Date: 2017-06-30  15:22:34
  ```

  
  And the pervious time it failed in January this year:
  ```Start-Date: 2017-01-13  02:35:06
  Commandline: /usr/bin/unattended-upgrade
  Install: host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, automatic)
  Upgrade: libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), 

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

[Steve Langasek]

Hello Brian, or anyone else affected,

Accepted apport into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.6 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-yakkety to verification-done-yakkety.If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-yakkety. 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 added: verification-needed-xenial

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

Title:
  duplicate signature for Package problems can be too short

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

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

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

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

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

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

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

  But is missing:

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

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

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

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

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

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

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

[Steve Langasek]

Hello Brian, or anyone else affected,

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

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

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

Title:
  duplicate signature for Package problems can be too short

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

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

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

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

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

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

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

  But is missing:

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

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

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

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

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

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

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

[Steve Langasek]

Hello Brian, or anyone else affected,

Accepted apport into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.4 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-zesty to verification-done-zesty.If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. 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 added: verification-needed-zesty

** Tags added: verification-needed-yakkety

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

Title:
  duplicate signature for Package problems can be too short

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

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

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

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

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

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

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

  But is missing:

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

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

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

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

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

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

[Touch-packages] [Bug 1701297] Re: NTP reload failure (unable to read library) on overlayfs

[John Johansen]

Andres,

can you be more specific about the kernel version of the hwe kernel you
are seeing this on?

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

Title:
  NTP reload failure (unable to read library) on overlayfs

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

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

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

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

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

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

[Touch-packages] [Bug 1701726] [NEW] unattended upgrades removing kerberos and breaking system

[Anton Piatek]

Public bug reported:

Ok, so this may not be a bug specifically in unattended-upgrades, but I
can't determine where else it would be.

Having my server broken by unattended upgrades removing the primary
login system (kerberos) once might be considered unlucky, or perhaps a
typo - but now that it has happened twice it looks like a bug.

The problem seems to be that several krb related packages were removed, along 
with puppet packages which we use to help maintain the system.
The result was all remote logins (ssh/http/smtp/imap/etc) were broken and 
serial console had to be used to recover the sysem


Pulling from logs from today:
```Start-Date: 2017-06-30  15:22:20
Commandline: /usr/bin/unattended-upgrade
Upgrade: libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.6, 
1:9.10.3.dfsg.P4-8ubuntu1.7)
Remove: ubuntu-standard:amd64 (1.361), host:amd64 
(1:9.10.3.dfsg.P4-8ubuntu1.6), librarian-puppet:amd64 (2.2.1-2), 
libapache2-mod-auth-kerb:amd64 (5.4-2.2), krb5-admin-server:amd64 
(1.13.2+dfsg-5ubuntu2), krb5-user:amd64 (1.13.2+dfsg-5ubuntu2), 
libpam-krb5:amd64 (4.7-2), facter:amd64 (2.4.6-1), krb5-kdc:amd64 
(1.13.2+dfsg-5ubuntu2), krb5-config:amd64 (2.3), puppet:amd64 
(3.8.5-2ubuntu0.1), puppet-common:amd64 (3.8.5-2ubuntu0.1)
End-Date: 2017-06-30  15:22:27

Start-Date: 2017-06-30  15:22:32
Commandline: /usr/bin/unattended-upgrade
Remove: libaugeas0:amd64 (1.4.0-0ubuntu1), libverto-libevent1:amd64 
(0.2.4-2.1ubuntu2), virt-what:amd64 (1.14-1), libkadm5clnt-mit9:amd64 
(1.13.2+dfsg-5ubuntu2), javascript-common:amd64 (11), ruby-multipart-post:amd64 
(1.2.0-2), ruby2.3:amd64 (2.3.1-2~16.04), ruby-safe-yaml:amd64 (1.0.4-1), 
rake:amd64 (10.5.0-2), ruby-net-telnet:amd64 (0.1.1-2), ruby-thor:amd64 
(0.19.1-2), ruby-librarian:amd64 (0.6.3-1), ruby-highline:amd64 (1.7.2-1), 
augeas-lenses:amd64 (1.4.0-0ubuntu1), ruby-minitar:amd64 (0.5.4-3), 
libkdb5-8:amd64 (1.13.2+dfsg-5ubuntu2), libjs-jquery:amd64 (1.11.3+dfsg-4), 
ruby-json:amd64 (1.8.3-1build4), ruby-augeas:amd64 (1:0.5.0-3build4), 
ruby-shadow:amd64 (2.4.1-1build4), ruby-minitest:amd64 (5.8.4-2), hiera:amd64 
(2.0.0-2), ruby-deep-merge:amd64 (1.0.1+gitf9df6fdb-1), libruby2.3:amd64 
(2.3.1-2~16.04), ruby-selinux:amd64 (2.4-3build2), ruby:amd64 (1:2.3.0+1), 
libgssrpc4:amd64 (1.13.2+dfsg-5ubuntu2), libverto1:amd64 (0.2.4-2.1ubuntu2), 
ruby-rsync:amd64 (1.0.9-1), ruby-faraday-m
 iddleware:amd64 (0.10.0-1), ruby-power-assert:amd64 (0.2.7-1), unzip:amd64 
(6.0-20ubuntu1), zip:amd64 (3.0-11), ruby-semantic-puppet:amd64 (0.1.1-1), 
ruby-rgen:amd64 (0.7.0-2), rubygems-integration:amd64 (1.10), fonts-lato:amd64 
(2.0-1), ruby-faraday:amd64 (0.9.2-3), ruby-nokogiri:amd64 (1.6.7.2-3build1), 
libkadm5srv-mit9:amd64 (1.13.2+dfsg-5ubuntu2), ruby-test-unit:amd64 (3.1.7-2), 
libyaml-0-2:amd64 (0.1.6-3), ruby-puppet-forge:amd64 (2.1.3-1), 
ruby-did-you-mean:amd64 (1.0.0-2)
End-Date: 2017-06-30  15:22:34
```


And the pervious time it failed in January this year:
```Start-Date: 2017-01-13  02:35:06
Commandline: /usr/bin/unattended-upgrade
Install: host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.4, automatic)
Upgrade: libisccfg140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), bind9-host:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), dnsutils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), libisc160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), liblwres141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), bind9:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), libdns162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), libisccc140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4), libbind9-140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.3, 
1:9.10.3.dfsg.P4-8ubuntu1.4)
Remove: ubuntu-standard:amd64 (1.361), librarian-puppet:amd64 (2.2.1-2), 
libapache2-mod-auth-kerb:amd64 (5.4-2.2), krb5-admin-server:amd64 
(1.13.2+dfsg-5), krb5-user:amd64 (1.13.2+dfsg-5), libpam-krb5:amd64 (4.7-2), 
facter:amd64 (2.4.6-1), krb5-kdc:amd64 (1.13.2+dfsg-5), krb5-config:amd64 
(2.3), puppet:amd64 (3.8.5-2), puppet-common:amd64 (3.8.5-2)
End-Date: 2017-01-13  02:35:13```

After the first failure in January the main 

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

[Shay Perlstein]

@Giacomo Orlandi, I experience what you describe since day one with
Ubuntu 16.04 (DELL + USB DOCK). My work around is to disable the
flickering screen and revert the settings.

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-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
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1701572] Re: [regression] bluetooth headset not connecting after regular update

[Thomas Mayer]

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

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

Title:
  [regression] bluetooth headset not connecting after regular update

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Hi, my bluetooth headset Arctic P311 was connecting until I installed
  these updates:

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

  For pulseaudio changes, I got this changelog:

  --- Änderungen für pulseaudio (libpulsedsp libpulse-mainloop-glib0 pulseaudio 
pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 
pulseaudio-module-zeroconf pulseaudio-utils) ---
  Holen:1 http://changelogs.ubuntu.com pulseaudio 1:8.0-0ubuntu3.3 Changelog 
[216 kB]
  pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

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

  Before, the P311 headset was connecting, after the update, it's not.
  Looks like a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluetooth 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 16:06:36 2017
  InstallationDate: Installed on 2014-11-29 (944 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E5510
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-58-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (379 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 5C:AC:4C:F8:E1:98  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:2055 acl:26 sco:0 events:96 errors:0
TX 

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Thomas Mayer]

I just reproduced the freeze again after switching off wireless devices
with a physical switch in my laptop. After reenabling wireless devices,
videos froze again. Worked around it by changing bluetooth profiles
(away from A2DP and back again).

So this issue is still not fixed.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Thomas Mayer]

I think that one of the recent updates fixed it (and it also survives
S2RAM):

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

I could not reproduce this issue at least. This time, I repaired my
device with Blueman as pure audio device. Could also be that this works
around the issue. At least does it seem to work now.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Touch-packages] [Bug 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

[Thomas Mayer]

Looks as if one of these updates improved it for S2RAM, but not for
hardware switch (I mean a real physical switch in my laptop for all
wireless hardware)

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

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

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking and after
  suspend/resume

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1701572] Re: [regression] bluetooth headset not connecting after regular update

[Thomas Mayer]

I worked around it.

I had to remove --purge
bluetooth bluez blueman bluetooth pulseaudio pulseaudio-module-bluetooth

Then I removed all pairing information with devices, both in
~/.config/pulse and /var/lib/bluetooth

Then rebooted

Then paired my A2DP device again, this time with blueman.

Then everything was working.

I think the main problem here is that I once had device discovery
disabled in /etc/pulse/default.pa. But that's not a bug in ubuntu.

Issue can be closed.

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

Title:
  [regression] bluetooth headset not connecting after regular update

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi, my bluetooth headset Arctic P311 was connecting until I installed
  these updates:

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

  For pulseaudio changes, I got this changelog:

  --- Änderungen für pulseaudio (libpulsedsp libpulse-mainloop-glib0 pulseaudio 
pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 
pulseaudio-module-zeroconf pulseaudio-utils) ---
  Holen:1 http://changelogs.ubuntu.com pulseaudio 1:8.0-0ubuntu3.3 Changelog 
[216 kB]
  pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

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

  Before, the P311 headset was connecting, after the update, it's not.
  Looks like a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluetooth 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 16:06:36 2017
  InstallationDate: Installed on 2014-11-29 (944 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E5510
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-58-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (379 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

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

[Esokrates]

Kai: I do not understand your last comment, could you elaborate? Did you
mean we should test if software boost = pulseaudio boost performs well
enough?

Kai, I am quite happy with
http://people.canonical.com/~khfeng/lp1654448-2/ please link me the
patch as the only drawback would be the lower volume, right? :-).

I will try to test the pulseaudio boost in the next days. Could you
explain a bit of theory? What would you expect in terms of quality
regarding the pulseaudio boost? Is there something special I  should
consider? What would be a good way to test for disortion?

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

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

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

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1701692] [NEW] package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Jesús]

Public bug reported:

package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is
in a very bad inconsistent state; you should  reinstall it before
attempting configuration

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: util-linux 2.29-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Fri Jun 30 18:02:59 2017
DpkgTerminalLog:
 dpkg: error processing package util-linux (--configure):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-06-27 (3 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: util-linux
Title: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in util-linux package in Ubuntu:
  New

Bug description:
  package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Fri Jun 30 18:02:59 2017
  DpkgTerminalLog:
   dpkg: error processing package util-linux (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-06-27 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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: unattended-upgrades does not block shutdown of system, as it is designed to

[Balint Reczey]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

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

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 1691901] Re: [SRU] 50-motd-news costs 5 seconds every login on firewalled systems

[Robie Basak]

Hello Scott, or anyone else affected,

Accepted base-files into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/9.6ubuntu13.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-zesty to verification-done-zesty.If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-zesty. 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: base-files (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

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

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

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

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

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

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

  === SRU ===

  [ IMPACT ]

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

  [ TEST CASE ]

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

  Failure case:

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

  Apply the fix.

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

  [ REGRESSION ]

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

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

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

[Will Cooke]

Added to Trello: https://trello.com/c/mCxJtmcj/175-bug1701688-remove-
patch-that-disables-cork-plugin

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

Title:
  Remove patch that disables Cork plugin

Status in pulseaudio package in Ubuntu:
  New

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

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

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

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

[Corentin Noël]

Public bug reported:

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

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

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

Title:
  Remove patch that disables Cork plugin

Status in pulseaudio package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1701570] Re: Acquire.run(): crash with "double free or corruption"

[Hans Joachim Desserud]

** Tags added: trusty

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

Title:
  Acquire.run(): crash with "double free or corruption"

Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  We tried to implement a function returning an Acquire object
  "fetcher". Whenever we called "fetcher.run()" after generating the
  object using this function our program crashed with "*** Error in
  `/usr/bin/python': double free or corruption (fasttop): .. ***.

  You can reproduce this with the attached example code ("func=1"); the
  package to download must not be in the local archive. When you set
  "func=0" in this example the code works as expected.

  Our researches indicate that Acquire.run() seems to depend on data
  structures (memory) of the PackageManager object "pm". In
  "pm.get_archives(fetcher, ...)" the "fetcher" object stores pointers
  to data structures owned by PackageManager object "pm". This data
  structures (filenames) are needed for "fetcher.run()". But in the case
  "func=1" the PackageManager pm object is automatically freed by Python
  as soon as function "initFetcher(progress)" is left. Therefore the
  pointers stored in Acquire object "fetcher" are no longer valid.

  # lsb_release -rd
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  python-apt 0.9.3.5ubuntu2 amd64

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

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

[Giacomo Orlandi]

Sorry for the delay, I tried:
linux-image-4.4.0-83-generic doesn't work
linux-image-4.8.0-040800-generic  doesn't work
linux-image-4.10.0-041000-generic works
linux-image-4.11.0-041100-generic works


By the way, I didn't mention is that even the kernel versions that work are far 
from perfect. When I first login one of the 2 external screens goes black or 
starts flickering, but there is a workaround. I have to switch to text mode 
(Ctrl+Alt+F1) and back. With the kernel versions that don't work I couldn't 
find any workaround, the external screens go black and they don't switch on 
anymore.
Also, when I undock it while it's running it often crashes, and if it doesn't 
it crashes when I dock it back. Switching to text mode before docking/undocking 
seems to make more stable. That's most likely a different bug though.

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-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
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1701676] [NEW] package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione impossibile configurarlo

[vincenzo]

Public bug reported:

I get a window with this error as ubuntu boot

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun 29 19:03:11 2017
ErrorMessage: il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione 
 impossibile configurarlo (stato corrente "half-installed")
InstallationDate: Installed on 2016-07-14 (351 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione  impossibile 
configurarlo (stato corrente "half-installed")
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione
  impossibile configurarlo (stato corrente "half-installed")

Status in openssl package in Ubuntu:
  New

Bug description:
  I get a window with this error as ubuntu boot

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 29 19:03:11 2017
  ErrorMessage: il pacchetto libssl1.0.0:amd64 non è pronto per la 
configurazione  impossibile configurarlo (stato corrente "half-installed")
  InstallationDate: Installed on 2016-07-14 (351 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
il pacchetto libssl1.0.0:amd64 non è pronto per la configurazione  impossibile 
configurarlo (stato corrente "half-installed")
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1701570] Re: Acquire.run(): crash with "double free or corruption"

[Julian Andres Klode]

** Changed in: python-apt (Ubuntu)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu)
   Status: New => Triaged

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

Title:
  Acquire.run(): crash with "double free or corruption"

Status in python-apt package in Ubuntu:
  Triaged

Bug description:
  We tried to implement a function returning an Acquire object
  "fetcher". Whenever we called "fetcher.run()" after generating the
  object using this function our program crashed with "*** Error in
  `/usr/bin/python': double free or corruption (fasttop): .. ***.

  You can reproduce this with the attached example code ("func=1"); the
  package to download must not be in the local archive. When you set
  "func=0" in this example the code works as expected.

  Our researches indicate that Acquire.run() seems to depend on data
  structures (memory) of the PackageManager object "pm". In
  "pm.get_archives(fetcher, ...)" the "fetcher" object stores pointers
  to data structures owned by PackageManager object "pm". This data
  structures (filenames) are needed for "fetcher.run()". But in the case
  "func=1" the PackageManager pm object is automatically freed by Python
  as soon as function "initFetcher(progress)" is left. Therefore the
  pointers stored in Acquire object "fetcher" are no longer valid.

  # lsb_release -rd
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  python-apt 0.9.3.5ubuntu2 amd64

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

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

[Touch-packages] [Bug 1701619] [NEW] package libqt5svg5:i386 5.6.1-2build1~1 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installere

[willem.l]

Public bug reported:


package libqt5svg5:i386 5.6.1-2build1~1 failed to install/ufor chirp
  :90-9091 for gimp
  :81-2500 for i 
believe skype

computer says this in verry bad state i must go for a new install, but how?
sincerely
wim

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libqt5svg5:i386 5.6.1-2build1~1
ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
Uname: Linux 4.8.0-58-generic i686
ApportVersion: 2.20.3-0ubuntu8.3
Architecture: i386
Date: Fri Jun 30 16:54:00 2017
ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u zou 
het  opnieuw moeten installeren alvorens het te configureren.
InstallationDate: Installed on 2017-06-12 (17 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1.1
 apt  1.3.5
SourcePackage: qtsvg-opensource-src
Title: package libqt5svg5:i386 5.6.1-2build1~1 failed to install/upgrade: 
pakket verkeert in een heel slechte en inconsistente staat; u zou het  opnieuw 
moeten installeren alvorens het te configureren.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtsvg-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 yakkety

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

Title:
  package libqt5svg5:i386 5.6.1-2build1~1 failed to install/upgrade:
  pakket verkeert in een heel slechte en inconsistente staat; u zou het
  opnieuw moeten installeren alvorens het te configureren.

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

Bug description:
  
  package libqt5svg5:i386 5.6.1-2build1~1 failed to install/ufor chirp
:90-9091 for gimp
:81-2500 for i 
believe skype

  computer says this in verry bad state i must go for a new install, but how?
  sincerely
  wim

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libqt5svg5:i386 5.6.1-2build1~1
  ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
  Uname: Linux 4.8.0-58-generic i686
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: i386
  Date: Fri Jun 30 16:54:00 2017
  ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u 
zou het  opnieuw moeten installeren alvorens het te configureren.
  InstallationDate: Installed on 2017-06-12 (17 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: qtsvg-opensource-src
  Title: package libqt5svg5:i386 5.6.1-2build1~1 failed to install/upgrade: 
pakket verkeert in een heel slechte en inconsistente staat; u zou het  opnieuw 
moeten installeren alvorens het te configureren.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsvg-opensource-src/+bug/1701619/+subscriptions

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

[Touch-packages] [Bug 1701572] Re: [regression] bluetooth headset not connecting after regular update

[Thomas Mayer]

When I try to connect the headset (which still seems to pair), I see the
little lock next to the bluetooth device for ~0.5 seconds. Then the lock
disappears.

Syslog reports:
Jun 30 16:00:40 lat61 bluetoothd[1235]: a2dp-sink profile connect failed for 
00:1A:7D:70:08:7E: Protocol not available
Jun 30 16:00:45 lat61 bluetoothd[1235]: a2dp-sink profile connect failed for 
00:1A:7D:D0:24:5D: Protocol not available

Enabling the line
AutoEnable=true
in /etc/bluetooth/main.conf
does not fix this issue

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

Title:
  [regression] bluetooth headset not connecting after regular update

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi, my bluetooth headset Arctic P311 was connecting until I installed
  these updates:

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

  For pulseaudio changes, I got this changelog:

  --- Änderungen für pulseaudio (libpulsedsp libpulse-mainloop-glib0 pulseaudio 
pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 
pulseaudio-module-zeroconf pulseaudio-utils) ---
  Holen:1 http://changelogs.ubuntu.com pulseaudio 1:8.0-0ubuntu3.3 Changelog 
[216 kB]
  pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

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

  Before, the P311 headset was connecting, after the update, it's not.
  Looks like a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluetooth 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 16:06:36 2017
  InstallationDate: Installed on 2014-11-29 (944 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude E5510
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-58-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (379 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  

[Touch-packages] [Bug 1576066] Re: 32bit glibc calls old socketcall() syscall, causing seccomp problems

[Jamie Strandboge]

FYI, >=16.10 has libseccomp >= 2.3. xenial has 2.2.3-3ubuntu3 that
includes updated syscall tables for this (https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=809556 and
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1554098).

>=16.04 have 4.4 kernels and updated glibc.

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

** Changed in: libseccomp (Ubuntu)
 Assignee: Jamie Strandboge (jdstrand) => (unassigned)

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

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

** Changed in: libseccomp (Ubuntu Trusty)
   Status: New => Triaged

** Changed in: glibc (Ubuntu Trusty)
   Status: New => Triaged

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

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

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

Title:
  32bit glibc calls old socketcall() syscall, causing seccomp problems

Status in glibc package in Ubuntu:
  Fix Released
Status in libseccomp package in Ubuntu:
  Fix Released
Status in glibc source package in Trusty:
  Triaged
Status in libseccomp source package in Trusty:
  Triaged
Status in glibc source package in Xenial:
  Fix Released
Status in libseccomp source package in Xenial:
  Fix Released

Bug description:
  Back in the day when Linux was created for i386, for who knows what
  reason, all socket calls were multiplexed through a single syscall
  API, socketcall().  This was a strange thing to do, but it probably
  made sense from the standpoint of the same part of the kernel handling
  all of those calls.

  It was realised a long time ago that this was a strange and suboptimal
  arrangement.

  By the time they got around to doing amd64 and other architectures,
  they fixed this arrangement and gave each socket call a separate
  syscall entry point.  32bit systems continued to do it this old way,
  however, multiplexing all calls through socketcall().

  This is a problem for seccomp.  If we want to allow a program to make
  casual use of the network, but not bind a listener socket, we cannot
  currently do that.  On 64bits we just filter out the bind() and
  listen() calls, but on 32bit, it's all the same syscall.

  The kernel people fixed this problem up last summer by introducing
  new, separate, syscall entries for each separate call.

http://patchwork.sourceware.org/patch/7679/

  The problem is that glibc in Y is still using the old socketcall()
  interface on i386.  It needs to be updated to use the new calls.

  A possible caveat is that this might create problems for running newer
  binaries on older kernels on i386 (as we sometimes do with builders)
  because they won't have the new syscalls.  A solution could involve
  checking for ENOSYS and trying again via the old route.

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

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

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

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: package libssl1.0.0:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Again.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 17:59:34 2017
  ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-03 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1701570] [NEW] Acquire.run(): crash with "double free or corruption"

[tserries]

Public bug reported:

We tried to implement a function returning an Acquire object "fetcher".
Whenever we called "fetcher.run()" after generating the object using
this function our program crashed with "*** Error in `/usr/bin/python':
double free or corruption (fasttop): .. ***.

You can reproduce this with the attached example code ("func=1"); the
package to download must not be in the local archive. When you set
"func=0" in this example the code works as expected.

Our researches indicate that Acquire.run() seems to depend on data
structures (memory) of the PackageManager object "pm". In
"pm.get_archives(fetcher, ...)" the "fetcher" object stores pointers to
data structures owned by PackageManager object "pm". This data
structures (filenames) are needed for "fetcher.run()". But in the case
"func=1" the PackageManager pm object is automatically freed by Python
as soon as function "initFetcher(progress)" is left. Therefore the
pointers stored in Acquire object "fetcher" are no longer valid.

# lsb_release -rd
Description:Ubuntu 14.04.5 LTS
Release:14.04

python-apt 0.9.3.5ubuntu2 amd64

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

** Attachment added: "acquire-2.py"
   
https://bugs.launchpad.net/bugs/1701570/+attachment/4906676/+files/acquire-2.py

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

Title:
  Acquire.run(): crash with "double free or corruption"

Status in python-apt package in Ubuntu:
  New

Bug description:
  We tried to implement a function returning an Acquire object
  "fetcher". Whenever we called "fetcher.run()" after generating the
  object using this function our program crashed with "*** Error in
  `/usr/bin/python': double free or corruption (fasttop): .. ***.

  You can reproduce this with the attached example code ("func=1"); the
  package to download must not be in the local archive. When you set
  "func=0" in this example the code works as expected.

  Our researches indicate that Acquire.run() seems to depend on data
  structures (memory) of the PackageManager object "pm". In
  "pm.get_archives(fetcher, ...)" the "fetcher" object stores pointers
  to data structures owned by PackageManager object "pm". This data
  structures (filenames) are needed for "fetcher.run()". But in the case
  "func=1" the PackageManager pm object is automatically freed by Python
  as soon as function "initFetcher(progress)" is left. Therefore the
  pointers stored in Acquire object "fetcher" are no longer valid.

  # lsb_release -rd
  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  python-apt 0.9.3.5ubuntu2 amd64

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

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

[Touch-packages] [Bug 1701572] [NEW] [regression] bluetooth headset not connecting after regular update

[Thomas Mayer]

Public bug reported:

Hi, my bluetooth headset Arctic P311 was connecting until I installed
these updates:

libpulse0 1:8.0-0ubuntu3.3
libpulsedsp 1:8.0-0ubuntu3.3
libpulse-mainloop-glib0 1:8.0-0ubuntu3.3
pulseaudio 1:8.0-0ubuntu3.3
pulseaudio-module-bluetooth 1:8.0-0ubuntu3.3
pulseaudio-module-gconf 1:8.0-0ubuntu3.3
pulseaudio-module-x11 1:8.0-0ubuntu3.3
pulseaudio-module-zeroconf 1:8.0-0ubuntu3.3
pulseaudio-utils 1:8.0-0ubuntu3.3

linux-generic-hwe-16.04 4.8.0.58.29
linux-headers-4.8.0-58 4.8.0-58.63~16.04.1
linux-headers-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-headers-generic-hwe-16.04 4.8.0.58.29
linux-hwe-tools-4.8.0-58 4.8.0-58.63~16.04.1
linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-image-generic-hwe-16.04 4.8.0.58.29
linux-tools-4.8.0-58-generic 4.8.0-58.63~16.04.1
linux-tools-generic-hwe-16.04 4.8.0.58.29

For pulseaudio changes, I got this changelog:

--- Änderungen für pulseaudio (libpulsedsp libpulse-mainloop-glib0 pulseaudio 
pulseaudio-module-bluetooth pulseaudio-module-gconf pulseaudio-module-x11 
pulseaudio-module-zeroconf pulseaudio-utils) ---
Holen:1 http://changelogs.ubuntu.com pulseaudio 1:8.0-0ubuntu3.3 Changelog [216 
kB]
pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

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

Before, the P311 headset was connecting, after the update, it's not.
Looks like a regression.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bluetooth 5.37-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun 30 16:06:36 2017
InstallationDate: Installed on 2014-11-29 (944 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude E5510
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-58-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to xenial on 2016-06-15 (379 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 5C:AC:4C:F8:E1:98  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:2055 acl:26 sco:0 events:96 errors:0
TX bytes:3977 acl:28 sco:0 commands:62 errors:0

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


** Tags: amd64 apport-bug xenial

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

Title:
  [regression] bluetooth headset not connecting after regular update

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi, my bluetooth headset Arctic 

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

[Orkhan Guliyev]

Public bug reported:

Again.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun 30 17:59:34 2017
ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-06-03 (27 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: package libssl1.0.0:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in openssl package in Ubuntu:
  New

Bug description:
  Again.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 17:59:34 2017
  ErrorMessage: package libssl1.0.0:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-06-03 (27 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1700743] Re: incorrect /etc/adjtime

[Phillip Susi]

It happened before you upgraded to the fixed version.  Now that you have
the fixed version, it won't happen again.


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

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

Title:
  incorrect /etc/adjtime

Status in util-linux package in Ubuntu:
  Invalid

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

  I ran hwclock to sync them and got:

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 27 04:50:29 2017
  InstallationDate: Installed on 2015-11-18 (586 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (68 days ago)

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

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

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

[Kai-Heng Feng]

That's exactly the testing kernel built for - to test if software boost
performs well.

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

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

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

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1701563] Re: On Artful Kate crashes when run on Mir

[Alan Griffiths]

New behavior on Artful: calling mir_create_menu_window_spec() with
parent == nullptr

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

Title:
  On Artful Kate crashes when run on Mir

Status in qtubuntu package in Ubuntu:
  New

Bug description:
  $ sudo apt install miral-examples kate
  $ miral-app
  [in the app terminal] $ gdb kate

  Expect: kate runs
  Actual:

  Thread 1 "kate" received signal SIGABRT, Aborted.
  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
  58../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  (gdb) bt
  #0  0x725da77f in __GI_raise (sig=sig@entry=6)
  at ../sysdeps/unix/sysv/linux/raise.c:58
  #1  0x725dc37a in __GI_abort () at abort.c:89
  #2  0x7fffe1463b78 in mir::require(bool) ()
  at ./src/include/common/mir/require.h:28
  #3  0x7fffe1463b78 in mir_create_menu_window_spec (connection=
  0x55959f40, width=640, height=480, parent=0x0, rect=0x7fffcb90, 
edge=mir_edge_attachment_any) at ./src/client/mir_surface_api.cpp:79
  #4  0x7fffe1716f31 in  ()
  at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #5  0x7fffe17180eb in  ()
  at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0x7fffe170506b in  ()
  at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #7  0x73f200c9 in QWindowPrivate::create(bool) ()
  at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  #8  0x746e5585 in QWidgetPrivate::create_sys(unsigned long long, 
bool, bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #9  0x746e4d7d in QWidget::create(unsigned long long, bool, bool) ()
  at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #10 0x746e51e9 in QWidget::winId() const ()
  at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

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

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

[Touch-packages] [Bug 1701563] [NEW] On Artful Kate crashes when run on Mir

[Alan Griffiths]

Public bug reported:

$ sudo apt install miral-examples kate
$ miral-app
[in the app terminal] $ gdb kate

Expect: kate runs
Actual:

Thread 1 "kate" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
58  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x725da77f in __GI_raise (sig=sig@entry=6)
at ../sysdeps/unix/sysv/linux/raise.c:58
#1  0x725dc37a in __GI_abort () at abort.c:89
#2  0x7fffe1463b78 in mir::require(bool) ()
at ./src/include/common/mir/require.h:28
#3  0x7fffe1463b78 in mir_create_menu_window_spec (connection=
0x55959f40, width=640, height=480, parent=0x0, rect=0x7fffcb90, 
edge=mir_edge_attachment_any) at ./src/client/mir_surface_api.cpp:79
#4  0x7fffe1716f31 in  ()
at /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
#5  0x7fffe17180eb in  ()
at /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
#6  0x7fffe170506b in  ()
at /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
#7  0x73f200c9 in QWindowPrivate::create(bool) ()
at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#8  0x746e5585 in QWidgetPrivate::create_sys(unsigned long long, bool, 
bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x746e4d7d in QWidget::create(unsigned long long, bool, bool) ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x746e51e9 in QWidget::winId() const ()
at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

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

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

Title:
  On Artful Kate crashes when run on Mir

Status in qtubuntu package in Ubuntu:
  New

Bug description:
  $ sudo apt install miral-examples kate
  $ miral-app
  [in the app terminal] $ gdb kate

  Expect: kate runs
  Actual:

  Thread 1 "kate" received signal SIGABRT, Aborted.
  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
  58../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  (gdb) bt
  #0  0x725da77f in __GI_raise (sig=sig@entry=6)
  at ../sysdeps/unix/sysv/linux/raise.c:58
  #1  0x725dc37a in __GI_abort () at abort.c:89
  #2  0x7fffe1463b78 in mir::require(bool) ()
  at ./src/include/common/mir/require.h:28
  #3  0x7fffe1463b78 in mir_create_menu_window_spec (connection=
  0x55959f40, width=640, height=480, parent=0x0, rect=0x7fffcb90, 
edge=mir_edge_attachment_any) at ./src/client/mir_surface_api.cpp:79
  #4  0x7fffe1716f31 in  ()
  at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #5  0x7fffe17180eb in  ()
  at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #6  0x7fffe170506b in  ()
  at 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so
  #7  0x73f200c9 in QWindowPrivate::create(bool) ()
  at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  #8  0x746e5585 in QWidgetPrivate::create_sys(unsigned long long, 
bool, bool) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #9  0x746e4d7d in QWidget::create(unsigned long long, bool, bool) ()
  at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #10 0x746e51e9 in QWidget::winId() const ()
  at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

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

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

[Touch-packages] [Bug 1576066] Re: 32bit glibc calls old socketcall() syscall, causing seccomp problems

[Michael Vogt]

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

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

** Also affects: glibc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: libseccomp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  32bit glibc calls old socketcall() syscall, causing seccomp problems

Status in glibc package in Ubuntu:
  Confirmed
Status in libseccomp package in Ubuntu:
  Confirmed
Status in glibc source package in Trusty:
  New
Status in libseccomp source package in Trusty:
  New
Status in glibc source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New

Bug description:
  Back in the day when Linux was created for i386, for who knows what
  reason, all socket calls were multiplexed through a single syscall
  API, socketcall().  This was a strange thing to do, but it probably
  made sense from the standpoint of the same part of the kernel handling
  all of those calls.

  It was realised a long time ago that this was a strange and suboptimal
  arrangement.

  By the time they got around to doing amd64 and other architectures,
  they fixed this arrangement and gave each socket call a separate
  syscall entry point.  32bit systems continued to do it this old way,
  however, multiplexing all calls through socketcall().

  This is a problem for seccomp.  If we want to allow a program to make
  casual use of the network, but not bind a listener socket, we cannot
  currently do that.  On 64bits we just filter out the bind() and
  listen() calls, but on 32bit, it's all the same syscall.

  The kernel people fixed this problem up last summer by introducing
  new, separate, syscall entries for each separate call.

http://patchwork.sourceware.org/patch/7679/

  The problem is that glibc in Y is still using the old socketcall()
  interface on i386.  It needs to be updated to use the new calls.

  A possible caveat is that this might create problems for running newer
  binaries on older kernels on i386 (as we sometimes do with builders)
  because they won't have the new syscalls.  A solution could involve
  checking for ENOSYS and trying again via the old route.

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

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

[Touch-packages] [Bug 1511824] Re: Can't login as ordinary user with lightdm

[George Vasileiou]

I had the same problem in elementary OS Loki. The same messages as it is
described above. Those bug was affecting my login time in the pantheon
graphical environment so I came out with a very quickie work - arround.
I edited and I delete the lines which have pam_kwallet.so and
pam_kwallet5.so. Make a backup before you try it.

/etc/pam.d/lightdm


#%PAM-1.0
authrequisite   pam_nologin.so
authsufficient  pam_succeed_if.so user ingroup nopasswdlogin
@include common-auth
authoptionalpam_gnome_keyring.so
authoptionalpam_kwallet.so
authoptionalpam_kwallet5.so
@include common-account
session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
#session requiredpam_loginuid.so
session requiredpam_limits.so
@include common-session
session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
session optionalpam_gnome_keyring.so auto_start
session optionalpam_kwallet.so auto_start
session optionalpam_kwallet5.so auto_start
session requiredpam_env.so readenv=1
session requiredpam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale
@include common-password


/etc/pam.d/lightdm-greeter
#%PAM-1.0
authrequiredpam_permit.so
authoptionalpam_gnome_keyring.so
authoptionalpam_kwallet.so
authoptionalpam_kwallet5.so
@include common-account
session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
session requiredpam_limits.so
@include common-session
session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
session optionalpam_gnome_keyring.so auto_start
session optionalpam_kwallet.so auto_start
session optionalpam_kwallet5.so auto_start
session requiredpam_env.so readenv=1
session requiredpam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale

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

Title:
  Can't login as ordinary user with lightdm

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I can't login as ordinary user rose with lightdm.
  It is an Ubuntu 15.04 for armv7l .
  At the beginning I saw the already reported issues with kwallet, which is not 
installed. I commented out the corresponding lines in. I have now:

  root@odroid6:~# cat /etc/pam.d/lightdm
  #%PAM-1.0
  auth requisite pam_nologin.so
  auth sufficient pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  auth optional pam_gnome_keyring.so
  #auth optional pam_kwallet.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  session required pam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optional pam_gnome_keyring.so auto_start
  #session optional pam_kwallet.so auto_start
  session required pam_env.so readenv=1
  session required pam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale
  @include common-password

  and

  root@odroid6:~# cat /etc/pam.d/lightdm-greeter
  #%PAM-1.0
  auth required pam_permit.so
  auth optional pam_gnome_keyring.so
  #auth optional pam_kwallet.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  session required pam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optional pam_gnome_keyring.so auto_start
  #session optional pam_kwallet.so auto_start
  session required pam_env.so readenv=1
  session required pam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale

  It seems that my password is accepted (login via ssh works perfectly),
  but with lightdm I get only a black screen with mouse cursor. Login as
  user odroid which is in group nopasswdlogin with lightdm works.

  After trying to login as user rose, I have to login with ssh and kill
  all processes owned by rose. At the end of /var/log/auth.log I see:

  Oct 28 19:34:17 odroid6 lightdm: pam_succeed_if(lightdm:auth): requirement 
"user ingroup nopasswdlogin" not met by user "rose"
  Oct 28 19:34:26 odroid6 lightdm: pam_unix(lightdm-greeter:session): session 
closed for user lightdm
  Oct 28 19:34:26 odroid6 lightdm: pam_unix(lightdm:session): session opened 
for user rose by (uid=0)
  Oct 28 19:34:26 odroid6 systemd-logind[651]: New session c8 of user rose.
  Oct 28 19:34:26 odroid6 systemd: pam_unix(systemd-user:session): session 
opened for user rose by (uid=0)
  Oct 28 19:35:10 odroid6 systemd-logind[651]: Removed session c6.
  Oct 28 19:35:10 odroid6 systemd: pam_unix(systemd-user:session): session 
closed for user lightdm

  

[Touch-packages] [Bug 1701298] Re: ssh_config should include /etc/ssh/ssh_config.d/* by default

[Erich E. Hoover]

@cjwatson, I've been getting my work into the habit of deploying Debian 
packages for all organization-wide system configuration files.  So, when I 
noticed the other day that openssh-client 7.3p1+ now supports include 
directives I put together a new package that gives all of our internal users 
no-login access to the systems that they need for their work.  The exact ".d" 
file I put together to do this is:
===
Match exec "getent hosts %h | grep -qE '^10\.10\.10\.'"
User root
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
IdentityFile /opt/insight/SLE-101_id_rsa
===
However, at the moment, for anyone to use this file I would need to modify 
/etc/ssh/ssh_config by adding "Include /etc/ssh/ssh_config.d/*".  While I can 
do that, I know that it's not generally recommended to have a package modify 
the config files of other packages.  So, ideally, the default ssh_config file 
would have an Include directive that allows me to simply place my ".d" file in 
the appropriate ".d" directory such that it automatically gets included 
whenever my custom package is installed.

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

Title:
  ssh_config should include /etc/ssh/ssh_config.d/* by default

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  It is not currently possible to deploy packages with system-specific SSH 
configuration settings without modifying the ssh_config file.  Ideally the 
default ssh_config file would simply contain:
  Include /etc/ssh/ssh_config.d/*
  as this would allow packages to deploy such settings without tampering with 
the main ssh_config file.

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Ubuntu Foundations Team Bug Bot]

The attachment "fix-1698287-for-totem-via-gstreamer-vaapi.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 libva in Ubuntu.
https://bugs.launchpad.net/bugs/1698287

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

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

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

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

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

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

  WORKAROUNDS:

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

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

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

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

[Touch-packages] [Bug 1675141] Re: lightdm crashed with SIGSEGV in munmap()

[corrado venturini]

corrado@corrado-art3:~/Documents$ ./inxi -Fx
System:Host: corrado-art3 Kernel: 4.11.0-9-generic x86_64 (64 bit gcc: 
6.3.0)
   Desktop: Gnome 3.24.2 (Gtk 3.22.15-0ubuntu2) Distro: Ubuntu Artful 
Aardvark (development branch)
Machine:   Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x UEFI: American 
Megatrends v: F3 date: 04/24/2013
CPU:   Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB
   flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13567
   clock speeds: max: 3400 MHz 1: 3400 MHz 2: 2720 MHz 3: 1712 MHz 4: 
3400 MHz
Graphics:  Card: Intel 4th Generation Core Processor Family Integrated Graphics 
Controller bus-ID: 00:02.0
   Display Server: x11 (X.Org 1.19.3) drivers: modesetting (unloaded: 
fbdev,vesa)
   Resolution: 1680x1050@59.88hz
   OpenGL: renderer: Mesa DRI Intel Haswell version: 4.5 Mesa 17.1.2 
Direct Render: Yes
Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
   driver: snd_hda_intel bus-ID: 00:1b.0
   Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller
   driver: snd_hda_intel bus-ID: 00:03.0
   Sound: Advanced Linux Sound Architecture v: k4.11.0-9-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
   driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0
   IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 
94:de:80:7e:90:a7
Drives:HDD Total Size: 1000.2GB (1.5% used)
   ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB
Partition: ID-1: / size: 32G used: 6.1G (21%) fs: ext4 dev: /dev/sda8
   ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C
   Fan Speeds (in rpm): cpu: N/A
Info:  Processes: 225 Uptime: 1:52 Memory: 1020.8/7861.1MB Init: systemd 
runlevel: 5 Gcc sys: N/A
   Client: Shell (bash 4.4.121) inxi: 2.3.22 
corrado@corrado-art3:~/Documents$

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

Title:
  lightdm crashed with SIGSEGV in munmap()

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  didn't notice anything except that message that I had a bug to
  report...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.21.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar 22 20:03:09 2017
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2017-03-16 (6 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170316)
  LightdmConfig:
   [Seat:*]
   autologin-guest=false
   autologin-user=ben
   autologin-user-timeout=0
  ProcCmdline: lightdm --session-child 13 16
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   munmap () at ../sysdeps/unix/syscall-template.S:84
   _dl_unmap_segments (l=l@entry=0x55eb13fedb40) at ./dl-unmap-segments.h:32
   _dl_unmap (map=map@entry=0x55eb13fedb40) at ../sysdeps/x86_64/tlsdesc.c:140
   _dl_close_worker (map=map@entry=0x55eb13fedb40, force=force@entry=false) at 
dl-close.c:678
   _dl_close_worker (force=false, map=0x55eb13fedb40) at dl-close.c:125
  Title: lightdm crashed with SIGSEGV in munmap()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

[Esokrates]

Could you please post the patch for
http://people.canonical.com/~khfeng/lp1654448-2/ ?

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

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

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

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

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

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-keyring not unlocked on boot

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

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

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

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

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

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

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

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

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

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

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

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-keyring not unlocked on boot

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

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

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

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

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

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

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

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

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

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

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

[Esokrates]

Kai, http://people.canonical.com/~khfeng/lp1654448-2/ does not have the
hiss :-).

Would compensating the lower output volume with setting pulseaudio to
100+% make the quality worse? Does setting pulseaudio to e.g. 130%
disort the quality?

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

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

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

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1701297] Re: NTP reload failure (unable to read library) on overlayfs

[Andres Rodriguez]

@Tyler,

That's is correct, MAAS 2.2.0+ sends the apparmor=0 for the ephemeral
environments.

That said, however, this affects else who is not using 2.2 (which in
fact, affects customers who are still in 2.1). Also, based on my
testing, it seems that when using hwe-16.04 kernel this doesn't happen,
but it does with the ga-16.04 kernel.

** Summary changed:

- NTP reload failure (causing deployment failures with MAAS)
+ NTP reload failure (unable to read library) on overlayfs

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

Title:
  NTP reload failure (unable to read library) on overlayfs

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

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

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

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

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

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

[Touch-packages] [Bug 1701298] Re: ssh_config should include /etc/ssh/ssh_config.d/* by default

[Colin Watson]

There are already bugs about an Include directive in sshd, so please
don't file more.  Also, it isn't really necessary to re-file this in
Debian since I follow both trackers.

Erich, could you give an example of the sort of changes you'd like to be
able to make in a .d directory?  Are you talking about site-local
changes, or things that might go into a distribution?

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

Title:
  ssh_config should include /etc/ssh/ssh_config.d/* by default

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  It is not currently possible to deploy packages with system-specific SSH 
configuration settings without modifying the ssh_config file.  Ideally the 
default ssh_config file would simply contain:
  Include /etc/ssh/ssh_config.d/*
  as this would allow packages to deploy such settings without tampering with 
the main ssh_config file.

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

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

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

[M. Jensen.]

+1 Thanks, for briging this important security information to me. I'll
remove the motd-file, to prevent tracking and the likes.

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

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

Status in base-files package in Ubuntu:
  Opinion

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Jeremy Bicha]

Khurshid and Mardy, thank you very much for your feedback.

libaccounts-glib, libsignon-glib, signon, signon-plugin-oauth, signon-
plugin-password, telepathy-accounts-glib (and a few more with more
obvious K sounding names) are being kept because they are used in KDE
Plasma.

Khurshid, is that sufficient for what you need? Or do you also need
account-plugins?

Mardy, I don't think there's a problem with ubports maintained stuff re-
entering Ubuntu if it's maintained. It looks to me like ubports is
currently focused on Xenial and PPAs which is a good approach too.

The list of Unity8 related removals is much longer (see xnox's estimate
in his merge proposal). This bug focuses on UOA stuff which does end up
including Unity8 too.

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qtpurchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  address-book-app
  address-book-service
  dialer-app
  messaging-app
  telephony-service
  tone-generator
  ubuntu-system-settings
  buteo-sync-plugins-contacts-google
  camera-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  ubuntu-experience-tests
  unity-scopes-shell
  unity8

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+subscriptions

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

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Alberto Mardegan]

As far as I can see, there is no plan to remove these packages (please confirm, 
Jeremy). And indeed I'm going to maintain these packages in the future as well:
  libsignon-{qt,glib}, signond, libaccounts-{qt,glib}

I'm also willing to maintain other packages mentioned in this bug, such
as online-accounts-api and ubuntu-system-settings-online-accounts, but
since these are effectively used only on the phone, I'll be maintaining
them as part of the ubports project and I have no objection on removing
them from the archive.

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qtpurchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  address-book-app
  address-book-service
  dialer-app
  messaging-app
  telephony-service
  tone-generator
  ubuntu-system-settings
  buteo-sync-plugins-contacts-google
  camera-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  ubuntu-experience-tests
  unity-scopes-shell
  unity8

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+subscriptions

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

Here's my first attempt at a fix for totem. Although fixing this bug in
totem then triggers corruption (bug 1701463) as well as higher CPU, so
still needs more verification to see if the higher CPU is just a side-
effect of poor plugin choice or related to the corruption...

** Patch added: "fix-1698287-for-totem-via-gstreamer-vaapi.patch"
   
https://bugs.launchpad.net/totem/+bug/1698287/+attachment/4906439/+files/fix-1698287-for-totem-via-gstreamer-vaapi.patch

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

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

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

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

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

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

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

  WORKAROUNDS:

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

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

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

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

[Touch-packages] [Bug 1701493] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: Paket libssl1.0.0:i386 ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (mo

[Paul Ecker]

Public bug reported:

Description:Ubuntu 16.04.2 LTS
Release:16.04

paul@paul-desktop:~$ apt-cache policy libssl1.0.0:i386 1.0.2g-1ubuntu4.6
libssl1.0.0:i386:
  Installiert:   1.0.2g-1ubuntu4.6
  Installationskandidat: 1.0.2g-1ubuntu4.8
  Versionstabelle:
 1.0.2g-1ubuntu4.8 500
500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
 *** 1.0.2g-1ubuntu4.6 500
500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages
100 /var/lib/dpkg/status
 1.0.2g-1ubuntu4 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main i386 Packages
N: Paket 1.0.2g-1ubuntu4.6 kann nicht gefunden werden.
N: Mittels des Musters »1.0.2g-1ubuntu4.6« konnte kein Paket gefunden werden.
N: Mittels regulärem Ausdruck »1.0.2g-1ubuntu4.6« konnte kein Paket gefunden 
werden.


I'm not able to install any update via the softwareupdater

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Thu Jun 29 13:44:22 2017
ErrorMessage: Paket libssl1.0.0:i386 ist nicht bereit zur Konfiguration  kann 
nicht konfiguriert werden (momentaner Status »half-installed«)
InstallationDate: Installed on 2016-10-28 (245 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
Paket libssl1.0.0:i386 ist nicht bereit zur Konfiguration  kann nicht 
konfiguriert werden (momentaner Status »half-installed«)
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade:
  Paket libssl1.0.0:i386 ist nicht bereit zur Konfiguration  kann nicht
  konfiguriert werden (momentaner Status »half-installed«)

Status in openssl package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  paul@paul-desktop:~$ apt-cache policy libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  libssl1.0.0:i386:
Installiert:   1.0.2g-1ubuntu4.6
Installationskandidat: 1.0.2g-1ubuntu4.8
Versionstabelle:
   1.0.2g-1ubuntu4.8 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
   *** 1.0.2g-1ubuntu4.6 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.0.2g-1ubuntu4 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  N: Paket 1.0.2g-1ubuntu4.6 kann nicht gefunden werden.
  N: Mittels des Musters »1.0.2g-1ubuntu4.6« konnte kein Paket gefunden werden.
  N: Mittels regulärem Ausdruck »1.0.2g-1ubuntu4.6« konnte kein Paket gefunden 
werden.

  
  I'm not able to install any update via the softwareupdater

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 29 13:44:22 2017
  ErrorMessage: Paket libssl1.0.0:i386 ist nicht bereit zur Konfiguration  kann 
nicht konfiguriert werden (momentaner Status »half-installed«)
  InstallationDate: Installed on 2016-10-28 (245 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.6 failed to install/upgrade: 
Paket libssl1.0.0:i386 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:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1701493/+subscriptions

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

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

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

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

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

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:
  there is some 200+gb being used on drive  someone eplainme this please

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Thu Jun 29 22:13:49 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386 (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/1701488/+subscriptions

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

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

[Orkhan Guliyev]

Public bug reported:

Problem after sleep mode.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun 30 12:09:51 2017
ErrorMessage: пакет libssl1.0.0:amd64 не готов к настройке  настройка 
невозможна (текущее состояние: «half-installed»)
InstallationDate: Installed on 2017-06-03 (26 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: lib/x86_64
  -linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so
  usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so
  usr/share/doc/libssl1.0.0/changelog.Debian.gz] failed to
  install/upgrade: пакет libssl1.0.0:amd64 не готов к настройке
  настройка невозможна (текущее состояние: «half-installed»)

Status in openssl package in Ubuntu:
  New

Bug description:
  Problem after sleep mode.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.6 [modified: 
lib/x86_64-linux-gnu/libcrypto.so.1.0.0 lib/x86_64-linux-gnu/libssl.so.1.0.0 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/lib4758cca.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libaep.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libatalla.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcapi.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libchil.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libcswift.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgmp.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libgost.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libnuron.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libpadlock.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libsureware.so 
usr/lib/x86_64-linux-gnu/openssl-1.0.0/engines/libubsec.so 
usr/share/doc/libssl1.0.0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 30 12:09:51 2017
  ErrorMessage: пакет libssl1.0.0:amd64 не готов к настройке  настройка 
невозможна (текущее состояние: «half-installed»)
  InstallationDate: Installed on 2017-06-03 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[dan formhals]

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

Public bug reported:

there is some 200+gb being used on drive  someone eplainme this please

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic i686
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
Date: Thu Jun 29 22:13:49 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-29 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386 (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: apport-package i386 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/1701488

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:
  there is some 200+gb being used on drive  someone eplainme this please

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic i686
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: i386
  Date: Thu Jun 29 22:13:49 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-29 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386 (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/1701488/+subscriptions

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

[Touch-packages] [Bug 1604583] Re: Crash occurred while system was unattended, installing the KDE before erradicating Gnome - 20160719-1239

[Rik Mills]

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

** This bug is no longer a duplicate of bug 1588346
   package kde-config-telepathy-accounts (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
account-plugin-google 0.12+16.04.20160126-0ubuntu1
** This bug has been marked a duplicate of bug 1451728
   [master] kde-config-telepathy-accounts package install error

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

Title:
  Crash occurred while system was unattended, installing the KDE before
  erradicating Gnome - 20160719-1239

Status in account-plugins package in Ubuntu:
  New
Status in ktp-accounts-kcm package in Ubuntu:
  New

Bug description:
  Brief description of incident:
  As the default Gnome Desktop Environment was still present and active, the 
KDE was being installed using 'apt-get install kubuntu-desktop'. Upon returning 
to a sleeping screen, tapping the KB/Mouse, the system woke the screen only to 
display a dialog box triggered to generate a bug report for whatever error 
occurred during the installation process.

  System and Package details:
  Description: Ubuntu 16.04 LTS
  Release: 16.04
  Package ID:  kubuntu-desktop
  Package: Kubuntu Plasma Desktop/Netbook system
Installed: 1.338
Candidate: 1.338
Version table:
   *** 1.338 500
   500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 
Packages
   100 /var/lib/dpkg/status

  Steps to reproduce:
  1) Boot to the desktop of Ubuntu 16.04 with the default GNOME desktop 
environment
  2) Open a terminal window
  3) Type the following and press the Enter key to submit the command:
  sudo apt-get install kubuntu-desktop

  Expected results:
  KDE package should install without incident.

  Actual results:
  KDE package installed, and is still installing, but generated errors 
triggering the automated creation of this bug report.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kde-config-telepathy-accounts (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Jul 19 12:19:46 2016
  DuplicateSignature:
   package:kde-config-telepathy-accounts:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
account-plugin-google 0.12+16.04.20160126-0ubuntu1
  InstallationDate: Installed on 2016-06-30 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: ktp-accounts-kcm
  Title: package kde-config-telepathy-accounts (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/accounts/services/google-im.service', which is also in package 
account-plugin-google 0.12+16.04.20160126-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Olivier Tilloy]

For info, I've tested a build of chromium-browser (dev branch) with
clang-4.0 from xenial-proposed, and that works well.

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

Title:
  Backport packages for 16.04.3 HWE stack

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

Bug description:
  [Impact]

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

  Revert changes to use debhelper10.

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

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

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

  [Test case]

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

  [Regression potential]

  zesty hasn't blown up

  [Other information]

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

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

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

[Touch-packages] [Bug 1701475] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Apport retracing service]

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

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 #1676380, 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 1676380
   Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures

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

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

Status in cups package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CupsErrorLog:
   
  Date: Thu Jun 29 20:56:45 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-06-24 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer TravelMate 6592
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/08
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.54
  dmi.board.name: TravelMate 6592
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV1.54:bd11/21/08:svnAcer:pnTravelMate6592:pvrPSMBOU-1234567:rvnAcer:rnTravelMate6592:rvrNotApplicable:cvnAcer:ct1:cvrN/A:
  dmi.product.name: TravelMate 6592
  dmi.product.version: PSMBOU-1234567
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1701475] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[philip]

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

Public bug reported:

Ubuntu 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CupsErrorLog:
 
Date: Thu Jun 29 20:56:45 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-06-24 (6 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Acer TravelMate 6592
Papersize: a4
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/08
dmi.bios.vendor: Acer
dmi.bios.version: V1.54
dmi.board.name: TravelMate 6592
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAcer:bvrV1.54:bd11/21/08:svnAcer:pnTravelMate6592:pvrPSMBOU-1234567:rvnAcer:rnTravelMate6592:rvrNotApplicable:cvnAcer:ct1:cvrN/A:
dmi.product.name: TravelMate 6592
dmi.product.version: PSMBOU-1234567
dmi.sys.vendor: Acer

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

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

Status in cups package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CupsErrorLog:
   
  Date: Thu Jun 29 20:56:45 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-06-24 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer TravelMate 6592
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-83-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/08
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.54
  dmi.board.name: TravelMate 6592
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV1.54:bd11/21/08:svnAcer:pnTravelMate6592:pvrPSMBOU-1234567:rvnAcer:rnTravelMate6592:rvrNotApplicable:cvnAcer:ct1:cvrN/A:
  dmi.product.name: TravelMate 6592
  dmi.product.version: PSMBOU-1234567
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1638902] Re: [2.27 Regression] gold internal error in fix_errata on aarch64-linux-gnu

[LocutusOfBorg]

ok, now also ghc fails on arm64 for the same issue

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

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

Title:
   [2.27 Regression] gold internal error in fix_errata on aarch64-linux-
  gnu

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  Confirmed

Bug description:
  seen with binutils from the 2.27 branch:

  $ sh link.sh 
  ld.gold: internal error in fix_errata, at ../../gold/aarch64.cc:1960

  This works with the BFD linker, or when dropping the --fix-
  cortex-a53-843419 option.

  The test cases comes from the build of the gitit package on Ubuntu 16.10,
  see https://launchpad.net/ubuntu/+source/gitit/0.12.1.1+dfsg-2build7

  The package built successfully with binutils 2.26.1

  test case at
  http://people.canonical.com/~doko/tmp/tst.tar.xz

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Bug Watch Updater]

** Changed in: totem
   Status: Unknown => Incomplete

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

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

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

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

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

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

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

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

  WORKAROUNDS:

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

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

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

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

[Touch-packages] [Bug 1699928] Re: Please delete obsolete android binaries

[Łukasz Zemczak]

With that said I think we all agree that goget-ubuntu-touch's sources
and binaries can be removed from the artful archive.

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

Title:
  Please delete obsolete android binaries

Status in android-tools package in Ubuntu:
  Fix Released
Status in goget-ubuntu-touch package in Ubuntu:
  New
Status in phablet-tools package in Ubuntu:
  New

Bug description:
  New Request
  ===
  Please remove phablet-tools and goget-ubuntu-touch and all their binaries 
from artful. goget-ubuntu-touch does not build in zesty or artful and I don't 
think anyone is interested in maintaining it in Ubuntu at this time. It can be 
re-added later if someone volunteers.

  phablet-tools also fails to build (pep8) but I don't think it's very
  useful without ubuntu-device-do and ubuntu-device-flash.

  Background
  ==
  Since Canonical's Ubuntu phone project is ending and no one has stepped up to 
maintain Ubuntu's android-tools fork, we are syncing the Android stack from 
Debian.

  This benefits users by allowing them to use the latest adb and
  fastboot instead of an old copy.

  There are a few obsolete binaries that need to be removed to make this
  happen, because Debian's android-tools is only built for a limited set
  of supported architectures (not ppc64el or s390x).

  
  Original Report
  ===
  Please delete these binaries:

  android-tools-fsutils for ppc64el and s390x
  ubuntu-device-do for ppc64el
  ubuntu-device-flash for ppc64el

  These are listed on update_excuses.html or update_output.txt

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

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

[Touch-packages] [Bug 1701298] Re: ssh_config should include /etc/ssh/ssh_config.d/* by default

[ChristianEhrhardt]

Hi Erich,
I agree that would be a nice change to have, but I got puzzled checking the 
details.

In general it seemed to requires 7.3p1 it seems: => 
https://bugzilla.mindrot.org/show_bug.cgi?id=1585.
Therefore e.g. in Xenial I wondered to find nothing about the Include statement 
but that was 7.2.
But all later versions are ok, so there it makes absolutely sense.

It is already done for the user side of the config in:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/739495

But looking deeper I realized that this is only implemented by Upstream
for the client part (ssh) but not the sshd server (at least trusting the
man pages updated with the referred upstream change).

That said I'd have to ask you for two thing:
1. This bug is present in Debian too and we carry next to no delta. So it would 
be best fixed in Debian, and then Ubuntu will pick it up on the next merge. 
Would you mind filing a bug with Debian please?
2. Also since at least according to my sniff check it seems the upstream sshd 
doesn't have an Include directive you might file a bug there as well and link 
it here and in the Debian bug.

For now confirming the idea and setting wishlist as for all feature
requests.

** Bug watch added: OpenSSH Portable Bugzilla #1585
   https://bugzilla.mindrot.org/show_bug.cgi?id=1585

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

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  ssh_config should include /etc/ssh/ssh_config.d/* by default

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  It is not currently possible to deploy packages with system-specific SSH 
configuration settings without modifying the ssh_config file.  Ideally the 
default ssh_config file would simply contain:
  Include /etc/ssh/ssh_config.d/*
  as this would allow packages to deploy such settings without tampering with 
the main ssh_config file.

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

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

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

** Description changed:

  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:
  
  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)
  
  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)
  
  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0
  
+ WORKAROUNDS:
+ 
+  * Use weston instead of gnome-shell; or
+  * $ env -uDISPLAY totem ...
+  * $ mpv --hwdec --opengl-backend=wayland ...
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:
  
  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)
  
  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)
  
  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0
  
  WORKAROUNDS:
  
-  * Use weston instead of gnome-shell; or
-  * $ env -uDISPLAY totem ...
-  * $ mpv --hwdec --opengl-backend=wayland ...
+  * Use weston instead of gnome-shell; or
+  * $ env -uDISPLAY totem ...# but see bug 1701463
+  * $ mpv --hwdec --opengl-backend=wayland ...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || 

[Touch-packages] [Bug 1701290] Re: package libhx509-5-heimdal:i386 7.1.0+dfsg-9ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

[ChristianEhrhardt]

Hi Jason,
your system wants to make you aware that some of your packages fail to 
install/upgrade.

In general for the class of errors it reported I recommend following [1]
but adapted for the offending package in your case which is
"libhx509-5-heimdal".

But then since you report "No idea what Im supposed to put here, Ubuntu asked 
me to report the error, so I did." you might (no offense please) not be the 
most experienced admin. And heimdal is often not needed, you might also 
consider checking what you installed that caused to install it in the first 
place and just get rid of it. For example I do so much on my systems and I 
checked it is not in stalled on any of them.
I see you did the install pulling it in on "Start-Date: 2017-06-19  01:31:40". 
I'm not sure what you installed there - wine maybe, but I have that as well and 
still no heimdal.

Anyway following [1] should resolve it - the "do you really need2 was
only a suggestion.

[1]: https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a
-very-bad-inconsistent-state-error

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

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

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

Status in heimdal package in Ubuntu:
  Incomplete

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

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

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

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

[Touch-packages] [Bug 496320] Re: The package libreadline5-dev should be rebuild with new debhelper to get trigger support

[Bug Watch Updater]

** Changed in: readline5 (Debian)
   Status: New => Fix Released

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

Title:
  The package libreadline5-dev should be rebuild with new debhelper to
  get trigger support

Status in readline5 package in Ubuntu:
  Triaged
Status in readline5 package in Debian:
  Fix Released

Bug description:
  LAST BUILD TESTED: 5.2-7build1

  Well the summary basically says it all. On karmic when I install
  libreadline5-dev by way of "sudo apt-get build-dep liferea" I see
  this:

  =
  (...)
  Setting up libreadline5-dev (5.2-6) ...
  Ignoring install-info called from maintainer script
  The package libreadline5-dev should be rebuild with new debhelper to get 
trigger support
  Ignoring install-info called from maintainer script
  The package libreadline5-dev should be rebuild with new debhelper to get 
trigger support
  (...)
  =

  lsb_release -rd
  Description:Ubuntu 9.10
  Release:9.10

  apt-cache policy libreadline5-dev
    Installed: 5.2-6
    Candidate: 5.2-6
    Version table:
   *** 5.2-6 0
  500 http://de.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: i386
  Date: Sun Dec 13 22:58:27 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: nvidia
  Package: libreadline5-dev 5.2-6
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic-pae
  SourcePackage: readline5
  Uname: Linux 2.6.31-16-generic-pae i686

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

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

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

[Kai-Heng Feng]

Here you go:

http://people.canonical.com/~khfeng/lp1654448-2/

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

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

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

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

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

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

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

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

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

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

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

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

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