[Touch-packages] [Bug 1266675] Re: newusers error adding more than one user

[Bug Watch Updater]

** Changed in: shadow (Debian)
   Status: Unknown => Fix Released

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

Title:
  newusers error adding more than one user

Status in shadow package in Ubuntu:
  Confirmed
Status in shadow package in Debian:
  Fix Released

Bug description:
  1)
  mcegielka@ftp-geodezja:~$ lsb_release -rd
  Description:Ubuntu 13.10
  Release:13.10

  2)
  mcegielka@ftp-geodezja:~$ sudo apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu6
Candidate: 1:4.1.5.1-1ubuntu6

  3)
  Expected: add system users from file given as argument:

  mcegielka@ftp-geodezja:~$ cat testusers.txt
  test1:a:::test user 1,,,:/home/test1:/bin/bash
  test2:b:::test user 2,,,:/home/test2:/bin/bash

  4)
  Instead: errors:

  mcegielka@ftp-geodezja:~$ sudo newusers testusers.txt
  *** Error in `newusers': free(): invalid next size (fast): 0x09319cd0 ***
  *** Error in `newusers': malloc(): memory corruption: 0x09319d00 ***

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: passwd 1:4.1.5.1-1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Tue Jan  7 09:04:11 2014
  InstallationDate: Installed on 2014-01-07 (0 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release i386 
(20131016)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720499] Re: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.8
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Sep 30 10:12:12 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2017-05-18 (134 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-06-16T13:22:47.273361

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

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

[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

[Wenduo Wang]

The solution by @robertjjoynt worked for me on 2017 HP Omen 15 with
Linux Mint 18.2 with Kernel 4.10.0-27. It is MAGIC!

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

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

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

[Touch-packages] [Bug 1720499] [NEW] package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[pawan singh dhami]

Public bug reported:

package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade:
subprocess installed post-installation script returned error exit status
127

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.8
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
.var.log.unattended-upgrades.unattended-upgrades.log:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sat Sep 30 10:12:12 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
InstallationDate: Installed on 2017-05-18 (134 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "0";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "0";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-06-16T13:22:47.273361

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

Title:
  package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.8
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  .var.log.unattended-upgrades.unattended-upgrades.log:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Sep 30 10:12:12 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2017-05-18 (134 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "0";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "0";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-06-16T13:22:47.273361

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

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

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Graham Bosworth]

Hello Nir,

A few things have been suggested as possibly being at fault, and this
has been a long saga, but one of the symptoms is that the "Network
Manager" icon can be lost, making it difficult to recover the connection
that way.  For myself, I want to know either how to prevent the problem
from happening, or to find an automated scripted method of recovering
after the problem.  Have you any suggestions please?

Thanks,
Graham

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Touch-packages] [Bug 1720488] [NEW] [LG HBS850, playback] volume slider problem

[Alex Welch]

Public bug reported:

the left ear bud is extremely quiet on ubuntu but is just fine on windows.
I am using Ubuntu 16.04 LTS

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   alex   1983 F...m pulseaudio
 /dev/snd/controlC0:  alex   1983 F pulseaudio
CurrentDesktop: Unity
Date: Fri Sep 29 21:36:39 2017
InstallationDate: Installed on 2016-11-25 (308 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: LG HBS850
Symptom_Type: Volume slider, or mixer problems
Title: [LG HBS850, playback] volume slider problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2012
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.60
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.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-0D102G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L745
dmi.product.version: PSK0YU-0D102G
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug xenial

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

Title:
  [LG HBS850, playback] volume slider problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the left ear bud is extremely quiet on ubuntu but is just fine on windows.
  I am using Ubuntu 16.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   alex   1983 F...m pulseaudio
   /dev/snd/controlC0:  alex   1983 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 29 21:36:39 2017
  InstallationDate: Installed on 2016-11-25 (308 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: LG HBS850
  Symptom_Type: Volume slider, or mixer problems
  Title: [LG HBS850, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  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.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-0D102G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L745
  dmi.product.version: PSK0YU-0D102G
  dmi.sys.vendor: TOSHIBA

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

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

[Touch-packages] [Bug 1709500] Re: [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance.

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+17.10.20170929-0ubuntu1

---
ubuntu-themes (16.10+17.10.20170929-0ubuntu1) artful; urgency=medium

  * Ambiance/Radiance/*/gtk-widget.css:
Make primary action button (suggested action) in headerbar more visible
(LP: #1709500)

 -- Didier Roche   Fri, 29 Sep 2017 09:57:25 -0400

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

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

Title:
  [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are
  not coloured at all in Ambiance.

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Artful:
  Fix Released

Bug description:
  Using Ambiance on artful, the "action buttons" used in GtkHeaderBar
  are using a color similar to bar background which makes them not stand
  out. One example is the file-roller extract dialog, when using Adwaita
  the "extract" button is blue which make it an obvious click target,
  that's not the case under our themes

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

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

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Nir Yeffet]

This is probably a bug with Network Manager. I was able to stop the
behavior by deleting the connection from the GUI menu (Ubuntu 17.04) and
creating new one.

Quick how to: from the network icon-> edit connections... "Network
Connections" appears -> choose the one with the problem -> edit -> keep
a note with your parameters in all tabs -> Cancel. From "Network
Connections" -> choose the one with the problem -> delete -> confirm.
(delete also redundant connections) From "Network Connections" -> Add ->
choose type -> create... -> set the parameters noted above.

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Touch-packages] [Bug 1712871] Re: ubuntu-standard should not depend on apt-transport-https in >= artful

[Jeremy Bicha]

** Branch linked: lp:~jbicha/ubuntu-seeds/platform.artful-apt-transport-
https

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

Title:
  ubuntu-standard should not depend on apt-transport-https in >= artful

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  https support has been merged into apt itself for artful (apt >=
  1.5~), and stable since 1.5~beta2, so please stop seeding apt-
  transport-https (maybe we can demote the binary package to universe
  then? - I don't know how well people like that).

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

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

[Touch-packages] [Bug 1706558] Re: Japanese Input Method doesn't work by default in Ubuntu 17.10 daily build.

[Jeremy Bicha]

ibus-mozc is on the Ubuntu 17.10 image. See also LP: #1719938

** Changed in: ubuntu-meta (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 ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1706558

Title:
  Japanese Input Method doesn't work by default in Ubuntu 17.10 daily
  build.

Status in ibus package in Ubuntu:
  Invalid
Status in mozc package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  I installed Ubuntu Desktop 17.10 daily build (selected Japanese
  Language), but ibus-mozc (Japanese Input Method) is not installed when
  installing Ubuntu 17.10 daily build.

  Fcitx and fcitx-mozc are installed when installing Ubuntu 17.10 daily build.
  But the default is ibus.

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

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

[Touch-packages] [Bug 1714764] Re: Excessive dependency on gnome-session-canberra

[Jeremy Bicha]

I think it is an essential part of the Ubuntu Desktop that there be an
audio cue when the login screen is ready for the benefit of users who
are blind.

The askubuntu link points out that all you have to do is mute the sound
on the login screen to not hear the sound there any more.

** Description changed:

  ubuntu-desktop package depends on gnome-session-canberra package in such
  a way that it's impossible to remove gnome-session-canberra without
  removing ubuntu-desktop. This is wrong, as aforementioned package
  contains only few loud sounds to be played at system start, and is not
  an essential part of Ubuntu Desktop.
  
  I think it should be in 'recommends' section, not in 'depends'.
  
  Corresponding discussion on Ask Ubuntu:
- https://askubuntu.com/posts/952353/
+ https://askubuntu.com/questions/952353/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-desktop 1.398
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Sun Sep  3 13:07:41 2017
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-xenial-amd64-20160624-2
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-22 (73 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Excessive dependency on gnome-session-canberra

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-desktop package depends on gnome-session-canberra package in
  such a way that it's impossible to remove gnome-session-canberra
  without removing ubuntu-desktop. This is wrong, as aforementioned
  package contains only few loud sounds to be played at system start,
  and is not an essential part of Ubuntu Desktop.

  I think it should be in 'recommends' section, not in 'depends'.

  Corresponding discussion on Ask Ubuntu:
  https://askubuntu.com/questions/952353/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-desktop 1.398
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Sun Sep  3 13:07:41 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-22 (73 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1266675] Re: newusers error adding more than one user

[Balint Reczey]

** Also affects: shadow (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756630
   Importance: Unknown
   Status: Unknown

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

Title:
  newusers error adding more than one user

Status in shadow package in Ubuntu:
  Confirmed
Status in shadow package in Debian:
  Unknown

Bug description:
  1)
  mcegielka@ftp-geodezja:~$ lsb_release -rd
  Description:Ubuntu 13.10
  Release:13.10

  2)
  mcegielka@ftp-geodezja:~$ sudo apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu6
Candidate: 1:4.1.5.1-1ubuntu6

  3)
  Expected: add system users from file given as argument:

  mcegielka@ftp-geodezja:~$ cat testusers.txt
  test1:a:::test user 1,,,:/home/test1:/bin/bash
  test2:b:::test user 2,,,:/home/test2:/bin/bash

  4)
  Instead: errors:

  mcegielka@ftp-geodezja:~$ sudo newusers testusers.txt
  *** Error in `newusers': free(): invalid next size (fast): 0x09319cd0 ***
  *** Error in `newusers': malloc(): memory corruption: 0x09319d00 ***

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: passwd 1:4.1.5.1-1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Tue Jan  7 09:04:11 2014
  InstallationDate: Installed on 2014-01-07 (0 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release i386 
(20131016)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720474] Re: lightdm crashed with SIGSEGV in _dl_fini()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1720474/+attachment/4958987/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1720474/+attachment/4958989/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1720474/+attachment/4958997/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1720474/+attachment/4958998/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1720474/+attachment/4958999/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1720474/+attachment/4959000/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1720474/+attachment/4959001/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1675141
   lightdm crashed with SIGSEGV in munmap()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  lightdm crashed with SIGSEGV in _dl_fini()

Status in lightdm package in Ubuntu:
  New

Bug description:
  Terminal cannot be closed and xclock is not fully shown.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: lightdm 1.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Sat Sep 30 08:27:47 2017
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2017-03-08 (205 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922)
  ProcCmdline: lightdm --session-child 17 20
  SegvAnalysis:
   Segfault happened at: 0x7efd43c53179 <_dl_fini+777>: mov0x8(%rax),%r12
   PC (0x7efd43c53179) ok
   source "0x8(%rax)" (0x7efd3eb47e70) not located in a known VMA region 
(needed readable region)!
   destination "%r12" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   _dl_fini () at dl-fini.c:231
   __run_exit_handlers (status=0, listp=0x7efd427d76f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at 
exit.c:83
   __GI_exit (status=) at exit.c:105
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
  Title: lightdm crashed with SIGSEGV in _dl_fini()
  UpgradeStatus: Upgraded to artful on 2017-09-15 (14 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1667963] Re: QuiteRSS AppArmor profile

[Launchpad Bug Tracker]

** Branch linked: lp:~raulvior-bcn/apparmor/apparmor-quiterss

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

Title:
  QuiteRSS AppArmor profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  Test plan:
  1. Boot application.
  2. Add feed
  3. Update feeds
  4. Read some feed.
  5. Open link in external browser.
  6. Click to view page inside QuiteRSS.
  7. Export feeds.
  8. Go to preferences, change something.
  9. Hide window (minimize it)
  9. Use notification area menu to show update feeds, show window.
  10. Close application.

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

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

[Touch-packages] [Bug 1719934] Re: Missing fonts in list of languages

[Gunnar Hjalmarsson]

I'm sure your calculation is more proper than mine (I have probably
installed some of the packages manually). Still think it's a good idea;
those fonts represent languages spoken by a huge number of people.

On 2017-09-30 01:14, Jeremy Bicha wrote:
> 
> https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.artful/view/head:/desktop#L34
> 
> So to amend my previous question, why not move fonts-indic from
> 'supported' to 'desktop-common'?
> And move those 3 fonts from 'desktop' to 'desktop-common'?

+1 from me (for what that is worth...)

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

Title:
  Missing fonts in list of languages

Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  There is a font missing on the ISO and one of the language is shown as
  unicode characters (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:22:24 2017
  InstallationDate: Installed on 2013-09-03 (1484 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719934] Re: Missing fonts in list of languages

[Jeremy Bicha]

On my computer, sudo apt install fonts-indic gives these numbers:

Need to get 3,315 kB of archives.
After this operation, 11.6 MB of additional disk space will be used.

The comment says there were "space reasons" to have some fonts listed in
desktop instead of desktop-common but I believe that doesn't apply any
more. (All the Desktop flavors appear to ship those fonts except Lubuntu
doesn't include fonts-liberation but Lubuntu Next does so that seems a
mistake to not include that font.)

https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/ubuntu.artful/view/head:/desktop#L34

So to amend my previous question, why not move fonts-indic from 'supported' to 
'desktop-common'?
And move those 3 fonts from 'desktop' to 'desktop-common'?

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

Title:
  Missing fonts in list of languages

Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  There is a font missing on the ISO and one of the language is shown as
  unicode characters (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:22:24 2017
  InstallationDate: Installed on 2013-09-03 (1484 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719934] Re: Missing fonts in list of languages

[Gunnar Hjalmarsson]

@Jeremy: I remember that we talked about fonts-indic a few weeks ago.
The accumulated size of the packages it pulls isn't huge - 5 MB disk
space if I didn't make a mistake - and it sounds like a good idea. Or
would it require a bunch of MIRs?

Maybe, though, replace fonts-knda and fonts-telu in the platform.artful
branch with fonts-indic. (Why do we pull some fonts via desktop-common
in platform.artful, and some via desktop in ubuntu.artful?)

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

Title:
  Missing fonts in list of languages

Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  There is a font missing on the ISO and one of the language is shown as
  unicode characters (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:22:24 2017
  InstallationDate: Installed on 2013-09-03 (1484 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[Marek]

I would just like to inform you that this bug appear since last CentOS 7.4 
update, 7.3 was ok.
https://bugs.centos.org/view.php?id=13916

Maybe it should be reported to Systemd Issues ?

** Bug watch added: bugs.centos.org/ #13916
   https://bugs.centos.org/view.php?id=13916

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 

[Touch-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

[Bug Watch Updater]

** Changed in: xserver
   Status: Unknown => Incomplete

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

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

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in XServer:
  Incomplete
Status in qemu package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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

[Touch-packages] [Bug 1631763] Re: Ubuntu needs a GPU accelerated browser

[Jeremy Bicha]

I am closing the ubuntu-meta task since we don't plan to change the
default web browser.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Ubuntu needs a GPU accelerated browser

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  We all know the Web support of an operating system is becoming more
  and more important for users.

  The situation right now in terms of browser Performance and power
  consumption of GNU/Linux is not really in a good shape compared to the
  2 other competitors : Windows and Mac OSX.

  Windows 10 : Microsoft has shown how its integrated browser is more
  efficient and less hungry on power consumption than other browsers.

  Mac OSX: Safari is also showing a great power consumption and
  integrated features.

  SO this bug is to track progress for an integrated browser for Ubuntu
  ( can be firefox, chromium, something else ) that would out of the box
  :

  - Use GPU for video decoding

  - Use GPU for Web 3D rendering like webGL

  - integrate as much as possible EME HTML5 for DRM support (like
  firefox 49 for netflix)

  Please suggest other features in the comments

  -- Chromium --

  For chromium we track progress on
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1424201

  -- Firefox --

  Firefox video decode progress should be tracked here :
  https://bugzilla.mozilla.org/show_bug.cgi?id=563206

  Firefox overlay support here
  https://bugzilla.mozilla.org/show_bug.cgi?id=495727

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

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

[Touch-packages] [Bug 1710353] Re: Window controls and menus aren't in top bar when app is maximized

[Jeremy Bicha]

See this bug for Firefox. In a future release, Firefox will move its
window control buttons to the same bar as the tabs which will save
vertical space.

https://bugzilla.mozilla.org/show_bug.cgi?id=1283299

** Summary changed:

- unable to maximize windows (doubled title bars?) in Ubuntu 17.10 alpha
+ Window controls and menus aren't in top bar when app is maximized

** Package changed: ubuntu-meta (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Wishlist

** Bug watch added: Mozilla Bugzilla #1283299
   https://bugzilla.mozilla.org/show_bug.cgi?id=1283299

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

Title:
  Window controls and menus aren't in top bar when app is maximized

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In Ubuntu 17.10 alpha (with Gnome being the default environment) -
  when compared to Unity on Ubuntu 17.04 and earlier - it is not
  possible to fully maximize a window.

  There are two title bars in Ubuntu 17.10 alpha and Gnome after a
  window is maximized, while we had only one title bar in Unity and
  earlier Ubuntu versions.

  Two title bars instead of one waste screen real estate and don't
  contain any extra information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-desktop 1.379
  Uname: Linux 4.12.2-041202-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Aug 12 19:40:16 2017
  InstallationDate: Installed on 2017-04-14 (120 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1688169] Re: artful fresh install is missing gnome-shell / ubuntu-gnome-desktop

[Jeremy Bicha]

This was fixed months ago.

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

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

Title:
  artful fresh install is missing gnome-shell / ubuntu-gnome-desktop

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  artful fresh install is missing gnome-shell / ubuntu-gnome-desktop

  Seems to install Unity7 alone.

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

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

[Touch-packages] [Bug 1719934] Re: Missing fonts in list of languages

[Jeremy Bicha]

What do you think about moving fonts-indic from 'supported' to 'live'?

desktop-common in 14.04 had recommends for:

 * (ttf-indic-fonts-core)
 * (ttf-punjabi-fonts)

https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/platform.trusty/view/head:/desktop-common#L89

But those were dropped before 16.04 LTS.

There's a description of ttf-indic-fonts-core in the changelog:
https://launchpad.net/ubuntu/+source/ttf-indic-fonts/1:0.5.14ubuntu1

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

Title:
  Missing fonts in list of languages

Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  There is a font missing on the ISO and one of the language is shown as
  unicode characters (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:22:24 2017
  InstallationDate: Installed on 2013-09-03 (1484 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Brian Murray]

I think source of the problem here is bug 1501844 and removing a linux-
image-extra package causes update-initramfs to be run. If the kernel
package maintainer scripts were written differently then removing linux-
image and linux-image-extra would not have a problem if /boot was full,
but removing linux-image-extra by itself would still be an issue as
update-initramfs would be run.

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

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

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

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

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

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

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

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

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

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

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

[Touch-packages] [Bug 1720452] Re: regression in Indian language keyboard layout selection (Malayalam, Kannada, Telugu etc missing)

[Anivar Aravind]

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

** This bug has been marked a duplicate of bug 1707929
   [FFe] Revert blacklisting of Indic layouts

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

Title:
  regression in Indian language  keyboard layout selection (Malayalam,
  Kannada, Telugu etc missing)

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Debian:
  Unknown

Bug description:
  Missing Indian language XKB keyboards.

  Issue resolved upstream. Please update the with the fix applied 
  I tested this in 17.10 beta 2 . The upstream fix is not reflecting in Ubuntu 
yet 
  https://bugs.freedesktop.org/show_bug.cgi?id=101532#c9

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Serhiy Zahoriya]

1. Have nvidia-3## and/or virtualbox installed.
2. Update kernel.

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720452] [NEW] regression in Indian language keyboard layout selection (Malayalam, Kannada, Telugu etc missing)

[Anivar Aravind]

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

Public bug reported:

Missing Indian language XKB keyboards.

Issue resolved upstream. Please update the with the fix applied 
I tested this in 17.10 beta 2 . The upstream fix is not reflecting in Ubuntu 
yet 
https://bugs.freedesktop.org/show_bug.cgi?id=101532#c9

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: gnome-control-center (Debian)
 Importance: Unknown
 Status: Unknown

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

** Also affects: xkeyboard-config (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Confirmed

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

** Also affects: gnome-control-center (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865316
   Importance: Unknown
   Status: Unknown

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

Title:
  regression in Indian language  keyboard layout selection (Malayalam,
  Kannada, Telugu etc missing)

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Debian:
  Unknown

Bug description:
  Missing Indian language XKB keyboards.

  Issue resolved upstream. Please update the with the fix applied 
  I tested this in 17.10 beta 2 . The upstream fix is not reflecting in Ubuntu 
yet 
  https://bugs.freedesktop.org/show_bug.cgi?id=101532#c9

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

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

[Touch-packages] [Bug 1718029] Re: cloudstack and azure datasources broken when using netplan/systemd-networkd

[Steve Langasek]

And I understand Dimitri has the necessary changes to systemd in
progress.

** Changed in: cloud-init (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  cloudstack and azure datasources broken when using netplan/systemd-
  networkd

Status in netplan:
  New
Status in cloud-init package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu artful, cloud-init renders network configuration through netplan.
  This means that there is no dhclient and thus no /var/lib/dhclient/*.leases.

  Azure and CloudStack both are reading those leases file to get useful
  information about the platform.

  Specifically:
   * Azure reads option-245 from the dhclient response to find the IP address 
of the metadata service.
   * CloudStack reads the 'dhcp-server-identifier' option in the dhclient 
response to get the address of the virtual router (metadata service). [1]

  In ubuntu this happens to be done with systemd-networkd, so cloud-init
  can possibly probably interact over the dbus with systemd-networkd to
  get information.  However that is less than ideal, as ultimately
  cloud-init should not need to know that it systemd-networkd is
  involved.  It should be hidden via netplan.  So there should be an
  interface to get current networking configuratoin information from
  netplan including dhcp lease response info.

  
  --
  [1] 
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/virtual_machines/user-data.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cloud-init 0.7.9-280-ge626966e-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CloudName: Amazon - Ec2
  Date: Mon Sep 18 19:56:40 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  user_data.txt:
   #cloud-config
   {}

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

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

[Touch-packages] [Bug 1720451] Re: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

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

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1720451/+attachment/4958952/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1720451/+attachment/4958953/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 1708947

** 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 gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1720451

Title:
  gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-
  packages/PyKDE4/__init__.py: No module named 'DLFCN'

Status in gdebi package in Ubuntu:
  New

Bug description:
  Crashed while trying to install dropbox on 17.10 with gnome 3.26.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gdebi-kde 0.9.5.7+nmu1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 15:57:28 2017
  ExecutablePath: /usr/share/gdebi/gdebi-kde
  InstallationDate: Installed on 2017-04-25 (156 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-kde
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu4
  PythonArgs: ['/usr/bin/gdebi-kde']
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: gdebi
  Title: gdebi-kde crashed with ModuleNotFoundError in 
/usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 299158] Re: Liberation Mono, Droid Sans Mono: Combining diacritics out of place

[Egmont Koblinger]

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854149.

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

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

Title:
  Liberation Mono, Droid Sans Mono: Combining diacritics out of place

Status in fonts-dejavu package in Ubuntu:
  Confirmed
Status in fonts-droid package in Ubuntu:
  Won't Fix
Status in fonts-liberation package in Ubuntu:
  Confirmed
Status in msttcorefonts package in Ubuntu:
  Won't Fix

Bug description:
  In the Liberation Mono font, combining diacritical marks are drawn
  over the following character rather than the preceding.

  According to the Unicode standard since at least version 3.0, chapter
  3.6, verse D56, combining characters apply to the preceding base
  character. However, this font renders them on the following base
  character.

  Version info:
  Ubuntu Intrepid
  ttf-liberation 1.04~beta2-2

  To reproduce:
  1. Open gedit.
  2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small 
letter a, Combining acute accent, Latin small letter e).
  3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font.

  Expected:
  * Two grapheme clusters are displayed: Latin small letter a with acute 
accent, Latin small letter e.

  Observed:
  * The grapheme clusters displayed are: Latin small letter a, Latin small 
letter e with acute accent.

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

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

[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind

[Brian Murray]

I'm looking for specific steps to recreate the problem on an Ubuntu
system. What steps do I need to take for dkms to leave to a bunch of
.old-dkms files in boot?

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

Title:
  /boot/initrd.img-*.old-dkms files left behind

Status in dkms package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in dkms package in Debian:
  New

Bug description:
  One notices *.old-dkms files being left behind still sitting on the
  disk after purging the related kernel. This can cause /boot to become
  full, and when it gets really bad, even sudo apt-get autoremove won't
  fix the problem - only deleting the old-dkms files manually solves the
  problem.

  Note:  Filling up the /boot partition causes updates to fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: dkms 2.2.0.3-2ubuntu3.3
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Nov 12 08:17:10 2015
  InstallationDate: Installed on 2015-05-05 (190 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: dkms
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720446] [NEW] Freefont is buggy and produce broken rendering for many indian languages

[Anivar Aravind]

Public bug reported:

Freefont is last updated in 2012& not maintained. It is buggy and not
producing quality rendering in Most Indian Languages. This is the only
font in Ubuntu as of now supported in indtaller. But this results in
broken rendering. I suggest to remove this font from installer and make
it optional. I also suggest to remove this from ubuntu-desktop & vlc
dependency

In past there was a package called ttf-indic-fonts-core as an installer 
dependency to support indian languages. But now that is also removed and 
producing Square boxes for many Indian languages. 
Ref : 
https://bugs.launchpad.net/ubuntu/+source/ttf-indic-fonts/+bug/958345/comments/39
There is a need of better addressing of Indian language support in Ubuntu prior 
to 17.10 . The support must come from seperate font package & not via broken 
ttf-freefont. 
As of now Beta 2 of 17.10 produces rendering errors for many languages 
including Malayalam because of fonts-freefont.

** Affects: fonts-freefont (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Freefont is buggy and produce broken rendering for many indian
  languages

Status in fonts-freefont package in Ubuntu:
  New

Bug description:
  Freefont is last updated in 2012& not maintained. It is buggy and not
  producing quality rendering in Most Indian Languages. This is the only
  font in Ubuntu as of now supported in indtaller. But this results in
  broken rendering. I suggest to remove this font from installer and
  make it optional. I also suggest to remove this from ubuntu-desktop &
  vlc dependency

  In past there was a package called ttf-indic-fonts-core as an installer 
dependency to support indian languages. But now that is also removed and 
producing Square boxes for many Indian languages. 
  Ref : 
https://bugs.launchpad.net/ubuntu/+source/ttf-indic-fonts/+bug/958345/comments/39
  There is a need of better addressing of Indian language support in Ubuntu 
prior to 17.10 . The support must come from seperate font package & not via 
broken ttf-freefont. 
  As of now Beta 2 of 17.10 produces rendering errors for many languages 
including Malayalam because of fonts-freefont.

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

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

[Touch-packages] [Bug 1718029] Re: cloudstack and azure datasources broken when using netplan/systemd-networkd

[Steve Langasek]

I understand that systemd in artful is already exposing these options
upstream, so marking this task fixed.

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

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

Title:
  cloudstack and azure datasources broken when using netplan/systemd-
  networkd

Status in netplan:
  New
Status in cloud-init package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu artful, cloud-init renders network configuration through netplan.
  This means that there is no dhclient and thus no /var/lib/dhclient/*.leases.

  Azure and CloudStack both are reading those leases file to get useful
  information about the platform.

  Specifically:
   * Azure reads option-245 from the dhclient response to find the IP address 
of the metadata service.
   * CloudStack reads the 'dhcp-server-identifier' option in the dhclient 
response to get the address of the virtual router (metadata service). [1]

  In ubuntu this happens to be done with systemd-networkd, so cloud-init
  can possibly probably interact over the dbus with systemd-networkd to
  get information.  However that is less than ideal, as ultimately
  cloud-init should not need to know that it systemd-networkd is
  involved.  It should be hidden via netplan.  So there should be an
  interface to get current networking configuratoin information from
  netplan including dhcp lease response info.

  
  --
  [1] 
http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.8/virtual_machines/user-data.html

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: cloud-init 0.7.9-280-ge626966e-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CloudName: Amazon - Ec2
  Date: Mon Sep 18 19:56:40 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  user_data.txt:
   #cloud-config
   {}

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

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

[Touch-packages] [Bug 1507247] Re: avahi-daemon dies after about a minute

[Val]

Confirming what appears to be the same or very similar issue on Ubuntu
16.04.3. The starting of avahi-daemon and SIGTERM after about a minute
is a cyclical process, repeating every few minutes or hours:

Sep 29 16:01:09 host123 avahi-daemon[7072]: Process 3321 died: No such process; 
trying to remove PID file. (/var/run/avahi-daemon//pid)
Sep 29 16:01:09 host123 avahi-daemon[7072]: Found user 'avahi' (UID 111) and 
group 'avahi' (GID 120).
Sep 29 16:01:09 host123 avahi-daemon[7072]: Successfully dropped root 
privileges.
Sep 29 16:01:09 host123 avahi-daemon[7072]: avahi-daemon 0.6.32-rc starting up.
Sep 29 16:01:09 host123 avahi-daemon[7072]: Successfully called chroot().
Sep 29 16:01:09 host123 avahi-daemon[7072]: Successfully dropped remaining 
capabilities.
Sep 29 16:01:09 host123 avahi-daemon[7072]: No service file found in 
/etc/avahi/services.
Sep 29 16:01:09 host123 avahi-daemon[7072]: *** WARNING: Detected another IPv4 
mDNS stack running on this host. This makes mDNS unreliable and is thus not 
recommended. ***
Sep 29 16:01:09 host123 avahi-daemon[7072]: *** WARNING: Detected another IPv6 
mDNS stack running on this host. This makes mDNS unreliable and is thus not 
recommended. ***
Sep 29 16:01:09 host123 avahi-daemon[7072]: Joining mDNS multicast group on 
interface eno1.IPv6 with address :4aae:be84:cf7d:f493.
Sep 29 16:01:09 host123 avahi-daemon[7072]: New relevant interface eno1.IPv6 
for mDNS.
Sep 29 16:01:09 host123 avahi-daemon[7072]: Joining mDNS multicast group on 
interface eno1.IPv4 with address 192.168.215.6.
Sep 29 16:01:09 host123 avahi-daemon[7072]: New relevant interface eno1.IPv4 
for mDNS.
Sep 29 16:01:09 host123 avahi-daemon[7072]: Network interface enumeration 
completed.
Sep 29 16:01:09 host123 avahi-daemon[7072]: Registering new address record for 
:4aae:be84:cf7d:f493 on eno1.*.
Sep 29 16:01:09 host123 avahi-daemon[7072]: Registering new address record for 
:781d:848d:385a:720c on eno1.*.
Sep 29 16:01:09 host123 avahi-daemon[7072]: Registering new address record for 
::6 on eno1.*.
Sep 29 16:01:09 host123 avahi-daemon[7072]: Registering new address record for 
192.168.215.6 on eno1.IPv4.
Sep 29 16:01:09 host123 avahi-daemon[7072]: Server startup complete. Host name 
is host123.local. Local service cookie is 4044503296.
Sep 29 16:02:39 host123 systemd[1]: avahi-daemon.service: Start operation timed 
out. Terminating.
Sep 29 16:02:39 host123 avahi-daemon[7072]: Got SIGTERM, quitting.
Sep 29 16:02:39 host123 avahi-daemon[7072]: Leaving mDNS multicast group on 
interface eno1.IPv6 with address :4aae:be84:cf7d:f493.
Sep 29 16:02:39 host123 avahi-daemon[7072]: Leaving mDNS multicast group on 
interface eno1.IPv4 with address 192.168.215.6.
Sep 29 16:02:39 host123 avahi-daemon[7072]: avahi-daemon 0.6.32-rc exiting.
Sep 29 16:02:39 host123 systemd[1]: avahi-daemon.service: Unit entered failed 
state.
Sep 29 16:02:39 host123 systemd[1]: avahi-daemon.service: Failed with result 
'timeout'.

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

Title:
  avahi-daemon dies after about a minute

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  So I thought I'd try running Vagrant inside of an Ubuntu VM to do some
  development work as detailed here:
  http://taoofmac.com/space/HOWTO/Vagrant

  When the box starts up, there is a short delay before broadcasting
  begins, and I'm able to ping the guest (in this case registered as
  "hobo-container.local").

  Then, after a minute or two, it stops responding.  The logs look like
  this:

  -- Logs begin at Thu 2015-10-15 14:36:55 EDT, end at Thu 2015-10-15 14:40:00 
EDT. --
  Oct 15 14:36:58 hobo-container systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: Found user 'avahi' (UID 
110) and group 'avahi' (GID 119).
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: Successfully dropped root 
privileges.
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: avahi-daemon 0.6.31 
starting up.
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: Successfully called 
chroot().
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: Successfully dropped 
remaining capabilities.
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: Loading service file 
/services/ssh.service.
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: Joining mDNS multicast 
group on interface eth1.IPv6 with address fe80::a0
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: New relevant interface 
eth1.IPv6 for mDNS.
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: Joining mDNS multicast 
group on interface eth1.IPv4 with address 203.0.11
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: New relevant interface 
eth1.IPv4 for mDNS.
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: Network interface 
enumeration completed.
  Oct 15 14:36:58 hobo-container avahi-daemon[507]: Registering 

[Touch-packages] [Bug 1667963] Re: QuiteRSS AppArmor profile

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  QuiteRSS AppArmor profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  Test plan:
  1. Boot application.
  2. Add feed
  3. Update feeds
  4. Read some feed.
  5. Open link in external browser.
  6. Click to view page inside QuiteRSS.
  7. Export feeds.
  8. Go to preferences, change something.
  9. Hide window (minimize it)
  9. Use notification area menu to show update feeds, show window.
  10. Close application.

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

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

[Touch-packages] [Bug 1720300] Re: List items become invisible when selected in g-c-c

[Sebastien Bacher]

in fact it started happening after the theme update today, seems an
issue with the g-c-c changes though

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

Title:
  List items become invisible when selected in g-c-c

Status in gnome-control-center package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Steps:

  1. Open gnome-control-center
  2. Select the Search panel
  3. Select any of the items in the list
  4. They become invisible when selected

  They should be visibly selected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170925-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 08:17:05 2017
  InstallationDate: Installed on 2017-09-21 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691901] [base-files/zesty] verification still needed

[Ubuntu Foundations Team Bug Bot]

The fix for this bug has been awaiting testing feedback in the -proposed
repository for zesty for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

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

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

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

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

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

  === SRU ===

  [ IMPACT ]

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

  [ TEST CASE ]

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

  Failure case:

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

  Apply the fix.

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

  [ REGRESSION ]

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

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

  --
  [1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/base-files/tree/update-motd.d/50-motd-news?h=applied/ubuntu/zesty#n108

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: User Name 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri May 19 01:11:30 2017
  Ec2AMI: ami-004f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   

[Touch-packages] [Bug 1720431] Re: Thin line below title bar

[Daniel van Vugt]

** Summary changed:

- 1px line in title bar
+ Thin line below title bar

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-themes
   Importance: Undecided => Medium

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

Title:
  Thin line below title bar

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  ubuntu artful desktop 20170929

  There is a 1px line in the title bar (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170925-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 14:54:27 2017
  InstallationDate: Installed on 2013-09-03 (1486 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

[Jonas Ådahl]

Upstream bug is probably
https://bugs.freedesktop.org/show_bug.cgi?id=102475 ?

** Bug watch added: freedesktop.org Bugzilla #102475
   https://bugs.freedesktop.org/show_bug.cgi?id=102475

** Also affects: xserver via
   https://bugs.freedesktop.org/show_bug.cgi?id=102475
   Importance: Unknown
   Status: Unknown

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

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in XServer:
  Unknown
Status in qemu package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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

[Touch-packages] [Bug 1720431] [NEW] 1px line in title bar

[Jean-Baptiste Lallement]

Public bug reported:

ubuntu artful desktop 20170929

There is a 1px line in the title bar (cf screenshot)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: light-themes 16.10+17.10.20170925-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 29 14:54:27 2017
InstallationDate: Installed on 2013-09-03 (1486 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
PackageArchitecture: all
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-themes (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed

** Affects: ubuntu-themes (Ubuntu Artful)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed


** Tags: amd64 apport-bug artful

** Attachment added: "Sélection_005.bmp"
   
https://bugs.launchpad.net/bugs/1720431/+attachment/4958885/+files/S%C3%A9lection_005.bmp

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

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Also affects: ubuntu-themes (Ubuntu Artful)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: 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/1720431

Title:
  1px line in title bar

Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  ubuntu artful desktop 20170929

  There is a 1px line in the title bar (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170925-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 14:54:27 2017
  InstallationDate: Installed on 2013-09-03 (1486 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

[ChristianEhrhardt]

So it is likely a wayland <-> SDL thing.
@Desktop Team could you take alook into this - the repro steps in c#2 are 
pretty easy I'd think but none of us would know where in the UI stack to look 
for.

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

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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

[Touch-packages] [Bug 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition

[Rafael David Tinoco]

Okay, so another quick workaround, now keeping the fsck enabled for the
volumes:

Create a file called "/lib/systemd/upstart/systemd-fsck@.service" with:


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

[Unit]
Description=File System Check on %f
Documentation=man:systemd-fsck@.service(8)
DefaultDependencies=no
BindsTo=%i.device
After=systemd-readahead-collect.service systemd-readahead-replay.service 
%i.device
Before=shutdown.target

[Service]
Type=oneshot
RemainAfterExit=no
ExecStart=/lib/systemd/systemd-fsck %f
StandardOutput=journal+console
TimeoutSec=0


and then do:

$ sudo ln -s /lib/systemd/upstart/systemd-fsck@.service 
/lib/systemd/upstart/multi-user.target.wants/systemd-fsck@.service
$ sudo systemctl daemon-reload

This will allow the mount units to work using systemd in Trusty:

inaddy@trustylivepatch:~$ sudo systemctl start teste.mount
inaddy@trustylivepatch:~$ df -kh | grep teste
/dev/sdb2   976M  1.3M  908M   1% /teste
inaddy@trustylivepatch:~$ sudo systemctl stop teste.mount
inaddy@trustylivepatch:~$ cat /etc/fstab| grep teste
LABEL=TESTE /teste ext4 defaults 0 1

While still having fsck enabled in /etc/fstab.

I'll provide a SRU patch for systemd in Trusty and it shall solve this
issue.

** Changed in: snapd
   Status: In Progress => Invalid

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

Title:
  Cannot install snaps on Ubuntu 14.04 with /var on its own partition

Status in snapd:
  Invalid
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  In Progress

Bug description:
  Installing snaps is not possible on Ubuntu 14.04 when having /var on
  its own partition, whether its LVM or not.

  The issue is with the core snap being unable to mount:

  The error with /var isolated and using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  The error with /var isolated but without using LVM:

  root@ubuntu:~# snap install canonical-livepatch
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service
 failed to load: No such file or directory. See system logs and 'systemctl 
status 
systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service'
 for details.
  )

  The same error happens if I try to install the hello-world snap (with
  LVM in this example):

  root@ubuntu:~# snap install hello-world
  error: cannot perform the following tasks:
  - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit 
status 6: Failed to issue method call: Unit 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or 
directory. See system logs and 'systemctl status 
systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details.
  )

  I cannot reproduce the issue in Ubuntu 16.04.

  I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image
  which doesn't isolate /var on its own partition. I tried adding a
  secondary disk to that cloud image VM and create a dummy VG and LV,
  but couldn't reproduce the issue.

  Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with
  only a / partition and swap.

  
  Steps to reproduce:
  ===

  # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and
  configure /, /var and swap on their own partitions (with LVM or not,
  the issue happens in both situations).

  root@ubuntu:~# lvs
  LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert
  rootvol vg00 -wi-ao--- 3.72g 
  swap vg00 -wi-ao--- 3.72g 
  varvol vg00 -wi-ao--- 3.72g 

  root@ubuntu:~# df -h
  Filesystem   Size  Used Avail Use% Mounted on
  udev 484M  4.0K  484M   1% /dev
  tmpfs100M  988K   99M   1% /run
  /dev/dm-03.7G  1.7G  1.8G  49% /
  none 4.0K 0  4.0K   0% /sys/fs/cgroup
  none 5.0M 0  5.0M   0% /run/lock
  none 497M 0  497M   0% /run/shm
  none 100M 0  100M   0% /run/user
  /dev/mapper/vg00-varvol  3.7G  716M  2.8G  21% /var

  
  

[Touch-packages] [Bug 1720116] Re: apport-gtk sigfault in libgtk-3

[Cliff Carson]

Attaching the syslog text showing the sigfault and I think the
corresponding crash file.

** Attachment added: "_usr_share_apport_apport-gtk.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+attachment/4958871/+files/_usr_share_apport_apport-gtk.0.crash

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

Title:
  apport-gtk sigfault in libgtk-3

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Daily notification of system error and request to report it but
  nothing get sent.  Syslog shows apport-gtk sigfault in libgtk-3.
  There us usually no crash dump generated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 
-0400:2017-09-22 05:36:27.979332060 
-0400:/var/crash/_usr_share_apport_apport-gtk.0.crash
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Thu Sep 28 06:54:23 2017
  InstallationDate: Installed on 2017-07-24 (65 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Francis Ginther]

** Tags added: id-597a835aabb9be94fe80eb45

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  Confirmed
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey,password
  debug1: Next authentication method: 

[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Francis Ginther]

** Tags added: id-596781a4fd7307546010c061

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

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

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Zesty:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  New

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

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

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

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

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

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

  
  * APT SRU *
  [Impact]
  Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the 
signals to all processes in the cgroup, and will send KILL quickly after.

  [Test case]
  Start apt-daily-upgrade.service and stop it while unattended-upgrades is 
running.

  The upgrade should run to completion or a safe exit point as long as
  it takes less than about 900s (which is the timeout for sending kill).

  [Regression potential]
  Leftover processes might remain in the apt-daily-upgrade cgroup if the 
postinst scripts or some apt hooks do something funny.

  Shutdown might take longer due to the 900 second timeout.

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

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

[Touch-packages] [Bug 1716979] Re: clean up unmodified /etc/rc.local on upgrade

[Francis Ginther]

** Tags added: id-59b965e3325c6b38afd5122b

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

Title:
  clean up unmodified /etc/rc.local on upgrade

Status in systemd package in Ubuntu:
  Fix Committed
Status in ubuntu-release-upgrader package in Ubuntu:
  Won't Fix

Bug description:
  If a user's system was installed before zesty, the initscripts package
  was installed as part of the base system, and a stub /etc/rc.local was
  created on install.

  rc.local is very much a legacy interface (it was legacy under Debian's 
sysvinit, so it's three generations of legacy); and if /etc/rc.local is present 
and executable, systemd runs an additional unit, rc-local.service, which is 
After=network-online.target (due to 
  /lib/systemd/system/rc-local.service.d/debian.conf).  This can unnecessarily 
impact boot speed in the event that the network is not available at boot.

  Since the initscripts package no longer exists in zesty and later, and
  this package should preferably be removed on upgrade, we can't put
  maintainer script code in this package to manage the removal of
  /etc/rc.local.

  Adding this to any other system package would be a kludge.

  I think this belongs as a quirk on upgrade, to remove the
  /etc/rc.local left behind by initscripts if it is unmodified.

  Here is the md5sum of the stock file, which has remained consistent
  from (at least) lucid through xenial:

  $ md5sum /etc/rc.local 
  10fd9f051accb6fd1f753f2d48371890  /etc/rc.local

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

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

[Touch-packages] [Bug 1714019] Re: Please merge unattended-upgrades 0.96 (main) from Debian unstable (main)

[Francis Ginther]

** Tags added: id-596781a4fd7307546010c061

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

Title:
  Please merge unattended-upgrades 0.96 (main) from Debian unstable
  (main)

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  I'm also asking for a Feature Freeze Exception following the rules for
  new upstream version per
  https://wiki.ubuntu.com/FreezeExceptionProcess.

  [Reason]
  Unattended-upgrades is planned to be enabled by default but the versions 
present in Ubuntu can break the system by not protecting the upgrade process 
from termination during shutdown (see LP: #1690980).
  The newer version in Debian fixes the shutdown-related issue and contains 
several additional reliability and debuggability fixes.

  [Logs]
  They are attached to this bug.

  [Testing]
  The autopkgtest log is attached and I also tested the version in Debian 
several times while preparing the fixes for various bugs.

  Note that the package in the PPA does not close this bug from the
  changelog while the patches attaches do.

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

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

[Touch-packages] [Bug 1667963] Re: QuiteRSS AppArmor profile

[Raúl Vidal]

Uh, sorry. This is the modification patch (see attachment).

** Patch added: "usr.bin.quiterss.patch"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667963/+attachment/4958867/+files/usr.bin.quiterss.patch

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

Title:
  QuiteRSS AppArmor profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  Test plan:
  1. Boot application.
  2. Add feed
  3. Update feeds
  4. Read some feed.
  5. Open link in external browser.
  6. Click to view page inside QuiteRSS.
  7. Export feeds.
  8. Go to preferences, change something.
  9. Hide window (minimize it)
  9. Use notification area menu to show update feeds, show window.
  10. Close application.

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

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

[Touch-packages] [Bug 1667963] Re: QuiteRSS AppArmor profile

[Raúl Vidal]

Yes, no problem. But since I uploaded the profile to launchpad I made a
slight modification. See attached profile.

** Attachment added: "usr.bin.quiterss"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667963/+attachment/4958853/+files/usr.bin.quiterss

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

Title:
  QuiteRSS AppArmor profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  Test plan:
  1. Boot application.
  2. Add feed
  3. Update feeds
  4. Read some feed.
  5. Open link in external browser.
  6. Click to view page inside QuiteRSS.
  7. Export feeds.
  8. Go to preferences, change something.
  9. Hide window (minimize it)
  9. Use notification area menu to show update feeds, show window.
  10. Close application.

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

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

[Touch-packages] [Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook

[Francis Ginther]

** Tags added: id-58e22b4afdee5f97b3bfbfd7

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

Title:
  ntp: changing the default config from server to pool broke the dhcp
  hook

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

Bug description:
  In 1:4.2.8p3+dfsg-1, the default config was changed to
  "Use pool instead of server".  This needs a corresponding
  update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the
  DHCP specified servers now get added to the default pool
  config instead of replacing them.

  This affects Xenial only as the Yakkety build includes the upstream
  fix (1:4.2.8p7+dfsg-1).

  Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344
  & https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676

  [Test Case]

  philroche: This surfaced for me initially while testing on GCE. On GCE
  NTP servers are provided via DHCP so the easiest test case is to
  launch an instance on GCE without our workaround configured.

  One such image is "daily-ubuntu-ntpdebug-1604-xenial-v20170331" in
  project "ubuntu-os-cloud-devel"

  To start an instance of this image:

  `gcloud compute instances create daily-ubuntu-
  ntpdebug-1604-xenial-v20170331 --image-project ubuntu-os-cloud-devel
  --image "daily-ubuntu-ntpdebug-1604-xenial-v20170331"`

  Then run `ntpq -p` which should, once ntp is patched, return only one
  entry 'metadata.google' and should not return any of the ubuntu NTP
  pools.

  [Regression Potential]

  As noted in comments #1 and #2, this SRU might surface an issue if the
  user is receiving a broken set of NTP servers.

  And as noted in comment #4, some people might be hackishly using the
  distinction between spaces and tabs in the config file to trick our
  current hook.  Debian has gotten rid of that distinction, so that hack
  will stop working on distro-upgrade anyway.  The fix is *probably*
  going to help more people who unintentionally mixed the two up rather
  than the few that are relying on that bug.  But that bit can be easily
  dropped from the SRU if ya like.

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

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

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

[Francis Ginther]

** Tags added: id-59668fbcb9edb050ebe5b008

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

Title:
  Include information about python versions

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Artful:
  Fix Released

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

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

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

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

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

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

[Francis Ginther]

** Tags added: id-58f0e5ff470e62b969ff06f3

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

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Released
Status in ubuntu-meta source package in Trusty:
  Confirmed
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Confirmed
Status in ubuntu-advantage-tools source package in Yakkety:
  Won't Fix
Status in ubuntu-meta source package in Yakkety:
  Won't Fix
Status in ubuntu-advantage-tools source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  Confirmed
Status in ubuntu-advantage-tools source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released

Bug description:
  The ubuntu-advantage-tools package is a bit odd as it was first landed
  in precise to support the ESM effort inside canonical. [0]  In order
  to bring this package up to date across other series in ubuntu, it has
  been recommended by the Ubuntu Foundations team to land into trusty
  next, then forward-port pocket-copy to all supported series until we
  get to the devel release.

  The version here:

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

  ... has all on-disk bits correctly working, for all series, but no-ops
  on any release other than precise (ESM is only for "unsupported" LTS
  releases as it were).  This is a request to land ubuntu-advantage-
  tools into trusty, then pocket-copy it to supported series of ubuntu
  once that is finished.

  [Impact]

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

  [Test Case]

   * Run ubuntu-advantage, it should print out help

   * Run sudo ubuntu-advantage enable  (without sudo it will warn
  you), but you need to be an ubuntu-advantage customer to get that
  token.  In the end, the script simply adds and removes an
  /etc/apt/sources.list.d entry.

   * Verify that the MOTD does not contain any mention of ubuntu-
  advantage esm or precise and its end of life

   * Verify that ubuntu-advantage enable-esm  installs needed 
dependencies:
- create the following file and its contents to have apt not install 
recommended packages by default:
  $ cat /etc/apt/apt.conf.d/no-recommends
  APT::Install-Recommends "false";
- remove ca-certificates and apt-transport-https:
  $ sudo apt remove ca-certificates apt-transport-https
- run sudo ubuntu-advantage enable-esm  and verify that the two 
removed packages are reinstalled

   * you can contact me (d...@canonical.com) if you would like a token
  for test purposes.

  [Regression Potential]

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

  [Other Info]

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

  [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04
  -esm-extended-security-maintenance/

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

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

[Touch-packages] [Bug 1706195] Re: whoopsie can start before network-manager during boot

[Francis Ginther]

** Tags added: id-59761bfbcfbdd79f928c8806

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

Title:
  whoopsie can start before network-manager during boot

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  whoopsie can start before network-manager and then will only work when a 
networking device state changes, however since it started before n-m it should 
notice the connection come on-line. This is upload is just in case there are 
some corner cases out there where whoopsie isn't working and uploading the 
crashes to the Error Tracker.

  [Test Case]
  1) Boot a system with the old version of whoopsie
  2) Run 'systemctl status whoopsie'
  3) Observe:
  Jul 25 11:07:01 clean-zesty-amd64 systemd[1]: Started crash report submission 
daemon.
  Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Using lock path: 
/var/lock/whoopsie/lock
  Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Could not get the 
Network Manager state:
  Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.NetworkManager was not provided by any .service files
  Jul 25 11:07:02 clean-zesty-amd64 whoopsie[446]: [11:07:02] offline

  With the version of whoopsie in -proposed you'll see the following:

  Jul 25 11:10:33 clean-zesty-amd64 systemd[1]: Started crash report submission 
daemon.
  Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Using lock path: 
/var/lock/whoopsie/lock
  Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] The default IPv4 
route is: /org/freedesktop/NetworkManager/ActiveConnection/0
  Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Not a paid data 
plan: /org/freedesktop/NetworkManager/ActiveConnection/0
  Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Found usable 
connection: /org/freedesktop/NetworkManager/ActiveConnection/0

  [Regression Potential]
  If whoopsie is working properly when it wasn't, this shouldn't be the case 
because whoopsie would start working when the network connection changed, then 
people might be surprised by additional network activity (uploading of crashes) 
and the Error Tracker may receive more crash reports.

  Original Description
  
  whoopsie's systemd service file does not start after networking which is 
incorrect since it initially needs to query network-manager's state. A fix was 
attempted by changing the service file to include "After=network-online.target" 
but this was insufficient. The following messages demonstrate the failure, if 
whoopsie were to start after network-manager we would not see them:

  Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network 
Manager state:
  Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.NetworkManager was not provided by any .service files

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

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

[Touch-packages] [Bug 1697375] Re: whoopsie's network-manager state querying is broken

[Francis Ginther]

** Tags added: id-59695177efc355a29a203a96

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

Title:
  whoopsie's network-manager state querying is broken

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Xenial:
  Fix Released
Status in whoopsie source package in Zesty:
  Fix Released
Status in whoopsie source package in Artful:
  Fix Released

Bug description:
  [Impact]
  whoopsie's querying of network-manager's state is broken and this results in 
whoopsie only being able to detect if the system is on-line when network 
manager's state changes. Subsequently, if one manually restarts whoopsie then 
whoopsie will stay off-line until an n-m state change. This can result in 
crashes not being uploaded.  Additionally, whoopsie's systemd service file does 
not start after networking which is incorrect since it initially needs to query 
network-manager's state. (However, this ended up allowing crash reports to 
still be submitted because whoopsie would start first then the n-m's state 
would change and whoopsie would detect that.)

  [Test Case] (state detection failure)
  1) Manually restart the whoopsie service
  2) Observe the following two messages:
  "Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network 
Manager state:
  Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'"

  with the version of network-manager from -proposed you will not see
  these messages when restarting whoopsie.

  [Test Case] (starting after network-manager0
  1) Boot your system
  2) Observe the following in syslog:
  "Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network 
Manager state:
  Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.NetworkManager was not provided by any .service files
  "

  with the version of network-manager in -proposed you will not see the
  "NetworkManager was not provided" messages.

  [Regression Potential]
  Its possible that systems that were not submitting crash reports suddenly 
will and that will use some network bandwidth and Error Tracker resources.

  - Original Description -
  
  On artful crash reports are not uploaded automatically (several .crash files 
in /var/crash and no corresponding upload or .uploaded files)

  ProblemType: BugDistroRelease: Ubuntu 17.10
  Package: whoopsie 0.2.56
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:39:29 2017
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: apport-noui N/ASourcePackage: whoopsie
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root

[Francis Ginther]

** Tags added: id-594d1970df3ec53730c0d28c

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

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1 
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
while [ -z "${FSTYPE}" ]; do
FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

# Run failure hooks, hoping one of them can fix up the system
# and we can restart the wait loop.  If they all fail, abort
# and move on to the panic handler and shell.
if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
break
fi
done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

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

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

[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

[Francis Ginther]

** Tags added: id-597a82bd36308ac7a63cff29

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed
Status in unattended-upgrades source package in Artful:
  Confirmed
Status in update-notifier source package in Artful:
  Confirmed

Bug description:
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.

[Francis Ginther]

** Tags added: id-597a833ca49ff66291d34705

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

Title:
  By default settings unattended-upgrade is unable to automatically
  remove packages that become unused in conjunction with updating by
  other software.

Status in apt package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in apt source package in Artful:
  New
Status in gnome-software source package in Artful:
  New
Status in unattended-upgrades source package in Artful:
  New
Status in update-manager source package in Artful:
  New

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

[Francis Ginther]

** Tags added: id-59b6c684c96dc86054510529

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Touch-packages] [Bug 1687122] Re: /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-repository@168:add_source_from_shortcut:/usr/bin/add-apt-repository@172

[Francis Ginther]

** Tags added: id-597a82f68d90d6cef4a9017f

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

Title:
  /usr/bin/add-apt-repository:OSError:/usr/bin/add-apt-
  repository@168:add_source_from_shortcut:/usr/bin/add-apt-
  repository@172

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Artful:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.96.24.13, the problem page at 
https://errors.ubuntu.com/problem/01a945aed47dfff0cdfea51c5923f51cadeafb00 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

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

[Francis Ginther]

** Tags added: id-597a82b5b13fc0c72914002c

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

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Released
Status in ubuntu-meta source package in Trusty:
  Confirmed
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Confirmed
Status in ubuntu-advantage-tools source package in Yakkety:
  Won't Fix
Status in ubuntu-meta source package in Yakkety:
  Won't Fix
Status in ubuntu-advantage-tools source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  Confirmed
Status in ubuntu-advantage-tools source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released

Bug description:
  The ubuntu-advantage-tools package is a bit odd as it was first landed
  in precise to support the ESM effort inside canonical. [0]  In order
  to bring this package up to date across other series in ubuntu, it has
  been recommended by the Ubuntu Foundations team to land into trusty
  next, then forward-port pocket-copy to all supported series until we
  get to the devel release.

  The version here:

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

  ... has all on-disk bits correctly working, for all series, but no-ops
  on any release other than precise (ESM is only for "unsupported" LTS
  releases as it were).  This is a request to land ubuntu-advantage-
  tools into trusty, then pocket-copy it to supported series of ubuntu
  once that is finished.

  [Impact]

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

  [Test Case]

   * Run ubuntu-advantage, it should print out help

   * Run sudo ubuntu-advantage enable  (without sudo it will warn
  you), but you need to be an ubuntu-advantage customer to get that
  token.  In the end, the script simply adds and removes an
  /etc/apt/sources.list.d entry.

   * Verify that the MOTD does not contain any mention of ubuntu-
  advantage esm or precise and its end of life

   * Verify that ubuntu-advantage enable-esm  installs needed 
dependencies:
- create the following file and its contents to have apt not install 
recommended packages by default:
  $ cat /etc/apt/apt.conf.d/no-recommends
  APT::Install-Recommends "false";
- remove ca-certificates and apt-transport-https:
  $ sudo apt remove ca-certificates apt-transport-https
- run sudo ubuntu-advantage enable-esm  and verify that the two 
removed packages are reinstalled

   * you can contact me (d...@canonical.com) if you would like a token
  for test purposes.

  [Regression Potential]

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

  [Other Info]

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

  [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04
  -esm-extended-security-maintenance/

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

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

[Touch-packages] [Bug 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install

[Francis Ginther]

** Tags added: id-59690d2a51b99cb84a07b129

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

Title:
  python3 in /usr/local/bin can cause python3 packages to fail to
  install

Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.5 package in Ubuntu:
  Fix Released
Status in python2.7 source package in Xenial:
  New
Status in python3.5 source package in Xenial:
  Fix Released
Status in python2.7 source package in Zesty:
  New
Status in python3.5 source package in Zesty:
  Fix Released
Status in python3.5 package in Debian:
  Fix Released

Bug description:
  [Impact]
  An upgrade of python3.5 will fail if someone has installed a different 
version of python3.5 in their path e.g. in /usr/local/bin. This is because the 
postinst scripts do not specify the complete path to python3.5.

  [Test Case]
  1) Ensure the version of python3.5 from the release pocket is installed
  2) Install python3 using the instructions at 
https://passingcuriosity.com/2015/installing-python-from-source/
  3) Confirm that python3.5 from /usr/local/bin/ is being used / the default
  4) Upgrade to a newer version of python3.5 from -proposed

  Observe the following Traceback:

  Setting up python3.5-minimal (3.5.3-1) ...
  Traceback (most recent call last):
File "/usr/lib/python3.5/py_compile.py", line 6, in 
  import importlib._bootstrap_external
File "/usr/lib/python3.5/importlib/__init__.py", line 57, in 
  import types
File "/usr/lib/python3.5/types.py", line 166, in 
  import functools as _functools
File "/usr/lib/python3.5/functools.py", line 23, in 
  from weakref import WeakKeyDictionary
File "/usr/lib/python3.5/weakref.py", line 12, in 
  from _weakref import (
  ImportError: cannot import name '_remove_dead_weakref'
  dpkg: error processing package python3.5-minimal (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of python3-minimal:
   python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
Package python3.5-minimal is not configured yet.

  dpkg: error processing package python3-minimal (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

Errors were encountered while processing:
   python3.5-minimal
   python3-minimal

  With the version of python3.5 from -proposed this Traceback will not
  be encountered.

  [Regression Potential]
  It's possible I missed a postinst script so other python3.5 binary packages 
should be installed to ensure they are all fixed e.g. python3.5-dbg.

  [Original Description]
  Got this error while using "Transmageddon Video Transcoder" and again while 
updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

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

[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation

[Francis Ginther]

** Tags added: id-597a82ade5d5089d05d20931

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

Title:
  Repeating "can't open /dev/ttyX: No such device or address" messages
  during installation

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in console-setup package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  console-setup continuously tries to open /dev/tty[1-6] on s390x, when
  such consoles do not exist on s390x.

  This can be seen on boot in the output from the initramfs, and during
  the installer.

  [Cuase]

  It seems to me that the postinst of the console-setup is incorrect for
  s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR,
  z/VM, KVM)

  [Solution]
  I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it 
to... "guess". Usually it should be slcp, but that depends on which consoles 
are configured/activated in the given KVM.

  [Testcase]
  On boot, scroll all the messages and makesure there are no error messages 
about inability to open /dev/tty*

  [Original Bug Report]

  During the installation (z/VM guest and KVM virtual machine) of Ubuntu
  Server 16.04.1 (and 16.04.2) repeating messages of the form:

  "
  Select and install software ... 10% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 20% can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 30%... 40% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 50% can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ... 60% can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  can't open /dev/tty4: No such device or address
  can't open /dev/tty2: No such device or address
  ...
  Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No 
such device or address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty4: No such device or address
  ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or 
address
  can't open /dev/tty2: No such device or address
  can't open /dev/tty3: No such device or address
  ... 90% The system is going down NOW
   Sent SIGTERM to all processes
   Sent SIGKILL to all processes
   Requesting system reboot
  01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop 
CPU 00.
  00 Storage cleared - system reset.
  00 zIPL ..
  "

  They start to occur when the software gets installed:

  "Select and install software ... 10% can't open /dev/tty4: No such
  device or address"

  And only stop with the final system reboot at the end of the
  installation.

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

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

[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot

[Francis Ginther]

** Tags added: id-5983be8a574a2f44b3cbc1ed

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

Title:
  kdump service does not start after configure/reboot

Status in The Ubuntu-power-systems project:
  Triaged
Status in makedumpfile package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Harish Sriram  - 2017-08-02 01:45:01 ==
  kdump service does not start after configure/reboot

  --Problem Description---
  kdump service does not start after configure/reboot. It has to be 
started/loaded manually, everytime after reboot.

  # kdump-config status
  current state   : Not ready to kdump

  
  ---uname output---
  Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux 
   
  Machine Type/Model = Power 8/8247-22L 

  Additional Info-
  # cat /proc/cmdline
  root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 
console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
   
  ---Steps to Reproduce---
  1. installed linux-crashdump
  2. edited the kdump-tools.cfg crashkernel cmdline to above
  3. update-grub
  4. reboot

  Expected:
  kdump-config to be loaded by default after reboot

  # kdump-config status
  current state   : Not ready to kdump

  # service kdump-tools status
  * kdump-tools.service - Kernel crash dump capture service
 Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor 
pres
 Active: inactive (dead)

  ...
  https://github.com/systemd/systemd/issues/6334

  systemd in artful is not properly picking up the unit files in 
  /etc/systemd/system/default.target.wants

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

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

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

[Francis Ginther]

** Tags added: id-597a8312028fa1cd2c156565

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

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

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Artful:
  Triaged

Bug description:
  artful unprivileged container on a xenial host

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

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

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

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

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

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

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

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

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

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

  More logs attached.

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

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

[Touch-packages] [Bug 1712921] Re: enabling networkd appears to eat up entropy

[Francis Ginther]

** Tags added: id-59a82980f80facbe02e40d09

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

Title:
  enabling networkd appears to eat up entropy

Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Triaged

Bug description:
  enabling networkd appears to eat up entropy

  as seen in openssh autopkgtest failing, when networkd is enabled by
  default.

  See http://autopkgtest.ubuntu.com/packages/openssh/artful/amd64 with
  triggers systemd/234-2ubuntu9

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

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

[Francis Ginther]

** Tags added: id-5988c348d036b6f6acb1e389

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

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  In Progress
Status in nplan source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  ethernets:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04

[Francis Ginther]

** Tags added: id-59a6de69fde9c920947b3d4b

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

Title:
  ssh connection attempts fail if hw crypto support on s390x is enabled
  on 17.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Zesty:
  Confirmed
Status in openssh source package in Artful:
  Fix Released

Bug description:
  [ Impact ]

  * Unable to ssh into Ubuntu, using default sshd configuration, when hw
  acceleration is enabled in openssl.

  [ Proposed solution ]

  * Cherrypick upstream fixes for:
- sandboxing code on big endian
- allowing hw accel iocls in the sandbox

  short:
  after investigations the following commits are needed by openssh-server 
version 7.4p1 that is part of 17.04:
  - 5f1596e11d55539678c41f68aed358628d33d86f
  - 9e96b41682aed793fadbea5ccd472f862179fb02
  on master branch in https://github.com/openssh/openssh-portable
  that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox 
errors for Linux S390 systems using an ICA crypto coprocessor."
  __

  [Test case]

  long:

  enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  sudo apt-get install openssl-ibmca libica-utils libica2
  sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf
  sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf

  afterwards ssh login attempts fail:
  $ ssh ubuntu@zlin42
  ubuntu@zlin42's password:
  Connection to zlin42 closed by remote host.
  Connection to zlin42 closed.

  the normal logs don't provide any interesting details:

  mit log:
    Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 
audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 
pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 
compat=0 ip=0x3ffb8a3fb32 code=0x0

  Verbose:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /home/fheimes/.ssh/config
  debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming"
  debug1: /home/fheimes/.ssh/config line 7: Applying options for *
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22.
  debug1: Connection established.
  debug1: identity file /home/fheimes/.ssh/id_rsa type 1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 
Ubuntu-10
  debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400
  debug1: Authenticating to 10.245.208.7:22 as 'ubuntu'
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: curve25519-sha...@libssh.org
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
  debug1: Server host key: ecdsa-sha2-nistp256 
SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk
  debug1: Host '10.245.208.7' is known and matches the ECDSA host key.
  debug1: Found key in /home/fheimes/.ssh/known_hosts:87
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: rekey after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey,password
  debug1: Next authentication method: 

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

[Francis Ginther]

** Tags added: id-597a8343fc8685288751db7a

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

Title:
  softlockup DoS causes systemd-journald.service to abort with SIGABORT

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

Bug description:
  I was running the new stress-ng softlockup stressor and observed that
  systemd-journald gets killed with an abort and this corrupts the
  systemd journal.

  How to reproduce:

  git clone git://kernel.ubuntu.com/cking/stress-ng
  cd stress-ng
  make clean; make

  sudo ./stress-ng --softlockup 0 -t 360 -v

  ..and wait for 360 seconds.  dmesg shows the following, 100%
  reproduceable:

  
  [  875.310331] systemd[1]: systemd-timesyncd.service: Watchdog timeout (limit 
3min)!
  [  875.310740] systemd[1]: systemd-timesyncd.service: Killing process 574 
(systemd-timesyn) with signal SIGABRT.
  [  875.327289] systemd[1]: systemd-timesyncd.service: Main process exited, 
code=killed, status=6/ABRT
  [  875.327666] systemd[1]: systemd-timesyncd.service: Unit entered failed 
state.
  [  875.327686] systemd[1]: systemd-timesyncd.service: Failed with result 
'watchdog'.
  [  875.327917] systemd[1]: systemd-timesyncd.service: Service has no hold-off 
time, scheduling restart.
  [  875.327954] systemd[1]: Stopped Network Time Synchronization.
  [  875.328845] systemd[1]: Starting Network Time Synchronization...
  [  875.525071] systemd[1]: Started Network Time Synchronization.
  [  875.539619] systemd[1]: systemd-journald.service: Main process exited, 
code=dumped, status=6/ABRT
  [  875.544257] systemd-journald[5214]: File 
/run/log/journal/440e485e550040e3b93b66b2faae8525/system.journal corrupted or 
uncleanly shut down, renaming and replacing.

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

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

[Touch-packages] [Bug 1698388] Re: Assertion failure in journal-remote-parse.c

[Francis Ginther]

** Tags added: id-594d08756bf06c332683f3a6

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

Title:
  Assertion failure in journal-remote-parse.c

Status in systemd package in Ubuntu:
  New

Bug description:
  I am observing the following assertion failure in systemd-journal-
  remote:

  Assertion 'source->filled <= source->size' failed at ../src/journal-
  remote/journal-remote-parse.c:95, function get_line(). Aborting.

  Systemd version:

  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Ubuntu release:

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  Package version:

  systemd:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu17

  It looks like this issue has been fixed upstream in v230, specifically
  in commit 9ba37525d0ef3d144a50ed5fd4710573e92b7ec1. Could this
  particular commit be backported?

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

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

[Touch-packages] [Bug 1718771] Re: Incorrect handling of link-local IPv6 DNS servers

[Francis Ginther]

** Tags added: id-59c41ec2d19ed45aedf778d1

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

Title:
  Incorrect handling of link-local IPv6 DNS servers

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

Bug description:
  We've recently seen odd looking DNS failures on autopkgtest:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/d/docker.io/20170921_065231_181b8@/log.gz

  This shows a fe80:: link-local IPv6 address as one of the DNS servers
  on the interface. That's because dnsmasq includes both the link-local
  and global addresses of its DNS server in the router advertisement.

  systemd-networkd appears to pick that up and send it to resolved,
  which includes it in its config but apparently doesn't know how to
  actually query it, leading to the failure above.

  
  This is racy because once DHCPv4 completes, the resolved config will then 
work properly again.

  
  I've confirmed that dnsmasq properly answers on all addresses:
http://paste.ubuntu.com/25588197/

  
  I've uploaded a workaround for this issue as part of the docker.io package.

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

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

[Touch-packages] [Bug 1719720] Re: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127

[Francis Ginther]

** Tags added: id-59cb2cac03a39eeafe504f18

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

Title:
  [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with
  exit code 127

Status in The Ubuntu-power-systems project:
  Triaged
Status in coreutils package in Ubuntu:
  Triaged

Bug description:
  ---Problem Description---
  Currently syslog is getting flooded with below log messages ..
  Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch 
/run/run.vpdd
  update' failed with exit code 127.

  This is on UBuntu 17.10 latest build.. 
   
  ---uname output---
  Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ZZ-L 

  ---Steps to Reproduce---
   I have seen these messages logged more often when we do any hotplug 
operations.. ex. cpu hotplug..

  Ok. .this is the continuation of LTC #144627 / Launchpad #1682774.

  As suggested in that bug, we did change udev script to create
  temporary file under /run and that patch is available in ubuntu 17.10.

  Looks like this is udev script issue. If I modify systemd-udevd like
  below it works fine.

  I've limited udev knowledge. I don't know if you have any other better
  solution to this issue.

  root@ltc-boston123:/lib/systemd/system# diff -Naurp  
systemd-udevd.service.org systemd-udevd.service
  --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500
  +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500
  @@ -25,7 +25,7 @@ KillMode=mixed
   WatchdogSec=3min
   TasksMax=infinity
   MountFlags=slave
  -MemoryDenyWriteExecute=yes
  +#MemoryDenyWriteExecute=yes
   RestrictRealtime=yes
   RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
   SystemCallArchitectures=native

  
  -Vasant

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

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

[Touch-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland

[Joshua Powers]

Hi! I am running Artful on my X1 Carbon Gen3.

I downloaded the Ubuntu Server Artful final beta and attempt to do an
install with the following qemu cli:

$ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d -hda
vdisk.img -cdrom artful-server-amd64.iso -monitor stdio

Trying to use the arrow key at the first menu does not work and errors
with the unknown keycodes error. However, if I issue the `sendkey down`
command from the qemu CLI it works as expected.

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

Title:
  qemu can't capture keys properly under wayland

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  This appears to be different than the previous similar bugs; patches
  do look to be applied to use libinput in the wayland case. Still:

  unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org

  I am using qemu-system-x86   1:2.10+dfsg-0ubuntu1
  on artful.

  Many key inputs work correctly, but at boot the system will not
  properly catch the arrow keys, the above error shows up immediately
  after hitting Esc (for instance) to get to the boot menu. Booting from
  CD onto a daily Ubuntu desktop image, I can't navigate the splash
  menu.

  The same works correctly through virt-manager (which uses spice
  AFAICT, but wayland tends to crash when running virt-manager), and
  things work if I switch my session to Xorg rather than wayland.

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

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

[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows

[Francis Ginther]

** Tags added: id-597a831a26eaec02914e6202

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

Title:
  Apt updates that are uniformly spread across all timezones, with
  predictable application windows

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Won't Fix
Status in unattended-upgrades source package in Yakkety:
  Won't Fix
Status in apt source package in Zesty:
  Fix Released
Status in unattended-upgrades source package in Zesty:
  Fix Released
Status in apt source package in Artful:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [ Impact ]

   * unattended-upgrades are enabled by default in Ubuntu 16.04 and
  later

   * Currently the following three things happen as a monolithic event:
     - metadata updates: apt update
     - download of updates: apt upgrade --download-only
     - application of updates: apt upgrade

   * For the long running instances, all of the above happens at random
     times throughout the day.

   * If systems were poweredoff / suspended, this happens on boot /
  resume

   * End-users would like to have predictable timing, and control over when
     the updates happen.

  Considering all of the above, the following new behavior is proposed
  which should address all concerns in question. It combines all the
  desired properties from both end-user and mirror perspectives.

  [ Proposed Default Behavior ]

   * Decouple unattended-upgrades application, from apt update

   * apt update:
     - shall be a systemd timer based unit, triggered every 12h with a
   random delay of 12h, therefore executed randomly twice a day.
     - if unattened-upgrades (default on), or download-upgreadaeble-packages
   are enabled, it should result in updates being downloaded aka
   `apt upgrade --download-only`

   * unattended-upgrades:
     - shall be a separate systemd timer based unit triggered at 6am local
   time with a random delay of 1h, therefore executed between 6am and
   7am local time.

   * On boot / resume:
     - if we have missed one, or more, apt update timers,
   apt update / download upgrades / unattended-upgrade will happen in
   sequence. This may result in mirror spikes, but we do want to secure
   cold/stale-booted systems as soon as possible.

  [Test Case]

   * Run system for more than 24h, and check that apt updates were
     automatically executed twice.

   * Check that unattended upgrades were triggered to be applied at
     6am..7am window, if any.

   * Poweroff the machine over the period when apt-get update was
     scheduled, poweron and observe that apt-get update / download /
     unattended upgrade are all performed on boot.

   * Downgrade systemd to the release version of the package (from
     -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*.
 Then run 'sudo systemctl start apt-daily.service'.
     Confirm that the systemd package is downloaded, but not upgraded.

  [Regression Potential]

   * The newly proposed behavior is a mix of Pre-xenial behavior of "do
     everything at 6am..6:30am window" and the xenial+ behavior of "do
     everything at random times throughout the day". If there are specific
     deployments that rely on the previous types of behaviour they will be
     able to adjust manually the systemd timers with the overrides to be
     executed exactly as they wish; or match the .0 release behaviour that
     they prefer.

   * If timers behavior is coded wrongly the proposed behaviour might not be
     executed as intended, thus requiring further SRUs to bring us in-line
     with the great expectations.

  [Other Info]

    * Related bug reports and history:
  - bug #1615482
  - bug #1554848

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

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

[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting

[Francis Ginther]

** Tags added: id-597a09900a9f730ee1bfade0

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

Title:
  udevadm trigger subsystem-match=net doesn't always run rules because
  of reconfiguration rate-limiting

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

Bug description:
  1. root@ubuntu:~# lsb_release -rd
  Description:Ubuntu Zesty Zapus (development branch)
  Release:17.04

  2. root@ubuntu:~# apt-cache policy udev
  udev:
    Installed: 232-18ubuntu1
    Candidate: 232-18ubuntu1
    Version table:
   *** 232-18ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  3. udevadm trigger --verbose --subsystem-match=net --action=add will run and 
read .link files from /run/systemd/network/10-netplan-interface1.link
  and apply MTU settings

  4. during system boot running (3) does not set the MTU; running (3)
  after boot has completed MTU is set correctly.

  Here'a log during boot where cloud-init generates a netplan config,
  invokes `netplan generate` which writes the networkd config out 
  and then udevadm trigger (3).  Upon logging in interface1 has an MTU of 1500. 
 Re-running udevadm trigger now runs the rules/link files and updates the MTU.

  Note that, if you run udevadm test /sys/class/net/interface1; this also will
  apply the MTU (test probably shouldn't change the interface, I'll file a
  bug for that as well).

  # journalctl -o short-precise --no-pager -b | grep WARK
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 
'generate']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', 
'/run/systemd/network/10-netplan-interface1.link']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', 
'--no-block', 'systemd-udev-trigger.service']:
  Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', 
'--verbose', '--subsystem-match=net', '--action=add']:

  root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link
  [Match]
  MACAddress=52:54:00:12:34:02

  [Link]
  Name=interface1
  WakeOnLan=off
  MTUBytes=1492

  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1500
  inet 10.0.2.100  netmask 255.255.255.0  broadcast 10.0.2.255
  inet6 fe80::5054:ff:fe12:3402  prefixlen 64  scopeid 0x20
  inet6 fec0::5054:ff:fe12:3402  prefixlen 64  scopeid 0x40
  ether 52:54:00:12:34:02  txqueuelen 1000  (Ethernet)
  RX packets 16  bytes 5053 (5.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 35  bytes 3287 (3.2 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add
  /sys/devices/pci:00/:00:04.0/virtio1/net/interface1
  /sys/devices/pci:00/:00:05.0/virtio2/net/interface2
    ys/devices/pci:00/:00:06.0/virtio3/net/interface0
  /sys/devices/virtual/net/lo

  root@ubuntu:~# ifconfig interface1
  interface1: flags=4163  mtu 1492
  inet 10.0.2.100  netmask 255.255.255.0  broadcast 10.0.2.255
  inet6 fe80::5054:ff:fe12:3402  prefixlen 64  scopeid 0x20
  inet6 fec0::5054:ff:fe12:3402  prefixlen 64  scopeid 0x40
  ether 52:54:00:12:34:02  txqueuelen 1000  (Ethernet)
  RX packets 16  bytes 5053 (5.0 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 37  bytes 3504 (3.5 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: udev 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Thu Mar  2 19:22:14 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic 
root=UUID=8bbb84fe-91e8-4a9a-bd91-f6af4793727e ro console=ttyS0
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.1-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-zesty
  dmi.modalias: 

[Touch-packages] [Bug 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

[Francis Ginther]

** Tags added: id-59774a219e9196af44a02a59

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller  
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller :
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

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

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

[Touch-packages] [Bug 1704795] Re: [17.10 FEAT] Upgrade to util-linux version >= 2.30

[Francis Ginther]

** Tags added: id-596df25142bcd078825a1eab

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

Title:
  [17.10 FEAT] Upgrade to util-linux version >= 2.30

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  this new version inlcudes now lsmem and chmen, which was originally
  hosted by s390-tools

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

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

[Touch-packages] [Bug 1704677] Re: 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=

[Francis Ginther]

** Tags added: id-596df10ca7021ce6e7899a19

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

Title:
  229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
  ExecStop*=

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  229-4ubuntu18 included changes irrelevant for xenial, which whilst harmless 
generates a lot of scary journal entries.

  [Fix]
  Drop the cherrypciked ExecStart|StopPost stanzas from the drop in snippet. 
Integration of the resolved stub resolver with resolvconf on xenial is not 
required, because resolved in xenial does not have stub resolver. Also xenial's 
systemd does not support '+' prefix on the Exec* lines.

  [Testcase]
  Upgrade to te new SRU, make sure testcase from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1673860 still passes

  Check that there is no extra journal warnings/errors about "Executable
  path is not absolute" from systemd reading /lib/systemd/system
  /systemd-resolved.service.d/resolvconf.con

  [Original Descrption]

  
  The systemd version 229-4ubuntu18 from xenial-proposed archive has a bug. The 
'+' prefix (see 
https://www.freedesktop.org/software/systemd/man/systemd.service.html) in 
ExecStart*= and ExecStop*= statements does not work any longer.

  File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
  this version contains two commands prefixed with '+':

  # When resolved is in use, it must be brought up before we consider networking
  # available because otherwise there is a window where DNS resolution doesn't
  # work.
  [Unit]
  Before=network-online.target

  # tell resolvconf about resolved's builtin DNS server, so that DNS servers
  # picked up via networkd are respected when using resolvconf, and that 
software
  # like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
  # resolution
  [Service]
  ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo 
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
  ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || 
/sbin/resolvconf -d systemd-resolved'

  Those two statements in section [Service] lead to the following two
  error messages in dmesg:

  [3.687475] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" | 
/sbin/resolvconf -a systemd-resolved'
  [3.687614] systemd[1]: 
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable 
path is not absolute, ignoring: +/bin/sh -c '[ ! -e 
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
  ---
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 16.04
  MachineType: LENOVO 42406AG
  Package: systemd 229-4ubuntu18
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-85-lowlatency 
root=UUID=1756e76f-2b6c-479f-8ea3-e3b087b1922f ro quiet apparmor=0
  ProcVersionSignature: Ubuntu 4.4.0-85.108-lowlatency 4.4.73
  Tags: xenial package-from-proposed third-party-packages
  Uname: Linux 4.4.0-85-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom colord davfs2 dialout dip fax floppy libvirtd 
lpadmin netdev plugdev saned scanner sudo tape video wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42406AG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn42406AG:pvrThinkPadT520:rvnLENOVO:rn42406AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42406AG
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.pam.d.systemd-user: 2017-03-09T13:47:30.332992

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

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

[Touch-packages] [Bug 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

[Francis Ginther]

** Tags added: id-59c57605d1dfa992a27e9102

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in ddclient package in Ubuntu:
  New
Status in maas package in Ubuntu:
  New
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in samba package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/avahi/+bug/1717983/+subscriptions

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

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

[Francis Ginther]

** Tags added: id-5988c3a877d5e440aecf0c3a

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

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  Fix Committed
Status in nplan source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  In Progress
Status in nplan source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  ethernets:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

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

[Touch-packages] [Bug 1713803] Re: replacement of resolvconf with systemd needs integration

[Francis Ginther]

** Tags added: id-59a5e384b534421baba26a0a

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

Title:
  replacement of resolvconf with systemd needs integration

Status in android-androresolvd package in Ubuntu:
  Triaged
Status in avahi package in Ubuntu:
  Triaged
Status in bind9 package in Ubuntu:
  Triaged
Status in cloud-init package in Ubuntu:
  New
Status in cloud-initramfs-tools package in Ubuntu:
  New
Status in dhcpcd5 package in Ubuntu:
  New
Status in dibbler package in Ubuntu:
  Won't Fix
Status in dnscrypt-proxy package in Ubuntu:
  New
Status in dnsmasq package in Ubuntu:
  New
Status in dnssec-trigger package in Ubuntu:
  New
Status in fetchmail package in Ubuntu:
  New
Status in freedombox-setup package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in ndisc6 package in Ubuntu:
  New
Status in netscript-2.4 package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in pppconfig package in Ubuntu:
  New
Status in pump package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  Invalid
Status in sendmail package in Ubuntu:
  New
Status in squid3 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in unbound package in Ubuntu:
  New
Status in vpnc package in Ubuntu:
  New
Status in vpnc-scripts package in Ubuntu:
  New
Status in whereami package in Ubuntu:
  Triaged

Bug description:
  There is a plan to remove resolvconf from the Ubuntu Server image.
  resolvconf integrated with other parts of the system in 2 ways:
   * hooks invoked on change (/etc/resolvconf/update.d/)
   * resolvconf tool (invoked with -a and -d or -u)

  Packages which install files into /etc/resolvconf/update.d are:
  - dnsmasq: This may be mostly covered by systemd-resolved itself (the dns
    caching path).
  - resolvconf: This probably isn't necessary in systemd-resolved path.
  - unbound: This is another "validating, recursive, caching DNS resolver".

  The list of Depends/Suggests/Recommends on resolvconf.

  # for pkg in $(apt-cache rdepends resolvconf | grep -v openreso | grep -v 
Reverse); do out=$(apt-cache show $pkg | grep resolvconf); src=$(apt-cache show 
$pkg | awk '$1 == "Source:" { print $2 }'); [ -n "$src" ] || src=$pkg; case 
"$out" in Depends:*resolvconf) r=depends;; Suggests:*) r=suggests;; 
Recommends:*) r=recommends;; esac; echo "$r $src"; done  | sort -u
  depends android-androresolvd
  recommends avahi
  recommends dhcpcd5
  recommends dibbler
  recommends ndisc6
  recommends whereami
  suggests bind9
  suggests dnscrypt-proxy
  suggests dnsmasq
  suggests dnssec-trigger
  suggests fetchmail
  suggests freedombox-setup
  suggests isc-dhcp
  suggests netscript-2.4
  suggests openvpn
  suggests postfix
  suggests pppconfig
  suggests pump
  suggests resolvconf
  suggests sendmail
  suggests squid3
  suggests vpnc
  suggests vpnc-scripts

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu9
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  Date: Tue Aug 29 18:53:50 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

  Related bugs:
   * bug 1698181: Switch to netplan renderer in Artful
   * bug 1714308: dns does not work in initramfs after configure_networking
   * bug 1717983 replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

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

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

[Touch-packages] [Bug 1667963] Re: QuiteRSS AppArmor profile

[Emily Ratliff]

Thanks for contributing this profile to help make apparmor better! Would
you be willing to submit this profile as a merge request against the
upstream AppArmor project at https://launchpad.net/apparmor ? New
profiles should go into the profiles/apparmor/profiles/extras directory.
Thanks!

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

Title:
  QuiteRSS AppArmor profile

Status in apparmor package in Ubuntu:
  New

Bug description:
  Test plan:
  1. Boot application.
  2. Add feed
  3. Update feeds
  4. Read some feed.
  5. Open link in external browser.
  6. Click to view page inside QuiteRSS.
  7. Export feeds.
  8. Go to preferences, change something.
  9. Hide window (minimize it)
  9. Use notification area menu to show update feeds, show window.
  10. Close application.

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

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

[Touch-packages] [Bug 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B

[Rustin Schenk]

I have an HP laptop and have been seeing these errors for many months:

Sep 29 11:33:51 hp-17 kernel: [ 7857.337291] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe A (start=113116 end=113117) time 484 us, 
min 894, max 899, scanline start 891, end 918
Sep 29 11:34:42 hp-17 kernel: [ 7908.344925] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe A (start=116180 end=116181) time 647 us, 
min 894, max 899, scanline start 873, end 873
Sep 29 11:36:45 hp-17 kernel: [ 8030.836446] [drm:intel_pipe_update_end [i915]] 
*ERROR* Atomic update failure on pipe A (start=123538 end=123539) time 662 us, 
min 894, max 899, scanline start 886, end 923

They haven't seemed to cause any problems until yesterday when my system
frozen up.  Couldn't do anything on the system and had to reboot.  The
above errors were the last thing shown in the system log before I
rebooted.  The errors were repeating at about 10 times a minute over the
course of an hour before the system locked up.  I am also seeing this
error between the Atomic update failures (maybe unrelated or not):

Sep 28 12:56:38 hp-17 org.gnome.SettingsDaemon.MediaKeys.desktop[3088]: Memory 
pressure relief: Total: res = 8822784/8876032/53248, res+swap = 0/0/0
Sep 28 13:25:10 hp-17 org.gnome.SettingsDaemon.MediaKeys.desktop[3088]: Memory 
pressure relief: Total: res = 2236416/2293760/57344, res+swap = 0/0/0

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

Title:
  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've a dual monitor setup and I'm running latest version of kubuntu.

  After a few days of uptime the desktop becomes so slow that I've to
  reboot it.

  In the log I find those errors, I don't know if they are related:

  kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
  failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max
  1079, scanline start 1072, end 1080

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 31 14:06:17 2017
  DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7978]
  InstallationDate: Installed on 2013-04-25 (1376 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address. 
   IBusInputContext::createInputContext: no connection to ibus-daemon 
   file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: 
Unable to assign [undefined] to QString usersession
  MachineType: MSI MS-7978
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic 
root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  

[Touch-packages] [Bug 1720349] Re: package software-properties-common 0.96.24.7.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package software-properties-common 0.96.24.7.2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in software-properties package in Ubuntu:
  New

Bug description:
  what is the problem i don't know plz fix this problem as soon as
  posible

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: software-properties-common 0.96.24.7.2
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  Date: Thu Sep 28 19:14:17 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-09-27 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.7.2 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/software-properties/+bug/1720349/+subscriptions

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

[Touch-packages] [Bug 1720404] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in ntp package in Ubuntu:
  New

Bug description:
  something to do with installing the driver for the printer and scanner
  Panasonic KX-MB2110.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.7
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep 29 15:50:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-15 (288 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1715069] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "hal

[Phillip Susi]

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

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

Title:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: il
  pacchetto util-linux non è pronto per la configurazione  impossibile
  configurarlo (stato corrente "half-installed")

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  i'don't know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Sep  5 08:20:29 2017
  DpkgTerminalLog:
   dpkg: errore nell'elaborare il pacchetto util-linux (--configure):
il pacchetto util-linux non è pronto per la configurazione
impossibile configurarlo (stato corrente "half-installed")
  ErrorMessage: il pacchetto util-linux non è pronto per la configurazione  
impossibile configurarlo (stato corrente "half-installed")
  InstallationDate: Installed on 2017-03-21 (167 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il 
pacchetto util-linux non è pronto per la configurazione  impossibile 
configurarlo (stato corrente "half-installed")
  UpgradeStatus: Upgraded to zesty on 2017-05-22 (105 days ago)

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

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

[Touch-packages] [Bug 1714997] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il pacchetto util-linux non è pronto per la configurazione impossibile configurarlo (stato corrente "hal

[Phillip Susi]

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

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

Title:
  package util-linux 2.29-1ubuntu2 failed to install/upgrade: il
  pacchetto util-linux non è pronto per la configurazione  impossibile
  configurarlo (stato corrente "half-installed")

Status in dpkg package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: util-linux 2.29-1ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon Sep  4 18:38:10 2017
  DpkgTerminalLog:
   dpkg: errore nell'elaborare il pacchetto util-linux (--configure):
il pacchetto util-linux non è pronto per la configurazione
impossibile configurarlo (stato corrente "half-installed")
  ErrorMessage: il pacchetto util-linux non è pronto per la configurazione  
impossibile configurarlo (stato corrente "half-installed")
  InstallationDate: Installed on 2016-11-04 (304 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: util-linux
  Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: il 
pacchetto util-linux non è pronto per la configurazione  impossibile 
configurarlo (stato corrente "half-installed")
  UpgradeStatus: Upgraded to zesty on 2017-04-23 (134 days ago)

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

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

[Touch-packages] [Bug 1700327] Re: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

  happened after update to 16

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 3.13.0-121.170-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-121-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sat Jun 24 23:29:06 2017
  DuplicateSignature:
   package:unattended-upgrades:0.90ubuntu0.6
   Installing new version of config file /etc/logrotate.d/unattended-upgrades 
...
   dpkg: error processing package unattended-upgrades (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-12-12 (925 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-06-25 (0 days ago)
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2017-06-25T00:51:54.028358

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

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

[Touch-packages] [Bug 1719765] Re: Evolution can't add new data(contact, appointment) to nextcloud

[Bug Watch Updater]

** Changed in: gnome-online-accounts
   Status: Confirmed => Invalid

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

Title:
  Evolution can't add new data(contact, appointment)  to nextcloud

Status in gnome-online-accounts:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Evolution is not able to add new data eg. new contacts, new
  appointments to nextcloud. Whenn trying I get the following error
  message: "... 415 (Unsupported Media Type):
  Sabre\DAV\Exception\UnsupportedMediaType ...". Synchronizing from
  nextcloud server to client works as expected.

  I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
  snap is used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1719765/+subscriptions

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

[Touch-packages] [Bug 1720404] [NEW] package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Павел Заец]

Public bug reported:

something to do with installing the driver for the printer and scanner
Panasonic KX-MB2110.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.7
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Sep 29 15:50:02 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-12-15 (288 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: ntp
Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in ntp package in Ubuntu:
  New

Bug description:
  something to do with installing the driver for the printer and scanner
  Panasonic KX-MB2110.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.7
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep 29 15:50:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-12-15 (288 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720116] Re: apport-gtk sigfault in libgtk-3

[Brian Murray]

Would you mind uploading the apport-gtk.0.crash file to the bug report?
I'd like to take a look at it and retrace it.

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

Title:
  apport-gtk sigfault in libgtk-3

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Daily notification of system error and request to report it but
  nothing get sent.  Syslog shows apport-gtk sigfault in libgtk-3.
  There us usually no crash dump generated.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 
-0400:2017-09-22 05:36:27.979332060 
-0400:/var/crash/_usr_share_apport_apport-gtk.0.crash
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Thu Sep 28 06:54:23 2017
  InstallationDate: Installed on 2017-07-24 (65 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1719934] Re: Missing fonts in list of languages

[Brian Murray]

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Missing fonts in list of languages

Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  There is a font missing on the ISO and one of the language is shown as
  unicode characters (cf screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 27 11:22:24 2017
  InstallationDate: Installed on 2013-09-03 (1484 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720349] Re: package software-properties-common 0.96.24.7.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  package software-properties-common 0.96.24.7.2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in software-properties package in Ubuntu:
  New

Bug description:
  what is the problem i don't know plz fix this problem as soon as
  posible

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: software-properties-common 0.96.24.7.2
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  Date: Thu Sep 28 19:14:17 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-09-27 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: software-properties
  Title: package software-properties-common 0.96.24.7.2 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/software-properties/+bug/1720349/+subscriptions

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

[Touch-packages] [Bug 1720083] Re: Profile defaults to headset mode instead of a2dp

[Daniel van Vugt]

** Tags added: a2dp

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

Title:
  Profile defaults to headset mode instead of a2dp

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using 17.10

  # Reproduce:

  1. Pair bluetooth headphone with mic (like Bose QC35)
  2. Play music

  # What I get:

  Music is very bad quality because the "headset head unit (HSP/HFP)"
  profile is chosen by default. Switching to the "High Fidelity Playback
  (A2DP Sink)" profile fixes the audio.

  # What I expect:

  Music is good quality because A2DP profile is chosen by default.

  # Why should A2DP be chosen by default?

  1. Given that HSP quality is so low, we can assume that the primary use for 
bluetooth headsets is to listen to music. As a result, setting it to A2DP by 
default will give good experience for the biggest amount of use-cases.
  2. Bluez supports automatic switching from A2DP to HSP when a program 
identifies a recording stream as "Phone" (or optionally when it doesn't 
identify the recording stream with PulseAudio 11 [1]) so in many cases, it's 
not even needed to manually switch to HSP.

  [1] https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/

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

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[dino99]

@Norbert


the full solution is not so easy; so be patient.
Several thinks can be done:
- run xhost script into a terminal each time a session is opened
- insert the xhost script into .bashrc file
- and/or test some more propositions:
   * 
https://unix.stackexchange.com/questions/317282/set-environment-variables-for-gnome-on-wayland-and-bash-on-virtual-terminals-or#326161
   * 
https://ask.fedoraproject.org/en/question/108631/running-command-after-gnome-login/
   * 
https://unix.stackexchange.com/questions/118811/why-cant-i-run-gui-apps-from-root-no-protocol-specified

And for non techy people or those still satisfied with X, then choose X
at login time (still prefer lightdm myself for the moment)

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

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  New
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gufw package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New
Status in zulucrypt package in Ubuntu:
  New

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  

[Touch-packages] [Bug 1720368] Re: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value()

[Sebastien Bacher]

The issue is
Settings schema 'com.ubuntu.update-notifier' does not contain a key named 
'auto-launch'

** This bug is no longer a duplicate of bug 945144
   gsettings-data-convert crashed with signal 5 in g_settings_set_value()

** Package changed: gconf (Ubuntu) => update-notifier (Ubuntu)

** Changed in: update-notifier (Ubuntu)
   Importance: Undecided => Low

** Changed in: update-notifier (Ubuntu)
   Status: New => In Progress

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

Title:
  gsettings-data-convert crashed with signal 5 in
  g_settings_schema_get_value()

Status in update-notifier package in Ubuntu:
  In Progress

Bug description:
  I was trying several desktop environments and after a while I found a
  crash file in /var/crash/.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 15:26:52 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gsettings-data-convert
  ProcCmdline: gsettings-data-convert
  Signal: 5
  SourcePackage: gconf
  StacktraceTop:
   g_settings_schema_get_value (schema=0x55b3d5780d40, key=0x55b3d57a71f0 
"auto-launch") at ../../../../gio/gsettingsschema.c:967
   g_settings_schema_key_init (key=key@entry=0x7ffccfe31a80, 
schema=0x55b3d5780d40, name=name@entry=0x55b3d57a71f0 "auto-launch") at 
../../../../gio/gsettingsschema.c:1246
   g_settings_set_value (settings=settings@entry=0x55b3d5730170 [GSettings], 
key=key@entry=0x55b3d57a71f0 "auto-launch", value=0x55b3d57a7960) at 
../../../../gio/gsettings.c:1563
   g_settings_set (settings=0x55b3d5730170 [GSettings], key=0x55b3d57a71f0 
"auto-launch", format=) at ../../../../gio/gsettings.c:1670
   ()
  Title: gsettings-data-convert crashed with signal 5 in 
g_settings_schema_get_value()
  UpgradeStatus: Upgraded to artful on 2017-09-29 (0 days ago)
  UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare 
staff sudo

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

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

[Touch-packages] [Bug 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

[Till Kamppeter]

Thanks for the feedback, but "Fix released" means that there is actually
released a newer package version which fixes the problem. In your case
the bug report was caused by some error on your system, so I mark the
bug report as "Invalid".

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

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Invalid

Bug description:
  after updates of cups-filter and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 21 17:43:42 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21
   device for PDF: cups-pdf:/
  MachineType: Dell Inc. OptiPlex 960
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer (w/ options)
   HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f32dc0c7954 : cmpq   
$0x0,(%rdi)
   PC (0x7f32dc0c7954) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0Y958C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1709500] Re: [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance.

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu-themes

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

Title:
  [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are
  not coloured at all in Ambiance.

Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  Using Ambiance on artful, the "action buttons" used in GtkHeaderBar
  are using a color similar to bar background which makes them not stand
  out. One example is the file-roller extract dialog, when using Adwaita
  the "extract" button is blue which make it an obvious click target,
  that's not the case under our themes

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

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

[Touch-packages] [Bug 1717946] Re: UIFe: Drop xterm and xdiagnose from default install

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.402

---
ubuntu-meta (1.402) artful; urgency=medium

  * Refreshed dependencies
  * Removed xdiagnose from desktop (LP: #1717946)
  * Removed xterm from desktop-recommends (LP: #1717946)

 -- Jeremy Bicha   Thu, 28 Sep 2017 13:09:49 -0400

** Changed in: ubuntu-meta (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 ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1717946

Title:
  UIFe: Drop xterm and xdiagnose from default install

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Impact
  ==
  I'm proposing to drop 3 apps from the default Ubuntu 17.10 install:
  XTerm
  UXTerm
  xdiagnose

  These are visible in the Show Applications view of the Activities
  Overview so this could impact screenshots.

  Justification
  =
  These were only in the default install because of the FailsafeX feature.
  Timo Aaltonen (tjaalton), maintainer of Ubuntu's X stack and co-maintainer in 
Debian, has said that feature isn't important any more, considering the 
transition to Wayland.

  xdiagnose also provided some apport hooks for diagnosing display
  problems but that was moved to xorg itself earlier this release cycle.

  xdiagnose currently doesn't run in the Ubuntu session on Wayland.

  https://irclogs.ubuntu.com/2017/09/18/%23ubuntu-desktop.html#t14:18

  Discussed earlier in the cycle:
  https://lists.ubuntu.com/archives/ubuntu-desktop/2017-June/004980.html
  https://lists.ubuntu.com/archives/ubuntu-desktop/2017-July/005059.html

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

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

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

[Touch-packages] [Bug 1720368] Re: gsettings-data-convert crashed with signal 5 in g_settings_schema_get_value()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1720368/+attachment/4958708/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1720368/+attachment/4958710/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1720368/+attachment/4958714/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1720368/+attachment/4958715/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1720368/+attachment/4958716/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1720368/+attachment/4958717/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1720368/+attachment/4958718/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 945144
   gsettings-data-convert crashed with signal 5 in g_settings_set_value()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gsettings-data-convert crashed with signal 5 in
  g_settings_schema_get_value()

Status in gconf package in Ubuntu:
  New

Bug description:
  I was trying several desktop environments and after a while I found a
  crash file in /var/crash/.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 29 15:26:52 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gsettings-data-convert
  ProcCmdline: gsettings-data-convert
  Signal: 5
  SourcePackage: gconf
  StacktraceTop:
   g_settings_schema_get_value (schema=0x55b3d5780d40, key=0x55b3d57a71f0 
"auto-launch") at ../../../../gio/gsettingsschema.c:967
   g_settings_schema_key_init (key=key@entry=0x7ffccfe31a80, 
schema=0x55b3d5780d40, name=name@entry=0x55b3d57a71f0 "auto-launch") at 
../../../../gio/gsettingsschema.c:1246
   g_settings_set_value (settings=settings@entry=0x55b3d5730170 [GSettings], 
key=key@entry=0x55b3d57a71f0 "auto-launch", value=0x55b3d57a7960) at 
../../../../gio/gsettings.c:1563
   g_settings_set (settings=0x55b3d5730170 [GSettings], key=0x55b3d57a71f0 
"auto-launch", format=) at ../../../../gio/gsettings.c:1670
   ()
  Title: gsettings-data-convert crashed with signal 5 in 
g_settings_schema_get_value()
  UpgradeStatus: Upgraded to artful on 2017-09-29 (0 days ago)
  UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare 
staff sudo

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

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

[Touch-packages] [Bug 1681249] Re: tracker-extract crashed with signal 31 in chdir()

[Apport retracing service]

** Tags added: artful

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

Title:
  tracker-extract crashed with signal 31 in chdir()

Status in tracker package in Ubuntu:
  New

Bug description:
  tracker crash while indexing my homedir

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: tracker-extract 1.12.0-0ubuntu1
  Uname: Linux 4.10.8-041008-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr  8 14:00:45 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/tracker/tracker-extract
  ExecutableTimestamp: 1490023113
  JournalErrors:
   No journal files were found.
   -- No entries --
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcCwd: /home/bonnaudl
  Signal: 31
  SourcePackage: tracker
  Title: tracker-extract crashed with signal 31 in chdir()
  UpgradeStatus: Upgraded to zesty on 2017-04-08 (0 days ago)
  UserGroups: adm cdrom dip fuse libvirt libvirtd lpadmin plugdev sambashare 
staff sudo

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

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