date:20190909

Upstream bug with fix: https://github.com/systemd/systemd/issues/13116

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

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

** Tags added: fixed-upstream

** Tags added: eoan

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in systemd:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1836266] Re: package python 2.7.11-1 failed to install/upgrade: pre-dependency problem - not installing python

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

** Changed in: python-defaults (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package python 2.7.11-1 failed to install/upgrade: pre-dependency
  problem - not installing python

Status in python-defaults package in Ubuntu:
  Expired

Bug description:
  I tried to upgrade ubuntu and cath whis bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python 2.7.11-1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Jul 12 01:04:31 2019
  ErrorMessage: pre-dependency problem - not installing python
  InstallationDate: Installed on 2017-08-27 (683 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.32
  SourcePackage: python-defaults
  Title: package python 2.7.11-1 failed to install/upgrade: pre-dependency 
problem - not installing python
  UpgradeStatus: Upgraded to xenial on 2019-07-11 (0 days ago)

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

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

[Touch-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

** Project changed: libinput => systemd

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in systemd:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

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

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in libinput:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-09 Thread Jamie Strandboge

@Rex and @Shih-Yuan, I believe Chris is planning to push this through
-security in his morning.

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

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

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

[Touch-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

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

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

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in libinput:
  Unknown
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1843295] Re: Desktop icons missing when join displays

Reassigning to Nautilus since that provides the desktop and icons.

** Package changed: xorg (Ubuntu) => nautilus (Ubuntu)

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

Title:
  Desktop icons missing when join displays

Status in nautilus package in Ubuntu:
  New

Bug description:
  In general there isn't any problems. But when I connect my computer to a 
second monitor. Use display mode "Join Displays". Then disappears all my 
desktop icons . 
  If I switch theDisplay mode to "Mirror" or "Single Display" then will all the 
icons come back.

  I have tryied to change ressolution, background, log out and then in
  again, restart, waited in a periode two weeks, updated etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 19:43:41 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 5.0.0-25-generic, x86_64: installed
   nvidia, 390.116, 5.0.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:505e]
 Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
  InstallationDate: Installed on 2019-08-09 (31 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20J60018MD
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0FET46W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J60018MD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET46W(1.26):bd10/16/2018:svnLENOVO:pn20J60018MD:pvrThinkPadT470p:rvnLENOVO:rn20J60018MD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470p
  dmi.product.name: 20J60018MD
  dmi.product.sku: LENOVO_MT_20J6_BU_Think_FM_ThinkPad T470p
  dmi.product.version: ThinkPad T470p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

** Package changed: wayland (Ubuntu) => unity (Ubuntu)

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

Title:
  Unity in Wayland prompts for keyboard focus on each run of ssh-
  askpass-gnome

Status in gnome-desktop package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  New

Bug description:
  When using a Wayland-based Unity session on Ubuntu 19.04:

  1. Have ssh-askpass-gnome as your askpass program.
  2. ssh-add -c 
  3. `ssh` to a host

  Each time, before the ssh-askpass prompt is shown, Unity shows this
  dialog:

  +-+
  | |
  | ssh-askpass wants to inhibit shortcuts  |
  | |
  | You can restore Shortcuts by pressing   |
  | Super+Escape.   |
  | |
  |_|
  |   Deny | Allow  |
  +-+

  This is mildly distracting, and it means that you need to hit ,
  answer, , instead of just answer .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ssh-askpass-gnome 1:7.9p1-10
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 15:04:25 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

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

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

[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-09 Thread Shih-Yuan Lee

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

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

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

[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-09 Thread Rex Tsai

Is there anything we can do to speed up the process? What would be the
next step to land the reverted version for the regression?

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

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

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

[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-09 Thread Shih-Yuan Lee

** Changed in: systemd (Ubuntu)
 Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)

** Changed in: oem-priority
 Assignee: Shih-Yuan Lee (fourdollars) => (unassigned)

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

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

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

[Touch-packages] [Bug 1720820] Re: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes.

Sounds like we have a semi-permanent workaround now:

gstreamer-vaapi (1.16.0-3ubuntu2) eoan; urgency=medium

  * debian/patches/git_no_amd.patch:
- backport an upstream change to disable vaapi with the amd drivers,
  the current experience is buggy and it's better to just not enable it
  see the discussions on this mailing list and the referenced bug
  https://mail.gnome.org/archives/distributor-list/2019-September

 -- Sebastien Bacher   Mon, 09 Sep 2019 17:09:08
+0200

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black
  screen, then crashes.

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUNDS

  Just for totem:  sudo apt remove gstreamer1.0-vaapi

  Or to workaround in all players:  sudo apt remove mesa-va-drivers

  
  ORIGINAL DESCRIPTION

  Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with
  AMD Fury graphics card and open source drivers. Video output is just a
  black frame and crash happens within just a few seconds after video
  playback starts.

  Could not reproduce bug on two older Intel laptops with iGPU's where
  hardware acceleration seemed to work fine under Wayland.

  Issue is only present on Wayland, not x.

  I can get hardware accelerated video playback working on Wayland with
  'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only
  way I have found so far. Even in mpv, no other option than vaapi-copy
  works.

  gst-play-1.0 outputs the following error:
  ERROR Internal error: could not render surface for file:///***
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  totem   3.25.90.1-0ubuntu3
  gstreamer1.0-vaapi:amd641.12.3-1ubuntu1

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

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

[Touch-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

Sounds like we have a semi-permanent workaround now:

gstreamer-vaapi (1.16.0-3ubuntu2) eoan; urgency=medium

  * debian/patches/git_no_amd.patch:
- backport an upstream change to disable vaapi with the amd drivers,
  the current experience is buggy and it's better to just not enable it
  see the discussions on this mailing list and the referenced bug
  https://mail.gnome.org/archives/distributor-list/2019-September

 -- Sebastien Bacher   Mon, 09 Sep 2019 17:09:08
+0200

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264
  videos

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

  WORKAROUND:
  sudo apt remove gstreamer1.0-vaapi
  or
  sudo apt remove mesa-va-drivers

  See also bug 1720820.

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

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

[Touch-packages] [Bug 1739628] Re: sysconfig paths are incorrect

2019-09-09 Thread Steven Clarkson

I've been using this as a workaround.

from distutils.sysconfig
print(distutils.sysconfig.get_python_inc())

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

Title:
  sysconfig paths are incorrect

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 17.10:

  $ ls /usr/include/python2.7
  abstract.h code.h   funcobject.h   marshal.h   
pgenheaders.h   pymem.h 
  
  $ ls /usr/local/include/python2.7
  ls: cannot access '/usr/local/include/python2.7': No such file or directory
  $ python -c "import sysconfig; print(sysconfig.get_path('include'))"
  /usr/local/include/python2.7

  Definitely wrong.

  Python is such a massive pain to integrate with - I actually switched
  from CMake's FindPythonLibs() which is heuristic-based and very
  unreliable to sysconfig - "surely python itself knows where it is
  installed?" I thought. Ha. Of course not. /rant

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

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

[Touch-packages] [Bug 1739628] Re: sysconfig paths are incorrect

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

** Changed in: python2.7 (Ubuntu)
   Status: New => Confirmed

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

Title:
  sysconfig paths are incorrect

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 17.10:

  $ ls /usr/include/python2.7
  abstract.h code.h   funcobject.h   marshal.h   
pgenheaders.h   pymem.h 
  
  $ ls /usr/local/include/python2.7
  ls: cannot access '/usr/local/include/python2.7': No such file or directory
  $ python -c "import sysconfig; print(sysconfig.get_path('include'))"
  /usr/local/include/python2.7

  Definitely wrong.

  Python is such a massive pain to integrate with - I actually switched
  from CMake's FindPythonLibs() which is heuristic-based and very
  unreliable to sysconfig - "surely python itself knows where it is
  installed?" I thought. Ha. Of course not. /rant

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

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

[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client

2019-09-09 Thread Steve Kieu

I just want to note here is that it seems not working still for me in
ubuntu 18.04 running on aws ec2 ami.

root@adc1:~# dpkg -l|grep netplan
ii  netplan.io  0.97-0ubuntu1~18.04.1 amd64 
   YAML network configuration abstraction for various backends
root@adc1:~# 

Followed the guide https://aws.amazon.com/premiumsupport/knowledge-
center/ec2-static-dns-ubuntu-debian/ and the version 0.97 should work
but it does not work

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

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

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

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

[Touch-packages] [Bug 1825167] Re: It does not correctly display the hard drive icon

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

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

Title:
  It does not correctly display the hard drive icon

Status in Nautilus:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/991

  ---

  The icon of my hard drive is SSD (Attach image).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  Uname: Linux 5.0.8-050008-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Apr 17 08:52:05 2019
  InstallationDate: Installed on 2018-12-02 (135 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=es_CL:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
  usr_lib_nautilus:

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

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

[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

** Changed in: gnome-terminal
   Status: Unknown => Fix Released

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in GNOME Terminal:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

2019-09-09 Thread Luke Faraone

Thanks for looking into this, and the pointer.

I guess, another option would be to not request shortcut inhibition,
unless I'm misunderstanding its value? Unless there's a worry that some
other application will be able to steal your password this way — it
doesn't seem obviously warranted to me.

For example, `ssh-askpass-fullscreen` does not generate this prompt. It
isn't clear to me that the fullscreen-ness of this implementation
materially changes the risk profile, so either shortcut inhibition isn't
useful, or I should file a bug against `ssh-askpass-fullscreen` to
either request this privilege or document the gap.

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

Title:
  Unity in Wayland prompts for keyboard focus on each run of ssh-
  askpass-gnome

Status in gnome-desktop package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  New

Bug description:
  When using a Wayland-based Unity session on Ubuntu 19.04:

  1. Have ssh-askpass-gnome as your askpass program.
  2. ssh-add -c 
  3. `ssh` to a host

  Each time, before the ssh-askpass prompt is shown, Unity shows this
  dialog:

  +-+
  | |
  | ssh-askpass wants to inhibit shortcuts  |
  | |
  | You can restore Shortcuts by pressing   |
  | Super+Escape.   |
  | |
  |_|
  |   Deny | Allow  |
  +-+

  This is mildly distracting, and it means that you need to hit ,
  answer, , instead of just answer .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ssh-askpass-gnome 1:7.9p1-10
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 15:04:25 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

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

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

[Touch-packages] [Bug 1843352] [NEW] systemd package version 237-3ubuntu10.28 breaks local network DNS resolution

2019-09-09 Thread Denis Rut'kov

Public bug reported:

After upgrading to the latest package the systemd-resolved service fails
to resolve names for local network.Manually invoking nslookup works
fine.

The only suspicious output from journalctl seems:
systemd-resolved[858]: Server returned error NXDOMAIN, mitigating potential DNS 
violation DVE-2018-0001, retrying transaction with reduced feature level UDP.

The latest change in that package is:
 * SECURITY UPDATE: Unprivileged users are granted access to privileged
systemd-resolved D-Bus methods
- d/p/0001-shared-but-util-drop-trusted-annotation-from-bus_ope.patch:
  drop trusted annotation from bus_open_system_watch_bind()
- CVE-2019-15718

 -- Chris Coulson   Thu, 29 Aug 2019
23:30:33 +0100

Please revert this.

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

** Attachment added: "This is output of dig command for a locally available 
resource (the name has been replaced)"
   https://bugs.launchpad.net/bugs/1843352/+attachment/5287638/+files/dig.txt

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

Title:
  systemd package version 237-3ubuntu10.28 breaks local network DNS
  resolution

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading to the latest package the systemd-resolved service
  fails to resolve names for local network.Manually invoking nslookup
  works fine.

  The only suspicious output from journalctl seems:
  systemd-resolved[858]: Server returned error NXDOMAIN, mitigating potential 
DNS violation DVE-2018-0001, retrying transaction with reduced feature level 
UDP.

  The latest change in that package is:
   * SECURITY UPDATE: Unprivileged users are granted access to privileged
  systemd-resolved D-Bus methods
  - d/p/0001-shared-but-util-drop-trusted-annotation-from-bus_ope.patch:
drop trusted annotation from bus_open_system_watch_bind()
  - CVE-2019-15718

   -- Chris Coulson   Thu, 29 Aug 2019
  23:30:33 +0100

  Please revert this.

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

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

[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-09 Thread Jamie Strandboge

> Please reject the packages that are currently in the unapproved queue.

Done

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

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

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

[Touch-packages] [Bug 1843333] [NEW] lvdisplay man page says to use -o help but that does not work.

2019-09-09 Thread Jay R. Wren

Public bug reported:

The lvdisplay man page suggesting something which does not work.

The manpage says:

Use -o help to view the list of all
  available fields.

Doing this gives an error:

$ sudo lvdisplay -o help /dev/datavg/lv1
  Incompatible options selected.
  Run `lvdisplay --help' for more information.


Expected:
A correct manpage.

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

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

Title:
  lvdisplay man page says to use -o help but that does not work.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  The lvdisplay man page suggesting something which does not work.

  The manpage says:

  Use -o help to view the list of all
available fields.

  Doing this gives an error:

  $ sudo lvdisplay -o help /dev/datavg/lv1
Incompatible options selected.
Run `lvdisplay --help' for more information.

  
  Expected:
  A correct manpage.

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

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

[Touch-packages] [Bug 1837734] Re: libnss3 reads fips_enabled flag and automatically switches to FIPS mode

2019-09-09 Thread Vineetha Kamath

The SRU was originally filed since firefox crashed due to libnss3
automatically entering FIPS mode. Firefox uses bundled nss and hence a
fix is being worked into firefox library to address the crash.

libnss3 does not need this change. Upon careful examination of code, the
code to read "fips_enabled" does not get compiled on Ubuntu.

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

Title:
  libnss3 reads fips_enabled flag and automatically switches to FIPS
  mode

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Xenial:
  Fix Committed
Status in nss source package in Bionic:
  Fix Committed
Status in nss source package in Disco:
  Fix Committed
Status in nss source package in Eoan:
  Fix Released

Bug description:
  [IMPACT]
  nss is not a FIPS certified library. On a machine running FIPS enabled 
kernel, the library by default goes into FIPS mode if 
/proc/sys/crypto/fips_enabled=1. This is an untested configuration and since 
libnss3 is not a certified library we propose disabling reading the 
'fips_enabled' flag and therefore switching the library automatically into FIPS 
mode. 

  The proposed patch disables reading the /proc/sys/crypto/fips_enabled
  flag. The users of the library however can force nss into FIPS mode
  via an environment variable. We plan to leave it as is so as not to
  regress existing users who may be using it.

  The issue impacts libnss3 versions in eoan, disco, bionic and xenial.

  lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release: 19.10

  Version: 2:3.45-1ubuntu1

  lsb_release -rd
  Description: Ubuntu Disco Dingo
  Release: 19.04

  Version: 2:3.42-1ubuntu2

  lsb_release -rd
  Description:  Ubuntu Bionic Beaver
  Release:  18.04

  Version: 2:3.35-2ubuntu2.3

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Version: 2:3.28.4-0ubuntu0.16.04

  [FIX]
  This fix proposes to disable libnss3 reading proc/sys/crypto/fips_enabled. We 
only want fips certified modules reading this file and running in fips mode. 
libnss3 is not one of our fips certified modules, so should not be reading this 
along with our fips certified modules to determine whether to run in fips mode.

  Users who do want to run the library in FIPS mode can do so by using
  the environment variable "NSS_FIPS". We propose to leave it as is so
  as not to regress anyone using this. The user who is using this option
  should be doing so with the awareness.

  [TEST]
  Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in 
FIPS mode. With the patch fix no crashes were observed when launching firefox 
browser.
  Without the patch fix, firefox crashes.

  Tested on a xenial and bionic desktop ISO running non-FIPS generic
  kernel. With the patch fix, firefox worked as expected and no changes
  were observed.

  [REGRESSION POTENTIAL]
  The regression potential for this is small. A FIPS kernel is required to
  create /proc/sys/crypto/fips_enabled and it is not available in standard 
ubuntu archive. For users forcing FIPS through environment variable, nothing 
has changed.

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

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

[Touch-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

2019-09-09 Thread Sherif

I installed Fedora 30 (64-bit) and I've the same issue.

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

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

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-09 Thread Chris Coulson

I've uploaded the changes that were sponsored to proposed to
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa.
Please reject the packages that are currently in the unapproved queue.

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

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

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

[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-09 Thread Jamie Strandboge

FYI, this broke me as well. I have an 18.04 multi-nic system that went
through several upgrades and was relying on /etc/udev/rules.d/70
-persistent-net.rules to give me predictable eth* names where each eth*
name was used as part of a bridge. The recent change regressed this
since non-existent eth* entries were specified for the bridge which
caused the bridges to never come up.

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

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

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

[Touch-packages] [Bug 1843295] [NEW] Desktop icons missing when join displays

2019-09-09 Thread Jonas Storm Nikolajsen

Public bug reported:

In general there isn't any problems. But when I connect my computer to a second 
monitor. Use display mode "Join Displays". Then disappears all my desktop icons 
. 
If I switch theDisplay mode to "Mirror" or "Single Display" then will all the 
icons come back.

I have tryied to change ressolution, background, log out and then in
again, restart, waited in a periode two weeks, updated etc.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep  9 19:43:41 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.116, 5.0.0-25-generic, x86_64: installed
 nvidia, 390.116, 5.0.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:505e]
   Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505e]
InstallationDate: Installed on 2019-08-09 (31 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 20J60018MD
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: R0FET46W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20J60018MD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0FET46W(1.26):bd10/16/2018:svnLENOVO:pn20J60018MD:pvrThinkPadT470p:rvnLENOVO:rn20J60018MD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470p
dmi.product.name: 20J60018MD
dmi.product.sku: LENOVO_MT_20J6_BU_Think_FM_ThinkPad T470p
dmi.product.version: ThinkPad T470p
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

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

Title:
  Desktop icons missing when join displays

Status in xorg package in Ubuntu:
  New

Bug description:
  In general there isn't any problems. But when I connect my computer to a 
second monitor. Use display mode "Join Displays". Then disappears all my 
desktop icons . 
  If I switch theDisplay mode to "Mirror" or "Single Display" then will all the 
icons come back.

  I have tryied to change ressolution, background, log out and then in
  again, restart, waited in a periode two weeks, updated etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  9 19:43:41 2019
  DistUpgraded:

[Touch-packages] [Bug 1841269] Re: dvbv5-scan Segmentation fault

This bug was fixed in the package v4l-utils - 1.16.7-1

---
v4l-utils (1.16.7-1) unstable; urgency=medium

  * Import latest 1.16.7 upstream release. LP: #1841269

 -- Gregor Jasny   Sun, 01 Sep 2019 14:59:49
+0200

** Changed in: v4l-utils (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  dvbv5-scan Segmentation fault

Status in v4l-utils package in Ubuntu:
  Fix Released

Bug description:
  LANG=en_US.UTF-8 gdb -ex=r --args dvbv5-scan -l UNIVERSAL -S0 -v -o 
Turksat.conf ./Turksat-42.0E 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Using LNBf UNIVERSAL
Universal, Europe
Freqs : 10800 to 11800 MHz, LO: 9750 MHz
Freqs : 11600 to 12700 MHz, LO: 10600 MHz
  using demux 'dvb0.demux0'
  Device Montage Technology DS3000/TS2020 (/dev/dvb/adapter0/frontend0) 
capabilities:
   CAN_2G_MODULATION
   CAN_FEC_1_2
   CAN_FEC_2_3
   CAN_FEC_3_4
   CAN_FEC_4_5
   CAN_FEC_5_6
   CAN_FEC_6_7
   CAN_FEC_7_8
   CAN_FEC_AUTO
   CAN_INVERSION_AUTO
   CAN_QPSK
   CAN_RECOVER
  DVB API Version 5.11, Current v5 delivery system: DVBS
  Supported delivery systems: 
  [DVBS]
   DVBS2
  Failed to guess country from the current locale setting.

  ERRORcommand BANDWIDTH_HZ (5) not found during retrieve
  Cannot calc frequency shift. Either bandwidth/symbol-rate is unavailable 
(yet).
  Scanning frequency #1 12346000
  frequency: 12346,00 MHz, high_band: 1
  SEC: set voltage to 18V
  DiSEqC TONE: OFF
  DiSEqC command: e0 10 38 f3 
  DiSEqC BURST: SEC_MINI_A
  DiSEqC TONE: ON
  L-Band frequency: 1746,00 MHz (offset = 10600,00 MHz)
  FREQUENCY = 12346000
  INVERSION = AUTO
  SYMBOL_RATE = 960
  INNER_FEC = 3/4
  POLARIZATION = HORIZONTAL
  DELIVERY_SYSTEM = DVBS
  Got parameters for DVBS:
  FREQUENCY = 12346000
  INVERSION = AUTO
  SYMBOL_RATE = 960
  INNER_FEC = 3/4
  POLARIZATION = HORIZONTAL
  DELIVERY_SYSTEM = DVBS
  Lock   (0x1f) Signal= 37,86% C/N= 47,97% UCB= 31440 postBER= 0
  dvb_read_sections: waiting for table ID 0x00, program ID 0x00
  dvb_parse_section: received table 0x00, extension ID 0xa414, section 0/0
  dvb_parse_section: table 0x00, extension ID 0xa414: done
  PAT
  | table_id 0x00
  | section_length  25
  | one 3
  | zero0
  | syntax  1
  | transport_stream_id 42004
  | current_next1
  | version 14
  | one23
  | section_number  0
  | last_section_number 0
  |\ 4 program pids
  |  pid 0x0010: service 0x
  |  pid 0x0065: service 0x3264
  |  pid 0x012d: service 0x3265
  |  pid 0x0066: service 0x3269
  Program #0 is network PID: 0x0010
  Program #1 ID 0x0065, service ID 0x3264
  dvb_read_sections: waiting for table ID 0x02, program ID 0x65
  dvb_parse_section: received table 0x02, extension ID 0x3264, section 0/0
  dvb_parse_section: table 0x02, extension ID 0x3264: done
  PMT
  | table_id 0x02
  | section_length  112
  | one 3
  | zero0
  | syntax  1
  | transport_stream_id 12900
  | current_next1
  | version 7
  | one23
  | section_number  0
  | last_section_number 0
  |- pcr_pid  0b54
  |  reserved2   7
  |  descriptor length   11
  |  zero3   0
  |  reserved3  15
  |0x0c: multiplex_buffer_utilization_descriptor
  |   80 b4 81 68...h
  |0x0e: maximum_bitrate_descriptor
  |   c0 3e a4   .>.
  |\
  |- stream 0x0b54: Video ISO/IEC 13818-2 (2)
  |descriptor length   16
  |0x52: stream_identifier_descriptor
  |   01 .
  |0x02: video_stream_descriptor
  |   1a 48 5f   .H_
  |0x06: ds_alignment_descriptor
  |   02 .
  |0x0e: maximum_bitrate_descriptor
  |   c0 39 4e   .9N
  |- stream 0x0bb8: Audio ISO/IEC 13818-3 (4)
  |descriptor length   17
  |0x52: stream_identifier_descriptor
  |   02 .
  |0x0a: iso639_language_descriptor
  |   lang: tur (type: 0)
  |0x03: audio_stream_descriptor
  |   67 g
  |0x0e: maximum_bitrate_descriptor
  |   c0 02 90   ...
  |- stream 0x0c1c: Audio ISO/IEC 13818-3 (4)
  |descriptor length   17
  |0x52:

[Touch-packages] [Bug 1843099] Re: Unattended upgrades does not work on shutdown

2019-09-09 Thread Zahid Bukhari

I'd submit a patch but I don't know which way we want to go with this
and ya'll are official devs.  Update code to handle returned FD or just
check to see if it's not -1 or update to use apt_pkg.FileLock?  Not
Sure, either way - enjoy!

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

Title:
  Unattended upgrades does not work on shutdown

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
   * Ubuntu Xenial 16.04.6 LTS
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
   * 1.1ubuntu1.18.04.7~16.04.3
  3) What you expected to happen
   * Packages to be upgraded on reboot / shutdown.
  4) What happened instead
   * The host just rebooted.  Didn't perform upgrades.  No useful output either 
until I enabled debug logging in the systemd unit file.

  I'm reporting a new bug but this is very similar to #1806487 and I'm
  actually wondering if it resurfaced somehow.

  We're running Ubuntu Xenial 16.04.6 which has
  1.1ubuntu1.18.04.7~16.04.3 installed.

  I see that #1806487 was resolved with 1.1ubuntu1.18.04.7~16.04.2.
  However I'm seeing similar behavior.

  So far I've modified systemd to see if anything stands out.  I do have
  an strace and then just debug mode.

  Unless needed, simply put, this is what a reboot with debug logging
  looks like (i.e. unattended-upgrades-shutdown.log):

  2019-09-06 09:20:04,871 DEBUG - Waiting for signal to start operation
  2019-09-06 09:20:43,996 WARNING - SIGTERM or SIGHUP received, stopping 
unattended-upgradesonly if it is running
  2019-09-06 09:20:43,996 DEBUG - Starting countdown of 25.0 minutes
  2019-09-06 09:20:43,997 DEBUG - get_lock returned 7
  2019-09-06 09:20:43,997 DEBUG - lock not taken

  I hope that helps, please let me know if you need anything else from
  me or if I can provide any more information.

  I've done this many times before, this is the first time it hasn't
  worked.  When I patched around the end of May, all went well.  My
  other variants worked, well mainly Trusty but that's EOL for public
  access.  Bionic doesn't seem to have anything it needs to update.

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

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

[Touch-packages] [Bug 1842902] Re: FFe: create zfs dataset for each user automatically

This bug was fixed in the package zsys - 0.2

---
zsys (0.2) eoan; urgency=medium

  * Add userdata hidden subcommand for creating and renaming user datasets.
(LP: #1842902)
  * Build-dep on grub2-common to not produce s390x build for now until
we support an alternative bootloader.

 -- Didier Roche   Mon, 09 Sep 2019 15:13:26 +0200

** Changed in: zsys (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  FFe: create zfs dataset for each user automatically

Status in shadow package in Ubuntu:
  Triaged
Status in zsys package in Ubuntu:
  Fix Released

Bug description:
  Part of the zsys spec is creating/associating one user dataset for
  each HOME user.

  As zsys is an official experimentation for 19.10, we would like to
  include this feature in a safe way, and reachable for any tool
  creating users (adduser, gnome-control-center, ubiquity…). Those are
  using useradd under the scene.

  For this, the proposed implementation:
  - patch useradd trying to execute "zsys useradd create USER HOMEDIR". If zsys 
isn't present or zsys returns a status code != 0 (which will be the case if the 
running system isn't a zsys one: pure zfs or non zfs like / on ext4), it will 
fallback to mkdir. Then the code does the usual chmod()
  - patch usermod, trying as well to execute "zsys useradd rename-home OLDHOME 
NEWHOME". Same failing reason (not a zsys system, not installed, OLDHOME isn't 
a zsys handled datasets) and fallback to rename(). Then the code does the usual 
chmod().

  Tested with and without zsys installed, the code does what we expect.

  I'm attaching the shadow (useradd/usermod) patches, as you can see it's very 
minimal.
  A new ZSYS release will be needed (https://github.com/ubuntu/zsys). As you 
can see, there are quite some commits since the last release, but it's all 
baked (as usual) by a huge suite of tests (in ZFS and machine layers) with 
corner cases tested and such. I'm confident on that change.

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

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

[Touch-packages] [Bug 1843099] Re: Unattended upgrades does not work on shutdown

2019-09-09 Thread Zahid Bukhari

Hello,

I looked deeper into this, I feel the issue may be with
apt_pkg.get_lock's return value now.  It seems the code considers 0
success whereas now an FD is returned which seems to mean it's fine.

# Example logging output
2019-09-06 10:54:31,249 WARNING - SIGTERM or SIGHUP received, stopping 
unattended-upgradesonly if it is running
2019-09-06 10:54:31,250 DEBUG - Starting countdown of 25.0 minutes
2019-09-06 10:54:31,250 DEBUG - get_lock returned 7
2019-09-06 10:54:31,250 DEBUG - lock not taken

# Tracing manually
/usr/share/unattended-upgrades/unattended-upgrade-shutdown:
L230> 2019-09-06 10:54:31,249 WARNING - SIGTERM or SIGHUP received, stopping 
unattended-upgradesonly if it is running
  * Bug - add space to end (i.e. "SIGTERM or SIGHUP received, stopping 
unattended-upgrades ")
L318> 2019-09-06 10:54:31,250 DEBUG - Starting countdown of 25.0 minutes
L333> 2019-09-06 10:54:31,250 DEBUG - get_lock returned 7
  * Bug - The lock should be acquired so it should be 0 ... according to code 
but docs say it's fine
  L332> res = apt_pkg.get_lock(self.options.lock_file)
  L333> logging.debug("get_lock returned %i" % res) # <-- This is where I 
believe there's the bug
  L334> # exit here if there is no lock
  L335> if res > 0:
  L336> logging.debug("lock not taken")
  L337> if self.lock_was_taken:
  L338> exit_log_result(self.signal_sent)
  L339> else:
  L340> sys.exit(0)
  L341> self.lock_was_taken = True
  L342> signal_stop_unattended_upgrade()
  L343> self.signal_sent = True
  L344> # show log
  L345> log_progress()
  L346> return True

  * Looking deeper into get_lock it shows that a file descriptor is returned
vs -1 or an error raised.  I believe the code may need to be updated as
running python3 interactively, importing apt_pkg and printing its
__doc__ shows the following.  This is Sparta err python 3... so perhaps
that's the reason.

>>> print(apt_pkg.get_lock.__doc__)
get_lock(file: str, errors: bool) -> int

Create an empty file of the given name and lock it. If the locking
succeeds, return the file descriptor of the lock file. Afterwards,
locking the file from another process will fail and thus cause
get_lock() to return -1 or raise an Error (if 'errors' is True).

>From Python 2.6 on, it is recommended to use the context manager
provided by apt_pkg.FileLock instead using the with-statement.

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

Title:
  Unattended upgrades does not work on shutdown

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
   * Ubuntu Xenial 16.04.6 LTS
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
   * 1.1ubuntu1.18.04.7~16.04.3
  3) What you expected to happen
   * Packages to be upgraded on reboot / shutdown.
  4) What happened instead
   * The host just rebooted.  Didn't perform upgrades.  No useful output either 
until I enabled debug logging in the systemd unit file.

  I'm reporting a new bug but this is very similar to #1806487 and I'm
  actually wondering if it resurfaced somehow.

  We're running Ubuntu Xenial 16.04.6 which has
  1.1ubuntu1.18.04.7~16.04.3 installed.

  I see that #1806487 was resolved with 1.1ubuntu1.18.04.7~16.04.2.
  However I'm seeing similar behavior.

  So far I've modified systemd to see if anything stands out.  I do have
  an strace and then just debug mode.

  Unless needed, simply put, this is what a reboot with debug logging
  looks like (i.e. unattended-upgrades-shutdown.log):

  2019-09-06 09:20:04,871 DEBUG - Waiting for signal to start operation
  2019-09-06 09:20:43,996 WARNING - SIGTERM or SIGHUP received, stopping 
unattended-upgradesonly if it is running
  2019-09-06 09:20:43,996 DEBUG - Starting countdown of 25.0 minutes
  2019-09-06 09:20:43,997 DEBUG - get_lock returned 7
  2019-09-06 09:20:43,997 DEBUG - lock not taken

  I hope that helps, please let me know if you need anything else from
  me or if I can provide any more information.

  I've done this many times before, this is the first time it hasn't
  worked.  When I patched around the end of May, all went well.  My
  other variants worked, well mainly Trusty but that's EOL for public
  access.  Bionic doesn't seem to have anything it needs to update.

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

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

[Touch-packages] [Bug 1835135] Re: FIPS OpenSSL crashes Python2 hashlib

This bug was fixed in the package python2.7 - 2.7.12-1ubuntu0~16.04.8

---
python2.7 (2.7.12-1ubuntu0~16.04.8) xenial-security; urgency=medium

  * SECURITY UPDATE: incorrect cookie domain check
- debian/patches/CVE-2018-20852.patch: prefix dot in domain for proper
  subdomain validation in Lib/cookielib.py, Lib/test/test_cookielib.py.
- CVE-2018-20852
  * SECURITY UPDATE: NULL pointer dereference via X509 certificate
- debian/patches/CVE-2019-5010.patch: fix segfault in ssl cert parser
  in Lib/test/talos-2019-0758.pem, Lib/test/test_ssl.py,
  Modules/_ssl.c.
- CVE-2019-5010
  * SECURITY UPDATE: improper handling of unicode encoding
- debian/patches/CVE-2019-9636-1.patch: add check for characters in
  netloc that normalize to separators in Doc/library/urlparse.rst,
  Lib/test/test_urlparse.py, Lib/urlparse.py.
- debian/patches/CVE-2019-9636-2.patch: only print test messages when
  verbose in Lib/test/test_urlparse.py.
- CVE-2019-9636
  * SECURITY UPDATE: HTTP header injection
- debian/patches/bpo30500.patch: simplify splithost by calling into
  urlparse in Lib/test/test_urllib.py, Lib/urllib.py.
- debian/patches/CVE-2019-9740.patch: disallow control chars in http
  URLs in Lib/httplib.py, Lib/test/test_urllib.py,
  Lib/test/test_urllib2.py, Lib/test/test_xmlrpc.py.
- CVE-2019-9740
- CVE-2019-9947
  * SECURITY UPDATE: urllib support the local_file: scheme
- debian/patches/CVE-2019-9948.patch: disallow file reading in
  Lib/urllib.py, Lib/test/test_urllib.py.
- CVE-2019-9948
  * SECURITY UPDATE: incomplete fix for CVE-2019-9636
- debian/patches/CVE-2019-10160-1.patch: fix handling of
  pre-normalization characters in urlsplit() in
  Lib/test/test_urlparse.py, Lib/urlparse.py.
- debian/patches/CVE-2019-10160-2.patch: correct fix to handle
  decomposition in usernames in Lib/test/test_urlparse.py,
  Lib/urlparse.py.
- debian/patches/CVE-2019-10160-3.patch: fix urlparse.urlsplit() error
  message for Unicode URL in Lib/test/test_urlparse.py,
  Lib/urlparse.py.
- CVE-2019-10160
  * debian/patches/issue9146.diff: fix FIPS mode environments where MD5
isn't available in Modules/_hashopenssl.c. (LP: #1835135)

 -- Marc Deslauriers   Thu, 22 Aug 2019
12:36:40 -0400

** Changed in: python2.7 (Ubuntu Xenial)
   Status: In Progress => Fix Released

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

Title:
  FIPS OpenSSL crashes Python2 hashlib

Status in python2.7 package in Ubuntu:
  Triaged
Status in python3.5 package in Ubuntu:
  Invalid
Status in python2.7 source package in Xenial:
  Fix Released
Status in python3.5 source package in Xenial:
  Fix Released
Status in python2.7 source package in Bionic:
  Fix Released
Status in python3.5 source package in Bionic:
  Invalid
Status in python2.7 source package in Cosmic:
  Won't Fix
Status in python3.5 source package in Cosmic:
  Invalid
Status in python2.7 source package in Disco:
  Fix Released
Status in python3.5 source package in Disco:
  Invalid
Status in python2.7 source package in Eoan:
  Triaged
Status in python3.5 source package in Eoan:
  Invalid

Bug description:
  If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with
  SSL_library_init, then Python2's hashlib bindings for MD5 can trigger
  a SIGSEGV via a NULL pointer dereference (if calling the .update
  method) or a SIGABRT (if passing input to the constructor or passing
  no input and invoking the .final method). This happens if, for
  example, PyOpenSSL is imported before hashlib.

  Canonical's FIPS patches for OpenSSL introduce some odd behavior that
  arguably should be revisited, but the (TL;DR) core bug is that Python2
  hashlib doesn't properly check the return value of EVP_DigestInit,
  preventing hashlib from falling back to it's internal MD5
  implementation and instead setting things up for use of the MD5
  context to trigger SIGSEGV or SIGABRT.

  Python3 correctly checks the return value, so the fix is to backport
  the relevant code into Python2 (see
  python2.7-2.7.12/Modules/_hashopenssl.c).

  See attached good.py and bad.py files which exhibit the import order-
  dependent crashing issue. See attached fips-md5-python-init-bug.c
  which shows the FIPS OpenSSL behaviors that conditionally tickle the
  Python2 bug. The C file also contains a much more detailed description
  of the Python2 bug and other behavior which I'd rather not repeat
  here.

  I discovered this bug investigating an issue with the third-party apt-
  boto-s3 package. See https://github.com/boto/boto3/issues/2021

  Note that this bug effects Splunk, Inc, which has a corporate Ubuntu
  Advantage license. My login account is attached to a different,
  single-seat license.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1835135] Re: FIPS OpenSSL crashes Python2 hashlib

This bug was fixed in the package python3.5 - 3.5.2-2ubuntu0~16.04.8

---
python3.5 (3.5.2-2ubuntu0~16.04.8) xenial-security; urgency=medium

  * SECURITY UPDATE: incorrect cookie domain check
- debian/patches/CVE-2018-20852.patch: prefix dot in domain for proper
  subdomain validation in Lib/http/cookiejar.py,
  Lib/test/test_http_cookiejar.py.
- CVE-2018-20852
  * SECURITY UPDATE: integer overflow in pickle
- debian/patches/CVE-2018-20406.patch: avoid relying on signed overflow
  in _pickle memos in Modules/_pickle.c.
- CVE-2018-20406
  * SECURITY UPDATE: NULL pointer dereference via X509 certificate
- debian/patches/CVE-2019-5010.patch: fix segfault in ssl cert parser
  in Lib/test/talos-2019-0758.pem, Lib/test/test_ssl.py,
  Modules/_ssl.c.
- CVE-2019-5010
  * SECURITY UPDATE: improper handling of unicode encoding
- debian/patches/CVE-2019-9636.patch: add check for characters in
  netloc that normalize to separators in Doc/library/urllib.parse.rst,
  Lib/test/test_urlparse.py, Lib/urllib/parse.py.
- CVE-2019-9636
  * SECURITY UPDATE: HTTP header injection
- debian/patches/CVE-2019-9740.patch: disallow control chars in http
  URLs in Lib/http/client.py, Lib/test/test_urllib.py,
  Lib/test/test_xmlrpc.py.
- CVE-2019-9740
- CVE-2019-9947
  * SECURITY UPDATE: urllib support the local_file: scheme
- debian/patches/CVE-2019-9948.patch: disallow file reading in
  Lib/urllib/request.py, Lib/test/test_urllib.py.
- CVE-2019-9948
  * SECURITY UPDATE: incomplete fix for CVE-2019-9636
- debian/patches/CVE-2019-10160-1.patch: fix handling of
  pre-normalization characters in urlsplit() in
  Lib/test/test_urlparse.py, Lib/urllib/parse.py.
- debian/patches/CVE-2019-10160-2.patch: correct fix to handle
  decomposition in usernames in Lib/test/test_urlparse.py,
  Lib/urllib/parse.py.
- CVE-2019-10160
  * debian/patches/issue9146.diff: fix FIPS mode environments where MD5
isn't available in Modules/_hashopenssl.c. (LP: #1835135)

 -- Marc Deslauriers   Wed, 10 Jul 2019
07:58:48 -0400

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

Title:
  FIPS OpenSSL crashes Python2 hashlib

Status in python2.7 package in Ubuntu:
  Triaged
Status in python3.5 package in Ubuntu:
  Invalid
Status in python2.7 source package in Xenial:
  In Progress
Status in python3.5 source package in Xenial:
  Fix Released
Status in python2.7 source package in Bionic:
  Fix Released
Status in python3.5 source package in Bionic:
  Invalid
Status in python2.7 source package in Cosmic:
  Won't Fix
Status in python3.5 source package in Cosmic:
  Invalid
Status in python2.7 source package in Disco:
  Fix Released
Status in python3.5 source package in Disco:
  Invalid
Status in python2.7 source package in Eoan:
  Triaged
Status in python3.5 source package in Eoan:
  Invalid

Bug description:
  If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with
  SSL_library_init, then Python2's hashlib bindings for MD5 can trigger
  a SIGSEGV via a NULL pointer dereference (if calling the .update
  method) or a SIGABRT (if passing input to the constructor or passing
  no input and invoking the .final method). This happens if, for
  example, PyOpenSSL is imported before hashlib.

  Canonical's FIPS patches for OpenSSL introduce some odd behavior that
  arguably should be revisited, but the (TL;DR) core bug is that Python2
  hashlib doesn't properly check the return value of EVP_DigestInit,
  preventing hashlib from falling back to it's internal MD5
  implementation and instead setting things up for use of the MD5
  context to trigger SIGSEGV or SIGABRT.

  Python3 correctly checks the return value, so the fix is to backport
  the relevant code into Python2 (see
  python2.7-2.7.12/Modules/_hashopenssl.c).

  See attached good.py and bad.py files which exhibit the import order-
  dependent crashing issue. See attached fips-md5-python-init-bug.c
  which shows the FIPS OpenSSL behaviors that conditionally tickle the
  Python2 bug. The C file also contains a much more detailed description
  of the Python2 bug and other behavior which I'd rather not repeat
  here.

  I discovered this bug investigating an issue with the third-party apt-
  boto-s3 package. See https://github.com/boto/boto3/issues/2021

  Note that this bug effects Splunk, Inc, which has a corporate Ubuntu
  Advantage license. My login account is attached to a different,
  single-seat license.

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

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

[Touch-packages] [Bug 1835135] Re: FIPS OpenSSL crashes Python2 hashlib

This bug was fixed in the package python2.7 - 2.7.16-2ubuntu0.1

---
python2.7 (2.7.16-2ubuntu0.1) disco-security; urgency=medium

  * SECURITY UPDATE: incorrect cookie domain check
- debian/patches/CVE-2018-20852.patch: prefix dot in domain for proper
  subdomain validation in Lib/cookielib.py, Lib/test/test_cookielib.py.
- CVE-2018-20852
  * SECURITY UPDATE: HTTP header injection
- debian/patches/CVE-2019-9740.patch: disallow control chars in http
  URLs in Lib/httplib.py, Lib/test/test_urllib.py,
  Lib/test/test_urllib2.py, Lib/test/test_xmlrpc.py.
- CVE-2019-9740
- CVE-2019-9947
  * SECURITY UPDATE: incomplete fix for CVE-2019-9636
- debian/patches/CVE-2019-10160-1.patch: fix handling of
  pre-normalization characters in urlsplit() in
  Lib/test/test_urlparse.py, Lib/urlparse.py.
- debian/patches/CVE-2019-10160-2.patch: correct fix to handle
  decomposition in usernames in Lib/test/test_urlparse.py,
  Lib/urlparse.py.
- debian/patches/CVE-2019-10160-3.patch: fix urlparse.urlsplit() error
  message for Unicode URL in Lib/test/test_urlparse.py,
  Lib/urlparse.py.
- CVE-2019-10160
  * debian/patches/issue36216-2.diff: only print test messages when verbose
in Lib/test/test_urlparse.py.
  * debian/patches/issue9146.diff: fix FIPS mode environments where MD5
isn't available in Modules/_hashopenssl.c. (LP: #1835135)

 -- Marc Deslauriers   Tue, 09 Jul 2019
12:43:02 -0400

** Changed in: python3.5 (Ubuntu Xenial)
   Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-20406

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

Title:
  FIPS OpenSSL crashes Python2 hashlib

Status in python2.7 package in Ubuntu:
  Triaged
Status in python3.5 package in Ubuntu:
  Invalid
Status in python2.7 source package in Xenial:
  In Progress
Status in python3.5 source package in Xenial:
  Fix Released
Status in python2.7 source package in Bionic:
  Fix Released
Status in python3.5 source package in Bionic:
  Invalid
Status in python2.7 source package in Cosmic:
  Won't Fix
Status in python3.5 source package in Cosmic:
  Invalid
Status in python2.7 source package in Disco:
  Fix Released
Status in python3.5 source package in Disco:
  Invalid
Status in python2.7 source package in Eoan:
  Triaged
Status in python3.5 source package in Eoan:
  Invalid

Bug description:
  If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with
  SSL_library_init, then Python2's hashlib bindings for MD5 can trigger
  a SIGSEGV via a NULL pointer dereference (if calling the .update
  method) or a SIGABRT (if passing input to the constructor or passing
  no input and invoking the .final method). This happens if, for
  example, PyOpenSSL is imported before hashlib.

  Canonical's FIPS patches for OpenSSL introduce some odd behavior that
  arguably should be revisited, but the (TL;DR) core bug is that Python2
  hashlib doesn't properly check the return value of EVP_DigestInit,
  preventing hashlib from falling back to it's internal MD5
  implementation and instead setting things up for use of the MD5
  context to trigger SIGSEGV or SIGABRT.

  Python3 correctly checks the return value, so the fix is to backport
  the relevant code into Python2 (see
  python2.7-2.7.12/Modules/_hashopenssl.c).

  See attached good.py and bad.py files which exhibit the import order-
  dependent crashing issue. See attached fips-md5-python-init-bug.c
  which shows the FIPS OpenSSL behaviors that conditionally tickle the
  Python2 bug. The C file also contains a much more detailed description
  of the Python2 bug and other behavior which I'd rather not repeat
  here.

  I discovered this bug investigating an issue with the third-party apt-
  boto-s3 package. See https://github.com/boto/boto3/issues/2021

  Note that this bug effects Splunk, Inc, which has a corporate Ubuntu
  Advantage license. My login account is attached to a different,
  single-seat license.

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

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

[Touch-packages] [Bug 1835135] Re: FIPS OpenSSL crashes Python2 hashlib

This bug was fixed in the package python2.7 - 2.7.15-4ubuntu4~18.04.1

---
python2.7 (2.7.15-4ubuntu4~18.04.1) bionic-security; urgency=medium

  * SECURITY UPDATE: incorrect cookie domain check
- debian/patches/CVE-2018-20852.patch: prefix dot in domain for proper
  subdomain validation in Lib/cookielib.py, Lib/test/test_cookielib.py.
- CVE-2018-20852
  * SECURITY UPDATE: NULL pointer dereference via X509 certificate
- debian/patches/CVE-2019-5010.patch: fix segfault in ssl cert parser
  in Lib/test/talos-2019-0758.pem, Lib/test/test_ssl.py,
  Modules/_ssl.c.
- CVE-2019-5010
  * SECURITY UPDATE: improper handling of unicode encoding
- debian/patches/CVE-2019-9636-1.patch: add check for characters in
  netloc that normalize to separators in Doc/library/urlparse.rst,
  Lib/test/test_urlparse.py, Lib/urlparse.py.
- debian/patches/CVE-2019-9636-2.patch: only print test messages when
  verbose in Lib/test/test_urlparse.py.
- CVE-2019-9636
  * SECURITY UPDATE: HTTP header injection
- debian/patches/CVE-2019-9740.patch: disallow control chars in http
  URLs in Lib/httplib.py, Lib/test/test_urllib.py,
  Lib/test/test_urllib2.py, Lib/test/test_xmlrpc.py.
- CVE-2019-9740
- CVE-2019-9947
  * SECURITY UPDATE: urllib support the local_file: scheme
- debian/patches/CVE-2019-9948.patch: disallow file reading in
  Lib/urllib.py, Lib/test/test_urllib.py.
- CVE-2019-9948
  * SECURITY UPDATE: incomplete fix for CVE-2019-9636
- debian/patches/CVE-2019-10160-1.patch: fix handling of
  pre-normalization characters in urlsplit() in
  Lib/test/test_urlparse.py, Lib/urlparse.py.
- debian/patches/CVE-2019-10160-2.patch: correct fix to handle
  decomposition in usernames in Lib/test/test_urlparse.py,
  Lib/urlparse.py.
- debian/patches/CVE-2019-10160-3.patch: fix urlparse.urlsplit() error
  message for Unicode URL in Lib/test/test_urlparse.py,
  Lib/urlparse.py.
- CVE-2019-10160
  * debian/patches/issue9146.diff: fix FIPS mode environments where MD5
isn't available in Modules/_hashopenssl.c. (LP: #1835135)

 -- Marc Deslauriers   Tue, 09 Jul 2019
12:51:35 -0400

** Changed in: python2.7 (Ubuntu Bionic)
   Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-20852

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-10160

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-5010

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9636

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9740

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9947

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9948

** Changed in: python2.7 (Ubuntu Disco)
   Status: In Progress => Fix Released

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

Title:
  FIPS OpenSSL crashes Python2 hashlib

Status in python2.7 package in Ubuntu:
  Triaged
Status in python3.5 package in Ubuntu:
  Invalid
Status in python2.7 source package in Xenial:
  In Progress
Status in python3.5 source package in Xenial:
  Fix Released
Status in python2.7 source package in Bionic:
  Fix Released
Status in python3.5 source package in Bionic:
  Invalid
Status in python2.7 source package in Cosmic:
  Won't Fix
Status in python3.5 source package in Cosmic:
  Invalid
Status in python2.7 source package in Disco:
  Fix Released
Status in python3.5 source package in Disco:
  Invalid
Status in python2.7 source package in Eoan:
  Triaged
Status in python3.5 source package in Eoan:
  Invalid

Bug description:
  If Ubuntu/Canonical's FIPS-compliant OpenSSL is initialized with
  SSL_library_init, then Python2's hashlib bindings for MD5 can trigger
  a SIGSEGV via a NULL pointer dereference (if calling the .update
  method) or a SIGABRT (if passing input to the constructor or passing
  no input and invoking the .final method). This happens if, for
  example, PyOpenSSL is imported before hashlib.

  Canonical's FIPS patches for OpenSSL introduce some odd behavior that
  arguably should be revisited, but the (TL;DR) core bug is that Python2
  hashlib doesn't properly check the return value of EVP_DigestInit,
  preventing hashlib from falling back to it's internal MD5
  implementation and instead setting things up for use of the MD5
  context to trigger SIGSEGV or SIGABRT.

  Python3 correctly checks the return value, so the fix is to backport
  the relevant code into Python2 (see
  python2.7-2.7.12/Modules/_hashopenssl.c).

  See attached good.py and bad.py files which exhibit the import order-
  dependent crashing issue. See attached fips-md5-python-init-bug.c
  which shows the FIPS OpenSSL behaviors that conditionally tickle the
  Python2 bug. The C file also contains a much more

[Touch-packages] [Bug 1842436] Re: [UBUNTU] Avoid creation of mixed-blocksize PV on LVM volume groups

Setup with mixed PVs (on dasds forced with dasdfmt):

ubuntu@eoan-disktest:~$ sudo pvdisplay 
  "/dev/vdc1" is a new physical volume of "<6.88 GiB"
  --- NEW Physical volume ---
  PV Name   /dev/vdc1
  VG Name   
  PV Size   <6.88 GiB
  Allocatable   NO
  PE Size   0   
  Total PE  0
  Free PE   0
  Allocated PE  0
  PV UUID   GqEvSA-Qalj-415c-01i7-0Zxb-gXTW-oUd7BW
   
  "/dev/vdd1" is a new physical volume of "<6.88 GiB"
  --- NEW Physical volume ---
  PV Name   /dev/vdd1
  VG Name   
  PV Size   <6.88 GiB
  Allocatable   NO
  PE Size   0   
  Total PE  0
  Free PE   0
  Allocated PE  0
  PV UUID   iMkCz2-JfSi-59ZS-RCzr-nAdC-9SUf-U9EeOu
   
  "/dev/vde1" is a new physical volume of "3.51 GiB"
  --- NEW Physical volume ---
  PV Name   /dev/vde1
  VG Name   
  PV Size   3.51 GiB
  Allocatable   NO
  PE Size   0   
  Total PE  0
  Free PE   0
  Allocated PE  0
  PV UUID   vuWlZW-lALQ-Om05-a57f-e0Qu-pE4W-6Rmqyn
   
  "/dev/vdf1" is a new physical volume of "3.51 GiB"
  --- NEW Physical volume ---
  PV Name   /dev/vdf1
  VG Name   
  PV Size   3.51 GiB
  Allocatable   NO
  PE Size   0   
  Total PE  0
  Free PE   0
  Allocated PE  0
  PV UUID   OkVIqF-yXA3-MHPr-b3ON-A6Ua-d5GZ-QOHUae
   
ubuntu@eoan-disktest:~$ sudo blockdev --getss /dev/vdc1 /dev/vdd1 /dev/vde1 
/dev/vdf1
4096
4096
512
512

out of these creating mixed size VG and LV:
$ sudo vgcreate vol_grp1 /dev/vdc1 /dev/vdd1 /dev/vde1 /dev/vdf1
$ sudo lvcreate  -l 18 -n log_vol1 vol_grp1
$ sudo lvdisplay 
  --- Logical volume ---
  LV Path/dev/vol_grp1/log_vol1
  LV Namelog_vol1
  VG Namevol_grp1
  LV UUIDSNbOFb-F233-2RYv-rjy4-iGW6-Fmo0-f0NNU0
  LV Write Accessread/write
  LV Creation host, time eoan-disktest, 2019-09-09 14:51:41 +
  LV Status  available
  # open 0
  LV Size72.00 MiB
  Current LE 18
  Segments   1
  Allocation inherit
  Read ahead sectors auto
  - currently set to 256
  Block device   253:0

Updating to the test build with the requested fix (after
lvremove/vgremove).

Now the same create gives me
$ sudo vgcreate vol_grp1 /dev/vdc1 /dev/vdd1 /dev/vde1 /dev/vdf1
  Devices have inconsistent logical block sizes (4096 and 512).
  See lvm.conf allow_mixed_block_sizes.
$ echo $?
5

I can throw this line into lvm.conf devices section:
allow_mixed_block_sizes = 1
to make it work again.


I personally miss an entry to the man page or the default .conf file.
I might need to take a look if that was added in another commit, but 
functionally it looks good already. But if anyone wants the PPA would be 
already testable.

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

Title:
  [UBUNTU] Avoid creation of mixed-blocksize PV on LVM volume groups

Status in Ubuntu on IBM z Systems:
  Triaged
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Default block-size of a file-system seems to be dependent on the volume-size.
  Big volume (at least ext4) does have 4k blk-size, even the underlying device 
with a smaller physical blk-size.

  The patch, avoiding define mixed-sized volume groups is now upstream
  in the master branch of LVM2
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=0404539edb25e4a9d3456bb3e6b402aa2767af6b

  Using this patch within the distribution is for sanity reasons.

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

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

[Touch-packages] [Bug 1586077] Re: no manual pages on Ubuntu Touch

2019-09-09 Thread Adolfo Jayme

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: New => Won't Fix

** Changed in: ubuntu-touch-meta (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  no manual pages on Ubuntu Touch

Status in ubuntu-touch-meta package in Ubuntu:
  Won't Fix

Bug description:
  There are no manual pages on Ubuntu Touch.

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

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

[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time

2019-09-09 Thread Edward Hope-Morley

** Tags removed: sts-sru-needed
** Tags added: sts-sru-done

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

Title:
  [SRU] systemd-resolved negative caching for extended period of time

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache
  the result for very long (infinity?). I have to restart systemd-
  resolved to have the negative caching purged.

  * After SERVFAIL DNS server issue has been resolved, chromium/firefox
  still returns DNS error despite host can correctly resolve the name.

  [Test Case]

  * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s 
(See 201d995),
  however, there are several use cases on which this condition is not 
acceptable (See #5552 comments)
  and the only workaround would be to disable cache entirely or flush it , 
which isn't optimal.

  * Configure /etc/systemd/resolved.conf as follows:

  Cache=yes (default)

  * Restart systemd-resolved (systemctl restart systemd-
  resolved.service)

  * Run a host/getent command against a entry that will return SERVFAIL
  and check the journalctl output to see that the reply gets served from
  cache.

  root@systemd-disco:/home/ubuntu# host www.no-record.cl
  Host www.montemar.cl not found: 2(SERVFAIL)
  root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n
  -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 
UTC. --
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for 
 on scope dns on ens3/* now complete with 
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet 
with id 61042 on interface 1/AF_INET.
  Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 
6222.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query 
packet for id 53580
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for  
www.no-record.cl IN A.
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache 
hit for  www.no-record.cl IN A
  Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < 
www.no-record.cl IN A> on scope dns on ens3/* now complete with  scope dns on ens3/.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP 
for transaction 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet 
with id 22382.
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming 
packet on transaction 22382 (rcode=SERVFAIL).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: 
SERVFAIL
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative 
entry for: www.metaklass.org IN A, cache mode set to no-negative
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for 
 on scope dns on ens3/ now complete with from network 
(unsigned).
  Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet 
with id 31060 on interface 1/AF_INET.

  The following patch https://github.com/systemd/systemd/pull/13047
  implements the required changes.

  [Other Info]

  Note that systemd in Eoan is being upgraded to upstream 242, so I am
  not adding this to Eoan now, as I don't want to disturb the merge. If
  needed after the merge, I'll add to Eoan.

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

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

[Touch-packages] [Bug 1842902] Re: FFe: create zfs dataset for each user automatically

2019-09-09 Thread Didier Roche

Thanks a lot Łukasz! The MIR is available at
https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1839271, the MIR
part has been acked, it's pending a security review for now.

Anyway, let's proceed with this so that we can test it early in the
wild, thanks again!

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

Title:
  FFe: create zfs dataset for each user automatically

Status in shadow package in Ubuntu:
  Triaged
Status in zsys package in Ubuntu:
  Triaged

Bug description:
  Part of the zsys spec is creating/associating one user dataset for
  each HOME user.

  As zsys is an official experimentation for 19.10, we would like to
  include this feature in a safe way, and reachable for any tool
  creating users (adduser, gnome-control-center, ubiquity…). Those are
  using useradd under the scene.

  For this, the proposed implementation:
  - patch useradd trying to execute "zsys useradd create USER HOMEDIR". If zsys 
isn't present or zsys returns a status code != 0 (which will be the case if the 
running system isn't a zsys one: pure zfs or non zfs like / on ext4), it will 
fallback to mkdir. Then the code does the usual chmod()
  - patch usermod, trying as well to execute "zsys useradd rename-home OLDHOME 
NEWHOME". Same failing reason (not a zsys system, not installed, OLDHOME isn't 
a zsys handled datasets) and fallback to rename(). Then the code does the usual 
chmod().

  Tested with and without zsys installed, the code does what we expect.

  I'm attaching the shadow (useradd/usermod) patches, as you can see it's very 
minimal.
  A new ZSYS release will be needed (https://github.com/ubuntu/zsys). As you 
can see, there are quite some commits since the last release, but it's all 
baked (as usual) by a huge suite of tests (in ZFS and machine layers) with 
corner cases tested and such. I'm confident on that change.

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

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

[Touch-packages] [Bug 1842902] Re: FFe: create zfs dataset for each user automatically

2019-09-09 Thread Łukasz Zemczak

Thanks Didier and Alex! This looks promising. I'm generally +1 on this,
especially that the shadow part of the feature doesn't have to be
blocked on zsys - if all works correctly that is.

For the zsys part, I assume that once we have that we'd like to pull in
zsys to main. Did you reach out to the MIR team and security team about
it already? I wouldn't want us to do a last minute push of zsys right
before release without proper review of all the bits and pieces.

All in all, I'm formally approving the shadow FFe and, with some fear,
the zsys FFe as well. Be sure to reach out to the MIR team as early as
possible. If zsys isn't main-ready before beta, well, I wouldn't want it
to be part of our official images.

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

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

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

Title:
  FFe: create zfs dataset for each user automatically

Status in shadow package in Ubuntu:
  Triaged
Status in zsys package in Ubuntu:
  Triaged

Bug description:
  Part of the zsys spec is creating/associating one user dataset for
  each HOME user.

  As zsys is an official experimentation for 19.10, we would like to
  include this feature in a safe way, and reachable for any tool
  creating users (adduser, gnome-control-center, ubiquity…). Those are
  using useradd under the scene.

  For this, the proposed implementation:
  - patch useradd trying to execute "zsys useradd create USER HOMEDIR". If zsys 
isn't present or zsys returns a status code != 0 (which will be the case if the 
running system isn't a zsys one: pure zfs or non zfs like / on ext4), it will 
fallback to mkdir. Then the code does the usual chmod()
  - patch usermod, trying as well to execute "zsys useradd rename-home OLDHOME 
NEWHOME". Same failing reason (not a zsys system, not installed, OLDHOME isn't 
a zsys handled datasets) and fallback to rename(). Then the code does the usual 
chmod().

  Tested with and without zsys installed, the code does what we expect.

  I'm attaching the shadow (useradd/usermod) patches, as you can see it's very 
minimal.
  A new ZSYS release will be needed (https://github.com/ubuntu/zsys). As you 
can see, there are quite some commits since the last release, but it's all 
baked (as usual) by a huge suite of tests (in ZFS and machine layers) with 
corner cases tested and such. I'm confident on that change.

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

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

[Touch-packages] [Bug 1842902] Re: FFe: create zfs dataset for each user automatically

2019-09-09 Thread Didier Roche

attaching shadow build logs

** Attachment added: "shadow_4.5-1.1ubuntu4_amd64.build"

https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1842902/+attachment/5287475/+files/shadow_4.5-1.1ubuntu4_amd64.build

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

Title:
FFe: create zfs dataset for each user automatically

Status in shadow package in Ubuntu:
New
Status in zsys package in Ubuntu:
New

Bug description:
Part of the zsys spec is creating/associating one user dataset for
each HOME user.

As zsys is an official experimentation for 19.10, we would like to
include this feature in a safe way, and reachable for any tool
creating users (adduser, gnome-control-center, ubiquity…). Those are
using useradd under the scene.

For this, the proposed implementation:
- patch useradd trying to execute "zsys useradd create USER HOMEDIR". If zsys
isn't present or zsys returns a status code != 0 (which will be the case if the
running system isn't a zsys one: pure zfs or non zfs like / on ext4), it will
fallback to mkdir. Then the code does the usual chmod()
- patch usermod, trying as well to execute "zsys useradd rename-home OLDHOME
NEWHOME". Same failing reason (not a zsys system, not installed, OLDHOME isn't
a zsys handled datasets) and fallback to rename(). Then the code does the usual
chmod().

Tested with and without zsys installed, the code does what we expect.

I'm attaching the shadow (useradd/usermod) patches, as you can see it's very
minimal.
A new ZSYS release will be needed (https://github.com/ubuntu/zsys). As you
can see, there are quite some commits since the last release, but it's all
baked (as usual) by a huge suite of tests (in ZFS and machine layers) with
corner cases tested and such. I'm confident on that change.

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

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

[Touch-packages] [Bug 1785629] Re: [MIR] gupnp-av

2019-09-09 Thread Sebastien Bacher

** Changed in: gupnp-av (Ubuntu)
   Status: Expired => New

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

Title:
  [MIR] gupnp-av

Status in gupnp-av package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries, including the gupnp-dlna one

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is not being used during build, we are going 
to look at changing that

  * Dependendies

  The package uses standard desktop libraries that are already in main
  (gstreamer, glib)

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 3.9.8, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

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

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

[Touch-packages] [Bug 1832042] Re: static ip= address configuration does not end up in netplan file

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

** Changed in: initramfs-tools (Ubuntu Disco)
   Status: New => Confirmed

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

Title:
  static ip= address configuration does not end up in netplan file

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in initramfs-tools source package in Disco:
  Confirmed
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  static ip= address configuration does not end up in netplan file

  klibc ipconfig process ip=...:$proto and dumps the state into a file,
  which is then parsed to generate runtime netplan configs.

  For static ip configuration ipconfig parses $proto values "off" "none"
  "static" as the same PROTO_NONE and encodes it as PROTO="none" in the
  serialized state file.

  The function that dumps ip data (_declare_ip_info()) has keys only
  values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig)
  or "off" (as valid by the kernel).

  This means that netplan files generated in /run for static ip
  configuration are incomplete.

  Imho we should accept "off" "none" "static" as all valid PROTO
  settings for static ip configuration.

  [Impact]

   * `netplan apply` will not reapply static ip configuration as
  declared in ip= kernel cmdline.

  [Test Case]

   * boot with static ip configuration in the kernel cmdline, e.g.

ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none

Check that /run/netplan/*.yaml contains addresses stanzas.

  [Regression Potential]

   * Runtime netplan configuration will now be more complete. Meaning
  that static ip addresses will now persist across `netplan apply` /
  downing, and reupping an interface. Whilst it was intended for static
  ip addresses to be there, it might be unexpected that they actually
  work properly now.

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

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

[Touch-packages] [Bug 1832042] Re: static ip= address configuration does not end up in netplan file

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

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  static ip= address configuration does not end up in netplan file

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in initramfs-tools source package in Disco:
  Confirmed
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  static ip= address configuration does not end up in netplan file

  klibc ipconfig process ip=...:$proto and dumps the state into a file,
  which is then parsed to generate runtime netplan configs.

  For static ip configuration ipconfig parses $proto values "off" "none"
  "static" as the same PROTO_NONE and encodes it as PROTO="none" in the
  serialized state file.

  The function that dumps ip data (_declare_ip_info()) has keys only
  values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig)
  or "off" (as valid by the kernel).

  This means that netplan files generated in /run for static ip
  configuration are incomplete.

  Imho we should accept "off" "none" "static" as all valid PROTO
  settings for static ip configuration.

  [Impact]

   * `netplan apply` will not reapply static ip configuration as
  declared in ip= kernel cmdline.

  [Test Case]

   * boot with static ip configuration in the kernel cmdline, e.g.

ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none

Check that /run/netplan/*.yaml contains addresses stanzas.

  [Regression Potential]

   * Runtime netplan configuration will now be more complete. Meaning
  that static ip addresses will now persist across `netplan apply` /
  downing, and reupping an interface. Whilst it was intended for static
  ip addresses to be there, it might be unexpected that they actually
  work properly now.

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

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

[Touch-packages] [Bug 1832042] Re: static ip= address configuration does not end up in netplan file

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

** Changed in: initramfs-tools (Ubuntu Cosmic)
   Status: New => Confirmed

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

Title:
  static ip= address configuration does not end up in netplan file

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in initramfs-tools source package in Disco:
  Confirmed
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  static ip= address configuration does not end up in netplan file

  klibc ipconfig process ip=...:$proto and dumps the state into a file,
  which is then parsed to generate runtime netplan configs.

  For static ip configuration ipconfig parses $proto values "off" "none"
  "static" as the same PROTO_NONE and encodes it as PROTO="none" in the
  serialized state file.

  The function that dumps ip data (_declare_ip_info()) has keys only
  values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig)
  or "off" (as valid by the kernel).

  This means that netplan files generated in /run for static ip
  configuration are incomplete.

  Imho we should accept "off" "none" "static" as all valid PROTO
  settings for static ip configuration.

  [Impact]

   * `netplan apply` will not reapply static ip configuration as
  declared in ip= kernel cmdline.

  [Test Case]

   * boot with static ip configuration in the kernel cmdline, e.g.

ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none

Check that /run/netplan/*.yaml contains addresses stanzas.

  [Regression Potential]

   * Runtime netplan configuration will now be more complete. Meaning
  that static ip addresses will now persist across `netplan apply` /
  downing, and reupping an interface. Whilst it was intended for static
  ip addresses to be there, it might be unexpected that they actually
  work properly now.

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

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

[Touch-packages] [Bug 1832042] Re: static ip= address configuration does not end up in netplan file

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

** Changed in: initramfs-tools (Ubuntu Bionic)
   Status: New => Confirmed

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

Title:
  static ip= address configuration does not end up in netplan file

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in initramfs-tools source package in Cosmic:
  Confirmed
Status in initramfs-tools source package in Disco:
  Confirmed
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  static ip= address configuration does not end up in netplan file

  klibc ipconfig process ip=...:$proto and dumps the state into a file,
  which is then parsed to generate runtime netplan configs.

  For static ip configuration ipconfig parses $proto values "off" "none"
  "static" as the same PROTO_NONE and encodes it as PROTO="none" in the
  serialized state file.

  The function that dumps ip data (_declare_ip_info()) has keys only
  values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig)
  or "off" (as valid by the kernel).

  This means that netplan files generated in /run for static ip
  configuration are incomplete.

  Imho we should accept "off" "none" "static" as all valid PROTO
  settings for static ip configuration.

  [Impact]

   * `netplan apply` will not reapply static ip configuration as
  declared in ip= kernel cmdline.

  [Test Case]

   * boot with static ip configuration in the kernel cmdline, e.g.

ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none

Check that /run/netplan/*.yaml contains addresses stanzas.

  [Regression Potential]

   * Runtime netplan configuration will now be more complete. Meaning
  that static ip addresses will now persist across `netplan apply` /
  downing, and reupping an interface. Whilst it was intended for static
  ip addresses to be there, it might be unexpected that they actually
  work properly now.

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

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

[Touch-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

Hi Luke,
thanks for the bug report and your help to make Ubuntu better.
I'm unsure what ssh could/should do differently in this case.

For similar issues there was a gnome PR [1] that went into gnome that should 
allow a "yes and remember" kind of use-case. Not sure if that is missing in the 
gnome in 19.04, just not yet released or not applying here for another case.
I added gnome/wayland tasks to the bug to get the right experts attention on 
this bug.

[1]: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/382

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

** Also affects: gnome-desktop (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Unity in Wayland prompts for keyboard focus on each run of ssh-
  askpass-gnome

Status in gnome-desktop package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Incomplete
Status in wayland package in Ubuntu:
  New

Bug description:
  When using a Wayland-based Unity session on Ubuntu 19.04:

  1. Have ssh-askpass-gnome as your askpass program.
  2. ssh-add -c 
  3. `ssh` to a host

  Each time, before the ssh-askpass prompt is shown, Unity shows this
  dialog:

  +-+
  | |
  | ssh-askpass wants to inhibit shortcuts  |
  | |
  | You can restore Shortcuts by pressing   |
  | Super+Escape.   |
  | |
  |_|
  |   Deny | Allow  |
  +-+

  This is mildly distracting, and it means that you need to hit ,
  answer, , instead of just answer .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ssh-askpass-gnome 1:7.9p1-10
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 15:04:25 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

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

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

[Touch-packages] [Bug 1483751] Re: Issues traversing a sftp server when files or folders contain the character "]"

Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the quality of this bug report and I'm sure
it'll be helpful to others experiencing the same issue.

This is even slightly worse IMHO as it does stripped mapping.
If on a server you have

$ ll \[a\]/ a
'[a]/':
total 8
drwxrwxr-x 2 ubuntu ubuntu 4096 Sep  9 09:51 ./
drwxr-xr-x 9 ubuntu ubuntu 4096 Sep  9 09:51 ../
-rw-rw-r-- 1 ubuntu ubuntu0 Sep  9 09:51 foo

a:
total 8
drwxrwxr-x 2 ubuntu ubuntu 4096 Sep  9 09:51 ./
drwxr-xr-x 9 ubuntu ubuntu 4096 Sep  9 09:51 ../
-rw-rw-r-- 1 ubuntu ubuntu0 Sep  9 09:51 foo

And you are in there with sftp and try to get the file from [a] then you
will get the "other one".

sftp> pwd
Remote working directory: /home/ubuntu/[a]
sftp> ls
foo  
sftp> get foo
Fetching /home/ubuntu/a/foo to foo


Never the less this sounds like an upstream bug/feature-request to me request 
I'd think.
Well and it sit around without anyone noticing for years :-/
But today is my bug triage duty and I at least want to guide you to the right 
place :-)

I tried this up to (including) the last version of 8.0p1.
But as much as this seems wrong, this isn't (IMHO) the kind of issue that 
Ubuntu would develop on its own and keep a delta. After all name/path handling 
often is security relevant and important for scripts (you'd not want different 
hosts to behave differently).

The best route to getting it fixed in Ubuntu in this case would be to
file an upstream bug if you're able to do that. Otherwise, I'm not sure
what we can do directly in Ubuntu to fix the problem.

If you do end up filing an upstream bug, please link to it from here.
Thanks!

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

Title:
  Issues traversing a sftp server when files or folders contain the
  character "]"

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  I am unsure if the bug is with openssh sftp client or within openssh-
  sftp-server

  When traversing an sftp server, I encounter issues for files and, in
  particular, directories containing the character "]". Tab completion
  does not escape the character in sftp shell, however, in bash it will
  escape the character for tab completion. If I "cd" into a directory
  that contains the character I cannot get any files with in that
  directory and I have to rename the directory outside of the sftp shell
  to remove the character in order to be able to correctly get files.

  Ex:

  sftp> cd Movie\ \[1080p]/
  sftp> ls
  Movie.1080p.mp4
  sftp> get Movie.1080p.mp4
  File "/home/hitsuji/movies/Movie [1080p]/Movie.1080p.mp4" not found.
  sftp>

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 14:36:00 2015
  InstallationDate: Installed on 2015-05-01 (101 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.6p1-2ubuntu2
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1842436] Re: [UBUNTU] Avoid creation of mixed-blocksize PV on LVM volume groups

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

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

Title:
  [UBUNTU] Avoid creation of mixed-blocksize PV on LVM volume groups

Status in Ubuntu on IBM z Systems:
  Triaged
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Default block-size of a file-system seems to be dependent on the volume-size.
  Big volume (at least ext4) does have 4k blk-size, even the underlying device 
with a smaller physical blk-size.

  The patch, avoiding define mixed-sized volume groups is now upstream
  in the master branch of LVM2
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=0404539edb25e4a9d3456bb3e6b402aa2767af6b

  Using this patch within the distribution is for sanity reasons.

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

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

[Touch-packages] [Bug 1825167] Re: It does not correctly display the hard drive icon

2019-09-09 Thread Sebastien Bacher

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => Triaged

** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2104
   https://gitlab.gnome.org/GNOME/gtk/issues/2104

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

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

Title:
  It does not correctly display the hard drive icon

Status in Nautilus:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/nautilus/issues/991

  ---

  The icon of my hard drive is SSD (Attach image).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  Uname: Linux 5.0.8-050008-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Apr 17 08:52:05 2019
  InstallationDate: Installed on 2018-12-02 (135 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=es_CL:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
  usr_lib_nautilus:

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

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

[Touch-packages] [Bug 1825167] [NEW] It does not correctly display the hard drive icon

You have been subscribed to a public bug:

https://gitlab.gnome.org/GNOME/nautilus/issues/991

---

The icon of my hard drive is SSD (Attach image).

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.0-0ubuntu2
Uname: Linux 5.0.8-050008-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Wed Apr 17 08:52:05 2019
InstallationDate: Installed on 2018-12-02 (135 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=es_CL:es
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
usr_lib_nautilus:

** Affects: nautilus
 Importance: Unknown
 Status: Fix Released

** Affects: gtk+3.0 (Ubuntu)
 Importance: Low
 Status: Triaged


** Tags: amd64 apport-bug disco
-- 
It does not correctly display the hard drive icon
https://bugs.launchpad.net/bugs/1825167
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1842436] Re: [UBUNTU] Avoid creation of mixed-blocksize PV on LVM volume groups

2019-09-09 Thread Frank Heimes

** Description changed:

- efault blocksize of a file-system seems to be dependent on the volume-size.
+ Default blocksize of a file-system seems to be dependent on the volume-size.
Big volume (at least ext4) does have 4k blk-size, even the underlaying devise
with a smaller phyiscal blk-size.

The patch, avoiding define mixed-sized volume groups is now upstream
in the master branch of LVM2

https://sourceware.org/git/?p=lvm2.git;a=commit;h=0404539edb25e4a9d3456bb3e6b402aa2767af6b

Using this patch within the distribution is for sanity reasons.

** Changed in: ubuntu-z-systems
Status: New => Triaged

** Description changed:

- Default blocksize of a file-system seems to be dependent on the volume-size.
- Big volume (at least ext4) does have 4k blk-size, even the underlaying devise
with a smaller phyiscal blk-size.
+ Default block-size of a file-system seems to be dependent on the volume-size.
+ Big volume (at least ext4) does have 4k blk-size, even the underlying device
with a smaller physical blk-size.

The patch, avoiding define mixed-sized volume groups is now upstream
in the master branch of LVM2

https://sourceware.org/git/?p=lvm2.git;a=commit;h=0404539edb25e4a9d3456bb3e6b402aa2767af6b

Using this patch within the distribution is for sanity reasons.

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

Title:
[UBUNTU] Avoid creation of mixed-blocksize PV on LVM volume groups

Status in Ubuntu on IBM z Systems:
Triaged
Status in lvm2 package in Ubuntu:
New

Bug description:
Default block-size of a file-system seems to be dependent on the volume-size.
Big volume (at least ext4) does have 4k blk-size, even the underlying device
with a smaller physical blk-size.

The patch, avoiding define mixed-sized volume groups is now upstream
in the master branch of LVM2

https://sourceware.org/git/?p=lvm2.git;a=commit;h=0404539edb25e4a9d3456bb3e6b402aa2767af6b

Using this patch within the distribution is for sanity reasons.

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

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

[Touch-packages] [Bug 611791] Re: package man-db 2.5.5-1build1 failed to install/upgrade:

2019-09-09 Thread Julian Andres Klode

This has very likely been fixed since there were a lot of ordering fixes
post trusty.

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

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

Title:
  package man-db 2.5.5-1build1 failed to install/upgrade:

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: man-db

  while trying to upgrade system state, was told this upgrade failed

  ProblemType: Package
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ErrorMessage:
   ErrorMessage: package man-db is already installed and configured
  NonfreeKernelModules: wl
  Package: man-db 2.5.5-1build1
  SourcePackage: man-db
  Title: package man-db 2.5.5-1build1 failed to install/upgrade:
  Uname: Linux 2.6.28-19-generic i686

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

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

[Touch-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken

** Changed in: mutter
   Status: Unknown => New

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

Title:
  [radeon] Rendering of combo boxes and tooltips is broken

Status in Mutter:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Invalid
Status in gtk+3.0 source package in Eoan:
  Invalid
Status in mesa source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Invalid

Bug description:
  Combo boxes are broken (cf screenshot) Tested in gnome-control-center
  and gtk3-demo.

  Tooltips are also garbage.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 07:08:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1869 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago)

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

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

[Touch-packages] [Bug 1691678] Re: Scrollbars escape the bottom and right side of the Terminal window by 1px

FYI, there's a workaround hacked into Yaru:

https://github.com/ubuntu/yaru/blob/master/gtk/src/light/gtk-3.20/_apps.scss#L174

** Also affects: yaru-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: New => Fix Released

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

** Also affects: ubuntu-themes (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Also affects: gnome-terminal via
   https://gitlab.gnome.org/GNOME/gnome-terminal/issues/132
   Importance: Unknown
   Status: Unknown

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

Title:
  Scrollbars escape the bottom and right side of the Terminal window by
  1px

Status in GNOME Terminal:
  Unknown
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu's orange overlay scrollbars escape the bottom of the window
  during resizing.

  To reproduce try gnome-shell on artful using the Ambiance theme. Open
  a Terminal window and resize it vertically, quickly. Notice the bottom
  of the overlay scrollbar overruns the bottom of the window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu3
  Architecture: amd64
  Date: Thu May 18 15:28:33 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 
'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken

Also reported upstream: https://gitlab.gnome.org/GNOME/mutter/issues/767

Though that's also on eoan.

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #767
   https://gitlab.gnome.org/GNOME/mutter/issues/767

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/767
   Importance: Unknown
   Status: Unknown

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

Title:
  [radeon] Rendering of combo boxes and tooltips is broken

Status in Mutter:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Invalid
Status in gtk+3.0 source package in Eoan:
  Invalid
Status in mesa source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Invalid

Bug description:
  Combo boxes are broken (cf screenshot) Tested in gnome-control-center
  and gtk3-demo.

  Tooltips are also garbage.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 07:08:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1869 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago)

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

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

[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2019-09-09 Thread Jerry Kao

I have similar issue with 19.04. Input/ouput with profile HSP/HFP is
very noisy.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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

[Touch-packages] [Bug 1806263] Re: MariaDB 10.1 server won't start when MySQL 5.7 server has been previously installed