date:20190415

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Lubuntu 18.04 ICS not working

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  network-manager:
Installed: 1.10.6-2ubuntu1.1
Candidate: 1.10.6-2ubuntu1.1
Version table:
   *** 1.10.6-2ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.10.6-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  ICS does NOT work.

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

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

[Touch-packages] [Bug 1824916] Re: Wallpaper corruption after waking from sleep

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

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


** This bug has been marked a duplicate of bug 1809407
   [nvidia] Corrupted wallpaper after resuming from suspend

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

Title:
  Wallpaper corruption after waking from sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded to Dingo today, and I'm having a new issue with waking from
  sleep on my Dell XPS 9560. When I wake my laptop, the wallpaper
  becomes corrupted (screenshot attached), and it doesn't go away until
  I restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 23:06:37 2019
  DistUpgraded: 2019-04-15 19:46:05,884 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2018-10-28 (170 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=9f074e0b-7e2f-475a-9cae-48d43abd3345 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-15 (0 days ago)
  dmi.bios.date: 10/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/xorg/+bug/1824916/+subscriptions

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

[Touch-packages] [Bug 1824916] [NEW] Wallpaper corruption after waking from sleep

2019-04-15 Thread Logan Rosen

Public bug reported:

I upgraded to Dingo today, and I'm having a new issue with waking from
sleep on my Dell XPS 9560. When I wake my laptop, the wallpaper becomes
corrupted (screenshot attached), and it doesn't go away until I restart.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
Uname: Linux 5.0.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 15 23:06:37 2019
DistUpgraded: 2019-04-15 19:46:05,884 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:07be]
   Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
InstallationDate: Installed on 2018-10-28 (170 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0c45:6713 Microdia 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/fish
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=9f074e0b-7e2f-475a-9cae-48d43abd3345 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-04-15 (0 days ago)
dmi.bios.date: 10/02/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.product.sku: 07BE
dmi.sys.vendor: Dell Inc.
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

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


** Tags: amd64 apport-bug corruption disco third-party-packages ubuntu

** Attachment added: "Screenshot from 2019-04-15 23-10-53.png"
   
https://bugs.launchpad.net/bugs/1824916/+attachment/5256177/+files/Screenshot%20from%202019-04-15%2023-10-53.png

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

Title:
  Wallpaper corruption after waking from sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded to Dingo today, and I'm having a new issue with waking from
  sleep on my Dell XPS 9560. When I wake my laptop, the wallpaper
  becomes corrupted (screenshot attached), and it doesn't go away until
  I restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 23:06:37 2019
  DistUpgraded: 2019-04-15 19:46:05,884 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  Dist

[Touch-packages] [Bug 1824894] Re: Xorg freeze

1. When the problem happens, can you still move the mouse pointer?

2. Please check for any history of crashes on the system:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

3. Next time the problem happens, please reboot and then run:

   journalctl -b-1 > prevboot.txt

   and send us the file 'prevboot.txt'.


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  When it freezes I typically try and go through my logs. I haven't been
  successful at finding where it crashes in my syslog. However, I did
  find what is listed below this time. I've also ran a memory test on my
  machine which passed. I originally had the nvidia drivers installed
  but after the first few lockups, I thought it might be driver related
  so I uninstalled the driver.

  
  Apr 15 17:13:09 Ben gnome-shell[2251]: Some code accessed the property 
'WindowPreviewMenu' on the module 'windowPreview'. That property was defined 
with 'let' or 'const' inside the module. This was previously supported, but is 
not correct according to the ES6 standard. Any symbols to be exported from a 
module must be defined with 'var'. The property access will work as previously 
for the time being, but please fix your code anyway.
  
\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Apr
 15 17:15:23 Ben systemd-modules-load[394]: Inserted module 'lp'
  Apr 15 17:15:23 Ben systemd-modules-load[394]: Inserted module 'ppdev'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 17:26:09 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver, 2.5.0, 4.18.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: I don't know
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
  InstallationDate: Installed on 2019-03-29 (17 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=758c51d3-8f49-4a44-860b-49982aebbe46 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6X58-E PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/28/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58-EPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug

[Touch-packages] [Bug 1824849] Re: Xorg freeze

If the mouse pointer is moving then it's not Xorg that has frozen.
Because Xorg moves the mouse pointer. It sounds like only your shell has
frozen.

** Tags added: nouveau

** Summary changed:

- Xorg freeze
+ [nouveau] XFCE freeze

** Package changed: xorg (Ubuntu) => xfce (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/1824849

Title:
  [nouveau] XFCE freeze

Status in xfce package in Ubuntu:
  Incomplete

Bug description:
  It seems to randomly lockup.

  Often, I am able to scroll the mouse pointer without being able to
  interact with the desktop itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 15 11:53:04 2019
  DistUpgraded: 2019-03-04 16:15:30,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-47-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: NVIDIA Corporation GK107 [NVS 510] [10de:0967]
  InstallationDate: Installed on 2016-08-18 (970 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 1050:0116 Yubico.com Yubikey NEO(-N) OTP+U2F+CCID
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision Tower 3620
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=UUID=9dad6725-3b16-46e0-806f-31fdb2d56121 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2019-03-04 (41 days ago)
  dmi.bios.date: 05/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 09WH54
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: Precision Tower 3620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.

Thanks. That log shows you are using lightdm and 'slick-greeter', so not
regular Ubuntu.

Are you able to redo those steps using plain Ubuntu? I want to see the
failure happening in a way where lightdm and slick-greeter are not
involved.

** Package changed: gdm3 (Ubuntu) => lightdm (Ubuntu)

** Also affects: slick-greeter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: slick-greeter (Ubuntu)
   Status: New => Incomplete

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

Title:
  Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to
  blank screen that flashes a couple times. Can't get to tty.

Status in lightdm package in Ubuntu:
  Incomplete
Status in slick-greeter package in Ubuntu:
  Incomplete

Bug description:
  Hello. I am having issues consistently with this laptop and the Nvidia
  drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu
  Budgie, and Ubuntu MATE. This is with both the recommended 418 driver
  as well as 390. Today I tried installing the latest daily of Ubuntu
  MATE with the proprietary driver option on my Dell XPS 15 9570 with
  Nvidia GP107M (GeForce GRX 1050 Time Mobile). Boots to blank screen
  that flashes a couple times. Can't get to tty. Reboot, editing grub to
  include nomodeset. Boots to underscore character in the top left. I
  can get tty at least. 418 driver is installed. Looking at logs but
  nothing seems obvious. If there's anything I can do to help with this
  please let me know. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr 13 18:27:12 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2019-04-13 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  MachineType: Dell Inc. XPS 15 9570
  ProcEnviron:
   TERM=cygwin
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=add8471d-1273-4547-aef3-4be006f9eb9c ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/lightdm/+bug/1824661/+subscriptions

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

[Touch-packages] [Bug 1824822] Re: error msg on boot

Please tell us what the error message is that you see, ideally with a
photo.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  error msg on boot

Status in Ubuntu:
  Incomplete

Bug description:
  attempting to find tool and solution to error msg displayed when
  booting ubuntu, nooby so attempting to climb learning mountain

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Apr 15 10:25:36 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.18.0-15-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.18.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-04-10 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 5748
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=9f9f5ad2-dd34-43a3-81a0-8f0cb9dd6759 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0YYR61
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron5748:pvrNotSpecified:rvnDellInc.:rn0YYR61:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5748
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1824661] [NEW] Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.

You have been subscribed to a public bug:

Hello. I am having issues consistently with this laptop and the Nvidia
drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu Budgie,
and Ubuntu MATE. This is with both the recommended 418 driver as well as
390. Today I tried installing the latest daily of Ubuntu MATE with the
proprietary driver option on my Dell XPS 15 9570 with Nvidia GP107M
(GeForce GRX 1050 Time Mobile). Boots to blank screen that flashes a
couple times. Can't get to tty. Reboot, editing grub to include
nomodeset. Boots to underscore character in the top left. I can get tty
at least. 418 driver is installed. Looking at logs but nothing seems
obvious. If there's anything I can do to help with this please let me
know. Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
Uname: Linux 5.0.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
Date: Sat Apr 13 18:27:12 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
InstallationDate: Installed on 2019-04-13 (0 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
MachineType: Dell Inc. XPS 15 9570
ProcEnviron:
 TERM=cygwin
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=add8471d-1273-4547-aef3-4be006f9eb9c ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.1
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

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


** Tags: amd64 apport-bug disco nvidia ubuntu
-- 
Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank 
screen that flashes a couple times. Can't get to tty.
https://bugs.launchpad.net/bugs/1824661
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to lightdm 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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

2019-04-15 Thread Derk Willem te Bokkel

I will try to do videos for you tomorrow it is getting late in the day
here ..

a brief synopsis for now ..

history: this is standard grub arrangement as "installed by default"
used to work flawlessly with multiple partitions of various linux OS's
.. It is only since early march that I noticed an issue with newer
install disco boots failing ..

I have an older disco install on sda1 which has been working all this
time through without issues .. upgraded daily .. no alteration of
netplan config or i915 module forcing..

I can prevent failures in two different ways .. add the module to
/etc/modules or change netplan config to not use NetworkManager as the
default.. attached

my suspicion is that NetworkManager is crashing the system by running
too early as on part of the failure..

the second part is slow loading of the necessary kernal module i915

this may be also the reason the plymouth (busy screen) does not show in
the boot phase of the effected partitions which are all recent disco
xubuntu spins..

an ubuntu install showed no issues .. wayland only works!

When using the freshly installed grub with the partition it belongs to
we get the first boot normal every thing works .. but on restarting
again (2nd boot) xorg/lightdm initially crash then in about 6 seconds
xorg/lightdm restarts ..and works

on any other disco-xubuntu partition (except sda1) booting from this
fresh grub .. we get the initial crash of xorg/lightdm and a locked
system .. no restart of xorg/lightdm at all .. no console either .. only
the power switch/ power removal works to reset ..

and thus " a very perturbed and frustrated tester "

** Attachment added: "01-netcfg.yaml (password obscured)"

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5256176/+files/01-netcfg.yaml

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

Title:
lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870

Status in lightdm package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
Invalid

Bug description:
Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..

back ground .. PC is lenovo sl 500 with evo860 SSD drive

3 partions contain installs of disco sda1 -- main working system -- I
usually install grub from here as master ..

sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
03-22-2019 repectively

on the test installs as long as the iso is using the grub boot loader
installed from that install the system will boot normally .. the display manger
tends to flicker on and off but does final start and login can proceed.

but if another install re-installs grub as master the display manager
fails to stay active or even come-up for sda6 or sda7 only if their
own grubs are reinstalled will they work normally

sda1 display manager/xorg login works always no matter which "grub-
source" is in control.

if I use rescue boot from any grub as master I can get the displays to work
by running dpkg fix which does nothing .. and then resuming the boot .. then
things work normally..
if the "non-rescue" boots are used the screen/computer locks and only a power
down and reboot gives access. (sometime requiring radical depowering ..
unpluging and removing battery)

now the is a message that appears that RCs??? level is missing.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu11
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Mar 25 11:25:58 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
InstallationDate: Installed on 2019-03-23 (1 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
MachineType: LENOVO 2746CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro rec

[Touch-packages] [Bug 1822590] Re: Found storing user fingerprints without encryption

2019-04-15 Thread Seong-Joong Kim

In Ubuntu, that would be good.

Btw, I would like to request escalate importance.

I think that this issue can be even more important than password
exposure in cleartext.

Once fingerprint has been leaked, victims are leaked for the rest of
life since it lasts for a life.

Then, it severely affects applications beyond the package responsible
for the root cause.

What do you think of it?

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

Title:
  Found storing user fingerprints without encryption

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

Bug description:
  Dear all,

  I would like to report a new issue as follows.
  ‘fprintd’ saves a fingerprint data, ISO/IEC 19794-2 formatted, to a file on 
the host without any encryption.
  Though fprintd generates fingerprint image with root permission for 
protecting the file from attackers, it is not of itself sufficient.
  It is well known threat model that a formatted fingerprint data can be 
restored to original image about a decade ago.
  [1-4] are presented to create sophisticated and natural-looking fingerprints 
only from the numerical template data format as defined in ISO/IEC 19794-2.
  They also successfully evaluated these approaches against a number of 
undisclosed state-of-the-art algorithms and the NIST Fingerprint Image Software.

  We need improvements of those issues.

  [1] R. Cappelli et al., “Fingerprint Image Reconstruction from Standard 
Templates”, IEEE Trans. on Pattern Analysis and Machine Intelligence, vol.29, 
no.9, pp.1489-1503, 2007.
  [2] A. Ross et al., “From template to image: Reconstructing fingerprints from 
minutiae points”, IEEE Trans on Pattern Analysis and Machine Intelligence, 
vol.29, no.4, pp.544-560, 2007.
  [3] R. Cappelli et al., “Can Fingerprints be reconstructed from ISO 
Templates?”, IEEE ICARCV 2006.
  [4] J. Feng et al., “Fingerprint Reconstruction: From Minutiae to Phase”, 
IEEE Trans on Pattern Analysis and Machine Intelligence, vol.33, no.2, 
pp.209-223, 2011.

  Sincerely,
  Seong-Joong Kim

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

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

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan mis-configuration ma

2019-04-15 Thread Mathieu Trudel-Lapierre

Okay, this bug has absolutely nothing to do with grub or netplan.
Changing the renderer couldn't possibly affect the behavior of X, and
the grub configuration looks, at a glace, to be run-of-the mill; pretty
much default if you disregard that there is any number of different
installs on the system.

For instance the kernel command-line:

BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-
275b-4537-bed5-f2d3080670eb ro quiet splash

(from various attached output of dmesg)
This command-line is pretty much default. The use of kernels 5.0.0-7 or 5.0.0-8 
are what I'd expect on disco images; and there are no special kernel parameters 
being passed. I don't know what partition root= points to; but this is the only 
possible thing I could see. Grub really doesn't care what you want to start, it 
will just run the kernel and initrd you tell it to. Unless this is a quite 
unforeseen and unlikely bad interaction between kernel drivers and the limited 
gfxmode changes we do in grub... but we'd see this on more than just this 
system.

Could you please attach a video or pictures of what you're seeing on the
screen, along with clear details of *any* modifications you do to boot
something, how you set up your tests, so that we could potentially
reproduce this or see what is happening?

I'm cleaning up the title here for clarity; but this seems like either a
kernel bug, some missing modules for your particular setup, or bad
interactions because of the very complicated multi-boot scenario you're
presenting.

** Summary changed:

- lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan 
mis-configuration maybe underlying cause.
+ lightdm login screen briefly appears and then blanks out on Intel(R) 
Core(TM)2 Duo CPU T5870

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

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in lightdm package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_I

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

2019-04-15 Thread Ubuntu Foundations Team Bug Bot

The attachment "UBUNTU: SAUCE: shiftfs: use correct llseek method for"
seems to be a patch.  If it isn't, please remove the "patch" flag from
the attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal

This bug was fixed in the package unattended-upgrades - 1.10ubuntu4

---
unattended-upgrades (1.10ubuntu4) disco; urgency=medium

  * Make sure autoremovals don't start with a dirty cache and remove other
packages (LP: #1824341)
  * Continue applying minimal sets when one set can't be marked for upgrade.
Thanks to Anderson Luiz Alves for the patch, it needed minor modifications
(LP: #1824341)
  * Stop raising NoAllowedOriginError when marking packages to upgrade/install
fails (LP: #1824876)

 -- Balint Reczey   Tue, 16 Apr 2019 00:01:56 +0200

** Changed in: unattended-upgrades (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  NoAllowedOrigin cause package removal

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.

  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS

  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.

  Log that happens package removal:
  $ sudo unattended-upgrade -d
  [...]
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
  debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
  self.allowed_origins)
File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
  raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
  Exception: 
  marking samba-common-bin for removal
  Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
  marking cliente-ldap for removal
  (Reading database ... 213413 files and directories currently installed.)
  Removing cliente-ldap (1:2.17.15) ...
  marking libcephfs2 for removal
  (Reading database ... 213392 files and directories currently installed.)
  Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking ldap-auth-config for removal
  (Reading database ... 213386 files and directories currently installed.)
  Removing libpam-ldap:amd64 (186-4ubuntu1) ...
  Removing ldap-auth-config (0.5.3) ...
  Removing ldap-auth-client (0.5.3) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking python-samba for removal
  (Reading database ... 213332 files and directories currently installed.)
  Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking nss-updatedb for removal
  (Reading database ... 212865 files and directories currently installed.)
  Removing nss-updatedb (10-3build1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking samba-vfs-modules for removal
  (Reading database ... 212859 files and directories currently installed.)
  Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking librados2 for removal
  (Reading database ... 212770 files and directories currently installed.)
  Removing librados2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking libibverbs1 for removal
  (Reading database ... 212761 files and directories currently installed.)
  Removing ibverbs-providers:amd64 (17.1-1ubuntu0.1) ...
  Removing libibverbs1:amd64 (17.1-1ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking libpam-mount for removal
  (Reading database ... 212731 files and directories currently installed.)
  Removing libpam-mount (2.16-3ubuntu0.1) ...
  Processing triggers for sgml-base (1.29) ...
  Processing triggers for libc-bin (2.27-3ubuntu1)

[Touch-packages] [Bug 1824876] Re: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted

This bug was fixed in the package unattended-upgrades - 1.10ubuntu4

---
unattended-upgrades (1.10ubuntu4) disco; urgency=medium

  * Make sure autoremovals don't start with a dirty cache and remove other
packages (LP: #1824341)
  * Continue applying minimal sets when one set can't be marked for upgrade.
Thanks to Anderson Luiz Alves for the patch, it needed minor modifications
(LP: #1824341)
  * Stop raising NoAllowedOriginError when marking packages to upgrade/install
fails (LP: #1824876)

 -- Balint Reczey   Tue, 16 Apr 2019 00:01:56 +0200

** Changed in: unattended-upgrades (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-
  upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Disco:
  Fix Released

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

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

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

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

2019-04-15 Thread Tyler Hicks

When running a test kernel with Christian's patch, the dir-seek test
case passes:

 $ ./dir-seek
 PASS: orig_count (9) == new_count (9)

Unfortunately, I can't be sure that apparmor policy is loaded correctly
when creating a new LXD container due to the apparmor portion of this
bug report. However, I was able to verify that I can use apparmor_parser
as expected and, after manually doing the SFS_MOUNTPOINT fix in the
apparmor init script, that policy is loaded during container boot.

** Changed in: linux (Ubuntu)
 Assignee: John Johansen (jjohansen) => Christian Brauner (cbrauner)

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

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

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  In Progress

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824894] [NEW] Xorg freeze

2019-04-15 Thread Retroverto

Public bug reported:

When it freezes I typically try and go through my logs. I haven't been
successful at finding where it crashes in my syslog. However, I did find
what is listed below this time. I've also ran a memory test on my
machine which passed. I originally had the nvidia drivers installed but
after the first few lockups, I thought it might be driver related so I
uninstalled the driver.


Apr 15 17:13:09 Ben gnome-shell[2251]: Some code accessed the property 
'WindowPreviewMenu' on the module 'windowPreview'. That property was defined 
with 'let' or 'const' inside the module. This was previously supported, but is 
not correct according to the ES6 standard. Any symbols to be exported from a 
module must be defined with 'var'. The property access will work as previously 
for the time being, but please fix your code anyway.
\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00Apr
 15 17:15:23 Ben systemd-modules-load[394]: Inserted module 'lp'
Apr 15 17:15:23 Ben systemd-modules-load[394]: Inserted module 'ppdev'

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 15 17:26:09 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: openrazer-driver, 2.5.0, 4.18.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: I don't know
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB] 
[19da:1438]
InstallationDate: Installed on 2019-03-29 (17 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=758c51d3-8f49-4a44-860b-49982aebbe46 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0504
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6X58-E PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0504:bd07/28/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58-EPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic freeze 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/1824894

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When it freezes I typically try and go through my logs. I haven't been
  successful at finding where it crashes in my syslog. However, I did
  find what is listed below this time. I've also ran a memory test on my
  machine which passed. I originally had the nvidia drivers installed
  but after the first few lockups, I thought it might be driver related
  so I uninstalled the driver.

  
  Apr 15 17:13:09 Ben gnome-shell[2251]: Some code accessed the property 
'WindowPreviewMenu' on

[Touch-packages] [Bug 1824893] [NEW] When I type systemctl reboot system reaches Target Reboot but then does not reboot

2019-04-15 Thread Robert Dinse

Public bug reported:

This is similar to the bug where systemd used to get stuck in target
Shutdown except that bug affected all my hardware, now it gets stuck at
target Reboot but this only affects my elderly Mac Pro 1,1 and does not
affect my laptop or i7-6700k and i7-6850k based servers.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: systemd 240-6ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
Uname: Linux 5.0.0-8-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Apr 15 16:30:34 2019
InstallationDate: Installed on 2018-12-06 (130 days ago)
InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
MachineType: Apple Computer, Inc. MacPro2,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency 
root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/ondemand.service → 
/lib/systemd/system/ondemand.service.d/ubuntustudio.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago)
dmi.bios.date: 07/02/07
dmi.bios.vendor: Apple Computer, Inc.
dmi.bios.version: MP21.88Z.007F.B06.0707021348
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F4208DC8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Computer, Inc.
dmi.chassis.version: Mac-F4208DC8
dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
dmi.product.family: MacPro
dmi.product.name: MacPro2,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Computer, Inc.

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


** Tags: amd64 apport-bug disco third-party-packages

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

Title:
  When I type systemctl reboot system reaches Target Reboot but then
  does not reboot

Status in systemd package in Ubuntu:
  New

Bug description:
  This is similar to the bug where systemd used to get stuck in target
  Shutdown except that bug affected all my hardware, now it gets stuck
  at target Reboot but this only affects my elderly Mac Pro 1,1 and does
  not affect my laptop or i7-6700k and i7-6850k based servers.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
  Uname: Linux 5.0.0-8-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 15 16:30:34 2019
  InstallationDate: Installed on 2018-12-06 (130 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Apple Computer, Inc. MacPro2,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency 
root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/ondemand.service → 
/lib/systemd/system/ondemand.service.d/ubuntustudio.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago)
  dmi.bios.date: 07/02/07
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MP21.88Z.007F.B06.0707021348
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F4208DC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F4208DC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro2,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

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

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

[Touch-packages] [Bug 1637253] Re: package whoopsie 0.2.24.6ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100

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

** This bug has been marked a duplicate of bug 1504897
   packages with only upstart+systemd without sysvinit fail to upgrade with 
do-release-upgrade: upgrade tarballs ship obsolete invoke-rc.d

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

Title:
  package whoopsie 0.2.24.6ubuntu3 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 100

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Occurred during upgrade from 14.04. System had sury php7 packages
  installed. This was automatically generated by the upgrade program.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: whoopsie 0.2.24.6ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  CrashReports: 600:0:107:362968:2016-10-27 11:51:07.414033651 -0400:2016-10-27 
11:51:08.414033651 -0400:/var/crash/whoopsie.0.crash
  Date: Thu Oct 27 11:51:08 2016
  DuplicateSignature: package:whoopsie:0.2.24.6ubuntu3:subprocess new 
pre-removal script returned error exit status 100
  ErrorMessage: subprocess new pre-removal script returned error exit status 100
  InstallationDate: Installed on 2013-05-21 (1255 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
i386 (20130214)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: whoopsie
  Title: package whoopsie 0.2.24.6ubuntu3 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 100
  UpgradeStatus: Upgraded to xenial on 2016-10-27 (0 days ago)

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

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

[Touch-packages] [Bug 1805203] Re: libcurl3-gnutls in cosmic breaks git with Azure DevOps

2019-04-15 Thread Mark Inderhees

@Thapelo, seems the back port is not yet in Cosmic (18.10). Follow the
steps recommended by Mikhail Shevtsov to resolve the issue.

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

Title:
  libcurl3-gnutls in cosmic breaks git with Azure DevOps

Status in curl package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  Git auth fails when trying to work with an Azure DevOps repository 

  * Test case
  Try to git clone from an Azure DevOps repository using a Personal Access Token
  The clone should work and not fail on an authentification error

  *  Regression potential
  The diff is in the curl http code, it would be good to test a few rdepends to 
make sure they have no regression

  

  The version of libcurl3-gnutls in cosmic (7.61.0) causes
  authentication failures with Azure DevOps. This causes all git
  operations with the server to fail (eg clone, push, pull). For details
  see this curl bug: https://github.com/curl/curl/pull/2754

  To work around this I downgraded libcurl3-gnutls to the version in
  bionic (7.58.0)

  From the curl change list https://curl.haxx.se/changes.html#7_61_1,
  this issue should be fixed in package version 7.61.1 or above.

  Request: please upgrade package in cosmic for libcurl3-gnutls to
  7.61.1 or above

  Details:
  1 - Ubuntu 18.10
  2 - libcurl3-gnutls (7.61.0-1ubuntu2.2 and others)
  3 - Be able to git clone from an Azure DevOps repository using a Personal 
Access Token
  4 - git operations fail to authenticate

  Thank you,
  Mark

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

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

[Touch-packages] [Bug 1504723] Re: package android-tools-adbd 4.2.2+git20130218-3ubuntu41 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100

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

** This bug has been marked a duplicate of bug 1504897
   packages with only upstart+systemd without sysvinit fail to upgrade with 
do-release-upgrade: upgrade tarballs ship obsolete invoke-rc.d

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

Title:
  package android-tools-adbd 4.2.2+git20130218-3ubuntu41 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 100

Status in android-tools package in Ubuntu:
  New

Bug description:
  Upgrading to 15.10

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: android-tools-adbd 4.2.2+git20130218-3ubuntu41
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  Date: Fri Oct  9 20:37:44 2015
  DuplicateSignature: 
package:android-tools-adbd:4.2.2+git20130218-3ubuntu41:subprocess new 
pre-removal script returned error exit status 100
  ErrorMessage: subprocess new pre-removal script returned error exit status 100
  InstallationDate: Installed on 2014-05-29 (498 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.10.2ubuntu1
  SourcePackage: android-tools
  Title: package android-tools-adbd 4.2.2+git20130218-3ubuntu41 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 
100
  UpgradeStatus: Upgraded to wily on 2015-10-10 (0 days ago)

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

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

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

2019-04-15 Thread Tyler Hicks

I was able to narrow down this apparmor_parser error to shiftfs:

AppArmor parser error for /etc/apparmor.d/sbin.dhclient in
/etc/apparmor.d/tunables/home at line 25: Could not process include
directory '/etc/apparmor.d/tunables/home.d' in 'tunables/home.d'

The problem stems from shiftfs not handling this sequence:

 getdents()
  lseek() to reset the f_pos to 0
   getdents()

I'm attaching a test case for this issue, called dir-seek.c.

When ran on a non-shiftfs filesystem, you'll see something like this:

 $ ./dir-seek 
 PASS: orig_count (29) == new_count (29)

When you run the test case on shiftfs, you'll see something like this:

 $ ./dir-seek 
 FAIL: orig_count (29) != new_count (0)

The f_pos of the directory file is not properly tracked/reset on
shiftfs.

** Attachment added: "dir-seek.c"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1824812/+attachment/5256075/+files/dir-seek.c

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

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

2019-04-15 Thread Christian Brauner

Okay, I have a fix for the shiftfs side I think. Attached here.

** Patch added: "UBUNTU: SAUCE: shiftfs: use correct llseek method for"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1824812/+attachment/5256074/+files/0001-UBUNTU-SAUCE-shiftfs-use-correct-llseek-method-for-d.patch

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

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal

Hello Anderson, or anyone else affected,

Accepted unattended-upgrades into disco-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/unattended-
upgrades/1.10ubuntu4 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unattended-upgrades (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

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

Title:
  NoAllowedOrigin cause package removal

Status in unattended-upgrades package in Ubuntu:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed

Bug description:
  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.

  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS

  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.

  Log that happens package removal:
  $ sudo unattended-upgrade -d
  [...]
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
  debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
  self.allowed_origins)
File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
  raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
  Exception: 
  marking samba-common-bin for removal
  Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
  marking cliente-ldap for removal
  (Reading database ... 213413 files and directories currently installed.)
  Removing cliente-ldap (1:2.17.15) ...
  marking libcephfs2 for removal
  (Reading database ... 213392 files and directories currently installed.)
  Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking ldap-auth-config for removal
  (Reading database ... 213386 files and directories currently installed.)
  Removing libpam-ldap:amd64 (186-4ubuntu1) ...
  Removing ldap-auth-config (0.5.3) ...
  Removing ldap-auth-client (0.5.3) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking python-samba for removal
  (Reading database ... 213332 files and directories currently installed.)
  Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking nss-updatedb for removal
  (Reading database ... 212865 files and directories currently installed.)
  Removing nss-updatedb (10-3build1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking samba-vfs-modules for removal
  (Reading database ... 212859 files and directories currently installed.)
  Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking librados2 for

[Touch-packages] [Bug 1824876] Re: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted

Hello errors.ubuntu.com, or anyone else affected,

Accepted unattended-upgrades into disco-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/unattended-
upgrades/1.10ubuntu4 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: unattended-upgrades (Ubuntu Disco)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-disco

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

Title:
  /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-
  upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted

Status in unattended-upgrades package in Ubuntu:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed

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

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

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

This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.2

---
netplan.io (0.96-0ubuntu0.18.10.2) cosmic; urgency=medium

  * d/p/0001-Partially-revert-the-change-for-enabling-systemd-net.patch:
Partially revert changes to networkd jobs ordering: leave systemd-networkd
enabled in multi-user.target instead of network-online.target, as in some
minimal setups there might be no job requiring network-online.target,
whereas the natural target to reach for booting is multi-user.target.
(LP: #1821867)

netplan.io (0.96-0ubuntu0.18.10.1) cosmic; urgency=medium

  * Backport netplan.io 0.96 to 18.10.
  * debian/patches/glib_changes.patch: Patch tests to work again on older GLib.
  * debian/control: adjust Depends for cosmic / re-add nplan package.

netplan.io (0.96-0ubuntu1) disco; urgency=medium

  * New upstream release 0.96.
- Moved netplan-wpa@ services to earlier at boot (LP: #1819014)
- Restart services when unconfiguring (LP: #1811868)
- Use the .nmconnection extension for NM keyfiles (LP: #1817655)
- Fixed integration tests runner to correctly report failures
- Enforce integrity for use-routes in networkd backend.
- Ensure terminal state at end of test (LP: #1817660)
- Various small test fixes.
- Fix typos in documentation.
  * debian/control: Update Maintainer for ubuntu upload.

netplan.io (0.95-2) unstable; urgency=medium

  * Set Priority to optional (Closes: #920327).

netplan.io (0.95-1) unstable; urgency=medium

  * New upstream release.
  * Update autopkgtests from the upstream.
  * Add debian/watch following GitHub releases.
  * Add Homepage (Closes: #917233).

netplan.io (0.95) disco; urgency=medium

  * New upstream release:
- Added support for WPA Enterprise / 802.1x authentication (LP: #1739578)
- Added support for setting up IP tunnels; supporting the types: ipip,
  gretap, VTI, ISATAP (NetworkManager only), sit, gre, ipip6 and ip6ip6.
  + Fixes sit (ipv6) tunnels using Hurricane Electric (LP: #1799487)
- Add support to override networkd UseMTU setting (LP: #1807273)
- Generate output files in dependency order
- Refactored unit and integration tests, along with various cleanups.
- Add DHCP overrides to control route usage and default metric for DHCP
  routes. (LP: #1776228)
- Mitigate against bad matching on devices behind bonds then they share
  the same MAC from a physical interface. (LP: #1804861)
- Added snapcraft.yaml.

netplan.io (0.90.1) disco; urgency=medium

  * Do not assume /etc/network exists in postinst, as netbase 5.5 no longer
creates it.
  * netplan/cli/commands/ip.py: fix a flake.

netplan.io (0.90) disco; urgency=medium

  * New upstream release:
- build: fixes for building on RPM-based distros
- build: code prettiness changes (make indentation consistent)
- Fix device name-changes detection (LP: #1770082)
- Add support for IPv6 Privacy Extensions (LP: #1750392)
- Add dhcp{4,6}-overrides to control DNS, NTP, hostname updates via DHCP
  (LP: #1759014)
- Clarify MAC and MTU setting requirements (LP: #1800668)
- Various documentation fixes (LP: #1800669)
- Improve error reporting to give clearer messages and context
  (LP: #1800670)
- Skip non-physical/bond interfaces when applying renames (LP: #1802322)

 -- Mathieu Trudel-Lapierre   Thu, 28 Mar 2019
13:57:46 -0400

** Changed in: netplan.io (Ubuntu Cosmic)
   Status: Fix Committed => 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/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 Committed
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.

[Touch-packages] [Bug 1759014] Update Released

The verification of the Stable Release Update for netplan.io has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
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 Committed
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 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.2

---
netplan.io (0.96-0ubuntu0.18.10.2) cosmic; urgency=medium

  * d/p/0001-Partially-revert-the-change-for-enabling-systemd-net.patch:
Partially revert changes to networkd jobs ordering: leave systemd-networkd
enabled in multi-user.target instead of network-online.target, as in some
minimal setups there might be no job requiring network-online.target,
whereas the natural target to reach for booting is multi-user.target.
(LP: #1821867)

netplan.io (0.96-0ubuntu0.18.10.1) cosmic; urgency=medium

  * Backport netplan.io 0.96 to 18.10.
  * debian/patches/glib_changes.patch: Patch tests to work again on older GLib.
  * debian/control: adjust Depends for cosmic / re-add nplan package.

netplan.io (0.96-0ubuntu1) disco; urgency=medium

  * New upstream release 0.96.
- Moved netplan-wpa@ services to earlier at boot (LP: #1819014)
- Restart services when unconfiguring (LP: #1811868)
- Use the .nmconnection extension for NM keyfiles (LP: #1817655)
- Fixed integration tests runner to correctly report failures
- Enforce integrity for use-routes in networkd backend.
- Ensure terminal state at end of test (LP: #1817660)
- Various small test fixes.
- Fix typos in documentation.
  * debian/control: Update Maintainer for ubuntu upload.

netplan.io (0.95-2) unstable; urgency=medium

  * Set Priority to optional (Closes: #920327).

netplan.io (0.95-1) unstable; urgency=medium

  * New upstream release.
  * Update autopkgtests from the upstream.
  * Add debian/watch following GitHub releases.
  * Add Homepage (Closes: #917233).

netplan.io (0.95) disco; urgency=medium

  * New upstream release:
- Added support for WPA Enterprise / 802.1x authentication (LP: #1739578)
- Added support for setting up IP tunnels; supporting the types: ipip,
  gretap, VTI, ISATAP (NetworkManager only), sit, gre, ipip6 and ip6ip6.
  + Fixes sit (ipv6) tunnels using Hurricane Electric (LP: #1799487)
- Add support to override networkd UseMTU setting (LP: #1807273)
- Generate output files in dependency order
- Refactored unit and integration tests, along with various cleanups.
- Add DHCP overrides to control route usage and default metric for DHCP
  routes. (LP: #1776228)
- Mitigate against bad matching on devices behind bonds then they share
  the same MAC from a physical interface. (LP: #1804861)
- Added snapcraft.yaml.

netplan.io (0.90.1) disco; urgency=medium

  * Do not assume /etc/network exists in postinst, as netbase 5.5 no longer
creates it.
  * netplan/cli/commands/ip.py: fix a flake.

netplan.io (0.90) disco; urgency=medium

  * New upstream release:
- build: fixes for building on RPM-based distros
- build: code prettiness changes (make indentation consistent)
- Fix device name-changes detection (LP: #1770082)
- Add support for IPv6 Privacy Extensions (LP: #1750392)
- Add dhcp{4,6}-overrides to control DNS, NTP, hostname updates via DHCP
  (LP: #1759014)
- Clarify MAC and MTU setting requirements (LP: #1800668)
- Various documentation fixes (LP: #1800669)
- Improve error reporting to give clearer messages and context
  (LP: #1800670)
- Skip non-physical/bond interfaces when applying renames (LP: #1802322)

 -- Mathieu Trudel-Lapierre   Thu, 28 Mar 2019
13:57:46 -0400

** Changed in: netplan.io (Ubuntu Cosmic)
   Status: Fix Committed => 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/1770082

Title:
  systemd-networkd not renaming devices on boot

Status in netplan:
  Fix Released
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in nplan source package in Xenial:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Committed
Status in netplan.io source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on

[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal

2019-04-15 Thread Balint Reczey

There are several issues that need fixing here:

https://github.com/mvo5/unattended-upgrades/pull/191
https://github.com/mvo5/unattended-upgrades/pull/189

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

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

Title:
  NoAllowedOrigin cause package removal

Status in unattended-upgrades package in Ubuntu:
  In Progress

Bug description:
  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.

  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS

  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.

  Log that happens package removal:
  $ sudo unattended-upgrade -d
  [...]
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
  debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
  self.allowed_origins)
File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
  raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
  Exception: 
  marking samba-common-bin for removal
  Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
  marking cliente-ldap for removal
  (Reading database ... 213413 files and directories currently installed.)
  Removing cliente-ldap (1:2.17.15) ...
  marking libcephfs2 for removal
  (Reading database ... 213392 files and directories currently installed.)
  Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking ldap-auth-config for removal
  (Reading database ... 213386 files and directories currently installed.)
  Removing libpam-ldap:amd64 (186-4ubuntu1) ...
  Removing ldap-auth-config (0.5.3) ...
  Removing ldap-auth-client (0.5.3) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking python-samba for removal
  (Reading database ... 213332 files and directories currently installed.)
  Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking nss-updatedb for removal
  (Reading database ... 212865 files and directories currently installed.)
  Removing nss-updatedb (10-3build1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking samba-vfs-modules for removal
  (Reading database ... 212859 files and directories currently installed.)
  Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking librados2 for removal
  (Reading database ... 212770 files and directories currently installed.)
  Removing librados2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking libibverbs1 for removal
  (Reading database ... 212761 files and directories currently installed.)
  Removing ibverbs-providers:amd64 (17.1-1ubuntu0.1) ...
  Removing libibverbs1:amd64 (17.1-1ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking libpam-mount for removal
  (Reading database ... 212731 files and directories currently installed.)
  Removing libpam-mount (2.16-3ubuntu0.1) ...
  Processing triggers for sgml-base (1.29) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking ibverbs-providers for removal
  marking tdb-tools for removal
  (Reading database ... 212691 files and directories currently installed.)
  Removing tdb-tools (1.3.15-2) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking samba-dsdb-modules for removal
  (Reading database ... 212680 files and directories currently installed.)
  Removing samba-dsdb-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  marking libnss-ldap for re

[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts

2019-04-15 Thread Dan Streetman

>  $ dig phspi05 @192.168.2.1
> ;; Warning: Message parser reports malformed message packet.

that's generally not good...

> phspi05.  69314   IN  A   192.168.2.35

ok, this is resolving the "single label" name.  systemd-resolved never
forwards lookups of single-label names (except for LLMNR, I believe).
So, based on earlier output in this bug showing your configured search
domain, let's see what the output looks like when we include the search
domain:

$ dig phspi05.phs

$ dig phspi05.phs @192.168.2.1

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

Title:
  DNS lookup fails for local hosts

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Mint 19 (Ubuntu Bionic) 
  Laptop so Using NetworkManager, and connecting wirelessly to LAN
  Upgraded from Mint 18.3 so using resolvconf...

  Versions:
  network-manager: 1.10.6-2ubuntu1.1
  resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
  systemd: 237-3ubuntu10.15

  dns is specified in NetworkMananager as 192.168.2.1
  the dns is a router, and has static ips assigned to certain hosts on my lan...

  $cat resolv.conf
  nameserver 127.0.0.53
  search phs
  options edns0

  $ nslookup phspi05
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find phspi05: SERVFAIL

  If I explicity specify the dns:

  $ nslookup phspi05 192.168.2.1
  Server:   192.168.2.1
  Address:  192.168.2.1#53

  Non-authoritative answer:
  Name: phspi05
  Address: 192.168.2.35

  I get the correct ip address...

  Same with dig...

  I would expect that the nameserver set in network-manager would be
  used

  From tail of $ systemd-resolve --status

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.2.1
DNS Domain: phs

  So the dns address had been picked up from NetworkManager, but
  apparently is not being used...

  Thought it might be related to this bug:
  https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903

  So installed the proposed fix, but no change. I also tried removing
  package resolvconf, again no change...

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

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

[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts

2019-04-15 Thread Steve Roberts

Sorry for slow response Dan, here is the output:

 $ dig phspi05 @192.168.2.1
;; Warning: Message parser reports malformed message packet.

; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05 @192.168.2.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2588
;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 79718a61fe0a1b8b (echoed)
;; QUESTION SECTION:
;phspi05.   IN  A

;; ADDITIONAL SECTION:
phspi05.69314   IN  A   192.168.2.35

;; Query time: 9 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Mon Apr 15 22:15:35 BST 2019
;; MSG SIZE  rcvd: 64

And for completeness, without specifying the server:

$ dig phspi05

; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37781
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;phspi05.   IN  A

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Apr 15 22:24:42 BST 2019
;; MSG SIZE  rcvd: 36

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

Title:
  DNS lookup fails for local hosts

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Mint 19 (Ubuntu Bionic) 
  Laptop so Using NetworkManager, and connecting wirelessly to LAN
  Upgraded from Mint 18.3 so using resolvconf...

  Versions:
  network-manager: 1.10.6-2ubuntu1.1
  resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
  systemd: 237-3ubuntu10.15

  dns is specified in NetworkMananager as 192.168.2.1
  the dns is a router, and has static ips assigned to certain hosts on my lan...

  $cat resolv.conf
  nameserver 127.0.0.53
  search phs
  options edns0

  $ nslookup phspi05
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find phspi05: SERVFAIL

  If I explicity specify the dns:

  $ nslookup phspi05 192.168.2.1
  Server:   192.168.2.1
  Address:  192.168.2.1#53

  Non-authoritative answer:
  Name: phspi05
  Address: 192.168.2.35

  I get the correct ip address...

  Same with dig...

  I would expect that the nameserver set in network-manager would be
  used

  From tail of $ systemd-resolve --status

  Link 2 (wlp2s0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.2.1
DNS Domain: phs

  So the dns address had been picked up from NetworkManager, but
  apparently is not being used...

  Thought it might be related to this bug:
  https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903

  So installed the proposed fix, but no change. I also tried removing
  package resolvconf, again no change...

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

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

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

Uploaded 2.13.2-9ubuntu6 with the SFS_MOUNTPOINT change.

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

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

2019-04-15 Thread Tyler Hicks

I noticed that confinement inside of LXD containers works fine when
shiftfs is disabled:

$ sudo rmmod shiftfs
$ sudo mv /lib/modules/5.0.0-11-generic/kernel/fs/shiftfs.ko .
$ sudo systemctl restart snap.lxd.daemon 
$ lxc launch ubuntu-daily:d noshift
Creating noshift
Starting noshift

# Now log in to the container and fix the apparmor init script bug
# around SFS_MOUNTPOINT by modifying /lib/apparmor/rc.apparmor.functions
# to define SFS_MOUNTPOINT="${SECURITYFS}/${MODULE}" at the top of
# is_container_with_internal_policy()

$ lxc exec noshift -- sh -x /lib/apparmor/apparmor.systemd reload
$ lxc exec noshift -- aa-status
apparmor module is loaded.
27 profiles are loaded.
27 profiles are in enforce mode.
   /sbin/dhclient
   /snap/core/6673/usr/lib/snapd/snap-confine
   /snap/core/6673/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /usr/bin/man
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/NetworkManager/nm-dhcp-helper
   /usr/lib/connman/scripts/dhclient-script
   /usr/lib/snapd/snap-confine
   /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /usr/sbin/tcpdump
   man_filter
   man_groff
   nvidia_modprobe
   nvidia_modprobe//kmod
   snap-update-ns.core
   snap-update-ns.lxd
   snap.core.hook.configure
   snap.lxd.activate
   snap.lxd.benchmark
   snap.lxd.buginfo
   snap.lxd.check-kernel
   snap.lxd.daemon
   snap.lxd.hook.configure
   snap.lxd.hook.install
   snap.lxd.lxc
   snap.lxd.lxd
   snap.lxd.migrate
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

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

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

Since the apparmor SFS_MOUNTPOINT change is small, I'll prepare an
upload for that immediately. We may need another parser update for the
other issue.

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

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

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  In Progress
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1815089] Re: 100% CPU / usr / lib / tracker / tracker-extract

2019-04-15 Thread El jinete sin cabeza

** Tags removed: 100 cpu
** Tags added: disco

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

Title:
  100% CPU / usr / lib / tracker / tracker-extract

Status in tracker package in Ubuntu:
  Incomplete

Bug description:
  The / usr / lib / tracker / tracker-extract is using almost 100% CPU
  resources see attached image

  After updates on today's date 07/02/2019 has improved the crashes, but
  the hunger for CPU continues.

  **

  O /usr/lib/tracker/tracker-extract está usando quase 100% de recursos
  da CPU vide imagem em anexo

  Após atualizações na data de hoje 07/02/2019 melhorou os travamentos,
  mas a fome por CPU continua.

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

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

[Touch-packages] [Bug 1824341] Re: NoAllowedOrigin cause package removal

** Tags added: bionic disco rls-dd-incoming

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

Title:
  NoAllowedOrigin cause package removal

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  unattended-upgrades remove packages that shouldn't when there is a
  NoAllowedOrigin exception.

  Version:
  unattended-upgrades=1.1ubuntu1.18.04.10
  Ubuntu 18.04.2 LTS

  Description of problem:
  We have a internal package cliente-ldap that depends on samba, when u-u check 
for upgrade samba-common it raise a NoAllowedOrigin exception, then it doesn't 
clear apt.cache and it removes packages that shouldn't.

  Log that happens package removal:
  $ sudo unattended-upgrade -d
  [...]
  Packages that will be upgraded: libsmbclient libwbclient0 python-samba samba 
samba-common samba-common-bin samba-dsdb-modules samba-libs samba-vfs-modules 
smbclient
  Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  debug: call_adjusted samba-common
  debug: marked_pkg: samba: install=False, upgrade=False, delete=True
  debug: marked_pkg: cliente-ldap: install=False, upgrade=False, delete=True
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 257, in call_adjusted
  self.allowed_origins)
File "/usr/bin/unattended-upgrade", line 764, in ver_in_allowed_origin
  raise NoAllowedOriginError()
  NoAllowedOriginError
  debug: marked_pkg: samba-common: install=False, upgrade=True, delete=False
  debug: marked_pkg: smbclient: install=False, upgrade=False, delete=True
  debug: marked_pkg: samba-common-bin: install=False, upgrade=False, delete=True
  Exception: 
  marking samba-common-bin for removal
  Keeping auto-removable samba-common-bin package(s) because it would also 
remove the following packages which should be kept in this step: samba-common
  marking cliente-ldap for removal
  (Reading database ... 213413 files and directories currently installed.)
  Removing cliente-ldap (1:2.17.15) ...
  marking libcephfs2 for removal
  (Reading database ... 213392 files and directories currently installed.)
  Removing libcephfs2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking ldap-auth-config for removal
  (Reading database ... 213386 files and directories currently installed.)
  Removing libpam-ldap:amd64 (186-4ubuntu1) ...
  Removing ldap-auth-config (0.5.3) ...
  Removing ldap-auth-client (0.5.3) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking python-samba for removal
  (Reading database ... 213332 files and directories currently installed.)
  Removing samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing samba-common-bin (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Removing python-samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking nss-updatedb for removal
  (Reading database ... 212865 files and directories currently installed.)
  Removing nss-updatedb (10-3build1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking samba-vfs-modules for removal
  (Reading database ... 212859 files and directories currently installed.)
  Removing samba-vfs-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking librados2 for removal
  (Reading database ... 212770 files and directories currently installed.)
  Removing librados2 (12.2.11-0ubuntu0.18.04.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking libibverbs1 for removal
  (Reading database ... 212761 files and directories currently installed.)
  Removing ibverbs-providers:amd64 (17.1-1ubuntu0.1) ...
  Removing libibverbs1:amd64 (17.1-1ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  marking libpam-mount for removal
  (Reading database ... 212731 files and directories currently installed.)
  Removing libpam-mount (2.16-3ubuntu0.1) ...
  Processing triggers for sgml-base (1.29) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking ibverbs-providers for removal
  marking tdb-tools for removal
  (Reading database ... 212691 files and directories currently installed.)
  Removing tdb-tools (1.3.15-2) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking samba-dsdb-modules for removal
  (Reading database ... 212680 files and directories currently installed.)
  Removing samba-dsdb-modules (2:4.7.6+dfsg~ubuntu-0ubuntu2.7) ...
  marking libnss-ldap for removal
  (Reading database ... 212630 files and directories currently installed.)
  Removing libnss-ldap:amd64 (265-5ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  marking smb

[Touch-packages] [Bug 1824849] Re: Xorg freeze

2019-04-15 Thread Sebastien Bacher

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

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

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  It seems to randomly lockup.

  Often, I am able to scroll the mouse pointer without being able to
  interact with the desktop itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 15 11:53:04 2019
  DistUpgraded: 2019-03-04 16:15:30,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-47-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: NVIDIA Corporation GK107 [NVS 510] [10de:0967]
  InstallationDate: Installed on 2016-08-18 (970 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 1050:0116 Yubico.com Yubikey NEO(-N) OTP+U2F+CCID
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision Tower 3620
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=UUID=9dad6725-3b16-46e0-806f-31fdb2d56121 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2019-03-04 (41 days ago)
  dmi.bios.date: 05/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.6
  dmi.board.name: 09WH54
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: Precision Tower 3620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

The following will reproduce the issue in a disco VM with disco LXD
container:

Initial setup:
1. have an up to date disco vm
$ cat /proc/version_signature 
Ubuntu 5.0.0-11.12-generic 5.0.6

2. sudo snap install lxd
3. sudo adduser `id -un` lxd
4. newgrp lxd
5. sudo lxd init # use defaults
6. . /etc/profile.d/apps-bin-path.sh

After this note the SFS_MOUNTPOINT bug:
1. lxc launch ubuntu-daily:d d-testapparmor
2. lxc exec d-testapparmor /lib/apparmor/apparmor.systemd reload
3. fix /lib/apparmor/rc.apparmor.functions to define 
SFS_MOUNTPOINT="${SECURITYFS}/${MODULE}" at the top of 
is_container_with_internal_policy(). Ie lxc exec d-testapparmor vi 
/lib/apparmor/rc.apparmor.functions 
4. lxc exec d-testapparmor -- sh -x /lib/apparmor/apparmor.systemd reload # 
notice apparmor_parser was called

At this point, these were called (as seen from the sh -x output, above):

/sbin/apparmor_parser --write-cache --replace -- /etc/apparmor.d
/sbin/apparmor_parser --write-cache --replace -- 
/var/lib/snapd/apparmor/profiles

but no profiles were loaded:
$ lxc exec d-testapparmor aa-status

Note weird parser error trying to load an individual profile:
$ lxc exec d-testapparmor -- apparmor_parser -r /etc/apparmor.d/sbin.dhclient 
AppArmor parser error for /etc/apparmor.d/sbin.dhclient in 
/etc/apparmor.d/tunables/home at line 25: Could not process include directory 
'/etc/apparmor.d/tunables/home.d' in 'tunables/home.d'

Stopping and starting the container doesn't help:
$ lxc stop d-testapparmor
$ lxc start d-testapparmor
$ lxc exec d-testapparmor aa-status
apparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.


Note, under 5.0.0-8.9 and with the SFS_MOUNTPOINT fix, the tunables error goes 
away:
$ lxc exec d-testapparmor -- apparmor_parser -r /etc/apparmor.d/sbin.dhclient
$

and the profiles load on container start:
$ lxc exec d-testapparmor aa-status
apparmor module is loaded.
27 profiles are loaded.
27 profiles are in enforce mode.
   /sbin/dhclient
   /snap/core/6673/usr/lib/snapd/snap-confine
   /snap/core/6673/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /usr/bin/man
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/NetworkManager/nm-dhcp-helper
   /usr/lib/connman/scripts/dhclient-script
   /usr/lib/snapd/snap-confine
   /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /usr/sbin/tcpdump
   man_filter
   man_groff
   nvidia_modprobe
   nvidia_modprobe//kmod
   snap-update-ns.core
   snap-update-ns.lxd
   snap.core.hook.configure
   snap.lxd.activate
   snap.lxd.benchmark
   snap.lxd.buginfo
   snap.lxd.check-kernel
   snap.lxd.daemon
   snap.lxd.hook.configure
   snap.lxd.hook.install
   snap.lxd.lxc
   snap.lxd.lxd
   snap.lxd.migrate
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

However, 5.0.0-11.12 has fixes for lxd and apparmor. This 11.12 also
starts using shiftfs. Very interestingly, if I create a container under
5.0.0-8.9, do the SFS_MOUNTPOINT fix and start it under 5.0.0-11.12,
then policy loads and everything seems fine; there are no shiftfs mounts
for that container:

$ lxc exec d-testapparmor -- grep shiftfs /proc/self/mountinfo
$

*but* if I create the container under 11.12, I see the problems and there are 
shiftfs mounts:
$ lxc exec shiftfs-testapparmor -- grep shiftfs /proc/self/mountinfo
1042 443 0:78 / / rw,relatime - shiftfs 
/var/snap/lxd/common/lxd/storage-pools/default/containers/shiftfs-testapparmor/rootfs
 rw,passthrough=3
1067 1043 0:57 /shiftfs-testapparmor /dev/.lxd-mounts rw,relatime master:216 - 
tmpfs tmpfs rw,size=100k,mode=711
1514 1042 0:78 /snap /snap rw,relatime shared:626 - shiftfs 
/var/snap/lxd/common/lxd/storage-pools/default/containers/shiftfs-testapparmor/rootfs
 rw,passthrough=3

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  apparmor does not start in Disco LXD containers

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Triaged
Status in libvirt package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will

[Touch-packages] [Bug 1824876] [NEW] /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted

2019-04-15 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: disco kylin-19.04

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

Title:
  /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-
  upgrade@2256:main:run:mark_pkgs_to_upgrade:mark_upgrade_adjusted:call_adjusted

Status in unattended-upgrades package in Ubuntu:
  New

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

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

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

[Touch-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen after policykit authentication

2019-04-15 Thread Sebastien Bacher

** Package changed: policykit-1 (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  undismissable, unclickable authentication dialog left on screen after
  policykit authentication

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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

[Touch-packages] [Bug 1824874] [NEW] undismissable, unclickable authentication dialog left on screen after policykit authentication

Public bug reported:

In disco, when policykit prompted me for a password in order for update-
manager to dispatch instructions to aptdaemon to perform package
updates, the password dialog remained on the screen after I clicked
'authenticate'.

The window is not clickable, it appears not to even be a window - mouse
presses are received by the window underneath.  The exception is that
the 'cancel' button is active and receives mouse events - but clicking
it does nothing.

This may be a gnome-shell issue rather than policykit.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: policykit-1 0.105-25
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 15 13:14:33 2019
InstallationDate: Installed on 2010-09-24 (3125 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
SourcePackage: policykit-1
UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug disco rls-dd-incoming

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

Title:
  undismissable, unclickable authentication dialog left on screen after
  policykit authentication

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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

[Touch-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen after policykit authentication

Restarting polkit.service does not cause the window to disappear.

** Changed in: policykit-1 (Ubuntu)
   Importance: Undecided => High

** Tags added: rls-dd-incoming

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

Title:
  undismissable, unclickable authentication dialog left on screen after
  policykit authentication

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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

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

[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111

Here's the strace output.

** Attachment added: "straceout"
   
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1824688/+attachment/5256046/+files/straceout

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

Title:
  date+%-Y -d "- N years" errors when N > 111

Status in coreutils package in Ubuntu:
  New

Bug description:
  I have been using 'date +%-Y -d "- 2010 years" in a script for years
  but today after using the script after upgrading to disco it has
  failed.

  After some experimentation it succeeds with upto 111 years but fails
  from 112 onwards.

  Error given is:

  'date: invalid date '- 112 years'.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: coreutils 8.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Sun Apr 14 10:59:36 2019
  InstallationDate: Installed on 2017-10-08 (553 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago)

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

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

[Touch-packages] [Bug 1823125] Re: tomcat9 fails to install in 18.04

2019-04-15 Thread Balint Reczey

** Changed in: tomcat9 (Ubuntu Cosmic)
   Status: Fix Released => Invalid

** Changed in: tomcat9 (Ubuntu Disco)
   Status: Fix Released => Invalid

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

Title:
  tomcat9 fails to install in 18.04

Status in systemd package in Ubuntu:
  Fix Released
Status in tomcat9 package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  Won't Fix
Status in tomcat9 source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in tomcat9 source package in Cosmic:
  Invalid
Status in systemd source package in Disco:
  Fix Released
Status in tomcat9 source package in Disco:
  Invalid

Bug description:
  # apt install tomcat9
  ...
  Setting up tomcat9 (9.0.16-3~18.04) ...
  [/usr/lib/sysusers.d/tomcat9.conf:7] Trailing garbage.

  Creating config file /etc/tomcat9/tomcat-users.xml with new version
  chown: invalid group: ‘root:tomcat’
  dpkg: error processing package tomcat9 (--configure):
   installed tomcat9 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Processing triggers for systemd (237-3ubuntu10.15) ...
  Processing triggers for ca-certificates (20180409) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...

  done.
  done.
  Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
  Errors were encountered while processing:
   tomcat9
  E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111

Thanks for the testing C de-Avillez.

Here's the output of debug:

$ date +%-Y -d "- 112 years" --debug
date: parsed relative part: -112 year(s)
date: input timezone: system default
date: using current time as starting value: '20:47:40'
date: using current date as starting value: '(Y-M-D) 2019-04-15'
date: starting date/time: '(Y-M-D) 2019-04-15 20:47:40'
date: error: adding relative date resulted in an invalid date: '(Y-M-D) 
1907-04-15 20:47:40'
date: invalid date ‘- 112 years’

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

Title:
  date+%-Y -d "- N years" errors when N > 111

Status in coreutils package in Ubuntu:
  New

Bug description:
  I have been using 'date +%-Y -d "- 2010 years" in a script for years
  but today after using the script after upgrading to disco it has
  failed.

  After some experimentation it succeeds with upto 111 years but fails
  from 112 onwards.

  Error given is:

  'date: invalid date '- 112 years'.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: coreutils 8.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Sun Apr 14 10:59:36 2019
  InstallationDate: Installed on 2017-10-08 (553 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago)

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

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

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

There are two bugs that are causing trouble for apparmor policy in LXD
containers:

1. the rc.apparmor.functions bug (easy fix: define SFS_MOUNTPOINT at the right 
time
2. there is some sort of an interaction with the 5.0.0 kernel that is causing 
problems

I'll give complete instructions on how to reproduce in a moment

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

Title:
  apparmor does not start in Disco LXD containers

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

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111

2019-04-15 Thread Paul Eggert

Assaf Gordon reports that he did not reproduce the problem on Ubuntu
Live amd64 dated 2019-04-13 22:28; see:

https://debbugs.gnu.org/35289#25

Perhaps the output of 'env' and 'strace' will help the original reporter
diagnose the problem.

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

Title:
  date+%-Y -d "- N years" errors when N > 111

Status in coreutils package in Ubuntu:
  New

Bug description:
  I have been using 'date +%-Y -d "- 2010 years" in a script for years
  but today after using the script after upgrading to disco it has
  failed.

  After some experimentation it succeeds with upto 111 years but fails
  from 112 onwards.

  Error given is:

  'date: invalid date '- 112 years'.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: coreutils 8.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Sun Apr 14 10:59:36 2019
  InstallationDate: Installed on 2017-10-08 (553 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago)

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

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

[Touch-packages] [Bug 1824498] Re: Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb update

2019-04-15 Thread Serpico

Once again today I couldn't connect to the SSID I normally use, I tried 
something in network manager, through the drop down menu ( accessible through 
left click on the network icon/indicator located on the upper panel, all the 
way down the menu, select "modifications des connexions" ( don't know the 
English version for sure ) select the wifi connection you usually use then 
press the button "modify", a configuration window opens up, on the second tab, 
"Wi-Fi" the "Mode:" setting was set on "Client" I changed it to "Ad hoc" and 
was able to connect right away.
I switched back to "Client" and will monitor the behavior...

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

Title:
  Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb
  update

Status in wpa package in Ubuntu:
  New

Bug description:
  I'm unable to connect to internet through wifi since this morning,
  since wpasupplicant_2.4-0ubuntu6.4_amd64.deb was updated on my machine
  this morning at 3 am and I didn't have trouble ever before I strongly
  suspect this update to have caused the problem

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

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

[Touch-packages] [Bug 1824809] Re: Videoresolution 640 x 480 since latest update. can't be changed

2019-04-15 Thread Timo Aaltonen

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

** This bug has been marked a duplicate of bug 1824677
   Display only has 640x480

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

Title:
  Videoresolution 640 x 480 since latest update. can't be changed

Status in xorg package in Ubuntu:
  New

Bug description:
  Since upgrade direct from start video resolutio borked. 
  Starting with 5.0.0.7 works fine - 5.0.0.11.12 has  problem
  could be - as hard to see - other programmas also unusable. Setting / 
Tweaktools etc can't be used

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 14:57:33 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP107 [GeForce GTX 
1050] [1462:3354]
  InstallationDate: Installed on 2019-04-14 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=67ed91e5-983a-46ac-92a8-146ebb1f62da ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.20
  dmi.board.name: FM2A68M-HD+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.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/xorg/+bug/1824809/+subscriptions

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

[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111

2019-04-15 Thread C de-Avillez

I have ran a few tests on 16.04, 18.04, 18.10, and 19.04 (all X86_64):

16.04:

root@u1604:~# date +%-Y -d '- 2010 years'
9
root@u1604:~# date --version
date (GNU coreutils) 8.25
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.


18.04:

root@bionic:~# date +%-Y -d '- 2010 years'
9
root@bionic:~# date --version
date (GNU coreutils) 8.28
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

18.10:

root@u1810:~# date +%-Y -d '- 2010 years'   

 
9
root@u1810:~# date --version
date (GNU coreutils) 8.28
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

19.04:

cerdea@piatam:/data/buildd/coreutils$ date +%-Y -d '- 2010 years'
date: invalid date ‘- 2010 years’
1 cerdea@piatam:/data/buildd/coreutils$ date --version
date (GNU coreutils) 8.30
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

Interestingly, it is also failing on git head:

130 cerdea@piatam:/data/buildd/coreutils$ src/date +%-Y -d '- 2010 years'
src/date: invalid date ‘- 2010 years’
1 cerdea@piatam:/data/buildd/coreutils$ src/date --version
date (GNU coreutils) 8.31.12-6d78a
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

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

Title:
  date+%-Y -d "- N years" errors when N > 111

Status in coreutils package in Ubuntu:
  New

Bug description:
  I have been using 'date +%-Y -d "- 2010 years" in a script for years
  but today after using the script after upgrading to disco it has
  failed.

  After some experimentation it succeeds with upto 111 years but fails
  from 112 onwards.

  Error given is:

  'date: invalid date '- 112 years'.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: coreutils 8.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Sun Apr 14 10:59:36 2019
  InstallationDate: Installed on 2017-10-08 (553 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago)

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

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

[Touch-packages] [Bug 1824205] Re: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] Playback problem

2019-04-15 Thread Florian Richer

Only Line Out works

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

Title:
  [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front]
  Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My card is detected and with ubuntu-bug all output is detected but on
  Sound Control only SPDIF Output is showed.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:47:50 2019
  InstallationDate: Installed on 2019-04-10 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: Sound Core3D [Sound Blaster Recon3D / Z-Series] - HDA Creative
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: Only some of outputs are working
  Title: [MS-7B09, Creative Sound BlasterX AE-5, Green Headphone Out, Front] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X399 GAMING PRO CARBON AC (MS-7B09)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd08/09/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B09:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX399GAMINGPROCARBONAC(MS-7B09):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B09
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Touch-packages] [Bug 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

2019-04-15 Thread Treviño

Nope, glib fix is enough for nautilus.

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+subscriptions

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

[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111

I got a reply to my bug report on gnu.org which says:

"
From: 
Paul Eggert 
It works for me with coreutils 8.31 on RHEL 7 x86-64:

$ date +%-Y -d "- 2010 years"
9

Most likely you are running on a 32-bit machine, and dates in the year 9
cannot be represented in a 32-bit timestamp. So a simple fix would be
for you to switch to a 64-bit machine.
"

I am using 64bit Ubuntu though.

I have downloaded and compiled coreutils 8.31 to see if the command
worked for me in the upgraded version but the error remains the same.

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

Title:
  date+%-Y -d "- N years" errors when N > 111

Status in coreutils package in Ubuntu:
  New

Bug description:
  I have been using 'date +%-Y -d "- 2010 years" in a script for years
  but today after using the script after upgrading to disco it has
  failed.

  After some experimentation it succeeds with upto 111 years but fails
  from 112 onwards.

  Error given is:

  'date: invalid date '- 112 years'.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: coreutils 8.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Sun Apr 14 10:59:36 2019
  InstallationDate: Installed on 2017-10-08 (553 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago)

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

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

[Touch-packages] [Bug 1824812] Re: apparmor does not start in Disco LXD containers

** Summary changed:

- apparmor no more starting in Disco LXD containers
+ apparmor does not start in Disco LXD containers

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

Title:
  apparmor does not start in Disco LXD containers

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

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824806] Re: Network stops working after systemd update

2019-04-15 Thread Dan Streetman

do you notice similar (problematic) behavior when just restarting
networkd, e.g.:

$ sudo systemctl restart systemd-networkd

or, stopping systemd-networkd, e.g.:

$ sudo systemctl stop systemd-networkd

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

Title:
  Network stops working after systemd update

Status in systemd package in Ubuntu:
  New

Bug description:
  I have four 18.04 servers that are regularly updated and have a
  bond/bridge configured via netplan. Every so often the interfaces
  themselves will have "speed changed to 0" and the server will be
  unresponsive over network. The servers are still usable via the
  console, though. I think I can confidently associate it with systemd
  updates. If I'm manually updating the servers, e.g., `apt dist-
  upgrade`, and there's a system update... the ssh session becomes
  unresponsive when updating systemd, timing of automatic security
  updates seems to coincide with it happening as well. Rebooting fixes
  the issue until the next systemd update. I've included some log
  excerpts and one of my netplan configs below. Thanks!

  syslog:
  `Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f3: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.661292] igb :04:00.3 
enp4s0f3: speed changed to 0 for port enp4s0f3
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f2: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host systemd[1]: Started Network Time Synchronization.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Stopped Flush Journal to Persistent 
Storage.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Stopping Flush Journal to Persistent 
Storage...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.732487] systemd[1]: Stopping 
Journal Service...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.732903] systemd-journald[672]: 
Received SIGTERM from PID 1 (systemd).
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.823634] igb :04:00.2 
enp4s0f2: speed changed to 0 for port enp4s0f2
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.833718] systemd[1]: Stopped 
Journal Service.
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.837652] systemd[1]: Starting 
Journal Service...
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: Lost carrier
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f1: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host systemd[1]: Starting Flush Journal to Persistent 
Storage...
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.912976] systemd[1]: Started 
Journal Service.
  Apr 9 06:39:01 stn-vm-host systemd[1]: Started Flush Journal to Persistent 
Storage.
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058497.971223] igb :04:00.1 
enp4s0f1: speed changed to 0 for port enp4s0f1
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: Lost carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: enp4s0f0: IPv6 
successfully disabled
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: reading /etc/resolv.conf
  Apr 9 06:39:01 stn-vm-host dnsmasq[2557]: using nameserver 127.0.0.53#53
  Apr 9 06:39:01 stn-vm-host kernel: [1058498.109063] igb :04:00.0 
enp4s0f0: speed changed to 0 for port enp4s0f0
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Gained carrier
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: bond0: Configured
  Apr 9 06:39:01 stn-vm-host systemd-networkd[13409]: br0: Configured`

  Apt history, noting the systemd update just before the interfaces when down
  `Start-Date: 2019-04-09 06:38:55
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.15, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.15, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.15, 
237-3ubuntu10.19)
  End-Date: 2019-04-09 06:39:06`

  The netplan config on this server:
  `network:
  ethernets:
  enp4s0f0:
  addresses: []
  dhcp4: false
  dhcp6: false
  enp4

[Touch-packages] [Bug 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

This bug was fixed in the package ubuntu-meta - 1.417.1

---
ubuntu-meta (1.417.1) bionic; urgency=medium

  * Added ubuntu-wsl metapackage from the wsl seed (LP: #1822341)
  * Added wslu to ubuntu-wsl

 -- Balint Reczey   Sat, 30 Mar 2019 15:59:08 +0100

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

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

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

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

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

[Touch-packages] [Bug 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

This bug was fixed in the package ubuntu-meta - 1.361.3

---
ubuntu-meta (1.361.3) xenial; urgency=medium

  * Added ubuntu-wsl metapackage from the wsl seed (LP: #1822341)
  * Added wslu and ubuntu-minimal's dependencies and recommends to ubuntu-wsl

 -- Balint Reczey   Sat, 30 Mar 2019 15:59:08 +0100

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in ubuntu-meta source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

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

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

[Touch-packages] [Bug 1824849] [NEW] Xorg freeze

2019-04-15 Thread Joris

Public bug reported:

It seems to randomly lockup.

Often, I am able to scroll the mouse pointer without being able to
interact with the desktop itself.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Apr 15 11:53:04 2019
DistUpgraded: 2019-03-04 16:15:30,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.15.0-47-generic, x86_64: installed
 virtualbox, 5.2.18, 4.15.0-48-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation GK107 [NVS 510] [10de:0967]
InstallationDate: Installed on 2016-08-18 (970 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
 Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
 Bus 001 Device 002: ID 1050:0116 Yubico.com Yubikey NEO(-N) OTP+U2F+CCID
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision Tower 3620
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic 
root=UUID=9dad6725-3b16-46e0-806f-31fdb2d56121 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to bionic on 2019-03-04 (41 days ago)
dmi.bios.date: 05/26/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.6
dmi.board.name: 09WH54
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: Precision Tower 3620
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze 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/1824849

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  It seems to randomly lockup.

  Often, I am able to scroll the mouse pointer without being able to
  interact with the desktop itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 15 11:53:04 2019
  DistUpgraded: 2019-03-04 16:15:30,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-47-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [NVS 510] [10de:0ffd] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: NVIDIA Corporation GK107 [NVS 510] [10de:0967]
  InstallationDate: Installed on 2016-08-18 (970 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 1050:0116 Yu

[Touch-packages] [Bug 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

There are only a couple of reports in the Error Tracker bucket about
this happening with version 2.20.10-0ubuntu13.3 and those are likely
showing that version due to apport's late package version collection.
Setting to verification-done.

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

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Cosmic:
  Fix Committed

Bug description:
  [Test Case]
  Check Error Tracker bucket and make sure version from -proposed doesn't show 
up there. Given that this happens a whole bunch we should know pretty quick if 
its fixed.

  [Regression Potential]
  The test being modified is designed to not report crashes that happen during 
logout. It's possible that some reports don't have a Date in them but in that 
case we couldn't compare the logind_session information to the Date anyway so 
those crashes would have been reported anyway. Regardless, the potential is 
that we'll have some more crashes reported about things crashing on logout 
which is better than the hundreds of crashes we get like this one.

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

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

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

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

This is due to a bug in upstream parser/rc.apparmor.functions because
SFS_MOUNTPOINT is only set after is_apparmor_loaded() is called, but
is_container_with_internal_policy() doesn't call it.
/lib/apparmor/apparmor.systemd calls is_container_with_internal_policy()
prior to apparmor_start() and it is only through apparmor_start() that
is_apparmor_loaded() is called.

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

Title:
  apparmor no more starting in Disco LXD containers

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

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

** Also affects: apparmor
   Importance: Undecided
   Status: New

** Changed in: apparmor
   Status: New => Triaged

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

Title:
  apparmor no more starting in Disco LXD containers

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

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824688] Re: date+%-Y -d "- N years" errors when N > 111

Ok, it is now reported upstream:

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35289

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

Title:
  date+%-Y -d "- N years" errors when N > 111

Status in coreutils package in Ubuntu:
  New

Bug description:
  I have been using 'date +%-Y -d "- 2010 years" in a script for years
  but today after using the script after upgrading to disco it has
  failed.

  After some experimentation it succeeds with upto 111 years but fails
  from 112 onwards.

  Error given is:

  'date: invalid date '- 112 years'.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: coreutils 8.30-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Sun Apr 14 10:59:36 2019
  InstallationDate: Installed on 2017-10-08 (553 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to disco on 2019-04-13 (1 days ago)

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

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

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

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

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

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

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

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

Title:
  apparmor no more starting in Disco LXD containers

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

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2019-04-15 Thread Eric Desrochers

This is affecting radosgw's civetweb (embedded webserver) when SSL is in
used for Bionic which doesn't yet support OpenSSL 1.1 in civetweb v1.8
-> LP: #1822872 .

The support of OpenSSL 1.1 start only with civetweb v1.10 and later.

- Eric

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  Incomplete
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  Fix Committed
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed
Status in ruby-openssl source package in Bionic:
  Fix Committed
Status in ruby2.5 source package in Bionic:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3
  (e.g. mongodb)

   * Backport TLS v1.3 support patches, where applicable

  [Test cases for the python updates]

  python3.7 is a preview in bionic as a non-supported/non-default
  version of python3. Passing it's own autopkgtests is sufficient
  validation for python3.7. It includes a point release update, with
  OpenSSL 1.1.1 compat and features.

  python3.6 not only has OpenSSL 1.1.1 compat and features patches, but
  also includes a point release update to 3.6.8. It has been part of the
  full-archive rebuild and regression analysis. Autopkgtests were
  triggered for python3.6 and python3-defaults with regressions already
  fixed in the individual packages as appropriate.

  python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1
  compat only. It has been part of the full-archive rebuild and
  regression analysis. Autopkgtests were triggered for python2.7 and
  python-defaults with regressions already fixed in the individual
  packages as appropriate.

  The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 
and python point releases as seen in:
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html

  And analyzed in
  
https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes

   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3

   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. 
Solution is client change to set hostname, or to clamp down the client to 
TLSv1.2.

     - session negotiation is different in TLSv1.3, existing client code
  may fail to create/negotiate/resume session. Clients need to learn how
  to use session callback.

   * This update bundles python 3.6 and 3.7 point releases

  [Other Info]

   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

   * Test OpenSSL is being prepared in
     https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

  [Autopkgtest Regressions]

  dovecot/armhf - flakey

  libnet-ssleay-perl - awaiting sru accept into proposed of
  libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and
  versioned breaks.

  linux* - rebuild testcases passes (for some edge flavours the build
  fail

[Touch-packages] [Bug 1824498] Re: Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb update

2019-04-15 Thread Serpico

Once again today I couldn't connect to the SSID I normally use, I tried 
something in network manager, through the drop down menu ( accessible through 
left click on the network icon/indicator located on the upper panel, all the 
way down the menu, select "modifications des connexions" ( don't know the 
English version for sure ) select the wifi connection you usually use then 
press the button "modify", a configuration window opens up, on the second tab, 
"Wi-Fi" the "Mode:" setting was set on "Client" I changed it to "Ad hoc" and 
was able to connect right away.
I switched back to "Client" and will monitor the behavior...

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

Title:
  Unable to connect to wifi since wpasupplicant_2.4-0ubuntu6.4_amd64.deb
  update

Status in wpa package in Ubuntu:
  New

Bug description:
  I'm unable to connect to internet through wifi since this morning,
  since wpasupplicant_2.4-0ubuntu6.4_amd64.deb was updated on my machine
  this morning at 3 am and I didn't have trouble ever before I strongly
  suspect this update to have caused the problem

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

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

[Touch-packages] [Bug 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages

2019-04-15 Thread Balint Reczey

** Tags added: regression-update

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

Title:
  Unattended upgrades falls back to adjust all upgradable packages in
  attempt to install held packages

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The fix for LP: #1821101 allowed installing packages for which APT's
  resolver could not find solution for without adjusting other packages,
  but also tries to adjust many packages to install packages which are
  held back.

  See:
  
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1396787/comments/21

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

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

[Touch-packages] [Bug 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

This bug was fixed in the package ubuntu-meta - 1.425.1

---
ubuntu-meta (1.425.1) cosmic; urgency=medium

  * Added ubuntu-wsl metapackage from the wsl seed (LP: #1822341)
  * Added wslu to ubuntu-wsl

 -- Balint Reczey   Sat, 30 Mar 2019 15:59:08 +0100

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

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

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

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

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

2019-04-15 Thread John Johansen

Perhaps because of bug 1823379, which broke some code's dynamic
detection of apparmor being enabled via
/sys/module/apparmor/parameters/enabled?

The fix is working its way through the queue and is currently in
proposed.

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

Title:
  apparmor no more starting in Disco LXD containers

Status in apparmor package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

2019-04-15 Thread John Johansen

Sorry, no. Ignore comment #10

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

Title:
  apparmor no more starting in Disco LXD containers

Status in apparmor package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

Yep, adding
 Environment=SFS_MOUNTPOINT=/sys/kernel/security/apparmor/
to
 /lib/systemd/system/apparmor.service
Fixes the bug.

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

Title:
  apparmor no more starting in Disco LXD containers

Status in apparmor package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1822341] Update Released

The verification of the Stable Release Update for ubuntu-meta has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

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

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

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

Adding set -x and calling this directly:

Cosmic:
. /lib/apparmor/functions
is_container_with_internal_policy
+ local ns_stacked_path=/sys/kernel/security/apparmor/.ns_stacked
+ local ns_name_path=/sys/kernel/security/apparmor/.ns_name
+ local ns_stacked
+ local ns_name
+ '[' -f /sys/kernel/security/apparmor/.ns_stacked ']'
+ '[' -f /sys/kernel/security/apparmor/.ns_name ']'
+ read -r ns_stacked
+ '[' yes '!=' yes ']'
+ read -r ns_name
+ '[' 'c-testapparmor_' = 
'lxd-c-testapparmor_' ']'
+ return 0


Disco:
. /lib/apparmor/rc.apparmor.functions
is_container_with_internal_policy
+ local ns_stacked_path=/.ns_stacked
+ local ns_name_path=/.ns_name
+ local ns_stacked
+ local ns_name
+ '[' -f /.ns_stacked ']'
+ return 1

Ok, in my case the ENV var that is now used is not set.

$ export SFS_MOUNTPOINT=/sys/kernel/security/apparmor/
$ is_container_with_internal_policy
+ is_container_with_internal_policy
+ set -x
+ local ns_stacked_path=/sys/kernel/security/apparmor//.ns_stacked
+ local ns_name_path=/sys/kernel/security/apparmor//.ns_name
+ local ns_stacked
+ local ns_name
+ '[' -f /sys/kernel/security/apparmor//.ns_stacked ']'
+ '[' -f /sys/kernel/security/apparmor//.ns_name ']'
+ read -r ns_stacked
+ '[' yes '!=' yes ']'
+ read -r ns_name
+ '[' 'd-testapparmor_' = 
'lxd-d-testapparmor_' ']'
+ return 0

Now it works, could it be that in the init script context this isn't set either?
Yep that is it:
If I patch in the path it works again
 # patch /lib/apparmor/rc.apparmor.functions to have 
SFS_MOUNTPOINT=/sys/kernel/security/apparmor/
 $ systemctl restart apparmor
 $ aa-status
   # lists all profiles again

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

Title:
  apparmor no more starting in Disco LXD containers

Status in apparmor package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1818282] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1812760] Update Released

The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  networkd: [Route] PreferredSource not working in *.network files

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Users cannot create IPv6 routes that specify PreferredSource. This
  means that users cannot specify a number of valid IPv6 routes that are
  useful in some circumstances. These routes can be created with the
  'ip' tool, just not with systemd.

  This was reported upstream in systemd issue #5882 is fixed by pulling
  in the changes in systemd PR #11375 -
  https://github.com/systemd/systemd/pull/11375

  [Test Case]

  Start a Bionic or Cosmic VM.

  Add the following netplan yaml (adjust for ethernet card and MAC):

  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:e2:c2:d7
  set-name: ens3
  addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"]
  routes:
    - to: "a::/16"
  via: "fd8f:1d7d:b141::1"
  from: "fd8f:1d7d:b141::2"
    - to: "fd8f:1d7d:b141::/64"
  scope: link
  from: "fd8f:1d7d:b141::2"
  metric: 255

  Run netplan apply or reboot. Wait ~10s.

  Alternately, to test without netplan, configure systemd-networkd with:

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=fd8f:1d7d:b141::2/64
  Address=fd8f:1d7d:b141::200/64

  [Route]
  Destination=a::/16
  Gateway=fd8f:1d7d:b141::1
  PreferredSource=fd8f:1d7d:b141::2

  [Route]
  Destination=fd8f:1d7d:b141::/64
  PreferredSource=fd8f:1d7d:b141::2
  Scope=link
  Metric=255

  [DHCP]
  UseMTU=true
  RouteMetric=100


  Currently, ip -6 route will not include a route to "a::/16", and will
  not include the route to "fd8f:1d7d:b141::/64" that has
  "fd8f:1d7d:b141::2" as the source address - both those addresses will
  be missing.

  Correct behaviour is for ip -6 route to report the following:

  ubuntu@b-np:~$ ip -6 route
  a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 
metric 1024 pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 
pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium
  fe80::/64 dev ens3 proto kernel metric 256 pref medium

  Check before and after upgrade that 'systemctl status network-
  online.target' shows that the target has been reached.

  [Regression Potential]

  This changes the state machine in systemd which configures the links.
  It passes systemd's internal tests, and has been approved by systemd
  maintainers, but it remains possible that the changes will break the
  configuration of obscure network setups.

  The backport requires pulling in two further commits that also change
  behaviour: currently systemd deletes all addresses and routes that
  were attached to an interface. With this change, it will only delete
  those that are not specified in the configuration files. A side effect
  of this is that restarting networkd will not cause remove/add netlink
  events to be emitted for these addresses, so if anyone is relying on
  this behavior this will break compatibility; but that is an unlikely
  thing to be relying on, and it seems worth this risk to reduce
  unnecessary network state changes.

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

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

[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

This bug was fixed in the package systemd - 239-7ubuntu10.13

---
systemd (239-7ubuntu10.13) cosmic; urgency=medium

  [ Ioanna Alifieraki ]
  * d/p/backport_network-fix-return-value-of-routing_policy_rule_get.patch,
d/p/backport_network-remove-routing-policy-rule-from-foreign.patch,

d/p/backport_network-do-not-remove-rule-when-requested-by-existing-links.patch:
  - Fix RoutingPolicyRule does not apply correctly (LP: #1818282)

  [ Dan Streetman ]
  * d/p/networkd-Track-address-configuration.patch,
d/p/networkd-Use-only-a-generic-CONFIGURING-state.patch,
d/p/networkd-don-t-remove-route.patch,
d/p/networkd-don-t-remove-ip-address.patch,
d/p/Move-link_check_ready-to-later-in-the-file.patch,
d/p/network-set-_configured-flags-to-false-before-reques.patch,
d/p/Install-routes-after-addresses-are-ready.patch:
  - PreferredSource not working in *.network files (LP: #1812760)
  * Specify Ubuntu's Vcs-Git

 -- Dan Streetman   Thu, 04 Apr 2019 07:29:38
-0400

** Changed in: systemd (Ubuntu Cosmic)
   Status: Fix Committed => 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/1818282

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

This bug was fixed in the package systemd - 237-3ubuntu10.20

---
systemd (237-3ubuntu10.20) bionic; urgency=medium

  [ Ioanna Alifieraki ]
  * d/p/backport_network-fix-return-value-of-routing_policy_rule_get.patch,
d/p/backport_network-remove-routing-policy-rule-from-foreign.patch,

d/p/backport_network-do-not-remove-rule-when-requested-by-existing-links.patch:
- Fix RoutingPolicyRule does not apply correctly (LP: #1818282)

  [ Dan Streetman ]
  * d/p/fix-test-22.patch
- fix TEST-22 failures
  * d/p/networkd-Track-address-configuration.patch,
d/p/networkd-Use-only-a-generic-CONFIGURING-state.patch,
d/p/networkd-don-t-remove-route.patch,
d/p/networkd-don-t-remove-ip-address.patch,
d/p/Move-link_check_ready-to-later-in-the-file.patch,
d/p/network-set-_configured-flags-to-false-before-reques.patch,
d/p/Install-routes-after-addresses-are-ready.patch:
- PreferredSource not working in *.network files (LP: #1812760)

  [ Dimitri John Ledkov ]
  * Specify Ubuntu's Vcs-Git

 -- Dan Streetman   Thu, 04 Apr 2019 07:29:38
-0400

** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Committed => 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/1818282

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1812760] Re: networkd: [Route] PreferredSource not working in *.network files

This bug was fixed in the package systemd - 237-3ubuntu10.20

---
systemd (237-3ubuntu10.20) bionic; urgency=medium

  [ Ioanna Alifieraki ]
  * d/p/backport_network-fix-return-value-of-routing_policy_rule_get.patch,
d/p/backport_network-remove-routing-policy-rule-from-foreign.patch,

d/p/backport_network-do-not-remove-rule-when-requested-by-existing-links.patch:
- Fix RoutingPolicyRule does not apply correctly (LP: #1818282)

  [ Dan Streetman ]
  * d/p/fix-test-22.patch
- fix TEST-22 failures
  * d/p/networkd-Track-address-configuration.patch,
d/p/networkd-Use-only-a-generic-CONFIGURING-state.patch,
d/p/networkd-don-t-remove-route.patch,
d/p/networkd-don-t-remove-ip-address.patch,
d/p/Move-link_check_ready-to-later-in-the-file.patch,
d/p/network-set-_configured-flags-to-false-before-reques.patch,
d/p/Install-routes-after-addresses-are-ready.patch:
- PreferredSource not working in *.network files (LP: #1812760)

  [ Dimitri John Ledkov ]
  * Specify Ubuntu's Vcs-Git

 -- Dan Streetman   Thu, 04 Apr 2019 07:29:38
-0400

** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Committed => 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/1812760

Title:
  networkd: [Route] PreferredSource not working in *.network files

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Users cannot create IPv6 routes that specify PreferredSource. This
  means that users cannot specify a number of valid IPv6 routes that are
  useful in some circumstances. These routes can be created with the
  'ip' tool, just not with systemd.

  This was reported upstream in systemd issue #5882 is fixed by pulling
  in the changes in systemd PR #11375 -
  https://github.com/systemd/systemd/pull/11375

  [Test Case]

  Start a Bionic or Cosmic VM.

  Add the following netplan yaml (adjust for ethernet card and MAC):

  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:e2:c2:d7
  set-name: ens3
  addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"]
  routes:
    - to: "a::/16"
  via: "fd8f:1d7d:b141::1"
  from: "fd8f:1d7d:b141::2"
    - to: "fd8f:1d7d:b141::/64"
  scope: link
  from: "fd8f:1d7d:b141::2"
  metric: 255

  Run netplan apply or reboot. Wait ~10s.

  Alternately, to test without netplan, configure systemd-networkd with:

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=fd8f:1d7d:b141::2/64
  Address=fd8f:1d7d:b141::200/64

  [Route]
  Destination=a::/16
  Gateway=fd8f:1d7d:b141::1
  PreferredSource=fd8f:1d7d:b141::2

  [Route]
  Destination=fd8f:1d7d:b141::/64
  PreferredSource=fd8f:1d7d:b141::2
  Scope=link
  Metric=255

  [DHCP]
  UseMTU=true
  RouteMetric=100


  Currently, ip -6 route will not include a route to "a::/16", and will
  not include the route to "fd8f:1d7d:b141::/64" that has
  "fd8f:1d7d:b141::2" as the source address - both those addresses will
  be missing.

  Correct behaviour is for ip -6 route to report the following:

  ubuntu@b-np:~$ ip -6 route
  a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 
metric 1024 pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 
pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium
  fe80::/64 dev ens3 proto kernel metric 256 pref medium

  Check before and after upgrade that 'systemctl status network-
  online.target' shows that the target has been reached.

  [Regression Potential]

  This changes the state machine in systemd which configures the links.
  It passes systemd's internal tests, and has been approved by systemd
  maintainers, but it remains possible that the changes will break the
  configuration of obscure network setups.

  The backport requires pulling in two further commits that also change
  behaviour: currently systemd deletes all addresses and routes that
  were attached to an interface. With this change, it will only delete
  those that are not specified in the configuration files. A side effect
  of this is that restarting networkd will not cause remove/add netlink
  events to be emitted for these addresses, so if anyone is relying on
  this behavior this will break compatibility; but that is an unlikely
  thing to be relying on, and it seems worth this risk to reduce
  unnecessary network state changes.

To manage notifications about this bug go to:
https://bugs.lau

[Touch-packages] [Bug 1812760] Re: networkd: [Route] PreferredSource not working in *.network files

This bug was fixed in the package systemd - 239-7ubuntu10.13

---
systemd (239-7ubuntu10.13) cosmic; urgency=medium

  [ Ioanna Alifieraki ]
  * d/p/backport_network-fix-return-value-of-routing_policy_rule_get.patch,
d/p/backport_network-remove-routing-policy-rule-from-foreign.patch,

d/p/backport_network-do-not-remove-rule-when-requested-by-existing-links.patch:
  - Fix RoutingPolicyRule does not apply correctly (LP: #1818282)

  [ Dan Streetman ]
  * d/p/networkd-Track-address-configuration.patch,
d/p/networkd-Use-only-a-generic-CONFIGURING-state.patch,
d/p/networkd-don-t-remove-route.patch,
d/p/networkd-don-t-remove-ip-address.patch,
d/p/Move-link_check_ready-to-later-in-the-file.patch,
d/p/network-set-_configured-flags-to-false-before-reques.patch,
d/p/Install-routes-after-addresses-are-ready.patch:
  - PreferredSource not working in *.network files (LP: #1812760)
  * Specify Ubuntu's Vcs-Git

 -- Dan Streetman   Thu, 04 Apr 2019 07:29:38
-0400

** Changed in: systemd (Ubuntu Cosmic)
   Status: Fix Committed => 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/1812760

Title:
  networkd: [Route] PreferredSource not working in *.network files

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Users cannot create IPv6 routes that specify PreferredSource. This
  means that users cannot specify a number of valid IPv6 routes that are
  useful in some circumstances. These routes can be created with the
  'ip' tool, just not with systemd.

  This was reported upstream in systemd issue #5882 is fixed by pulling
  in the changes in systemd PR #11375 -
  https://github.com/systemd/systemd/pull/11375

  [Test Case]

  Start a Bionic or Cosmic VM.

  Add the following netplan yaml (adjust for ethernet card and MAC):

  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:e2:c2:d7
  set-name: ens3
  addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"]
  routes:
    - to: "a::/16"
  via: "fd8f:1d7d:b141::1"
  from: "fd8f:1d7d:b141::2"
    - to: "fd8f:1d7d:b141::/64"
  scope: link
  from: "fd8f:1d7d:b141::2"
  metric: 255

  Run netplan apply or reboot. Wait ~10s.

  Alternately, to test without netplan, configure systemd-networkd with:

  [Match]
  Name=ens3

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  Address=fd8f:1d7d:b141::2/64
  Address=fd8f:1d7d:b141::200/64

  [Route]
  Destination=a::/16
  Gateway=fd8f:1d7d:b141::1
  PreferredSource=fd8f:1d7d:b141::2

  [Route]
  Destination=fd8f:1d7d:b141::/64
  PreferredSource=fd8f:1d7d:b141::2
  Scope=link
  Metric=255

  [DHCP]
  UseMTU=true
  RouteMetric=100


  Currently, ip -6 route will not include a route to "a::/16", and will
  not include the route to "fd8f:1d7d:b141::/64" that has
  "fd8f:1d7d:b141::2" as the source address - both those addresses will
  be missing.

  Correct behaviour is for ip -6 route to report the following:

  ubuntu@b-np:~$ ip -6 route
  a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 
metric 1024 pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 
pref medium
  fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium
  fe80::/64 dev ens3 proto kernel metric 256 pref medium

  Check before and after upgrade that 'systemctl status network-
  online.target' shows that the target has been reached.

  [Regression Potential]

  This changes the state machine in systemd which configures the links.
  It passes systemd's internal tests, and has been approved by systemd
  maintainers, but it remains possible that the changes will break the
  configuration of obscure network setups.

  The backport requires pulling in two further commits that also change
  behaviour: currently systemd deletes all addresses and routes that
  were attached to an interface. With this change, it will only delete
  those that are not specified in the configuration files. A side effect
  of this is that restarting networkd will not cause remove/add netlink
  events to be emitted for these addresses, so if anyone is relying on
  this behavior this will break compatibility; but that is an unlikely
  thing to be relying on, and it seems worth this risk to reduce
  unnecessary network state changes.

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

-- 
Mailing list: https://la

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

In Cosmic /lib/systemd/system/apparmor.service pointed to "/etc/init.d/apparmor 
start"
This had some code, but it was not triggered:
if [ -x /usr/bin/systemd-detect-virt ] && \
   systemd-detect-virt --quiet --container && \
   ! is_container_with_internal_policy; then
log_daemon_msg "Not starting AppArmor in container"
log_end_msg 0
exit 0

The interesting bit here is /lib/apparmor/functions with the function
is_container_with_internal_policy

That essentially detected stacked namespaces in LXD and made it continue
to work.

In Disco this now uses /lib/apparmor/apparmor.systemd instead.
I still calls is_container_with_internal_policy which now is only slightly 
different and stored in /lib/apparmor/rc.apparmor.functions

We need to track down why this now no more returns true ...

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

Title:
  apparmor no more starting in Disco LXD containers

Status in apparmor package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.

  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container

  I can get those profiles (the default installed ones) loaded, for example:
    $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
    22 profiles are in enforce mode.
     /sbin/dhclient

  I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
  will call apparmor_parser via the dh_apparmor snippet and it is fine.

  To fully disable all of them:
$ lxc stop 
$ lxc start 
$ lxc exec d-testapparmor aa-status
  apparmor module is loaded.
  0 profiles are loaded.
  0 profiles are in enforce mode.
  0 profiles are in complain mode.
  0 processes have profiles defined.
  0 processes are in enforce mode.
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  That would match the service doing an early exit as shown in systemctl
  status output above. The package install or manual load works, but
  none are loaded by the service automatically e.g. on container
  restart.

  --- --- ---

  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"

  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.

  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor

  I need to analyze what changed

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

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

[Touch-packages] [Bug 1824817] Re: CRTL+ALT+F7 bypasses the lock-screen with lightdm

2019-04-15 Thread Ted

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

** Summary changed:

- Security breach with CRTL+ALT+F7
+ CRTL+ALT+F7 bypasses the  lock-screen with lightdm

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

Title:
  CRTL+ALT+F7 bypasses the  lock-screen with lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem concerns every versions of Ubuntu 18 (Desktop or LTS) :

  When I lock my session with the padlock icon, I can open it with
  CRTL+ALT+F7 without password.

  This is the step to reproduce the problem:

  - Install Ubuntu 18 (Desktop or LTS) with the default option.
  The default windows manager is gnome

  - Install lightdm => the opening window logging will be replaced by
  the opening window logging of lightdm

  - Open a session

  - Lock the session with the padlock icon (in the right upper corner,
  click on the down arrow and click on the padlock icon)

  - The session seems lock because you can see the opening window
  logging wich asks you the password but press on CRTL+ALT+F7 and you
  can open the session without password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 15:26:04 2019
  InstallationDate: Installed on 2019-04-11 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

Since I started seeing this in libvirt There might be reasons that is done that 
way but this affects me and probably other use cases e.g. if I install libvirt:
  $ apt install libvirt-daemon-system
  $ aa-status | grep libvirt

On my test systems the containers do not get any profile loaded:
$ aa-status 
apparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

When testing a new disco container on my laptop they at least have only
less profiles, but some profiles work. Odd at least.

** Description changed:

- In LXD apparmor now skips starting:
- Formerly:
- root@testkvm-bionic-from:~# systemctl status apparmor
- ● apparmor.service - AppArmor initialization
-Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
-Active: active (exited) since Mon 2019-04-15 13:09:07 UTC; 1h 8min ago
-  Docs: man:apparmor(7)
-http://wiki.apparmor.net/
-   Process: 90 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=0/SUCCESS)
-  Main PID: 90 (code=exited, status=0/SUCCESS)
+ In LXD apparmor now skips starting.
  
- Apr 15 13:09:07 testkvm-bionic-from systemd[1]: apparmor.service: Failed to 
reset devices.list: Operation not permitted
- Apr 15 13:09:07 testkvm-bionic-from systemd[1]: Starting AppArmor 
initialization...
- Apr 15 13:09:07 testkvm-bionic-from apparmor[90]:  * Starting AppArmor 
profiles
- Apr 15 13:09:07 testkvm-bionic-from apparmor[90]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
- Apr 15 13:09:07 testkvm-bionic-from apparmor[90]:...done.
- Apr 15 13:09:07 testkvm-bionic-from systemd[1]: Started AppArmor 
initialization.
+ Steps to reproduce:
+ 1. start LXD container
+   $ lxc launch ubuntu-daily:d d-testapparmor
+   (disco to trigger the issue, cosmic as reference)
+ 2. check the default profiles loaded
+   $ aa-status
  
+ => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
+ Cosmic: 
+   25 profiles are loaded.
+   25 profiles are in enforce mode.
+ Disco:
+   15 profiles are loaded.
+   15 profiles are in enforce mode.
  
- Now:
- root@testkvm-disco-to:~# systemctl status apparmor
- ● apparmor.service - Load AppArmor profiles
-Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
-Active: active (exited) since Mon 2019-04-15 13:56:12 UTC; 21min ago
-  Docs: man:apparmor(7)
-https://gitlab.com/apparmor/apparmor/wikis/home/
-   Process: 101 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, 
status=0/SUCCESS)
-  Main PID: 101 (code=exited, status=0/SUCCESS)
+ All those 15 remaining are from snaps.
+ The service of apparmor.service actually states that it refuses to start.
  
- Apr 15 13:56:12 testkvm-disco-to systemd[1]: Starting Load AppArmor 
profiles...
+ $ systemctl status apparmor
+ ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container
- Apr 15 13:56:12 testkvm-disco-to systemd[1]: Started Load AppArmor profiles.
  
+ Since some apparmor seems to work I need to debug it further why so many
+ are missing initially and why it affects me in libvirt.
  
- ---
+ --- --- ---
  
  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"
  
  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.
  
  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor
  
  I need to analyze what changed

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

Title:
  apparmor no more starting in Disco LXD containers

Status in apparmor package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  In LXD apparmor now skips starting.

  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status

  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.

  All those 15 r

[Touch-packages] [Bug 1824812] Re: apparmor no more starting in Disco LXD containers

In that container that has no profiles at all I can explicitly load them.
 $ sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.libvirtd
 $ systemctl restart libvirtd

makes it show up correctly
  1 processes are in enforce mode.
   /usr/sbin/libvirtd (1146)

But why is it missing in the first place ... ?

** Description changed:

  In LXD apparmor now skips starting.
  
  Steps to reproduce:
  1. start LXD container
-   $ lxc launch ubuntu-daily:d d-testapparmor
-   (disco to trigger the issue, cosmic as reference)
+   $ lxc launch ubuntu-daily:d d-testapparmor
+   (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
-   $ aa-status
+   $ aa-status
  
  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
- Cosmic: 
-   25 profiles are loaded.
-   25 profiles are in enforce mode.
+ Cosmic:
+   25 profiles are loaded.
+   25 profiles are in enforce mode.
  Disco:
-   15 profiles are loaded.
-   15 profiles are in enforce mode.
+   15 profiles are loaded.
+   15 profiles are in enforce mode.
  
  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.
  
  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container
  
- Since some apparmor seems to work I need to debug it further why so many
- are missing initially and why it affects me in libvirt.
+ I can get those profiles (the default installed ones) loaded, for example:
+   $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
+ makes it appear
+   22 profiles are in enforce mode.
+/sbin/dhclient
+ 
+ 
+ Since some apparmor seems to work I need to debug it further why so many are 
missing initially and why it affects me in libvirt.
  
  --- --- ---
  
  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"
  
  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have migrated to
  Disco's qemu 3.1 already which makes me doubts generic issues in qemu
  3.1 in general.
  
  The virt tests that run cross release work fine starting from X/B/C but all 
those chains fail at mirgating to Disco now with:
    $ lxc exec testkvm-cosmic-from -- virsh migrate --unsafe --live 
kvmguest-bionic-normal
    qemu+ssh://10.21.151.207/system
    error: unsupported configuration: Unable to find security driver for model 
apparmor
  
  I need to analyze what changed

** Description changed:

  In LXD apparmor now skips starting.
  
  Steps to reproduce:
  1. start LXD container
    $ lxc launch ubuntu-daily:d d-testapparmor
    (disco to trigger the issue, cosmic as reference)
  2. check the default profiles loaded
    $ aa-status
  
  => This will in cosmic and up to recently disco list plenty of profiles 
active even in the default install.
  Cosmic:
    25 profiles are loaded.
    25 profiles are in enforce mode.
  Disco:
    15 profiles are loaded.
    15 profiles are in enforce mode.
  
  All those 15 remaining are from snaps.
  The service of apparmor.service actually states that it refuses to start.
  
  $ systemctl status apparmor
  ...
  Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container
  
  I can get those profiles (the default installed ones) loaded, for example:
-   $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
+   $ sudo apparmor_parser -r /etc/apparmor.d/sbin.dhclient
  makes it appear
-   22 profiles are in enforce mode.
-/sbin/dhclient
+   22 profiles are in enforce mode.
+    /sbin/dhclient
  
+ I was wondering as in my case I found my guest with no (=0) profiles loaded. 
But as shown above after "apparmor_parser -r" and package install profiles 
seemed fine. Then the puzzle was solved, on package install they
+ will call apparmor_parser via the dh_apparmor snippet and it is fine.
  
- Since some apparmor seems to work I need to debug it further why so many are 
missing initially and why it affects me in libvirt.
+ To fully disable all of them:
+   $ lxc stop 
+   $ lxc start 
+   $ lxc exec d-testapparmor aa-status
+ apparmor module is loaded.
+ 0 profiles are loaded.
+ 0 profiles are in enforce mode.
+ 0 profiles are in complain mode.
+ 0 processes have profiles defined.
+ 0 processes are in enforce mode.
+ 0 processes are in complain mode.
+ 0 processes are unconfined but have a profile defined.
+ 
+ That would match the service doing an early exit as shown in systemctl
+ status output above. The package install or manual load works, but none
+ are loaded by the service automatically e.g. on container restart.
  
  --- --- ---
  
  This bug started as:
  Migrations to Disco trigger "Unable to find security driver for model 
apparmor"
  
  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I have mi

[Touch-packages] [Bug 1824817] Re: Security breach with CRTL+ALT+F7

2019-04-15 Thread Eduardo dos Santos Barretto

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

** This bug has been marked a duplicate of bug 1806961
   Lock can be circumvented by switching tty when using lightdm

** Information type changed from Private Security to Public Security

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

Title:
  Security breach with CRTL+ALT+F7

Status in lightdm package in Ubuntu:
  New

Bug description:
  This problem concerns every versions of Ubuntu 18 (Desktop or LTS) :

  When I lock my session with the padlock icon, I can open it with
  CRTL+ALT+F7 without password.

  This is the step to reproduce the problem:

  - Install Ubuntu 18 (Desktop or LTS) with the default option.
  The default windows manager is gnome

  - Install lightdm => the opening window logging will be replaced by
  the opening window logging of lightdm

  - Open a session

  - Lock the session with the padlock icon (in the right upper corner,
  click on the down arrow and click on the padlock icon)

  - The session seems lock because you can see the opening window
  logging wich asks you the password but press on CRTL+ALT+F7 and you
  can open the session without password.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: lightdm 1.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 15:26:04 2019
  InstallationDate: Installed on 2019-04-11 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

Thanks for the autopkgtest check! Looks good. For cosmic (and partially
bionic too), I will not be hinting the test failures that we think LP:
#182423 is responsible for. Since apparently those should go away with
the new snapd - if not, we'll at least know what's up.

Few others I will hint before releasing the package.

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

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1824822] [NEW] error msg on boot

2019-04-15 Thread Ramon Quinones

Public bug reported:

attempting to find tool and solution to error msg displayed when booting
ubuntu, nooby so attempting to climb learning mountain

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Mon Apr 15 10:25:36 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.18.0-15-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.18.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
InstallationDate: Installed on 2019-04-10 (4 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. Inspiron 5748
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=9f9f5ad2-dd34-43a3-81a0-8f0cb9dd6759 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0YYR61
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron5748:pvrNotSpecified:rvnDellInc.:rn0YYR61:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5748
dmi.product.sku: 0651
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  error msg on boot

Status in xorg package in Ubuntu:
  New

Bug description:
  attempting to find tool and solution to error msg displayed when
  booting ubuntu, nooby so attempting to climb learning mountain

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Apr 15 10:25:36 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.18.0-15-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.18.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-04-10 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. Inspiron 5748
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=9f9f5ad2-dd34-43a3-81a0-8f0cb9dd6759 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0YYR61
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron5748:pvrNotSpecified:rvnDellInc.:rn0YYR61:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5748
  dmi.product.sku: 0651
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-vide

[Touch-packages] [Bug 1824810] Re: use host uuid on kvm on power too

https://www.redhat.com/archives/libvir-list/2019-April/msg00987.html

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

Title:
  use host uuid on kvm on power too

Status in libvirt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  use host uuid on kvm on power too

  On power, the qemu uuid is exposed as
  /sys/firmware/devicetree/base/vm,uuid and should be used like
  /sys/class/dmi/id/product_uuid is used on x86.

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

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

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

2019-04-15 Thread Manoj Iyer

** Changed in: util-linux (Ubuntu)
 Assignee: Manoj Iyer (manjo) => Canonical Foundations Team 
(canonical-foundations)

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

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

Status in The Ubuntu-power-systems project:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress

Bug description:
  [IMPACT]

  In xenial lscpu prints the wrong "Hypervisor vendor" and
  "Virtualization type" on PowerVM or KVM systems. Incorrect hypervisor
  and virtualization type reported in ubuntu 16.04.04 guest running in
  P8compat mode on P9 boston-LC.

  [TEST]

  Curent output:

  ubuntu@P8lpar3:~$ dpkg -l "*util-linux*"
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  util-linux 2.31.1-0.4ub ppc64el  miscellaneous system utilities
  un  util-linux-loc   (no description available)

  ubuntu@P8lpar3:~$ lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  128
  On-line CPU(s) list: 0-127
  Thread(s) per core:  8
  Core(s) per socket:  1
  Socket(s):   16
  NUMA node(s):2
  Model:   2.1 (pvr 004b 0201)
  Model name:  POWER8 (architected), altivec supported
  Hypervisor vendor:   pHyp
  Virtualization type: para
  L1d cache:   64K
  L1i cache:   32K
  NUMA node0 CPU(s):   
  NUMA node4 CPU(s):   0-127
  ubuntu@P8lpar3:~$ 

  Expected Output:

  $ lscpu 
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):128
  On-line CPU(s) list:   0-127
  Thread(s) per core:8
  Core(s) per socket:1
  Socket(s): 16
  NUMA node(s):  2
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8 (architected), altivec supported
  Hypervisor vendor: pHyp
  Virtualization type:   para
  L1d cache: 64K
  L1i cache: 32K
  NUMA node0 CPU(s): 
  NUMA node4 CPU(s): 0-127

  [Potential Regression]
  The fix changes the logic to how lscpu-dmi returns from read_hypervisor_dmi() 
this could introduce potential regression in platforms  that has incorrect DMI 
information.

  [Other Info]
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = boston-LC

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

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

  Stack trace output:
   no

  Oops output:
   no

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

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

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

[Touch-packages] [Bug 1824812] Re: Migrations to Disco trigger "Unable to find security driver for model apparmor"

Apparmor is disabled in LXD containers now !?!
Compare aa-status after spawning a new container.

root@d-testapparmor:~# aa-status 
apparmor module is loaded.
15 profiles are loaded.
15 profiles are in enforce mode.
   /snap/core/6673/usr/lib/snapd/snap-confine
   /snap/core/6673/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   snap-update-ns.core
   snap-update-ns.lxd
   snap.core.hook.configure
   snap.lxd.activate
   snap.lxd.benchmark
   snap.lxd.buginfo
   snap.lxd.check-kernel
   snap.lxd.daemon
   snap.lxd.hook.configure
   snap.lxd.hook.install
   snap.lxd.lxc
   snap.lxd.lxd
   snap.lxd.migrate
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.


root@c-testapparmor:~# aa-status
apparmor module is loaded.
25 profiles are loaded.
25 profiles are in enforce mode.
   /sbin/dhclient
   /snap/core/6673/usr/lib/snapd/snap-confine
   /snap/core/6673/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /usr/bin/man
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/NetworkManager/nm-dhcp-helper
   /usr/lib/connman/scripts/dhclient-script
   /usr/lib/snapd/snap-confine
   /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
   /usr/sbin/tcpdump
   man_filter
   man_groff
   snap-update-ns.core
   snap-update-ns.lxd
   snap.core.hook.configure
   snap.lxd.activate
   snap.lxd.benchmark
   snap.lxd.buginfo
   snap.lxd.check-kernel
   snap.lxd.daemon  

  
   snap.lxd.hook.configure  

  
   snap.lxd.hook.install

  
   snap.lxd.lxc
   snap.lxd.lxd
   snap.lxd.migrate
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

That is confirmed by the service:
Apr 15 14:16:21 d-testapparmor systemd[1]: Starting Load AppArmor profiles...
Apr 15 14:16:21 d-testapparmor apparmor.systemd[101]: Not starting AppArmor in 
container
Apr 15 14:16:21 d-testapparmor systemd[1]: Started Load AppArmor profiles.

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

** Summary changed:

- Migrations to Disco trigger "Unable to find security driver for model 
apparmor"
+ apparmor no more starting in Disco LXD containers

** Description changed:

+ In LXD apparmor now skips starting:
+ Formerly:
+ root@testkvm-bionic-from:~# systemctl status apparmor
+ ● apparmor.service - AppArmor initialization
+Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
+Active: active (exited) since Mon 2019-04-15 13:09:07 UTC; 1h 8min ago
+  Docs: man:apparmor(7)
+http://wiki.apparmor.net/
+   Process: 90 ExecStart=/etc/init.d/apparmor start (code=exited, 
status=0/SUCCESS)
+  Main PID: 90 (code=exited, status=0/SUCCESS)
+ 
+ Apr 15 13:09:07 testkvm-bionic-from systemd[1]: apparmor.service: Failed to 
reset devices.list: Operation not permitted
+ Apr 15 13:09:07 testkvm-bionic-from systemd[1]: Starting AppArmor 
initialization...
+ Apr 15 13:09:07 testkvm-bionic-from apparmor[90]:  * Starting AppArmor 
profiles
+ Apr 15 13:09:07 testkvm-bionic-from apparmor[90]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
+ Apr 15 13:09:07 testkvm-bionic-from apparmor[90]:...done.
+ Apr 15 13:09:07 testkvm-bionic-from systemd[1]: Started AppArmor 
initialization.
+ 
+ 
+ Now:
+ root@testkvm-disco-to:~# systemctl status apparmor
+ ● apparmor.service - Load AppArmor profiles
+Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
+Active: active (exited) since Mon 2019-04-15 13:56:12 UTC; 21min ago
+  Docs: man:apparmor(7)
+https://gitlab.com/apparmor/apparmor/wikis/home/
+   Process: 101 ExecStart=/lib/apparmor/apparmor.systemd reload (code=exited, 
status=0/SUCCESS)
+  Main PID: 101 (code=exited, status=0/SUCCESS)
+ 
+ Apr 15 13:56:12 testkvm-disco-to systemd[1]: Starting Load AppArmor 
profiles...
+ Apr 15 13:56:12 testkvm-disco-to apparmor.systemd[101]: Not starting AppArmor 
in container
+ Apr 15 13:56:12 testkvm-disco-to systemd[1]: Started Load AppArmor profiles.
+ 
+ 
+ ---
+ 
+ This bug started as:
+ Migrations to Disco trigger "Unable to find security driver for model 
apparmor"
+ 
  This most likely is related to my KVM-in-LXD setup but it worked fine
  for years and I'd like to sort out what broke. I h

[Touch-packages] [Bug 1824810] Re: use host uuid on kvm on power too

https://github.com/systemd/systemd/pull/12321

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

Title:
  use host uuid on kvm on power too

Status in libvirt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  use host uuid on kvm on power too

  On power, the qemu uuid is exposed as
  /sys/firmware/devicetree/base/vm,uuid and should be used like
  /sys/class/dmi/id/product_uuid is used on x86.

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

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

[Touch-packages] [Bug 1824810] Re: use host uuid on kvm on power too

Ack. Also DPM mode has LPAR UUID we should be using.

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

Title:
  use host uuid on kvm on power too

Status in libvirt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  use host uuid on kvm on power too

  On power, the qemu uuid is exposed as
  /sys/firmware/devicetree/base/vm,uuid and should be used like
  /sys/class/dmi/id/product_uuid is used on x86.

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

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

[Touch-packages] [Bug 1824810] Re: use host uuid on kvm on power too

On s390x it only uses sysinfo for systemd-detect-virt,
  src/basic/virt.c:306:r = get_proc_field("/proc/sysinfo", "VM00 
Control Program", 
  WHITESPACE, &t);

but there also the Host UUID is exposed:
  $ cat /proc/sysinfo
  VM00 UUID:0804001f-c45f-4345-994f-9fec048e822e

There it also seems not used to (re-)generate a machine ID consistently:

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

Title:
  use host uuid on kvm on power too

Status in libvirt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  use host uuid on kvm on power too

  On power, the qemu uuid is exposed as
  /sys/firmware/devicetree/base/vm,uuid and should be used like
  /sys/class/dmi/id/product_uuid is used on x86.

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

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

[Touch-packages] [Bug 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages

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

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

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

Title:
  Unattended upgrades falls back to adjust all upgradable packages in
  attempt to install held packages

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  The fix for LP: #1821101 allowed installing packages for which APT's
  resolver could not find solution for without adjusting other packages,
  but also tries to adjust many packages to install packages which are
  held back.

  See:
  
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1396787/comments/21

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

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

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub") netplan mis-configuration ma

2019-04-15 Thread Derk Willem te Bokkel

bug is still present in disco xubuntu iso "final" 04-13.1-2019

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")
  netplan mis-configuration maybe underlying cause.

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/lightdm/+bug/1821609/+subscriptions

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

[Touch-packages] [Bug 1824678] Re: package libqt5svg5:amd64 5.11.1-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2019-04-15 Thread Eduardo dos Santos Barretto

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

** Information type changed from Private Security to Public

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

Title:
  package libqt5svg5:amd64 5.11.1-2 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

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

Bug description:
  i can't install applications

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libqt5svg5:amd64 5.11.1-2
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Sun Apr 14 11:07:50 2019
  DuplicateSignature:
   package:libqt5svg5:amd64:5.11.1-2
   Setting up libvlccore9:amd64 (3.0.4-2build1) ...
   dpkg: error processing package libqt5svg5:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2019-03-22 (22 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: qtsvg-opensource-src
  Title: package libqt5svg5:amd64 5.11.1-2 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1824678] Re: package libqt5svg5:amd64 5.11.1-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2019-04-15 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libqt5svg5:amd64 5.11.1-2 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

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

Bug description:
  i can't install applications

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libqt5svg5:amd64 5.11.1-2
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Sun Apr 14 11:07:50 2019
  DuplicateSignature:
   package:libqt5svg5:amd64:5.11.1-2
   Setting up libvlccore9:amd64 (3.0.4-2build1) ...
   dpkg: error processing package libqt5svg5:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2019-03-22 (22 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: qtsvg-opensource-src
  Title: package libqt5svg5:amd64 5.11.1-2 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1824810] [NEW] use host uuid on kvm on power too