[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

[damianreloaded]

I had a dns server configured in my thinkpad and 127.0.0.1 set in
resolv.conf. After upgrading from 16.04 to 17.04 resolv.conf gets reset
to 127.0.0.53 which in my humble opinion and extensive experience makes
absolutely no sense whatsoever. At the very least this file should be
left alone.

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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

[Touch-packages] [Bug 1741398] Re: Commented line in sudoers file breaks sudo

[Plutocrat]

cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"


Possibly related: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/501204

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

Title:
  Commented line in sudoers file breaks sudo

Status in sudo package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 Amazon AWS image. 
  sudo:
Installed: 1.8.16-0ubuntu1.5

  Used sudo visudo to edit /etc/sudoers file from the ubutntu admin user

  At the bottom of the file is a line

  #includedir /etc/sudoers.d

  I added a couple of lines at the end of the file to give permissions
  to another user. I accidentally hit backspace and altered the
  includedir line so it looked like this

  #includedir /etc/sudoercs

  I couldn't remember what the actual directory was at the time, but I
  thought, hey, its a commented line, it doesn't matter anyway. I was
  wrong.

  So visudo saved the file OK, but from then on, no valid sudo commands
  would work for any user. Including sudo visudo of course. Its an AWS
  instance, so no root login. Only recourse was to detach the volume,
  re-attach it to another instance, fix the spelling mistake.

  So obviously sudo freaked when the directory given didn't exist. But
  why would it, if the line is a comment? Something obviously wrong
  here. And given the lack of root, a particularly irritating and time
  consuming one.

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

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

[Touch-packages] [Bug 1741398] [NEW] Commented line in sudoers file breaks sudo

[Plutocrat]

Public bug reported:

Ubuntu 16.04 Amazon AWS image. 
sudo:
  Installed: 1.8.16-0ubuntu1.5

Used sudo visudo to edit /etc/sudoers file from the ubutntu admin user

At the bottom of the file is a line

#includedir /etc/sudoers.d

I added a couple of lines at the end of the file to give permissions to
another user. I accidentally hit backspace and altered the includedir
line so it looked like this

#includedir /etc/sudoercs

I couldn't remember what the actual directory was at the time, but I
thought, hey, its a commented line, it doesn't matter anyway. I was
wrong.

So visudo saved the file OK, but from then on, no valid sudo commands
would work for any user. Including sudo visudo of course. Its an AWS
instance, so no root login. Only recourse was to detach the volume, re-
attach it to another instance, fix the spelling mistake.

So obviously sudo freaked when the directory given didn't exist. But why
would it, if the line is a comment? Something obviously wrong here. And
given the lack of root, a particularly irritating and time consuming
one.

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

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

Title:
  Commented line in sudoers file breaks sudo

Status in sudo package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 Amazon AWS image. 
  sudo:
Installed: 1.8.16-0ubuntu1.5

  Used sudo visudo to edit /etc/sudoers file from the ubutntu admin user

  At the bottom of the file is a line

  #includedir /etc/sudoers.d

  I added a couple of lines at the end of the file to give permissions
  to another user. I accidentally hit backspace and altered the
  includedir line so it looked like this

  #includedir /etc/sudoercs

  I couldn't remember what the actual directory was at the time, but I
  thought, hey, its a commented line, it doesn't matter anyway. I was
  wrong.

  So visudo saved the file OK, but from then on, no valid sudo commands
  would work for any user. Including sudo visudo of course. Its an AWS
  instance, so no root login. Only recourse was to detach the volume,
  re-attach it to another instance, fix the spelling mistake.

  So obviously sudo freaked when the directory given didn't exist. But
  why would it, if the line is a comment? Something obviously wrong
  here. And given the lack of root, a particularly irritating and time
  consuming one.

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

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

[Touch-packages] [Bug 1730213] Re: Mouse cursor flickers with box when external Display Link monitor is connected

[Launchpad Bug Tracker]

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

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

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

Title:
  Mouse cursor flickers  with box when external Display Link monitor is
  connected

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I'm having the same issue as well. With three screens the mouse has a
  glitch where it's like part of the screen makes a box around it. It
  almost seems to happen on interactions.. It's very noticable moving
  over tabs on a browser window.

  I'm not sure if the same effect would happen with two video cards two
  monitors share the 1050ti with the Nvidia drivers installed. I did get
  the latest display link drivers installed.

  Thanks again for the help

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-39.43-generic 4.10.17
  Uname: Linux 4.10.0-39-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Sun Nov  5 11:30:06 2017
  DistUpgraded: 2017-11-05 00:25:16,311 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-28-generic, x86_64: installedError! Could not locate 
dkms.conf file.
   File:  does not exist.
   
   bbswitch, 0.8, 4.10.0-38-generic, x86_64: installed
   bbswitch, 0.8, 4.10.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6253]
  InstallationDate: Installed on 2017-11-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Gigabyte Technology Co., Ltd. H110M-M.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-39-generic 
root=UUID=8718e5d2-d2a9-4711-9619-505cb18367c9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2017-11-05 (0 days ago)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F21
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-M2-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF21:bd02/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnH110M-M.2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-M2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: H110M-M.2
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Nov  5 11:22:13 2017
  xserver.configfile: default
  

[Touch-packages] [Bug 1741045] Re: Change the default resample-method to speex-float-10 in daemon.conf

[Daniel van Vugt]

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

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

Title:
  Change the default resample-method to speex-float-10 in daemon.conf

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

Bug description:
  I suggest changing the default resample-method to speex-float-10,
  instead of speex-float-1, which is the current default now, in
  /etc/pulse/daemon.conf.

  It would look like this in daemon.conf:
  resample-method = speex-float-10

  I have always done that since at least 12.04 LTS. I was not satisfied
  with the sound quality in Ubuntu compared to Windows, so I changed the
  resample-method.

  In my day-to-day usage, it gives better sound quality without
  sacrificing CPU power.

  I have not tried other resample methods. Maybe there are better
  options I don't know about.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr1696 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 14:37:25 2018
  InstallationDate: Installed on 2017-10-02 (92 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[Seth Arnold]

Thanks for investigating!

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1631342] Re: [Raspberry Pi 2/3] Sound is stopping and starting in the beginning of each song

[Daniel van Vugt]

** Summary changed:

- Sound is stopping and starting in the beginning of each song
+ [Raspberry Pi 2/3] Sound is stopping and starting in the beginning of each 
song

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

Title:
  [Raspberry Pi 2/3] Sound is stopping and starting in the beginning of
  each song

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Senario is running on a raspberry pi 2/3:
  Running VLC Player or any other player and putting some MP3 songs in a list. 
Playing this list and when the song starts playing the sound becomes distorted 
with sound starting and stopping. After a few seconds the song continues 
normally. This happens even if i slide the general volume to lower and back to 
the same position during the playing any time. It is not happening every time 
the song changes or every time i slide the volume. Its an intermittent problem.

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial), please disable LLMNR

[Dimitri John Ledkov]

** Summary changed:

- Regression in getaddrinfo(): calls block for much longer on Bionic (compared 
to Xenial)
+ Regression in getaddrinfo(): calls block for much longer on Bionic (compared 
to Xenial), please disable LLMNR

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial), please disable LLMNR

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1741164] Re: package apport 2.20.1-0ubuntu2.13 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package apport 2.20.1-0ubuntu2.13 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Happened on startup, after password, loading desktop.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.13
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CrashReports:
   640:0:117:28321:2018-01-03 20:05:51.323303222 -0700:2018-01-03 
20:05:53.767416549 -0700:/var/crash/_usr_bin_pyclean.0.crash
   644:0:117:0:2018-01-03 20:05:53.767416549 -0700:2018-01-03 
20:05:53.767416549 -0700:/var/crash/_usr_bin_pyclean.0.upload
   640:0:117:94462:2018-01-03 20:05:53.363460302 -0700:2018-01-03 
20:05:54.363460302 -0700:/var/crash/apport.0.crash
   600:109:117:0:2018-01-03 20:05:55.019506896 -0700:2018-01-03 
20:05:55.019506896 -0700:/var/crash/_usr_bin_pyclean.0.uploaded
   640:0:117:16569:2018-01-03 20:05:25.257935448 -0700:2018-01-03 
20:05:25.257935448 -0700:/var/crash/_usr_bin_pycompile.0.crash
  Date: Wed Jan  3 20:05:25 2018
  DpkgHistoryLog:
   Start-Date: 2018-01-03  20:05:24
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: apport:amd64 (2.20.1-0ubuntu2.13, 2.20.1-0ubuntu2.15), 
python3-apport:amd64 (2.20.1-0ubuntu2.13, 2.20.1-0ubuntu2.15), 
libwebkit2gtk-4.0-37:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), 
apport-gtk:amd64 (2.20.1-0ubuntu2.13, 2.20.1-0ubuntu2.15), 
gir1.2-webkit2-4.0:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), 
libjavascriptcoregtk-4.0-18:amd64 (2.18.3-0ubuntu0.16.04.1, 
2.18.4-0ubuntu0.16.04.1), python3-problem-report:amd64 (2.20.1-0ubuntu2.13, 
2.20.1-0ubuntu2.15), libwebkit2gtk-4.0-37-gtk2:amd64 (2.18.3-0ubuntu0.16.04.1, 
2.18.4-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:amd64 
(2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1)
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-08-11 (145 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.13 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/apport/+bug/1741164/+subscriptions

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Dimitri John Ledkov]

avahi is zeroconf or IPv4LL, which is RFC 3927; whilst LLMNR is RFC
4795. In many aspects LLMNR is like mdns, yet the two are distinct and
resolve different things quite differently, when inspected closer.


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

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1741365] [NEW] i don't know

[PAUL WESTON]

Public bug reported:

not sure

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jan  4 15:04:52 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GK107 [GeForce GT 630 OEM] [10de:0fc2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK107 [GeForce GT 630 OEM] [1043:83e2]
InstallationDate: Installed on 2017-12-26 (9 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: ASUSTeK COMPUTER INC. CM6870
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0408
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CM6870
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0408:bd02/24/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: CM6870
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jan  4 01:51:57 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  i don't know

Status in xorg package in Ubuntu:
  New

Bug description:
  not sure

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan  4 15:04:52 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 630 OEM] [10de:0fc2] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK107 [GeForce GT 630 OEM] [1043:83e2]
  InstallationDate: Installed on 2017-12-26 (9 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: ASUSTeK COMPUTER INC. CM6870
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0408
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6870
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Mike Pontillo]

Workaround:

grep -q 'LLMNR=no' /etc/systemd/resolved.conf || \
echo 'LLMNR=no' | sudo tee -a /etc/systemd/resolved.conf
sudo service systemd-networkd restart

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1733700] Re: python tools do not understand 'non-magic' include rules

[Jamie Strandboge]

** Description changed:

  The apparmor parser supports 'include' and '#include' rules for
  specifying absolute paths, but the python tools only understand include
  rules for so called 'magic' '<>' file locations.
  
+ = test case #0 (testsuite) =
+ $ sudo apt-get install apparmor apparmor-utils # not required with 2.12
+ $ sudo apt-get build-dep apparmor
+ $ sudo apt-get install quilt pyflakes pyflakes3
+ $ apt-get source apparmor
+ $ cd apparmor-*
+ $ quilt push -a
+ $ export PYTHONPATH=$(realpath libraries/libapparmor/swig/python)
+ $ export PYTHON=/usr/bin/python3
+ $ export PYTHON_VERSION=3
+ $ export PYTHON_VERSIONS=python3
+ $ cd libraries/libapparmor
+ $ sh ./autogen.sh
+ $ sh ./configure --prefix=/usr --with-perl --with-python
+ $ make
+ $ cd ../../binutils
+ $ make
+ $ ../parser
+ $ make
+ $ cd ../utils
+ $ make
+ $ make check
  
  = test case #1 (aa-enforce) =
  $ mkdir /tmp/test1 /tmp/test2
  
  $ cat /etc/apparmor.d/lp1733700
  profile lp1733700 {
#include "/tmp/test1"
include "/tmp/test2"
  }
  
  $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok
  
  $ sudo aa-enforce /etc/apparmor.d/lp1733700 # currently fails
  
  
  = test case #2 (aa-genprof) =
  
  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.
  
  $ cat /tmp/lp1733700
  #!/bin/sh
  set -e
  sh -c "$@"
  
  # run without confinement:
  $ /tmp/lp1733700 'cat /etc/fstab' | head -1
  # /etc/fstab: static file system information.
  
  # invoke genprof
  $ sudo aa-genprof /tmp/lp1733700
  ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 's' - currently 
fails
  ... don't exercise the application any so we just have the default profile ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 'f'
  ...
  Finished generating profile for /tmp/lp1733700.
  
  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 15:53:07 2017
  #include 
  
  /tmp/lp1733700 {
#include 
#include 
  
/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,
  
  }
  
  
  = test case #3 (aa-logprof) =
  
  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.
  
  This also assumes test case #2 was already performed and
  /etc/apparmor.d/tmp.lp1733700 exists.
  
  Disable kernel rate limiting:
  $ sudo sysctl -w kernel.printk_ratelimit=0
  
  Create mark entry in syslog:
  $ logger mark-lp1733700
  
  Try running logprof with no new denials:
  
  $ sudo aa-logprof -m mark-lp1733700   # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  $
  
  Adjust /etc/apparmor.d/tmp.lp1733700 to add:
  
#include "/tmp/test1"
include "/tmp/test2"
  
  Load it into the kernel:
  $ sudo apparmor_parser -r /etc/apparmor.d/tmp.lp1733700
  
  Create a new denial:
  $ /tmp/lp1733700 'uptime'
  sh: 1: uptime: Permission denied
  $
  
  Try running logprof:
  
  $ sudo aa-logprof -m mark-lp1733700 # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  
  Profile:  /tmp/lp1733700
  Execute:  /usr/bin/uptime
  Severity: unknown
  
  (I)nherit / (C)hild / (N)amed / (X) ix On / (D)eny / Abo(r)t / (F)inish
  ...
  The following local profiles were changed. Would you like to save them?
  
   [1 - /tmp/lp1733700]
  (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes 
b/w (C)lean profiles / Abo(r)t
  
  
  Writing updated profile for /tmp/lp1733700.
  $
  
  Verify the profile for 'uptime' addition and that the /tmp/test1 and
  /tmp/test2 includes were not removed (it is ok that they are both
  '#include'):
  
  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 16:19:19 2017
  #include 
  
  /tmp/lp1733700 {
#include "/tmp/test1"
#include "/tmp/test2"
#include 
#include 
  
/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,
/usr/bin/uptime mrix,
  
  }
  
  
  = test case #4 (aa-mergeprof) =
  
  $ mkdir -p /tmp/aa-mergeprof/new
  $ mkdir /tmp/aa-mergeprof/new/tunables /tmp/aa-mergeprof/new/abstractions
  $ touch /tmp/aa-mergeprof/new/tunables/global 
/tmp/aa-mergeprof/new/abstractions/base /tmp/aa-mergeprof/new/abstractions/bash
  $ cp -a /tmp/aa-mergeprof/new /tmp/aa-mergeprof/old
  
  $ cat /tmp/aa-mergeprof/old/tmp.lp1733700 # no test2 include or cat
  #include 
  
  /tmp/lp1733700 {
#include 
#include 
#include "/tmp/test1"
  
/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,
/usr/bin/uptime mrix,
  
  }
  
  $ cat /tmp/aa-mergeprof/new/tmp.lp1733700 # no test1 include or uptime
  #include 
  
  /tmp/lp1733700 {
#include 
#include 
#include "/tmp/test2"
  
/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,
/bin/cat ixr,
  
  }
  
  $ sudo aa-mergeprof -d /tmp/aa-mergeprof/new 

[Touch-packages] [Bug 1733700] Re: python tools do not understand 'non-magic' include rules

[Jamie Strandboge]

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

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

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

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

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

Title:
  python tools do not understand 'non-magic' include rules

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Trusty:
  Triaged
Status in apparmor source package in Xenial:
  Triaged
Status in apparmor source package in Zesty:
  Triaged
Status in apparmor source package in Artful:
  Triaged
Status in apparmor source package in Bionic:
  In Progress

Bug description:
  The apparmor parser supports 'include' and '#include' rules for
  specifying absolute paths, but the python tools only understand
  include rules for so called 'magic' '<>' file locations.

  = test case #0 (testsuite) =
  $ sudo apt-get install apparmor apparmor-utils # not required with 2.12
  $ sudo apt-get build-dep apparmor
  $ sudo apt-get install quilt pyflakes pyflakes3
  $ apt-get source apparmor
  $ cd apparmor-*
  $ quilt push -a
  $ export PYTHONPATH=$(realpath libraries/libapparmor/swig/python)
  $ export PYTHON=/usr/bin/python3
  $ export PYTHON_VERSION=3
  $ export PYTHON_VERSIONS=python3
  $ cd libraries/libapparmor
  $ sh ./autogen.sh
  $ sh ./configure --prefix=/usr --with-perl --with-python
  $ make
  $ cd ../../binutils
  $ make
  $ ../parser
  $ make
  $ cd ../utils
  $ make
  $ make check

  = test case #1 (aa-enforce) =
  $ mkdir /tmp/test1 /tmp/test2

  $ cat /etc/apparmor.d/lp1733700
  profile lp1733700 {
#include "/tmp/test1"
include "/tmp/test2"
  }

  $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok

  $ sudo aa-enforce /etc/apparmor.d/lp1733700 # currently fails

  
  = test case #2 (aa-genprof) =

  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.

  $ cat /tmp/lp1733700
  #!/bin/sh
  set -e
  sh -c "$@"

  $ chmod 755 /tmp/lp1733700

  # run without confinement:
  $ /tmp/lp1733700 'cat /etc/fstab' | head -1
  # /etc/fstab: static file system information.

  # invoke genprof
  $ sudo aa-genprof /tmp/lp1733700
  ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 's' - currently 
fails
  ... don't exercise the application any so we just have the default profile ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 'f'
  ...
  Finished generating profile for /tmp/lp1733700.

  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 15:53:07 2017
  #include 

  /tmp/lp1733700 {
#include 
#include 

/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,

  }

  
  = test case #3 (aa-logprof) =

  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.

  This also assumes test case #2 was already performed and
  /etc/apparmor.d/tmp.lp1733700 exists.

  Disable kernel rate limiting:
  $ sudo sysctl -w kernel.printk_ratelimit=0

  Create mark entry in syslog:
  $ logger mark-lp1733700

  Try running logprof with no new denials:

  $ sudo aa-logprof -m mark-lp1733700   # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  $

  Adjust /etc/apparmor.d/tmp.lp1733700 to add:

#include "/tmp/test1"
include "/tmp/test2"

  Load it into the kernel:
  $ sudo apparmor_parser -r /etc/apparmor.d/tmp.lp1733700

  Create a new denial:
  $ /tmp/lp1733700 'uptime'
  sh: 1: uptime: Permission denied
  $

  Try running logprof:

  $ sudo aa-logprof -m mark-lp1733700 # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.

  Profile:  /tmp/lp1733700
  Execute:  /usr/bin/uptime
  Severity: unknown

  (I)nherit / (C)hild / (N)amed / (X) ix On / (D)eny / Abo(r)t / (F)inish
  ...
  The following local profiles were changed. Would you like to save them?
  
   [1 - /tmp/lp1733700]
  (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes 
b/w (C)lean profiles / Abo(r)t
  

  Writing updated profile for /tmp/lp1733700.
  $

  Verify the profile for 'uptime' addition and that the /tmp/test1 and
  /tmp/test2 includes were not removed (it is ok that they are both
  '#include'):

  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 16:19:19 2017
  #include 

  /tmp/lp1733700 {
#include "/tmp/test1"
#include "/tmp/test2"
#include 
#include 

/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,

[Touch-packages] [Bug 1737592] Re: no zfs module in initramfs

[Scott Moser]

** Changed in: maas-images
   Status: Confirmed => Fix Committed

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

Title:
  no zfs module in initramfs

Status in maas-images:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  zfs support exists in Ubuntu kernels for 16.04 and later, but the
  default initramfs build does not include this module.

  Other common filesystems are included.

  As a small piece of information:
  $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
  3.2M  /lib/modules/4.13.0-17-generic/kernel/zfs/


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools-core 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 13:05:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (872 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1737592/+subscriptions

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

[Touch-packages] [Bug 1631342] Re: Sound is stopping and starting in the beginning of each song

[Sebastian Ramacher]

Affects all players, so not a vlc bug. Reassigning to pulseaudio, but
might as well be a kernel, driver or hardware bug.

** Package changed: vlc (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Sound is stopping and starting in the beginning of each song

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Senario is running on a raspberry pi 2/3:
  Running VLC Player or any other player and putting some MP3 songs in a list. 
Playing this list and when the song starts playing the sound becomes distorted 
with sound starting and stopping. After a few seconds the song continues 
normally. This happens even if i slide the general volume to lower and back to 
the same position during the playing any time. It is not happening every time 
the song changes or every time i slide the volume. Its an intermittent problem.

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

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

[Touch-packages] [Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Konrad Krawiec]

I can confirm this bug on Ubuntu 18.04 (20180104). I checked the auto
log in option in the installer, but I still need to log in manually.

** Tags added: bionic

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in Ubuntu GNOME:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1631342] [NEW] Sound is stopping and starting in the beginning of each song

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Senario is running on a raspberry pi 2/3:
Running VLC Player or any other player and putting some MP3 songs in a list. 
Playing this list and when the song starts playing the sound becomes distorted 
with sound starting and stopping. After a few seconds the song continues 
normally. This happens even if i slide the general volume to lower and back to 
the same position during the playing any time. It is not happening every time 
the song changes or every time i slide the volume. Its an intermittent problem.

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


** Tags: audio sound
-- 
Sound is stopping and starting in the beginning of each song
https://bugs.launchpad.net/bugs/1631342
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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

[Touch-packages] [Bug 1741331] Re: Ethernet interface aquire IP even if not defined in /etc/network/interfaces

[Fawzi Masri]

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

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

Title:
  Ethernet interface aquire IP even if not defined in
  /etc/network/interfaces

Status in Ubuntu:
  New

Bug description:
  i have a server (Proliant DL380 gen9). it has 4 Ethernet ports eno1 thru 
eno4. i am using ubuntu 17.10 and KVM with 4 multiple guest VMs. 
  under Ubuntu 17.04 i had this in my /etc/network/interfaces:

  
 auto virbr0
 iface virbr0 inet dhcp
 bridge_ports eno1
 bridge_stp off
 bridge_fd 0
 bridge_maxwait 0   

  So i did not define eno2 thru eno4 and everything worked fine.

  After i upgraded to Ubuntu 17.10, i suddenly started having IP conflict from 
the DHCP server. 
  after a lot of search, i figured my problem may be from the eno2-4 are 
getting IP even though they are dedicated to VMs.

  so i defined them as manual in /etc/network/interfaces as such:
  # Ethernet port for cad-srvr VM
  auto eno2
  iface eno2 inet manual
  up ifconfig eno2 up

  # Ethernet port for nxtcld-srvr VM
  auto eno3
  iface eno3 inet manual
  up ifconfig eno3 up

  # Ethernet port for Future-srvr VM
  auto eno4
  iface eno4 inet manual
  up ifconfig eno4 up

  
  This caused the DHCP warnings of conflicted IP to disappear.

  I am not sure if this is per design or not... 
  please advice me if i need to provide any other info

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

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

[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string

[Michael Vogt]

Yes, I will work on this!

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  New
Status in initramfs-tools-ubuntu-core source package in Xenial:
  Fix Released

Bug description:
  [TEST CASE]
  * this will be tested by the snappy team
  * without this fix the dragonboard will not boot on a freshly written image

  [REGRESSION POTENTIAL]
  * low as it only fixes an invalid string

  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

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

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

[Touch-packages] [Bug 1741331] [NEW] Ethernet interface aquire IP even if not defined in /etc/network/interfaces

[Fawzi Masri]

Public bug reported:

i have a server (Proliant DL380 gen9). it has 4 Ethernet ports eno1 thru eno4. 
i am using ubuntu 17.10 and KVM with 4 multiple guest VMs. 
under Ubuntu 17.04 i had this in my /etc/network/interfaces:


   auto virbr0
   iface virbr0 inet dhcp
   bridge_ports eno1
   bridge_stp off
   bridge_fd 0
   bridge_maxwait 0   

So i did not define eno2 thru eno4 and everything worked fine.

After i upgraded to Ubuntu 17.10, i suddenly started having IP conflict from 
the DHCP server. 
after a lot of search, i figured my problem may be from the eno2-4 are getting 
IP even though they are dedicated to VMs.

so i defined them as manual in /etc/network/interfaces as such:
# Ethernet port for cad-srvr VM
auto eno2
iface eno2 inet manual
up ifconfig eno2 up

# Ethernet port for nxtcld-srvr VM
auto eno3
iface eno3 inet manual
up ifconfig eno3 up

# Ethernet port for Future-srvr VM
auto eno4
iface eno4 inet manual
up ifconfig eno4 up


This caused the DHCP warnings of conflicted IP to disappear.

I am not sure if this is per design or not... 
please advice me if i need to provide any other info

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

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

Title:
  Ethernet interface aquire IP even if not defined in
  /etc/network/interfaces

Status in apparmor package in Ubuntu:
  New

Bug description:
  i have a server (Proliant DL380 gen9). it has 4 Ethernet ports eno1 thru 
eno4. i am using ubuntu 17.10 and KVM with 4 multiple guest VMs. 
  under Ubuntu 17.04 i had this in my /etc/network/interfaces:

  
 auto virbr0
 iface virbr0 inet dhcp
 bridge_ports eno1
 bridge_stp off
 bridge_fd 0
 bridge_maxwait 0   

  So i did not define eno2 thru eno4 and everything worked fine.

  After i upgraded to Ubuntu 17.10, i suddenly started having IP conflict from 
the DHCP server. 
  after a lot of search, i figured my problem may be from the eno2-4 are 
getting IP even though they are dedicated to VMs.

  so i defined them as manual in /etc/network/interfaces as such:
  # Ethernet port for cad-srvr VM
  auto eno2
  iface eno2 inet manual
  up ifconfig eno2 up

  # Ethernet port for nxtcld-srvr VM
  auto eno3
  iface eno3 inet manual
  up ifconfig eno3 up

  # Ethernet port for Future-srvr VM
  auto eno4
  iface eno4 inet manual
  up ifconfig eno4 up

  
  This caused the DHCP warnings of conflicted IP to disappear.

  I am not sure if this is per design or not... 
  please advice me if i need to provide any other info

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

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

[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

[Paweu]

I'd gladly help with this issue is any of the developers willing to do
this? I can provide alsa info and other stuff. I mean... its a pain it
hasn't been solved for almost two years now.

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Joseph Salisbury]

** Tags removed: kernel-da-key

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1733700] Re: python tools do not understand 'non-magic' include rules

[Jamie Strandboge]

The was fixed upstream in 2.12.

** Changed in: apparmor
   Status: In Progress => Fix Released

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

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

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

Title:
  python tools do not understand 'non-magic' include rules

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  In Progress
Status in apparmor source package in Trusty:
  Triaged
Status in apparmor source package in Xenial:
  Triaged
Status in apparmor source package in Zesty:
  Triaged
Status in apparmor source package in Artful:
  Triaged
Status in apparmor source package in Bionic:
  In Progress

Bug description:
  The apparmor parser supports 'include' and '#include' rules for
  specifying absolute paths, but the python tools only understand
  include rules for so called 'magic' '<>' file locations.

  
  = test case #1 (aa-enforce) =
  $ mkdir /tmp/test1 /tmp/test2

  $ cat /etc/apparmor.d/lp1733700
  profile lp1733700 {
#include "/tmp/test1"
include "/tmp/test2"
  }

  $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok

  $ sudo aa-enforce /etc/apparmor.d/lp1733700 # currently fails

  
  = test case #2 (aa-genprof) =

  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.

  $ cat /tmp/lp1733700
  #!/bin/sh
  set -e
  sh -c "$@"

  # run without confinement:
  $ /tmp/lp1733700 'cat /etc/fstab' | head -1
  # /etc/fstab: static file system information.

  # invoke genprof
  $ sudo aa-genprof /tmp/lp1733700
  ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 's' - currently 
fails
  ... don't exercise the application any so we just have the default profile ...
  [(S)can system log for AppArmor events] / (F)inish - PRESS 'f'
  ...
  Finished generating profile for /tmp/lp1733700.

  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 15:53:07 2017
  #include 

  /tmp/lp1733700 {
#include 
#include 

/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,

  }

  
  = test case #3 (aa-logprof) =

  This assumes test case #1 was already performed and
  /etc/apparmor.d/lp1733700 exists with the above includes.

  This also assumes test case #2 was already performed and
  /etc/apparmor.d/tmp.lp1733700 exists.

  Disable kernel rate limiting:
  $ sudo sysctl -w kernel.printk_ratelimit=0

  Create mark entry in syslog:
  $ logger mark-lp1733700

  Try running logprof with no new denials:

  $ sudo aa-logprof -m mark-lp1733700   # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  $

  Adjust /etc/apparmor.d/tmp.lp1733700 to add:

#include "/tmp/test1"
include "/tmp/test2"

  Load it into the kernel:
  $ sudo apparmor_parser -r /etc/apparmor.d/tmp.lp1733700

  Create a new denial:
  $ /tmp/lp1733700 'uptime'
  sh: 1: uptime: Permission denied
  $

  Try running logprof:

  $ sudo aa-logprof -m mark-lp1733700 # currently fails
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.

  Profile:  /tmp/lp1733700
  Execute:  /usr/bin/uptime
  Severity: unknown

  (I)nherit / (C)hild / (N)amed / (X) ix On / (D)eny / Abo(r)t / (F)inish
  ...
  The following local profiles were changed. Would you like to save them?
  
   [1 - /tmp/lp1733700]
  (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes 
b/w (C)lean profiles / Abo(r)t
  

  Writing updated profile for /tmp/lp1733700.
  $

  Verify the profile for 'uptime' addition and that the /tmp/test1 and
  /tmp/test2 includes were not removed (it is ok that they are both
  '#include'):

  $ sudo cat /etc/apparmor.d/tmp.lp1733700
  # Last Modified: Wed Dec 20 16:19:19 2017
  #include 

  /tmp/lp1733700 {
#include "/tmp/test1"
#include "/tmp/test2"
#include 
#include 

/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,
/usr/bin/uptime mrix,

  }

  
  = test case #4 (aa-mergeprof) =

  $ mkdir -p /tmp/aa-mergeprof/new
  $ mkdir /tmp/aa-mergeprof/new/tunables /tmp/aa-mergeprof/new/abstractions
  $ touch /tmp/aa-mergeprof/new/tunables/global 
/tmp/aa-mergeprof/new/abstractions/base /tmp/aa-mergeprof/new/abstractions/bash
  $ cp -a /tmp/aa-mergeprof/new /tmp/aa-mergeprof/old

  $ cat /tmp/aa-mergeprof/old/tmp.lp1733700 # no test2 include or cat
  #include 

  /tmp/lp1733700 {
#include 
#include 
#include "/tmp/test1"

/bin/dash ix,
/lib/x86_64-linux-gnu/ld-*.so mr,
/tmp/lp1733700 r,
/usr/bin/uptime mrix,

  }

  $ cat /tmp/aa-mergeprof/new/tmp.lp1733700 # no test1 include or uptime
  #include 

  /tmp/lp1733700 {
#include 
#include 
#include 

[Touch-packages] [Bug 1737592] Re: no zfs module in initramfs

[Launchpad Bug Tracker]

** Branch linked: lp:maas-images

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

Title:
  no zfs module in initramfs

Status in maas-images:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  zfs support exists in Ubuntu kernels for 16.04 and later, but the
  default initramfs build does not include this module.

  Other common filesystems are included.

  As a small piece of information:
  $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/
  3.2M  /lib/modules/4.13.0-17-generic/kernel/zfs/


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools-core 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 11 13:05:15 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (872 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/1737592/+subscriptions

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

[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string

[Oliver Grawert]

since we dont build ubuntu core images based on the artful archive this
would just be cosmetic ... (but yeah, technically we could also upload
it to artful ... xenial and bionic are the critical ones here though)

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

Title:
  fixrtc script does not catch "Last mount time: n/a" string

Status in Snappy:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools-ubuntu-core package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  New
Status in initramfs-tools-ubuntu-core source package in Xenial:
  Fix Released

Bug description:
  [TEST CASE]
  * this will be tested by the snappy team
  * without this fix the dragonboard will not boot on a freshly written image

  [REGRESSION POTENTIAL]
  * low as it only fixes an invalid string

  trying to boot a new dragonboard image results in:

  error: assertion is signed with expired public key
  "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by
  canonical

  this is due to a clock skew that should normally be catched by the
  fixrtc script in the initrd.

  the script is supposed to check the last mount time of the writable
  disk (SD card) and if this does not exist, fall back to the filesystem
  creation time ...

  in former versions of mkfs.ext4 the last mount time filed was simply
  left empty, so this fallback worked fine ... in xenial the fields now
  look like:

  Filesystem created:   Tue Sep 13 17:32:20 2016
  Last mount time:  n/a
  Last write time:  Tue Sep 13 17:32:20 2016

  due to the script running with "set -e" it falls over on the "n/a" and
  exists before falling back to creation time, there needs to be a check
  added for the "n/a" string now.

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Mike Pontillo]

Interesting; the first thing I tried when triaging this was to edit
/etc/nsswitch.conf as follows:

# hosts:  files mdns4_minimal [NOTFOUND=return] dns myhostname
hosts:  files dns

... to eliminate the possibility that it was multicast DNS causing the
slowdown. But it appears I'm behind the times. ;-) (And didn't this only
affect the .local domain?)

Does this mean there are now two subsystems responsible for link-local
address resolution? (avahi and systemd-resolved?)

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1730744] Re: sudo is slow (10 seconds) when hostname is not resolvable

[Steve Langasek]

This looks like the same as the just-diagnosed
https://launchpad.net/bugs/1739672

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

Title:
  sudo is slow (10 seconds) when hostname is not resolvable

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm seeing very slow 'sudo' times in a qemu guest when the host uses 
systemd-resolved.
  If I change /etc/resolv.conf on the host to point directly to a dns server 
(8.8.8.8) then the problem goes away.

  
  To recreate, you can download a cloud image and boot it under qemu with a 
command line like:
cloud-localds seed.img user-data meta-data 
qemu-system-x86_64 -enable-kvm \
   -device virtio-net-pci,netdev=net00 \
   -netdev type=user,id=net00 \
   -drive file=root.img,id=disk00,if=none,index=0 \
   -device virtio-blk,drive=disk00,serial=root.img \
   -drive file=seed.img,id=disk01,if=none,index=1 \
   -device virtio-blk,drive=disk01,serial=seed.img \
   -m 768

  Make sure that your hostname does not resolve (change it to 'bogus-host1').
  Log into the guest and then just try sudo, you'll see something like:
  # time sudo ls
  sudo: unable to resolve host rooturl-trusty

  real0m10.029s
  user0m0.006s
  sys 0m0.011s

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

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

[Touch-packages] [Bug 1741274] Re: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging tot overschrijven van gedeelde '/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt

[Hans Joachim Desserud]

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

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

** This bug has been marked a duplicate of bug 1574351
   package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different 
from other instances of package libperl5.22:i386

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

Title:
  package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging
  tot overschrijven van gedeelde
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van
  andere exemplaren van pakket libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  the crash popped up out of the blue, was just working without any
  indication that installing/upgrading was happening.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-8ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-lowlatency 4.13.13
  Uname: Linux 4.13.0-21-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Thu Jan  4 12:49:36 2018
  ErrorMessage: poging tot overschrijven van gedeelde 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere 
exemplaren van pakket libperl5.26:i386
  InstallationDate: Installed on 2017-03-09 (301 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging 
tot overschrijven van gedeelde 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere 
exemplaren van pakket libperl5.26:i386
  UpgradeStatus: Upgraded to artful on 2017-10-21 (74 days ago)

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Steve Langasek]

> The dns resolution from systemd-resolve is fast; the llmnr one is not.
> We currently have llmnr resolution enabled by default. ...it's a feature?!

It is not a feature for a local DNS resolver to be doing llmnr under the
hood by default.  Please disable this.

> What is the use case of resolving things that do not exist?

DNS search paths.
User typoed the name and shouldn't have to wait 10 seconds for the response.

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Dimitri John Ledkov]

$ time systemd-resolve -p dns not-a-real-hostname
not-a-real-hostname: resolve call failed: No appropriate name servers or 
networks for name found

real0m0.003s
user0m0.000s
sys 0m0.004s

$ time systemd-resolve -p llmnr not-a-real-hostname
not-a-real-hostname: resolve call failed: All attempts to contact name servers 
or networks failed

real0m0.850s
user0m0.000s
sys 0m0.004s

$ time systemd-resolve -p llmnr-ipv4 not-a-real-hostname
not-a-real-hostname: resolve call failed: All attempts to contact name servers 
or networks failed

real0m0.820s
user0m0.000s
sys 0m0.000s

$ time systemd-resolve -p llmnr-ipv6 not-a-real-hostname
not-a-real-hostname: resolve call failed: All attempts to contact name servers 
or networks failed

real0m0.750s
user0m0.000s
sys 0m0.000s

$ time systemd-resolve not-a-real-hostname
not-a-real-hostname: resolve call failed: All attempts to contact name servers 
or networks failed

real0m0.712s
user0m0.004s
sys 0m0.000s

The dns resolution from systemd-resolve is fast; the llmnr one is not.
We currently have llmnr resolution enabled by default. ...it's a
feature?!

What is the usecase of resolving things that do not exist? Surely we
optimise for the fact that most resolutions will succeed, from
performance point of view. The first result retrieved, is returned back.

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Steve Langasek]

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

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Dimitri John Ledkov]

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

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

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

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

** Changed in: systemd (Ubuntu Artful)
   Status: Triaged => Invalid

** Changed in: systemd (Ubuntu Bionic)
   Status: Triaged => Invalid

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

Title:
  enabling networkd appears to eat up entropy

Status in nplan package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in nplan source package in Xenial:
  Fix Committed
Status in openssh source package in Xenial:
  Won't Fix
Status in systemd source package in Xenial:
  Invalid
Status in nplan source package in Zesty:
  Fix Committed
Status in openssh source package in Zesty:
  Won't Fix
Status in systemd source package in Zesty:
  Invalid
Status in nplan source package in Artful:
  Fix Released
Status in openssh source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Invalid
Status in nplan source package in Bionic:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Booting systems have a limited amount of entropy, especially in some of the 
cloud cases. We should avoid using it up unnecessarily.

  [Test cases]

  == netplan ==
  1) Boot system with netplan config; using networkd renderer
  2) Validate that it starts and does not cause undue delay.
  2b) strace nplan at boottime (the netplan generator at 
/lib/systemd/system-generators/netplan) and validate it does not call 
get_random() / uuid_generate().
  3) Validate that config with NetworkManager renderer generates UUIDs.

  [Regression potential]
  Netplan depends on UUID generation to create correct networkManager 
configuration for VLANs. This is a specific use-case that is typically not hit, 
but any failure to generate valid NetworkManager configuration would be a 
regression from this SRU.

  ---

  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/nplan/+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 1739531] Re: apport-collect SHOULD NOT collect gnome-shell command history and favorites

[Steve Langasek]

** Also affects: apport (Ubuntu Bionic)
   Importance: High
   Status: Confirmed

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

Title:
  apport-collect SHOULD NOT collect gnome-shell command history and
  favorites

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Bionic:
  Confirmed

Bug description:
  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1739525/comments/4, I ran apport-collect for that bug
  report.

  To my horror, it posted "org.gnome.shell command-history" and "favorites" in 
the "GsettingsChanges.txt"!
  https://launchpadlibrarian.net/349970997/GsettingsChanges.txt

  It's _completely_ reasonable to see:
   * enabled-extensions
   * org.gnome.shell.* diffs
   * org.gnome.desktop.* diffs

  But it is _NOT_ acceptable (privacy reasons) to automatically harvest
  a user's favorites in the gnome-shell, nor their command histories.

  _IF_ we must harvest for bug-data gathering, it MUST come in a secure
  mechanism that is private only to submitter + the assigned dev.

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

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

[Touch-packages] [Bug 1713004] Re: Temporary files left under /var/tmp by mkinitramfs

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.103ubuntu4.10

---
initramfs-tools (0.103ubuntu4.10) trusty; urgency=medium

  * mkinitramfs: Delete or report temporary files in /var/tmp/ on failure.
(LP: #1713004)

 -- Brian Murray   Tue, 05 Dec 2017 11:29:04 -0800

** Changed in: initramfs-tools (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Temporary files left under /var/tmp by mkinitramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  Test Case
  -
  1) confirm there are no mkinitramfs junk files in /var/tmp
  2) run 'sudo update-initramfs -k all -u -v'
  3) interrupt update-initramfs with Ctrl-C
  4) observe junk files in /var/tmp e.g. /var/tmp/mkinitramfs*

  With the version of initramfs-tools in -proposed you should see not
  have any leftovers in /var/tmp.

  I recently ran out of disk space on my / mount.  While looking for
  what consumed the disk I noticed a large number (130) of directories
  with names / paths beginning /var/tmp/mkinitramfs.  These directories
  seem to be either ~103 MB or ~927 MB in size.  Many of these files are
  months old, some are almost a year.

  Having had a quick look about for an explanation as to why these files
  are here and found Debian Bug #814345.  That explains that temporary
  files are left behind by the initramfs-tools if something fails in the
  process.  If this is the cause of my files then updating the Ubuntu
  package to version 0.123 should resolve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 25 09:40:41 2017
  InstallationDate: Installed on 2015-03-12 (896 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.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/ubuntu/+source/initramfs-tools/+bug/1713004/+subscriptions

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

[Touch-packages] [Bug 1683576] Re: cd with multiple directory argument fails

[Norbert]

** Tags added: zesty

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

Title:
  cd with multiple directory argument fails

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  In bash 4.4, a new behaviour was introduced for cd, where it would complain 
if multiple arguments are provided. From config-top.h [1]:
   
  /* Define CD_COMPLAINS if you want the non-standard, but sometimes-desired
 error messages about multiple directory arguments to `cd'. */
  #define CD_COMPLAINS

  It seems like this is enabled for Ubuntu. However, this behaviour
  conflicts with the manual (both Ubuntu's and GNU's), which says
  something similar to: "Any additional arguments following directory
  are ignored."

  Please revert to the old behaviour, or correct the manual. This is not
  a user-configurable setting, and push is also affected.

  Ubuntu 17.04
  bash 4.4-2ubuntu1

  
  [1]: http://git.savannah.gnu.org/cgit/bash.git/tree/config-top.h#n30

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Blake Rouse]

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

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Blake Rouse]

$ systemd-resolve --status
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 8 (vethJWPPL8)
  Current Scopes: LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 4 (lxdbr0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 3 (eno1)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 192.168.1.1

Link 2 (enp4s0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Blake Rouse]

The issue is with the systemd resolver not with glibc.

With systemd-resolve IP in /etc/resolv.conf:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53

$ time ./test not-a-hostname
Trying to resolve: not-a-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)

real0m10.076s
user0m0.001s
sys 0m0.000s


Without systemd-resolve in /etc/resolv.conf. I changed it to point to my local 
DNS server directly.

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
#nameserver 127.0.0.53
nameserver 192.168.1.1

$ time ./test not-a-hostname
Trying to resolve: not-a-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)

real0m0.097s
user0m0.001s
sys 0m0.000s


** Changed in: glibc (Ubuntu)
   Status: New => 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/1739672

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  When testing MAAS on Bionic, we noticed sluggish performance that we
  could not immediately explain.

  After comparing the results from a run of the test suite on Xenial to
  a run on Bionic, we determined that the slowdowns had to do with DNS
  lookups. In particular, if MAAS attempts to resolve a hostname using
  getaddrinfo() and the call fails, on Xenial the negative result is
  returned in a fraction of a second. On Bionic, the negative result is
  returned in ~1.6 seconds, according to some measures.

  ### To run the test ###

  git clone https://github.com/mpontillo/test-getaddrinfo
  cd test-getaddrinfo
  make

  ### Results on Xenial ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Success
  getaddrinfo() return value: -2 (Name or service not known)

  real  0m0.015s
  user  0m0.000s
  sys   0m0.000s

  ### Results on Bionic ###
  $ time ./test not-a-real-hostname
  Trying to resolve: not-a-real-hostname
  getaddrinfo errno: Resource temporarily unavailable
  getaddrinfo() return value: -3 (Temporary failure in name resolution)

  real  0m1.609s
  user  0m0.004s
  sys   0m0.000s

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

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

[Touch-packages] [Bug 1741274] [NEW] package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging tot overschrijven van gedeelde '/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschil

[bartje]

Public bug reported:

the crash popped up out of the blue, was just working without any
indication that installing/upgrading was happening.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libperl5.26 5.26.0-8ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-21.24-lowlatency 4.13.13
Uname: Linux 4.13.0-21-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
Date: Thu Jan  4 12:49:36 2018
ErrorMessage: poging tot overschrijven van gedeelde 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere 
exemplaren van pakket libperl5.26:i386
InstallationDate: Installed on 2017-03-09 (301 days ago)
InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: perl
Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging 
tot overschrijven van gedeelde 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere 
exemplaren van pakket libperl5.26:i386
UpgradeStatus: Upgraded to artful on 2017-10-21 (74 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging
  tot overschrijven van gedeelde
  '/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van
  andere exemplaren van pakket libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  the crash popped up out of the blue, was just working without any
  indication that installing/upgrading was happening.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libperl5.26 5.26.0-8ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-lowlatency 4.13.13
  Uname: Linux 4.13.0-21-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Thu Jan  4 12:49:36 2018
  ErrorMessage: poging tot overschrijven van gedeelde 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere 
exemplaren van pakket libperl5.26:i386
  InstallationDate: Installed on 2017-03-09 (301 days ago)
  InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: perl
  Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging 
tot overschrijven van gedeelde 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere 
exemplaren van pakket libperl5.26:i386
  UpgradeStatus: Upgraded to artful on 2017-10-21 (74 days ago)

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

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

[Touch-packages] [Bug 1713004] Re: Temporary files left under /var/tmp by mkinitramfs

[Dan Streetman]

> There are tons of reds in the autopkg tests for initramfs-tools on trusty, 
> were those
> considered and deemed flaky tests or something?

Those fail due to bug 1723223 which I am working on; it's a problem with
the 'ubuntu-regression-suite' linux autopkgtest and can be ignored.

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

Title:
  Temporary files left under /var/tmp by mkinitramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  Test Case
  -
  1) confirm there are no mkinitramfs junk files in /var/tmp
  2) run 'sudo update-initramfs -k all -u -v'
  3) interrupt update-initramfs with Ctrl-C
  4) observe junk files in /var/tmp e.g. /var/tmp/mkinitramfs*

  With the version of initramfs-tools in -proposed you should see not
  have any leftovers in /var/tmp.

  I recently ran out of disk space on my / mount.  While looking for
  what consumed the disk I noticed a large number (130) of directories
  with names / paths beginning /var/tmp/mkinitramfs.  These directories
  seem to be either ~103 MB or ~927 MB in size.  Many of these files are
  months old, some are almost a year.

  Having had a quick look about for an explanation as to why these files
  are here and found Debian Bug #814345.  That explains that temporary
  files are left behind by the initramfs-tools if something fails in the
  process.  If this is the cause of my files then updating the Ubuntu
  package to version 0.123 should resolve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 25 09:40:41 2017
  InstallationDate: Installed on 2015-03-12 (896 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.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/ubuntu/+source/initramfs-tools/+bug/1713004/+subscriptions

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

[Touch-packages] [Bug 1741262] [NEW] regression in dnsmasq breaks DNS resolution for precise ESM

[Leonidas S. Barbosa]

*** This bug is a security vulnerability ***

Private security bug reported:

Haw Loeung reports the follow issue in dnsmasq

ubuntu@instance-lcy01:~$ host www.googleapis.com
;; Warning: Message parser reports malformed message packet.
;; Warning: Message parser reports malformed message packet.
www.googleapis.com is an alias for googleapis.l.google.com.
ubuntu@instance-lcy01:$ grep nameserver /etc/resolv.conf
nameserver 10.55.60.1

ubuntu@instance-lcy02:~$ host www.googleapis.com
;; Warning: Message parser reports malformed message packet.
;; Warning: Message parser reports malformed message packet.
www.googleapis.com is an alias for googleapis.l.google.com.
ubuntu@instance-lcy02:~$ grep nameserver /etc/resolv.conf
nameserver 10.55.32.1

[hloeung@silver ~]$ host www.googleapis.com 10.55.32.1 | grep Warning
;; Warning: Message parser reports malformed message packet.
;; Warning: Message parser reports malformed message packet.

[hloeung@silver ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
[hloeung@silver ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
[hloeung@silver ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
[hloeung@silver ~]$ host www.googleapis.com 10.55.59.1 | grep Warning


[hloeung@dziban ~]$ host www.googleapis.com 10.55.60.1 | grep Warning
;; Warning: Message parser reports malformed message packet.
;; Warning: Message parser reports malformed message packet.

[hloeung@dziban ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
[hloeung@dziban ~]$ host www.googleapis.com 10.55.59.1 | grep Warning
[hloeung@dziban ~]$ host www.googleapis.com 10.55.59.1 | grep Warning


[hloeung@dziban ~]$ apt-cache policy dnsmasq-base
dnsmasq-base:
  Installed: 2.59-4ubuntu0.3

[hloeung@silver ~]$ apt-cache policy dnsmasq-base
dnsmasq-base:
  Installed: 2.59-4ubuntu0.3
  Candidate: 2.59-4ubuntu0.3
  Version table:
 *** 2.59-4ubuntu0.3 0
500 https://esm.ubuntu.com/ubuntu/ precise/main amd64 Packages


[hloeung@silver ~]$ dig +tcp a www.googleapis.com @10.55.32.1
;; Warning: Message parser reports malformed message packet.
...
;; WARNING: Messages has 109 extra bytes at end
...
;; MSG SIZE  rcvd: 157

[hloeung@silver ~]$ sudo strace -f -p 2418 -s 1024 2>&1 | grep googleapis 
-B3 -A3
[pid 11479] getpeername(10, {sa_family=AF_INET, sin_port=htons(33976), 
sin_addr=inet_addr("10.55.32.1")}, [16]) = 0
[pid 11479] read(10, "\0", 1)   = 1
[pid 11479] read(10, "$", 1)= 1
[pid 11479] read(10, 
"\334r\1\0\0\1\0\0\0\0\0\0\3www\ngoogleapis\3com\0\0\1\0\1", 36) = 36
[pid 11479] write(10, "\0", 1)  = 1
[pid 11479] write(10, "\235", 1)= 1
[pid 11479] write(10, 
"\334r\201\200\0\1\0\6\0\0\0\0\3www\ngoogleapis\3com\0\0\1\0\1\300\f\0\5\0\1\0\0\10\2\0\35\ngoogleapis.\1l.\6google.\3com\0\0\3000\0\1\0\1\0\0\0%\0\4\330:\301J\3000\0\1\0\1\0\0\0%\0\4\254\331\3\312\3000\0\1\0\1\0\0\0%\0\4\254\331\3\252\3000\0\1\0\1\0\0\0%\0\4\330:\330\252\3000\0\1\0\1\0\0\0%\0\4\330:\330\212",
 157) = 157
[pid 11479] read(10, "", 1) = 0
[pid 11479] shutdown(10, 2 /* send and receive */) = 0
[pid 11479] close(10)   = 0
--
[pid 11491] getpeername(10, {sa_family=AF_INET, sin_port=htons(54452), 
sin_addr=inet_addr("10.55.32.1")}, [16]) = 0
[pid 11491] read(10, "\0", 1)   = 1
[pid 11491] read(10, "$", 1)= 1
[pid 11491] read(10, 
"\352t\1\0\0\1\0\0\0\0\0\0\3www\ngoogleapis\3com\0\0\1\0\1", 36) = 36
[pid 11491] write(10, "\0", 1)  = 1
[pid 11491] write(10, "\235", 1)= 1
[pid 11491] write(10, 
"\352t\201\200\0\1\0\6\0\0\0\0\3www\ngoogleapis\3com\0\0\1\0\1\300\f\0\5\0\1\0\0\10\1\0\35\ngoogleapis.\1l.\6google.\3com\0\0\3000\0\1\0\1\0\0\0$\0\4\330:\301J\3000\0\1\0\1\0\0\0$\0\4\254\331\3\312\3000\0\1\0\1\0\0\0$\0\4\254\331\3\252\3000\0\1\0\1\0\0\0$\0\4\330:\330\252\3000\0\1\0\1\0\0\0$\0\4\330:\330\212",
 157) = 157
[pid 11491] read(10, "", 1) = 0
[pid 11491] shutdown(10, 2 /* send and receive */) = 0
[pid 11491] close(10)   = 0
^C

157 bytes (= 157 from strace)


Junien has also seen this with a tcpdump:

https://pastebin.canonical.com/204043/

For now, I've downgraded to dnsmasq-base to 2.59-4ubuntu0.2:

[hloeung@silver ~]$ apt-cache policy dnsmasq-base
dnsmasq-base:
  Installed: 2.59-4ubuntu0.2
  Candidate: 2.59-4ubuntu0.3
  Version table:
 2.59-4ubuntu0.3 0
500 https://esm.ubuntu.com/ubuntu/ precise/main amd64 Packages
 *** 2.59-4ubuntu0.2 0
500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
100 /var/lib/dpkg/status

[hloeung@dziban ~]$ apt-cache policy dnsmasq-base
dnsmasq-base:
  Installed: 2.59-4ubuntu0.2
  Candidate: 2.59-4ubuntu0.3
  Version table:
 2.59-4ubuntu0.3 0
500 https://esm.ubuntu.com/ubuntu/ precise/main amd64 Packages
 *** 2.59-4ubuntu0.2 0
500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
500 

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/335703

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

[Andreas Hasenack]

I installed the updated package on an existing maas server on
xenial/amd64, and deployed a new node (also xenial/amd64) where I also
installed the updated package plus some server software. No visible side
effects.

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Zesty:
  Fix Committed
Status in iproute2 source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  root@roselp1:~# ip maddr show
  ...
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet  224.0.0.252
  inet  224.0.0.1
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 users 3
  inet6 ff02::1
  inet6 ff01::1
  ...

  root@roselp1:~# ip maddr show dev enP20p96s0
  10: enP20p96s0
  link  33:33:00:00:00:01
  link  01:00:5e:00:00:01
  link  33:33:ff:6d:d0:d0
  link  01:00:5e:00:00:fc
  link  33:33:00:01:00:03
  inet6 ff02::1:3
  inet6 ff02::1:ff6d:d0d0 

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

Yep - testing shows that read is enough and since we have such rules for 
similar paths I think it is fine to add them.
Prepping a change to the packaging.

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 972223] Re: regression in gtk underlining rendering

[Bug Watch Updater]

** Changed in: freetype
   Status: New => Fix Released

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

Title:
  regression in gtk underlining rendering

Status in FreeType:
  Fix Released
Status in freetype package in Ubuntu:
  Fix Released

Bug description:
  The issue started with 2.4.6 and got tracked to
  
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0962ac34e66052ccfee7996e5468f30d4bd5a72

  Michael Vogt came with a testcase on
  https://bugs.launchpad.net/ubuntu/+source/software-
  center/+bug/955030/+attachment/2988350/+files/lala.py

  The commit also created http://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=636776

  I talked to Steve and I'm going to revert that commit for precise

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

And btw - we had such rules for /bin and /usr/bin already - maybe even for the 
same reasons.
Chances are that the actual change is that /usr/local/bin and /usr/local/sbin 
are now in PATH of the service.

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data

[Andreas Hasenack]

Well, network-manager depends on iproute2, as do many other things. When
I try to remove iproute2 from my system I get this:

The following packages will be REMOVED:
  gnome-control-center* ifupdown* iproute2* isc-dhcp-client* keepalived* 
network-manager* network-manager-config-connectivity-ubuntu* 
network-manager-gnome* network-manager-openvpn*
  network-manager-openvpn-gnome* network-manager-pptp* 
network-manager-pptp-gnome* openvpn* pppoeconf* ubuntu-desktop*

Of these I use extensively openvpn (via network manager) and, although
it's not listed as a dependency, lxd (in the host), which I just
confirmed uses iproute2 to set up its bridges and networking.

That being said, this is on artful, not xenial. The xenial dep8 tests in
the excuses page are all green, though.

I'll setup up a xenial vm, with a lot of networking "things" (nics,
bridges, server software), update iproute2, and let it boot.

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

Title:
  ip maddr show and ip maddr show dev enP20p96s0 show different data

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Zesty:
  Fix Committed
Status in iproute2 source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When a nic has a long enough name such that there is no space between the 
name and the ":" in /proc/net/igmp, ip maddr show dev  will miss the IPV4 
addresses which is otherwise shown with "ip maddr show".

  This is inconsistent behavior and can break scripts and tests, as
  shown in this bug's original description.

  Three patches from upstream were taken to fix this bug, and they were used 
individually instead of being merged into one single patch so it's easier to 
track and recognize authorship:
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6
  
https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9

  [Test Case]
  * deploy the ubuntu release under test. Please use bare metal or a VM instead 
of containers, because the ip tool parses a file in /proc. Make sure iproute2 
is installed:
  sudo apt install iproute2

  * Run these commands to setup a dummy interface with a long name and
  an IPv4 address. Please change the address if it conflicts with a real
  network you might have available on that machine:

  sudo ip link add dummylongnic0 type dummy
  sudo ip addr add 192.168.199.10/24 dev dummylongnic0
  sudo ip link set dev dummylongnic0 up

  * Compare the output of these two commands with regards to the dummylongnic0 
interface:
  sudo ip maddr show
  sudo ip maddr show dev dummylongnic0

  * With the buggy iproute2 package installed, the more specific output "ip 
maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line:
  ip maddr show dev dummylongnic0
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet6 ff02::1
inet6 ff01::1

  
  Whereas the less specific command, which lists all interfaces, will have it 
listed for dummylongnic0:
  2:dummylongnic0
link  33:33:00:00:00:01
link  01:00:5e:00:00:01
inet  224.0.0.1
inet6 ff02::1
inet6 ff01::1

  
  * With the fixed iproute2 package, all dummylongnic0 addresses will be 
present in both outputs.

  
  [Regression Potential]
  In the end, the ip tool is parsing a text file produced by the kernel. As 
most parsing done in C, it's pretty low level and sensitive to changes in the 
file it's reading.

  [Other Info]
  I suggest to conduct the tests in VMs instead of containers (LXD) because the 
ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you 
use a container, then it's the host's kernel that will be providing that file 
and it might not be the same as with the native kernel of that particular 
ubuntu release.

  --- Original description ---
  Attn. Canonical:  Please make sure that the existing iproute2 package gets 
updated with the two referenced patches as the missing information is impacting 
our standard test suites.

  Thanks.

  == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 ==
  ---Problem Description---
  ip maddr show and ip maddr show dev enP20p96s0 show different data

  ---uname output---
  Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8286-42A

  ---Steps to Reproduce---
   run these at command line:
  

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

@Martin - hi, thanks to chime in.
There are no hooks of that kind, but really just option parsing on (re-)start.

But still if it is happy with "r" only I might add a rule for it.

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1683576] Re: cd with multiple directory argument fails

[Norbert]

Also on "Ubuntu 17.04 — bash: cd: too many arguments"
(https://askubuntu.com/q/905832/66509).

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

Title:
  cd with multiple directory argument fails

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  In bash 4.4, a new behaviour was introduced for cd, where it would complain 
if multiple arguments are provided. From config-top.h [1]:
   
  /* Define CD_COMPLAINS if you want the non-standard, but sometimes-desired
 error messages about multiple directory arguments to `cd'. */
  #define CD_COMPLAINS

  It seems like this is enabled for Ubuntu. However, this behaviour
  conflicts with the manual (both Ubuntu's and GNU's), which says
  something similar to: "Any additional arguments following directory
  are ignored."

  Please revert to the old behaviour, or correct the manual. This is not
  a user-configurable setting, and push is also affected.

  Ubuntu 17.04
  bash 4.4-2ubuntu1

  
  [1]: http://git.savannah.gnu.org/cgit/bash.git/tree/config-top.h#n30

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

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

[Touch-packages] [Bug 1683576] Re: cd with multiple directory argument fails

[Norbert]

Seen on AskUbuntu during discussion of the problem "Command cd behavior"
(https://askubuntu.com/q/992192/66509).

** Tags added: artful bionic

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

Title:
  cd with multiple directory argument fails

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  In bash 4.4, a new behaviour was introduced for cd, where it would complain 
if multiple arguments are provided. From config-top.h [1]:
   
  /* Define CD_COMPLAINS if you want the non-standard, but sometimes-desired
 error messages about multiple directory arguments to `cd'. */
  #define CD_COMPLAINS

  It seems like this is enabled for Ubuntu. However, this behaviour
  conflicts with the manual (both Ubuntu's and GNU's), which says
  something similar to: "Any additional arguments following directory
  are ignored."

  Please revert to the old behaviour, or correct the manual. This is not
  a user-configurable setting, and push is also affected.

  Ubuntu 17.04
  bash 4.4-2ubuntu1

  
  [1]: http://git.savannah.gnu.org/cgit/bash.git/tree/config-top.h#n30

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

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

[Touch-packages] [Bug 1683576] Re: cd with multiple directory argument fails

[Launchpad Bug Tracker]

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

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

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

Title:
  cd with multiple directory argument fails

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  In bash 4.4, a new behaviour was introduced for cd, where it would complain 
if multiple arguments are provided. From config-top.h [1]:
   
  /* Define CD_COMPLAINS if you want the non-standard, but sometimes-desired
 error messages about multiple directory arguments to `cd'. */
  #define CD_COMPLAINS

  It seems like this is enabled for Ubuntu. However, this behaviour
  conflicts with the manual (both Ubuntu's and GNU's), which says
  something similar to: "Any additional arguments following directory
  are ignored."

  Please revert to the old behaviour, or correct the manual. This is not
  a user-configurable setting, and push is also affected.

  Ubuntu 17.04
  bash 4.4-2ubuntu1

  
  [1]: http://git.savannah.gnu.org/cgit/bash.git/tree/config-top.h#n30

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

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

[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Martin Pitt]

The most plausible explanation for enumerating /usr/local/bin/ is that
ntpd has some hooks.d/ mechanism which gets called after syncing the
time, and that runs a shell in between. So IMHO this should be allowed.

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Invalid
Status in ntp source package in Zesty:
  Invalid
Status in ntp source package in Artful:
  Fix Released
Status in ntp source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[Martin Pitt]

The most plausible explanation for enumerating /usr/local/bin/ is that
ntpd has some hooks.d/ mechanism which gets called after syncing the
time, and that runs a shell in between. So IMHO this should be allowed.

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1567744] Re: USB NICs get too long name for ifupdown aliases or bridge names

[Kalle Tuulos]

Just an update - this problem still exists in Ubuntu 16.04.3 LTS.

In case someone gets to this page due to this problem, there is a
workaround. Downside on this workaround is, that all network interface
names are then changed to eth0, eth1, eth2 etc, so one must change
settings on the /etc/network/interfaces -file so, that they work also
after this change.

Steps:
1) Update /etc/default/grub as follows:
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"

2) Update GRUB:
sudo update-grub

3) If necessary, modify /etc/network/interfaces, specially if you have
static IP addresses

4) Reboot the computer.

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

Title:
  USB NICs get too long name for ifupdown aliases or bridge names

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  I have a USB NIC that is connected to my denial system. I tried to
  create an alias, and after reboot, it wasn't created. When I manually
  try to bring it up I have the error.

  /e/n/i:

  auto enx000ec688b79f
  iface enx000ec688b79f inet static
  address 10.90.90.1
  netmask 255.255.255.0

  auto enx000ec688b79f:1
  iface enx000ec688b79f:1 inet static
  address 192.168.100.1
  netmask 255.255.255.0

  ubuntu@maas00:~$ sudo ifup enx000ec688b79f
  ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1
  RTNETLINK answers: Numerical result out of range
  Failed to bring up enx000ec688b79f:1.

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

So what happens is this:
1. ntp verifies its options
2. the binary name is always included, so we get a verify in libopts like
   validate_struct (opts=opts@entry=0x55a84db841e0 , 
pname=0x7fff724dd836 "/usr/sbin/ntpd")
3. if opts->pzProgName is not set validate_struct will check for the binary 
through paths
4. it calls pathfind which looks through all of PATH
5. there is uses opendir and wants to enumerate things (to find the prog)

If path does not include forbidden dir's the error is non existing.

So the denie is really low severity - although it partially is stupid
programming as it is not really needed.

I wonder if we should add an allow or even a deny rule to just silence
it?

Since this only happens in later ntp versions an upstream change might
have dropped opts->pzProgName somehow to now trigger.


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

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

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Confirmed

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1741150] Re: 'ubuntu-bug cups'

[dino99]

You might need to install the driver:

sudo apt-get install printer-driver-escpr

'This package contains the CUPS filter driver and the compressed PPDs for the
supported printers.'

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

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

Title:
  'ubuntu-bug cups'

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  i can't print a single file.

  i think my printer is not detected.

  printer is always idle.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:
   E [04/Jan/2018:08:39:32 +0800] [cups-deviced] PID 6431 (gutenprint52+usb) 
stopped with status 1!
   E [04/Jan/2018:08:40:41 +0800] [cups-deviced] PID 6583 (gutenprint52+usb) 
stopped with status 1!
   W [04/Jan/2018:08:41:34 +0800] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'EPSON-ME-10-Series-Gray..\' already exists
   E [04/Jan/2018:08:45:32 +0800] [cups-deviced] PID 7126 (gutenprint52+usb) 
stopped with status 1!
   E [04/Jan/2018:08:51:42 +0800] [cups-deviced] PID 7239 (gutenprint52+usb) 
stopped with status 1!
  CurrentDesktop: Unity
  Date: Thu Jan  4 08:59:36 2018
  InstallationDate: Installed on 2018-01-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat: device for EPSON-ME-10-Series: 
usb://EPSON/ME-10%20Series?serial=51344C4B3031333571
  MachineType: Hewlett-Packard 500-232d
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/EPSON-ME-10-Series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/EPSON-ME-10-Series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed 
root=UUID=0ba09fb1-b9fa-45aa-a08e-c801161d6dcd ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2014
  dmi.bios.vendor: AMI
  dmi.bios.version: 80.12
  dmi.board.name: 2AF7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: 4CE4110B0Q
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr80.12:bd01/15/2014:svnHewlett-Packard:pn500-232d:pvr1.00:rvnHewlett-Packard:rn2AF7:rvr1.03:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: 500-232d
  dmi.product.version: 1.00
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

libopts is of autogen
See
autogen-5.18.12/autoopts/autoopts.c

Note for gdb on affected systems:
(gdb) catch syscall open
(gdb) run -p /var/run/ntpd.pid -g -c /run/ntp.conf.dhcp -u 112:116

dbg on libopts is odd
get from https://launchpad.net/ubuntu/bionic/amd64/libopts25-dbgsym/1:5.18.12-3


Now Details are better:
#0  0x7fd4f489fd53 in __opendir (name=name@entry=0x7fff724da8d0 
"/usr/local/sbin") at ../sysdeps/posix/opendir.c:191
#1  0x7fd4f5569ba7 in option_pathfind (path=0x7fff724ddf82 
"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin", 
fname=fname@entry=0x7fff724dd836 "/usr/sbin/ntpd", mode=) at ../compat/pathfind.c:61
#2  0x7fd4f5570de6 in validate_struct (opts=opts@entry=0x55a84db841e0 
, pname=0x7fff724dd836 "/usr/sbin/ntpd") at init.c:108
#3  0x7fd4f5572a4f in optionProcess (opts=0x55a84db841e0 , 
a_ct=8, a_v=0x7fff724dbff8) at autoopts.c:335
#4  0x55a84d8e8e7f in parse_cmdline_opts (pargc=0x7fff724dba1c, 
pargv=0x7fff724dba10) at ntpd.c:359
#5  0x55a84d8e8f8d in ntpdmain (argc=, argv=) 
at ntpd.c:575
#6  0x7fd4f47ed1c1 in __libc_start_main (main=0x55a84d8d90e0 , 
argc=8, argv=0x7fff724dbff8, init=, 
fini=, rtld_fini=, stack_end=0x7fff724dbfe8) 
at ../csu/libc-start.c:308

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  New

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[ChristianEhrhardt]

FYI - The curiosity of the /usr/local denials will be checked in bug
1741227

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Invalid
Status in ntp source package in Zesty:
  Invalid
Status in ntp source package in Artful:
  Fix Released
Status in ntp source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

I found a setup that triggers it again (often but not always happening).

Once reproducible I took backtraces of the sys open to see what in ntp
does that.

Both opens are from the same place.
Thread 1 "ntpd" hit Catchpoint 1 (returned from syscall open), 
0x7f8afd8fcd53 in __opendir (name=0x7ffcdf90 "/usr/local/sbin")
at ../sysdeps/posix/opendir.c:191
191 in ../sysdeps/posix/opendir.c
(gdb) bt
#0  0x7f8afd8fcd53 in __opendir (name=0x7ffcdf90 "/usr/local/sbin") at 
../sysdeps/posix/opendir.c:191
#1  0x7f8afe5c6ba7 in ?? () from /usr/lib/x86_64-linux-gnu/libopts.so.25
#2  0x7f8afe5cdde6 in ?? () from /usr/lib/x86_64-linux-gnu/libopts.so.25
#3  0x7f8afe5cfa4f in optionProcess () from 
/usr/lib/x86_64-linux-gnu/libopts.so.25
#4  0x55c12781ae7f in parse_cmdline_opts (pargc=0x7ffcf0dc, 
pargv=0x7ffcf0d0) at ntpd.c:359
#5  0x55c12781af8d in ntpdmain (argc=, argv=) 
at ntpd.c:575
#6  0x7f8afd84a1c1 in __libc_start_main (main=0x55c12780b0e0 , 
argc=8, argv=0x7ffcf6b8, init=, 
fini=, rtld_fini=, stack_end=0x7ffcf6a8) 
at ../csu/libc-start.c:308
#7  0x55c12780b11a in _start ()

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  New

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1741227] [NEW] apparmor denial to several paths to binaries

[ChristianEhrhardt]

Public bug reported:

Issue shows up (non fatal) as:
 apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
 apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

Since non crit this is mostyl about many of us being curious why it
actually does do it :-)

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

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  New

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Anthony Somerset]

I can confirm this bug is still present in 16.04.3

single line import fine, multiple not

-- 
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 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Merlijn Sebrechts]

Awesome! Thanks Dimitri!

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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

[Touch-packages] [Bug 1741045] Re: Change the default resample-method to speex-float-10 in daemon.conf

[Bug Watch Updater]

** Changed in: pulseaudio
   Status: Unknown => Confirmed

** Changed in: pulseaudio
   Importance: Unknown => Wishlist

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

Title:
  Change the default resample-method to speex-float-10 in daemon.conf

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

Bug description:
  I suggest changing the default resample-method to speex-float-10,
  instead of speex-float-1, which is the current default now, in
  /etc/pulse/daemon.conf.

  It would look like this in daemon.conf:
  resample-method = speex-float-10

  I have always done that since at least 12.04 LTS. I was not satisfied
  with the sound quality in Ubuntu compared to Windows, so I changed the
  resample-method.

  In my day-to-day usage, it gives better sound quality without
  sacrificing CPU power.

  I have not tried other resample methods. Maybe there are better
  options I don't know about.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr1696 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 14:37:25 2018
  InstallationDate: Installed on 2017-10-02 (92 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018

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

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

[Touch-packages] [Bug 1741045] Re: Change the default resample-method to speex-float-10 in daemon.conf

[Amr Ibrahim]

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

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

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

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

Title:
  Change the default resample-method to speex-float-10 in daemon.conf

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I suggest changing the default resample-method to speex-float-10,
  instead of speex-float-1, which is the current default now, in
  /etc/pulse/daemon.conf.

  It would look like this in daemon.conf:
  resample-method = speex-float-10

  I have always done that since at least 12.04 LTS. I was not satisfied
  with the sound quality in Ubuntu compared to Windows, so I changed the
  resample-method.

  In my day-to-day usage, it gives better sound quality without
  sacrificing CPU power.

  I have not tried other resample methods. Maybe there are better
  options I don't know about.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr1696 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 14:37:25 2018
  InstallationDate: Installed on 2017-10-02 (92 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018

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

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

[Touch-packages] [Bug 1741189] Re: New bugfix release 17.2.8

[Timo Aaltonen]

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  New bugfix release 17.2.8

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.4:

  Mesa 17.2.5 is now available.

  In this release we have:

  In Mesa Core a GL error related to the ARB_ES3_1_compatibility spec
  noticed with the GFXBench 5 Aztec Ruins has been corrected. 

  The GLSL compiler is not giving a linker error for mismatching uniform
  precision with GLSL ES 1.00 any more. This enables, specially, several
  Android applications which violate this rule, like Forge of Empires,
  for example.

  The SPIR-V compiler has corrected an assert triggered when support for
  the simple memory model was claimed.

  NIR has also received a correction related with
  gl_SubGroupG{e,t}MaskARB.

  The Intel drivers, specially i965, have received several fixes,
  including a plug for a memory leak and another one in the compiler to
  avoid GPU hangs on Broxton.

  The gallium i915g driver for Intel has also seen an important
  correction.

  AMD drivers, mostly radv, have also received several fixes, including a
  correction for a DCC corruption that was visible with Rust, breaking an
  endless loop in r600, avoiding a GPU hang with vulkan dota2 in VR mode
  and a plug for a memory leak.

  Broadcom's vc4 has gotten a fix to compile out some non-debug code that
  shouldn't be there for the release build.

  

  Mesa 17.2.6 is now available.

  In this release we have:

  In Mesa Core we have included a correction to keep a program alive when
  re-linking and prevent an use-after-free.

  The GLSL compiler has received several fixes, including one to prevent
  a SIGSEV when calling an undeclared subroutine in certain conditions
  and another to mark the xfb buffers as active only if a variable uses
  them.

  The SPIR-V compiler has corrected a couple of issues involving the
  usage of separate images and texture/samplers.

  The Intel drivers include many new fixes, specially for i965. Several 
  are focused on improving SIMD32 and little-core. It also includes a fix
  for a GPU hang which was detected while playing HW accelerated video
  with mpv.

  The AMD drivers have also received some care. radv has seen plugged 2
  memory leaks while r600 has gotten a fix through reversing the tess
  factor components for isolines.

  The swr driver has corrected two performance regressions, one for the
  avx512 platforms and the other for the avx/avx2 platforms.

  In the ddebug gallium driver we have a fix for an use-after-free.

  On the EGL side, the Wayland platform of the the DRI2 drivers has
  received a fix to prevent crashing in ancient systems.

  GLX has also received corrections to prevent a couple of errors when
  creating and binding a context in DRI3 and DRISW, respectively.

  From build and integration point of view, we have added some few more
  fixes, including one to allow building libglvnd when EGL is present but
  not GLX, another to enable building targets which don't need X11, such
  as omx and va, when XCB is not present, and another one to be able to
  specify the prefix installation for the OpenCL icd file.

  

  Mesa 17.2.7 is now available.

  In this release we have:

  The current queue consists of a variety of fixes, with a sizeable hunk in the
  shared GLSL codebase.

  Whereas for individual drivers - i965 has a crash fix for when playing various
  Valve games, r600 and nouveau have tweaks in their compiler backends. Fast
  clears on radeonsi and RADV are better now, while the VAAPI encoding is 
playing
  nicely with GStreamer.

  The WGL state tracker and SWR driver have also seen minor
  improvements.

  To top of up - Mesa should build fine with the latest glibc 2.17.

  

  Mesa 17.2.8 is now available.

  In this release we have:

  The SPIR-V compiler has seen corrected a possible SEGFAULT.

  The Intel i965 driver includes a correction for Haswell involving
  doubles management. 

  The AMD drivers have also received some fixes. A couple have gone for
  radv and radeon's VCE while r600 has seen corrected some glitches
  detected with This War of Mine.

  Gallium has also received a patch fixing a problem affecting the VMware
  driver and the st/nine state tracker.

  The endianness detection in Windows platform has been corrected to
  default to little endian.

  Finally, the X11 driver has been improved to notify properly a mesa
  warning rather than using fprintf.

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  

[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Khurshid Alam]

What??!!! Persistent logging does lot more that just logging. Do you
people even use sata hard disk? There are multiple reports (check
archlinux forums) that it is bad for sata. That is why it is set to auto
by default. The word "auto" exactly created for that purposewhen
there is both benefit ane cost with certain action. We don't want our
hard disk to die quickly becquse of we want to see some logs that we
don't understand any way,

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

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" 
report memory usage as disk 
usage](https://github.com/systemd/systemd/issues/4059), giving the impression 
that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the 
logs were thrown 
away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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

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