[Bug 1940043] Re: Upgrade from OVN 20.03 to newer OVN version will cause data plane outage
** Changed in: charm-ovn-chassis Status: Fix Committed => Fix Released ** Changed in: charm-layer-ovn Status: Fix Committed => Fix Released ** Changed in: charm-ovn-dedicated-chassis 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/1940043 Title: Upgrade from OVN 20.03 to newer OVN version will cause data plane outage To manage notifications about this bug go to: https://bugs.launchpad.net/charm-layer-ovn/+bug/1940043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944424] Re: AppArmor causing HA routers to be in backup state on wallaby-focal
** Changed in: charm-neutron-gateway 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/1944424 Title: AppArmor causing HA routers to be in backup state on wallaby-focal To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-gateway/+bug/1944424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943120] Re: interface not removed
I Tested netplan.io 0.103-0ubuntu5~20.04.2 inside a fresh Focal LXD container: $ lxc launch ubuntu-daily:focal ff $ lxc exec ff bash => Enabled focal-proposed & installed/upgraded netplan.io root@ff:~# dpkg -l | grep netplan ii libnetplan0:amd64 0.103-0ubuntu5~20.04.2 ii netplan.io 0.103-0ubuntu5~20.04.2 root@ff:~# netplan set network.bridges.br54.dhcp4=false root@ff:~# netplan get # check that br54 is present network: bridges: br54: dhcp4: false ethernets: eth0: dhcp4: true root@ff:~# netplan apply root@ff:~# ip link show br54 && echo OK 3: br54: mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/ether 06:0f:64:90:38:53 brd ff:ff:ff:ff:ff:ff OK root@ff:~# mkdir -p /tmp/np_backup/etc/ && cp -r /etc/netplan /tmp/np_backup/etc/ root@ff:~# netplan set network.bridges.br54=null root@ff:~# netplan get # check that br54 is NOT present network: ethernets: eth0: dhcp4: true netplan apply --state /tmp/np_backup root@ff:~# ip link show br54 && echo ERROR Device "br54" does not exist. In accordance with https://wiki.ubuntu.com/NetplanUpdates I'm also attaching the full autopkgtest logs for those builds: https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_amd64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_arm64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_armhf.log https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_ppc64el.log https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_s390x.log ** 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/1943120 Title: interface not removed To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1943120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942930] Re: Unset a subtree crashes
I Tested netplan.io 0.103-0ubuntu5~20.04.2 inside a fresh Focal LXD container:
$ lxc launch ubuntu-daily:focal ff
$ lxc exec ff bash
=> Enabled focal-proposed & installed/upgraded netplan.io
root@ff:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~20.04.2
ii netplan.io 0.103-0ubuntu5~20.04.2
root@ff:~# rm /etc/netplan/*
root@ff:~# cat /etc/netplan/00-ethernets.yaml
network:
version: 2
ethernets:
all-en:
dhcp4: true
match:
name: en*
all-eth:
dhcp4: true
match:
name: eth*
root@ff:~# netplan get
network:
ethernets:
all-en:
dhcp4: true
match:
name: en*
all-eth:
dhcp4: true
match:
name: eth*
version: 2
root@ff:~# netplan set network.ethernets=null
root@ff:~# netplan get
{}
In accordance with https://wiki.ubuntu.com/NetplanUpdates I'm also attaching
the full autopkgtest logs for those builds:
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_amd64.log
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_arm64.log
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_armhf.log
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_ppc64el.log
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/focal_s390x.log
** 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/1942930
Title:
Unset a subtree crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1942930/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948460] [NEW] unable to upgrade into 21.04 to 21.40
Public bug reported: unable to upgrade 21.04 to 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.17 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CrashDB: ubuntu Date: Fri Oct 22 18:39:42 2021 InstallationDate: Installed on 2021-10-11 (11 days ago) InstallationMedia: PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to hirsute on 2021-10-22 (0 days ago) VarLogDistupgradeAptlog: Log time: 2021-10-22 18:36:24.859420 Log time: 2021-10-22 18:36:46.726175 Log time: 2021-10-22 18:39:24.882622 Log time: 2021-10-22 18:39:45.475218 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948460 Title: unable to upgrade into 21.04 to 21.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1948460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943120] Re: interface not removed
I Tested netplan.io 0.103-0ubuntu5~21.04.2 inside a fresh Hirsute LXD container: $ lxc launch ubuntu-daily:hirsute hh $ lxc exec hh bash => Enabled hirsute-proposed & installed/upgraded netplan.io root@hh:~# dpkg -l | grep netplan ii libnetplan0:amd64 0.103-0ubuntu5~21.04.2 ii netplan.io 0.103-0ubuntu5~21.04.2 root@hh:~# netplan set network.bridges.br54.dhcp4=false root@hh:~# netplan get # check that br54 is present network: bridges: br54: dhcp4: false ethernets: eth0: dhcp4: true root@hh:~# netplan apply root@hh:~# ip link show br54 && echo OK 3: br54: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 7a:32:79:fc:e6:a2 brd ff:ff:ff:ff:ff:ff OK root@hh:~# mkdir -p /tmp/np_backup/etc/ && cp -r /etc/netplan /tmp/np_backup/etc/ root@hh:~# netplan set network.bridges.br54=null root@hh:~# netplan get # check that br54 is NOT present network: ethernets: eth0: dhcp4: true root@hh:~# netplan apply --state /tmp/np_backup root@hh:~# ip link show br54 && echo ERROR Device "br54" does not exist. In accordance with https://wiki.ubuntu.com/NetplanUpdates I'm also attaching the full autopkgtest logs for those builds: https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_amd64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_arm64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_armhf.log https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_ppc64el.log https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_s390x.log The mentioned autopkgtest regression is gone after a retry. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943120 Title: interface not removed To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1943120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942930] Re: Unset a subtree crashes
Indeed, a `netplan set network=null` would basically be the same as `rm /etc/netplan/*.yaml`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942930 Title: Unset a subtree crashes To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1942930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942930] Re: Unset a subtree crashes
I Tested netplan.io 0.103-0ubuntu5~21.04.2 inside a fresh Hirsute LXD container:
$ lxc launch ubuntu-daily:hirsute hh
$ lxc exec hh bash
=> Enabled hirsute-proposed & installed/upgraded netplan.io
root@hh:~# dpkg -l | grep netplan
ii libnetplan0:amd64 0.103-0ubuntu5~21.04.2
ii netplan.io 0.103-0ubuntu5~21.04.2
root@hh:~# cat /etc/netplan/00-ethernets.yaml
network:
version: 2
ethernets:
all-en:
dhcp4: true
match:
name: en*
all-eth:
dhcp4: true
match:
name: eth*
root@hh:~# netplan get
network:
ethernets:
all-en:
dhcp4: true
match:
name: en*
all-eth:
dhcp4: true
match:
name: eth*
version: 2
root@hh:~# netplan set network.ethernets=null
root@hh:~# netplan get
{}
In accordance with https://wiki.ubuntu.com/NetplanUpdates I'm also attaching
the full autopkgtest logs for those builds:
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_amd64.log
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_arm64.log
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_armhf.log
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_ppc64el.log
https://git.launchpad.net/~slyon/+git/files/tree/LP1943120/hirsute_s390x.log
The mentioned autopkgtest regression is gone after a retry.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942930
Title:
Unset a subtree crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1942930/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
Once it's in proposed: $ sudo apt-add-repository -p proposed $ sudo apt install linux-raspi And then if you want to remove proposed again: $ sudo apt-add-repository -r -p proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948439] Re: Not able to create image with cinder as storage backend
The attachment "lp1948439_focal.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948439 Title: Not able to create image with cinder as storage backend To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1948439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948055] Re: Landscape Repository Profile Lost After Access Group Change
I reported this on the the wrong thread. I re-posted under the correct thread. https://bugs.launchpad.net/landscape/+bug/1948455 You can close this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948055 Title: Landscape Repository Profile Lost After Access Group Change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1948055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948357] Re: sshd have no USER_LOGOUT audit event
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssh (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/1948357 Title: sshd have no USER_LOGOUT audit event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1948357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948428] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
** Package changed: ubuntu => nvidia-graphics-drivers-340 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948428 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1948428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903848] Re: Latest kernel update to "5.4.0-53-generic" = Internal audio, USB webcam no longer working
7446.610760] USB Video Class driver (1.1.1) [ 7461.313217] usb 1-1: 3:1: cannot get freq at ep 0x82 [ 7463.017338] usb 1-1: 3:1: cannot get freq at ep 0x82 [ 7469.563231] usb 1-1: timeout: still 10 active urbs on EP #82 unable to access my usb webcam. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903848 Title: Latest kernel update to "5.4.0-53-generic" = Internal audio, USB webcam no longer working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1903848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels
Thanks. Could you post back with step by step instructions for a semi- technical user on how to install the fix kernel when it lands in proposed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946368 Title: HDMI output freezes under current/proposed impish kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1946368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881184] Re: Blender ist compiled without Open Image Denoise
** Changed in: blender (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881184 Title: Blender ist compiled without Open Image Denoise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blender/+bug/1881184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947818] Re: The fans are constantly whirring on ThinkPad P14S Gen 2
Installed the 21.10 on P14s Gen 2i, the kernel is 5.13.0-19-generic, BIOS is N34ET44W(1.44), and EC is N34HT35W, I could not reproduce this issue. coretemp-isa- Adapter: ISA adapter Package id 0: +29.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+28.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+25.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+24.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+24.0°C (high = +100.0°C, crit = +100.0°C) thinkpad-isa- Adapter: ISA adapter fan1: 0 RPM CPU: +29.0°C GPU: N/A temp3:+26.0°C temp4: +0.0°C temp5:+28.0°C temp6:+29.0°C temp7:+29.0°C temp8:N/A -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947818 Title: The fans are constantly whirring on ThinkPad P14S Gen 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948439] Re: Not able to create image with cinder as storage backend
** Tags added: sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948439 Title: Not able to create image with cinder as storage backend To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1948439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948449] [NEW] package linux-image-5.11.0-37-generic (not installed) failed to install/upgrade: installed linux-image-5.11.0-37-generic package pre-removal script subprocess returned error exit s
Public bug reported: I'm not sure what happened - I just got a notice that something happened. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-37-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 19 14:45:11 2021 ErrorMessage: installed linux-image-5.11.0-37-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2020-07-04 (475 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-37-generic (not installed) failed to install/upgrade: installed linux-image-5.11.0-37-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (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/1948449 Title: package linux-image-5.11.0-37-generic (not installed) failed to install/upgrade: installed linux-image-5.11.0-37-generic package pre- removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1948449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948339] Re: Logon screen can be bypassed using various shortcuts
Thanks :) I haven't registered a CVE yet and I'm waiting for final confirmation which components are causing the described issue. Happy to contribute to the ArcticaProject issue tracker directly. As you also mentioned I can confirm that the affected arctica-greeter version is present in the following versions of Ubuntu Mate: Ubuntu Mate 20.10 - Groovy Gorilla Ubuntu Mate 21.04 - Hirsute Hippo Ubuntu Mate 21.10 - Impish Indri It doesn't seem to work for 20.04 - Focal Fossa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947925] Re: Seagate IronWolf 125 support
Is this a problem specific to the Pi platform or ARM in general? Is the SSD self-powered via USB or externally powered? Also, you logged this against linux-raspi2 which seems wrong since it doesn't support the Pi 4. Which release and kernel are you running (lsb_release -a, uname -a)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947925 Title: Seagate IronWolf 125 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1947925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948351] Re: linux ADT test_bpf failure with linux/5.4.0-90.101
Tested on P8 node entei with 4.15.0-162-generic Kernel 4.15.0-162-generic + Source 4.15.0-162-generic [12008.662733] test_bpf: #145 ALU_MOD_K: 3 % 1 = 0 jited:1 ret 3 != 0 FAIL (1 times) [12008.663071] test_bpf: #148 ALU64_MOD_K: 3 % 1 = 0 jited:1 ret 3 != 0 FAIL (1 times) [12012.150242] test_bpf: Summary: 340 PASSED, 2 FAILED, [334/334 JIT'ed] Note that the test environment is not clean as I don't have any available P8 node at hand (gulpin cannot be deployed with Bionic for some reason) so I am re-using the ubuntu_qrt_apparmor job, which is hanging for the moment. Also, this test output needs to be improved, I have filed bug 1948448 for this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948351 Title: linux ADT test_bpf failure with linux/5.4.0-90.101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948439] Re: Not able to create image with cinder as storage backend
** Patch added: "lp1948439_focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/python-glance-store/+bug/1948439/+attachment/5535216/+files/lp1948439_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948439 Title: Not able to create image with cinder as storage backend To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1948439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948439] Re: Not able to create image with cinder as storage backend
** Patch added: "lp1948439_ussuri.debdiff" https://bugs.launchpad.net/ubuntu/+source/python-glance-store/+bug/1948439/+attachment/5535217/+files/lp1948439_ussuri.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948439 Title: Not able to create image with cinder as storage backend To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1948439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948439] Re: Not able to create image with cinder as storage backend
Hi SRU team, Uploaded debdiff's for focal and UCA ussuri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948439 Title: Not able to create image with cinder as storage backend To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1948439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948439] Re: Not able to create image with cinder as storage backend
The fix for LP#1870289 are available in UCA Victoria and further. ** Description changed: On Ussuri, creation of image with cinder as glance storage backend fails. Reproduction Steps: 1. Deploy cloud environment - focal ussuri 2. Change the following configuration in /etc/glance/glance-api.conf to setup Cinder as Storage backend to Glance. [DEFAULT] enabled_backends = local:file, cinder:cinder [glance_store] default_backend = cinder Restart glance-api service systemctl restart glance-api.service 3. Upload a cirros image to glance openstack image create --container-format bare --disk-format qcow2 --file /home/ubuntu/images/cirros-0.4.0-x86_64-disk.img test The above command throws an exception. Exception in /var/log/glance/glance-api.log 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder [req-282b09b7-3db4-44f7-937c-b7c2fb71453b da9d04a5652c41b98126e1a2b1ce9601 1c133b846e4e4948873aa3af847c23df - 4d430c7d67e0416a95e38b10aad4fc5f 4d430c7d67e0416a95e38b10aad4fc5f] Exception while accessing to cinder volume 7553d4cd-d315-4f97-8abe-f375864fa84a.: TypeError: temporary_chown() got an unexpected keyword argument 'backend' 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder Traceback (most recent call last): 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder File "/usr/lib/python3/dist-packages/glance_store/_drivers/cinder.py", line 575, in _open_cinder_volume 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder with self.temporary_chown( 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder File "/usr/lib/python3.8/contextlib.py", line 240, in helper 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder return _GeneratorContextManager(func, args, kwds) 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder File "/usr/lib/python3.8/contextlib.py", line 83, in __init__ 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder self.gen = func(*args, **kwds) 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder TypeError: temporary_chown() got an unexpected keyword argument 'backend' 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder - Package used: python3-glance-store/focal-updates,now 2.0.0-0ubuntu2 all [installed,automatic] Analysis: The method signature and the calling method args seems different for function temporary_chown https://opendev.org/openstack/glance_store/src/tag/2.0.0/glance_store/_drivers/cinder.py#L458 https://opendev.org/openstack/glance_store/src/tag/2.0.0/glance_store/_drivers/cinder.py#L573 This is fixed in upstream as part of https://bugs.launchpad.net/glance-store/+bug/1870289 The bug fix for LP#1870289 need to be SRU'ed to Ubuntu python3-glance-store packages. + + ++ + + [Impact] + Not able to upload an image to glance + + [Test Case] + 1. Deploy cloud with focal ussuri + 2. Configure cinder as glance storage backend + + Ensure the following configurations in glance-api.conf + [DEFAULT] + enabled_backends = local:file, cinder:cinder + [glance_store] + default_backend = cinder + + Restart glance-api service + systemctl restart glance-api.service + + 3. Upload an image to glance + openstack image create --container-format bare --disk-format qcow2 --file /home/ubuntu/images/cirros-0.4.0-x86_64-disk.img test + + [Regression Potential] + The fix is available in upstream and CI unit and functional tempest test cases are successful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948439 Title: Not able to create image with cinder as storage backend To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1948439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947723] Re: /dev/ttyUSB? port lost on upgrading to 21.10
It's a new package in Impish and going forward, it doesn't exist in older series. The reason being that we enabled a whole bunch of new drivers in Impish and don't want to blow up the size of linux-modules. As a result, some other non-essential drivers moved to the new package. ** Changed in: linux-raspi (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/1947723 Title: /dev/ttyUSB? port lost on upgrading to 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1947723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929923] Re: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function
Okay, thanks Aleksandra for having a look at an env. with the latest level and for providing feedback on this! (so this bug is closed) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929923 Title: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948446] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1948446 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948446 Title: failure is observed in remapping BARs 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929923] Comment bridged from LTC Bugzilla
--- Comment From aleksandra.pa...@de.ibm.com 2021-10-22 06:55 EDT--- I have talked with our team and we have not seen the problem on the last supported Ubuntu level yet. So you, from our perspective, can cancel the Bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929923 Title: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948446] [NEW] failure is observed in remapping BARs 20.04
Public bug reported: In Ubuntu, CONFIG_PCI_REALLOC_ENABLE_AUTO config option is enabled by default. As a result, OS tries to remap BAR addresses and a failure is observed in remapping BARs. The issue is observed only when the SRIOV flag is disabled in BIOS. The issue can be worked by disabling BAR remapping bypassing “pci=realloc=off” kernel parameter. It has been tested with positive results. Dmesg also shows the following messages indicating that the setting up of standard BAR registers for the GPGPUs has failed. Jun 21 06:14:47 R750XAS kernel: [ 70.384361] pci :17:00.0: BAR 1: no space for [mem size 0x20 64bit pref] Jun 21 06:14:47 R750XAS kernel: [ 70.476810] pci :17:00.0: BAR 1: failed to assign [mem size 0x20 64bit pref] Jun 21 06:14:47 R750XAS kernel: [ 71.041877] pci :17:00.0: BAR 0: no space for [mem size 0x0100] Jun 21 06:14:47 R750XAS kernel: [ 71.120838] pci :17:00.0: BAR 0: failed to assign [mem size 0x0100] ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948446 Title: failure is observed in remapping BARs 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
Thanks Dariusz. Are you intending to fix gnome-shell-extension-desktop-icons in Focal also then, to restore the behaviour? If so, then shouldn't these be uploaded together with a Breaks clause to make sure users get both at the same time? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
Could someone having the issue set log-level=debug in /etc/pulse/daemon.conf , restart and add the journalctl log after getting the bug? ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945632] Re: Re-enable DEBUG_INFO_BTF where it was dissabled
This bug is awaiting verification that the linux- hwe-5.11/5.11.0-40.44~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945632 Title: Re-enable DEBUG_INFO_BTF where it was dissabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948444] [NEW] package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-38-generic package pre-removal script subprocess returned error e
Public bug reported: I am facing open afs problem ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 22 15:28:00 2021 ErrorMessage: installed linux-image-5.11.0-38-generic package pre-removal script subprocess returned error exit status 255 InstallationDate: Installed on 2021-05-10 (164 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-signed-hwe-5.11 Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-38-generic package pre-removal script subprocess returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (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/1948444 Title: package linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 failed to install/upgrade: installed linux-image-5.11.0-38-generic package pre- removal script subprocess returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1948444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
This is actively being worked on - for those interested you can follow the progress in https://github.com/snapcore/snapd/pull/10836 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843937] Re: checkinstall makes the computer unbootable
Which version of Ubuntu did you use? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843937 Title: checkinstall makes the computer unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/1843937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start
I have the same issue: systemd-resolved: Failed to save link data /run/systemd/resolve/netif/3: Permission denied The netif folder is indeed owned by root. If I change the ownership to systemd-resolved and restart the service, there is no error but as soon as I reboot the system, the ownership is reverted to root and the error is back. Also, I searched the log for other resolved messages and found the error below as well: nm-dispatcher[4641]: /etc/network/if-up.d/resolved: 12: mystatedir: not found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896772 Title: systemd-resolved configures no Current Scopes on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948439] Re: Not able to create image with cinder as storage backend
** Also affects: python-glance-store (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Also affects: cloud-archive/ussuri Importance: Undecided Status: New ** Changed in: python-glance-store (Ubuntu) Assignee: (unassigned) => Hemanth Nakkina (hemanth-n) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948439 Title: Not able to create image with cinder as storage backend To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1948439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948439] [NEW] Not able to create image with cinder as storage backend
Public bug reported: On Ussuri, creation of image with cinder as glance storage backend fails. Reproduction Steps: 1. Deploy cloud environment - focal ussuri 2. Change the following configuration in /etc/glance/glance-api.conf to setup Cinder as Storage backend to Glance. [DEFAULT] enabled_backends = local:file, cinder:cinder [glance_store] default_backend = cinder Restart glance-api service systemctl restart glance-api.service 3. Upload a cirros image to glance openstack image create --container-format bare --disk-format qcow2 --file /home/ubuntu/images/cirros-0.4.0-x86_64-disk.img test The above command throws an exception. Exception in /var/log/glance/glance-api.log 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder [req-282b09b7-3db4-44f7-937c-b7c2fb71453b da9d04a5652c41b98126e1a2b1ce9601 1c133b846e4e4948873aa3af847c23df - 4d430c7d67e0416a95e38b10aad4fc5f 4d430c7d67e0416a95e38b10aad4fc5f] Exception while accessing to cinder volume 7553d4cd-d315-4f97-8abe-f375864fa84a.: TypeError: temporary_chown() got an unexpected keyword argument 'backend' 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder Traceback (most recent call last): 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder File "/usr/lib/python3/dist-packages/glance_store/_drivers/cinder.py", line 575, in _open_cinder_volume 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder with self.temporary_chown( 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder File "/usr/lib/python3.8/contextlib.py", line 240, in helper 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder return _GeneratorContextManager(func, args, kwds) 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder File "/usr/lib/python3.8/contextlib.py", line 83, in __init__ 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder self.gen = func(*args, **kwds) 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder TypeError: temporary_chown() got an unexpected keyword argument 'backend' 2021-10-20 06:34:34.894 279293 ERROR glance_store._drivers.cinder Package used: python3-glance-store/focal-updates,now 2.0.0-0ubuntu2 all [installed,automatic] Analysis: The method signature and the calling method args seems different for function temporary_chown https://opendev.org/openstack/glance_store/src/tag/2.0.0/glance_store/_drivers/cinder.py#L458 https://opendev.org/openstack/glance_store/src/tag/2.0.0/glance_store/_drivers/cinder.py#L573 This is fixed in upstream as part of https://bugs.launchpad.net/glance-store/+bug/1870289 The bug fix for LP#1870289 need to be SRU'ed to Ubuntu python3-glance-store packages. ** Affects: python-glance-store (Ubuntu) Importance: Undecided Status: New ** Tags: sts ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948439 Title: Not able to create image with cinder as storage backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-glance-store/+bug/1948439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948440] [NEW] "synaptics touchpad" not detected after system update october 20th
Public bug reported: after an update the touchpad stopped working and isnt detected in devices in the command line. laptop is lenovo V15. i think the linux wiki told me to send you this, but i dont really understand what im doing so that may be incorrect: fomorii@marvin:~$ cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0003 Vendor=413c Product=3010 Version=0110 N: Name="HID 413c:3010" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:413C:3010.0001/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0003 Vendor=04f2 Product=b624 Version=1428 N: Name="Integrated Camera: Integrated C" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input14 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=11" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input15 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=12" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input16 U: Uniq= H: Handlers=event16 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=0d8c Product=0014 Version=0100 N: Name="C-Media Electronics Inc. USB Headset" P: Phys=usb-:00:14.0-2/input3 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.3/0003:0D8C:0014.0002/input/input17 U: Uniq= H: Handlers=kbd event17 B: PROP=0 B: EV=13 B: KEY=e 0 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-38-lowlatency 5.11.0-38.42~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-lowlatency 5.11.22 Uname: Linux 5.11.0-38-lowlatency x86_64 ApportVersion: 2.20.11-
[Bug 1948438] [NEW] Printer kan niet worden gestart. Controleer de configuratie van uw printer
Public bug reported: My Canon MP499 printer is recognized, but if i try to use it in LibreOffice Writer, a message appears (see above). Using translate, it shows this message: Printer cannot be started. Check your printer's configuration fred@fred-Latitude-E6430:~$ lpstat fred@fred-Latitude-E6430:~$ lpstat -t scheduler is running no system default destination device for DCP-L3550CDW: dnssd://Brother%20DCP-L3550CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4dc9c43 device for MP495-series: usb://Canon/MP495%20series?serial=24F65A&interface=1 DCP-L3550CDW accepting requests since vr 23 jul 2021 12:55:49 CEST MP495-series accepting requests since vr 22 okt 2021 10:58:01 CEST printer DCP-L3550CDW is idle. enabled since vr 23 jul 2021 12:55:49 CEST printer MP495-series is idle. enabled since vr 22 okt 2021 10:58:01 CEST fred@fred-Latitude-E6430:~$ sudo service cups status [sudo] wachtwoord voor fred: ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├─ 977 /usr/sbin/cupsd -l ├─2129 /usr/lib/cups/notifier/dbus dbus:// └─4449 /usr/lib/cups/notifier/dbus dbus:// okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler. okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-16/16 (END)...skipping... ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: > Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago TriggeredBy: ● cups.path ● cups.socket Docs: man:cupsd(8) Main PID: 977 (cupsd) Tasks: 3 (limit: 9421) Memory: 24.9M CGroup: /system.slice/cups.service ├
[Bug 1843937] Re: checkinstall makes the computer unbootable
Just experienced the same problem also while installing emacs (2a0a368ddcd9b4eed067ddc114f3fb18b13bbe14) with sudo checkinstall --fstrans=no. The issue is that /lib -> usr/lib symlink is being replaced with a directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843937 Title: checkinstall makes the computer unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/1843937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843937] Re: checkinstall makes the computer unbootable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: checkinstall (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/1843937 Title: checkinstall makes the computer unbootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/1843937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948436] [NEW] Add RevID field to VPD info in EEPROM
Public bug reported: SRU Justification: [Impact] Currently, the VPD info stored in the EEPROM does not include a Rev ID. This field is incremented when a PN goes through minor HW changes. Sometimes, SW needs to differentiate the two versions of the card. Hence, this field should be supported in the EEPROM MFG partition. [Fix] EC (Engineering Changes) field is used to denote the HW Revision of a PN. Add it to the EEPROM MFG and provide a sysfs entry to access the same via mlx-bootctl. [Test Case] This field is typically programmed at the manufacturing step using the bfcfg tool which uses the write mechanism in the driver and then the MFG partition is locked. Reading the "rev" sysfs will show the current value. [Regression Potential] Can be considered minimum. ** Affects: linux-bluefield (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/1948436 Title: Add RevID field to VPD info in EEPROM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948351] Re: linux ADT test_bpf failure with linux/5.4.0-90.101
These are the BPF related changes between 5.4.0-89 and 5.4.0-90. Nothing where I would immediately think of causing division to go wrong... git log Ubuntu-5.4.0-89.100..origin/master-prep --grep="bpf" --oneline 760480fda833 selftests/bpf: Enlarge select() timeout for test_maps 5c85b4d0b051 selftests/bpf: Fix xdp_tx.c prog section name 0f84b7521f50 samples: bpf: Fix tracex7 error raised on the missing argument 8bc1bccb0744 bpf/tests: Do not PASS tests without actually testing the result 0885ac9bc408 bpf/tests: Fix copy-and-paste error in double word test 3801d5662248 netlink: Deal with ESRCH error in nlmsg_notify() ed5c6f4c1b06 bpf: Fix pointer arithmetic mask tightening under state pruning 884ec8412e0d bpf: verifier: Allocate idmap scratch in verifier env dd5342c1a35a bpf: Fix leakage due to insufficient speculative store bypass mitigation 5362e01b39f6 bpf: Introduce BPF nospec instruction for mitigating Spectre v4 329efcf517b2 bpf: Fix possible out of bound write in narrow load handling 9c56c222fb51 tcp: seq_file: Avoid skipping sk during tcp_seek_last_pos 481ad73a440e drm/amdgpu/acp: Make PM domain really work 42341fc22763 bpf: Fix potential memleak and UAF in the verifier. 53ace18dddea bpf: Fix a typo of reuseport map in bpf.h. 6f143214953f bpf: Fix cast to pointer from integer of different size warning b8e3620c71b7 bpf: Track contents of read-only maps as scalars -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948351 Title: linux ADT test_bpf failure with linux/5.4.0-90.101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948435] [NEW] imsm: After reboot spare devices are not placed in to different container.
Public bug reported: Description of problem: Distribution: UBUNTU 20.04, latest mdadm package mdadm/focal-updates,now 4.1-5ubuntu1. The expected behavior is that spares are going to different container after reboot. Currently it is possible that spare drive will be added to the container with existing volume. This a backport request for Focal distribution. How reproducible: The wrong behavior is based on the order of the assembled disks. It can be reproduced without reboot, with steps below. Steps to Reproduce: 1. Create container # mdadm -C /dev/md/imsm1 -n3 -e imsm /dev/nvme[0-1]n1 2.Create RAID1 # mdadm -C /dev/md/md1 -l1 -n2 /dev/imsm1 3.Add spare device to container # mdadm --add /dev/imsm1 /dev/nvme2n1 4. Add conf file with policy # echo "POLICY domain=RAID_DOMAIN_1 path=* metadata=imsm action=spare-same-slot" > /etc/mdadm.conf 5. Stop volume and container # mdadm -Ss 6. Assemble first device of volume incrementally # mdadm -I /dev/nvme0n1 7. Assemble spare device incrementally # mdadm -I /dev/nvme2n1 8. Assemble second device of volume incrementally # mdadm -I /dev/nvme1n1 Actual results: Volume is assembled, and spare device is moved to container with volume after assemble second volume device. Expected results: All spares goes to separate container Additional info: Patch that fixes the issue: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=69068584f9ed68b8b2736287a1c9863e11b741d5 ** Affects: mdadm (Ubuntu) Importance: Undecided Status: New ** Tags: vroc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948435 Title: imsm: After reboot spare devices are not placed in to different container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1948435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948434] [NEW] Check if secure boot is enabled with development keys
Public bug reported: SRU Justification: [Impact] Currently, there is no indication from mlx-bootctl when the user reads the lifecycle_state sysfs as to whether secure boot is enabled with development keys or production keys. In order to make this clear to the user, add a check in the driver. [Fix] Check the secure boot development mode status bit. If secure boot is enabled with the development key, then print it to the output buffer when lifecycle_state_show() is invoked. [Test Case] On a system in secure state, if it has been programmed with development keys, then reading the lifecycle_state sysfs entry in the mlx-bootctl driver should print a message that indicates the same. Similarly, a secure system which has been programmed with production keys must print the appropriate message when the lifecycle_state sysfs is read. [Regression Potential] Can be considered minimum. ** Affects: linux-bluefield (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/1948434 Title: Check if secure boot is enabled with development keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1948434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437359] Re: A PIDFILE is double-defined for the corosync-notifyd init script
** Changed in: corosync (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: corosync (Ubuntu Bionic) Importance: Low => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437359 Title: A PIDFILE is double-defined for the corosync-notifyd init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1437359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping
** Changed in: oem-priority/focal Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926547 Title: Add Dell Privacy Mic Mute Key mapping To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936826]
*** Bug 2016353 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936826 Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936826]
*** Bug 2016444 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936826 Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936826]
*** Bug 2016329 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936826 Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group() [st-focus-manager.c:199] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947833] Re: MAAS discovery gets failed and SUT enters into Intramfs mode
Hi Michael, I think the information from comment#1 is still necessary for clarifying this issue. In the other hand, if your ethernet chip is newer then probably doesn't work in focal-hwe kernel (if you could share more details as comment#1 then it will help to debug). you can check the driver whether working in initramfs shell. or changing it to hwe-edge to give it a try. or pick a RJ45 to USB adapter to deploy (r8152 usually stable in each kernel if you choose the production adapter). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947833 Title: MAAS discovery gets failed and SUT enters into Intramfs mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1947833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947311] Re: Cloud init ignores growpart off on impish for raspberry pi
Thanks, that's a good suggestion, but it didn't work. Can I just reassign this ticket to the linux-raspi project? ** Also affects: linux-raspi (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/1947311 Title: Cloud init ignores growpart off on impish for raspberry pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815278] Re: LyX restores the same cursor position wherever it was placed next time(s)
Hello Konstantin, I see that I never followed up on this bug. Does it still affect you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815278 Title: LyX restores the same cursor position wherever it was placed next time(s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/1815278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
After 5 years there's still no fix. This is so annoying. I'm now getting rid of all snap packages and installing deb variants instead. Finally I'll purge snap and if these weird decisions keep on going I'll also move to another distro. Common Canonical. Seriously? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948351] Re: linux ADT test_bpf failure with linux/5.4.0-90.101
BTW here is the test summary, it looks like we have 2 cases removed in 5.4.0-90. (in lib/test Test results: * Kernel: 5.4.0-89 + Source: 5.4.0-89 = Summary: 378 PASSED, 0 FAILED, [366/366 JIT'ed] * Kernel: 5.4.0-89 + Source: 5.4.0-90 = Summary: 378 PASSED, 0 FAILED, [366/366 JIT'ed] * Kernel: 5.4.0-90 + Source: 5.4.0-90 = Summary: 376 PASSED, 2 FAILED, [366/366 JIT'ed] * Kernel: 5.4.0-90 + Source: 5.4.0-89 = Summary: 376 PASSED, 2 FAILED, [366/366 JIT'ed] ** Also affects: linux (Ubuntu Focal) 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/1948351 Title: linux ADT test_bpf failure with linux/5.4.0-90.101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948428] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: i do not know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-38-generic Date: Thu Oct 21 17:51:52 2021 InstallationDate: Installed on 2020-07-21 (457 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: 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/1948428 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1948428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948417] [NEW] package texlive-lang-german (not installed) failed to install/upgrade: no se puede crear el nuevo fichero '/var/lib/dpkg/info/texlive-lang-german.list-new': Operación no permitida
Public bug reported: Also experimenting issues. Cannot install google chrome. Error that shows up: dpkg execution was interrupted, run <> manually to solve the problem. When I run that, I get another error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: texlive-lang-german (not installed) ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 22 09:41:33 2021 ErrorMessage: no se puede crear el nuevo fichero '/var/lib/dpkg/info/texlive-lang-german.list-new': Operación no permitida InstallationDate: Installed on 2021-10-08 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: texlive-lang Title: package texlive-lang-german (not installed) failed to install/upgrade: no se puede crear el nuevo fichero '/var/lib/dpkg/info/texlive-lang-german.list-new': Operación no permitida UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-lang (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/1948417 Title: package texlive-lang-german (not installed) failed to install/upgrade: no se puede crear el nuevo fichero '/var/lib/dpkg/info/texlive-lang- german.list-new': Operación no permitida To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1948417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947598] Re: can`t draw band structure
Do you mean input file that I got from vasp? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947598 Title: can`t draw band structure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p4vasp/+bug/1947598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938678] Re: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H
I dumped binary_bios_measurements on a production board (Aaeon EHL) and didn't see "UEFI Debug Mode" from the log. With snapd (2.53.1) and patched kernel snap, I can install UC20 with FDE enabled without any problem. For detailed log, please see attached file. --- Board: Aaeon UPN-EHL01 BIOS: UNEHAM0D 5.19 BIOS Release Date: 09/02/2021 ** Attachment added: "Aaeon-EHL.log" https://bugs.launchpad.net/intel/+bug/1938678/+attachment/5535135/+files/Aaeon-EHL.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938678 Title: [intel] [tgl-h][iotg] [hwe-tpm] Ubuntu Core hangs during bootup on TGL-H To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948044] Re: charon-systemd fails on raspberry pi systems under ubuntu 21.10
Looks like your kernel is missing required modules (xfrm_user etc.) or they were not automatically loaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948044 Title: charon-systemd fails on raspberry pi systems under ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1948044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948355] Re: Firefox settings font size dropdown flashes, hard to select
Firefox 91.0-1 Ubuntu 21.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948355 Title: Firefox settings font size dropdown flashes, hard to select To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948355] Re: Firefox settings font size dropdown flashes, hard to select
Firefox 93.0-1 Ubuntu 21.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948355 Title: Firefox settings font size dropdown flashes, hard to select To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948415] [NEW] cgroup-tools not compatible with cgroup2
Public bug reported: When launching cgroup commands like cgcreate after the upgrade to 21.10, the following error is printed: cgcreate: libcgroup initialization failed: Cgroup is not mounted The issue seems to be related to the libcgroup version, which does not support the now used cgroup2. Expected behavior: the cgroup-tools should be compatible with the cgroup version delivered with the distribution. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cgroup-tools 0.41-11 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 09:21:30 2021 InstallationDate: Installed on 2020-02-06 (623 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libcgroup UpgradeStatus: Upgraded to impish on 2021-10-18 (3 days ago) ** Affects: libcgroup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948415 Title: cgroup-tools not compatible with cgroup2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1948415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948377] Re: [linux-iot][F] USB: serial: pl2303: add support for PL2303HXN
** Description changed: [Impact] PL2303HXN is not supported by 5.4 kernel. - 5.5 kernel starts to support it. + 5.5 kernel starts to support it. so only SRU for focal 5.4 kernel. [Fix] Add support for PL2303HXN. [Test] Verified on hardware, use minicom to test serial port, it works fine. [Where problems could occur] It may break the pl2303 ttyUSBx. ** Changed in: linux (Ubuntu Focal) Assignee: Jesse Sung (wenchien) => (unassigned) ** Summary changed: - [linux-iot][F] USB: serial: pl2303: add support for PL2303HXN + [SRU][F] USB: serial: pl2303: add support for PL2303HXN ** Description changed: [Impact] PL2303HXN is not supported by 5.4 kernel. 5.5 kernel starts to support it. so only SRU for focal 5.4 kernel. [Fix] + Clean cherry-pick upstream commits. Add support for PL2303HXN. [Test] Verified on hardware, use minicom to test serial port, it works fine. [Where problems could occur] It may break the pl2303 ttyUSBx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948377 Title: [SRU][F] USB: serial: pl2303: add support for PL2303HXN To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1948377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948339] Re: Logon screen can be bypassed using various shortcuts
Upstream is now informed via https://github.com/ArcticaProject/arctica-greeter/issues/28 . I cited this bug there. Bastian Kanbach (bkanbach), you are welcome to add more comments there. ** Bug watch added: github.com/ArcticaProject/arctica-greeter/issues #28 https://github.com/ArcticaProject/arctica-greeter/issues/28 ** Bug watch added: github.com/canonical/lightdm/issues #214 https://github.com/canonical/lightdm/issues/214 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948410] [NEW] [nvidia] Software cursor in Wayland sessions (EGLStreams)
Public bug reported: Software cursor used in Wayland sessions (EGLStreams). To see it just add this to /etc/environment: CLUTTER_PAINT=damage-region and reboot. ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Low Status: Triaged ** Tags: impish nvidia nvidia-drm.modeset performance ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: New => Triaged ** Tags added: impish ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1980 https://gitlab.gnome.org/GNOME/mutter/-/issues/1980 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1980 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/1948410 Title: [nvidia] Software cursor in Wayland sessions (EGLStreams) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948339] Re: Logon screen can be bypassed using various shortcuts
Lightdm - https://github.com/canonical/lightdm/issues/214 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835340] Re: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications
** Description changed: Description: During run-time, the kernel can be notified of new/latent errors in two different ways: If an application trips over a latent/unknown error, and if the system has machine check recovery, then we will be notified via the mce handler, and the app will be killed. In this case, the kernel should take the chance to go clear-errors for that page, and re-online it so it can be used again in the future. If the 'patrol scrubber' discovers an error on a yet-to-be-accessed location, it can send an ACPI notification to the nfit driver. In this case, the kernel should go clear the error if the page is not in use. If it is in use, the application that has it mapped may need to killed as in case 1 above. This additional run-time handling of errors will augment (and be complimentary to) the init-time handling in userspace, and having both will give us the best possible coverage for media errors. - Target Release: 21.10 + Target Release: 22.04 Target Kernel: TBD ** Tags removed: intel-kernel-21.10 ** Tags added: intel-kernel-22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835340 Title: [HMEM] kmem: clear poison reported via mce or ACPI patrol scrub notifications To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
