[Bug 1877089] Re: zfcpdump kernel can not be IPLed when secure boot is requested

2020-09-23 Thread Dimitri John Ledkov
** Changed in: zfcpdump-kernel (Ubuntu)
   Status: Won't Fix => Confirmed

** Changed in: zfcpdump-kernel (Ubuntu Focal)
   Status: Won't Fix => Confirmed

** Changed in: zfcpdump-kernel (Ubuntu Groovy)
   Status: Won't Fix => Confirmed

** Summary changed:

- zfcpdump kernel can not be IPLed when secure boot is requested
+ zfcpdump kernel can not be IPLed, wrong file name

** Description changed:

  [Impact]
  
-  * zfcpdump-kernel incompatible with s390-tools in focal
-  * zfcpdump-kernel incompatible with SIPL (secure IPL)
+  * zfcpdump-kernel incompatible with s390-tools in focal, due to wrong file 
name
+  * zfcpdump-kernel incompatible with SIPL (secure IPL), and will not be fixed.
   * fix all that for focal and up
  
   * Upgrade to the v5.4 kernel
-  * Enable signing
+  * Signing will not be enabled
   * Update the path of the image, to the one that `zipl -d` in focal expects
  
  [Test Case]
  
   * Prepare sda1 drive for SCSI dump
   * Stop all processes from the HMC
   * Perform SCSI dump load from HMC
   * Observe that dump is successful and used v5.4 kernel from the Operating 
System Messages
-  * Perform regular
+  * Perform regular boot
   * Mount the dump, and observe it is there in full
  
   * Can be performed on the canonical z13 hmc without SIPL
-  * Will need IBM confirmation with SIPL, or further fixes
+  * zfcpdump with secureboot will not be possible
  
  [Publication]
  
-  * zfcpdump-kernel image is OS series independant, and thus can be build
+  * zfcpdump-kernel image is OS series independant, and thus can be build
  in focal with copies up to groovy.
  
  [Regression Potential]
  
   * The kernel image used for zfcpdump is fairly static, doesn't have
  loadable modules, but it does allow reading kernel memory which in
  theory is not in the same spirit as lockdown. However, stopping all
  processes and triggering scsi-dump is a priviledged HMC operation that
  is otheriwse has a much higher access restrictions than lockdown can
  provide.
  
  [Other Info]
  
   * Original bug report
  
  I installed Ubuntu 20.04 on IBM z15 with secure=1 in zipl conf.
  System can be secure booted, /sys/firmware/ipl/secure shows "1".
  I prepared zfcp dump disk as described in LTC bug 185713.
  Stopped the system and performed a SCSI dump with "Enable Secure Boot for 
Linux" enabled.
  
  Operating System Messages on HMC:
  Preparing system.
  Starting system.
  System version 8.
  Watchdog enabled.
  Running 'ZBootLoader' version '1.0.0' level 'D41C.D41C_0014'.
  ZBootLoader 2.1.0.
  MLOLOA6269064E Secure IPL: There are no signed components available on device 
HB
  A=0.0.1800, WWPN=500507630309D327, LUN=40464009.
  IPL failed.
  
  Without "Enable Secure Boot for Linux" the dump kernel was IPLed and a
  dump created.
  
  Then I tried to rewrite the zfcp dump kernel with explicite setting of 
--secure=1:
  root@t35lp25:~# zipl --secure=1 -d 
/dev/disk/by-id/scsi-36005076303ffd3274609-part1
  Building bootmap directly on partition 
'/dev/disk/by-id/scsi-36005076303ffd3274609-part1'
  Adding dump section
    initial ramdisk...: /lib/s390-tools/zfcpdump/zfcpdump-initrd
    kernel image..: /lib/s390-tools/zfcpdump/zfcpdump-image
    kernel parmline...: 'root=/dev/ram0 dump_mem=1 possible_cpus=1 
cgroup_disable=memory '
    component address:
  heap area...: 0x2000-0x5fff
  stack area..: 0xf000-0x
  internal loader.: 0xa000-0xdfff
  parameters..: 0x9000-0x91ff
  kernel image: 0x0001-0x001b9fff
  parmline: 0x001ba000-0x001ba1ff
  initial ramdisk.: 0x001c-0x0020edff
  Preparing boot device: sde.
  Done.
  
  ...and tried to SCSI dump this device again. But the same  failure occured.
  Again, without "Enable Secure Boot for Linux" the dump kernel was IPLed and a 
dump created.

** Description changed:

  [Impact]
  
-  * zfcpdump-kernel incompatible with s390-tools in focal, due to wrong file 
name
+  * zfcpdump-kernel incompatible with s390-tools in focal, due to wrong file 
name, needed in focal and up
   * zfcpdump-kernel incompatible with SIPL (secure IPL), and will not be fixed.
-  * fix all that for focal and up
  
   * Upgrade to the v5.4 kernel
   * Signing will not be enabled
   * Update the path of the image, to the one that `zipl -d` in focal expects
  
  [Test Case]
  
   * Prepare sda1 drive for SCSI dump
   * Stop all processes from the HMC
   * Perform SCSI dump load from HMC
   * Observe that dump is successful and used v5.4 kernel from the Operating 
System Messages
   * Perform regular boot
   * Mount the dump, and observe it is there in full
  
   * Can be performed on the canonical z13 hmc without SIPL
   * zfcpdump with secureboot will not be possible
  
  [Publication]
  
   * zfcpdump-kernel image is OS series independant, and thus can be build
  in focal with copies up to groovy.
  
  [Regression Potential]
  
   * The kernel image 

[Bug 1878640] Re: uc20 image on pi often cannot get ip addr via eth0 on first boot of run mode

2020-09-23 Thread Dimitri John Ledkov
** No longer affects: netplan.io (Ubuntu Groovy)

** No longer affects: netplan.io (Ubuntu)

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878640

Title:
  uc20 image on pi often cannot get ip addr via eth0 on first boot of
  run mode

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896755] Re: Backport snap-preseed work from groovy to focal

2020-09-23 Thread Dimitri John Ledkov
** Merge proposal linked:
   
https://code.launchpad.net/~xnox/livecd-rootfs/+git/livecd-rootfs/+merge/391196

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896755

Title:
  Backport snap-preseed work from groovy to focal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896755] [NEW] Backport snap-preseed work from groovy to focal

2020-09-23 Thread Dimitri John Ledkov
Public bug reported:

[Impact]

 * livecd-rootfs when building classic images with snaps preseeded
doesn't perform any first-boot tasks during image building. It means
fist boot is computationally intensive. In groovy, livecd-rootfs gained
ability to precompute snap seeding, apparmor profiles making first boot
snap seeding a lot faster. Backport the goodies.

[Test Case]

 * Perform stock build of ubuntu-cpc lxd or qcow cloud image

 * Boot and observe they complete boot, and perfrom snap seeding very
quickly (i.e. less than a couple of seconds)

[Regression Potential]

 * Images might fail to build, or be missbuilt. However, these changes
have been tested on groovy with the same snapd across all SKUs. Thus
only groovy-vs-focal incompatibilities may arise.

** Affects: livecd-rootfs (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: livecd-rootfs (Ubuntu Focal)
 Importance: Undecided
 Status: Confirmed

** Affects: livecd-rootfs (Ubuntu Groovy)
 Importance: Undecided
 Status: Fix Released

** Also affects: livecd-rootfs (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu Groovy)
   Status: New => Fix Released

** Changed in: livecd-rootfs (Ubuntu Focal)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896755

Title:
  Backport snap-preseed work from groovy to focal

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896638] Re: Path to swapfile doesn't use a static device path

2020-09-22 Thread Dimitri John Ledkov
although, our cloud images normally boot by-label, thus potentially we
should use the same LABEL= device, as specified in fstab of our cloud-
images.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896638

Title:
  Path to swapfile doesn't use a static device path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1896638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896638] Re: Path to swapfile doesn't use a static device path

2020-09-22 Thread Dimitri John Ledkov
i.e. ext4 /dev/disk/by-uuid/9958d086-4f20-4807-8976-58807a5bc7e0 or some
such, if it will be accepted by our initrd.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896638

Title:
  Path to swapfile doesn't use a static device path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1896638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896638] Re: Path to swapfile doesn't use a static device path

2020-09-22 Thread Dimitri John Ledkov
please use by-id with uuid path as listed in
https://wiki.ubuntu.com/FSTAB

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896638

Title:
  Path to swapfile doesn't use a static device path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1896638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895160] Re: Backport finalrd 6 to xenial and up

2020-09-22 Thread Dimitri John Ledkov
installed finalrd 6~ubuntu16.04.1 on xenial system

observed that running $ sudo finalrd, manually doesn't produce any
errors.

Observed that finalrd is used on shutdown too.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895160

Title:
  Backport finalrd 6 to xenial and up

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895160] Re: Backport finalrd 6 to xenial and up

2020-09-22 Thread Dimitri John Ledkov
Next up is building core snaps with these finalrd packages preinstalled.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895160

Title:
  Backport finalrd 6 to xenial and up

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896614] Re: Race condition when starting dbus services

2020-09-22 Thread Dimitri John Ledkov
restarting systemd-logind is not safe, as existing sessions can be
logged out.

also performing daemon-reload, mid-boot, also is not safe.

Can you explain the usecase and why these actions are performed
together, racing each other?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896614

Title:
  Race condition when starting dbus services

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876715] Re: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects

2020-09-22 Thread Dimitri John Ledkov
In unapproved queue, after dropping unsupported SIPL signing.
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text
=zfcpdump-kernel

** Description changed:

+ [Impact]
+ 
+  * Cannot perform ZFCP SCSI dump of LPAR instance
+ 
+ [Test Case]
+ 
+  * install zfcdump-kernel package
+ 
+  * Prepare zfcp dump with zipl -d
+ 
+  * Use HMC to stop all processors and perform SCSI dump
+ 
+  * Boot normally, verify that kernel dump is readable from the SCSI dump
+ partition.
+ 
+ [Regression Potential]
+ 
+  * This update corrects the name of the kernel image, but also bumps the
+ zfcpdump kernel sources to v5.4 to match focal. Currently zfcpdump is
+ unusable in focal. Bringing the kernel config to v5.4 may expose config
+ changes that behave differently. Please note this kernel is only used
+ when performing kernel dump and is not used for any regular operations.
+ 
+ [Other Info]
+  
+  * Original Bug report.
+ 
+ 
  Under Ubuntu 20.04 I wanted to prepare a SCSI dump disk:
  
  root@t35lp25:/~# apt install zfcpdump-kernel
  Reading package lists... Done
- Building dependency tree   
+ Building dependency tree
  Reading state information... Done
  The following NEW packages will be installed:
-   zfcpdump-kernel
+   zfcpdump-kernel
  0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
  Need to get 1655 kB of archives.
  After this operation, 1757 kB of additional disk space will be used.
  Get:1 http://de.ports.ubuntu.com/ubuntu-ports focal/universe s390x 
zfcpdump-kernel s390x 4.13-0ubuntu1 [1655 kB]
- Fetched 1655 kB in 1s (1803 kB/s) 
+ Fetched 1655 kB in 1s (1803 kB/s)
  Selecting previously unselected package zfcpdump-kernel.
  (Reading database ... 53866 files and directories currently installed.)
  Preparing to unpack .../zfcpdump-kernel_4.13-0ubuntu1_s390x.deb ...
  Unpacking zfcpdump-kernel (4.13-0ubuntu1) ...
  Setting up zfcpdump-kernel (4.13-0ubuntu1) ...
  root@t35lp25:/~# zipl -d 
/dev/disk/by-id/scsi-36005076303ffd3274609-part1
  Error: Need external file '/lib/s390-tools/zfcpdump/zfcpdump-image' for 
partition dump: No such file or directory
  root@t35lp25:~# ls /lib/s390-tools/zfcpdump/
  zfcpdump-initrd  zfcpdump_part.image
  root@t35lp25:~#
  
  As you can see, zipl expects "zfcpdump-image", but "zfcpdump_part.image" is 
available.
  with paramater -d, zipl does NOT accept -i to override the image name. Thus I 
renamed zfcpdump_part.image to zfcpdump-image:
  
  root@t35lp25:~# cd /lib/s390-tools/zfcpdump
  root@t35lp25:/lib/s390-tools/zfcpdump# mv zfcpdump_part.image zfcpdump-image
  root@t35lp25:/lib/s390-tools/zfcpdump# zipl -d 
/dev/disk/by-id/scsi-36005076303ffd3274609-part1
  Building bootmap directly on partition 
'/dev/disk/by-id/scsi-36005076303ffd3274609-part1'
  Adding dump section
-   initial ramdisk...: /lib/s390-tools/zfcpdump/zfcpdump-initrd
-   kernel image..: /lib/s390-tools/zfcpdump/zfcpdump-image
-   kernel parmline...: 'root=/dev/ram0 dump_mem=1 possible_cpus=1 
cgroup_disable=memory '
-   component address:
- heap area...: 0x2000-0x5fff
- stack area..: 0xf000-0x
- internal loader.: 0xa000-0xdfff
- parameters..: 0x9000-0x91ff
- kernel image: 0x0001-0x001b9fff
- parmline: 0x001ba000-0x001ba1ff
- initial ramdisk.: 0x001c-0x0020edff
+   initial ramdisk...: /lib/s390-tools/zfcpdump/zfcpdump-initrd
+   kernel image..: /lib/s390-tools/zfcpdump/zfcpdump-image
+   kernel parmline...: 'root=/dev/ram0 dump_mem=1 possible_cpus=1 
cgroup_disable=memory '
+   component address:
+ heap area...: 0x2000-0x5fff
+ stack area..: 0xf000-0x
+ internal loader.: 0xa000-0xdfff
+ parameters..: 0x9000-0x91ff
+ kernel image: 0x0001-0x001b9fff
+ parmline: 0x001ba000-0x001ba1ff
+ initial ramdisk.: 0x001c-0x0020edff
  Preparing boot device: sde.
  Done.
  root@t35lp25:/lib/s390-tools/zfcpdump#
  
  ===
  Hi,
  
  zfcpdump_part.image got renamed to zfcpdump-image upstream with
  s390-tools v2.7.0. For me it looks like the old name is hard coded
  somewhere in the packaging/installation routines.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876715

Title:
  [UBUNTU 20.04] zfcpdump-kernel package has different name for
  dumpkernel image than zipl expects

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895160] Re: Backport finalrd 6 to xenial and up

2020-09-21 Thread Dimitri John Ledkov
installed finalrd 6~ubuntu20.04.1 on focal system

observed that running $ sudo finalrd, manually doesn't produce any
errors.

added extra hook with 6 second delay, and printing args. finalrd is
running and hook is executed on shutdown as observed on the serial
console.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895160

Title:
  Backport finalrd 6 to xenial and up

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895160] Re: Backport finalrd 6 to xenial and up

2020-09-21 Thread Dimitri John Ledkov
installed finalrd 6~ubuntu18.04.1 on bionic system.

observed that running $ sudo finalrd, manually doesn't produce any
errors.

added extra hook with 6 second delay, and printing args. It did show
that finalrd is running and printing things to the serial console on
reboot & shutdown.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895160

Title:
  Backport finalrd 6 to xenial and up

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890835] Re: secureboot-db 2020 update

2020-09-18 Thread Dimitri John Ledkov
Slow phasing is merged and deployed now.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890835

Title:
  secureboot-db 2020 update

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890835] Re: secureboot-db 2020 update

2020-09-18 Thread Dimitri John Ledkov
Booted 20.04.1 ISO, in a 4k ovmf qemu KVM VM with secureboot MS keys and
installed secureboot-db from focal-proposed, checking in journalctl that
dbxupdate from 1.6~20.04.1  got applied.

Shut down the VM.

Attempted to boot 20.04 BETA iso, and it failed to boot with
Verification failed Security Violation. Thus dbx update was correctly
applied and vulnerable OS can no longer boot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890835

Title:
  secureboot-db 2020 update

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890835] Re: secureboot-db 2020 update

2020-09-18 Thread Dimitri John Ledkov
Yes, ESM will be poked after other series release this.

** Tags removed: block-proposed-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890835

Title:
  secureboot-db 2020 update

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893653] Re: [20.10 FEAT] Algebra lib optimizations - OpenBlas (0.3.10) + enable DYNAMIC_ARCH=1

2020-09-17 Thread Dimitri John Ledkov
** Information type changed from Private to Public

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893653

Title:
  [20.10 FEAT] Algebra lib optimizations - OpenBlas (0.3.10) + enable
  DYNAMIC_ARCH=1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1863116] Re: debian/rules editconfigs does not work on s390x to change s390x only configs

2020-09-17 Thread Dimitri John Ledkov
** Changed in: linux (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863116

Title:
  debian/rules editconfigs does not work on s390x to change s390x only
  configs

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893216] Re: [20.10 FEAT] openCryptoki: PIN conversion tool -> addl req. patches

2020-09-17 Thread Dimitri John Ledkov
** Information type changed from Private to Public

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893216

Title:
  [20.10 FEAT] openCryptoki: PIN conversion tool -> addl req. patches

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895817] [NEW] [FFe] Dual-signed shim

2020-09-16 Thread Dimitri John Ledkov
Public bug reported:

[FFe] Dual-signed shim

shim-signed package currently ships two files

/usr/lib/shim/shimx64.efi.signed
/usr/lib/shim/shimx64.efi.dualsigned

The two shims are the same, but have different signatures.

.signed is signed with MS UEFI CA 2011 only

.dualsigned is signed with Canonical CA & MS UEFI CA 2011.

$ sbverify --list /usr/lib/shim/shimx64.efi.signed
warning: data remaining[1177936 vs 1341560]: gaps between PE/COFF sections?
signature 1
image signature issuers:
 - /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Corporation UEFI CA 2011
image signature certificates:
 - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Windows UEFI Driver Publisher
   issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Corporation UEFI CA 2011
 - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Corporation UEFI CA 2011
   issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Corporation Third Party Marketplace Root


$ sbverify --list /usr/lib/shim/shimx64.efi.dualsigned
warning: data remaining[1179856 vs 1343480]: gaps between PE/COFF sections?
signature 1
image signature issuers:
 - /C=GB/ST=Isle of Man/L=Douglas/O=Canonical Ltd./CN=Canonical Ltd. Master 
Certificate Authority
image signature certificates:
 - subject: /C=GB/ST=Isle of Man/O=Canonical Ltd./OU=Secure Boot/CN=Canonical 
Ltd. Secure Boot Signing (2017)
   issuer:  /C=GB/ST=Isle of Man/L=Douglas/O=Canonical Ltd./CN=Canonical Ltd. 
Master Certificate Authority
signature 2
image signature issuers:
 - /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Corporation UEFI CA 2011
image signature certificates:
 - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Windows UEFI Driver Publisher
   issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Corporation UEFI CA 2011
 - subject: /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Corporation UEFI CA 2011
   issuer:  /C=US/ST=Washington/L=Redmond/O=Microsoft Corporation/CN=Microsoft 
Corporation Third Party Marketplace Root

In light of the current Boothole vulnerabilities, it is desirable to
support a more constrained boot chain. Specifically, UEFI 2011 signed
Canonical shim can be booted universally on most hardware but also means
other shims from other vendors can boot too. But if we provide a shim
signed by Canonical CA, one can remove MS UEFI 2011 key from db, add
Canonical CA, and thus only boot shims provided by canonical. In such
scenario machine will only be able to boot Windows and Ubuntu, and no
other Linux. Furthermore Windows production key can be removed from db
as well, if one wishes to disable booting Windows too.

Certain hardware manufacturers ship Canonical CA key in db already. Thus
out-of-the-box shipping dual-signed shim would improve security there,
by reducing attack-vectors / having more constrained TPM measurements.

I am requesting FFe to ship dualsigned shim as
/usr/lib/shim/shimx64.efi.signed and use it by default.

Regression potential is as follows:

 - very old / initial implementations of Secureboot using very old UEFI
SB specs from 2008 do not support multiple signatures on .efi binary.
Thus this change, may result in certain older firmware unable to boot.
It is not clear with hardware doesn't support multiple signatures. And
whether or not the order of signatures helps at all (i.e. if MS
signature or Canonical one is first)

Mitigation strategy in case of regressions:

 - revert back to single-signed shim

** Affects: shim-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: block-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895817

Title:
  [FFe] Dual-signed shim

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891460] Re: Add riscv64 to cross-targets

2020-09-16 Thread Dimitri John Ledkov
Created cross-build chroot using sbuild, and crossbuilt hello
successfully producing hello_2.10-2ubuntu2_riscv64.deb

crossbuild-essential-riscv64 12.8ubuntu1.1 is installable too on amd64.


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891460

Title:
  Add riscv64 to cross-targets

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891460] Re: Add riscv64 to cross-targets

2020-09-16 Thread Dimitri John Ledkov
build-essential is a metapackage that doesn't change which compilers are
used, thus autopkgtest regressions identified, could not have been
caused by build-essential rebuild itself.

retried all of those tests.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891460

Title:
  Add riscv64 to cross-targets

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891460] Re: Add riscv64 to cross-targets

2020-09-16 Thread Dimitri John Ledkov
linux is in updates that have matching libc headers across all
architectures as needed for cross building linux 5.4.0-47.51

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891460

Title:
  Add riscv64 to cross-targets

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1799928] Re: [20.10 FEAT] openssl: RNG support

2020-09-15 Thread Dimitri John Ledkov
The patch mentioned alone does not apply on 1.1.1f in Ubuntu, it seems
it also needs

9cc834d966ea5afc38fb829bfe498aed4c5d498d
0d011f540400b425aba1c3e59624ad9dbabe83cb
a1ec85c169a8e53e52ab35914ad47b5baea84070
53eb05bdf00d7237e3b12976c2ac38d68206eb13
e6a80cbad28ee748830815634917efe96948f2f3

Will try this set next.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799928

Title:
  [20.10 FEAT] openssl: RNG support

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895708] Re: Openssl should integrate with needrestart better

2020-09-15 Thread Dimitri John Ledkov
** Changed in: openssl (Ubuntu)
   Status: New => Triaged

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

** Changed in: openssl (Ubuntu)
   Importance: Low => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895708

Title:
  Openssl should integrate with needrestart better

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895708] [NEW] Openssl should integrate with needrestart better

2020-09-15 Thread Dimitri John Ledkov
Public bug reported:

[Impact]

 * needrestart is a better solution to track and restart services that use 
openssl
 * when needrestart is available, openssl should not ask about restarting 
services or rebooting the host, as needrestart is a better way to report that.

[Test Case]

 * Install needrestart
 * Upgrade openssl
 * Observe that openssl debconf questions about restarting services are not 
raised, and requirement to reboot the system is not raised

[Regression Potential]

 * Needrestart may be installed, but dpkg/apt hooks could have been
disabled, in such scenarios one may not see any notifications that one
needs to do something to their system to ensure that openssl using
applications are restarted to become protected.

[Other Info]
 
 * glibc, libpam potentially need similar fixes.

** Affects: openssl (Ubuntu)
 Importance: Wishlist
 Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895708

Title:
  Openssl should integrate with needrestart better

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1799928] Re: [20.10 FEAT] openssl: RNG support

2020-09-15 Thread Dimitri John Ledkov
** Information type changed from Private to Public

** Changed in: openssl (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: ubuntu-z-systems
   Status: Expired => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799928

Title:
  [20.10 FEAT] openssl: RNG support

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884147] Re: package libssl1.1 1.1.1f-1ubuntu2 [modified: usr/share/doc/libssl1.1/NEWS.Debian.gz usr/share/doc/libssl1.1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared

2020-09-15 Thread Dimitri John Ledkov
a legacy app most likely will not be using libssl1.1 but the older
libssl1.0.0 which is no longer provided in ubuntu.

you need to create a chroot or a VM, or manually enable old series to
download old libssl1.0 which may still be available for i386.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884147

Title:
  package libssl1.1 1.1.1f-1ubuntu2 [modified:
  usr/share/doc/libssl1.1/NEWS.Debian.gz
  usr/share/doc/libssl1.1/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libssl1.1/NEWS.Debian.gz', which is different from
  other instances of package libssl1.1:i386

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879826] Re: User interface error when executing openssl from a daemon

2020-09-15 Thread Dimitri John Ledkov
** Changed in: openssl (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879826

Title:
  User interface error when executing openssl from a daemon

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878519] Re: Unable to use TLSv1.1 to connect to external servers

2020-09-15 Thread Dimitri John Ledkov
Instructions on how to make your system insecure and easy to hack are
here https://discourse.ubuntu.com/t/default-to-tls-v1-2-in-all-tls-
libraries-in-20-04-lts/12464/8?u=xnox

** Changed in: openssl (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878519

Title:
  Unable to use TLSv1.1 to connect to external servers

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876790] Re: cannot connect to the mail server

2020-09-15 Thread Dimitri John Ledkov
Please use https://www.orange.sk/napiste-nam/internetove-sluzby
/vseobecne-informacie-o-internetovych-sluzbach-a-ich-dostupnosti with
your mobile phone number requesting orange to add support for TLSv1.2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876790

Title:
  cannot connect to the mail server

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893264] Re: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.6 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 128

2020-09-15 Thread Dimitri John Ledkov
Please attempt to reinstall / upgrade the package again.

I.e. $ sudo dpkg --configure -a

or

$ sudo apt install --reinstall libssl1.1

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893264

Title:
  package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.6 failed to
  install/upgrade: installed libssl1.1:amd64 package post-installation
  script subprocess returned error exit status 128

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888101] Re: 'unsupported protocol' error when using PyMySQL

2020-09-15 Thread Dimitri John Ledkov
If you require using obsolete, deprecated, old protocols, with weak
keys, and broken hash algorithms you can use these instructions to
downgrade security on your systems https://discourse.ubuntu.com/t
/default-to-tls-v1-2-in-all-tls-libraries-in-20-04-lts/12464/8?u=xnox

** Changed in: openssl (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888101

Title:
  'unsupported protocol' error when using PyMySQL

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876790] Re: cannot connect to the mail server

2020-09-15 Thread Dimitri John Ledkov
Hi,

After inspecting imap4.orangemail.sk host, it appears to only support
TLS1.0 and does not support TLS1.1 or TLS1.2 which have been release
more than 12 years ago and widely adopted. It only supports TLS1.0 which
has been deprecated this year and is no longer supported by default as
it is weak and insecure.

Please contact orangemail.sk requesting for them to support TLSv1.2.

The problem is with them, not Ubuntu. Ubuntu is trying to protect your
communication to be secure.

If you wish to downgrade security and allow broken cryptography you can
use the following documentation to allow connecting to said host in an
insecure manner that is easier to hack https://discourse.ubuntu.com/t
/default-to-tls-v1-2-in-all-tls-libraries-in-20-04-lts/12464/8?u=xnox

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876790

Title:
  cannot connect to the mail server

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875781] Re: Unable to verify self signed certificate

2020-09-15 Thread Dimitri John Ledkov
The patch to address this is rather large, and doesn't quite apply
cleanly to 1.1.1f that we currently ship.

Also there is a workaround for this - just generate a better / different
self-signed cert which is identified as such by openssl.

But I do understand that doing that may be very inconvenient as well.

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875781

Title:
  Unable to verify self signed certificate

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

2020-09-15 Thread Dimitri John Ledkov
I'm not quite sure about the attempts written in the description of the
bug, as they do not look like correct instructions to downgrade openssl
to Seclevel 0.

If you are looking for instuctions on how to make your systems insecure
and allow using weak keys, broken certificates and obsolete protocol
versions you can use these instructions for OpenSSL and GnuTLS on per-
app or system-wide basis https://discourse.ubuntu.com/t/default-to-
tls-v1-2-in-all-tls-libraries-in-20-04-lts/12464/8?u=xnox

However, I advise you to rotate / upgrade your certificates to use
widely available and accepted hash-algos, key sizes, protocol versions
indead.

I will close this bug as invalid.

** Changed in: openssl (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866611

Title:
  OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866611] Re: OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

2020-09-15 Thread Dimitri John Ledkov
The status of this bug is invalid, because we will not downgrade default
security level to the one that allows broken crypto to be used by
default. And instructions on how to self-compromise systems are
available and are currently known to work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866611

Title:
  OpenVPN w. SHA1 signed CA broken after upgrade to 1.1.1d-2ubuntu6

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895294] Re: Fix Raccoon vulnerability (CVE-2020-1968)

2020-09-15 Thread Dimitri John Ledkov
It is true that said vulnerability is not patched in xenial; but also it
is low; and no public patches for it exist.

Please upgrade to bionic or focal? which are unaffected / fixes
released?

** Information type changed from Public to Public Security

** Also affects: openssl (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895294

Title:
  Fix Raccoon vulnerability (CVE-2020-1968)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895358] Re: [Bug] A simple code including tgmath.h cannot be compiled with icc with Ubuntu 20.04 OS

2020-09-15 Thread Dimitri John Ledkov
groovy-proposed has 2.32
https://launchpad.net/ubuntu/+source/glibc/2.32-0ubuntu2 can this issue
be reproduced there?

Do you have glibc upstream commit id on master and/or stable branches
with fix for this?

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895358

Title:
  [Bug] A simple code including tgmath.h cannot be compiled with icc
  with Ubuntu 20.04 OS

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1839592] Re: Open vSwitch (Version 2.9.2) goes into deadlocked state

2020-09-15 Thread Dimitri John Ledkov
is this duplicate of
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1864864 ?

does new glibc from bionic-proposed
https://launchpad.net/ubuntu/+source/glibc/2.27-3ubuntu1.3 help?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839592

Title:
  Open vSwitch (Version 2.9.2) goes into deadlocked state

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst

2020-09-15 Thread Dimitri John Ledkov
Installed from 18.04.4 media, in bios mode.

Added and loaded apparmor profile.

Enabled focal, focal-updates, focal-proposed archives.

Exported DEBIAN_FRONTEND=noniteractive to ensure non-interactive
updates.

Started upgrade of grub-pc grub-pc-bin grub2-common grub-common.

Configuration of grub-pc 2.04-1.ubuntu26.4 failed (GOOD) iF state

in /boot/grub git diff shows only one change => fonts/unicode.pf2 has
changed. (not ideal, but nothing else important has changed, i.e. all
modules are the same and modinfo.sh still says 2.02-2ubuntu8.18 as the
package version) (GOOD)

executed
echo grub-pc grub-pc/install_devices multiselect /dev/sda | 
debconf-set-selections
to set install_devices to invalid /dev/sda, instead of the correct /dev/vda for 
the next test case. And removed the apparmor profile.

Reboot. Still worked (good)

exported DEBIAN_FRONTEND=noninteractive, and attempted to configure all
the packages with dpkg --configure -a

configuration/installing onto /dev/sda failed (GOOD). No further changes
in /boot (GOOD). Reboot works. (GOOD)

Finally performing dpkg --configure -a worked, got asked which drive to
update, elected the correct /dev/vda and all modules got updated in the
/boot/grub dir. Reboot works. (GOOD)

Just to be sure, executed dpkg-reconfigure grub-pc and all questions got
asked and grub got installed onto /dev/vda again. (GOOD)



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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680

Title:
  grub-pc needs to detect when debconf points to invalid drive and stop
  in preinst, before unpacking files, and also treat this as a failure
  in postinst

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892526] Re: dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices

2020-09-15 Thread Dimitri John Ledkov
** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892526

Title:
  dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894824] Re: compare grub efi during build

2020-09-15 Thread Dimitri John Ledkov
I've triggered many successful builds, where grub2 deb & signing
artefacts matched, and thus build succeeded.

To produce the race of missmatched grub2 deb & signing artefacts I did
the following:

1) edit-acl on a ppa release pocket and self grant admin rights to myself
2) copy .deb from focal-proposed into said ppa
3) whilst signing tarball is still in Accepted queue, use queue tool with '-e' 
option to filter and reject signing tarball.

This resulted in a PPA that has the latest .deb, but will never have
matching signing.

4) copy source-only grub2-signed into said PPA

Expecting a failure to build from source, as the archive that had the
candidate deb, did not have matching signing.

make[1]: Entering directory '/<>'
cmp current/grubx64.efi /usr/lib/grub/x86_64-efi/monolithic/grubx64.efi
current/grubx64.efi /usr/lib/grub/x86_64-efi/monolithic/grubx64.efi differ: 
byte 162, line 2
make[1]: *** [Makefile:27: check] Error 1

And it failed correctly.

Successful builds are visibile in the Ubuntu Archive proposed it self.
Thus the build-time check now works correctly.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894824

Title:
  compare grub efi during build

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895480] Re: slrn cannot connect when using SSL encrypted connections

2020-09-14 Thread Dimitri John Ledkov
Both GnuTLS and OpenSSL can connect to said server without slrn in the
way.

openssl s_client -connect secure-us.news.easynews.com:8000
CONNECTED(0003)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = news.easynews.com
verify return:1
---
Certificate chain
 0 s:CN = news.easynews.com
   i:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
 1 s:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
   i:O = Digital Signature Trust Co., CN = DST Root CA X3
---
Server certificate
-BEGIN CERTIFICATE-
MIIKCzCCCPOgAwIBAgISAxh2BKBc4Tk6oSjofm6Fe9QuMA0GCSqGSIb3DQEBCwUA
MEoxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MSMwIQYDVQQD
ExpMZXQncyBFbmNyeXB0IEF1dGhvcml0eSBYMzAeFw0yMDA3MTIyMTAwNTJaFw0y
MDEwMTAyMTAwNTJaMBwxGjAYBgNVBAMTEW5ld3MuZWFzeW5ld3MuY29tMIICIjAN
BgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAs88/6aBieUZLdZPChQdMZxMHaa3v
IOg7gLB+VQp3R2NS74SVx4bKQm5h5qpAqDiFAl4w4rHW+7Z2Gb1+gVFaYkZPbhEp
HfKlsDTv54OE0FlrPDjWFCSOx0qTgCQ5wkxPAb8JLhzS+OACn/xNk10/B1vp/PVO
yAcdRRzJzHE7WLMRW5+rvswSHSyFM5PUk6DiOoiWoGtkmIX7os4XwGlSWerOkldn
2zunKSLEYR5Ju+xgPoLtlWWvVqttNS7rHRaMmNe0jD/2fgRd1xn1aYX7+6ZskjHx
ERxhgo+qvgxm4m1H6DwWlxq8G9XazHa9McHhpMMblB8mOWGmF4/Z2RVTUzzEQxeM
hB9wdwiUB6oo68iQ7aRjwl6DSbB+0mjlZwXwjn5xHnFoTaBbU9/E8q1yQN0NxwCl
8MDAzRaG3sDfYZlF8IA6b7cpbwcbw9qJr7GkqkuTenO1+kMQntIT9L8VZXz7UnvD
riI0Vmw92fgeE5piDJfoXJNPIloZrMNFKuCFdvlL1jpYMw3xKB+F3En8zWL/p7fR
/JykeRae2ZmfWw9gWswkNZNQZGbswzy7PXTDsUb84akXiSyjbnYvMlQ8uSiieDIw
HEZk2RcXsgx1leqh4asC9ZK3Uv6cFJ9ABOx6ilVvEe41LK5oLVA62mFE3Jk2oMrn
tHtgNHW7tggs0N8CAwEAAaOCBhcwggYTMA4GA1UdDwEB/wQEAwIFoDAdBgNVHSUE
FjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwDAYDVR0TAQH/BAIwADAdBgNVHQ4EFgQU
ZTSV6YW26AYulK4/fn+NORmBeXcwHwYDVR0jBBgwFoAUqEpqYwR93brm0Tm3pkVl
7/Oo7KEwbwYIKwYBBQUHAQEEYzBhMC4GCCsGAQUFBzABhiJodHRwOi8vb2NzcC5p
bnQteDMubGV0c2VuY3J5cHQub3JnMC8GCCsGAQUFBzAChiNodHRwOi8vY2VydC5p
bnQteDMubGV0c2VuY3J5cHQub3JnLzCCA8oGA1UdEQSCA8EwggO9ghliZXRhLWV1
Lm5ld3MuZWFzeW5ld3MuY29tghliZXRhLXVzLm5ld3MuZWFzeW5ld3MuY29tghZi
ZXRhLm5ld3MuZWFzeW5ld3MuY29tghFuZXdzLmVhc3luZXdzLmNvbYIUbmV3cy5l
dS5lYXN5bmV3cy5jb22CFG5ld3MudXMuZWFzeW5ld3MuY29tghJuZXdzNC5lYXN5
bmV3cy5jb22CEm5ld3M2LmVhc3luZXdzLmNvbYIVbmV3czYuZXUuZWFzeW5ld3Mu
Y29tghVuZXdzNi51cy5lYXN5bmV3cy5jb22CF3Byb3h5Lm5ld3MuZWFzeW5ld3Mu
Y29tgiBzZWN1cmUtYmV0YS1ldS5uZXdzLmVhc3luZXdzLmNvbYIgc2VjdXJlLWJl
dGEtdXMubmV3cy5lYXN5bmV3cy5jb22CHXNlY3VyZS1iZXRhLm5ld3MuZWFzeW5l
d3MuY29tghtzZWN1cmUtZXUubmV3cy5lYXN5bmV3cy5jb22CG3NlY3VyZS11cy5u
ZXdzLmVhc3luZXdzLmNvbYIYc2VjdXJlLm5ld3MuZWFzeW5ld3MuY29tghtzZWN1
cmUubmV3cy5ldS5lYXN5bmV3cy5jb22CGXNlY3VyZTYubmV3cy5lYXN5bmV3cy5j
b22CHHNlY3VyZTYubmV3cy5ldS5lYXN5bmV3cy5jb22CHHNlY3VyZTYubmV3cy51
cy5lYXN5bmV3cy5jb22CHnRlc3QtZXUtaXB2NC5uZXdzLmVhc3luZXdzLmNvbYIe
dGVzdC1ldS1pcHY2Lm5ld3MuZWFzeW5ld3MuY29tghl0ZXN0LWV1Lm5ld3MuZWFz
eW5ld3MuY29tgiV0ZXN0LXNlY3VyZS1ldS1pcHY0Lm5ld3MuZWFzeW5ld3MuY29t
giV0ZXN0LXNlY3VyZS1ldS1pcHY2Lm5ld3MuZWFzeW5ld3MuY29tgiB0ZXN0LXNl
Y3VyZS1ldS5uZXdzLmVhc3luZXdzLmNvbYIldGVzdC1zZWN1cmUtdXMtaXB2NC5u
ZXdzLmVhc3luZXdzLmNvbYIldGVzdC1zZWN1cmUtdXMtaXB2Ni5uZXdzLmVhc3lu
ZXdzLmNvbYIgdGVzdC1zZWN1cmUtdXMubmV3cy5lYXN5bmV3cy5jb22CHnRlc3Qt
dXMtaXB2NC5uZXdzLmVhc3luZXdzLmNvbYIedGVzdC11cy1pcHY2Lm5ld3MuZWFz
eW5ld3MuY29tghl0ZXN0LXVzLm5ld3MuZWFzeW5ld3MuY29tMEwGA1UdIARFMEMw
CAYGZ4EMAQIBMDcGCysGAQQBgt8TAQEBMCgwJgYIKwYBBQUHAgEWGmh0dHA6Ly9j
cHMubGV0c2VuY3J5cHQub3JnMIIBBQYKKwYBBAHWeQIEAgSB9gSB8wDxAHcA8JWk
WfIA0YJAEC0vk4iOrUv+HUfjmeHQNKawqKqOsnMAAAFzRQuQVQAABAMASDBGAiEA
w3DGIabSN4EcYRJ+nzGiM5NOFfh9opOEk4UqvEOm9lsCIQCPFqdm9b9vz2S5yTrm
pDyjV5GVPuVNtRyOOIAyt8bhdQB2ALIeBcyLos2KIE6HZvkruYolIGdr2vpw57JJ
Uy3vi5BeAAABc0ULkF0AAAQDAEcwRQIgWL/q4XKIiMrnLDrapzRG847zxcuQAe1X
rmeoirve0CUCIQDCNTvrr0WQnBODsblBzfWYBpP11ub5ZmD8qEBUIYrspzANBgkq
hkiG9w0BAQsFAAOCAQEAOR9oQmQtIHbxQ8CzgdW/eaoVw1MwwZY7fZpSiud713kL
m3OIizT4F2PEfj/Afl9Orttvid9scPa6xixgexU2J/ufcoY6Ak84G+orsh4alqgQ
VFDeS3w+mh+ZmSHyCl9VzBt4VWD6bp0z8MlCxaMexPMrxIjuXuarS76B5KTidmft
vzMzttw1qJ1OEf+qkwQ9ekFQfZQT1zcM2gFxW2zJ8M9CJkWu+PnS8myCrCNTI8FD
UzgU6zP0CUzHx3pHj16IV7cJ80JEHfUeC7OuetKUwPQvRT/0y48NvJWd/3BjHRjn
Z/TrNGYB4JO2un/hAzmTwIgpelhf8URrHv9RW963dA==
-END CERTIFICATE-
subject=CN = news.easynews.com

issuer=C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3

---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 4570 bytes and written 399 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 4096 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
Protocol  : TLSv1.3
Cipher: TLS_AES_256_GCM_SHA384
Session-ID: A16868D9ABC7C67BF06FC492F76A3BEA6E4AEC58C9E3A1A18056081DDD5651BA
Session-ID-ctx: 
Resumption PSK: 

[Bug 1879012] Re: GRUB does not bring up networking when loaded over HTTP

2020-09-10 Thread Dimitri John Ledkov
nevermind, uuid is the one from dhcp client-id obviously as implemented
/ referenced in my earlier comment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012

Title:
  GRUB does not bring up networking when loaded over HTTP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879012] Re: GRUB does not bring up networking when loaded over HTTP

2020-09-10 Thread Dimitri John Ledkov
"MAAS could also respond to /grub/grub.cfg-$uuid as we have that
information as well"

In that sentence which $uuid do you mean? UUID of the machine? Something
grub can query from smbios?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879012

Title:
  GRUB does not bring up networking when loaded over HTTP

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1862171] Re: [SRU] shim 15+1552672080.a4a1fbe-0ubuntu2

2020-09-10 Thread Dimitri John Ledkov
-device e1000,netdev=n1,bootindex=1

adding ',bootindex=1' causes the netboot to actually be used by default.

And for automating the test, it would be nice to boot to echo a message
and shutdown, such that one can capture console log to verify if the
boot was as expected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862171

Title:
  [SRU] shim 15+1552672080.a4a1fbe-0ubuntu2

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895200] Re: [MIR] microcode-initrd

2020-09-10 Thread Dimitri John Ledkov
https://lists.ubuntu.com/archives/kernel-team/2020-September/113356.html

** Package changed: linux-aws (Ubuntu) => linux-meta-aws (Ubuntu)

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895200

Title:
  [MIR] microcode-initrd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895200] [NEW] [MIR] microcode-initrd

2020-09-10 Thread Dimitri John Ledkov
Public bug reported:

[Availability]

 * Groovy Universe

[Rationale]

 * Needed to apply microcode updates, on bare-metal public-cloud
machines, that otherwise boot without a full initrd.

[Security]

 * This package is tiny, just a single small shell script trigger hook
that create microcode-initrd from intel-microcode and amd-microcode
packages.

[Quality assurance]

 * Installing this package automatically integrates with grub2 thus this
package needs no configuration to start using.

 * There are no debconf questions

 * Package is new, unique to Ubuntu

[Dependencies]

 * All dependencies are in main

[Standards compliance]

 * Complies with policy

[Maintenance]

 * Foundations-bugs subscribed

[Background information]

 * Currently we have a few public-clouds with bare-metal instance types
that boot without initrd. To apply microcode updates as required to
mitigate Spectre, Meldown, MDS attacks, a microcode-only initrd needs to
be loaded by grub, as late-loading of microcode is not safe. This
package was tested successfully on multiple instance types to ensure
correct operation.

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: microcode-initrd (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Changed in: microcode-initrd (Ubuntu)
   Status: New => Confirmed

** Description changed:

  [Availability]
  
-  * Focal Universe
+  * Groovy Universe
  
  [Rationale]
  
-  * Needed to apply microcode updates, on bare-metal public-cloud
+  * Needed to apply microcode updates, on bare-metal public-cloud
  machines, that otherwise boot without a full initrd.
  
  [Security]
  
-  * This package is tiny, just a single small shell script trigger hook
+  * This package is tiny, just a single small shell script trigger hook
  that create microcode-initrd from intel-microcode and amd-microcode
  packages.
  
  [Quality assurance]
  
-  * Installing this package automatically integrates with grub2 thus this
+  * Installing this package automatically integrates with grub2 thus this
  package needs no configuration to start using.
  
-  * There are no debconf questions
+  * There are no debconf questions
  
-  * Package is new, unique to Ubuntu
+  * Package is new, unique to Ubuntu
  
  [Dependencies]
  
-  * All dependencies are in main
+  * All dependencies are in main
  
  [Standards compliance]
  
-  * Complies with policy
+  * Complies with policy
  
  [Maintenance]
  
-  * Foundations-bugs subscribed
+  * Foundations-bugs subscribed
  
  [Background information]
  
-  * Currently we have a few public-clouds with bare-metal instance types
+  * Currently we have a few public-clouds with bare-metal instance types
  that boot without initrd. To apply microcode updates as required to
  mitigate Spectre, Meldown, MDS attacks, a microcode-only initrd needs to
  be loaded by grub, as late-loading of microcode is not safe. This
  package was tested successfully on multiple instance types to ensure
  correct operation.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895200

Title:
  [MIR] microcode-initrd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892086] Re: please remove syslinux-legacy from groovy

2020-09-10 Thread Dimitri John Ledkov
** Changed in: syslinux-legacy (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892086

Title:
  please remove syslinux-legacy from groovy

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894352] Re: bash-completion not working properly with directories with spaces in them when using some commands

2020-09-10 Thread Dimitri John Ledkov
Have you experienced this with upstream bash-completion?
https://github.com/scop/bash-completion

Could you submit your patch there? Cause this issue is not Ubuntu
specific, is it? And thus should be fixed for everyone?

** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894352

Title:
  bash-completion not working properly with directories with spaces in
  them when using some commands

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847191] Re: Selected experimental ZFS option and install in QEMU/KVM and crashed

2020-09-10 Thread Dimitri John Ledkov
** Changed in: ubiquity (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847191

Title:
  Selected experimental ZFS option and install in QEMU/KVM and crashed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2020-09-10 Thread Dimitri John Ledkov
Hm, so is desktop working on this? Have we figured out at all what is
happening? Or just the general symptoms that dbus seems to be non-
responsive and then everything goes bad?

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895160] [NEW] Backport finalrd 6 to xenial and up

2020-09-10 Thread Dimitri John Ledkov
Public bug reported:

[Impact]

 * finalrd is a useful tool, that improves ability to cleanly shut down
systems. It is now desired to backport it all the way back to xenial. On
classic systems it will not be installed by default, but available for
users to opt-in into having it. On Ubuntu Core systems it will be
installed by default, and used instead of snap-shutdown. As finalrd does
everything that snap-shutdown already did, and much more.

 * finalrd is only tweaked slightly in version 6 to be compatible with
any systemd from xenial to groovy.

[Test Case]

Classic
 * Install finalrd
 * execute `sudo finalrd` and observe that no stderr is printed, and command 
exits successfully
 * check that /run/initramfs is created and populated with 
/run/initramfs/shutdown, binaries and libraries.
 * Reboot
 * Observe that finalrd unit is started
 ** (optional) to make observing finalrd easier add /etc/finalrd/echo.finalrd 
hook that does `echo $@` with a sleep
 * Shutdown, capture console-log observe that finalrd was executed

Core
 * Create custom core, core18 with finalrd preinstalled
 * Building custom Ubuntu Core 16 and Ubuntu Core 18 image with above core
 * Observe that finalrd unit is started on boot
 * Shutdown, capture console-log observe that finarld was executed.
 * Boot again
 * execute `sudo finalrd` and observe that no stderr is printed, and command 
exits successfully
 * check that /run/initramfs is created and populated with 
/run/initramfs/shutdown, binaries and libraries.

[Regression Potential]

 * Packaging & tmpfiles were changed to be compatible with older systemd
versions. There are no changes to api/abi of the systemd units, or
.finalrd hooks. The package is not installed by default on
xenial/bionic, hence the number and type of machines affected is small.
If regressions are identified, reverting to previous version of the
package is safe course of action, as there are no upgrade/downgrade
incompatibilities between old & new versions of finalrd.

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

** Affects: finalrd (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: finalrd (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: finalrd (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Also affects: finalrd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: finalrd (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: finalrd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895160

Title:
  Backport finalrd 6 to xenial and up

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1862300] Re: "systemctl kexec" reboots

2020-09-10 Thread Dimitri John Ledkov
Yes, kexec-tools should ship finalrd hook to fix this.

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

** Changed in: kexec-tools (Ubuntu)
   Status: New => Triaged

** Changed in: kexec-tools (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862300

Title:
  "systemctl kexec" reboots

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust

2020-09-10 Thread Dimitri John Ledkov
So what is the order of boot?

(FW) -> grubnet -> shim (local) -> grub (local) ? I don't think that
would work, given that grubnet doesn't know how to validate shim,
without shim protocol installed.

I thought the chain must be (FW) -> shim -> grubnet -> shim (local) ->
grub (local). But I'm not sure how to netboot remote shim.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865515

Title:
  Chainbooting from grub over the network to local shim breaks chain of
  trust

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884566] Re: Please provide dual-signed shim chained to both MS & Canonical certificates

2020-09-10 Thread Dimitri John Ledkov
** Changed in: shim-signed (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884566

Title:
  Please provide dual-signed shim chained to both MS & Canonical
  certificates

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895144] [NEW] ubuntu-server CET gap analysis

2020-09-10 Thread Dimitri John Ledkov
Public bug reported:

* linux lacks CET, not upstream yet

* snapd lacks CET, as golang has no support for CET yet

* libunwind lacks CET, as no upstream support yet

* klibc lacks CET, no upstream support yet

** Affects: golang-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: golang-defaults (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895144

Title:
  ubuntu-server CET gap analysis

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-09-09 Thread Dimitri John Ledkov
On a bionic system, with atomics & libc6-lse installed, I observed that
whilst atomics libraries were present in the initrd, and libpthread.
libgcc_s was not at all.

$ lsinitramfs /boot/initrd.img-5.3.0-1034-aws  | grep atomics
lib/aarch64-linux-gnu/atomics
lib/aarch64-linux-gnu/atomics/libc.so.6
lib/aarch64-linux-gnu/atomics/libdl.so.2
lib/aarch64-linux-gnu/atomics/libc-2.27.so
lib/aarch64-linux-gnu/atomics/libm-2.27.so
lib/aarch64-linux-gnu/atomics/libpthread.so.0
lib/aarch64-linux-gnu/atomics/librt.so.1
lib/aarch64-linux-gnu/atomics/libpthread-2.27.so
lib/aarch64-linux-gnu/atomics/libdl-2.27.so
lib/aarch64-linux-gnu/atomics/librt-2.27.so
lib/aarch64-linux-gnu/atomics/libm.so.6

$ lsinitramfs /boot/initrd.img-5.3.0-1034-aws  | grep libgcc
$

Installed initramfs-tools (,-core,-bin) version 0.130ubuntu3.10, and now
libgcc_s is there

$ lsinitramfs /boot/initrd.img-5.3.0-1034-aws  | grep libgcc
lib/aarch64-linux-gnu/libgcc_s.so.1

as needed by libpthread-2.27.so.

Verification done.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880853

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895017] [NEW] openssl: backport TLSv1.3 compat fix

2020-09-09 Thread Dimitri John Ledkov
Public bug reported:

https://github.com/openssl/openssl/pull/9780/files breaks golang, so
would be useful to backport in bionic which ships openssl 1.1.1 now too.

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

** Affects: openssl (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Also affects: openssl (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895017

Title:
  openssl: backport TLSv1.3 compat fix

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892851] Re: Staged boot, to fix integration of systemd generators

2020-09-09 Thread Dimitri John Ledkov
I think it's best to keep cloud-init task as Invalid for now.

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892851

Title:
  Staged boot, to fix integration of systemd generators

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1892851/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894851] [NEW] RM seqan3 FTBFS with gcc 10

2020-09-08 Thread Dimitri John Ledkov
Public bug reported:

RM seqan3 FTBFS with gcc 10

removed from testing

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894851

Title:
  RM seqan3 FTBFS with gcc 10

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894850] [NEW] RM android-platform-art FTBFS on arm64, removed from debian testing

2020-09-08 Thread Dimitri John Ledkov
Public bug reported:

RM FTBFS on arm64, removed from debian testing

** Affects: android-platform-art (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: android-platform-art (Debian)
 Importance: Unknown
 Status: Unknown

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

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

** Summary changed:

- RM FTBFS on arm64, removed from debian testing
+ RM android-platform-art FTBFS on arm64, removed from debian testing

** Changed in: android-platform-art (Ubuntu)
   Status: New => Triaged

** Changed in: android-platform-art (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894850

Title:
  RM android-platform-art FTBFS on arm64, removed from debian testing

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1881468] Re: gnome-shell-xrdesktop/kwin-effect-xrdesktop FTBFS: universe package needs dependency from multiverse

2020-09-08 Thread Dimitri John Ledkov
** Changed in: kwin-effect-xrdesktop (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-shell-xrdesktop (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881468

Title:
  gnome-shell-xrdesktop/kwin-effect-xrdesktop FTBFS: universe package
  needs dependency from multiverse

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879494] Re: RM ancient obsolete version of mongodb

2020-09-08 Thread Dimitri John Ledkov
Updated two reverse-testsuite-triggers to skip if not installable, as
monogdb-server will be removed.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879494

Title:
  RM ancient obsolete version of mongodb

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-aodh/+bug/1879494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879494] Re: RM ancient obsolete version of mongodb

2020-09-08 Thread Dimitri John Ledkov
** Changed in: mongodb (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879494

Title:
  RM ancient obsolete version of mongodb

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-aodh/+bug/1879494/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894824] [NEW] compare grub efi during build

2020-09-08 Thread Dimitri John Ledkov
Public bug reported:

[Impact]

 * When resigning grub in a PPA, one can satisfy the build-depends from the 
main Ubuntu Archive, without PPA signature ready yet.
 * In such cases, grub2-signed is missbuilt with signature from an old PPA 
build attached to a newer binary, resulting in validation errors.
 * Add a check to ensure that signed grub & build-depends grub are the same

[Test Case]

 * Copy grub2 from -updates into PPA and await signing
 * Copy grub2-signed from Ubuntu Archive -proposed into PPA
 * Observe that grub2-signed FTBFS, instead of successfully producing 
uninstallable/unverifiable debs
 * Copy grub2 from -proposed into PPA, and await signing
 * Retry grub2-signed build, which should now succeed

[Regression Potential]

 * Only a build-time quickcheck is added, without any other changes of
how signed grub efi images are assembled.

[Other Info]
 
 * Previously this issue resulted in miss built UC20 grub copies

** Affects: grub2-signed (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: grub2-signed (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: grub2-signed (Ubuntu Groovy)
 Importance: Undecided
 Status: Fix Released

** Also affects: grub2-signed (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: grub2-signed (Ubuntu Groovy)
   Status: New => Incomplete

** Changed in: grub2-signed (Ubuntu Groovy)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894824

Title:
  compare grub efi during build

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894611] Re: kmod in bionic can't parse hwe/cloud kernel signatures

2020-09-08 Thread Dimitri John Ledkov
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894611

Title:
  kmod in bionic can't parse hwe/cloud kernel signatures

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892526] Re: dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices

2020-09-08 Thread Dimitri John Ledkov
** Changed in: grub2 (Ubuntu Focal)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892526

Title:
  dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst

2020-09-08 Thread Dimitri John Ledkov
** Changed in: grub2 (Ubuntu Focal)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680

Title:
  grub-pc needs to detect when debconf points to invalid drive and stop
  in preinst, before unpacking files, and also treat this as a failure
  in postinst

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD

2020-09-08 Thread Dimitri John Ledkov
So the history of this msdos/dasd partitioning table stuff in the old
installer were as follows:

LTC-135429 
https://bugs.launchpad.net/ubuntu/+source/partman-partitioning/+bug/1534629
LTC-136054 
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1527328
https://bugs.launchpad.net/ubuntu/+source/partman-partitioning/+bug/1537942
LTC-137464 
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1548411
LTC-149975 
https://bugs.launchpad.net/ubuntu/+source/partman-partitioning/+bug/1650300
https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1595495
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815916

partman-partitioning (110ubuntu3) xenial; urgency=medium

  * Set s390x partitioning tables (parted label type) to dasd. LP:
#1534629, LP: #1527328, LP: #1537942.

 -- Dimitri John Ledkov   Tue, 09 Feb 2016 19:32:43
+

partman-partitioning (110ubuntu4) xenial; urgency=medium

  [ Viktor Mihajlovski ]
  * Revert to using msdos partitioning table on s390x as a fallback,
however use dasd partitioning table if advised to do so by
partman. LP: #1548411

 -- Dimitri John Ledkov   Mon, 29 Feb 2016 14:27:51
+

partman-partitioning (112ubuntu1) yakkety; urgency=medium

  * Resynchronise with Debian.  Remaining changes:

- On s390x use msdos partition table by default, unless partman
  advises dasd.

 -- Dimitri John Ledkov   Fri, 12 Aug 2016 09:52:51
+0100

But also this:

partman-base (190) unstable; urgency=medium

  [ Viktor Mihajlovski ]
  * Add disk label type to device directory, such that
e.g. partman-partitioning can elect dasd partitioning table for dasd
drives.

  [ Dimitri John Ledkov ]
  * On s390[x], prevent using extended partitions on DASD drives that can
only hold 3 partitions. Parted doesn't have special knowledge about
that and claims that msdos partition table on DASD drives can hold
the usual maximum number of partitions types.

 -- Christian Perrier   Sun, 13 Nov 2016 07:45:31
+0100

The code there is:

s390|s390x)
if [ -e ./label ]; then
disklabel=$(cat label)
fi
# FBA devices have parted label dasd, but should not use dasd
# partition table. Maybe FBA|ECKD type should be exposed by
# partman-base and/or parted. LP: #1650300
device=$(sed 's|.*/||' ./device)
if grep -q "(FBA ).*$device" /proc/dasd/devices; then
disklabel=msdos
fi
if [ "$disklabel" != dasd ]; then
disklabel=msdos
fi
echo $disklabel;;

In partman-base we also limit msdos to primary partitions only on dasd
+#ifdef __s390__
+  /* DASD drives can only do 3 partitions */
+  && strcmp(disk->dev->model, "IBM S390 DASD drive")
+#endif

and disk label is saved to a file.

It is extremely limiting if installer cannot create/recreate/reformat
the drive, and has such hardcoded bad guesses.

In the past, qemu did not have vfio-ccw, but now it does. Surely, the
new libvirt/qemu in focal, when given a --disk path=/dev/disk/by-
path/ccw-0.0.1601 it must be emulating vfio-ccw if at all possible as
then on the guest it would appear as a /dev/dasda, and be correctly
processed.

So on s390x, the old installer
- default to use ms-dos partition table, with primary partitions only, with 
default layout having less than 4 partitions. 
- if previously detected DASD partition table, use DASD, unless operating on 
FBA in that case use msdos again

The above I think was ultimately driven by "lowlevel formateded FBA or
ECKD drives" without a dasd partition table. In such cases, it was
reported in qemu/kvm as "unknown" and thus "msdos with 3 partitions" was
used which seemed to work, but is extremely fragile.

In the new installer, I do no wish to support partition tables that are
limited by a very small upper bound of 2TiB. My laptop has that, and
it's trivial to over-provision/thinly provision such sizes.

Is it reasonable to say that:
- nvme, zfcp, virtio-scsi will use GPT
- dasd ECKD devices must use vfio-ccw if passed directly to KVM, and uses dasd 
partition table
- If vfio-ccw is not available, one can partition it on the host, create LVM or 
ext4 storage pool, and passthrough LVM volume or qcow2 file via virtio-scsi
- passing through dasd devices as virtio-scsi in the guest must not be allowed
- dasd FBA is still confusing to me as it seems to not support neither dasd nor 
gpt partition table


Or what are you proposing we should be using across all storage variants, 
with/without passthrough?

I am interested to know what should be used for DASD-FBA passthrough
from host to guest as virtio-scsi.

I am also interested to know if we can pass more information from host
to guest via virtio-scsi to indicate what sort of b

[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD

2020-09-07 Thread Dimitri John Ledkov
Request to always force ms-dos partition table in KVM was requested
before.

However, surely it is virtualization/layering violation, when a physical
host device which is not virtio-scsi compatible is passed through to
qemu which emulates it as scsi, despite the underlying device on the
host not able to create GPT, extended partitions, etc.

Can we please prohibit passing through /dev/dasda to qemu as virtio-scsi
provider on qemu and/or virtio layer?

If one passes /dev/dasda to qemu, it must show up as /dev/dasd* inside
the guest too. As there is no way for the guest to know or figure out
that the passthrough device is actually masquerading a dasd drive.

Can you please explain again, why is it correct and desired to provide
/dev/vda in the guest with /dev/dasda on the host, when the two types
are incompatible with each other?

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893775

Title:
  [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on
  DASD

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893775] Re: [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on DASD

2020-09-07 Thread Dimitri John Ledkov
I thought that one must use vfio-ccw to passthrough dasd drives, not
virtio-scsi.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893775

Title:
  [UBUNTU 20.04.1] Failure to install Ubuntu 20.04.1 as KVM guest on
  DASD

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894166] Re: libasan missing debug symbols break debugging

2020-09-07 Thread Dimitri John Ledkov
** Also affects: gcc-10 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894166

Title:
  libasan missing debug symbols break debugging

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894611] [NEW] kmod in bionic can't parse hwe/cloud kernel signatures

2020-09-07 Thread Dimitri John Ledkov
Public bug reported:

kmod in bionic can't parse hwe/cloud kernel signatures

kmod 27 https://lwn.net/Articles/812803/

linxu v5.2-rc1 changed kernel module signatures, which bionic's kmod 24
cannot parse. Only kmod 27 gained that ability.

But we have backported v5.3+ kernels to bionic, resulting in modinfo
showing incomplete information about the kernel modules.


Originally reported at: 
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2020-September/018781.html

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894611

Title:
  kmod in bionic can't parse hwe/cloud kernel signatures

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893205] Re: linux-generic-hwe-20.04 transitional to linux-generic does not exist in groovy

2020-09-03 Thread Dimitri John Ledkov
** Changed in: linux-meta (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893205

Title:
  linux-generic-hwe-20.04 transitional to linux-generic does not exist
  in groovy

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894082] [NEW] RM oem-somerville-three-eyed-raven-meta from groovy

2020-09-03 Thread Dimitri John Ledkov
Public bug reported:

RM oem-somerville-three-eyed-raven-meta from groovy


This oem platform is only certified for focal. Please remove this package from 
groovy from now on.

** Affects: oem-somerville-three-eyed-raven-meta (Ubuntu)
 Importance: Undecided
 Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894082

Title:
  RM oem-somerville-three-eyed-raven-meta from groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/oem-somerville-three-eyed-raven-meta/+bug/1894082/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

2020-09-02 Thread Dimitri John Ledkov
All tests run automatically, and yes flatpak-builder was automatically
tested and new flatpak with this fix migrated fine.

See http://autopkgtest.ubuntu.com/packages/flatpak-builder/groovy/s390x

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

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

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: make-dfsg (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886814

Title:
  posix_spawn usage in gnu make causes failures on s390x

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840845] Re: secureboot-db.service should not run in a container

2020-09-02 Thread Dimitri John Ledkov
** Changed in: secureboot-db (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840845

Title:
  secureboot-db.service should not run in a container

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816045] Re: secureboot-db: release upgrade from 16.04 to 18.04 modifies changelog.gz but resets mtime

2020-09-02 Thread Dimitri John Ledkov
so the mtime is set to the one mentioned inside the changelog, "Fri, 19
Oct 2018 11:20:34 -0700" and that's what's included in the package, and
by Debian Policy, one should maintain the timestamps as much as
possible.

at the moment we do not provide any guarantees that files in later
series, have higher/same/lower mtime than in previous releases. For
example, a package in xenial may have an SRU to fix a bug, which doesn't
affect and/or has always been fixed in bionic, thus upgrade from xenial
to bionic may see files go back in time w.r.t. mtime.

A backup system that exclusively relies on mtime, or mtime increasing
linearly, will be broken across release-upgrades. After a release-
upgrade a contents/checksum check should be executed to detect changes.

Which backup system are you using?

** Changed in: secureboot-db (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816045

Title:
  secureboot-db: release upgrade from 16.04 to 18.04 modifies
  changelog.gz but resets mtime

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888653] Re: [UBUNTU 20.10] GCC: Accept vector alignment hints on z13

2020-09-02 Thread Dimitri John Ledkov
20.04 will be done, whenever gcc packages will be updated again in
focal, batched up with other gcc upstream point release. I don't have an
ETA at the moment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888653

Title:
  [UBUNTU 20.10] GCC: Accept vector alignment hints on z13

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876715] Re: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects

2020-09-02 Thread Dimitri John Ledkov
** Changed in: linux (Ubuntu)
   Status: Fix Committed => In Progress

** Changed in: ubuntu-z-systems
   Status: Fix Committed => In Progress

** Package changed: linux (Ubuntu) => zfcpdump-kernel (Ubuntu)

** Changed in: zfcpdump-kernel (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876715

Title:
  [UBUNTU 20.04] zfcpdump-kernel package has different name for
  dumpkernel image than zipl expects

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-09-02 Thread Dimitri John Ledkov
** Description changed:

  [Impact]
  
   * update-initramfs -u fails on arm64 m6g instances in AWS
  
  [Test Case]
  
   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed
+  * It should contain pthread, and libgcc_s libraries
  
  [Regression Potential]
  
   * Adding one more path to libgcc_s1 resolution. This will still fail if
  something compiles libc6 for _two_ optimisations like
  /lib/$arch/foo/bar/libpthread.
  
  [Other Info]
  
   * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in
  the initrd libgcc_s1 must be copied in too. However the logic to find
  matching libgcc_s1 is broken for optimizied builds of libc6 without
  optimized build of libgcc_s1. I think libpthread should link against
  libgcc_s1 to prevent these issues.
  
   * Original bug report
  
  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:
  
  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.
  
  ## Steps to reproduce (on AWS)
  
  ### With focal 20200423 AMI
  
  1. Find the following AMI and launch on m6g instance family
  
     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423
  
  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u
  
  ### With focal 20200522 AMI
  
  1. Find the following AMI and launch on m6g instance family
  
     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522
  
  2. Try: sudo update-initramfs -u
  
  ## Note
  
  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.
  
  ## Expected behavior
  
  Does not fail.
  
  ## Background to find this bug
  
  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade
  pulls newer package that triggers update-initramfs, apt-get upgrade
  always fail on 20200522 AMI.
  
  the following is an apport report on 20200423 AMI:
  
  
  
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880853

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892526] Re: dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices

2020-09-01 Thread Dimitri John Ledkov
** Description changed:

+ [Impact]
+ 
+  * dpkg-reconfigure grub-pc no longer reinstalls grub, as it should.
+ 
+ [Test Case]
+ 
+  * Set grub-pc/install_devices to some invalid device that does not
+ exist (i.e. /dev/hda)
+ 
+  * Execute $ sudo dpkg-reconfigure grub-pc
+ 
+ One should expect attempts to grub-instal onto /dev/hda, fail that, and
+ see dialogues asking which devices to install grub-pc onto, and
+ successfully install them.
+ 
+ [Regression Potential]
+ 
+  * We are patching, the recently/newly added postinst condition to skip
+ trying to install grub-install during typical/regular upgrades. Further
+ tighten the conditions there, to still force install grub-install when
+ executing grub-reconfigure to be inline with existing documentation that
+ this is the command to use when one wishes to reinstall grub-pc
+ interactively.
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
  I recently had a RAID-5 disk failure and was greeted by an inoperable
  grub due to not having installed grub on all the disks.  I temporarily
  fixed this problem by manually running "grub-install" on the other disks
  in the array and got my system working.
  
  Previously it was advised to run "dpkg-reconfigure grub-pc" and select
  the relevant disks to ensure that future grub updates installed on all
  the disks in the array.  This command no longer prompts for the install
  disks due to the changed introduced by
  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889556.  In
  /var/lib/dpkg/info/grub-pc.postinst, the following elif block
  immediately precedes the elif block that prompts for grub-
  pc/install_devices and short circuits on all recent grub versions:
  
-   elif dpkg --compare-versions "$2" ge 2.04-1ubuntu26; then
- # Avoid the possibility of breaking grub on SRU update
- # due to ABI change
- :
+   elif dpkg --compare-versions "$2" ge 2.04-1ubuntu26; then
+ # Avoid the possibility of breaking grub on SRU update
+ # due to ABI change
+ :
  
  I can confirm this issue is present on 20.04.1 and it appears to be
  present on 18.04.4 per https://askubuntu.com/questions/1212569/dpkg-
  reconfigure-grub-pc-no-option-to-select-boot-device

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892526

Title:
  dpkg-reconfigure grub-pc no longer prompts for grub-pc/install_devices

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)

2020-08-28 Thread Dimitri John Ledkov
@satmandu

Thank you for pointing that documentation out.

It is correct that it is helpful to test Proposed, but I think that
information was written when packages in proposed were only published
for stable series, which only contain prospective Stable Release
Updates, and is the way "for testing updates".

That is not true for devel series. In devel series, -proposed is not for
human consumption. Instead simply running devel series, release pocket
is already testing and providing feedback from such config is useful.

I'm not sure how we can update that testing page to be more informative.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892915

Title:
  gnome-shell crashing (libffi8ubuntu1 upgrade issue)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst

2020-08-28 Thread Dimitri John Ledkov
I disagree that preinst changes are needed.

I have fixed error reporting in non-interactive postinst case.

And made grub-install resilient, w.r.t. operating against non-existent
devices or devices that refuse writing to. In all such cases, backup is
created and restored. Thus there is no need to abort at preinst.
Consistency between MBR & /boot is required and fixed here, without
reimplementing postinst in preinst.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891680

Title:
  grub-pc needs to detect when debconf points to invalid drive and stop
  in preinst, before unpacking files, and also treat this as a failure
  in postinst

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)

2020-08-27 Thread Dimitri John Ledkov
The deps are now out of date. At least mozjs68 has now moved.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892915

Title:
  gnome-shell crashing (libffi8ubuntu1 upgrade issue)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)

2020-08-27 Thread Dimitri John Ledkov
also using groovy-proposed is not supported, as it contains incompatible
mix of packages.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892915

Title:
  gnome-shell crashing (libffi8ubuntu1 upgrade issue)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877089] Re: zfcpdump kernel can not be IPLed when secure boot is requested

2020-08-27 Thread Dimitri John Ledkov
** Changed in: zfcpdump-kernel (Ubuntu)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877089

Title:
  zfcpdump kernel can not be IPLed when secure boot is requested

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878541] Re: Grub fails to load kernel from squashfs if mem < 1500mb

2020-08-27 Thread Dimitri John Ledkov
Booted existing core20 vm with old grub2.
rss went up from 128264 to 422636, after executing loopback loop1 
(hd0,gpt2)/snaps/pc-kernel_565.snap.

Replacing grubx64.efi with the one from grub-efi-
amd64-signed_1.142.5+2.04-1ubuntu26.3_amd64.deb.

loopback command was very quick, and rss went up from 129244 to just
129452.

So this is good!

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878541

Title:
  Grub fails to load kernel from squashfs if mem < 1500mb

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893205] [NEW] linux-generic-hwe-20.04 transitional to linux-generic does not exist in groovy

2020-08-27 Thread Dimitri John Ledkov
Public bug reported:

linux-generic-hwe-20.04 transitional to linux-generic does not exist in
groovy, instead it still points at 5.4 kernel.

Please create transitional meta from linux-generic-hwe-20.04 to linux-
generic.

Otherwise machines that installed Ubuntu Desktop focal, then upgrade to
groovy, remain on v5.4 kernel, instead of getting v5.8 kernel.

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: groovy

** Changed in: linux-meta (Ubuntu)
Milestone: None => ubuntu-20.10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893205

Title:
  linux-generic-hwe-20.04 transitional to linux-generic does not exist
  in groovy

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1893195] [NEW] RM ecere-sdk RC-buggy FTBFS removed from testing

2020-08-27 Thread Dimitri John Ledkov
Public bug reported:

RM ecere-sdk RC-buggy FTBFS removed from testing

https://tracker.debian.org/news/965662/ecere-sdk-removed-from-testing/

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898832

I think the bug is old, and FTBFS logs now look different, but it still
FTBFS.

** Affects: ecere-sdk (Ubuntu)
 Importance: High
 Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893195

Title:
  RM ecere-sdk RC-buggy FTBFS removed from testing

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888653] Re: [UBUNTU 20.10] GCC: Accept vector alignment hints on z13

2020-08-27 Thread Dimitri John Ledkov
releases/gcc-9 as commit 313e02cfb97

Has been available in Groovy since 11th of August, when 9.3.0-17ubuntu1
migrated, but the change was part of the 16ubuntu1 upload.

gcc-9 (9.3.0-16ubuntu1) groovy; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Disable the LTO build on arm64, armhf for now, takes 24+ hours ...

 -- Matthias Klose   Tue, 21 Jul 2020 11:57:43 +0200

gcc-9 (9.3.0-16) unstable; urgency=medium

  * Update to git 20200721 from the gcc-9 branch.
- Fix PR target/94891 (AArch64), PR target/94791 (AArch64),
  PR target/96001 (AArch64).
- Fix missing dependencies for selftests which occasionally causes
  failed builds. Addresses: #960913.
  * Build the GC enabled libobjc on arm64, mips and mipsel as well.

 -- Matthias Klose   Tue, 21 Jul 2020 11:49:23 +0200

** Changed in: gcc-9 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888653

Title:
  [UBUNTU 20.10] GCC: Accept vector alignment hints on z13

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888653] Re: [UBUNTU 20.10] GCC: Accept vector alignment hints on z13

2020-08-27 Thread Dimitri John Ledkov
releases/gcc-10 as commit 710f7d977d1

Has been available in Groovy since 8th of August, when 10.2.0-3ubuntu1
migrated

gcc-10 (10.2.0-3ubuntu1) groovy; urgency=medium

  * Merge with Debian; remaining changes:
- Build from upstream sources.
- Don't run the tests on riscv64.

 -- Matthias Klose   Sat, 25 Jul 2020 14:57:54 +0200

gcc-10 (10.2.0-3) unstable; urgency=medium

  * Update to git 20200725 from the gcc-10 branch.
- Fix PR target/96190 (SPARC), PR target/96236 (PPC), PR target/96260,
  PR fortran/95980, PR fortran/95980, PR fortran/96086, PR fortran/89574,
  PR fortran/96220, PR fortran/96018.
  * Re-enable gm2, disabled by accident in 10.2.0-1.
  * Refresh gm2 patches.
  * Apply proposed gdc patch (Iain Buclaw). Closes: #966026.
  * Apply proposed patch for PR bootstrap/96203, add -fcf-protection=check.

 -- Matthias Klose   Sat, 25 Jul 2020 14:52:31 +0200

** Changed in: gcc-10 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888653

Title:
  [UBUNTU 20.10] GCC: Accept vector alignment hints on z13

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1884763] Re: [20.10 FEAT] Upgrade openssl-ibmca >= 2.1.1 (crypto)

2020-08-27 Thread Dimitri John Ledkov
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884763

Title:
  [20.10 FEAT] Upgrade openssl-ibmca >= 2.1.1 (crypto)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891642] Re: [20.10] smc-tools 1.3.0, Enable bash autocompletion support

2020-08-26 Thread Dimitri John Ledkov
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891642

Title:
  [20.10] smc-tools 1.3.0, Enable bash autocompletion support

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888377] Re: [20.10 FEAT] Update perftest to latest version 4.4.0-29

2020-08-26 Thread Dimitri John Ledkov
** Changed in: perftest (Ubuntu)
   Status: Invalid => Fix Released

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888377

Title:
  [20.10 FEAT] Update perftest to latest version 4.4.0-29

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887900] Re: [20.10 FEAT] Upgrade libdfp to latest version 1.0.15

2020-08-26 Thread Dimitri John Ledkov
** Information type changed from Private to Public

** Changed in: libdfp (Ubuntu Groovy)
   Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887900

Title:
  [20.10 FEAT] Upgrade libdfp to latest version 1.0.15

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892797] Re: sbkeysync fails to return non-zero on error

2020-08-26 Thread Dimitri John Ledkov
sbsigntool (0.9.2-2ubuntu3) groovy; urgency=medium

  * sbkeysync: exit non-zero upon key insertion failure. (LP: #1892797)

 -- dann frazier  Mon, 24 Aug 2020 18:35:41 -0600

Please revert this!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892797

Title:
  sbkeysync fails to return non-zero on error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1892797] Re: sbkeysync fails to return non-zero on error

2020-08-26 Thread Dimitri John Ledkov
If you want this in, then one must adjust secureboot-db package service
unit to ignore the error from sbkeysync, and/or declare the relevant
error codes as normal.

This behaviour has been discussed on the grub_distros keybase channel,
without any objections raised.

And no, seeing that package update / sbkeysync succeeded once, is not
good enough. As one has to verify that on every boot. Becuase dbx
variable store can be reverted/reset between each boot back to stock
defaults. Thus a single success from sbkeysync, can only give a false
sense of security.

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

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

** Changed in: sbsigntool (Ubuntu Bionic)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892797

Title:
  sbkeysync fails to return non-zero on error

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   8   9   10   >