[Bug 1919451] Re: Update (python-)zhmcclient to latest release

2021-05-17 Thread Frank Heimes
** Description changed:

  While working on MAAS DPM/LPAR it turned out that a newer python-
  zhmcclient (package zhmcclient) is needed to get certain functions work,
  like especially storage group support.
  
  The latest is package is v0.27 on hirsute and v0.22 on focal.
  
  v0.28 is currently the latest release, but 0.29 is coming shortly.
  https://github.com/zhmcclient/python-zhmcclient/issues/731
  
  Hence an updated package (ideally to 0.29) is needed for focal (knowing that 
this will require a good justification: 
https://wiki.ubuntu.com/StableReleaseUpdates).
  Please notice that MAAS was the only reason why the zhmcclient package was 
created at all.
+ 
+ The updated package is especially needed for focal, since focal is the
+ recommended base distro for MAAS DPM/LPAR, hence this would require a
+ special SRU (for this package version bump).

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

Title:
  Update (python-)zhmcclient to latest release

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

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

[Bug 1928744] [NEW] Disk IO very slow on kernel 4.15.0-142-generic

2021-05-17 Thread Mariusz
Public bug reported:

After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel
4.15.0-142-generic disk IOs (writes) are suffering from terrible delay.

Time required to write 1GB of data to the dist is ~12 minutes.
 
1GB in 12 minutes:
strace -ttvvff -o mel.strace dd bs=1024k count=1024  if=/dev/zero 
of=/data/disk_test/dd_test

Before the upgrade,  it took seconds to complete.
The only change which was done on the system was security upgrade done with 
unattended-upgrade utility and main repositories for bionic and bionic-security.

This is physical server LENOVO System x3650 M5, with Symbios Logic
MegaRAID SAS-3 3108  disk controller.

The only difference which I see is that there are more modules loaded by
the latest kernel.

I would expect that the performance would be the same. There were no
changes to the physical server and the disks are reported as online and
healthy. No only dd is affected but also all disk-based operation by
barman (we are using postgres steaming backup along with rsync/ssh
archiving).

I think this could be a kernel bug. I would be happy to provide other
information which would help in fixing this problem.

=
Details:

lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04


lsmod
Module  Size  Used by
ip6_tables 28672  0
iptable_filter 16384  0
ip_tables  28672  1 iptable_filter
x_tables   40960  3 iptable_filter,ip6_tables,ip_tables
tcp_diag   16384  0
udp_diag   16384  0
raw_diag   16384  0
inet_diag  24576  3 tcp_diag,raw_diag,udp_diag
unix_diag  16384  0
binfmt_misc20480  1
ipmi_ssif  32768  0
kvm_intel 217088  0
kvm   614400  1 kvm_intel
irqbypass  16384  1 kvm
crct10dif_pclmul   16384  0
crc32_pclmul   16384  0
ghash_clmulni_intel16384  0
pcbc   16384  0
aesni_intel   188416  0
aes_x86_64 20480  1 aesni_intel
crypto_simd16384  1 aesni_intel
glue_helper16384  1 aesni_intel
cryptd 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel
ipmi_si57344  0
ipmi_devintf   20480  0
ipmi_msghandler53248  3 ipmi_devintf,ipmi_si,ipmi_ssif
acpi_pad  180224  0
bonding   163840  0
lp 20480  0
parport49152  1 lp
autofs440960  2
mgag20045056  1
i2c_algo_bit   16384  1 mgag200
ttm   106496  1 mgag200
drm_kms_helper172032  1 mgag200
syscopyarea16384  1 drm_kms_helper
tg3   167936  0
sysfillrect16384  1 drm_kms_helper
sysimgblt  16384  1 drm_kms_helper
fb_sys_fops16384  1 drm_kms_helper
ptp20480  1 tg3
drm   401408  4 drm_kms_helper,mgag200,ttm
pps_core   20480  1 ptp
megaraid_sas  143360  12


lspci  -vnn -s 0b:00.0
0b:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3 
3108 [Invader] [1000:005d] (rev 02)
Subsystem: IBM MegaRAID SAS-3 3108 [Invader] [1014:0454]
Physical Slot: 9
Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0
I/O ports at 2e00 [size=256]
Memory at 903f (64-bit, non-prefetchable) [size=64K]
Memory at 9040 (64-bit, non-prefetchable) [size=1M]
Expansion ROM at  [disabled]
Capabilities: [50] Power Management version 3
Capabilities: [68] Express Endpoint, MSI 00
Capabilities: [d0] Vital Product Data
Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [c0] MSI-X: Enable+ Count=97 Masked-
Capabilities: [100] Advanced Error Reporting
Capabilities: [1e0] #19
Capabilities: [1c0] Power Budgeting 
Capabilities: [148] Alternative Routing-ID Interpretation (ARI)
Kernel driver in use: megaraid_sas
Kernel modules: megaraid_sas

Strace example for 10MB:
strace -ttvvff -o mel.strace   dd bs=1024k count=10  if=/dev/zero 
of=/data/disk_test/dd_test 
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 6.73972 s, 1.6 MB/s

14:59:19.145037 execve("/bin/dd", ["dd", "bs=1024k", "count=10", 
"if=/dev/zero", "of=/data/disk_test/dd_test"], 
["LS_COLORS=rs=0:di=01;34:ln=01;36"..., "LESSCLOSE=/usr/bin/lesspipe %s %"..., 
"LANG=en_AU.UTF-8", "SUDO_GID=4118", "USERNAME=root", "SUDO_COMMAND=/bin/bash", 
"S_COLORS=auto", "USER=root", "PWD=/data/disk_test", "HOME=/root", 
"SUDO_USER=mariusz.boruc", "SUDO_UID=4118", "MAIL=/var/mail/root", 
"SHELL=/bin/bash", "TERM=xterm-256color", "SHLVL=1", "LANGUAGE=en_AU:", 
"LOGNAME=root", "PATH=/usr/local/sbin:/usr/local/"..., "LESSOPEN=| 
/usr/bin/lesspipe %s", "_=/usr/bin/strace", "OLDPWD=/data"]) = 0
14:59:19.145685 

[Bug 1927839] Re: libawt_xawt.so missing in openjdk 11.0.11

2021-05-17 Thread Reto Galante
The workaround to additionally install the default-jre has another downside: 
the size of the snap is increased by around 30M. 

Only to have the now missing libawt_xawt.so which itselves weights less
than 400B.

** Bug watch added: github.com/RetGal/Dayon/issues #36
   https://github.com/RetGal/Dayon/issues/36

** Also affects: dayon via
   https://github.com/RetGal/Dayon/issues/36
   Importance: Unknown
   Status: Unknown

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

Title:
  libawt_xawt.so missing in openjdk 11.0.11

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

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

[Bug 1928743] [NEW] started the 20.xx upgrade, allowed to start adn crashed ould not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then

2021-05-17 Thread JTHSr
Public bug reported:

Current distro:
Description:Ubuntu 18.04.5 LTS
Release:18.04

Started distro upgrade to 20.04 - error and stalled at setting new
software channels

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

 If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to
investigate this yourself the log files in '/var/log/dist-upgrade' will
contain details about the upgrade. Specifically, look at 'main.log' and
'apt.log'.

see main.log attached

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.44
ProcVersionSignature: Ubuntu 4.15.0-143.147-generic 4.15.18
Uname: Linux 4.15.0-143-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Mon May 17 21:58:37 2021
InstallationDate: Installed on 2021-04-13 (34 days ago)
InstallationMedia: ChaletOS 16.04 - Release amd64
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-05-18 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages

** Attachment added: "apport.ubuntu-release-upgrader-core.kolmo0wx.apport"
   
https://bugs.launchpad.net/bugs/1928743/+attachment/5498366/+files/apport.ubuntu-release-upgrader-core.kolmo0wx.apport

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

Title:
  started the 20.xx upgrade, allowed to start adn crashed ould not
  calculate the upgrade  An unresolvable problem occurred while
  calculating the upgrade.   If none of this applies, then please report
  this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core'
  in a terminal. If you want to investigate this yourself the log files
  in '/var/log/dist-upgrade' will contain details about the upgrade.
  Specifically, look at 'main.log' and 'apt.log'

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

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

[Bug 1876678] Re: Ubuntu 20.04 KVM / QEMU Failure with nested FreeBSD bhyve

2021-05-17 Thread Christian Ehrhardt 
** Also affects: qemu-gitlab via
   https://gitlab.com/qemu-project/qemu/-/issues/337
   Importance: Unknown
   Status: Unknown

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

Title:
  Ubuntu 20.04 KVM / QEMU Failure with nested FreeBSD bhyve

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

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

[Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34

2021-05-17 Thread Kai-Heng Feng
Thanks. Please file an upstream bug.

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

Title:
  Fans switching on and off every 10 seconds after update to kernel
  5.8.0-34

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

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

[Bug 1928642] Re: [SRU] libreoffice 7.0.6 for groovy

2021-05-17 Thread Rico Tzschichholz
** Description changed:

  [Impact]
  
-  * LibreOffice 7.0.6 is in its sixth bugfix release of the 7.0 line:
-  https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.6_release
+  * LibreOffice 7.0.6 is in its sixth bugfix release of the 7.0 line:
+  https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.6_release
  
-  * Version 7.0.5 is currently released in groovy. For a list of fixed bugs 
compared to 7.0.5 see the list of bugs fixed in the release candidates of 7.0.6 
(that's a total of 50 bugs):
-  https://wiki.documentfoundation.org/Releases/7.0.6/RC1#List_of_fixed_bugs
-  https://wiki.documentfoundation.org/Releases/7.0.6/RC2#List_of_fixed_bugs
+  * Version 7.0.5 is currently released in groovy. For a list of fixed bugs 
compared to 7.0.5 see the list of bugs fixed in the release candidates of 7.0.6 
(that's a total of 50 bugs):
+  https://wiki.documentfoundation.org/Releases/7.0.6/RC1#List_of_fixed_bugs
+  https://wiki.documentfoundation.org/Releases/7.0.6/RC2#List_of_fixed_bugs
  
-  * Given the nature of the project, the complexity of the codebase and
+  * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU a
  minor release rather than cherry-pick selected bug fixes.
  
  [Testing]
  
-  * Upstream testing. Bugs fixed upstream typically include
+  * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).
  
-   * A recent set of upstream's automated jenkins testing can be found here:
- https://ci.libreoffice.org/job/gerrit_linux_gcc_release/82662/console
+   * A recent set of upstream's automated jenkins testing can be found here:
+ https://ci.libreoffice.org/job/gerrit_linux_gcc_release/82662/console
  
-   * More information about the upstream QA testing can be found here:
- * Automated tests
-   https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
- * Automated UI tests
-   https://wiki.documentfoundation.org/Development/UITests
- * Regression tests
-   https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
- * Feature tests
-   https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
+   * More information about the upstream QA testing can be found here:
+ * Automated tests
+   https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
+ * Automated UI tests
+   https://wiki.documentfoundation.org/Development/UITests
+ * Regression tests
+   https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
+ * Feature tests
+   https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
  
-  * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
- * [amd64] ...
- * [arm64] ...
- * [armhf] ...
- * [ppc64el] ...
- * [s390x] ...
+  * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
+ * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/amd64/libr/libreoffice/20210518_015036_da635@/log.gz
+ * [arm64] ...
+ * [armhf] ...
+ * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/ppc64el/libr/libreoffice/20210518_025204_037c5@/log.gz
+ * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-groovy-ricotz-ppa/groovy/s390x/libr/libreoffice/20210518_014102_69cc4@/log.gz
  
-  * General smoke testing of all the applications in the office suite
+  * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented by:
  https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
  
  [Regression Potential]
  
-  * A minor release with a total of 50 bug fixes always carries the
+  * A minor release with a total of 50 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.
  
-  * A combination of autopkgtests and careful smoke testing as described
+  * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

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

Title:
  [SRU] libreoffice 7.0.6 for groovy

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

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

[Bug 1874377] Re: Netplan does not connect to Wireless after `sudo netplan apply` until reboot

2021-05-17 Thread mdyn
20.04.02 it's still the same

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

Title:
  Netplan does not connect to Wireless after `sudo netplan apply` until
  reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1874377/+subscriptions

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

[Bug 1901363] Re: Updating to 1.2.4-1 breaks pulseaudio on AMD Renoir devices

2021-05-17 Thread Launchpad Bug Tracker
[Expired for alsa-ucm-conf (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: alsa-ucm-conf (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Updating to 1.2.4-1 breaks pulseaudio on AMD Renoir devices

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

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

[Bug 1876567] Re: ubuntu 20.04 nfs page fault since Kernel 5.3 (?)

2021-05-17 Thread Launchpad Bug Tracker
[Expired for linux-oem-5.6 (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: linux-oem-5.6 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  ubuntu 20.04 nfs page fault since Kernel 5.3 (?)

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

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

[Bug 1908286] Re: Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10

2021-05-17 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Asus G732LWS | ALC294 | Speakers don't work on 20.04 or 20.10

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

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

[Bug 1919097] Re: Installation crashed

2021-05-17 Thread Launchpad Bug Tracker
[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: grub-installer (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Installation crashed

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

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

[Bug 1919480] Re: package postgresql-12 12.6-0ubuntu0.20.04.1 failed to install/upgrade: installed postgresql-12 package post-installation script subprocess returned error exit status 1

2021-05-17 Thread Launchpad Bug Tracker
[Expired for postgresql-12 (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: postgresql-12 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package postgresql-12 12.6-0ubuntu0.20.04.1 failed to install/upgrade:
  installed postgresql-12 package post-installation script subprocess
  returned error exit status 1

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

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

[Bug 1928741] [NEW] Root filesystem not resized if e2fsck repairs any issues

2021-05-17 Thread Aaron Jones
Public bug reported:

Observed on Ubuntu Core 18, which uses initramfs-tools-ubuntu-
core_0.7.45+ppa5_all.deb (see https://launchpad.net/~snappy-
dev/+archive/ubuntu/image/+sourcepub/11283241/+listing-archive-extra),
but this issue appears to affect the official package in addition to the
one in the PPA.

The script which resizes the writable partition (scripts/local-
premount/resize) invokes "e2fsck -fy $writable_part" but it does not pay
attention to the exit code. Since the script is invoked with "-e" any
nonzero exit code will cause the script to exit. Looking at the manpage
for e2fsck (https://man7.org/linux/man-pages/man8/e2fsck.8.html) an exit
code of 1 means "File system errors corrected". It seems likely that if
there were only correctable errors that the script should continue and
run resize2fs.

The current behavior is that the script exits prematurely. The partition
has been resized, but the filesystem has not. Because Ubuntu Core 18
lacks the fix that will resize the filesystem even when the partition is
the correct size (https://git.launchpad.net/ubuntu/+source/initramfs-
tools-devices/tree/scripts/local-premount/resize?h=ubuntu/focal#n143)
this issue is not corrected even on a reboot. The issue can be worked
around by manually running resize2fs.

I found this issue because I was improperly ejecting an SD card after
flashing it with the Ubuntu Core 18 image, and wound up with ext4
filesystem issues. I was waiting for the flashing command to sync, so
all of the files were intact, but parts of Gnome were automouting it and
doing something with it, which I believe lead to the issues with the
filesystem that were correctable by e2fsck. I totally admit the root
cause here was due to operator error, and any image made with ubuntu-
image that is not accidentally corrupted due to premature ejection would
not exhibit this issue. That said, the end result was fairly difficult
to diagnose and the fix seems straightforward -- look at the exit code
from e2fsck -- so I figured I would report it.

** Affects: initramfs-tools-ubuntu-core (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/1928741

Title:
  Root filesystem not resized if e2fsck repairs any issues

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

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

[Bug 1910976] Re: Cherry-pick dm-crypt performance improvement patch from Linux 5.9

2021-05-17 Thread gerald.yang
** Description changed:

  === SRU Justification ===
  [Impact]
- To get better performance for dm-crypt in some cases, bypass kcryptd 
workqueue can reduce the overhead in context switch between workers, 
cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline 
kernel, and this is not enabled by default
+ To get better performance for dm-crypt in some cases, bypass kcryptd 
workqueue can reduce the overhead in context switch between workers, 
cherry-pick commit 39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877 from mainline 
kernel, and bypass kcryptd workqueue is not enabled by default
  
  [Fix]
  Add flags to bypass kcryptd workqueue
  
  [Test]
  create dm-crypt and setup DM_CRYPT_NO_READ_WORKQUEUE and 
DM_CRYPT_NO_WRITE_WORKQUEUE, read/write data and run perf record to see if 
read/write to the encrypted device will bypass kcryptd workqueue
  
  [Regression Potential]
  Low, this feature is disabled by default, need to enable manually
  
  = original bug description =
  Hi,
  
  I'm asking if it would be possible to cherry-pick patch "dm crypt: add
  flags to optionally bypass kcryptd workqueues" into the 5.4 Ubuntu
  kernel. This patch has been merged in mainline kernel 5.9
  
https://github.com/torvalds/linux/commit/39d42fa96ba1b7d2544db3f8ed5da8fb0d5cb877
  but was not tagged for the stable tree.
  
  This patch provides important performance gains for some workloads using
  dm-crypt / LUKS and cherry-picking it would be very beneficial for dm-
  crypt users. You can find details on the expected gain in the following
  links:
  
  * https://www.redhat.com/archives/dm-devel/2020-July/msg00138.html
  * https://blog.cloudflare.com/speeding-up-linux-disk-encryption/
  
  The patch mostly applies cleanly on the Ubuntu 5.4 kernel, the only
  merge conflict is due to the module version at the end of the patch. I
  can provide a backport patch if needed.
  
  Thanks,

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

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => gerald.yang (gerald-yang-tw)

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => gerald.yang (gerald-yang-tw)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => gerald.yang (gerald-yang-tw)

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

Title:
  Cherry-pick dm-crypt performance improvement patch from Linux 5.9

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

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

Re: [Bug 1920180] Re: Can't detect intel wifi 6235

2021-05-17 Thread sugianto
Dear Mr. Alex,

Thank you so much for your help and great information. I'm very excited
while wait for it to work.


On Tue, May 11, 2021, 3:05 AM Alex Hung <1920...@bugs.launchpad.net> wrote:

> Updates: the patch was not included in kernel 5.13-rc1 yet but I sent a
> follow-up email and let's see how this goes.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1920180
>
> Title:
>   Can't detect intel wifi 6235
>
> Status in linux package in Ubuntu:
>   In Progress
>
> Bug description:
>   Can't detect Wireless intel advance 6235
>
>   03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N
> 6235 [8086:088f] (rev 24)
> Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a]
> Flags: fast devsel, IRQ 255
> Memory at e040 (64-bit, non-prefetchable) [size=8K]
> Capabilities: 
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.11-0ubuntu27.16
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  sgo1245 F pulseaudio
>/dev/snd/controlC0:  sgo1245 F pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: X-Cinnamon
>   DistroRelease: Linux Mint 20.1
>   InstallationDate: Installed on 2021-03-15 (4 days ago)
>   InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103
>   IwConfig:
>enp0s25   no wireless extensions.
>
>lono wireless extensions.
>   MachineType: LENOVO 20AWS0DS0T
>   Package: linux (not installed)
>   ProcFB: 0 i915drmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic
> root=UUID=7bbc36d4-b65d-4291-a3b9-dc840a88f20a ro quiet splash
>   ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94
>   RelatedPackageVersions:
>linux-restricted-modules-5.4.0-67-generic N/A
>linux-backports-modules-5.4.0-67-generic  N/A
>linux-firmware1.187.10
>   RfKill:
>0: tpacpi_bluetooth_sw: Bluetooth
> Soft blocked: yes
> Hard blocked: no
>   Tags:  ulyssa
>   Uname: Linux 5.4.0-67-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 04/20/2020
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: GLETA1WW (2.55 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20AWS0DS0T
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias:
> dmi:bvnLENOVO:bvrGLETA1WW(2.55):bd04/20/2020:svnLENOVO:pn20AWS0DS0T:pvrThinkPadT440p:rvnLENOVO:rn20AWS0DS0T:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.family: ThinkPad T440p
>   dmi.product.name: 20AWS0DS0T
>   dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p
>   dmi.product.version: ThinkPad T440p
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920180/+subscriptions
>

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

Title:
  Can't detect intel wifi 6235

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

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

[Bug 1928600] Re: [amdgpu] Gnome locks up with artifacts on screen

2021-05-17 Thread Daniel van Vugt
Thanks for that. Next time you experience a lockup, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

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

Title:
  [amdgpu] Gnome locks up with artifacts on screen

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

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

[Bug 1928656] Re: [i915] Horizontal lines of flickering random pixels on Comet Lake

2021-05-17 Thread Daniel van Vugt
** Summary changed:

- flickering random pixels 
+ [i915] Horizontal lines of flickering random pixels on Comet Lake

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: Incomplete => New

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

Title:
  [i915] Horizontal lines of flickering random pixels on Comet Lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1928656/+subscriptions

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

[Bug 1928475] Re: Xorg freeze when booting up

2021-05-17 Thread Daniel van Vugt
Thanks but it's not obvious to me where the hang of a few minutes is in
that log. Can you say the exact time it occurred? Or can you reproduce
the hang again and tell us what time it occurred?

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

Title:
  Xorg freeze when booting up

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

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

[Bug 1926811] Re: After upgrading to 20.04 applications no longer launch from overview

2021-05-17 Thread Daniel van Vugt
** Changed in: gnome-shell (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/1926811

Title:
  After upgrading to 20.04 applications no longer launch from overview

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

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

Re: [Bug 1928593] Re: Dell Precision 3560: system hang upon resume from s2idle suspend

2021-05-17 Thread koba
@Brian,
would you mind helping me try this cmd? then please s2idle
*echo 0|sudo tee /sys/bus/pci/devices/*/d3cold_allowed

please also provide dmesg. thanks

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

Title:
  Dell Precision 3560: system hang upon resume from s2idle suspend

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

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

[Bug 1876678] Re: Ubuntu 20.04 KVM / QEMU Failure with nested FreeBSD bhyve

2021-05-17 Thread John Hartley
Hi Christian,

I have posted issue to upstream QEMU

https://gitlab.com/qemu-project/qemu/-/issues/337


Thanks again for assistance / advise.

Cheers from Oz,

John.

** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #337
   https://gitlab.com/qemu-project/qemu/-/issues/337

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

Title:
  Ubuntu 20.04 KVM / QEMU Failure with nested FreeBSD bhyve

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

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

[Bug 1926455] Re: sendCtrlAltDelete is not defined

2021-05-17 Thread Pedro Victor Lourenço Fragola
I tested the focal-proposed package:

ii  spice-html5  0.2.2-0ubuntu2.20.04.1
all  Spice Web client which runs entirely within a modern
browser

After installing the package it was possible to use the "Ctrl+Alt+Del"
button successfully.

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

Title:
  sendCtrlAltDelete is not defined

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

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

[Bug 1928513] Re: 232403

2021-05-17 Thread Bryce Harrington
** Changed in: apache2 (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/1928513

Title:
  232403

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

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

[Bug 1927911] Re: Update intel-microcode to latest upstream release 20210216 for CVE fixes for xeon platforms

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package intel-microcode -
3.20210216.0ubuntu0.16.04.1

---
intel-microcode (3.20210216.0ubuntu0.16.04.1) xenial-security; urgency=medium

  * SECURITY UPDATE: New upstream microcode datafile 2021-02-16 (LP: #1927911)
+ Updated Microcodes:
  sig 0x00050654, pf_mask 0xb7, 2020-12-31, rev 0x2006a0a, size 36864
  sig 0x00050656, pf_mask 0xbf, 2020-12-31, rev 0x4003006, size 53248
  sig 0x00050657, pf_mask 0xbf, 2020-12-31, rev 0x5003006, size 53248
  sig 0x000706a1, pf_mask 0x01, 2020-06-09, rev 0x0034, size 74752
- CVE-2020-8695 RAPL, INTEL-TA-00389
- CVE-2020-8696 Vector Register Leakage-Active, INTEL-TA-00381
- CVE-2020-8698 Fast forward store predictor, INTEL-TA-00381

 -- Alex Murray   Fri, 14 May 2021 16:31:00
+0930

** Changed in: intel-microcode (Ubuntu Xenial)
   Status: Confirmed => 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/1927911

Title:
  Update intel-microcode to latest upstream release 20210216 for CVE
  fixes for xeon platforms

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

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

[Bug 1928709] Re: Can't launch hirsute VM using LXD

2021-05-17 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1928709/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

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

Title:
  Can't launch hirsute VM using LXD

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

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

[Bug 1928735] [NEW] unable to start (segmentation fault)

2021-05-17 Thread Adam Poldauf
Public bug reported:

I'm not able to start postsrsd due segmaintation fault

root@mail-proxymx-4:~$ dpkg -l | grep post
ii  postfix3.3.0-1ubuntu0.3amd64
High-performance mail transport agent
ii  postfix-mysql  3.3.0-1ubuntu0.3amd64
MySQL map support for Postfix
ii  postfix-pcre   3.3.0-1ubuntu0.3amd64
PCRE map support for Postfix
ii  postfix-policyd-spf-python 2.0.2-1 all  
Postfix policy server for SPF checking
ii  postsrsd   1.4-1ubuntu0.1  amd64
Sender Rewriting Scheme (SRS) lookup table for Postfix
root@mail-proxymx-4:~$ lsb_release -rd
Description:Ubuntu 18.04.5 LTS
Release:18.04
root@mail-proxymx-4:~$ apt-cache policy postsrsd
postsrsd:
  Installed: 1.4-1ubuntu0.1
  Candidate: 1.4-1ubuntu0.1
  Version table:
 *** 1.4-1ubuntu0.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 1.4-1 500
500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
root@mail-proxymx-4:~$ postsrsd -4 -f 10005 -r 10006 -d example.com -s 
/etc/postsrsd.secret -u nobody
Segmentation fault

Just let me know if you need more info about env.

** Affects: postsrsd (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/1928735

Title:
  unable to start (segmentation fault)

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

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

[Bug 1864020] Re: libvirt.libvirtError: Requested operation is not valid: format of backing image %s of image %s was not specified in the image metadata (See https://libvirt.org/kbase/backing_chains.h

2021-05-17 Thread Shi Yan
We are using the ussuri nova, which already includes the above patch,
but still have the problem to start the instance.

trace logs are as following:

=
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server Traceback (most recent call last):
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/oslo_messaging/rpc/server.py", line 165, in 
_process_incoming
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 276, in 
dispatch
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, 
args)
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/oslo_messaging/rpc/dispatcher.py", line 196, in 
_do_dispatch
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server result = func(ctxt, **new_args)
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/nova/exception_wrapper.py", line 79, in wrapped
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server function_name, call_dict, binary, tb)
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server self.force_reraise()
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb)
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File "/usr/lib/python3/dist-packages/six.py", line 
703, in reraise
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server raise value
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/nova/exception_wrapper.py", line 69, in wrapped
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server return f(self, context, *args, **kw)
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/nova/compute/manager.py", line 189, in 
decorated_function
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server "Error: %s", e, instance=instance)
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server self.force_reraise()
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb)
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File "/usr/lib/python3/dist-packages/six.py", line 
703, in reraise
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server raise value
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/nova/compute/manager.py", line 159, in 
decorated_function
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server return function(self, context, *args, **kwargs)
  2021-05-18 10:05:32.386 144075 ERROR 
oslo_messaging.rpc.server   File 
"/usr/lib/python3/dist-packages/nova/compute/utils.py", line 1456, in 
decorated_function
  

[Bug 1927558] Re: Check boxes in Software Updater are trimmed along left edge

2021-05-17 Thread PJSingh5000
The issue occurs when there are more than one tree roots in the updates
list.

This is what I see...

   ] Security updates
 > Ubuntu base
   ] Other updates
 > Ubuntu base

The expander ">" is missing and the leftmost section of the checkbox is
cropped.

It should look like this...

> [] Security updates
 > Ubuntu base
> [] Other updates
 > Ubuntu base


** Attachment added: "The expander ">" is missing and the leftmost section of 
the checkbox is cropped."
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1927558/+attachment/5498349/+files/Screenshot%20from%202021-05-17%2020-26-30.png

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

Title:
  Check boxes in Software Updater are trimmed along left edge

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

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

[Bug 1928734] [NEW] Upgrade from 18.04 to 20.04 failed

2021-05-17 Thread Justus Schlichting
Public bug reported:

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

 If none of this applies, then please report this bug using the command
'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to
investigate this yourself the log files in '/var/log/dist-upgrade' will
contain details about the upgrade. Specifically, look at 'main.log' and
'apt.log'.

>From main.log ...
2021-05-17 16:31:04,840 INFO checking for python-dbg (auto_inst=False)
2021-05-17 16:31:04,840 INFO checking for python-doc (auto_inst=False)
2021-05-17 16:31:04,840 INFO checking for python-minimal (auto_inst=False)
2021-05-17 16:31:04,840 INFO installing python-is-python2 because 
python-minimal was installed
2021-05-17 16:31:04,840 DEBUG Installing 'python-is-python2' (python-minimal 
was installed on the system)
2021-05-17 16:31:04,900 INFO removing python-minimal because python-is-python2 
is being installed
2021-05-17 16:31:04,900 DEBUG Removing 'python-minimal' (python-is-python2 is 
being installed on the system)
2021-05-17 16:31:04,956 INFO failed to remove python-minimal
2021-05-17 16:31:04,957 INFO checking for python-dev (auto_inst=False)
2021-05-17 16:31:04,957 INFO checking for libpython-dev (auto_inst=False)
2021-05-17 16:31:04,957 INFO checking for libpython-stdlib (auto_inst=False)
2021-05-17 16:31:04,957 INFO removing libpython-stdlib because None is being 
installed
2021-05-17 16:31:04,957 DEBUG Removing 'libpython-stdlib' (None is being 
installed on the system)
2021-05-17 16:31:05,013 INFO failed to remove libpython-stdlib
2021-05-17 16:31:05,013 INFO checking for libpython-dbg (auto_inst=False)
2021-05-17 16:31:05,013 INFO checking for python-dbg (auto_inst=True)
2021-05-17 16:31:05,013 INFO checking for python-doc (auto_inst=True)
2021-05-17 16:31:05,013 INFO checking for python-minimal (auto_inst=True)
2021-05-17 16:31:05,013 INFO installing python-is-python2 because 
python-minimal was installed
2021-05-17 16:31:05,014 DEBUG Installing 'python-is-python2' (python-minimal 
was installed on the system)
2021-05-17 16:31:05,073 INFO removing python-minimal because python-is-python2 
is being installed
2021-05-17 16:31:05,073 DEBUG Removing 'python-minimal' (python-is-python2 is 
being installed on the system)
2021-05-17 16:31:05,073 INFO failed to remove python-minimal
2021-05-17 16:31:05,073 INFO checking for python-dev (auto_inst=True)
2021-05-17 16:31:05,073 INFO checking for libpython-dev (auto_inst=True)
2021-05-17 16:31:05,073 INFO checking for libpython-stdlib (auto_inst=True)
2021-05-17 16:31:05,073 INFO removing libpython-stdlib because None is being 
installed
2021-05-17 16:31:05,073 DEBUG Removing 'libpython-stdlib' (None is being 
installed on the system)
2021-05-17 16:31:05,074 INFO failed to remove libpython-stdlib
2021-05-17 16:31:05,074 INFO checking for libpython-dbg (auto_inst=True)
2021-05-17 16:37:47,739 ERROR Dist-upgrade failed: 'E:Error, 
pkgProblemResolver::Resolve generated breaks, this may be caused by held 
packages.'
2021-05-17 16:37:47,745 DEBUG abort called
2021-05-17 16:37:47,748 DEBUG openCache()
2021-05-17 16:37:51,388 DEBUG Comparing 3.11.0-26 with
2021-05-17 16:37:51,389 DEBUG Comparing 3.13.0-109 with 3.11.0-26
2021-05-17 16:37:51,389 DEBUG Comparing 3.13.0-165 with 3.13.0-109
2021-05-17 16:37:51,390 DEBUG Comparing 3.13.0-96 with 3.13.0-165
2021-05-17 16:37:51,390 DEBUG Comparing 3.8.0-32 with 3.13.0-165
2021-05-17 16:37:51,396 DEBUG Comparing 4.15.0-142 with 3.13.0-165
2021-05-17 16:37:51,396 DEBUG Comparing 4.15.0-143 with 4.15.0-142
2021-05-17 16:37:51,845 DEBUG /openCache(), new cache size 104343

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.44
ProcVersionSignature: Ubuntu 4.15.0-143.147-generic 4.15.18
Uname: Linux 4.15.0-143-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon May 17 17:04:14 2021
InstallationDate: Installed on 2013-05-10 (2929 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-05-18 (0 days ago)
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages

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

Title:
  Upgrade from 18.04 to 20.04 failed

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

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

[Bug 1698261]

2021-05-17 Thread Arilou
Just wanted to update a workaround, it seems like the issue is that the
API that Blizzard are using (is probably Winhttp) which ends up doing
DNS lookups for wpad, which simply times out.

A simple solution that worked for me was to add to /etc/hosts
127.0.0.1 wpad
127.0.0.1 wpad.lan

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

Title:
  Wine Regression in 17.04 Ubuntu, 16.04 works

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

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

[Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04

2021-05-17 Thread Robert Dinse
I removed a bunch of stuff I did not really need, game servers, xorg-
xserver drivers for hardware I did not have, kvm-qemu stuff that I have
not used on this machine since last July, tor, and after getting rid of
a bunch of cruft, it does reboot properly so now I have to figure out
which application breaks it.

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

Title:
  systemctl reboot hangs the machine under hirsute 21.04

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

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

[Bug 1928733] [NEW] Starting systemd Network Service fails with "Invalid argument"

2021-05-17 Thread David Cunningham
Public bug reported:

This server has a new install of Ubuntu 18.04 server. Sometimes (around
50% of the time) when it boots systemd-networkd.service initially fails
to start with an error as below. It then tries again and succeeds,
however other services which depend on systemd-networkd have already
failed on the dependency by then.

>From the output of "journalctl -u systemd-networkd":

-- Reboot --
May 17 19:44:28 server1 systemd[1]: Starting Network Service...
May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed to set 
up mount namespacing: Invalid argument
May 17 19:44:30 server1 systemd[2261]: systemd-networkd.service: Failed at step 
NAMESPACE spawning /lib/systemd/systemd-networkd: Invalid argument
May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Main process 
exited, code=exited, status=226/NAMESPACE
May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Failed with 
result 'exit-code'.
May 17 19:44:30 server1 systemd[1]: Failed to start Network Service.
May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Service has no 
hold-off time, scheduling restart.
May 17 19:44:30 server1 systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 1.
May 17 19:44:30 server1 systemd[1]: Stopped Network Service.
May 17 19:44:30 server1 systemd[1]: Starting Network Service...
May 17 19:44:30 server1 systemd-networkd[2321]: Enumeration completed
May 17 19:44:30 server1 systemd[1]: Started Network Service.
May 17 19:44:30 server1 systemd-networkd[2321]: eno2: IPv6 successfully enabled
May 17 19:44:30 server1 systemd-networkd[2321]: eno1: Link is not managed by us
May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not 
managed by us
May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not 
managed by us
May 17 19:44:30 server1 systemd-networkd[2321]: eno1: IPv6 successfully enabled
May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f0np0: Link is not 
managed by us
May 17 19:44:30 server1 systemd-networkd[2321]: lo: Link is not managed by us
May 17 19:44:30 server1 systemd-networkd[2321]: enp94s0f1np1: Link is not 
managed by us
May 17 19:44:31 server1 systemd-networkd[2321]: eno2: Link UP
May 17 19:44:31 server1 systemd-networkd[2321]: eno1: Link UP
May 17 19:44:34 server1 systemd-networkd[2321]: eno2: Gained carrier
May 17 19:44:34 server1 systemd-networkd[2321]: eno1: Gained carrier
May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Gained IPv6LL
May 17 19:44:35 server1 systemd-networkd[2321]: eno1: Configured
May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Gained IPv6LL
May 17 19:44:36 server1 systemd-networkd[2321]: eno2: Configured

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.46
ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
Date: Mon May 17 19:53:11 2021
InstallationDate: Installed on 2021-03-18 (60 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1604:10c0 Tascam 
 Bus 001 Device 003: ID 1604:10c0 Tascam 
 Bus 001 Device 002: ID 1604:10c0 Tascam 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R440
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=/dev/mapper/vg1-lv_root ro processor.max_cstate=1 intel_idle.max_cstate=0 
transparent_hugepage=never
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/23/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.9.3
dmi.board.name: 04JN2K
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.9.3:bd09/23/2020:svnDellInc.:pnPowerEdgeR440:pvr:rvnDellInc.:rn04JN2K:rvrA06:cvnDellInc.:ct23:cvr:
dmi.product.family: PowerEdge
dmi.product.name: PowerEdge R440
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  Starting systemd Network Service fails with "Invalid argument"

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

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

[Bug 1926796] Update Released

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

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

Title:
  [SRU] Enable support for Xena Cloud Archive

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

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

[Bug 1926796] Re: [SRU] Enable support for Xena Cloud Archive

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.98.9.5

---
software-properties (0.98.9.5) focal; urgency=medium

  * cloudarchive: Enable support for the Xena Ubuntu Cloud Archive on
20.04 (LP: #1926796).

 -- Corey Bryant   Fri, 30 Apr 2021 14:13:30
-0400

** Changed in: software-properties (Ubuntu Focal)
   Status: Fix Committed => 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/1926796

Title:
  [SRU] Enable support for Xena Cloud Archive

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

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

[Bug 1901294] Re: nouveau timeout and system lockup

2021-05-17 Thread Ivan Larionov
This is fixed in 21.04.

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

Title:
  nouveau timeout and system lockup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

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

[Bug 1907686] Re: ovn: instance unable to retrieve metadata

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package openvswitch - 2.13.3-0ubuntu0.20.04.1

---
openvswitch (2.13.3-0ubuntu0.20.04.1) focal; urgency=medium

  [ James Page ]
  * New upstream point release (LP: #1920141, LP: #1907686).
  * Dropped security patches, included in release:
- CVE-2015-8011.patch
- CVE-2020-27827.patch
- CVE-2020-35498.patch
  * Add BD on libdbus-1-dev to resolve linking issues for DPDK builds due
to changes in DPDK.
  * d/control: Set minimum version of libdpdk-dev to avoid build
failures with 19.11.6-0ubuntu0.20.04.1.

  [ Frode Nordahl ]
  * Fix recording of FQDN/hostname on startup (LP: #1915829):
- d/p/ovs-dev-ovs-ctl-Allow-recording-hostname-separately.patch: Cherry
  pick of committed upstream fix to support skip of hostname
  configuration on ovs-vswitchd/ovsdb-server startup.
- d/openvswitch-switch.ovs-record-hostname.service: Record hostname in
  Open vSwitch after network-online.target using new systemd unit.
- d/openvswitch-switch.ovs-vswitchd.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.ovsdb-server.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.service: Add `Also` reference to
  ovs-record-hostname.service so that the service is enabled on install.
- d/rules: Add `ovs-record-hostname.service` to package build.

 -- James Page   Wed, 24 Mar 2021 08:46:41 +

** Changed in: openvswitch (Ubuntu Focal)
   Status: Fix Committed => 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/1907686

Title:
  ovn: instance unable to retrieve metadata

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-chassis/+bug/1907686/+subscriptions

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

[Bug 1912905] Update Released

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

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

Title:
  Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server
  image

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

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

[Bug 1912905] Re: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.04.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.04.1) focal; urgency=medium

  * Backport to focal (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

** Changed in: linux-firmware-raspi2 (Ubuntu Focal)
   Status: Fix Committed => 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/1912905

Title:
  Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server
  image

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

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

[Bug 1912905] Re: Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server image

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.10.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.10.1) groovy; urgency=medium

  * Pull in latest from hirsute (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

** Changed in: linux-firmware-raspi2 (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

** Bug watch added: github.com/raspberrypi/linux/issues #3849
   https://github.com/raspberrypi/linux/issues/3849

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

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

Title:
  Can't find WLAN device on RPI-CM4L with 20.10 armhf preinstall server
  image

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

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

[Bug 1915829] Re: FQDN / hostname recorded in OVSDB is unreliable

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package openvswitch - 2.13.3-0ubuntu0.20.04.1

---
openvswitch (2.13.3-0ubuntu0.20.04.1) focal; urgency=medium

  [ James Page ]
  * New upstream point release (LP: #1920141, LP: #1907686).
  * Dropped security patches, included in release:
- CVE-2015-8011.patch
- CVE-2020-27827.patch
- CVE-2020-35498.patch
  * Add BD on libdbus-1-dev to resolve linking issues for DPDK builds due
to changes in DPDK.
  * d/control: Set minimum version of libdpdk-dev to avoid build
failures with 19.11.6-0ubuntu0.20.04.1.

  [ Frode Nordahl ]
  * Fix recording of FQDN/hostname on startup (LP: #1915829):
- d/p/ovs-dev-ovs-ctl-Allow-recording-hostname-separately.patch: Cherry
  pick of committed upstream fix to support skip of hostname
  configuration on ovs-vswitchd/ovsdb-server startup.
- d/openvswitch-switch.ovs-record-hostname.service: Record hostname in
  Open vSwitch after network-online.target using new systemd unit.
- d/openvswitch-switch.ovs-vswitchd.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.ovsdb-server.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.service: Add `Also` reference to
  ovs-record-hostname.service so that the service is enabled on install.
- d/rules: Add `ovs-record-hostname.service` to package build.

 -- James Page   Wed, 24 Mar 2021 08:46:41 +

** Changed in: openvswitch (Ubuntu Focal)
   Status: Fix Committed => 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/1915829

Title:
  FQDN / hostname recorded in OVSDB is unreliable

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

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

[Bug 1918013] Re: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi, 3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.04.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.04.1) focal; urgency=medium

  * Backport to focal (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

** Changed in: linux-firmware-raspi2 (Ubuntu Focal)
   Status: Fix Committed => 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/1918013

Title:
  package linux-firmware 1.194 [modified:
  lib/firmware/brcm/brcmfmac43430-sdio.bin
  lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt
  lib/firmware/brcm/brcmfmac43455-sdio.bin
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed
  to install/upgrade: trying to overwrite
  '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in
  package linux-firmware-raspi2 3-0ubuntu2

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

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

[Bug 1918013] Update Released

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

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

Title:
  package linux-firmware 1.194 [modified:
  lib/firmware/brcm/brcmfmac43430-sdio.bin
  lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt
  lib/firmware/brcm/brcmfmac43455-sdio.bin
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed
  to install/upgrade: trying to overwrite
  '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in
  package linux-firmware-raspi2 3-0ubuntu2

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

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

[Bug 1920141] Re: [SRU] openvswitch 2.13.3 / linking changes in DPDK 19.11.x

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package openvswitch - 2.13.3-0ubuntu0.20.10.1

---
openvswitch (2.13.3-0ubuntu0.20.10.1) groovy; urgency=medium

  [ James Page ]
  * New upstream point release (LP: #1920141, LP: #1907686):
- d/p/*: Refresh including drop of part of patch as equivalent
  changes included in point release.
- Dropped security patches, included in release:
  + CVE-2015-8011.patch
  + CVE-2020-27827.patch
  + CVE-2020-35498.patch
  * Add BD on libdbus-1-dev to resolve linking issues for DPDK builds due
to changes in DPDK.
  * d/control: Set minimum version of libdpdk-dev to avoid build
failures with 19.11.6-0ubuntu0.20.10.1.

  [ Frode Nordahl ]
  * Fix recording of FQDN/hostname on startup (LP: #1915829):
- d/p/ovs-dev-ovs-ctl-Allow-recording-hostname-separately.patch: Cherry
  pick of committed upstream fix to support skip of hostname
  configuration on ovs-vswitchd/ovsdb-server startup.
- d/openvswitch-switch.ovs-record-hostname.service: Record hostname in
  Open vSwitch after network-online.target using new systemd unit.
- d/openvswitch-switch.ovs-vswitchd.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.ovsdb-server.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.service: Add `Also` reference to
  ovs-record-hostname.service so that the service is enabled on install.
- d/rules: Add `ovs-record-hostname.service` to package build.

 -- James Page   Wed, 24 Mar 2021 08:46:06 +

** Changed in: openvswitch (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

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

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

** Changed in: openvswitch (Ubuntu Focal)
   Status: Fix Committed => 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/1920141

Title:
  [SRU] openvswitch 2.13.3 / linking changes in DPDK 19.11.x

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

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

[Bug 1918013] Re: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi, 3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.10.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.10.1) groovy; urgency=medium

  * Pull in latest from hirsute (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

** Changed in: linux-firmware-raspi2 (Ubuntu Groovy)
   Status: Fix Committed => 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/1918013

Title:
  package linux-firmware 1.194 [modified:
  lib/firmware/brcm/brcmfmac43430-sdio.bin
  lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt
  lib/firmware/brcm/brcmfmac43455-sdio.bin
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt
  lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed
  to install/upgrade: trying to overwrite
  '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in
  package linux-firmware-raspi2 3-0ubuntu2

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

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

[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.10.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.10.1) groovy; urgency=medium

  * Pull in latest from hirsute (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

** Changed in: linux-firmware-raspi2 (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

** Bug watch added: github.com/raspberrypi/linux/issues #3849
   https://github.com/raspberrypi/linux/issues/3849

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

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

Title:
  SRU bluetooth fixes and CVEs to focal and groovy

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

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

[Bug 1925971] Re: SRU bluetooth fixes and CVEs to focal and groovy

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware-raspi2 -
4-0ubuntu0~20.04.1

---
linux-firmware-raspi2 (4-0ubuntu0~20.04.1) focal; urgency=medium

  * Backport to focal (LP: #1925971)
- Add aliases and diversions for brcmfmac43455 configuration on the
  Raspberry Pi Compute Module 4, and 400 (LP: #1912905)

- Added diversions for all wifi firmware blobs (LP: #1918013)
- New upstream boot firmware release, 1.20210303
- New upstream bluetooth firmware release, 1.2-4+rpt8

  [ Phil Elwell ]
  - Second Spectra fix for CYW43455 (CVE-2020-10370)
- Original firmware name: BCM4345C0_003.001.025.0174.0342.hcd

- New upstream wifi firmware release, 1:20190114-1+rpt11

  [ Serge Schneider ]
  - Update CYW43455 firmware
- brcm/brcmfmac43455-sdio.bin 7.45.229
- See: https://github.com/raspberrypi/linux/issues/3849

 -- William 'jawn-smith' Wilson   Fri, 23
Apr 2021 16:05:55 -0500

** Changed in: linux-firmware-raspi2 (Ubuntu Focal)
   Status: Fix Committed => 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/1925971

Title:
  SRU bluetooth fixes and CVEs to focal and groovy

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

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

[Bug 1925971] Update Released

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

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

Title:
  SRU bluetooth fixes and CVEs to focal and groovy

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

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

[Bug 1920141] Re: [SRU] openvswitch 2.13.3 / linking changes in DPDK 19.11.x

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package openvswitch - 2.13.3-0ubuntu0.20.04.1

---
openvswitch (2.13.3-0ubuntu0.20.04.1) focal; urgency=medium

  [ James Page ]
  * New upstream point release (LP: #1920141, LP: #1907686).
  * Dropped security patches, included in release:
- CVE-2015-8011.patch
- CVE-2020-27827.patch
- CVE-2020-35498.patch
  * Add BD on libdbus-1-dev to resolve linking issues for DPDK builds due
to changes in DPDK.
  * d/control: Set minimum version of libdpdk-dev to avoid build
failures with 19.11.6-0ubuntu0.20.04.1.

  [ Frode Nordahl ]
  * Fix recording of FQDN/hostname on startup (LP: #1915829):
- d/p/ovs-dev-ovs-ctl-Allow-recording-hostname-separately.patch: Cherry
  pick of committed upstream fix to support skip of hostname
  configuration on ovs-vswitchd/ovsdb-server startup.
- d/openvswitch-switch.ovs-record-hostname.service: Record hostname in
  Open vSwitch after network-online.target using new systemd unit.
- d/openvswitch-switch.ovs-vswitchd.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.ovsdb-server.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.service: Add `Also` reference to
  ovs-record-hostname.service so that the service is enabled on install.
- d/rules: Add `ovs-record-hostname.service` to package build.

 -- James Page   Wed, 24 Mar 2021 08:46:41 +

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

Title:
  [SRU] openvswitch 2.13.3 / linking changes in DPDK 19.11.x

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

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

[Bug 1907686] Update Released

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

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

Title:
  ovn: instance unable to retrieve metadata

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-chassis/+bug/1907686/+subscriptions

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

[Bug 1907686] Re: ovn: instance unable to retrieve metadata

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package openvswitch - 2.13.3-0ubuntu0.20.10.1

---
openvswitch (2.13.3-0ubuntu0.20.10.1) groovy; urgency=medium

  [ James Page ]
  * New upstream point release (LP: #1920141, LP: #1907686):
- d/p/*: Refresh including drop of part of patch as equivalent
  changes included in point release.
- Dropped security patches, included in release:
  + CVE-2015-8011.patch
  + CVE-2020-27827.patch
  + CVE-2020-35498.patch
  * Add BD on libdbus-1-dev to resolve linking issues for DPDK builds due
to changes in DPDK.
  * d/control: Set minimum version of libdpdk-dev to avoid build
failures with 19.11.6-0ubuntu0.20.10.1.

  [ Frode Nordahl ]
  * Fix recording of FQDN/hostname on startup (LP: #1915829):
- d/p/ovs-dev-ovs-ctl-Allow-recording-hostname-separately.patch: Cherry
  pick of committed upstream fix to support skip of hostname
  configuration on ovs-vswitchd/ovsdb-server startup.
- d/openvswitch-switch.ovs-record-hostname.service: Record hostname in
  Open vSwitch after network-online.target using new systemd unit.
- d/openvswitch-switch.ovs-vswitchd.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.ovsdb-server.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.service: Add `Also` reference to
  ovs-record-hostname.service so that the service is enabled on install.
- d/rules: Add `ovs-record-hostname.service` to package build.

 -- James Page   Wed, 24 Mar 2021 08:46:06 +

** Changed in: openvswitch (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

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

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

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

Title:
  ovn: instance unable to retrieve metadata

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ovn-chassis/+bug/1907686/+subscriptions

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

[Bug 1915829] Update Released

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

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

Title:
  FQDN / hostname recorded in OVSDB is unreliable

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

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

[Bug 1915829] Re: FQDN / hostname recorded in OVSDB is unreliable

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package openvswitch - 2.13.3-0ubuntu0.20.10.1

---
openvswitch (2.13.3-0ubuntu0.20.10.1) groovy; urgency=medium

  [ James Page ]
  * New upstream point release (LP: #1920141, LP: #1907686):
- d/p/*: Refresh including drop of part of patch as equivalent
  changes included in point release.
- Dropped security patches, included in release:
  + CVE-2015-8011.patch
  + CVE-2020-27827.patch
  + CVE-2020-35498.patch
  * Add BD on libdbus-1-dev to resolve linking issues for DPDK builds due
to changes in DPDK.
  * d/control: Set minimum version of libdpdk-dev to avoid build
failures with 19.11.6-0ubuntu0.20.10.1.

  [ Frode Nordahl ]
  * Fix recording of FQDN/hostname on startup (LP: #1915829):
- d/p/ovs-dev-ovs-ctl-Allow-recording-hostname-separately.patch: Cherry
  pick of committed upstream fix to support skip of hostname
  configuration on ovs-vswitchd/ovsdb-server startup.
- d/openvswitch-switch.ovs-record-hostname.service: Record hostname in
  Open vSwitch after network-online.target using new systemd unit.
- d/openvswitch-switch.ovs-vswitchd.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.ovsdb-server.service: Pass `--no-record-hostname`
  option to `ovs-ctl` to delegate recording of hostname to the separate
  service.
- d/openvswitch-switch.service: Add `Also` reference to
  ovs-record-hostname.service so that the service is enabled on install.
- d/rules: Add `ovs-record-hostname.service` to package build.

 -- James Page   Wed, 24 Mar 2021 08:46:06 +

** Changed in: openvswitch (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

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

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

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

Title:
  FQDN / hostname recorded in OVSDB is unreliable

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

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

[Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04

2021-05-17 Thread Robert Dinse
I accidentally saved the reboot image attachment before I completed the 
comment, so that's where
it hangs.  This time I only waited about a minute and a half before holding 
down control+alt+del to force the reboot, but I've walked away for an hour and 
let it sit, it does not finish beyond this point.

Strangely reboot and shutdown work but not systemctl reboot.

Tried deleting tor to see if it was causing issues, got past thermald
but still hung, see logs2.


** Attachment added: "systemctl reboot after removing tor."
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+attachment/5498330/+files/logs2

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

Title:
  systemctl reboot hangs the machine under hirsute 21.04

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

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

[Bug 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package python-apt - 2.2.0~ubuntu0.21.04.1

---
python-apt (2.2.0~ubuntu0.21.04.1) hirsute; urgency=medium

  * Upload to hirsute; changes since 2.1.7ubuntu2:
- Annotate test dependencies with  (Closes: #980719)
- Mirror list updates
- debfile: Pass `Name` instead of `Binary` to ExtractTar.
  Passing the binary causes it to fail trying to find the `false`
  compressor when a binary for a given compressor is not installed.
  (LP: #1926437)
- debian/gbp.conf: Branch name is main

python-apt (2.2.0) unstable; urgency=medium

  [ Helmut Grohne ]
  * Annotate test dependencies with  (Closes: #980719)

  [ Julian Andres Klode ]
  * debian/rules: Re-enable PIE hardening
  * Mirror list updates
  * debfile: Pass `Name` instead of `Binary` to ExtractTar.
Passing the binary causes it to fail trying to find the `false`
compressor when a binary for a given compressor is not installed.
(LP: #1926437)
  * debian/gbp.conf: Branch name is main

 -- Julian Andres Klode   Thu, 29 Apr 2021 15:20:13
+0200

** Changed in: python-apt (Ubuntu Hirsute)
   Status: Fix Committed => 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/1926437

Title:
  [SRU] Backport zstd support, fix bug in python-apt

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

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

[Bug 1927334] Update Released

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

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

Title:
  [SRU] libreoffice 7.1.3 for hirsute

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

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

[Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04

2021-05-17 Thread Robert Dinse
I accidentally saved the reboot image attachment before I completed the 
comment, so that's where
it hangs.  This time I only waited about a minute and a half before holding 
down control+alt+del to force the reboot, but I've walked away for an hour and 
let it sit, it does not finish beyond this point.

Strangely reboot and shutdown work but not systemctl reboot.

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

Title:
  systemctl reboot hangs the machine under hirsute 21.04

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

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

[Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04

2021-05-17 Thread Robert Dinse
** Attachment added: "Picture of Monitor at please reboot hangs."
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+attachment/5498329/+files/reboot.png

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

Title:
  systemctl reboot hangs the machine under hirsute 21.04

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

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

[Bug 1928564] Re: systemctl reboot hangs the machine under hirsute 21.04

2021-05-17 Thread Robert Dinse
** Attachment added: "Log of what happened after I typed systemctl reboot"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928564/+attachment/5498328/+files/logs

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

Title:
  systemctl reboot hangs the machine under hirsute 21.04

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

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

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-05-17 Thread Steve Langasek
** Description changed:

  [Impact]
  
   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on arm64
  with grub-efi-arm64 (a dependency of grub-efi-arm64-signed) installed
  
   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on amd64
  with grub-efi-amd64 (an ORed dependency of grub-efi-amd64-signed)
  installed.
  
   * This results in newly installed kernels not getting added to grub.cfg
  and thus upon reboot one does not boot into the new kernel.
  
   * In later series these scripts moved to grub2-common, which is why
  they are absent in the backported grub-efi-* packages.  They should be
  restored to these packages in the backport.
  
  [Test Plan]
  
   * Install new grubs
  
-  * If testing on arm64 ensure that grub-efi-arm64 is not installed; and
- grub-efi-arm64-signed is installed.
- 
-  * If testing on amd64 ensure that grub-efi-amd64 and grub-pc are not
- installed; and grub-efi-amd64-signed is installed.
+  * If testing on amd64 ensure that grub-efi-amd64 is installed, not
+ grub-pc.
  
   * Install a new kernel that was not installed before
  
   * Observe that grub.cfg is regenerated and new kernel is present
  
   * Remove an old kernel
  
   * Observe that grub.cfg is regenerated and new kernel is removed from
  grub.cfg
  
  [Where problems could occur]
  
   * These are conffiles. Although nobody should modify them, care should
  be taken when moving conffiles around.
  
  [Other Info]
  
   * First reported by klebers

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

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

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

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

[Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

2021-05-17 Thread Brian Murray
I tested and upgrade from a Bionic system to Focal using do-release-
upgrade -p and as you can see in the attached screenshot the "Inhibiting
until Ctrl+C is pressed" message no longer appears. So I'm setting this
to verification-done.

** Attachment added: "bug-1898026-focal-verification.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898026/+attachment/5498327/+files/bug-1898026-focal-verification.png

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

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

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

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

[Bug 1928397] Re: ensure python is marked for removal when upgrading from 18.04 to 20.04

2021-05-17 Thread Brian Murray
** 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/1928397

Title:
  ensure python is marked for removal when upgrading from 18.04 to 20.04

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

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

[Bug 1928592] Re: xfdesktop-settings (part of xfce4-settings) - not able to change background folder from default /usr/share/xfce4/backdrops/

2021-05-17 Thread kjur
After choosing the directory I have to select also a picture (even if random 
wallpaper selection is enabled). Then the a directory change works fine.
So the bug can be closed.
SOLVED!

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

Title:
  xfdesktop-settings (part of xfce4-settings) - not able to change
  background folder from default /usr/share/xfce4/backdrops/

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

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

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-05-17 Thread Steve Langasek
** Description changed:

  [Impact]
  
   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on arm64
- with grub-efi-arm64-signed installed, without grub-efi-arm64.
+ with grub-efi-arm64 (a dependency of grub-efi-arm64-signed) installed
  
   * /etc/kernel/{postinst.d,postrm.d}/zz-update-grub missing on amd64
- with grub-efi-amd64-signed installed without grub-pc or grub-efi-amd64.
+ with grub-efi-amd64 (an ORed dependency of grub-efi-amd64-signed)
+ installed.
  
   * This results in newly installed kernels not getting added to grub.cfg
  and thus upon reboot one does not boot into the new kernel.
  
-  * In later series these scripts moved to grub2-common. Maybe we should
- move these to grub2-common in bionic and earlier too, for compatibility
- with onegrub. Or alternatively grub2-signed should ship these in grub-
- efi-{amd64,arm64}-signed packages too.
+  * In later series these scripts moved to grub2-common, which is why
+ they are absent in the backported grub-efi-* packages.  They should be
+ restored to these packages in the backport.
  
  [Test Plan]
  
   * Install new grubs
  
-  * If testing on arm64 ensure that grub-efi-arm64 is not installed; and
+  * If testing on arm64 ensure that grub-efi-arm64 is not installed; and
  grub-efi-arm64-signed is installed.
  
-  * If testing on amd64 ensure that grub-efi-amd64 and grub-pc are not
+  * If testing on amd64 ensure that grub-efi-amd64 and grub-pc are not
  installed; and grub-efi-amd64-signed is installed.
  
   * Install a new kernel that was not installed before
  
   * Observe that grub.cfg is regenerated and new kernel is present
  
   * Remove an old kernel
  
   * Observe that grub.cfg is regenerated and new kernel is removed from
  grub.cfg
  
  [Where problems could occur]
  
   * These are conffiles. Although nobody should modify them, care should
  be taken when moving conffiles around.
  
  [Other Info]
  
   * First reported by klebers

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

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

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

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

[Bug 1928397] Re: ensure python is marked for removal when upgrading from 18.04 to 20.04

2021-05-17 Thread Brian Murray
Additionally, the 7 duplicates of the is bug were able to upgrade using
the version of the release upgrader from -proposed.

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

Title:
  ensure python is marked for removal when upgrading from 18.04 to 20.04

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

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

[Bug 1923111] Re: Azure Ubuntu 18.04.5 LTS hit a bug when running 'do-release-upgrade'

2021-05-17 Thread Brian Murray
*** This bug is a duplicate of bug 1928397 ***
https://bugs.launchpad.net/bugs/1928397

** This bug has been marked a duplicate of bug 1928397
   ensure python is marked for removal when upgrading from 18.04 to 20.04

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

Title:
  Azure Ubuntu 18.04.5 LTS hit a bug when running 'do-release-upgrade'

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

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

[Bug 1925457] Re: impossible to upgrade from 18.04 to 20.04

2021-05-17 Thread Brian Murray
*** This bug is a duplicate of bug 1928397 ***
https://bugs.launchpad.net/bugs/1928397

** This bug has been marked a duplicate of bug 1928397
   ensure python is marked for removal when upgrading from 18.04 to 20.04

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

Title:
  impossible to upgrade from 18.04 to 20.04

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

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

[Bug 1925821] Re: do-release-upgrade 18 to 20 LTS failed

2021-05-17 Thread Brian Murray
*** This bug is a duplicate of bug 1928397 ***
https://bugs.launchpad.net/bugs/1928397

** This bug has been marked a duplicate of bug 1928397
   ensure python is marked for removal when upgrading from 18.04 to 20.04

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

Title:
  do-release-upgrade 18 to 20 LTS failed

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

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

[Bug 1928111] Re: python depencies block upgrade from 18.04 towards 20.04

2021-05-17 Thread Brian Murray
*** This bug is a duplicate of bug 1928397 ***
https://bugs.launchpad.net/bugs/1928397

** This bug is no longer a duplicate of bug 1928101
   sudo do-release-upgrade fails 18.04-20.04
** This bug has been marked a duplicate of bug 1928397
   ensure python is marked for removal when upgrading from 18.04 to 20.04

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

Title:
  python depencies block upgrade from 18.04 towards 20.04

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

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

[Bug 1928446] Re: trying to upgrade to new release

2021-05-17 Thread Brian Murray
*** This bug is a duplicate of bug 1928397 ***
https://bugs.launchpad.net/bugs/1928397

** This bug has been marked a duplicate of bug 1928397
   ensure python is marked for removal when upgrading from 18.04 to 20.04

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

Title:
  trying to upgrade to new release

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

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

[Bug 1928674] Re: grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

2021-05-17 Thread Steve Langasek
** Summary changed:

- due to a new recommends grub-efi-arm64-signed is installed which does not 
have postinst.d script
+ grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

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

Title:
  grub-efi-amd64 from grub2-unsigned has lost kernel/postinst.d script

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

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

[Bug 1926858] Re: on azure upgraded from 16 to 18, now can not upgrade from 18 to 20

2021-05-17 Thread Brian Murray
*** This bug is a duplicate of bug 1928397 ***
https://bugs.launchpad.net/bugs/1928397

** This bug has been marked a duplicate of bug 1928397
   ensure python is marked for removal when upgrading from 18.04 to 20.04

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

Title:
  on azure upgraded from 16 to 18, now can not upgrade from 18 to 20

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

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

[Bug 1928249] Re: Ubuntu Server Upgrade 18.04 to 20.04

2021-05-17 Thread Brian Murray
*** This bug is a duplicate of bug 1928397 ***
https://bugs.launchpad.net/bugs/1928397

** This bug has been marked a duplicate of bug 1928397
   ensure python is marked for removal when upgrading from 18.04 to 20.04

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

Title:
  Ubuntu Server Upgrade 18.04 to 20.04

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

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

[Bug 1928601] Re: Ubuntu fails to start by default after upgrade 18.04 to 20.04 in virtual machine

2021-05-17 Thread Reijo Korhonen
I can run 'apport-collect 1928601' in the virtual machine, if I boot
using series-4 kernel, but does it give any information why series-5
kernel panics? Please tell if helps, if I run apport-collect 1928601' in
series-4 kernel.

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

Title:
  Ubuntu fails to start by default after upgrade 18.04 to 20.04 in
  virtual machine

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

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

[Bug 1928728] [NEW] package elpa-magit 2.99.0.git0957.ge8c7bd03-1 failed to install/upgrade: el subproceso instalado paquete elpa-magit script post-installation devolvió el código de salida de error 2

2021-05-17 Thread Carlos Martin
Public bug reported:

bug with ubuntu 21

ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: elpa-magit 2.99.0.git0957.ge8c7bd03-1
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
Date: Sun May 16 17:51:29 2021
ErrorMessage: el subproceso instalado paquete elpa-magit script 
post-installation devolvió el código de salida de error 2
InstallationDate: Installed on 2021-05-16 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.9ubuntu1
 apt  2.2.3
SourcePackage: magit
Title: package elpa-magit 2.99.0.git0957.ge8c7bd03-1 failed to install/upgrade: 
el subproceso instalado paquete elpa-magit script post-installation devolvió el 
código de salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package hirsute

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

Title:
  package elpa-magit 2.99.0.git0957.ge8c7bd03-1 failed to
  install/upgrade: el subproceso instalado paquete elpa-magit script
  post-installation devolvió el código de salida de error 2

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

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

[Bug 1927491] Re: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute

2021-05-17 Thread James Falcon
Attach file nocloud-lxd-sru-21.2-3.txt.

** Attachment added: "nocloud-lxd-sru-21.2-3.txt"
   
https://bugs.launchpad.net/bugs/1927491/+attachment/5498311/+files/nocloud-lxd-sru-21.2-3.txt

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

Title:
  sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute

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

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

[Bug 1927491] Re: sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute

2021-05-17 Thread James Falcon
Attach file nocloud-nocloud-kvm-sru-21.2-3.txt.

** Attachment added: "nocloud-nocloud-kvm-sru-21.2-3.txt"
   
https://bugs.launchpad.net/bugs/1927491/+attachment/5498312/+files/nocloud-nocloud-kvm-sru-21.2-3.txt

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

Title:
  sru cloud-init (21.1-19 to 21.2-3) Bionic, Focal, Groovy, and Hirsute

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

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

[Bug 1928601] Re: Ubuntu fails to start by default after upgrade 18.04 to 20.04 in virtual machine

2021-05-17 Thread Reijo Korhonen
When virtual machine's kernel panics in the boot, it not possiblr run
apport-collect 1928601 any more, I'm afraid.

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

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

Title:
  Ubuntu fails to start by default after upgrade 18.04 to 20.04 in
  virtual machine

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

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

[Bug 1928725] [NEW] package k3b-data (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/HTML/en/k3b/index.cache.bz2', which is also in package k3b:i386 0.11.5-1

2021-05-17 Thread Carson Wilcox
Public bug reported:

Errors were encountered while processing:
 /tmp/apt-dpkg-install-fVlwNq/06-k3b-data_19.12.3-0ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: k3b-data (not installed)
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon May 17 17:43:44 2021
ErrorMessage: trying to overwrite '/usr/share/doc/HTML/en/k3b/index.cache.bz2', 
which is also in package k3b:i386 0.11.5-1
InstallationDate: Installed on 2021-03-22 (56 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: k3b
Title: package k3b-data (not installed) failed to install/upgrade: trying to 
overwrite '/usr/share/doc/HTML/en/k3b/index.cache.bz2', which is also in 
package k3b:i386 0.11.5-1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package k3b-data (not installed) failed to install/upgrade: trying to
  overwrite '/usr/share/doc/HTML/en/k3b/index.cache.bz2', which is also
  in package k3b:i386 0.11.5-1

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

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

[Bug 1928674] Re: due to a new recommends grub-efi-arm64-signed is installed which does not have postinst.d script

2021-05-17 Thread Steve Langasek
And it's easier to reintroduce the conffiles to grub-efi-amd64.

** Package changed: grub2-signed (Ubuntu) => grub2-unsigned (Ubuntu)

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

Title:
  due to a new recommends grub-efi-arm64-signed is installed which does
  not have postinst.d script

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

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

[Bug 1928723] [NEW] fails to install on 20.04 LTS

2021-05-17 Thread Aramís Segovia Noriega
Public bug reported:


Release:
$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

Expected behavior: the package installs successfully

What happened:

$ sudo apt install steam
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 steam:i386 : Depends: libgl1-mesa-dri:i386 (>= 17.3) but it is not going to be 
installed or
   libtxc-dxtn0:i386 but it is not installable
  Depends: libgl1-mesa-glx:i386 but it is not going to be installed
  Depends: libgpg-error0:i386 (>= 1.10) but it is not going to be 
installed
  Depends: libudev1:i386 but it is not going to be installed
  Depends: libxcb-dri3-0:i386 (>= 1.11.1) but it is not going to be 
installed
  Depends: libxinerama1:i386 (>= 2:1.1.1) but it is not going to be 
installed
  Depends: libc6:i386 (>= 2.15) but it is not going to be installed
  Depends: libstdc++6:i386 (>= 4.8) but it is not going to be 
installed
  Depends: libx11-6:i386 but it is not going to be installed
  Recommends: libxss1:i386 but it is not going to be installed
  Recommends: mesa-vulkan-drivers:i386 but it is not going to be 
installed
E: Unable to correct problems, you have held broken packages.

** Affects: steam (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/1928723

Title:
  fails to install on 20.04 LTS

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

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

[Bug 1928674] Re: due to a new recommends grub-efi-arm64-signed is installed which does not have postinst.d script

2021-05-17 Thread Steve Langasek
The bug description here is all wrong.  grub-efi-amd64-signed depends on
grub-pc | grub-efi-amd64; you never have grub-efi-amd64-signed without
one of these.  The regression is because grub-efi-amd64 from
grub2-unsigned has dropped the conffiles, expecting them to be provided
by the grub2-common which it depends on; but we still have the old
grub2-common from grub2 source which does not ship these conffiles.

We must either have grub-efi-amd64 reintroduce the conffiles in stable
series, or add them to grub2-common.

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

Title:
  due to a new recommends grub-efi-arm64-signed is installed which does
  not have postinst.d script

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

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

[Bug 1751923] Re: [SRU]_heal_instance_info_cache periodic task bases on port list from nova db, not from neutron server

2021-05-17 Thread Jorge Niedbalski
** Description changed:

  [Impact]
  
  * During periodic task _heal_instance_info_cache the instance_info_caches are 
not updated using instance port_ids taken from neutron, but from nova db.
  * This causes that existing VMs to loose their network interfaces after 
reboot.
  
  [Test Plan]
  
  * This bug is reproducible on Bionic/Queens clouds.
  
  1) Deploy the following Juju bundle: https://paste.ubuntu.com/p/HgsqZfsDGh/
- 2) Run the following script: https://paste.ubuntu.com/p/DrFcDXZGSt/
+ 2) Run the following script: https://paste.ubuntu.com/p/c4VDkqyR2z/
  3) If the script finishes with "Port not found" , the bug is still present.
  
  [Where problems could occur]
  
  ** No specific regression potential has been identified.
  ** Check the other info section ***
- 
  
  [Other Info]
  
  How it looks now?
  =
  
  _heal_instance_info_cache during crontask:
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/compute/manager.py#L6525
  
  is using network_api to get instance_nw_info (instance_info_caches):
  
  \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0try:
  
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0#
 Call to network API to get instance info.. this will
  
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0#
 force an update to the instance's info_cache
  
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0self.network_api.get_instance_nw_info(context,
 instance)
  
  self.network_api.get_instance_nw_info() is listed below:
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/network/neutronv2/api.py#L1377
  
  and it uses _build_network_info_model() without networks and port_ids
  parameters (because we're not adding any new interface to instance):
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/network/neutronv2/api.py#L2356
  
  Next: _gather_port_ids_and_networks() generates the list of instance
  networks and port_ids:
  
  \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0networks, port_ids = 
self._gather_port_ids_and_networks(
  
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0context,
 instance, networks, port_ids, client)
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/network/neutronv2/api.py#L2389-L2390
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/network/neutronv2/api.py#L1393
  
  As we see that _gather_port_ids_and_networks() takes the port list from
  DB:
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/objects/instance.py#L1173-L1176
  
  And thats it. When we lose a port its not possible to add it again with this 
periodic task.
  The only way is to clean device_id field in neutron port object and re-attach 
the interface using `nova interface-attach`.
  
  When the interface is missing and there is no port configured on compute
  host (for example after compute reboot) - interface is not added to
  instance and from neutron point of view port state is DOWN.
  
  When the interface is missing in cache and we reboot hard the instance -
  its not added as tapinterface in xml file = we don't have the network on
  host.
  
  Steps to reproduce
  ==
  1. Spawn devstack
  2. Spawn VM inside devstack with multiple ports (for example also from 2 
different networks)
  3. Update the DB row, drop one interface from interfaces_list
  4. Hard-Reboot the instance
  5. See that nova list shows instance without one address, but nova 
interface-list shows all 
addresseshttps://launchpad.net/~niedbalski/+archive/ubuntu/lp1751923/+packages
  6. See that one port is missing in instance xml files
  7. In theory the _heal_instance_info_cache should fix this things, it relies 
on memory, not on the fresh list of instance ports taken from neutron.
  
  Reproduced Example
  ==
  1. Spawn VM with 1 private network port
  nova boot --flavor m1.small --image cirros-0.3.5-x86_64-disk --nic 
net-name=private  test-2
  2. Attach ports to have 2 private and 2 public interfaces
  nova list:
  | a64ed18d-9868-4bf0-90d3-d710d278922d | test-2 | ACTIVE | -  | 
Running | public=2001:db8::e, 172.24.4.15, 2001:db8::c, 172.24.4.16; 
private=fdda:5d77:e18e:0:f816:3eff:fee8:, 10.0.0.3, 
fdda:5d77:e18e:0:f816:3eff:fe53:231c, 10.0.0.5 |
  
  So we see 4 ports:
  stack@mjozefcz-devstack-ptg:~$ nova interface-list 
a64ed18d-9868-4bf0-90d3-d710d278922d
  
++--+--+---+---+
  | Port State | Port ID  | Net ID  
 | 

[Bug 1928397] Re: ensure python is marked for removal when upgrading from 18.04 to 20.04

2021-05-17 Thread Brian Murray
I tested an upgrade from Bionic to Focal with 'do-release-upgrade -p'
using the apt-clone file mentioned in the bug description and an upgrade
was successfully calculated.

ubuntu@grown-crow:~$ head /var/log/dist-upgrade/main.log
2021-05-17 21:02:59,243 INFO Using config files '['./DistUpgrade.cfg.bionic', 
'/etc/update-manager/release-upgrades.d/ubuntu-advantage-upgrades.cfg']'
2021-05-17 21:02:59,244 INFO uname information: 'Linux grown-crow 
5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11 UTC 2021 x86_64'
2021-05-17 21:02:59,495 INFO apt version: '1.6.13'
2021-05-17 21:02:59,495 INFO python version: '3.6.9 (default, Jan 26 2021, 
15:33:00) 
[GCC 8.4.0]'
2021-05-17 21:02:59,498 INFO release-upgrader version '20.04.33' started
2021-05-17 21:02:59,502 INFO locale: 'en_US' 'UTF-8'
2021-05-17 21:02:59,566 WARNING estimate_kernel_initrd_size_in_boot() returned 
'0' for kernel?
2021-05-17 21:02:59,566 WARNING estimate_kernel_initrd_size_in_boot() returned 
'0' for initrd?
2021-05-17 21:02:59,579 DEBUG Using 'DistUpgradeViewText' view
ubuntu@grown-crow:~$ grep "Do you want to start" 
/var/log/dist-upgrade/screenlog.0
Do you want to start the upgrade?

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

Title:
  ensure python is marked for removal when upgrading from 18.04 to 20.04

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

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

[Bug 1901294] Re: nouveau timeout and system lockup

2021-05-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-nouveau (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/1901294

Title:
  nouveau timeout and system lockup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1901294/+subscriptions

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

[Bug 1928721] [NEW] rpc-gssd fails to fallback on unsuccessful principal search

2021-05-17 Thread Jack Polk
Public bug reported:

Our team is currently using rpc-gssd for NFS shares that are secured
with Kerberos. We are using an Active Directory server as our KDC.
Something that we are trying out as a potential solution to naming
conflicts is the use of a computer name in AD that does not match the
machine's local hostname. We have ensured that the appropriate DNS
records exist for this alternate hostname.

After using adcli to join the machine to the domain, we get the
following principals:

root@demo:~# klist -ke
Keytab name: FILE:/etc/krb5.keytab
KVNO Principal
 --
   2 CORP-DEMO$@CORP.NET (arcfour-hmac) 
   2 CORP-DEMO$@CORP.NET (aes128-cts-hmac-sha1-96) 
   2 CORP-DEMO$@CORP.NET (aes256-cts-hmac-sha1-96) 
   2 demo.corp@corp.net (arcfour-hmac) 
   2 demo.corp@corp.net (aes128-cts-hmac-sha1-96) 
   2 demo.corp@corp.net (aes256-cts-hmac-sha1-96) 
   2 host/corp-d...@corp.net (arcfour-hmac) 
   2 host/corp-d...@corp.net (aes128-cts-hmac-sha1-96) 
   2 host/corp-d...@corp.net (aes256-cts-hmac-sha1-96) 
   2 host/demo.corp@corp.net (arcfour-hmac) 
   2 host/demo.corp@corp.net (aes128-cts-hmac-sha1-96) 
   2 host/demo.corp@corp.net (aes256-cts-hmac-sha1-96) 
   2 RestrictedKrbHost/corp-d...@corp.net (arcfour-hmac) 
   2 RestrictedKrbHost/corp-d...@corp.net (aes128-cts-hmac-sha1-96) 
   2 RestrictedKrbHost/corp-d...@corp.net (aes256-cts-hmac-sha1-96) 
   2 RestrictedKrbHost/demo.corp@corp.net (arcfour-hmac) 
   2 RestrictedKrbHost/demo.corp@corp.net (aes128-cts-hmac-sha1-96) 
   2 RestrictedKrbHost/demo.corp@corp.net (aes256-cts-hmac-sha1-96)

Unfortunately, when attempting to mount, rpc.gssd throws the following
errors:

root@demo:~# rpc.gssd -vvv -f
...
handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2' (nfs/clnt44)   


krb5_use_machine_creds: uid 0 tgtname (null)
Full hostname for 'storage.corp.net' is 'storage.corp.net'
Full hostname for 'demo.corp.net' is 'demo.corp.net'
No key table entry found for demo$@CORP.NET while getting keytab entry for 
'demo$@CORP.NET'
No key table entry found for DEMO$@CORP.NET while getting keytab entry for 
'DEMO$@CORP.NET'
No key table entry found for root/demo.corp@corp.net while getting keytab 
entry for 'root/demo.corp@corp.net'
No key table entry found for nfs/demo.corp@corp.net while getting keytab 
entry for 'nfs/demo.corp@corp.net'
Success getting keytab entry for 'host/demo.corp@corp.net'
WARNING: Client 'host/demo.corp@corp.net' not found in Kerberos database 
while getting initial ticket for principal 'host/demo.corp@corp.net' using 
keytab 'FILE
:/etc/krb5.keytab'
ERROR: No credentials found for connection to server storage.corp.net
doing error downcall
...

After some brief debugging, we found that when removing the principals
that are causing the failure the mount works fine:

root@demo:~# klist -ke
Keytab name: FILE:/etc/krb5.keytab
KVNO Principal
 --
   2 CORP-DEMO$@CORP.NET (arcfour-hmac) 
   2 CORP-DEMO$@CORP.NET (aes128-cts-hmac-sha1-96) 
   2 CORP-DEMO$@CORP.NET (aes256-cts-hmac-sha1-96) 
   2 demo.corp@corp.net (arcfour-hmac) 
   2 demo.corp@corp.net (aes128-cts-hmac-sha1-96) 
   2 demo.corp@corp.net (aes256-cts-hmac-sha1-96) 
   2 host/corp-d...@corp.net (arcfour-hmac) 
   2 host/corp-d...@corp.net (aes128-cts-hmac-sha1-96) 
   2 host/corp-d...@corp.net (aes256-cts-hmac-sha1-96) 
   2 RestrictedKrbHost/d...@corp.net (arcfour-hmac) 
   2 RestrictedKrbHost/d...@corp.net (aes128-cts-hmac-sha1-96) 
   2 RestrictedKrbHost/d...@corp.net (aes256-cts-hmac-sha1-96) 
   2 RestrictedKrbHost/demo.corp@corp.net (arcfour-hmac) 
   2 RestrictedKrbHost/demo.corp@corp.net (aes128-cts-hmac-sha1-96) 
   2 RestrictedKrbHost/demo.corp@corp.net (aes256-cts-hmac-sha1-96) 

root@demo:~# rpc.gssd -vvv -f
...
handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2' (nfs/clnt4f)
krb5_use_machine_creds: uid 0 tgtname (null)
Full hostname for 'storage.corp.net' is 'storage.corp.net'
Full hostname for 'demo.corp.net' is 'demo.corp.net'
No key table entry found for demo$@CORP.NET while getting keytab entry for 
'demo$@CORP.NET'
Success getting keytab entry for 'CORP-DEMO$@CORP.NET'
INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_CORP.NET' are good until 
1621320566
INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_CORP.NET' are good until 
1621320566
creating tcp client for server storage.corp.net
DEBUG: port already set to 2049
creating context with server n...@storage.corp.net
doing downcall: lifetime_rec=36000 acceptor=n...@storage.corp.net
...

The solution seems straightforward: don't assume because a principal has
been found that the principal is sufficient or allow for users to
manually specify which principal to use 

Re: [Bug 1928434] Re: shim-signed does not boot on EFI 2.40 by Apple

2021-05-17 Thread Steve Langasek
On Mon, May 17, 2021 at 03:23:45PM -, Dimitri John Ledkov wrote:
> See
> https://github.com/lcp/mokutil/commit/03bb7af4a84c39f2417fd14ef20b11b2e8d1ad51

> Is this something you can compile yourself, or do you need me to provide
> you with an updated mokutil package?

I have provided a mokutil package with the fix here:

  https://launchpad.net/~vorlon/+archive/ubuntu/ppa

Please install it by running:

  sudo add-apt-repository ppa:vorlon/ppa
  sudo apt install mokutil

and then 'sudo mokutil --set-verbosity true' should work.

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

Title:
  shim-signed does not boot on EFI 2.40 by Apple

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

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

[Bug 1912060] Re: [SRU] caribou: Segfault (as regression of xorg CVE-2020-25712 fix) cause security issue for cinnamon

2021-05-17 Thread Launchpad Bug Tracker
This bug was fixed in the package caribou - 0.4.21-7ubuntu0.20.10.1

---
caribou (0.4.21-7ubuntu0.20.10.1) groovy-security; urgency=high

  * SECURITY UPDATE: Fix segfaults with recent versions of Xorg that
causes cinnamon to crash (LP: #1912060)
  * Fix build with newer versions of valac

 -- Joshua Peisach   Mon, 22 Mar 2021
18:04:23 -0400

** Changed in: caribou (Ubuntu Groovy)
   Status: In Progress => 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/1912060

Title:
  [SRU] caribou: Segfault (as regression of xorg CVE-2020-25712 fix)
  cause security issue for cinnamon

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

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

[Bug 1923209] Re: [sos4.1][Policy|Ubuntu] Upload no longer working

2021-05-17 Thread Eric Desrochers
[VERIFICATION GROOVY]

I ran the following command:
# sos report -o ubuntu --upload # The important bit here is the --upload 
option, the rest is just to generate the sos archive.

The above command line output:
"


Attempting upload to Canonical Support File Server
Uploaded archive successfully
"

I also confirmed that the sos archive was present on the Canonical sftp
under the right location as it should and as it was before this
regression occurs.

- Eric

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

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

Title:
  [sos4.1][Policy|Ubuntu] Upload no longer working

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

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

[Bug 1923209] Re: [sos4.1][Policy|Ubuntu] Upload no longer working

2021-05-17 Thread Eric Desrochers
[VERIFICATION FOCAL]

I ran the following command:
# sos report -o ubuntu --upload # The important bit here is the --upload 
option, the rest is just to generate the sos archive.

The above command line output:
"


Attempting upload to Canonical Support File Server
Uploaded archive successfully
"

I also confirmed that the sos archive was present on the Canonical sftp
under the right location as it should and as it was before this
regression occurs.

- Arif

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

Title:
  [sos4.1][Policy|Ubuntu] Upload no longer working

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

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

[Bug 1923209] Re: [sos4.1][Policy|Ubuntu] Upload no longer working

2021-05-17 Thread Eric Desrochers
[VERIFICATION FOCAL]

I ran the following command:
# sos report -o ubuntu --upload # The important bit here is the --upload 
option, the rest is just to generate the sos archive.

The above command line output:
"


Attempting upload to Canonical Support File Server
Uploaded archive successfully
"

I also confirmed that the sos archive was present on the Canonical sftp
under the right location as it should and as it was before this
regression occurs.

- Eric

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

Title:
  [sos4.1][Policy|Ubuntu] Upload no longer working

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

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

[Bug 1925517] Re: Update PKA firmware image

2021-05-17 Thread Meriton Tuli
Using Kernel 5.4.0-1012-bluefield this Issue is fixed

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

Title:
  Update PKA firmware image

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

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

[Bug 1925514] Re: Add tests to check TRNG block in PKA HW

2021-05-17 Thread Meriton Tuli
Correction: Using Kernel 5.4.0-1012-bluefield *

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

Title:
  Add tests to check TRNG block in PKA HW

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

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

[Bug 1925508] Re: Update PKA driver version

2021-05-17 Thread Meriton Tuli
Correction: Using Kernel 5.4.0-1012-bluefield*

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

Title:
  Update PKA driver version

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

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

[Bug 1926994] Re: Backport TLS Bond

2021-05-17 Thread Dan Jurgens
** 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/1926994

Title:
  Backport TLS Bond

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

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

[Bug 1927244] Re: Fix NAT IPv6 offload mangling

2021-05-17 Thread Dan Jurgens
** 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/1927244

Title:
  Fix NAT IPv6 offload mangling

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

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

[Bug 1927374] Re: Do offload refresh when requested

2021-05-17 Thread Dan Jurgens
** 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/1927374

Title:
  Do offload refresh when requested

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

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

[Bug 1751923] Re: [SRU]_heal_instance_info_cache periodic task bases on port list from nova db, not from neutron server

2021-05-17 Thread Jorge Niedbalski
** Patch added: "lp1751923_bionic.debdiff"
   
https://bugs.launchpad.net/nova/+bug/1751923/+attachment/5498309/+files/lp1751923_bionic.debdiff

** Description changed:

  [Impact]
  
  * During periodic task _heal_instance_info_cache the instance_info_caches are 
not updated using instance port_ids taken from neutron, but from nova db.
  * This causes that existing VMs to loose their network interfaces after 
reboot.
  
  [Test Plan]
  
  * This bug is reproducible on Bionic/Queens clouds.
  
  1) Deploy the following Juju bundle: https://paste.ubuntu.com/p/HgsqZfsDGh/
  2) Run the following script: https://paste.ubuntu.com/p/DrFcDXZGSt/
  3) If the script finishes with "Port not found" , the bug is still present.
  
  [Where problems could occur]
  
+ ** No specific regression potential has been identified.
  ** Check the other info section ***
  
  
  [Other Info]
  
  How it looks now?
  =
  
  _heal_instance_info_cache during crontask:
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/compute/manager.py#L6525
  
  is using network_api to get instance_nw_info (instance_info_caches):
  
  \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0try:
  
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0#
 Call to network API to get instance info.. this will
  
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0#
 force an update to the instance's info_cache
  
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0self.network_api.get_instance_nw_info(context,
 instance)
  
  self.network_api.get_instance_nw_info() is listed below:
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/network/neutronv2/api.py#L1377
  
  and it uses _build_network_info_model() without networks and port_ids
  parameters (because we're not adding any new interface to instance):
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/network/neutronv2/api.py#L2356
  
  Next: _gather_port_ids_and_networks() generates the list of instance
  networks and port_ids:
  
  \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0networks, port_ids = 
self._gather_port_ids_and_networks(
  
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0context,
 instance, networks, port_ids, client)
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/network/neutronv2/api.py#L2389-L2390
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/network/neutronv2/api.py#L1393
  
  As we see that _gather_port_ids_and_networks() takes the port list from
  DB:
  
  
https://github.com/openstack/nova/blob/ef4000a0d326deb004843ee51d18030224c5630f/nova/objects/instance.py#L1173-L1176
  
  And thats it. When we lose a port its not possible to add it again with this 
periodic task.
  The only way is to clean device_id field in neutron port object and re-attach 
the interface using `nova interface-attach`.
  
  When the interface is missing and there is no port configured on compute
  host (for example after compute reboot) - interface is not added to
  instance and from neutron point of view port state is DOWN.
  
  When the interface is missing in cache and we reboot hard the instance -
  its not added as tapinterface in xml file = we don't have the network on
  host.
  
  Steps to reproduce
  ==
  1. Spawn devstack
  2. Spawn VM inside devstack with multiple ports (for example also from 2 
different networks)
  3. Update the DB row, drop one interface from interfaces_list
  4. Hard-Reboot the instance
- 5. See that nova list shows instance without one address, but nova 
interface-list shows all addresses
+ 5. See that nova list shows instance without one address, but nova 
interface-list shows all 
addresseshttps://launchpad.net/~niedbalski/+archive/ubuntu/lp1751923/+packages
  6. See that one port is missing in instance xml files
  7. In theory the _heal_instance_info_cache should fix this things, it relies 
on memory, not on the fresh list of instance ports taken from neutron.
  
  Reproduced Example
  ==
  1. Spawn VM with 1 private network port
  nova boot --flavor m1.small --image cirros-0.3.5-x86_64-disk --nic 
net-name=private  test-2
  2. Attach ports to have 2 private and 2 public interfaces
  nova list:
  | a64ed18d-9868-4bf0-90d3-d710d278922d | test-2 | ACTIVE | -  | 
Running | public=2001:db8::e, 172.24.4.15, 2001:db8::c, 172.24.4.16; 
private=fdda:5d77:e18e:0:f816:3eff:fee8:, 10.0.0.3, 
fdda:5d77:e18e:0:f816:3eff:fe53:231c, 10.0.0.5 |
  
  So we see 4 ports:
  stack@mjozefcz-devstack-ptg:~$ nova interface-list 
a64ed18d-9868-4bf0-90d3-d710d278922d
  

[Bug 1751923] Re: [SRU]_heal_instance_info_cache periodic task bases on port list from nova db, not from neutron server

2021-05-17 Thread Jorge Niedbalski
Hello,

I've prepared a PPA for testing the proposed patch on B/Queens
https://launchpad.net/~niedbalski/+archive/ubuntu/lp1751923/+packages

Attached is the debdiff for bionic.

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

Title:
  [SRU]_heal_instance_info_cache periodic task bases on port list from
  nova db, not from neutron server

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

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

[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

2021-05-17 Thread Ivan D
Tested on: Ubuntu 21.04
Package: evolution-data-server 3.40.1-2 (from Impish-proposed)

There aren't packages for hursuit (21.04) but I just tried the impish
(21.10) package and works.

Thanks again

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions

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

  1   2   3   >