[Touch-packages] [Bug 1764945] [NEW] package dbus 1.10.6-1ubuntu3.3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Alessander Botti Benevides]

Public bug reported:

Upgrade from 14.04 to 16.04.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.6-1ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Tue Apr 17 21:41:34 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
InstallationDate: Installed on 2015-10-05 (925 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: dbus
Title: package dbus 1.10.6-1ubuntu3.3 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: Upgraded to xenial on 2018-04-18 (0 days ago)

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

Title:
  package dbus 1.10.6-1ubuntu3.3 failed to install/upgrade: sub-processo
  script post-installation instalado retornou estado de saída de erro 1

Status in dbus package in Ubuntu:
  New

Bug description:
  Upgrade from 14.04 to 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Tue Apr 17 21:41:34 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2015-10-05 (925 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: dbus
  Title: package dbus 1.10.6-1ubuntu3.3 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
  UpgradeStatus: Upgraded to xenial on 2018-04-18 (0 days ago)

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

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

[Touch-packages] [Bug 1764946] [NEW] package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[Alessander Botti Benevides]

Public bug reported:

Upgrade from 14.04 to 16.04.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sysv-rc 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Tue Apr 17 21:22:39 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
InstallationDate: Installed on 2015-10-05 (925 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: sysvinit
Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
UpgradeStatus: Upgraded to xenial on 2018-04-18 (0 days ago)

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

Title:
  package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in sysvinit package in Ubuntu:
  New

Bug description:
  Upgrade from 14.04 to 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Tue Apr 17 21:22:39 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2015-10-05 (925 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: Upgraded to xenial on 2018-04-18 (0 days ago)

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

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

[Touch-packages] [Bug 1764628] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From sthou...@in.ibm.com 2018-04-18 01:24 EDT---
(In reply to comment #13)
> There seems to be no reason for
> https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 to fix
> this bug, since that is a targeted bugfix; and I understand your bug report
> to be asking if it's reproducible with this version, rather than telling
> that it is not.
>
> What are the values you expect in the output of lscpu for the "Hypervisor
> vendor" and "Virtualization type" fields that you highlight?  In what
> upstream version of util-linux is this known to be fixed?

We have not seen this issue in 
https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 version.
So we could like to know if you could include this version in 16.04.04 Ubuntu 
version..

The expected value is

Hypervisor vendor:   KVM
Virtualization type: para

root@guest:~/util-linux# ./lscpu
Architecture:ppc64le
Byte Order:  Little Endian
CPU(s):  2
On-line CPU(s) list: 0,1
Thread(s) per core:  2
Core(s) per socket:  1
Socket(s):   1
NUMA node(s):1
Model:   2.2 (pvr 004e 1202)
Model name:  POWER8 (architected), altivec supported
Hypervisor vendor:   KVM
Virtualization type: para
L1d cache:   32K
L1i cache:   32K
NUMA node0 CPU(s):   0,1

We downloaded the below upstream code and did not see the issue.

https://github.com/Distrotech/util-linux

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1


   
  Stack trace output:
   no
   
  Oops output:
   no
   

  
  We test what is coming along with distro. If you are not able to see issue 
with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can 
we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions

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

Re: [Touch-packages] [Bug 1764725] Re: Je n'ai plus de son sous ubuntu

[thiltges]

Quand j'ouvre la boite des parametres "son" je vois qu'il n'y a rien 
dans le pavé "jouer le son à travers de :" donc il ne connait pas le 
pilote de ma carte Realtek

Bonne journée

René


Le 17/04/2018 à 14:34, dino99 a écrit :
> Voir thes parametres de son dans le tableau de bord (icone coin droit)
> et vérifier que le curseur n'est pas sur 0 (muet) et/ou faire les tests
> de sortie son (via les icones)
>
> https://help.ubuntu.com/community/Sound
>
> https://wiki.ubuntu.com/Sound
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>
> ** Package changed: xorg (Ubuntu) => pulseaudio (Ubuntu)
>

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

Title:
  Je n'ai plus de son sous ubuntu

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  j'ai du son sous windows mais pas sous ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Apr 17 14:03:58 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV635 [Radeon HD 3650/3750/4570/4580] 
[1002:9598] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RV635 [Radeon HD 3650/3750/4570/4580] 
[1043:9010]
  InstallationDate: Installed on 2018-02-20 (55 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: HP-Pavilion FZ061AA-ABF a6575.fr
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=95cef207-c8c3-49b6-9776-6f663aa4997a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.11
  dmi.board.name: Boston
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.11:bd07/15/2008:svnHP-Pavilion:pnFZ061AA-ABFa6575.fr:pvr:rvnMSI:rnBoston:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: FZ061AA-ABF a6575.fr
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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 17 12:05:55 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1528195] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no pacote libjpeg-turbo-progs

[Jarno Suni]

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

** This bug is no longer a duplicate of bug 1527455
   package libjpeg-progs (not installed) failed to install/upgrade: försöker 
skriva över "/usr/share/man/man1/djpeg.1.gz" som också finns i paketet 
libjpeg-turbo-progs 1.3.0-0ubuntu2
** This bug has been marked a duplicate of bug 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar
  sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no
  pacote libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  Não sei...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  Date: Mon Dec 21 09:57:10 2015
  ErrorMessage: a tentar sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que 
também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2015-10-30 (51 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.1.5
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar 
sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no pacote 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1516242] Re: dpkg: error al procesar el archivo /var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack): intentando sobreescribir `/usr/share/man/man1/djpeg.1

[Jarno Suni]

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

** This bug has been marked a duplicate of bug 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  dpkg: error al procesar el archivo /var/cache/apt/archives/libjpeg-
  progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):  intentando sobreescribir
  `/usr/share/man/man1/djpeg.1.gz', que está también en el paquete
  libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  the mfollowing line appears when trying to upgrade

  
  dpkg: error al procesar el archivo 
/var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):
   intentando sobreescribir `/usr/share/man/man1/djpeg.1.gz', que está también 
en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.2.0-19.23-lowlatency 4.2.6
  Uname: Linux 4.2.0-19-lowlatency x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 14 14:25:34 2015
  InstallationDate: Installed on 2012-02-27 (1355 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: libjpeg8-empty
  UpgradeStatus: Upgraded to xenial on 2015-11-08 (6 days ago)

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

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

[Touch-packages] [Bug 1571195] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2

[Jarno Suni]

I think these are duplicates of each other despite the different 
libjpeg-turbo-progs version:
Bug #1550124

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-
  progs 1.3.0-0ubuntu2

Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  apt-cache policy libjpeg-progs
  libjpeg-progs:
Installed: 8c-2ubuntu8
Candidate: 1:9b-1
Version table:
   1:9b-1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   *** 8c-2ubuntu8 100
  100 /var/lib/dpkg/status

  
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 16 15:36:52 2016
  ErrorMessage: trying to overwrite '/usr/bin/rdjpgcom', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2014-10-21 (542 days ago)
  InstallationMedia:
   
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2
  UpgradeStatus: Upgraded to xenial on 2016-04-16 (0 days ago)

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

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

[Touch-packages] [Bug 1576937] Re: trying to overwrite '/usr/bin/rdjpgcom'

[Jarno Suni]

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

** This bug has been marked a duplicate of bug 1571195
   package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.3.0-0ubuntu2

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

Title:
  trying to overwrite '/usr/bin/rdjpgcom'

Status in libjpeg-turbo package in Ubuntu:
  New
Status in libjpeg9 package in Ubuntu:
  New

Bug description:
  Seen while upgrading from trusty to xenial:

  Unpacking libjpeg-progs (1:9b-1) over (8c-2ubuntu8) ...
  dpkg: error processing archive 
/mnt/ubuntu/pool/universe/libj/libjpeg9/libjpeg-progs_9b-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/rdjpgcom', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  Errors were encountered while processing:
   /mnt/ubuntu/pool/universe/libj/libjpeg9/libjpeg-progs_9b-1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-turbo-progs 1.3.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 30 00:43:24 2016
  InstallationDate: Installed on 2012-10-18 (1290 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: libjpeg-turbo
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (0 days ago)

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

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

[Touch-packages] [Bug 1701161] Re: black terminal

[Launchpad Bug Tracker]

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

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

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

Title:
  black terminal

Status in xorg package in Ubuntu:
  Expired

Bug description:
  my terminal becoms black all

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jun 29 12:32:32 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fdd0]
  InstallationDate: Installed on 2016-10-16 (255 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  MachineType: TOSHIBA Satellite L740
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5c492036-60d3-4079-8608-60181e27aac2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.50:bd04/12/2012:svnTOSHIBA:pnSatelliteL740:pvrPSK6XL-00C002:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L740
  dmi.product.version: PSK6XL-00C002
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Jun 29 11:43:33 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 760 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Touch-packages] [Bug 1702140] Re: freeze system again adn again

[Launchpad Bug Tracker]

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

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

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

Title:
  freeze system again adn again

Status in xorg package in Ubuntu:
  Expired

Bug description:
  every three and four hours system will be freeze. i need help

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jul  3 22:48:38 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-83-generic, x86_64: installed
   nvidia-340, 340.102, 4.4.0-83-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF119M [GeForce 410M] [10de:1055] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF119M [GeForce 410M] [104d:908b]
  InstallationDate: Installed on 2017-06-30 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Sony Corporation VPCEH25EN
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=53b92317-9503-44fe-bd39-9bbb573646ad ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0190Z9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0190Z9:bd11/17/2011:svnSonyCorporation:pnVPCEH25EN:pvrC105Z9ZK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEH25EN
  dmi.product.version: C105Z9ZK
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81+git20170630.3095cc8e-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
17.1.4~git20170629+17.1.03a0fdbd-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
17.1.4~git20170629+17.1.03a0fdbd-0ubuntu0ricotz~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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.8.99+git20170208.1351e48e-0ubuntu0ricotz2~xenial
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170208.e4fe79cf-0ubuntu0ricotz~xenial
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git20170208.1516d35b-0ubuntu0ricotz~xenial
  xserver.bootTime: Mon Jul  3 22:23:30 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest

[Steve Langasek]

There seems to be no reason for https://launchpad.net/ubuntu/+source
/util-linux/2.27.1-6ubuntu3.5 to fix this bug, since that is a targeted
bugfix; and I understand your bug report to be asking if it's
reproducible with this version, rather than telling that it is not.

What are the values you expect in the output of lscpu for the
"Hypervisor vendor" and "Virtualization type" fields that you highlight?
In what upstream version of util-linux is this known to be fixed?

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

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1


   
  Stack trace output:
   no
   
  Oops output:
   no
   

  
  We test what is coming along with distro. If you are not able to see issue 
with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can 
we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions

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

[Touch-packages] [Bug 1702347] Re: Graphical glitches in screen by default on 17.10 & 18.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Graphical glitches in screen by default on 17.10 & 18.04

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.10 development branch

  updated and dist-upgraded on 4 july 2017

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

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

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

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

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

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

[Touch-packages] [Bug 1550124] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1

[Jarno Suni]

Why would you want to install both libjpeg-progs and libjpeg-turbo-progs? 
"apt-cache depends libjpeg-progs" tells they conflict and replace each other.

I noticed similar issue after upgrading from Trusty to Xenial. Both packages 
were installed. I resolved that by purging libjpeg-progs. I did not want to 
purge libjpeg-turbo-progs, because jhead depends on it and I wanted to keep it. 
I had no problem by purging libjpeg-progs by apt, but some have had and here is 
related post:
https://askubuntu.com/q/766929/21005

BTW what is libjpeg8-empty? 
$ apt-cache policy libjpeg8-empty 
N: Unable to locate package libjpeg8-empty

I see similar bugs
Bug #1576010
Bug #1559754 
Bug #1576937
Bug #1571195
Bug #1527455
Bug #1516242


** Tags added: package-conflict

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-
  progs 1.4.2-0ubuntu1

Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  update failed with this.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Feb 22 20:02:43 2016
  ErrorMessage: trying to overwrite '/usr/bin/rdjpgcom', which is also in 
package libjpeg-turbo-progs 1.4.2-0ubuntu1
  InstallationDate: Installed on 2012-09-23 (1251 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 
1.4.2-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764928] [NEW] Please document apt-daily

[madumlao]

Public bug reported:

The following systemd services are installed along with apt:

/lib/systemd/system/apt-daily.timer
/lib/systemd/system/apt-daily-upgrade.timer
/lib/systemd/system/apt-daily-upgrade.service
/lib/systemd/system/apt-daily.service

By default, these run the equivalent of "apt update", and "apt upgrade"
at specified times. However, this behavior is documented nowhere in the
man pages or /usr/share/doc.

Furthermore, they run the command /usr/lib/apt/apt.systemd.daily, which
is also undocumented, nor does it respond to a --help option. A non-
savvy Linux user will not be able to determine that this is a shell
script and find out what it does. Or worse, a partially-savvy Linux user
will be able to determine that this is a shell script, and will read it
imperfectly (usage is also not described in script comments) ending up
with a wrong idea of what it does.

The idea is to keep the system updates. That is a GOOD THING (tm).

But it relies on undocumented behavior. That is a BAD THING (tm).

Can we have the apt-daily service documented?


madumlao@lezard ~ $ lsb_release -rd
Description:Ubuntu 16.04.4 LTS
Release:16.04


apt version: 1.2.26

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

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

Title:
  Please document apt-daily

Status in apt package in Ubuntu:
  New

Bug description:
  The following systemd services are installed along with apt:

  /lib/systemd/system/apt-daily.timer
  /lib/systemd/system/apt-daily-upgrade.timer
  /lib/systemd/system/apt-daily-upgrade.service
  /lib/systemd/system/apt-daily.service

  By default, these run the equivalent of "apt update", and "apt
  upgrade" at specified times. However, this behavior is documented
  nowhere in the man pages or /usr/share/doc.

  Furthermore, they run the command /usr/lib/apt/apt.systemd.daily,
  which is also undocumented, nor does it respond to a --help option. A
  non-savvy Linux user will not be able to determine that this is a
  shell script and find out what it does. Or worse, a partially-savvy
  Linux user will be able to determine that this is a shell script, and
  will read it imperfectly (usage is also not described in script
  comments) ending up with a wrong idea of what it does.

  The idea is to keep the system updates. That is a GOOD THING (tm).

  But it relies on undocumented behavior. That is a BAD THING (tm).

  Can we have the apt-daily service documented?

  
  madumlao@lezard ~ $ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  
  apt version: 1.2.26

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

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

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

[Trent Lloyd]

There is a new bind9 upload to bionic-proposed (9.11.3+dfsg-1ubuntu1)

Tested with this version and 'host' is still hanging.  So this fix is
still required.

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Confirmed
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid

Bug description:
  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

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

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

[Touch-packages] [Bug 1764614] Re: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/l

[Mike B.]

Found a FIX! Just need to move/backup the shared doc file that was
causing the problem and all is right again.

~| sudo mv /usr/share/doc/libperl5.26 /usr/share/doc/libperl5.26.barron
~| sudo apt --fix-broken install

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libperl5.26:i386
The following NEW packages will be installed:
  libperl5.26:i386
0 upgraded, 1 newly installed, 0 to remove and 20 not upgraded.
3 not fully installed or removed.
Need to get 0 B/3,169 kB of archives.
After this operation, 16.3 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 647255 files and directories currently installed.)
Preparing to unpack .../libperl5.26_5.26.0-8ubuntu1.1_i386.deb ...
Unpacking libperl5.26:i386 (5.26.0-8ubuntu1.1) ...
Setting up perl-modules-5.26 (5.26.0-8ubuntu1.1) ...
Processing triggers for libc-bin (2.26-0ubuntu2.1) ...
Setting up libperl5.26:amd64 (5.26.0-8ubuntu1.1) ...
Setting up libperl5.26:i386 (5.26.0-8ubuntu1.1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up perl (5.26.0-8ubuntu1.1) ...
Processing triggers for libc-bin (2.26-0ubuntu2.1) ...

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

Title:
  package libperl5.26 5.26.0-8ubuntu1 [modified:
  usr/share/doc/libperl5.26/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:amd64

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  Gestionnaire de mise à jour
  Echec de traitement du paquet
  l'installation ou la desinstallation du paquet a échoué

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue Apr 17 04:25:22 2018
  DuplicateSignature:
   package:libperl5.26:5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
   Unpacking libperl5.26:amd64 (5.26.0-8ubuntu1.1) over (5.26.0-8ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:amd64
  InstallationDate: Installed on 2017-11-15 (152 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763417] Re: Thin red lines around red headerbar buttons

[Daniel van Vugt]

** Tags added: visual-quality

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

Title:
  Thin red lines around red headerbar buttons

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

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

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

[Touch-packages] [Bug 1764614] Re: package libperl5.26 5.26.0-8ubuntu1 [modified: usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/l

[Mike B.]

Some additional attempts to fix failed for me - I'm stuck and cannot
update or remove anything.


~| sudo apt install perl
Reading package lists... Done
Building dependency tree   
Reading state information... Done
perl is already the newest version (5.26.0-8ubuntu1.1).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libperl5.26 : Breaks: libperl5.26:i386 (!= 5.26.0-8ubuntu1) but 
5.26.0-8ubuntu1.1 is to be installed
 libperl5.26:i386 : Breaks: libperl5.26 (!= 5.26.0-8ubuntu1.1) but 
5.26.0-8ubuntu1 is to be installed
 perl : Depends: libperl5.26 (= 5.26.0-8ubuntu1.1) but 5.26.0-8ubuntu1 is to be 
installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).


~| sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libperl5.26
The following packages will be upgraded:
  libperl5.26
1 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
3 not fully installed or removed.
Need to get 0 B/3,544 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 647747 files and directories currently installed.)
Preparing to unpack .../libperl5.26_5.26.0-8ubuntu1.1_amd64.deb ...
Unpacking libperl5.26:amd64 (5.26.0-8ubuntu1.1) over (5.26.0-8ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:amd64
Errors were encountered while processing:
 /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package libperl5.26 5.26.0-8ubuntu1 [modified:
  usr/share/doc/libperl5.26/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different
  from other instances of package libperl5.26:amd64

Status in perl package in Ubuntu:
  Confirmed

Bug description:
  Gestionnaire de mise à jour
  Echec de traitement du paquet
  l'installation ou la desinstallation du paquet a échoué

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Tue Apr 17 04:25:22 2018
  DuplicateSignature:
   package:libperl5.26:5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz]
   Unpacking libperl5.26:amd64 (5.26.0-8ubuntu1.1) over (5.26.0-8ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1.1_amd64.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:amd64
  InstallationDate: Installed on 2017-11-15 (152 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-8ubuntu1 [modified: 
usr/share/doc/libperl5.26/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1763417] Re: thin red lines around "Format" button in gnome-disks

[Daniel van Vugt]

** No longer affects: gnome-disk-utility (Ubuntu)

** Summary changed:

- thin red lines around "Format" button in gnome-disks
+ Thin red lines around red headerbar buttons

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

Title:
  Thin red lines around red headerbar buttons

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

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

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

[Touch-packages] [Bug 1763417] Re: thin red lines around "Format" button in gnome-disks

[Launchpad Bug Tracker]

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

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

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

Title:
  Thin red lines around red headerbar buttons

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

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

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

[Touch-packages] [Bug 1763417] Re: thin red lines around "Format" button in gnome-disks

[Daniel van Vugt]

I'm seeing the same bug with red headerbar buttons in other apps. I
think colorhug-client was where I saw it last.

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

Title:
  Thin red lines around red headerbar buttons

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

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

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

[Touch-packages] [Bug 1763417] Re: thin red lines around "Format" button in gnome-disks

[Launchpad Bug Tracker]

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

** Changed in: gnome-disk-utility (Ubuntu)
   Status: New => Confirmed

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

Title:
  Thin red lines around red headerbar buttons

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  There are thin red lines around the format button of gnome-disks.
  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 12 17:20:11 2018
  InstallationDate: Installed on 2014-07-15 (1367 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (19 days ago)

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

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

[Touch-packages] [Bug 1764551]

[Steve Beattie]

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

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

** This bug has been marked a duplicate of bug 1764848
   Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be 
removed if duplicate certs found

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  I have no prior idea it showed me that there's some error while
  upgrading the system.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 23:00:44 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-02-14 (61 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~rc1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-16 (0 days ago)

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

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

[Touch-packages] [Bug 1764060] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Steve Beattie]

This is likely a duplicate of bug 1764848. Do you have python-ubuntu-
sso-client installed? Purging that package should hopefully let you work
around this issue.

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Triaged

Bug description:
  upgrading ca-certificates fails with:
  Updating certificates in /etc/ssl/certs...
  rehash: skipping duplicate certificate in Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1

  or

  rehash: skipping duplicate certificate in UbuntuOne-Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 08:32:40 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-03-19 (1122 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764431] Re: package ca-certificates 20180409 failed to install/upgrade: підпроцес installed ca-certificates package post-installation script повернув помилковий код завершення 1

[Steve Beattie]

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

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

** This bug has been marked a duplicate of bug 1764848
   Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be 
removed if duplicate certs found

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: підпроцес
  installed ca-certificates package post-installation script повернув
  помилковий код завершення 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 18.04

  
  ca-certificates 20180409

  During updating:
  Sub-process /usr/bin/dpkg returned an error code

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 17:49:58 2018
  ErrorMessage: підпроцес installed ca-certificates package post-installation 
script повернув помилковий код завершення 1
  InstallationDate: Installed on 2016-03-26 (751 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~rc1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: підпроцес 
installed ca-certificates package post-installation script повернув помилковий 
код завершення 1
  UpgradeStatus: Upgraded to bionic on 2018-03-09 (38 days ago)

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

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

[Touch-packages] [Bug 1764804] Re: package ca-certificates 20180409 failed to install/upgrade: instalado ca-certificates paquete post-installation guión el subproceso devolvió un error con estado de s

[Steve Beattie]

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

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

** This bug has been marked a duplicate of bug 1764848
   Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be 
removed if duplicate certs found

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: instalado
  ca-certificates paquete post-installation guión el subproceso devolvió
  un error con estado de salida 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Linux 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux
  Procesor AMD® A12-9700p radeon r7, 10 compute cores 4c+6g × 4 
  Grafics AMD® Carrizo
  Gnome 3.28.1 

  
   100 /var/lib/dpkg/status
   release a=now
   500 http://ppa.launchpad.net/wfg/0ad/ubuntu bionic/main i386 Packages
   release v=18.04,o=LP-PPA-wfg-0ad,a=bionic,n=bionic,l=0 A.D.,c=main,b=i386
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/wfg/0ad/ubuntu bionic/main amd64 Packages
   release v=18.04,o=LP-PPA-wfg-0ad,a=bionic,n=bionic,l=0 
A.D.,c=main,b=amd64
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic/main i386 
Packages
   release v=18.04,o=LP-PPA-webupd8team-java,a=bionic,n=bionic,l=Oracle 
Java (JDK) 8 / 9 Installer PPA,c=main,b=i386
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/webupd8team/java/ubuntu bionic/main amd64 
Packages
   release v=18.04,o=LP-PPA-webupd8team-java,a=bionic,n=bionic,l=Oracle 
Java (JDK) 8 / 9 Installer PPA,c=main,b=amd64
   origin ppa.launchpad.net
   500 https://packages.microsoft.com/repos/vscode stable/main amd64 Packages
   release o=vscode stable,a=stable,n=stable,l=vscode stable,c=main,b=amd64
   origin packages.microsoft.com
   500 https://deb.opera.com/opera-stable stable/non-free i386 Packages
   release o=Opera Software ASA,a=stable,n=stable,l=The Opera web 
browser,c=non-free,b=i386
   origin deb.opera.com
   500 https://deb.opera.com/opera-stable stable/non-free amd64 Packages
   release o=Opera Software ASA,a=stable,n=stable,l=The Opera web 
browser,c=non-free,b=amd64
   origin deb.opera.com
   500 http://ppa.launchpad.net/obsproject/obs-studio/ubuntu bionic/main i386 
Packages
   release v=18.04,o=LP-PPA-obsproject-obs-studio,a=bionic,n=bionic,l=OBS 
Studio,c=main,b=i386
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/obsproject/obs-studio/ubuntu bionic/main amd64 
Packages
   release v=18.04,o=LP-PPA-obsproject-obs-studio,a=bionic,n=bionic,l=OBS 
Studio,c=main,b=amd64
   origin ppa.launchpad.net
   500 https://deb.nodesource.com/node_8.x bionic/main i386 Packages
   release o=Node Source,n=bionic,l=Node Source,c=main,b=i386
   origin deb.nodesource.com
   500 https://deb.nodesource.com/node_8.x bionic/main amd64 Packages
   release o=Node Source,n=bionic,l=Node Source,c=main,b=amd64
   origin deb.nodesource.com
   500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu bionic/main i386 Packages
   release v=18.04,o=LP-PPA-libreoffice,a=bionic,n=bionic,l=LibreOffice 
Fresh,c=main,b=i386
   origin ppa.launchpad.net
   500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu bionic/main amd64 
Packages
   release v=18.04,o=LP-PPA-libreoffice,a=bionic,n=bionic,l=LibreOffice 
Fresh,c=main,b=amd64
   origin ppa.launchpad.net
   500 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages
   release v=1.0,o=Google, Inc.,a=stable,n=stable,l=Google,c=main,b=amd64
   origin dl.google.com
   500 http://storage.googleapis.com/bazel-apt stable/jdk1.8 amd64 Packages
   release o=Bazel Authors,n=stable,l=Bazel,c=jdk1.8,b=amd64
   origin storage.googleapis.com
   500 http://archive.canonical.com/ubuntu bionic/partner i386 Packages
   release v=18.04,o=Canonical,a=bionic,n=bionic,l=Partner 
archive,c=partner,b=i386
   origin archive.canonical.com
   500 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages
   release v=18.04,o=Canonical,a=bionic,n=bionic,l=Partner 
archive,c=partner,b=amd64
   origin archive.canonical.com
   500 

[Touch-packages] [Bug 1764896] [NEW] System will not display using displayport from AMD GPU

[terry b]

Public bug reported:

There are 2 monitors connected to 1 GPU. The monitor connected via a
digital connection always comes up correctly. The monitor connected via
DISPLAYPORT does not come up, even though the machine is booting
correctly.

It's almost like the DP path isn't recognized by xorg.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Apr 17 18:02:09 2018
DistUpgraded: 2018-03-30 21:12:37,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 
470/480/570/580] [1462:3417]
InstallationDate: Installed on 2017-03-11 (402 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=UUID=68755ecb-0ee0-46a1-8a3e-c027d0cbac65 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-03-31 (17 days ago)
dmi.bios.date: 12/13/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.20
dmi.board.name: Z170M Pro4S
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP7.20:bd12/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170MPro4S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

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

Title:
  System will not display using displayport from AMD GPU

Status in xorg package in Ubuntu:
  New

Bug description:
  There are 2 monitors connected to 1 GPU. The monitor connected via a
  digital connection always comes up correctly. The monitor connected
  via DISPLAYPORT does not come up, even though the machine is booting
  correctly.

  It's almost like the DP path isn't recognized by xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 17 18:02:09 2018
  DistUpgraded: 2018-03-30 21:12:37,078 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] 
[1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 
470/480/570/580] [1462:3417]
  InstallationDate: Installed on 2017-03-11 (402 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=UUID=68755ecb-0ee0-46a1-8a3e-c027d0cbac65 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
 

Re: [Touch-packages] [Bug 1681515] Re: package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

[guezil ahmed hani]

i think that  the probleme is solved because i upgrade my ubuntu to 17.10 ,
i'm not very gifted in data , thank you


On Tue, Apr 17, 2018 at 11:07 PM, Jamie Strandboge  wrote:

> There isn't enough information to process this bug. Is your system still
> affected? Can you provide steps to reproduce?
>
> ** Changed in: apparmor (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1681515
>
> Title:
>   package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package
>   is in a very bad inconsistent state; you should  reinstall it before
>   attempting configuration
>
> Status in apparmor package in Ubuntu:
>   Incomplete
>
> Bug description:
>   the update don't want to be complited
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 15.04
>   Package: dh-apparmor 2.9.1-0ubuntu9
>   ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22
>   Uname: Linux 3.19.0-84-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.17.2-0ubuntu1.8
>   Architecture: amd64
>   Date: Fri Apr  7 01:33:58 2017
>   Dependencies:
>
>   DpkgHistoryLog:
>Start-Date: 2017-04-07  01:32:59
>Commandline: aptdaemon role='role-commit-packages' sender=':1.93'
>Install: linux-headers-3.19.0-84-generic:amd64 (3.19.0-84.92),
> linux-headers-3.19.0-84:amd64 (3.19.0-84.92), 
> linux-image-extra-3.19.0-84-generic:amd64
> (3.19.0-84.92), linux-image-3.19.0-84-generic:amd64 (3.19.0-84.92)
>Upgrade: linux-headers-generic:amd64 (3.19.0.82.80, 3.19.0.84.82),
> google-chrome-stable:amd64 (57.0.2987.98-1, 57.0.2987.133-1),
> linux-libc-dev:amd64 (3.19.0-82.90, 3.19.0-84.92),
> linux-image-generic:amd64 (3.19.0.82.80, 3.19.0.84.82)
>   DuplicateSignature: package:dh-apparmor:2.9.1-0ubuntu9: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 2015-10-30 (527 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
>   PackageArchitecture: all
>   ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-84-generic
> root=UUID=9ce7fb5a-2b9f-407f-bcd0-b256764f29c4 ro quiet splash
>   RelatedPackageVersions:
>dpkg 1.17.25ubuntu1.1
>apt  1.0.9.7ubuntu4.2
>   SourcePackage: apparmor
>   Syslog: Apr 10 19:07:10 zambla dbus[688]: [system] AppArmor D-Bus
> mediation is enabled
>   Title: package dh-apparmor 2.9.1-0ubuntu9 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/apparmor/+bug/
> 1681515/+subscriptions
>

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

Title:
  package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  the update don't want to be complited

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: dh-apparmor 2.9.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-84-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  Date: Fri Apr  7 01:33:58 2017
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2017-04-07  01:32:59
   Commandline: aptdaemon role='role-commit-packages' sender=':1.93'
   Install: linux-headers-3.19.0-84-generic:amd64 (3.19.0-84.92), 
linux-headers-3.19.0-84:amd64 (3.19.0-84.92), 
linux-image-extra-3.19.0-84-generic:amd64 (3.19.0-84.92), 
linux-image-3.19.0-84-generic:amd64 (3.19.0-84.92)
   Upgrade: linux-headers-generic:amd64 (3.19.0.82.80, 3.19.0.84.82), 
google-chrome-stable:amd64 (57.0.2987.98-1, 57.0.2987.133-1), 
linux-libc-dev:amd64 (3.19.0-82.90, 3.19.0-84.92), linux-image-generic:amd64 
(3.19.0.82.80, 3.19.0.84.82)
  DuplicateSignature: package:dh-apparmor:2.9.1-0ubuntu9: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 2015-10-30 (527 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-84-generic 
root=UUID=9ce7fb5a-2b9f-407f-bcd0-b256764f29c4 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  

[Touch-packages] [Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found

[Brian Murray]

** Tags added: bionic rls-bb-incoming

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

Title:
  Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to
  be removed if duplicate certs found

Status in Ubuntu Single Sign On Client:
  New
Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  The certificate /usr/share/ca-
  certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-
  certificates is conflicting with /etc/ssl/certs/UbuntuOne-
  Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client.

  This results in the postinst trigger for ca-certificates to remove the
  /etc/ssl/certs/ca-certificates.crt file.  This happens because the
  postinst trigger runs update-ca-certificates --fresh.

  If I run update-ca-certificates without the --fresh flag, the conflict
  is a non-issue and the ca-certificates.crt file is restored.

  If I understand some of the postinst code correctly, --fresh should
  only be run if called directly or if upgrading from a ca-certificates
  version older than 2011.

  Running bionic with daily -updates channel and ran into this this
  morning due to the release of ca-certificates version 20180409.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions

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

[Touch-packages] [Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found

[Brian Murray]

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to
  be removed if duplicate certs found

Status in Ubuntu Single Sign On Client:
  New
Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  The certificate /usr/share/ca-
  certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-
  certificates is conflicting with /etc/ssl/certs/UbuntuOne-
  Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client.

  This results in the postinst trigger for ca-certificates to remove the
  /etc/ssl/certs/ca-certificates.crt file.  This happens because the
  postinst trigger runs update-ca-certificates --fresh.

  If I run update-ca-certificates without the --fresh flag, the conflict
  is a non-issue and the ca-certificates.crt file is restored.

  If I understand some of the postinst code correctly, --fresh should
  only be run if called directly or if upgrading from a ca-certificates
  version older than 2011.

  Running bionic with daily -updates channel and ran into this this
  morning due to the release of ca-certificates version 20180409.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions

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

[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

[Dan Streetman]

Test build in ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1447715

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot. It will fail to get a dhcp address during
  boot.

  [Regression Potential]

  None

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

  Related Bugs:
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)

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

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

[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

[Dan Streetman]

** Patch removed: "lp1447715-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1447715/+attachment/4745626/+files/lp1447715-xenial.debdiff

** Patch added: "lp1447715-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1447715/+attachment/5120139/+files/lp1447715-xenial.debdiff

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot. It will fail to get a dhcp address during
  boot.

  [Regression Potential]

  None

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

  Related Bugs:
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)

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

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

[Jamie Strandboge]

** Changed in: apparmor (Ubuntu)
   Status: Confirmed => 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/1701297

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

Status in cloud-init:
  Won't Fix
Status in apparmor package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed

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.

  Related bugs:
   * bug 1645644: cloud-init ntp not using expected servers

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 1712039] Re: AppArmor profile misses entry for /var/lib/snapd/desktop/applications/mimeinfo.cache

[Jamie Strandboge]

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

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

Title:
  AppArmor profile misses entry for
  /var/lib/snapd/desktop/applications/mimeinfo.cache

Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  The evince AppArmor profile seems to miss an entry for 
/var/lib/snapd/desktop/applications/mimeinfo.cache.
  If evince is launched, the following gets logged to syslog:

  kernel: [81577.596186] audit: type=1400 audit(1503306090.062:2011):
  apparmor="DENIED" operation="open" profile="/usr/bin/evince"
  name="/var/lib/snapd/desktop/applications/mimeinfo.cache" pid=32268
  comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  I don't know if this should be allowed or denied. If you could add the
  correct behaviour to the profile, that would be nice; otherwise, every
  time evince is launched, a notification pops up (apparmor-notify
  installed).

  
  (Workaround:

  Add to original profile (/etc/apparmor.d/usr.bin.evince):
#include 

  Insert into local profile (/etc/apparmor.d/local/usr.bin.evince):
/var/lib/snapd/desktop/applications/mimeinfo.cache r,
  )

  Release: Ubuntu 16.04.3 LTS
  Package Version: evince-common 3.18.2-1ubuntu4.1

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

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

[Touch-packages] [Bug 1752806] Re: package apparmor 2.10.95-0ubuntu2.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29

[Jamie Strandboge]

This looks like it might have been a transient file system issue. Is
your system still in this state? If so, please run afilesystem check and
then run 'sudo dpkg --configure -a ; sudo apt-get update ; sudo apt-get
upgrade'.

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

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

Title:
  package apparmor 2.10.95-0ubuntu2.9 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 29

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  failed to upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.9
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar  1 08:48:41 2018
  DpkgHistoryLog:
   
  DuplicateSignature:
   package:apparmor:2.10.95-0ubuntu2.9
   Installing new version of config file /etc/apparmor.d/abstractions/base ...
   Can't locate object method "new" via package "Text::Iconv" (perhaps you 
forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65.
   dpkg: error processing package apparmor (--configure):
subprocess installed post-installation script returned error exit status 29
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 29
  InstallationDate: Installed on 2017-11-01 (120 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=23ec1776-d281-4d0e-89b3-c7843e709030 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: apparmor
  Syslog: Mar  2 09:14:31 yadiris-Satellite-U400 dbus[761]: [system] AppArmor 
D-Bus mediation is enabled
  Title: package apparmor 2.10.95-0ubuntu2.9 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 29
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1734461] Re: laptop boots, post messages scoll up screen, and FAILED in red appears. cannot restart the saervice

[Jamie Strandboge]

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

This is almost certainly a duplicate of LP: #1756800. Please take a look
at that bug and remove the affected profiles. Do note that apparmor is a
oneshot service and it will report an error if any profiles fail to
load, but will continue to load all the profiles.

** This bug has been marked a duplicate of bug 1756800
   Failed to start AppArmor initialization with status=123/n/a

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

Title:
  laptop boots, post messages scoll up screen, and FAILED in red
  appears.  cannot restart  the saervice

Status in apparmor package in Ubuntu:
  New

Bug description:
  tried to restart service, It would not restart. fails on every reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.7
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: wl
  ApparmorStatusOutput: Error: command ['pkexec', '/usr/sbin/apparmor_status'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 25 17:29:59 2017
  InstallationDate: Installed on 2016-10-18 (402 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic.efi.signed 
root=UUID=bfca8567-c8c6-4f94-aeb3-6548beb32023 ro drm.debug=0xe plymouth:debug
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1761016] Re: cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma

[Simon Quigley]

This has migrated.

** Changed in: qtdeclarative-opensource-src (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix
  image slideshows in KDE Plasma

Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  KDE Plasma is affected by a Qt bug that causes image slideshows to
  leak memory, eventually exhausting all available memory and crashing
  the system: https://bugs.kde.org/show_bug.cgi?id=368838

  This principally affects people who use the popular slideshow
  wallpaper feature. Thankfully, there's a Qt patch to fix it the issue:
  https://codereview.qt-project.org/#/c/224684/

  It's slated to go into Qt 5.11. We should strongly consider cherry-
  picking it into 5.9.x to get this important fix into our users' hands
  as soon as possible.

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

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

[Touch-packages] [Bug 1762983] Re: communitheme snap doesn't work with evince

[Jamie Strandboge]

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

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

Title:
  communitheme snap doesn't work with evince

Status in apparmor package in Ubuntu:
  In Progress

Bug description:
  As mentioned on https://github.com/ubuntu/gtk-
  communitheme/issues/325#issuecomment-380383969, evince can't load the
  communitheme snap.

  Indeed, as the directory isn't a standard one (/snap/…), the protected
  applications by apparmor can't load it.

  As the snap is temporary, distro-patch (ubuntu only) common
  abstractions directory for theme and icons (similar than the flatpak
  patches).

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

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

[Touch-packages] [Bug 1757256] Re: Apparmor profile gajim

[Jamie Strandboge]

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

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

Title:
  Apparmor profile gajim

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  Followed this guide: https://gitlab.com/apparmor/apparmor/wi … with_tools and 
saved usr.bin.gajim after scanning.
  After I restart machine and run Gajim from terminal I get:

  Fatal Python error: Py_Initialize: Unable to get the locale encoding
  ModuleNotFoundError: No module named 'encodings'

  Current thread 0x6a383a1d5540 (most recent call first):
  Aborted (core dumped)

  If I delete the profile and restart machine it runs (to confirm it is
  profile causing).

  This is my current profile

  
  # vim:syntax=apparmor
  # --
  #
  #Copyright (C) 2015-2018 Mikhail Morfikov
  #
  #This program is free software; you can redistribute it and/or
  #modify it under the terms of version 2 of the GNU General Public
  #License published by the Free Software Foundation.
  #
  # --

  #include 

  /usr/bin/gajim {
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

/usr/bin/gajim mr,

/usr/bin/ r,
/usr/local/bin/ r,

# Gajim plugins
/usr/share/gajim/plugins/ r,
/usr/share/gajim/plugins/** r,

# Gajim home files
owner @{HOME}/.config/gajim/ rw,
owner @{HOME}/.config/gajim/** rw,
owner @{HOME}/.local/share/gajim/ rw,
owner @{HOME}/.local/share/gajim/** rwk,

# User downloads
owner @{HOME}/[dD]ownload{,s}/ r,
owner @{HOME}/[dD]ownload{,s}/** rwl,
owner @{HOME}/[dD]esktop/ r,
owner @{HOME}/[dD]esktop/** rwl,

# Cache
owner /tmp/morfik_cache/.cache/gajim/ rwk,
owner /tmp/morfik_cache/.cache/gajim/** rwk,
owner @{HOME}/.cache/gajim/ rwk,
owner @{HOME}/.cache/gajim/** rwk,

# Deny access to webcam and mic
deny /dev/video0 rw,
deny /dev/v4l/by-path/ r,
deny /dev/snd/pcmC0D0c rw,

owner @{PROC}/@{pid}/mounts r,
owner @{PROC}/@{pid}/fd/ r,
owner @{PROC}/@{pid}/mountinfo r,

# External apps
/usr/lib/firefox/firefox rPUx,
/usr/bin/gpg rPUx,

/usr/share/glib-2.0/schemas/gschemas.compiled r,

owner /{,var/}run/user/[0-9]*/dconf/user rw,

# Silencer
deny /usr/lib/python3/dist-packages/** w,
deny /usr/share/gajim/plugins/** w,
deny @{HOME}/ r,

# Sounds
/usr/bin/aplay Cx -> audio,
/usr/bin/pacat Cx -> audio,
profile audio {
  #include 
  #include 

  /usr/bin/aplay mr,
  /usr/bin/pacat mr,

  owner @{HOME}/.Xauthority r,

  /etc/machine-id r,
  /var/lib/dbus/machine-id r,

}

/sbin/ldconfig Cx -> ldconfig,
profile ldconfig {
  #include 

  /sbin/ldconfig mr,

}

/bin/dash Cx -> dash,
profile dash {
  #include 

  /bin/dash mr,

  /bin/uname rix,

  /usr/bin/gpg rPUx,

}

  }

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

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

[Touch-packages] [Bug 1764312] Re: fails to start in Bionic

[Jamie Strandboge]

The initial report indicated a parser error, but then it was reported
that the apparmor package was removed, so then it would not be able to
run properly. I'm not able to reproduce with the information given. If
you are able to provide exact steps to reproduce, please do and we can
take another look.

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

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

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

Title:
  fails to start in Bionic

Status in apparmor package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  $ systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 
10min ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 635 (code=exited, status=123)

  Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]:...fail!
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization.

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

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

[Touch-packages] [Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found

[Brian Murray]

I was able to recreate this when upgrading a Ubuntu 16.04 chroot to
Ubuntu 18.04 by editing /etc/apt/sources.list from xenial to bionic and
running 'apt-get dist-upgrade'.

Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
rehash: skipping duplicate certificate in Go_Daddy_Class_2_CA.pem
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned 
error exit status 1

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

Title:
  Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to
  be removed if duplicate certs found

Status in Ubuntu Single Sign On Client:
  New
Status in ca-certificates package in Ubuntu:
  New

Bug description:
  The certificate /usr/share/ca-
  certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-
  certificates is conflicting with /etc/ssl/certs/UbuntuOne-
  Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client.

  This results in the postinst trigger for ca-certificates to remove the
  /etc/ssl/certs/ca-certificates.crt file.  This happens because the
  postinst trigger runs update-ca-certificates --fresh.

  If I run update-ca-certificates without the --fresh flag, the conflict
  is a non-issue and the ca-certificates.crt file is restored.

  If I understand some of the postinst code correctly, --fresh should
  only be run if called directly or if upgrading from a ca-certificates
  version older than 2011.

  Running bionic with daily -updates channel and ran into this this
  morning due to the release of ca-certificates version 20180409.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions

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

[Touch-packages] [Bug 1730908] Re: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/

[Jamie Strandboge]

Does evince not work or is this simply a noisy denial?

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

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

Title:
  [ 1549.847151] audit: type=1400 audit(1510129355.497:61):
  apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-
  gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062
  comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  Since I installed Ubuntu 17.10 I cannot print anymore.

  The only thing I see in the logs are many lines like the following:
  [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" 
operation="file_mmap" profile="/usr/bin/evince" 
name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.14/modules/network_networkmanager.so"
 pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  I'm not sure it is the cause of my problems, but there is at least a
  problem with apparmor's configuration in Ubuntu 17.10

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

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

[Touch-packages] [Bug 1745872] Re: package libapparmor-perl 2.10.95-0ubuntu2.6 failed to install/upgrade: package libapparmor-perl is not ready for configuration cannot configure (current status 'half

[Jamie Strandboge]

There is not enough information to process this bug report. Is your
system still in this state? Do you have steps to reproduce?

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

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

Title:
  package libapparmor-perl 2.10.95-0ubuntu2.6 failed to install/upgrade:
  package libapparmor-perl is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libapparmor-perl 2.10.95-0ubuntu2.6
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Jan 24 00:50:28 2018
  ErrorMessage: package libapparmor-perl is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-01-24 (4 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apparmor
  Syslog: Jan 28 14:30:18 Laptop dbus[813]: [system] AppArmor D-Bus mediation 
is enabled
  Title: package libapparmor-perl 2.10.95-0ubuntu2.6 failed to install/upgrade: 
package libapparmor-perl 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/apparmor/+bug/1745872/+subscriptions

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

[Touch-packages] [Bug 1764858] Re: Can't update / install / delete packages

[Vasily]

Hi, Julian!

Thank for reply. I have think similar way, but there are no any errors
in logs. You can find logs attached

(term.log consist russian strings cause system locale)

** Attachment added: "apt_logs.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1764858/+attachment/5120114/+files/apt_logs.tar.gz

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

Title:
  Can't update / install / delete packages

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  After todays upgrade:

  vasily@vasily-desktop:~$ sudo apt-get update
  [sudo] пароль для vasily: 
  apt-get: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory

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

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

[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

[Dan Streetman]

I'm re-opening this for Xenial, moving from Wontfix back to in progress.
This is because while 'normal' dhcpv6 works without this fix because of
the patch to dhclient (see my explanation in comment 23), there is a
special case of using dhclient in 'stateless' mode, i.e. dhclient -6 -S.
In that mode, dhclient does not call its 'PREINIT6' which is where the
wait-for-dad patch was added.  When configuring ifupdown in this way,
dhclient still fails due to this bug; e.g.:

auto eth0
iface eth0 inet6 auto
  dhcp 1

if eth0 is down, then running ifup eth0 with the above config will
result in dhclient always failing due to this bug.

** Changed in: ifupdown (Ubuntu Xenial)
   Status: Won't Fix => In Progress

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot. It will fail to get a dhcp address during
  boot.

  [Regression Potential]

  None

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

  Related Bugs:
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)

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

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

[Touch-packages] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address

[Dan Streetman]

i opened bug 1764478 to change dhclient 'stateless' mode, but as
explained in that bug, it's better to fix ifupdown, here.

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

Title:
  dhclient -6: Can't bind to dhcp address: Cannot assign requested
  address

Status in ifupdown package in Ubuntu:
  Fix Released
Status in ifupdown source package in Xenial:
  In Progress
Status in ifupdown package in Debian:
  Fix Released

Bug description:
  [Impact]

  When using dhcpv6 configured via ifupdown, the interface's dhcp client
  fails to start at boot with the error:

  Can't bind to dhcp address: Cannot assign requested address

  This is because ifupdown doesn't wait, after bringing the interface
  up, for it to complete its link-local Duplicate Address Detection
  (DAD), and the dhcp client can't bind to the link-local address
  because it's still in "tentative" state (until DAD completes).

  This is fixed upstream in debian ifupdown in version 0.8.11 by adding
  '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the
  script was only waiting for the link-local address to appear, now it
  waits until the link-local address appears and is not in 'tentative'
  state.

  [Test Case]

  Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0
  inet6 dhcp) and reboot. It will fail to get a dhcp address during
  boot.

  [Regression Potential]

  None

  [Other Info]

  After upgrading to Ubuntu 15.04 my computer is unable to obtain an
  IPv6 address via DHCPv6. The root cause is that dhclient is exiting
  with the following message:

  -
  Can't bind to dhcp address: Cannot assign requested address
  Please make sure there is no other dhcp server
  running and that there's no entry for dhcp or
  bootp in /etc/inetd.conf.   Also make sure you
  are not running HP JetAdmin software, which
  includes a bootp server.

  If you think you have received this message due to a bug rather
  than a configuration issue please read the section on submitting
  bugs on either our web page at www.isc.org or in the README file
  before submitting a bug.  These pages explain the proper
  process and the information we find helpful for debugging..

  exiting.
  -

  The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04
  version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10
  version) allows me to obtain an address.

  NetworkManager is the one launching dhclient. The two invocations (one
  for IPv4 and one for IPv6) are:

  dhclient_start(): running: /sbin/dhclient -d -q -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager
  /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient-eth0.conf eth0

  dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf
  /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d
  /network-manager.dhclient6-eth0.pid -lf
  /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b-
  563cfb1fb9d2-eth0.lease -cf
  /var/lib/NetworkManager/dhclient6-eth0.conf eth0

  I do not see anything suspicious with the way both dhclients are
  invoked.

  Given that a downgrade allows me to obtain an IPv6 address I think
  this might be a bug in the ISC DHCP client rather than in
  NetworkManager.

  Related Bugs:
   * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address 
detection)

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

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

[Touch-packages] [Bug 1741673] Re: package apparmor 2.10.95-0ubuntu2.7 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvo

[Jamie Strandboge]

There is not enough information to process this bug. Is your system
still in this state? Do you have steps to reproduce?

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

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

Title:
  package apparmor 2.10.95-0ubuntu2.7 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 apparmor package in Ubuntu:
  Incomplete

Bug description:
  this just appears after boot

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2.7
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Jan  6 19:09:45 2018
  ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u 
zou het  opnieuw moeten installeren alvorens het te configureren.
  InstallationDate: Installed on 2018-01-06 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed 
root=UUID=078c3b1f-8051-46e0-b2bd-28f8338f4dcf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apparmor
  Syslog:
   Jan  6 18:38:06 wendie-X705UAR dbus[790]: [system] AppArmor D-Bus mediation 
is enabled
   Jan  6 18:56:11 wendie-X705UAR dbus[777]: [system] AppArmor D-Bus mediation 
is enabled
   Jan  6 19:17:47 wendie-X705UAR dbus[771]: [system] AppArmor D-Bus mediation 
is enabled
  Title: package apparmor 2.10.95-0ubuntu2.7 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/apparmor/+bug/1741673/+subscriptions

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Pioterus]

Commenting out dnsmasq stopped working. What I have done recently:
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
so my kernel is 4.13 and to my big surprise after connecting with OpenVPN I can 
resolve host names of my remote site (using host myhost.remote.domain.name), 
but I cannot ping to them (or krdc to them etc) host unknown and thats it. What 
is going on?

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1718841] Re: package libapparmor1:amd64 2.10.95-0ubuntu2.7 failed to install/upgrade: package libapparmor1:amd64 is not ready for configuration cannot configure (current status '

[Jamie Strandboge]

There is not enough information to process this bug report. Is your
system still in this state? Do you have steps to reproduce?

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

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

Title:
  package libapparmor1:amd64 2.10.95-0ubuntu2.7 failed to
  install/upgrade: package libapparmor1:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  Error in the start

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libapparmor1:amd64 2.10.95-0ubuntu2.7
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Sep 21 18:30:24 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DpkgTerminalLog:
   dpkg: error processing package libapparmor1:amd64 (--configure):
package libapparmor1:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libapparmor1:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed 
root=UUID=922051bf-9077-47e0-8b11-082cc4e1c1ec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apparmor
  Syslog:
   Sep 21 17:39:32 iter-PeCe dbus[789]: [system] AppArmor D-Bus mediation is 
enabled
   Sep 21 18:26:09 iter-PeCe dbus[802]: [system] AppArmor D-Bus mediation is 
enabled
   Sep 21 19:25:09 iter-PeCe dbus[782]: [system] AppArmor D-Bus mediation is 
enabled
  Title: package libapparmor1:amd64 2.10.95-0ubuntu2.7 failed to 
install/upgrade: package libapparmor1:amd64 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/apparmor/+bug/1718841/+subscriptions

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

[Touch-packages] [Bug 1764551] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: ca-certificates (Ubuntu)
   Status: New => Confirmed

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  I have no prior idea it showed me that there's some error while
  upgrading the system.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 23:00:44 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-02-14 (61 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~rc1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-16 (0 days ago)

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

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

[Touch-packages] [Bug 1704681] Re: package python3-apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade

[Jamie Strandboge]

There is not enough information to process this bug. Is your system
still affected? Do you have specific steps on how to reproduce?

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

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

Title:
  package python3-apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  An error message occurs when trying to update package via command line : 
`sudo apt-get update && sudo apt-get upgrade`. I've got below error message :
  ""
  package python3-apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration.
  ""

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-apparmor 2.10.95-0ubuntu2.6
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  Date: Wed Jul 12 22:33:38 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-05-10 (798 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  KernLog:
   
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed 
root=UUID=ba670a30-9821-4238-9e27-25887fc23447 ro 
usbhid.quirks=0x1B1C:0x1B19:0x2000 quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apparmor
  Syslog:
   
  Title: package python3-apparmor 2.10.95-0ubuntu2.6 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/apparmor/+bug/1704681/+subscriptions

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

[Touch-packages] [Bug 1704516] Re: package apparmor 2.10.95-0ubuntu2 failed to install/upgrade: 现在尚不能配置软件包 apparmor 不能配置(目前状态为 half-installed )

[Jamie Strandboge]

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

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

Title:
  package apparmor 2.10.95-0ubuntu2 failed to install/upgrade:
  现在尚不能配置软件包 apparmor  不能配置(目前状态为 half-installed )

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  package apparmor 2.10.95-0ubuntu2 failed to install/upgrade:
  现在尚不能配置软件包 apparmor  不能配置(目前状态为 half-installed )

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apparmor 2.10.95-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Sat Jul 15 09:53:11 2017
  ErrorMessage: 现在尚不能配置软件包 apparmor  不能配置(目前状态为 half-installed )
  InstallationDate: Installed on 2016-12-23 (203 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  KernLog:
   
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic 
root=UUID=0fc728e5-8021-4555-9639-7d880aab4399 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.15ubuntu0.2
  SourcePackage: apparmor
  Syslog:
   
  Title: package apparmor 2.10.95-0ubuntu2 failed to install/upgrade: 
现在尚不能配置软件包 apparmor  不能配置(目前状态为 half-installed )
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1681515] Re: package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Jamie Strandboge]

There isn't enough information to process this bug. Is your system still
affected? Can you provide steps to reproduce?

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

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

Title:
  package dh-apparmor 2.9.1-0ubuntu9 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  the update don't want to be complited

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: dh-apparmor 2.9.1-0ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-84-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  Date: Fri Apr  7 01:33:58 2017
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2017-04-07  01:32:59
   Commandline: aptdaemon role='role-commit-packages' sender=':1.93'
   Install: linux-headers-3.19.0-84-generic:amd64 (3.19.0-84.92), 
linux-headers-3.19.0-84:amd64 (3.19.0-84.92), 
linux-image-extra-3.19.0-84-generic:amd64 (3.19.0-84.92), 
linux-image-3.19.0-84-generic:amd64 (3.19.0-84.92)
   Upgrade: linux-headers-generic:amd64 (3.19.0.82.80, 3.19.0.84.82), 
google-chrome-stable:amd64 (57.0.2987.98-1, 57.0.2987.133-1), 
linux-libc-dev:amd64 (3.19.0-82.90, 3.19.0-84.92), linux-image-generic:amd64 
(3.19.0.82.80, 3.19.0.84.82)
  DuplicateSignature: package:dh-apparmor:2.9.1-0ubuntu9: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 2015-10-30 (527 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-84-generic 
root=UUID=9ce7fb5a-2b9f-407f-bcd0-b256764f29c4 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: apparmor
  Syslog: Apr 10 19:07:10 zambla dbus[688]: [system] AppArmor D-Bus mediation 
is enabled
  Title: package dh-apparmor 2.9.1-0ubuntu9 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/apparmor/+bug/1681515/+subscriptions

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

[Touch-packages] [Bug 1764478] Re: dhclient in 'stateless' mode does not wait for ipv6 dad

[Dan Streetman]

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

this is also related to bug 1447715 in which i added the DAD wait to
ifupdown.  however, since bug 1633479 fixed the issue in dhclient
instead of ifupdown, at around the same time, i marked bug 1447715 as
wontfix, since that ifupdown change was no longer required to get
dhclient working.

But, now with this bug, the side-effect of changing dhclient to do its
'PREINIT6' (as mentioned in last comment) seems to be prohibitive and it
probably is much easier to simply re-open bug 1447715 and push that
ifupdown fix into xenial.

That approach does mean that manual running of dhclient -6 -S will
always fail with an interface that's down (or was brought up immediately
before running dhclient -S, which is what ifupdown does).  However,
while manually running dhclient -6 on a currently down interface in
order to both bring it up and get a dhcpv6 address does make sense,
running dhclient -6 -S on a down interface does not really make sense,
since doing that will only get the 'other' network info like DNS server,
and won't actually set up an address on the interface.  So I think I
have to agree with the conclusion in bug 1633562, to mark waiting for
dad when manually running dhclient -6 -S as invalid.

So, I'll mark this bug as a dup of that original bug, and I'll re-open
bug 1447715 to push that ifupdown fix into xenial.

** This bug has been marked a duplicate of bug 1633562
   'dhclient -6 -S' does not bring interface up

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

Title:
  dhclient in 'stateless' mode does not wait for ipv6 dad

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

Bug description:
  [impact]

  when configuring an interface in ifupdown to use 'inet6 auto' (SLAAC),
  the option 'dhcp 1' can also be used, which will use isc-dhcp-client
  to perform 'stateless' dhcpv6, which does not get a dhcpv6 address,
  only config info, like DNS domain and server, etc.

  bug 1633479 fixed isc-dhcp-client to properly bring up and wait for
  the interface's ipv6 Duplicate Address Detection (DAD) to complete,
  which is required for isc-dhcp-client to be able to open a socket and
  begin broadcasting DHCPv6 requests.  However, that fix is skipped when
  isc-dhcp-client is used in 'stateless' mode, so it fails in exactly
  the same way, for the same reason; isc-dhcp-client needs to be updated
  to perform the 'PREINIT6' call to the dhclient script, which properly
  sets up the interface for dhclient to use.

  Without that setup, isc-dhcp-client in DHCPv6 'stateless' mode will
  always fail immediately when the interface it's using is down.  If the
  interface is up, it will already have completed DAD and dhclient will
  work.

  [test case]

  configure ifupdown with:

  auto eth0
  iface eth0 inet6 auto
dhcp 1

  replacing eth0 with the interface to test.  Make sure the interface is
  down, then ifup the interface.  isc-dhcp-client will fail claiming
  that:

  no link-local IPv6 address for eth0

  
  Alternately, ifupdown can be bypassed; for an interface that is currently 
down, do:

  $ sudo dhclient -6 -S eth0

  which will fail immediately (the -S param uses 'stateless' mode).

  [regression potential]

  changing isc-dhcp-client to perform PREINIT6 adds a new point of
  failure for doing DHCPv6, so there is the potential to break existing
  DHCPv6 clients if the preinit fails.  However, 'normal' DHCPv6 already
  does preinit6 - this only adds it to 'stateless' DHCPv6, so the
  failure potential should be limited to only users of 'stateless'
  DHCPv6, and those users are likely already seeing failures as
  described in this bug.

  [other info]

  This is related to bug 1633479

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

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

[Touch-packages] [Bug 1764797] Re: [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable (main)

[Balint Reczey]

** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Feature Freeze Justification
  

  Latest unattended-upgrades upload fixed multiple serious issues and
  includes a few minor fixes which are not worth skipping.

  Most notably it now runs upgrade-between-snapshots autopkgtest with
  updated python-apt thus regressions can block migration to release
  pocket and fixes frequent crashes due to using python-apt's API in a
  wrong way.

  Changes:
   unattended-upgrades (1.1ubuntu1) bionic; urgency=medium
   .
     * Merge from Debian unstable (LP: #1764797)
   - Remaining changes:
     - unattended-upgrades: Do not automatically upgrade the development
   release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
   - Dropped changes, included in Debian:
     - Rename d/NEWS.Debian to d/NEWS to have it shipped
     - Fix typo in NEWS file
     - d/rules: Exclude mypy cache from source package.
   .
   unattended-upgrades (1.1) unstable; urgency=medium
   .
     [ cgail914 ]
     * Update 50unattended-upgrades.Raspbian
   added a semi-column sign on line 86 to facilitate uncommenting the line
   for users and not end up with an error message when running
   unattended-upgrades. And make the whole file consistent.
   .
     [ Tobias Bannert ]
     * completed german translation
   .
     [ Simon McVittie ]
     * d/rules: Exclude mypy cache from source package.
   .
     [ Julian Andres Klode ]
     * Do not reuse old apt.Version objects after reopening cache (LP: #1737441)
   .
     [ Balint Reczey ]
     * Rename d/NEWS.Debian to d/NEWS to have it shipped
     * Fix typo in NEWS file
     * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages 
option
     * Set UnattendedUpgradesCache.allowed_origins before calling
   apt.Cache.__init__()
     * Find package candidates to adjust sweeping through all packages only 
once.
   Later reuse the list candidates and filter out packages installed in the
   meantime. Thanks to Julian Andres Klode for the original patch
     * Use updated python-apt in upgrade-between-snapshots test
     * upgrade-between-snapshots: Mount /proc, too, in the chroot.
   Also clean up chroot properly on exit.
     * upgrade-between-snapshots: Use http_proxy environment variable in chroot,
   too
     * upgrade-between-snapshots: Remove packages installed as the side-effect 
of
   updating apt and python-apt
     * Ignore errors from compiling backported packages
     * Make is_autoremove_valid() nondestructive.
   Also fix autoremoval of packages when one package can't be removed and
   keeps back other package removals due to missing cache.clear()
     * Fix tracking removed packages
     * Suggest default-mta | mail-transport-agent to keep Lintian happy
   .
     [ Michael Vogt ]
     * unattanded-upgrades: refactor get_candidates_to_adjust() to
   adjust_candidates()

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

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

[Touch-packages] [Bug 1739943] Re: apparmor ntpd profile problem [64238.000768] audit: type=1400 audit(1513904231.500:45): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected

[Jamie Strandboge]

The profile needs attach_disconnected.

** Package changed: apparmor (Ubuntu) => ntp (Ubuntu)

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

Title:
  apparmor ntpd profile problem [64238.000768] audit: type=1400
  audit(1513904231.500:45): apparmor="DENIED" operation="sendmsg"
  info="Failed name lookup - disconnected path" error=-13
  profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=30945
  comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

Status in ntp package in Ubuntu:
  New

Bug description:
  It would seem apparmor is denying ntpd access to log:
  [64238.000768] audit: type=1400 audit(1513904231.500:45): apparmor="DENIED" 
operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 
profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=30945 
comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor 2.11.0-2ubuntu17
  ProcVersionSignature: Ubuntu 4.13.0-22.25-lowlatency 4.13.13
  Uname: Linux 4.13.0-22-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 24 01:02:15 2017
  InstallationDate: Installed on 2017-08-14 (132 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  KernLog:
   
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-22-lowlatency 
root=UUID=a3646d61-5a64-4011-9bd5-bb806d3e3e8c ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to artful on 2017-10-19 (65 days ago)

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

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

[Touch-packages] [Bug 1764478] Re: dhclient in 'stateless' mode does not wait for ipv6 dad

[Dan Streetman]

this issue was raised before in bug 1633562, and closed as invalid
because a side effect of isc-dhcp doing 'preinit6' is clearing any
existing global ipv6 addresses from the interface, which definitely is
not desirable when using RA to get the address.

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

Title:
  dhclient in 'stateless' mode does not wait for ipv6 dad

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

Bug description:
  [impact]

  when configuring an interface in ifupdown to use 'inet6 auto' (SLAAC),
  the option 'dhcp 1' can also be used, which will use isc-dhcp-client
  to perform 'stateless' dhcpv6, which does not get a dhcpv6 address,
  only config info, like DNS domain and server, etc.

  bug 1633479 fixed isc-dhcp-client to properly bring up and wait for
  the interface's ipv6 Duplicate Address Detection (DAD) to complete,
  which is required for isc-dhcp-client to be able to open a socket and
  begin broadcasting DHCPv6 requests.  However, that fix is skipped when
  isc-dhcp-client is used in 'stateless' mode, so it fails in exactly
  the same way, for the same reason; isc-dhcp-client needs to be updated
  to perform the 'PREINIT6' call to the dhclient script, which properly
  sets up the interface for dhclient to use.

  Without that setup, isc-dhcp-client in DHCPv6 'stateless' mode will
  always fail immediately when the interface it's using is down.  If the
  interface is up, it will already have completed DAD and dhclient will
  work.

  [test case]

  configure ifupdown with:

  auto eth0
  iface eth0 inet6 auto
dhcp 1

  replacing eth0 with the interface to test.  Make sure the interface is
  down, then ifup the interface.  isc-dhcp-client will fail claiming
  that:

  no link-local IPv6 address for eth0

  
  Alternately, ifupdown can be bypassed; for an interface that is currently 
down, do:

  $ sudo dhclient -6 -S eth0

  which will fail immediately (the -S param uses 'stateless' mode).

  [regression potential]

  changing isc-dhcp-client to perform PREINIT6 adds a new point of
  failure for doing DHCPv6, so there is the potential to break existing
  DHCPv6 clients if the preinit fails.  However, 'normal' DHCPv6 already
  does preinit6 - this only adds it to 'stateless' DHCPv6, so the
  failure potential should be limited to only users of 'stateless'
  DHCPv6, and those users are likely already seeing failures as
  described in this bug.

  [other info]

  This is related to bug 1633479

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

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

[Touch-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

[Gunnar Hjalmarsson]

** Changed in: ibus (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

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

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

[Touch-packages] [Bug 1738155] Re: Calling reboot or poweroff on a node-red snap is fail

[Jamie Strandboge]

Did you use 'snap connect' to connect the shutdown interface?

** Package changed: apparmor (Ubuntu) => snapd (Ubuntu)

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

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

Title:
  Calling reboot or poweroff on a node-red snap is fail

Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  OS:Ubuntu 16.04.3-amd64

  when I run command "reboot" or "poweroff" in the node-red snap.It is
  no longer effective.

  my snapcraft.yaml:

  name: nodered
  version: 1.00
  summary: A visual tool for wiring the Internet of Things
  description: Node-RED is a tool for wiring together hardware devices, APIs 
and online services in new and interesting ways.
  confinement: strict
  grade: stable

  apps:
red:
  daemon: simple
  command: bin/launch
  plugs:
- network-bind
- network
- network-observe

  parts:
red:
  plugin: nodejs
  node-packages:
- node-red
- node-red-dashboard
  filesets:
othermodules: [ -lib/node_modules/npm ]
  stage: [ $othermodules ]
settings:
  plugin: dump
  source: settings
  filesets:
settings:
  - .
  organize:
start.sh : bin/launch
  snap:
- .
  filesets:
all: [ . ]
  
  when I run "poweroff" in the node-red snap, the syslog will show:

  Dec 14 04:07:34 zy-PR-VR4 bor.red[1905]: 14 Dec 04:07:34 - [info] 
[exec:command]  poweroff
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.060923] kauditd_printk_skb: 25 
callbacks suppressed
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.060927] audit: type=1400 
audit(1513242454.177:329): apparmor="ALLOWED" operation="exec" 
profile="snap.bor.red" name="/bin/systemctl" pid=2453 comm="sh" 
requested_mask="x" denied_mask="x" fsuid=0 ouid=0 
target="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061474] audit: type=1400 
audit(1513242454.177:330): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061480] audit: type=1400 
audit(1513242454.181:331): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061483] audit: type=1400 
audit(1513242454.181:332): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061487] audit: type=1400 
audit(1513242454.181:333): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061489] audit: type=1400 
audit(1513242454.181:334): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red//null-/bin/systemctl" pid=2453 comm="poweroff" 
family="unix" sock_type="stream" protocol=0 requested_mask="send receive" 
denied_mask="send receive" addr=none peer_addr=none
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061493] audit: type=1400 
audit(1513242454.181:335): apparmor="ALLOWED" operation="file_inherit" 
profile="snap.bor.red" pid=2453 comm="poweroff" family="unix" 
sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send 
receive" addr=none peer_addr=none peer="snap.bor.red//null-/bin/systemctl"
  Dec 14 04:07:34 zy-PR-VR4 kernel: [  186.061496] audit: type=1400 
audit(1513242454.181:336): apparmor="ALLOWED" operation="file_mmap" 
profile="snap.bor.red//null-/bin/systemctl" name="/bin/systemctl" pid=2453 
comm="poweroff" requested_mask="rm" denied_mask="rm" fsuid=0 ouid=0

  it looks the command is runing in the ubuntu 16.04.3, but it does not 
effective.
  ---
  when I run "dmesg" in the node-red snap, the syslog will show:

  bor.red[1905]: 14 Dec 04:10:02 - [info] [exec:command]  dmesg
  Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739205] kauditd_printk_skb: 90 
callbacks suppressed
  Dec 14 04:10:02 zy-PR-VR4 kernel: [  334.739207] audit: type=1400 
audit(1513242602.837:463): apparmor="ALLOWED" operation="exec" 
profile="snap.bor.red" 

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

[Jamie Strandboge]

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

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

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

Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  actually i don't know

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

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

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

[Touch-packages] [Bug 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)

[Dan Streetman]

Additional note for this bug: this has been "fixed" upstream by adding a
--dad-wait-time parameter to dhclient.  However, that param defaults to
0, and also requires an update to the dhclient-script.linux that isc-
dhcp provides.  Debian has its own modified dhclient-script.linux,
slightly different than upstream, which is what we modified to fix this
bug.

The upstream bug is:
https://bugs.isc.org/Public/Bug/Display.html?id=36169

I don't personally recommend using the upstream isc-dhcp "fix" for this;
our change to the dhclient-script.linux maintained by debian/ubuntu is a
better fix, at least for the SRU releases; and our change doesn't
require tooling that uses dhclient to add a new --dad-wait-time
parameter.

** Bug watch added: bugs.isc.org/Public/ #36169
   https://bugs.isc.org/Public/Ticket/Display.html?id=36169

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

Title:
  dhclient does not wait for ipv6 dad (duplicate address detection)

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

Bug description:
  dhclient -6 does not wait for an interface go through duplicate address 
detection.
  As a result the following will almost always fail:

   $ dev=eth0
   $ ip link set down dev $dev
   $ dhclient -6 -1 -v eth0
   Internet Systems Consortium DHCP Client 4.3.3
   Copyright 2004-2015 Internet Systems Consortium.
   All rights reserved.
   For info, please visit https://www.isc.org/software/dhcp/

   Can't bind to dhcp address: Cannot assign requested address
   Please make sure there is no other dhcp server
   running and that there's no entry for dhcp or
   bootp in /etc/inetd.conf.   Also make sure you
   are not running HP JetAdmin software, which
   includes a bootp server.

   If you think you have received this message due to a bug rather
   than a configuration issue please read the section on submitting
   bugs on either our web page at www.isc.org or in the README file
   before submitting a bug.  These pages explain the proper
   process and the information we find helpful for debugging..
   $ echo $?
   1

  Related bugs:
   * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign 
requested address
   * bug 1633562: 'dhclient -6 -S' does not bring interface up 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: isc-dhcp-client 4.3.3-5ubuntu15
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:18:52 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (449 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764860] Re: dbus crashed with SIGABRT in _dbus_abort()

[Till Kamppeter]

** Information type changed from Private to Public

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

Title:
  dbus crashed with SIGABRT in _dbus_abort()

Status in cups package in Ubuntu:
  New

Bug description:
  bionic beaver @ dell xps12

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.7-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 16 20:42:40 2018
  ExecutablePath: /usr/lib/cups/notifier/dbus
  InstallationDate: Installed on 2018-03-11 (37 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Lpstat:
   device for HP_LaserJet_500_color_M551_2F183C_: 
ipp://BKPRT777.local:631/ipp/print
   device for HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: 
ipps://BKPRT777.local:443/ipp/print
   device for Lexmark-W820-Bravo: socket://10.42.9.152:9100
  MachineType: Dell Inc. XPS 12 9Q23
  Papersize: letter
  PpdFiles:
   Lexmark-W820-Bravo: Lexmark W820 PS
   HP_LaserJet_500_color_M551_2F183C_@BKPRT777.local: HP LaserJet 500 color 
M551, driverless, cups-filters 1.20.2
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct 
i8042.dumbkbd vt.handoff=1
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=e8186b16-2ca7-47a4-a261-792524adbc6b ro quiet splash i8042.direct 
i8042.dumbkbd vt.handoff=1
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
   __libc_start_main (main=0x55f0c84c81b0, argc=3, argv=0x7ffcaf592438, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcaf592428) at ../csu/libc-start.c:310
  Title: dbus crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (37 days ago)
  UserGroups:
   
  dmi.bios.date: 12/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.asset.tag: 0004061282
  dmi.board.name: 0520M8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 0004061282
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd12/07/2012:svnDellInc.:pnXPS129Q23:pvrA05:rvnDellInc.:rn0520M8:rvrA00:cvnDellInc.:ct8:cvrA05:
  dmi.product.family: 103C_5335KV
  dmi.product.name: XPS 12 9Q23
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1761708] Re: QWebEngineView crashes

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.9.5+dfsg-
0ubuntu1

---
qtbase-opensource-src (5.9.5+dfsg-0ubuntu1) bionic; urgency=medium

  [ Simon Quigley ]
  * New upstream release.
- Refresh patches.
- Update symbols from build logs.
  * Bump independent build dependencies.
  * Bump the virtual ABI package from qtbase-abi-5-9-4 to qtbase-abi-5-9-5.
  * Fix loading OpenGL library when libGL.so is missing (LP: #1761708).
- fix-loading-OpenGL-when-symlink-missing.patch
- QTBUG-67537

  [ Dmitry Shachnev ]
  * Update list of Qt WebKit build-dependencies in debian/README.source.

 -- Simon Quigley   Thu, 12 Apr 2018 18:24:40 -0500

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  QWebEngineView crashes

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  I have KUbuntu 18.04 with the latest updates. I installed all pyqt3
  stuff plus python3-pyqt5.qtwebengine and tried to execute a tiny
  webengine demo (attached):

  $ python3 browser.py
  Segmentation fault (core dumped)
  [1:1:0100/00.971262:ERROR:broker_posix.cc(41)] Invalid node channel 
message

  Please see the attached core file & gdb bt

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

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

[Touch-packages] [Bug 1436302] Re: python3.4 segmentation fault while running unattended-upgrade

[Balint Reczey]

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

I believe this it triggered by u-u using python-apt's API the wrong way
hitting the same memory management issue in in python-apt as the one
reported in the duplicate bug.

** This bug has been marked a duplicate of bug 1737441
   
/usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string

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

Title:
  python3.4 segmentation fault while running unattended-upgrade

Status in python-apt package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  We run 'unattended-upgrade -d' from cron and have seen regular core
  dumps. Below is some gdb output for one case:

  (gdb) where
  #0 _int_malloc (av=av@entry=0x7fd4362de760 , 
bytes=bytes@entry=193) at malloc.c:3489
  #1 0x7fd435fa17e1 in _int_realloc (av=0x7fd4362de760 , 
oldp=0xd6fe30, oldsize=144, nb=208) at malloc.c:4286
  #2 0x7fd435fa2fc9 in _GI__libc_realloc (oldmem=0xd6fe40, bytes=200) at 
malloc.c:3029
  #3 0x004851cd in PyMem_Realloc (new_size=, 
ptr=) at ../Objects/obmalloc.c:308
  #4 list_resize.7991 (self=0x7fd436549e48, newsize=17) at 
../Objects/listobject.c:63
  #5 0x00485269 in app1 (v=0x7fd435306288, self=0x7fd436549e48) at 
../Objects/listobject.c:294
  #6 PyList_Append (op=op@entry=0x7fd436549e48, 
newitem=newitem@entry=0x7fd435306288) at ../Objects/listobject.c:306
  #7 0x005bf7a9 in PyImport_Cleanup () at ../Python/import.c:464
  #8 0x005bf945 in Py_Finalize.part.6.32879 () at 
../Python/pythonrun.c:616
  #9 0x0060cb12 in Py_Finalize () at ../Python/pythonrun.c:564
  #10 Py_Main (argc=argc@entry=3, argv=argv@entry=0xae6010) at 
../Modules/main.c:771
  #11 0x0041ec0d in main (argc=3, argv=) at 
../Modules/python.c:69

  Note that gdb always complains that the coredump may not match the
  binary I provided. However, I'm pretty sure I got the right one.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python3-minimal 3.4.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Wed Mar 25 11:57:03 2015
  Ec2AMI: ami-254ad452
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1b
  Ec2InstanceType: r3.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

[Sebastien Bacher]

The use of dh-translations was removed without explanation in that upload
http://launchpadlibrarian.net/227995812/ibus_1.5.10-1ubuntu1_1.5.11-1ubuntu1.diff.gz

I just did an upload adding the build-depends and rules translations use

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

** Changed in: ibus (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

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

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

[Touch-packages] [Bug 1764858] Re: Can't update / install / delete packages

[Julian Andres Klode]

I'm sorry for you, but your upgrade seems to have gone wrong. apt (well,
libapt-pkg5.0) certainly depends on libzstd1, so it should be there -
these kind of dependencies get created automatically.

Please run apport-collect 1764858 or attach at least
/var/log/apt/term.log; or read it and see yourself what is broken.



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

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

Title:
  Can't update / install / delete packages

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  After todays upgrade:

  vasily@vasily-desktop:~$ sudo apt-get update
  [sudo] пароль для vasily: 
  apt-get: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory

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

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

[Touch-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

[Gunnar Hjalmarsson]

Or, even better, a real upload which fixes the issue also going forward.
:) Sebastien let me know on IRC what's needed, so I wrote a patch.

** Patch added: "ibus_lp1764161.debdiff"
   
https://bugs.launchpad.net/ubuntu-translations/+bug/1764161/+attachment/5120061/+files/ibus_lp1764161.debdiff

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

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

** Changed in: ibus (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Tags added: patch

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  Fix Committed

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

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

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

[Touch-packages] [Bug 1764797] Re: [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable (main)

[Balint Reczey]

I uploaded the merged package to 
https://launchpad.net/~rbalint/+archive/ubuntu/scratch and also ran autopkgtest 
which is passing:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-rbalint-scratch/bionic/amd64/u/unattended-upgrades/20180417_174816_81c82@/log.gz

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

Title:
  [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Feature Freeze Justification
  

  Latest unattended-upgrades upload fixed multiple serious issues and
  includes a few minor fixes which are not worth skipping.

  Most notably it now runs upgrade-between-snapshots autopkgtest with
  updated python-apt thus regressions can block migration to release
  pocket and fixes frequent crashes due to using python-apt's API in a
  wrong way.

  Changes:
   unattended-upgrades (1.1ubuntu1) bionic; urgency=medium
   .
     * Merge from Debian unstable (LP: #1764797)
   - Remaining changes:
     - unattended-upgrades: Do not automatically upgrade the development
   release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
   - Dropped changes, included in Debian:
     - Rename d/NEWS.Debian to d/NEWS to have it shipped
     - Fix typo in NEWS file
     - d/rules: Exclude mypy cache from source package.
   .
   unattended-upgrades (1.1) unstable; urgency=medium
   .
     [ cgail914 ]
     * Update 50unattended-upgrades.Raspbian
   added a semi-column sign on line 86 to facilitate uncommenting the line
   for users and not end up with an error message when running
   unattended-upgrades. And make the whole file consistent.
   .
     [ Tobias Bannert ]
     * completed german translation
   .
     [ Simon McVittie ]
     * d/rules: Exclude mypy cache from source package.
   .
     [ Julian Andres Klode ]
     * Do not reuse old apt.Version objects after reopening cache (LP: #1737441)
   .
     [ Balint Reczey ]
     * Rename d/NEWS.Debian to d/NEWS to have it shipped
     * Fix typo in NEWS file
     * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages 
option
     * Set UnattendedUpgradesCache.allowed_origins before calling
   apt.Cache.__init__()
     * Find package candidates to adjust sweeping through all packages only 
once.
   Later reuse the list candidates and filter out packages installed in the
   meantime. Thanks to Julian Andres Klode for the original patch
     * Use updated python-apt in upgrade-between-snapshots test
     * upgrade-between-snapshots: Mount /proc, too, in the chroot.
   Also clean up chroot properly on exit.
     * upgrade-between-snapshots: Use http_proxy environment variable in chroot,
   too
     * upgrade-between-snapshots: Remove packages installed as the side-effect 
of
   updating apt and python-apt
     * Ignore errors from compiling backported packages
     * Make is_autoremove_valid() nondestructive.
   Also fix autoremoval of packages when one package can't be removed and
   keeps back other package removals due to missing cache.clear()
     * Fix tracking removed packages
     * Suggest default-mta | mail-transport-agent to keep Lintian happy
   .
     [ Michael Vogt ]
     * unattanded-upgrades: refactor get_candidates_to_adjust() to
   adjust_candidates()

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

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

[Touch-packages] [Bug 1753431] Re: bonding does not works

[Mathieu Trudel-Lapierre]

Your original config in comment #1 is correct: you must specify the
underlying devices, because those names are matched later for
"interfaces:" in the bond config.

The issue with 802.3ad is likely a driver issue or a bug in systemd; the
right mode needs to be set by networkd (which may require rebooting
rather than just running 'netplan apply').

Reassigning to systemd for investigation, we do have unit / autopkg
tests running for netplan which look like 802.3ad is correctly set, but
they do not interact with other network devices (there are no other
network devices in the test environment).

Furthermore, is anything beyond the physical network adapters configured
to used 802.3ad? This is important for the bonding to work.

** Package changed: nplan (Ubuntu) => systemd (Ubuntu)

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

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

Title:
  bonding does not works

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm working on libvirt/kvm hypervisor
  I user 2 bondind interfaces:
  eno1 + eno2 => bond0 via "netplan" ("service" interface for hypervisor)
  eno3 + eno4 => bond1 via "ifupdown" ("virtualization" interface for libvirt)

  Since last upgrade (today), i got "Warning, no 802.3ad response from
  the link partner ..." with dmesg, bonding doesn't longer works with
  "netplan" and "ifupdown".

  Kernel problem ? ifenslave problem ?

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

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

[Touch-packages] [Bug 1764858] [NEW] Can't update / install / delete packages

[Vasily]

Public bug reported:

Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

After todays upgrade:

vasily@vasily-desktop:~$ sudo apt-get update
[sudo] пароль для vasily: 
apt-get: error while loading shared libraries: libzstd.so.1: cannot open shared 
object file: No such file or directory

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

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

Title:
  Can't update / install / delete packages

Status in apt package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  After todays upgrade:

  vasily@vasily-desktop:~$ sudo apt-get update
  [sudo] пароль для vasily: 
  apt-get: error while loading shared libraries: libzstd.so.1: cannot open 
shared object file: No such file or directory

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

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

[Touch-packages] [Bug 1753431] [NEW] bonding does not works

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm working on libvirt/kvm hypervisor
I user 2 bondind interfaces:
eno1 + eno2 => bond0 via "netplan" ("service" interface for hypervisor)
eno3 + eno4 => bond1 via "ifupdown" ("virtualization" interface for libvirt)

Since last upgrade (today), i got "Warning, no 802.3ad response from the
link partner ..." with dmesg, bonding doesn't longer works with
"netplan" and "ifupdown".

Kernel problem ? ifenslave problem ?

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

-- 
bonding does not works
https://bugs.launchpad.net/bugs/1753431
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found

[Drew Freiberger]

perhaps a proper fix is for ubuntu-sso-client to release a new python-
ubuntu-sso-client package in bionic that doesn't include this UbuntuOne-
Go_Daddy_Class_2_CA.pem now that ca-certificates package has the CA.

However, I'd still like to see duplicate certs not causing ca-
certificates.crt to be deleted.

** Also affects: ubuntu-sso-client
   Importance: Undecided
   Status: New

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

Title:
  Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to
  be removed if duplicate certs found

Status in Ubuntu Single Sign On Client:
  New
Status in ca-certificates package in Ubuntu:
  New

Bug description:
  The certificate /usr/share/ca-
  certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-
  certificates is conflicting with /etc/ssl/certs/UbuntuOne-
  Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client.

  This results in the postinst trigger for ca-certificates to remove the
  /etc/ssl/certs/ca-certificates.crt file.  This happens because the
  postinst trigger runs update-ca-certificates --fresh.

  If I run update-ca-certificates without the --fresh flag, the conflict
  is a non-issue and the ca-certificates.crt file is restored.

  If I understand some of the postinst code correctly, --fresh should
  only be run if called directly or if upgrading from a ca-certificates
  version older than 2011.

  Running bionic with daily -updates channel and ran into this this
  morning due to the release of ca-certificates version 20180409.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions

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

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Mark Foster]

Still an issue in bionic final beta

To unlock root partition, and maybe others like swap, run `cryptroot-
unlock`


BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

# cryptroot-unlock
ps: invalid option -- 'e'
BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu3) multi-call binary.

Usage: ps

Show list of processes

w   Wide output
l   Long output
/bin/cryptroot-unlock: line 186: usleep: not found

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Confirmed
Status in cryptsetup package in Ubuntu:
  Confirmed

Bug description:
  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

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

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

[Touch-packages] [Bug 1726912] Re: fails to keep dhcplease

[Mathieu Trudel-Lapierre]

This would be a systemd-networkd bug, which I suspect might have already
been fixed too. Reassigning to systemd.

** Package changed: nplan (Ubuntu) => systemd (Ubuntu)

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

Title:
  fails to keep dhcplease

Status in systemd package in Ubuntu:
  New

Bug description:
  Not 100% sure if this is a networkd bug or a nplan bug, but...

  On new install of 17.10 systemd-networkd loops with:

  Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service...
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained IPv6LL
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed
  Oct 23 16:45:24 san-jose systemd[1]: Started Network Service.
  Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
128.30.3.94/24 via 12
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
128.30.3.94/24 via 12
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Configured
  Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
  Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost

  that is the correct interface and address.

  If I manually run 'dhclient nep129s0f0' the lease sticks and
  'journalctl -fu systemd-networkd' shows:

  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
128.30.3.94/24 via 12
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Configured

  installer generated 01-netcfg.yaml:

  network:
version: 2
renderer: networkd
ethernets:
  enp129s0f0:
dhcp4: yes

  root@host:~#  lsb_release -rd;uname -r ; dpkg -l nplan  systemd
  Description:  Ubuntu 17.10
  Release:  17.10
  4.13.0-16-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   VersionArchitecture   Description
  
+++-==-==-==-=
  ii  nplan  0.30   amd64  YAML network 
configuration abstraction fo
  ii  systemd234-2ubuntu12  amd64  system and service 
manager

  
  my current workaround:

  root@host:~# cat /etc/rc.local
  #!/bin/sh
  dhclient enp129s0f0

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

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

[Touch-packages] [Bug 1764848] [NEW] Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found

[Drew Freiberger]

Public bug reported:

The certificate /usr/share/ca-
certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-certificates
is conflicting with /etc/ssl/certs/UbuntuOne-Go_Daddy_Class_2_CA.pem
from package python-ubuntu-sso-client.

This results in the postinst trigger for ca-certificates to remove the
/etc/ssl/certs/ca-certificates.crt file.  This happens because the
postinst trigger runs update-ca-certificates --fresh.

If I run update-ca-certificates without the --fresh flag, the conflict
is a non-issue and the ca-certificates.crt file is restored.

If I understand some of the postinst code correctly, --fresh should only
be run if called directly or if upgrading from a ca-certificates version
older than 2011.

Running bionic with daily -updates channel and ran into this this
morning due to the release of ca-certificates version 20180409.

** Affects: ubuntu-sso-client
 Importance: Undecided
 Status: New

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

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

Title:
  Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to
  be removed if duplicate certs found

Status in Ubuntu Single Sign On Client:
  New
Status in ca-certificates package in Ubuntu:
  New

Bug description:
  The certificate /usr/share/ca-
  certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca-
  certificates is conflicting with /etc/ssl/certs/UbuntuOne-
  Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client.

  This results in the postinst trigger for ca-certificates to remove the
  /etc/ssl/certs/ca-certificates.crt file.  This happens because the
  postinst trigger runs update-ca-certificates --fresh.

  If I run update-ca-certificates without the --fresh flag, the conflict
  is a non-issue and the ca-certificates.crt file is restored.

  If I understand some of the postinst code correctly, --fresh should
  only be run if called directly or if upgrading from a ca-certificates
  version older than 2011.

  Running bionic with daily -updates channel and ran into this this
  morning due to the release of ca-certificates version 20180409.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions

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

[Touch-packages] [Bug 1364173] Re: Xsession sourced scripts shouldn't be run using user's default shell

[Bug Watch Updater]

** Changed in: kdebase-workspace
   Status: New => Unknown

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

Title:
  Xsession sourced scripts shouldn't be run using user's default shell

Status in KDE Base Workspace:
  Unknown
Status in kde-workspace package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Recently I encountered a problem that my input method malfunctions
  because the environmental variables are wrongly set(which is, fully
  configured using im-config), after hours of debugging I found that
  it's Z-shell(my current default shell)'s bug that prematurely quits
  before the Xsession.d im-config input method configure script
  completes.

  The problem is, /etc/X11/Xsession (and all the Xsession.d scripts it sourced) 
**shouldn't** be run in Z-shell.  Patching /etc/kde4/kdm/Xsession # invoke 
global X session script. code from
  . /etc/X11/Xsession
  to
  /etc/X11/Xsession

  workarounded the issue (however I have no idea why).  Switching to
  other display managers instead of KDM worked also)

  Reproducible: Always

  Steps to Reproduce:
  Currently there's no simple reproduce method as another software(zsh)'s bug 
involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1364173/+subscriptions

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

[Touch-packages] [Bug 1726912] [NEW] fails to keep dhcplease

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Not 100% sure if this is a networkd bug or a nplan bug, but...

On new install of 17.10 systemd-networkd loops with:

Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service...
Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained IPv6LL
Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed
Oct 23 16:45:24 san-jose systemd[1]: Started Network Service.
Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
128.30.3.94/24 via 12
Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost
Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
128.30.3.94/24 via 12
Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Configured
Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost

that is the correct interface and address.

If I manually run 'dhclient nep129s0f0' the lease sticks and 'journalctl
-fu systemd-networkd' shows:

Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
128.30.3.94/24 via 12
Oct 23 16:45:34 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Configured

installer generated 01-netcfg.yaml:

network:
  version: 2
  renderer: networkd
  ethernets:
enp129s0f0:
  dhcp4: yes

root@host:~#  lsb_release -rd;uname -r ; dpkg -l nplan  systemd
Description:Ubuntu 17.10
Release:17.10
4.13.0-16-generic
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionArchitecture   Description
+++-==-==-==-=
ii  nplan  0.30   amd64  YAML network configuration 
abstraction fo
ii  systemd234-2ubuntu12  amd64  system and service manager


my current workaround:

root@host:~# cat /etc/rc.local
#!/bin/sh
dhclient enp129s0f0

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

-- 
fails to keep dhcplease
https://bugs.launchpad.net/bugs/1726912
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd 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

Re: [Touch-packages] [Bug 905022] Re: No sounds from headphones on ThinkPad T420

[Chris Kirby]

Wow, this is a blast from the past. That bug was probably one or two
machines ago and I no longer have the hardware to test / reproduce it.
This can be closed.

> On Apr 17, 2018, at 10:37, Rolf Leggewie <905...@bugs.launchpad.net> wrote:
> 
> Sorry for the long delay.  Is this something that still affects Xenial
> or later?
> 
> ** Changed in: alsa-driver (Ubuntu)
>   Status: Confirmed => Incomplete
> 
> ** Changed in: alsa-driver (Ubuntu)
> Assignee: (unassigned) => Rolf Leggewie (r0lf)
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/905022
> 
> Title:
>  No sounds from headphones on ThinkPad T420
> 
> Status in alsa-driver package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  Long time reader, first time poster :-)
> 
>  I cannot get sound from the analog headphone/microphone port on my
>  Lenovo ThinkPad T420. Based on Google searches I have fiddled with the
>  snd-hda-intel options in /etc/modprobe.d/alsa-base.conf as follows:
> 
>  - Set model=thinkpad resulting in no sound through the headphone jack
>  and the loss of the headphone playback connector in alsamixer.
>  Unsurprisingly this results in no option to set or configure the
>  analog headphone connector in the sound settings applet and/or
>  pavucontrol.
> 
>  - Set model=generic with the same results as above.
> 
>  - Set model=auto which resulted in the appearance of the headphone
>  connector (progress!) but I still get no sound from the headphones
>  when I select the connector and/or mute the speakers through
>  alsamixer.
> 
>  I also tried re-configuring the alsa-driver package to include verbose
>  debugging support but ran into a whole lot of hassles (some of the
>  source references smp_lock.h which is no more in kernel 3+, macro
>  conflicts with system includes, etc.) when I tried to build it with
>  module-assistant. I also tried to build it from the latest tarball
>  from the alsa project with mixed results and ultimately no joy.
> 
>  Most problems of this kind I've seen tend to fall into 3 categories:
>  (i) fixed by changing snd-hda-intel options, (ii) fixed through some
>  sequence of random updates, (iii) sitting in silence. I'm hoping to be
>  a bit more proactive.
> 
>  The output of alsa-info.sh is attached.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/905022/+subscriptions

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

Title:
  No sounds from headphones on ThinkPad T420

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Long time reader, first time poster :-)

  I cannot get sound from the analog headphone/microphone port on my
  Lenovo ThinkPad T420. Based on Google searches I have fiddled with the
  snd-hda-intel options in /etc/modprobe.d/alsa-base.conf as follows:

  - Set model=thinkpad resulting in no sound through the headphone jack
  and the loss of the headphone playback connector in alsamixer.
  Unsurprisingly this results in no option to set or configure the
  analog headphone connector in the sound settings applet and/or
  pavucontrol.

  - Set model=generic with the same results as above.

  - Set model=auto which resulted in the appearance of the headphone
  connector (progress!) but I still get no sound from the headphones
  when I select the connector and/or mute the speakers through
  alsamixer.

  I also tried re-configuring the alsa-driver package to include verbose
  debugging support but ran into a whole lot of hassles (some of the
  source references smp_lock.h which is no more in kernel 3+, macro
  conflicts with system includes, etc.) when I tried to build it with
  module-assistant. I also tried to build it from the latest tarball
  from the alsa project with mixed results and ultimately no joy.

  Most problems of this kind I've seen tend to fall into 3 categories:
  (i) fixed by changing snd-hda-intel options, (ii) fixed through some
  sequence of random updates, (iii) sitting in silence. I'm hoping to be
  a bit more proactive.

  The output of alsa-info.sh is attached.

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

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

[Touch-packages] [Bug 1764312] Re: fails to start in Bionic

[Tom Chiverton]

sudo: apparmor_parser: command not found

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

Title:
  fails to start in Bionic

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  $ systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 
10min ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 635 (code=exited, status=123)

  Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]:...fail!
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization.

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

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

[Touch-packages] [Bug 1764312] Re: fails to start in Bionic

[Tom Chiverton]

installed it, and it says

$ sudo apparmor_parser --replace /etc/apparmor.d/usr.lib.snapd.snap-confine.real
File /etc/apparmor.d/usr.lib.snapd.snap-confine.real not found, skipping...

$ sudo systemctl start apparmor
$ sudo systemctl status apparmor
● apparmor.service - AppArmor initialization
   Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Tue 2018-04-17 20:06:52 BST; 4s ago
 Docs: man:apparmor(7)
   http://wiki.apparmor.net/
  Process: 3101 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=0/SUCCESS)
 Main PID: 3101 (code=exited, status=0/SUCCESS)

Apr 17 20:06:51 wopr.house systemd[1]: Starting AppArmor initialization...
Apr 17 20:06:51 wopr.house apparmor[3101]:  * Starting AppArmor profiles
Apr 17 20:06:51 wopr.house apparmor[3101]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
Apr 17 20:06:51 wopr.house apparmor[3101]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox-esr
Apr 17 20:06:52 wopr.house apparmor[3101]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
Apr 17 20:06:52 wopr.house apparmor[3101]:...done.
Apr 17 20:06:52 wopr.house systemd[1]: Started AppArmor initialization.

so somehow it was part installed

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

Title:
  fails to start in Bionic

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  $ systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 
10min ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 635 (code=exited, status=123)

  Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]:...fail!
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization.

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

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

[Touch-packages] [Bug 1764312] Re: fails to start in Bionic

[Tom Chiverton]

$ dpkg -l|grep appar
rc  apparmor2.12-4ubuntu4   
amd64user-space parser utility for AppArmor
ii  libapparmor1:amd64  2.12-4ubuntu4   
amd64changehat AppArmor library

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

Title:
  fails to start in Bionic

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  $ systemctl status apparmor
  ● apparmor.service - AppArmor initialization
 Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 
10min ago
   Docs: man:apparmor(7)
 http://wiki.apparmor.net/
Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 635 (code=exited, status=123)

  Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]:...fail!
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization.

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

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

[Touch-packages] [Bug 1764827] [NEW] sometimes, maybe after pluging in headphones, there is no sound. Sound goes thrue , , dummy output''

[Lukas Birstonas]

Public bug reported:

No sound. Sound goes to dummy output

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lukasbirstonas   1259 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 17 21:25:57 2018
InstallationDate: Installed on 2017-12-02 (136 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Front
Title: [20CD0034UK, Conexant CX20751/2, Green Headphone Out, Front] Pulseaudio 
fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GQET35WW (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CD0034UK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50518 Std
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGQET35WW(1.15):bd04/21/2014:svnLENOVO:pn20CD0034UK:pvrThinkPadS1Yoga:rvnLENOVO:rn20CD0034UK:rvrSDK0E50518Std:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad S1 Yoga
dmi.product.name: 20CD0034UK
dmi.product.version: ThinkPad S1 Yoga
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  sometimes, maybe after pluging in headphones, there is no sound. Sound
  goes thrue ,,dummy output''

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound. Sound goes to dummy output

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lukasbirstonas   1259 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 21:25:57 2018
  InstallationDate: Installed on 2017-12-02 (136 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Title: [20CD0034UK, Conexant CX20751/2, Green Headphone Out, Front] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET35WW (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CD0034UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50518 Std
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET35WW(1.15):bd04/21/2014:svnLENOVO:pn20CD0034UK:pvrThinkPadS1Yoga:rvnLENOVO:rn20CD0034UK:rvrSDK0E50518Std:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad S1 Yoga
  dmi.product.name: 20CD0034UK
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1764042] Re: wifi crashes in ubuntu 16.04 lts xenial

[israel oluwole]

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/network-manager/+question/668023

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

Title:
  wifi crashes in ubuntu 16.04 lts xenial

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Good day,
  I am a new ubuntu user and I've been finding a solution everywhere to this 
issue:
  I run ubuntu (studio) 16.04 lts, code name: xenial dual booted with windows 8 
on Hp notebook 15. When I first installed ubuntu, hotspot from my BlackBerry 
q10 connects fine but suddenly it stopped and every time i connect it pops up 
the dialog box: wifi authentication required by wifi network and expects me to 
retype a password that is already correct!
  I have tried reinstalling network manager, adding [device] wifi-rand*... to 
network*.conf and so on and rebooted over and again. Nothing has changed yet. 
The same applies to my bluetooth too (it was okay suddenly it changed)

  I need help quick, I need my pc for an imminent exam. Thank you

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

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

[Touch-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

[Gunnar Hjalmarsson]

Not sure. Possibly a no-change rebuild would make a difference now when
an up-to-date template is in. But for that we need a developer who has
time to do it by tomorrow. You may want to wait another day before doing
it manually.

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  New

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

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

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

[Touch-packages] [Bug 1760128] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Jacopo Losi]

I tried:

sudo apt-get -f install

and it worked just fine. I hope this is useful.
Have a nice day,
Jacopo

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  Fix Released
Status in avahi source package in Xenial:
  Fix Committed

Bug description:
  Ubuntu Update 30.03.18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 16:32:50 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-31 (788 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160131)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764797] Re: [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable (main)

[Hans Joachim Desserud]

** Tags added: needs-debian-merge upgrade-software-version

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

Title:
  [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Feature Freeze Justification
  

  Latest unattended-upgrades upload fixed multiple serious issues and
  includes a few minor fixes which are not worth skipping.

  Most notably it now runs upgrade-between-snapshots autopkgtest with
  updated python-apt thus regressions can block migration to release
  pocket and fixes frequent crashes due to using python-apt's API in a
  wrong way.

  Changes:
   unattended-upgrades (1.1ubuntu1) bionic; urgency=medium
   .
     * Merge from Debian unstable (LP: #1764797)
   - Remaining changes:
     - unattended-upgrades: Do not automatically upgrade the development
   release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
   - Dropped changes, included in Debian:
     - Rename d/NEWS.Debian to d/NEWS to have it shipped
     - Fix typo in NEWS file
     - d/rules: Exclude mypy cache from source package.
   .
   unattended-upgrades (1.1) unstable; urgency=medium
   .
     [ cgail914 ]
     * Update 50unattended-upgrades.Raspbian
   added a semi-column sign on line 86 to facilitate uncommenting the line
   for users and not end up with an error message when running
   unattended-upgrades. And make the whole file consistent.
   .
     [ Tobias Bannert ]
     * completed german translation
   .
     [ Simon McVittie ]
     * d/rules: Exclude mypy cache from source package.
   .
     [ Julian Andres Klode ]
     * Do not reuse old apt.Version objects after reopening cache (LP: #1737441)
   .
     [ Balint Reczey ]
     * Rename d/NEWS.Debian to d/NEWS to have it shipped
     * Fix typo in NEWS file
     * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages 
option
     * Set UnattendedUpgradesCache.allowed_origins before calling
   apt.Cache.__init__()
     * Find package candidates to adjust sweeping through all packages only 
once.
   Later reuse the list candidates and filter out packages installed in the
   meantime. Thanks to Julian Andres Klode for the original patch
     * Use updated python-apt in upgrade-between-snapshots test
     * upgrade-between-snapshots: Mount /proc, too, in the chroot.
   Also clean up chroot properly on exit.
     * upgrade-between-snapshots: Use http_proxy environment variable in chroot,
   too
     * upgrade-between-snapshots: Remove packages installed as the side-effect 
of
   updating apt and python-apt
     * Ignore errors from compiling backported packages
     * Make is_autoremove_valid() nondestructive.
   Also fix autoremoval of packages when one package can't be removed and
   keeps back other package removals due to missing cache.clear()
     * Fix tracking removed packages
     * Suggest default-mta | mail-transport-agent to keep Lintian happy
   .
     [ Michael Vogt ]
     * unattanded-upgrades: refactor get_candidates_to_adjust() to
   adjust_candidates()

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

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

[Touch-packages] [Bug 831022] Re: avahi daemon erroneously assumes host name conflicts (and causes more trouble then)

[Brian Murray]

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

** Changed in: avahi
 Remote watch: github.com/lathiat/avahi/issues #176 => 
github.com/lathiat/avahi/issues #117

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

Title:
  avahi daemon erroneously assumes host name conflicts (and causes more
  trouble then)

Status in Avahi:
  Unknown
Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Hi,

  i am running the server edition of Ubuntu LTS on a HP Proliant server.
  That avahi daemon is driving me crazy.

  The server is named Server1 , retrieves it's IP address
  pseudostatically from a DHCP server, and announces several of its
  services through avahi (e.g. offering print services to iPads, that's
  why Avahi is needed).

  every now and then (not always) avahi daemon claims to have detected a
  name collision at boot time. It then logs

  Aug 22 13:09:40 Server1 avahi-daemon[1520]: Host name conflict,
  retrying with 

  and uses Server1-2 as it's name, causing even the DHCP-Server to apply
  with a different host name, thus causing a new IP address to be
  assigned. This avahi daemon is breaking my network structure and does
  not even tell in the logs, where the conflict came from or what made
  the daemon believe that there was a conflict.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: avahi-daemon 0.6.25-1ubuntu6.2
  ProcVersionSignature: Ubuntu 2.6.32-33.72-server 2.6.32.41+drm33.18
  Uname: Linux 2.6.32-33-server x86_64
  Architecture: amd64
  Date: Mon Aug 22 13:24:06 2011
  InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.2)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  SourcePackage: avahi

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

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

[Touch-packages] [Bug 1760128] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Łukasz Zemczak]

Hello Rolf, or anyone else affected,

Accepted avahi into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/avahi/0.6.32~rc+dfsg-
1ubuntu2.2 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-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, without details of
your testing we will not be able to proceed.

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

** Changed in: avahi (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  Fix Released
Status in avahi source package in Xenial:
  Fix Committed

Bug description:
  Ubuntu Update 30.03.18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 16:32:50 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-31 (788 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160131)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Pioterus]

This bug forced me to search for ubuntu alternatives. I'm looking
currently at Manjaro.

About commenting out dns=dnsmasq.
Doing so on laptop (LAN and wifi connections active) has this drawback:
ping my_comp_name
.unresloved name
adding my_comp_name to /etc/hosts  makes the ping my_comp_name  working again, 
but 
unplagging RJ45, system changes automatically to wifi connetcion (other IP) and 
ping my_comp_name again is not working. With dnsmasq enabled the system nicely 
deals with name resolution so there are no such issues. What happens when the 
host name resolution is not working ok? System behaves oddly (it delays some 
operations in many situations).

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1747411] Re: Change of default database file format to SQL

[Timo Aaltonen]

and freeipa doesn't use libapache2-mod-nss either anymore

** Changed in: libapache2-mod-nss (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Change of default database file format to SQL

Status in certmonger package in Ubuntu:
  Fix Released
Status in corosync package in Ubuntu:
  New
Status in dogtag-pki package in Ubuntu:
  Fix Released
Status in freeipa package in Ubuntu:
  Fix Released
Status in libapache2-mod-nss package in Ubuntu:
  Won't Fix
Status in nss package in Ubuntu:
  New

Bug description:
  nss in version 3.35 in upstream changed [2] the default file format [1] (if 
no explicit one is specified).
  For now we reverted that change in bug 1746947 until all packages depending 
on it are ready to work with that correctly.

  This bug here is about to track when the revert can be dropped.
  Therefore we list all known-to-be-affected packages and once all are resolved 
this can be dropped.

  [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
  [2]: 
https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

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

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

[Touch-packages] [Bug 1747411] Re: Change of default database file format to SQL

[Timo Aaltonen]

freeipa in bionic-proposed doesn't use nss db's anymore

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

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

Title:
  Change of default database file format to SQL

Status in certmonger package in Ubuntu:
  Fix Released
Status in corosync package in Ubuntu:
  New
Status in dogtag-pki package in Ubuntu:
  Fix Released
Status in freeipa package in Ubuntu:
  Fix Released
Status in libapache2-mod-nss package in Ubuntu:
  Won't Fix
Status in nss package in Ubuntu:
  New

Bug description:
  nss in version 3.35 in upstream changed [2] the default file format [1] (if 
no explicit one is specified).
  For now we reverted that change in bug 1746947 until all packages depending 
on it are ready to work with that correctly.

  This bug here is about to track when the revert can be dropped.
  Therefore we list all known-to-be-affected packages and once all are resolved 
this can be dropped.

  [1]: https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql
  [2]: 
https://github.com/nss-dev/nss/commit/33b114e38278c4ffbb6b244a0ebc9910e5245cd3

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

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

[Touch-packages] [Bug 1764803] [NEW] failed install of nvidia-drivers-390

[Dean ford]

Public bug reported:

insulation method using ubuntu-driver, blacklisting nouveau.
also tried with the ppa added and driver from nvidia.com. All failed which 
hasnt happed before when installing (K)ubuntu 

Black screen after reboot
GPU running hot
Kubuntu 18.04 final beta

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
BootLog: /dev/sda1: clean, 226700/2428272 files, 2097944/9707520 blocks
Date: Tue Apr 17 17:30:25 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0504]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 620M/630M/635M/640M 
LE] [1025:0505]
InstallationDate: Installed on 2018-04-12 (4 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: Acer Aspire 5755G
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=7ce01f2b-9fff-47af-a177-4bb10ec8e87f ro acpi_osi=Linux 
acpi_backlight=vendor quiet nomodset splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JV51_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.15
dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/07/2011:svnAcer:pnAspire5755G:pvrV1.15:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.15:
dmi.product.name: Aspire 5755G
dmi.product.version: V1.15
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  failed install of nvidia-drivers-390

Status in xorg package in Ubuntu:
  New

Bug description:
  insulation method using ubuntu-driver, blacklisting nouveau.
  also tried with the ppa added and driver from nvidia.com. All failed which 
hasnt happed before when installing (K)ubuntu 

  Black screen after reboot
  GPU running hot
  Kubuntu 18.04 final beta

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: /dev/sda1: clean, 226700/2428272 files, 2097944/9707520 blocks
  Date: Tue Apr 17 17:30:25 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA 

[Touch-packages] [Bug 1760128] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Brian Murray]

** Tags removed: bugpattern-needed

** Tags added: bugpattern-written

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

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

Bug description:
  Ubuntu Update 30.03.18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 16:32:50 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-01-31 (788 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160131)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 905022] Re: No sounds from headphones on ThinkPad T420

[Rolf Leggewie]

Sorry for the long delay.  Is this something that still affects Xenial
or later?

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => Rolf Leggewie (r0lf)

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

Title:
  No sounds from headphones on ThinkPad T420

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Long time reader, first time poster :-)

  I cannot get sound from the analog headphone/microphone port on my
  Lenovo ThinkPad T420. Based on Google searches I have fiddled with the
  snd-hda-intel options in /etc/modprobe.d/alsa-base.conf as follows:

  - Set model=thinkpad resulting in no sound through the headphone jack
  and the loss of the headphone playback connector in alsamixer.
  Unsurprisingly this results in no option to set or configure the
  analog headphone connector in the sound settings applet and/or
  pavucontrol.

  - Set model=generic with the same results as above.

  - Set model=auto which resulted in the appearance of the headphone
  connector (progress!) but I still get no sound from the headphones
  when I select the connector and/or mute the speakers through
  alsamixer.

  I also tried re-configuring the alsa-driver package to include verbose
  debugging support but ran into a whole lot of hassles (some of the
  source references smp_lock.h which is no more in kernel 3+, macro
  conflicts with system includes, etc.) when I tried to build it with
  module-assistant. I also tried to build it from the latest tarball
  from the alsa project with mixed results and ultimately no joy.

  Most problems of this kind I've seen tend to fall into 3 categories:
  (i) fixed by changing snd-hda-intel options, (ii) fixed through some
  sequence of random updates, (iii) sitting in silence. I'm hoping to be
  a bit more proactive.

  The output of alsa-info.sh is attached.

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

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

[Touch-packages] [Bug 1763570] Re: file does not fully recognize ISO images

[Brian Murray]

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

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

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

Title:
  file does not fully recognize ISO images

Status in file package in Ubuntu:
  Confirmed

Bug description:
  Environment:

  Xubuntu 18.04

  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ apt-cache policy file
  file:
Installed: 1:5.32-2
Candidate: 1:5.32-2
Version table:
   *** 1:5.32-2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Steps-to-reproduce:

  1) Download Xubuntu 16.04 ISO from
  http://cdimages.ubuntu.com/xubuntu/releases/16.04/release/xubuntu-16.04
  -desktop-amd64.iso

  2) run: file --mime-type xubuntu-16.04-desktop-amd64.iso

  3) run: file xubuntu-16.04-desktop-amd64.iso

  
  Expected results:

  Result of (2) should be:
  $ file --mime-type xubuntu-16.04-desktop-amd64.iso
  xubuntu-16.04-desktop-amd64.iso: application/x-iso9660-image

  ... and result of (3) should be:
  $ file xubuntu-16.04-desktop-amd64.iso
  xubuntu-16.04-desktop-amd64.iso: DOS/MBR boot sector ISO 9660 CD-ROM 
filesystem data (DOS/MBR boot sector) 'Xubuntu 16.04 LTS amd64' (bootable); 
partition 2 : ID=0xef, start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), 
startsector 2410708, 4736 sectors

  
  Actual results:

  $ file --mime-type xubuntu-16.04-desktop-amd64.iso
  xubuntu-16.04-desktop-amd64.iso: application/octet-stream

  $ file xubuntu-16.04-desktop-amd64.iso
  xubuntu-16.04-desktop-amd64.iso: DOS/MBR boot sector; partition 2 : ID=0xef, 
start-CHS (0x3ff,254,63), end-CHS (0x3ff,254,63), startsector 2410708, 4736 
sectors

  
  ubuntuforums thread: https://ubuntuforums.org/showthread.php?t=2388736

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

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

[Touch-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

[AsciiWolf]

Should I add the missing Czech translated strings manually?

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  New

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

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

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

[Touch-packages] [Bug 1764797] [NEW] [FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable (main)

[Balint Reczey]

Public bug reported:

Feature Freeze Justification


Latest unattended-upgrades upload fixed multiple serious issues and
includes a few minor fixes which are not worth skipping.

Most notably it now runs upgrade-between-snapshots autopkgtest with
updated python-apt thus regressions can block migration to release
pocket and fixes frequent crashes due to using python-apt's API in a
wrong way.

Changes:
 unattended-upgrades (1.1ubuntu1) bionic; urgency=medium
 .
   * Merge from Debian unstable (LP: #1764797)
 - Remaining changes:
   - unattended-upgrades: Do not automatically upgrade the development
 release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
 - Dropped changes, included in Debian:
   - Rename d/NEWS.Debian to d/NEWS to have it shipped
   - Fix typo in NEWS file
   - d/rules: Exclude mypy cache from source package.
 .
 unattended-upgrades (1.1) unstable; urgency=medium
 .
   [ cgail914 ]
   * Update 50unattended-upgrades.Raspbian
 added a semi-column sign on line 86 to facilitate uncommenting the line
 for users and not end up with an error message when running
 unattended-upgrades. And make the whole file consistent.
 .
   [ Tobias Bannert ]
   * completed german translation
 .
   [ Simon McVittie ]
   * d/rules: Exclude mypy cache from source package.
 .
   [ Julian Andres Klode ]
   * Do not reuse old apt.Version objects after reopening cache (LP: #1737441)
 .
   [ Balint Reczey ]
   * Rename d/NEWS.Debian to d/NEWS to have it shipped
   * Fix typo in NEWS file
   * Add missing semicolon to commented-out Remove-Unused-Kernel-Packages option
   * Set UnattendedUpgradesCache.allowed_origins before calling
 apt.Cache.__init__()
   * Find package candidates to adjust sweeping through all packages only once.
 Later reuse the list candidates and filter out packages installed in the
 meantime. Thanks to Julian Andres Klode for the original patch
   * Use updated python-apt in upgrade-between-snapshots test
   * upgrade-between-snapshots: Mount /proc, too, in the chroot.
 Also clean up chroot properly on exit.
   * upgrade-between-snapshots: Use http_proxy environment variable in chroot,
 too
   * upgrade-between-snapshots: Remove packages installed as the side-effect of
 updating apt and python-apt
   * Ignore errors from compiling backported packages
   * Make is_autoremove_valid() nondestructive.
 Also fix autoremoval of packages when one package can't be removed and
 keeps back other package removals due to missing cache.clear()
   * Fix tracking removed packages
   * Suggest default-mta | mail-transport-agent to keep Lintian happy
 .
   [ Michael Vogt ]
   * unattanded-upgrades: refactor get_candidates_to_adjust() to
 adjust_candidates()

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Feature Freeze Justification
  
  
  Latest unattended-upgrades upload fixed multiple serious issues and
  includes a few minor fixes which are not worth skipping.
  
  Most notably it now runs upgrade-between-snapshots autopkgtest with
  updated python-apt thus regressions can block migration to release
  pocket and fixes frequent crashes due to using python-apt's API in a
  wrong way.
  
  Changes:
-  unattended-upgrades (1.1ubuntu1) bionic; urgency=medium
-  .
-* Merge from Debian unstable (LP: )
-  - Remaining changes:
-- unattended-upgrades: Do not automatically upgrade the development
-  release of Ubuntu unless Unattended-Upgrade::DevRelease is true.
-  - Dropped changes, included in Debian:
-- Rename d/NEWS.Debian to d/NEWS to have it shipped
-- Fix typo in NEWS file
-- d/rules: Exclude mypy cache from source package.
-  .
-  unattended-upgrades (1.1) unstable; urgency=medium
-  .
-[ cgail914 ]
-* Update 50unattended-upgrades.Raspbian
-  added a semi-column sign on line 86 to facilitate uncommenting the line
-  for users and not end up with an error message when running
-  unattended-upgrades. And make the whole file consistent.
-  .
-[ Tobias Bannert ]
-* completed german translation
-  .
-[ Simon McVittie ]
-* d/rules: Exclude mypy cache from source package.
-  .
-[ Julian Andres Klode ]
-* Do not reuse old apt.Version objects after reopening cache (LP: #1737441)
-  .
-[ Balint Reczey ]
-* Rename d/NEWS.Debian to d/NEWS to have it shipped
-* Fix typo in NEWS file
-* Add missing semicolon to commented-out Remove-Unused-Kernel-Packages 
option
-* Set UnattendedUpgradesCache.allowed_origins before calling
-  apt.Cache.__init__()
-* Find package candidates to adjust sweeping through all packages only 
once.
-  Later reuse the list candidates and filter out packages installed in the
-  meantime. Thanks to Julian Andres Klode for the original patch
-* Use updated 

[Touch-packages] [Bug 1763492] Re: Update page - Sign In is in German, unable to proceed

[Sebastien Bacher]

That was a buggy en_GB translation and has been fixed in that update
https://launchpad.net/ubuntu/+source/language-pack-en/1:18.04+20180412

** Package changed: software-properties (Ubuntu) => language-pack-en
(Ubuntu)

** Changed in: language-pack-en (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Update page - Sign In is in German, unable to proceed

Status in language-pack-en package in Ubuntu:
  Fix Released

Bug description:
  On a system setup for English, UK English keyboard - Sign In on the
  update page is in German not English.

  Further - following click on the first Anmelden - I get a dialogue
  that seems to get no further.

  Can I take it from the second issue that LivePatch is only available
  to Ubuntu and not flavours?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.28
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 12 20:22:13 2018
  InstallationDate: Installed on 2017-09-02 (222 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-en/+bug/1763492/+subscriptions

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

[Touch-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

[Gunnar Hjalmarsson]

I noticed that dh-translations is not in Build-Depends, so I added cdbs
to Build-Depends to pull it and uploaded to PPA, but the dh_translations
program was still not run according to the build log.

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  New

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

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

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

[Touch-packages] [Bug 1764474] Re: software-properties-gtk should not store the goa account-id used for livepatch in the keyring.

[Sebastien Bacher]

** Changed in: software-properties (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  software-properties-gtk should not store the goa account-id used for
  livepatch in the keyring.

Status in software-properties package in Ubuntu:
  Fix Committed

Bug description:
  There is no need to store the goa account id in the keyring. gsettings
  should be enough.

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

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