[Bug 1335391] Re: etckeeper with git breaks update-manager
Thanks for your reply Borim, although it has a sad touch since you had to switch away. I've thrown a few more test servers of mine into using etckeeper, if there is anything left I'd hope they will expose a remaining issue. If nothing else happens that confirms the bug still exists the bug will auto-expired in ~60 days and then go to incomplete which is the right state. That is even more correct than setting fix released as have never explicitly found and fixed what it was back then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335391 Title: etckeeper with git breaks update-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1335391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935665] Re: open-vm-tools builds without fuse support when built with libfuse3-dev
Thanks Marco, have you seen that there are some licensing shenanigans to pass there? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935665 Title: open-vm-tools builds without fuse support when built with libfuse3-dev To manage notifications about this bug go to: https://bugs.launchpad.net/open-vm-tools/+bug/1935665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
I actually use Dash to Panel instead of the Ubuntu Dock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944799] [NEW] Crash on install Both server and desktop
Public bug reported: Crash of both server and desktop versions install crashes at enter your name. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.19 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 24 00:24:11 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944799 Title: Crash on install Both server and desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944797] [NEW] i am install os but bug found
Public bug reported: i am install os but bug found ubi-console-setup failed with exit code 139 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Patch added: "69b72c12-b856-4318-874a-b837030b7dd1.jpg" https://bugs.launchpad.net/bugs/1944797/+attachment/5527489/+files/69b72c12-b856-4318-874a-b837030b7dd1.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944797 Title: i am install os but bug found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944475] Re: DistUpgradeViewNonInteractive is now interactive
** Changed in: ubuntu-release-upgrader (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944475 Title: DistUpgradeViewNonInteractive is now interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1944475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935583] Re: Kernel panic on Bionic 5.4.0-47-generic
[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/1935583 Title: Kernel panic on Bionic 5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1935583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944099] Re: dconf setting "/apps/update-manager/show-details" does not work
> Thank you for your bug report. The settings control the view of the available updates, not the description box at the bottom. The description of the settings clearly explains that it control description box at the bottom. See screenshot ** Attachment added: "UpdateManager.png" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1944099/+attachment/5527481/+files/UpdateManager.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944099 Title: dconf setting "/apps/update-manager/show-details" does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1944099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944794] Re: Intel AX200 bluetooth is not stable on Ubuntu 18.04
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944794 Title: Intel AX200 bluetooth is not stable on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1944794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944794] [NEW] Intel AX200 bluetooth is not stable on Ubuntu 18.04
Public bug reported: dmesg message: [127123.832636] input: MINISO-K66 Consumer Control as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:05D6:000A.0017/input/input75 [127123.832863] hid-generic 0005:05D6:000A.0017: input,hidraw3: BLUETOOTH HID v2.40 Device [MINISO-K66] on 48:51:c5:7e:bd:9f [127210.072008] userif-3: sent link down event. [127210.072012] userif-3: sent link up event. [127538.625230] userif-3: sent link down event. [127538.625236] userif-3: sent link up event. [127810.100467] userif-3: sent link down event. [127810.100471] userif-3: sent link up event. [128720.890536] Bluetooth: hci0: Received unexpected HCI Event [128720.890541] Bluetooth: hci0: Received unexpected HCI Event [128720.890542] Bluetooth: hci0: Received unexpected HCI Event [128720.890544] Bluetooth: hci0: Received unexpected HCI Event [128720.890545] Bluetooth: hci0: Received unexpected HCI Event [128720.890547] Bluetooth: hci0: Received unexpected HCI Event [128720.890548] Bluetooth: hci0: Received unexpected HCI Event [128720.890550] Bluetooth: hci0: Received unexpected HCI Event [128720.890551] Bluetooth: hci0: Received unexpected HCI Event [128720.890553] Bluetooth: hci0: Received unexpected HCI Event [128720.890554] Bluetooth: hci0: Received unexpected HCI Event [128720.890556] Bluetooth: hci0: Received unexpected HCI Event [128720.890557] Bluetooth: hci0: Received unexpected HCI Event [128720.890559] Bluetooth: hci0: Received unexpected HCI Event [128720.890560] Bluetooth: hci0: Received unexpected HCI Event [128720.890562] Bluetooth: hci0: Received unexpected HCI Event [128720.890563] Bluetooth: hci0: Received unexpected HCI Event [128720.890565] Bluetooth: hci0: Received unexpected HCI Event [128720.890566] Bluetooth: hci0: Received unexpected HCI Event [128720.890568] Bluetooth: hci0: Received unexpected HCI Event [128720.890569] Bluetooth: hci0: Received unexpected HCI Event [128721.002494] Bluetooth: hci0: Received unexpected HCI Event [128721.416496] Bluetooth: hci0: Received unexpected HCI Event [128722.251531] Bluetooth: hci0: Received unexpected HCI Event [128722.251536] Bluetooth: hci0: Received unexpected HCI Event [128722.254493] Bluetooth: hci0: Received unexpected HCI Event [128722.254496] Bluetooth: hci0: Received unexpected HCI Event [128722.254498] Bluetooth: hci0: Received unexpected HCI Event [128722.254500] Bluetooth: hci0: Received unexpected HCI Event [128723.277471] Bluetooth: hci0: command 0x1405 tx timeout [128778.444082] Bluetooth: hci0: link tx timeout [128778.444089] Bluetooth: hci0: killing stalled connection 7c:ce:58:22:8b:80 bluetooth.service status: sudo systemctl status bluetooth.service [sudo] password for yanghuafang: ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2021-09-23 10:56:03 CST; 1 day 1h ago Docs: man:bluetoothd(8) Main PID: 17790 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─17790 /usr/lib/bluetooth/bluetoothd Sep 24 09:25:53 yanghuafang-XPS-15-9570 bluetoothd[17790]: /org/bluez/hci0/dev_7C_CE_58_22_8B_80/fd7: fd(35) ready Sep 24 11:04:27 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:04:30 yanghuafang-XPS-15-9570 bluetoothd[17790]: /org/bluez/hci0/dev_7C_CE_58_22_8B_80/fd8: fd(35) ready Sep 24 11:32:02 yanghuafang-XPS-15-9570 bluetoothd[17790]: No reply to Suspend request Sep 24 11:32:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:32:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: connect error: Device or resource busy (16) Sep 24 11:33:03 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:33:03 yanghuafang-XPS-15-9570 bluetoothd[17790]: connect error: Device or resource busy (16) Sep 24 11:33:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: Can't get HIDP connection info Sep 24 11:33:33 yanghuafang-XPS-15-9570 bluetoothd[17790]: connect error: Device or resource busy (16) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-86.97~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yanghuafang 4442 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 24 11:48:29 2021 InstallationDate: Installed on 2020-06-01 (479 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
[Bug 1944468] Re: Electron applications all crash upon launch
Ah, glad to hear the fix is making it's way back. I still wonder if disabling clone3 for impish release is the pragmatic thing to do, I don't know if vscode, slack, skype etc etc are going to get an update in the next 4 weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944468 Title: Electron applications all crash upon launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1944468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
A few more observations: 1) The output shown for the hook is just snapd debugging goo. It's not meaningful. 2) It is libc6 :( You can demonstrate 2) by: starting a container with a known good image, removing lxd, upgrading libc6 & co and then running "snap install /var/lib/snapd/seed/snaps/lxd_21400.snap". I tried to strace snapd while the installing the lxd snap but that fails even with the old libc (probably because apparmor gets upset about something being ptraced?). snap install --devmode /var/lib/snapd/seed/snaps/lxd_21400.snap also fails, I don't know if that's surprising. If I hack the install hook out of the lxd snap, then it fails with a segfault in snap.lxd.activate.service. If I start the good image, let lxd seed properly, and then upgrade libc6, things are pretty broken: root@mwhudson-test-03:~# lxc 2021/09/24 03:34:20.355414 tool_linux.go:204: DEBUG: restarting into "/snap/snapd/current/usr/bin/snap" 2021/09/24 03:34:20.372561 cmd_run.go:410: DEBUG: SELinux not enabled 2021/09/24 03:34:20.372797 tracking.go:44: DEBUG: creating transient scope snap.lxd.lxc 2021/09/24 03:34:20.373178 tracking.go:176: DEBUG: session bus is not available: cannot find session bus 2021/09/24 03:34:20.373373 tracking.go:178: DEBUG: falling back to system bus 2021/09/24 03:34:20.374487 tracking.go:183: DEBUG: using system bus now, session bus was not available 2021/09/24 03:34:20.379914 tracking.go:305: DEBUG: created transient scope as object: /org/freedesktop/systemd1/job/1461 2021/09/24 03:34:20.380008 tracking.go:135: DEBUG: systemd could not associate process 2970 with transient scope snap.lxd.lxc.8787a98f-da32-4466-8105-764dc71b092b.scope 2021/09/24 03:34:20.380020 cmd_run.go:1170: DEBUG: snapd cannot track the started application 2021/09/24 03:34:20.380027 cmd_run.go:1171: DEBUG: snap refreshes will not be postponed by this process Segmentation fault But annoyingly the debugging aids all fail to work, e.g.: root@mwhudson-test-03:~# snap run --strace lxd.lxc 2021/09/24 03:35:26.821544 tool_linux.go:204: DEBUG: restarting into "/snap/snapd/current/usr/bin/snap" 2021/09/24 03:35:26.848119 cmd_run.go:410: DEBUG: SELinux not enabled 2021/09/24 03:35:26.848487 tracking.go:44: DEBUG: creating transient scope snap.lxd.lxc 2021/09/24 03:35:26.848719 tracking.go:176: DEBUG: session bus is not available: cannot find session bus 2021/09/24 03:35:26.848805 tracking.go:178: DEBUG: falling back to system bus 2021/09/24 03:35:26.849923 tracking.go:183: DEBUG: using system bus now, session bus was not available 2021/09/24 03:35:26.851652 tracking.go:305: DEBUG: created transient scope as object: /org/freedesktop/systemd1/job/1469 2021/09/24 03:35:26.851734 tracking.go:135: DEBUG: systemd could not associate process 3003 with transient scope snap.lxd.lxc.5d763d6a-a730-41bf-b6e3-6cd519cd1919.scope 2021/09/24 03:35:26.851742 cmd_run.go:1170: DEBUG: snapd cannot track the started application 2021/09/24 03:35:26.851748 cmd_run.go:1171: DEBUG: snap refreshes will not be postponed by this process error: exit status 1 Is it possible that snapd's own seccomp policies need updating? I guess I can try building a glibc with clone3 disabled and see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
@mwhudson I'm still not convinced that the udev noise is not the problem, but another data point I just went ahead and got to prove this is that when trying to seed another snap which uses interfaces and has an install hook and is available on arm64, the docker snap, it fails the "same" way with udev things in the setup-profiles task: https://pastebin.ubuntu.com/p/ZGQSxpFHm4/ but in this state setup the install hook is never even attempted to be run. I also am attaching the state.json that results: https://pastebin.ubuntu.com/p/j5MbT8XjVb/ You can see that all the udev output is from the setup-profiles task for snapd from the state.json as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944741] Re: HiFive Unmatched partitions are named "Unleashed"
** Patch added: "util_linux_debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+attachment/5527466/+files/util_linux_debdiff.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944741 Title: HiFive Unmatched partitions are named "Unleashed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1944741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944642] Re: Xenial (ESM) - 4.15.0-156 creates event storm when ejecting DVD-ROM media
*** This bug is a duplicate of bug 1942299 *** https://bugs.launchpad.net/bugs/1942299 Hi Kenneth, Thank you for taking the time to report the issue. In the future, please feel free to file a case through the support portal if you find a issue that needs to be fixed urgently in ESM. In any case, I did some investigating, and found the below commit was backported to 4.15.0-155-generic: commit 7dd753ca59d6c8cc09aa1ed24f7657524803c7f3 Author: ManYi Li Date: Fri Jun 11 17:44:02 2021 +0800 Subject: scsi: sr: Return appropriate error code when disk is ejected Link: https://github.com/torvalds/linux/commit/7dd753ca59d6c8cc09aa1ed24f7657524803c7f3 It landed in a few other kernels too, the full list is: Bionic 4.15.0-155-generic Focal 5.4.0-82-generic Hirsute 5.11.0-32-generic Impish 5.13.0-1-generic I believe this is the root cause, and it lines up with your 4.15.0-154-generic (good) and 4.15.0-156-generic (bad) findings. This has been fixed upstream, by the below commit: commit 5c04243a56a7977185b00400e59ca7e108004faf Author: Li Manyi Date: Mon Jul 26 19:49:13 2021 +0800 Subject: scsi: sr: Return correct event when media event code is 3 Link: https://github.com/torvalds/linux/commit/5c04243a56a7977185b00400e59ca7e108004faf This commit has already been applied to all the Ubuntu kernels, which are currently sitting in -proposed: Bionic 4.15.0-159-generic Focal 5.4.0-87-generic Hirsute 5.11.0-37-generic Impish 5.13.0-16-generic Looking at https://kernel.ubuntu.com/, the current SRU cycle is scheduled to come to an end early next week, so we should expect a release to -updates on ther 27th of September, give or take a few days if any CVEs turn up. At the moment, it is not very straightforward to access the -proposed repo under ESM, but if you can also reproduce the issue under Bionic, feel free to enable -proposed and try 4.15.0-159-generic to confirm it fixes the issue. https://wiki.ubuntu.com/Testing/EnableProposed I set bug 1942299 to track this issue, so I am going to mark this one as a duplicate of it. If you have any questions, feel free to write back, or open a case on the support portal. Thanks, Matthew ** This bug has been marked a duplicate of bug 1942299 CD/DVD tray ejects on boot or waking from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944642 Title: Xenial (ESM) - 4.15.0-156 creates event storm when ejecting DVD-ROM media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944447] Re: refresh-app-awareness=true does not seem to concern dependencies
** Changed in: snapd Status: Incomplete => Confirmed ** Changed in: snapd Importance: Undecided => High ** No longer affects: snapd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/197 Title: refresh-app-awareness=true does not seem to concern dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925246] Re: binderfs support is not enabled
This bug was fixed in the package linux-azure - 5.13.0-1004.5 --- linux-azure (5.13.0-1004.5) impish; urgency=medium * impish/linux-azure: 5.13.0-1004.5 -proposed tracker (LP: #1943742) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) * LRMv5: switch primary version handling to kernel-versions data set (LP: #1928921) - [Packaging] switch to kernel-versions * binderfs support is not enabled (LP: #1925246) - [Config] linux-azure: CONFIG_ANDROID_BINDERFS=m * Miscellaneous Ubuntu changes - [Config] update toolchain version [ Ubuntu: 5.13.0-16.16 ] * impish/linux: 5.13.0-16.16 -proposed tracker (LP: #1942611) * Miscellaneous Ubuntu changes - [Config] update toolchain in configs * Miscellaneous upstream changes - Revert "UBUNTU: [Config] Enable CONFIG_UBSAN_BOUNDS" -- Andrea Righi Fri, 17 Sep 2021 20:47:47 +0200 ** Changed in: linux-azure (Ubuntu Impish) 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/1925246 Title: binderfs support is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1925246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942299] Re: On booting (or wake from suspend) Ubuntu/Lubuntu impish daily - cd/dvd tray ejects
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Description changed: - Lubuntu impish daily boot on - - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) + [Impact] - This daily was booted more than once, on each boot, just prior to - plymouth screen appearing the cd/dvd tray would be ejected. + A regression was introduced via upstream -stable patches which causes + the CD / DVD rom drive to open when the system boots, or wakes from + suspend. - If my installation media was on the cd/dvd - would that have crashed - install? + This has had some side effects on some systems where you cannot insert + media at all, since the drive will eject as soon as the tray is closed. - I've been noting this behavior on my primary box - - dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) - each day (Ubuntu impish, ubuntu, xubuntu & lubuntu desktops installed; occurs when Xfce or LXQt is running.. I don't think I've tried suspend with GNOME with 5.13 kernel) when I resume it in the morning (I suspend each night), likely the 11 days since `uptime` says I last rebooted (I tend to reboot only about once per fortnight) + The problematic patch is: - ** actual results + commit 7dd753ca59d6c8cc09aa1ed24f7657524803c7f3 + Author: ManYi Li + Date: Fri Jun 11 17:44:02 2021 +0800 + Subject: scsi: sr: Return appropriate error code when disk is ejected + Link: https://github.com/torvalds/linux/commit/7dd753ca59d6c8cc09aa1ed24f7657524803c7f3 - On booting daily; the CD/DVD tray ejects + This was backported to: - ** expected results + Bionic 4.15.0-155-generic + Focal 5.4.0-82-generic + Hirsute 5.11.0-32-generic + Impish 5.13.0-1-generic - The CD/DVD is not being used on this boot; I'd expect the tray to remain - as it was + [Fix] - ProblemType: Bug - DistroRelease: Ubuntu 21.10 - Package: linux-image-5.13.0-14-generic 5.13.0-14.14 - ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 - Uname: Linux 5.13.0-14-generic x86_64 - ApportVersion: 2.20.11-0ubuntu68 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: lubuntu1602 F pulseaudio - /dev/snd/controlC1: lubuntu1602 F pulseaudio - CasperMD5CheckResult: pass - CasperVersion: 1.465 - CurrentDesktop: LXQt - Date: Wed Sep 1 07:03:31 2021 - IwConfig: - lono wireless extensions. + The issue was fixed in the below commit: - enp0s25 no wireless extensions. - LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Alpha amd64 (20210831) - MachineType: Dell Inc. OptiPlex 780 - ProcFB: 0 radeondrmfb - ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- - RelatedPackageVersions: - linux-restricted-modules-5.13.0-14-generic N/A - linux-backports-modules-5.13.0-14-generic N/A - linux-firmware 1.199 - RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no - SourcePackage: linux - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 02/13/2010 - dmi.bios.release: 3.0 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: A03 - dmi.board.name: 0200DY - dmi.board.vendor: Dell Inc. - dmi.board.version: A00 - dmi.chassis.type: 3 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/13/2010:br3.0:svnDellInc.:pnOptiPlex780:pvr:sku:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr: - dmi.product.name: OptiPlex 780 - dmi.sys.vendor: Dell Inc. + commit 5c04243a56a7977185b00400e59ca7e108004faf + Author: Li Manyi + Date: Mon Jul 26 19:49:13 2021 +0800 + Subject: scsi: sr: Return correct event when media event code is 3 + Link: https://github.com/torvalds/linux/commit/5c04243a56a7977185b00400e59ca7e108004faf + + This patch is already applied to Ubuntu kernels through upstream + -stable, and will land in the following releases, currently in + -proposed: + + Bionic 4.15.0-159-generic + Focal 5.4.0-87-generic + Hirsute 5.11.0-37-generic + Impish 5.13.0-16-generic + + [Testcase] + + If your machine is affected, the CD / DVD rom drive
[Bug 1943616] Re: CD-ROM tray opens on wake from suspend on Ubuntu 20.04 LTS Focal
*** This bug is a duplicate of bug 1942299 *** https://bugs.launchpad.net/bugs/1942299 ** This bug has been marked a duplicate of bug 1942299 CD/DVD tray ejects on boot or waking from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943616 Title: CD-ROM tray opens on wake from suspend on Ubuntu 20.04 LTS Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943379] Re: CD tray ejected on hibernate resume
*** This bug is a duplicate of bug 1942299 *** https://bugs.launchpad.net/bugs/1942299 ** This bug has been marked a duplicate of bug 1942299 CD/DVD tray ejects on boot or waking from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943379 Title: CD tray ejected on hibernate resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1943379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943662] Re: on booting 18.04.6 ISO (RC QA-test) the CD/DVD tray ejects
*** This bug is a duplicate of bug 1942299 *** https://bugs.launchpad.net/bugs/1942299 ** This bug has been marked a duplicate of bug 1942299 CD/DVD tray ejects on boot or waking from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943662 Title: on booting 18.04.6 ISO (RC QA-test) the CD/DVD tray ejects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1943662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944657] Re: CD-ROM tray opens on boot up linux mint 20.2 version 5.0.5
*** This bug is a duplicate of bug 1942299 *** https://bugs.launchpad.net/bugs/1942299 ** This bug has been marked a duplicate of bug 1942299 CD/DVD tray ejects on boot or waking from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944657 Title: CD-ROM tray opens on boot up linux mint 20.2 version 5.0.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944435] Re: Backlight on P17 Gen 1 not working Nvidia 470
Hi Mark, The log attached is in hybrid mode. If Descrite mode, for my experience, this only happen on 470 driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944435 Title: Backlight on P17 Gen 1 not working Nvidia 470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() fr
** Summary changed: - gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() + gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1942031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944435] Re: Backlight on P17 Gen 1 not working Nvidia 470
Thanks Aaron, Customer noted that this didn't help him - but I assume the above only helps in hybrid mode. Customer is quite grumpy...but David is on PTO and he has the system for reproducing so I'm just trying to manage expectations at the moment. Let me know if there are any other suggestions. Mark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944435 Title: Backlight on P17 Gen 1 not working Nvidia 470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632529] Re: sound problem
Are you still experiencing this problem in VirtualBox? ** Changed in: pulseaudio (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/1632529 Title: sound problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1632529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944542] Re: [Lenovo IdeaPad 5 15IIL05] very slow
If that's true then please also attach a screenshot of the full 'top' window including the '%Cpu(s)' line. Also, while the problem is happening and after you have uninstalled Slack, please run this command again: journalctl -b0 > journal.txt and 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/1944542 Title: [Lenovo IdeaPad 5 15IIL05] very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1944542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944769] Re: [VirtualBox] [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound
** Summary changed: - [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound + [VirtualBox] [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944769 Title: [VirtualBox] [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1944769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
So one thing that I think is going on here is that the udev noise is
caused by trying to _undo_ the "Setup snap "snapd" (12886) security
profiles" task. In the state.json of the image, that task is done:
"7": {
"id": "7",
"kind": "setup-profiles",
"summary": "Setup snap \"snapd\" (12886) security profiles",
"status": 4,
...
},
(4 is DoneStatus in overlord/state/change.go in snapd). So that's a red
herring, or at least, not the underlying problem. The underlying problem
is that "Run install hook of "lxd" snap if present" is failing (this
task is not done in the state.json of either the 20210903 or 20210904 --
in fact those two state.json file differ only in timestamps and cookies
afaict). So the next question: why is the install hook failing? snap
changes 1 only has this to say about this task:
Run install hook of "lxd" snap if present
2021-09-24T01:53:16Z ERROR run hook "install":
-
cmd_run.go:410: DEBUG: SELinux not enabled
tracking.go:44: DEBUG: creating transient scope snap.lxd.hook.install
tracking.go:305: DEBUG: created transient scope as object:
/org/freedesktop/systemd1/job/339
-
which is not very helpful. This output isn't present for the working
image but maybe output for successful tasks isn't saved? I don't know
how this works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944004
Title:
snapd.seeded.service never finishes on non-amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935665] Re: open-vm-tools builds without fuse support when built with libfuse3-dev
Branch supporting libfuse3 is ready at https://github.com/vmware/open- vm-tools/pull/544 ** Changed in: open-vm-tools (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: open-vm-tools (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935665 Title: open-vm-tools builds without fuse support when built with libfuse3-dev To manage notifications about this bug go to: https://bugs.launchpad.net/open-vm-tools/+bug/1935665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944712 Title: systemd/237-3ubuntu10.52 ADT test failure with linux- aws-5.4/5.4.0-1057.60~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1944712 Title: systemd/237-3ubuntu10.52 ADT test failure with linux- aws-5.4/5.4.0-1057.60~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-aws-5.4 (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/1944712 Title: systemd/237-3ubuntu10.52 ADT test failure with linux- aws-5.4/5.4.0-1057.60~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944785] Re: systemd adt runs triggered by linux-meta-* hitting timeouts
*** This bug is a duplicate of bug 1944712 *** https://bugs.launchpad.net/bugs/1944712 ** This bug has been marked a duplicate of bug 1944712 systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944785 Title: systemd adt runs triggered by linux-meta-* hitting timeouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1944785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944712] Re: systemd/237-3ubuntu10.52 ADT test failure with linux-aws-5.4/5.4.0-1057.60~18.04.1
I filed one like this as well, so let me merge with this one. My notes: Systemd amd64 autopkgtest runs, when triggered by non-linux-meta packages, usually pass. You can find some failures on a possible flaky TEST-29-PORTABLE. Ignore those for the moment. Systemd amd64 autopkgtest runs, triggered by linux-meta packages, usually fail and hit the 2 second timeout on the systemd upstream-1 (and sometimes upstream-2) test. I did find an outlier that hit the same timeout: 248.3-1ubuntu3 e2fsprogs/1.46.3-1ubuntu3 2021-09-05 15:02:56 UTC 6h 58m 46s -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944712 Title: systemd/237-3ubuntu10.52 ADT test failure with linux- aws-5.4/5.4.0-1057.60~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.4/+bug/1944712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
I reviewed fence-agents 4.7.1-1ubuntu6 as checked into impish. This shouldn't be considered a full audit but rather a quick gauge of maintainability. fence-agents provides per-hardware or cloud details on how to forcibly remove a machine from a high-availability setup, whether it's by yanking power or by yanking network. It's nothing but sharp edges and corner cases. - CVE History: - two cves: one not validating tls certificates, one a non-ascii error causing a failure to fence - Build-Depends: autoconf, automake, debhelper-compat (= 13), dh-python, iputils-ping, libglib2.0-dev, libnspr4-dev, libnss3-dev, libtool, perl, python3, python3-boto3, python3-googleapi, python3-oauth2client, python3-pexpect, python3-pycurl, python3-requests, python3-suds, time, xsltproc, libxml2-utils, libnet-telnet-perl - pre/post inst/rm scripts? - Automatically-added dh_python3 - init scripts? - none - systemd units? - none - dbus services? - none - setuid binaries? - none - binaries in PATH? - many, all start /usr/sbin/fence_ - sudo fragments? - none - polkit files? - none - udev rules? - none - unit tests / autopkgtests? - I didn't spot any unit tests - autopkgtests provide a simple smoke test, better than nothing - cron jobs? - none - Build logs: - nothing too drastic, but they do give the impression they are unread - lintian unhappy: E: fence-agents-common: dir-or-file-in-var-run var/run/cluster/ - Processes spawned? - that's the whole point of the project; the commands shut machines off, so pretty much only handling trusted inputs, so I didn't inspect calls carefully - Memory management? - Python - File IO? - under control of callers - Logging? - extensive -- sometimes logs passwords. I opened an issue for this. - Environment variable usage? - Nothing explicit - Use of privileged functions? - extensive, the point of the project - Use of cryptography / random number sources etc? - it's very easy to bypass certificate requirements - Use of temp files? - two fixed path names in /tmp, one in 'dummy' the other in 'rhevm'. Probably not in the threat model of the project. - Use of networking? - extensive, the point of the thing; nothing stood out as drastically unsafe but it does feel like it assumes everything is trusted - Use of WebKit? - none - Use of PolicyKit? - none - Any significant cppcheck results? - none - Any significant Coverity results? - not really, some dead code due to bug, I opened an issue - Any significant shellcheck results? - not really - Any significant bandit results? - points out some exec(), system(), subprocess(), assert(), and something about unsafely handling xml. Nothing sounds like a surprise. fence-agents sits in an interesting space with lots of networking and highly privileged operations, command executions, etc, as the main goal. It's probably best to assume inputs are pretty well trusted. It looked professionally programmed, but by its nature it just does unsafe operations. I think we need to fix the lintian error: E: fence-agents-common: dir-or-file-in-var-run var/run/cluster/ before we promote this to main -- I expect this will cause dpkg unhappyness after a reboot, if not outright incorrect operation of the tools. Security team ACK for promoting fence-agents to main. Here's some notes I took while reading it. I filed two issues for things, but neither looks like a big deal to me. set_boot_order() in agents/amt_ws/fence_amt_ws.py misunderstands python 'or' https://github.com/ClusterLabs/fence-agents/issues/434 fence-agents/agents/eps/fence_eps.py can debug-log passwords https://github.com/ClusterLabs/fence-agents/issues/436 fence_action() in agents/autodetect/fencing.py uses status.upper() when status might be None get_instance_id() in agents/aws/fence_aws.py is claimed to pass data retrieved from the metadata service in a header to the metadata service -- I'm not convinced, but it'd be nice if someone gives this a look. fence_action() in lib/fencing.py.py uses status.upper() when status might be None ** Changed in: fence-agents (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Bug watch added: github.com/ClusterLabs/fence-agents/issues #434 https://github.com/ClusterLabs/fence-agents/issues/434 ** Bug watch added: github.com/ClusterLabs/fence-agents/issues #436 https://github.com/ClusterLabs/fence-agents/issues/436 ** Changed in: fence-agents (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004
[Bug 1944785] [NEW] systemd adt runs triggered by linux-meta-* hitting timeouts
Public bug reported: Systemd amd64 autopkgtest runs, when triggered by non-linux-meta packages, usually pass. You can find some failures on a possible flaky TEST-29-PORTABLE. Ignore those for the moment. Systemd amd64 autopkgtest runs, triggered by linux-meta packages, usually fail and hit the 2 second timeout on the systemd upstream-1 (and sometimes upstream-2) test. I did find an outlier that hit the same timeout: 248.3-1ubuntu3 e2fsprogs/1.46.3-1ubuntu3 2021-09-05 15:02:56 UTC 6h 58m 46s ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: systemd (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/1944785 Title: systemd adt runs triggered by linux-meta-* hitting timeouts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1944785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.4/5.4.0.87.98~18.04.78)
All autopkgtests for the newly accepted linux-meta-hwe-5.4 (5.4.0.87.98~18.04.78) for bionic have finished running. The following regressions have been reported in tests triggered by the package: asic0x/1.0.1-1 (s390x) kpatch/0.5.0-0ubuntu1.1 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (s390x) acpi-call/1.1.0-4 (ppc64el, s390x) lxc/3.0.3-0ubuntu1~18.04.1 (amd64, i386, ppc64el, s390x, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-hwe-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875930] Re: underscore not shown in scite editor window
This should be fixed in 5.1.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875930 Title: underscore not shown in scite editor window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scite/+bug/1875930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944475] Re: DistUpgradeViewNonInteractive is now interactive
The attachment "Hirsute Patch" 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/1944475 Title: DistUpgradeViewNonInteractive is now interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1944475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()
This has been added to the release notes for Impish Indri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1942031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Second one today. Hopefully this has more information. ** Attachment added: "prevboot-2021-09-23-b.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+attachment/5527459/+files/prevboot-2021-09-23-b.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904730] Re: neutron-agent-sriov fails to create port
For bionic, the provided test case needs some tweaks as the neutron
version on bionic does not have the provided functions. Instead, I've
written a quick test script that will exercise the pyroute2 code path to
exercise the errors. Still requires enabling vfs as James did.
Simple script is:
#!/usr/bin/python3
import pyroute2
ip = pyroute2.IPRoute()
devname = 'enp3s0f0'
link_idx = ip.link_lookup(ifname=devname)[0]
link = ip.link('get', index=link_idx, ext_mask=1)[0]
num_vfs = link.get_attr('IFLA_NUM_VF')
print(num_vfs)
Running test on bionic without this fix to prove its enough to show the error:
$ dpkg -l | grep python3-pyroute2
ii python3-pyroute2 0.4.21-0.1ubuntu2
all Python3 Netlink library
$ sudo ./lp1904730-test.py
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1232, in _ft_decode_generic
self.decode_nlas(offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1357, in decode_nlas
offset)
struct.error: unpack_from requires a buffer of at least 4 bytes
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./lp1904730-test.py", line 7, in
link = ip.link('get', index=link_idx, ext_mask=1)[0]
File "/usr/lib/python3/dist-packages/pyroute2/iproute.py", line 1310, in link
msg_flags=msg_flags)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 804,
in nlm_request
return do_try()
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 783,
in do_try
callback=callback)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 648,
in get
raise msg['header']['error']
File "/usr/lib/python3/dist-packages/pyroute2/netlink/nlsocket.py", line 171,
in parse
msg.decode()
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line 941,
in decode
self._ft_decode(self, offset)
File "/usr/lib/python3/dist-packages/pyroute2/netlink/__init__.py", line
1235, in _ft_decode_generic
raise NetlinkNLADecodeError(e)
pyroute2.netlink.exceptions.NetlinkNLADecodeError: unpack_from requires a
buffer of at least 4 bytes
Running with the proposed patch:
$ dpkg -l | grep python3-pyroute2
ii python3-pyroute2 0.4.21-0.1ubuntu2.1
all Python3 Netlink library
$ sudo ./lp1904730-test.py
63
** Tags removed: verification-needed
** Tags added: verification-done verification-done-bionic
** Tags removed: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904730
Title:
neutron-agent-sriov fails to create port
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1904730/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Fix merged to neutron (stable/ussuri)
Reviewed: https://review.opendev.org/c/openstack/neutron/+/809383 Committed: https://opendev.org/openstack/neutron/commit/c45f0fd4bce12d9ee3ef07c1ce5d574d3308959f Submitter: "Zuul (22348)" Branch:stable/ussuri commit c45f0fd4bce12d9ee3ef07c1ce5d574d3308959f Author: Edward Hope-Morley Date: Fri Aug 20 12:25:04 2021 +0100 Revert "[L3][HA] Retry when setting HA router GW status." In short this patch can cause the privsep reader thread to die resulting in the l3 agent getting stuck and e.g. not processing any router updates. See related LP bug for full explanation. Closes-Bug: #1927868 This reverts commit 662f483120972a373e19bde52f16392e2ccb9c82. Change-Id: Ide7e9771d08eb623dd75941e425813d9b857b4c6 (cherry picked from commit 344fc0c8d2ce7d942606c834a54cb81f0b47aa37) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927868] Re: vRouter not working after update to 16.3.1
Reviewed: https://review.opendev.org/c/openstack/neutron/+/809384 Committed: https://opendev.org/openstack/neutron/commit/f54658c203e66355e94fdd48fbd57682577fc928 Submitter: "Zuul (22348)" Branch:stable/train commit f54658c203e66355e94fdd48fbd57682577fc928 Author: Edward Hope-Morley Date: Fri Aug 20 12:25:04 2021 +0100 Revert "[L3][HA] Retry when setting HA router GW status." In short this patch can cause the privsep reader thread to die resulting in the l3 agent getting stuck and e.g. not processing any router updates. See related LP bug for full explanation. Closes-Bug: #1927868 This reverts commit 662f483120972a373e19bde52f16392e2ccb9c82. Change-Id: Ide7e9771d08eb623dd75941e425813d9b857b4c6 (cherry picked from commit 344fc0c8d2ce7d942606c834a54cb81f0b47aa37) ** Tags added: in-stable-train ** Tags added: in-stable-ussuri -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
So some thoughts: 1. The root failure of snapd failing to finish seeding is that it is trying to run `udevadm trigger --subsystem-nomatch=input` which ends up dying on every write like so: openat(AT_FDCWD, "/sys/devices/virtual/workqueue/writeback/uevent", O_WRONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC) = -1 EACCES (Permission denied) writeback: Failed to write 'change' to '/sys/devices/virtual/workqueue/writeback/uevent': Permission denied which is peculiar to me because that command fails on both the 03 and the 04 image, but only causes snapd to fail to seed on the 04 image for some reason. This is triply peculiar to me because that same command run in a 21.04 container (amd64 and arm64) works fine without issues. Quadruply peculiar is that the same command in a 21.10 daily container on amd64 actually also fails, but again does not cause snapd to fail seeding on the amd64 image. My guess is that maybe snapd doesn't think it needs to run this command on the other 21.10 images and so it doesn't die on this command, but for some reason on the new arm64 images it thinks it has to run this command. Quintuply peculiar is the failure around EACCES. 2. If you diff the manifest between the image you see this change: -libc-bin2.33-0ubuntu9 -libc6:arm642.33-0ubuntu9 +libc-bin2.34-0ubuntu2 +libc6:arm642.34-0ubuntu2 I have no reason to believe that libc6 is the root of this problem, other than the fact that it has been at the root of many other problems that present themselves in weird ways especially when containers are involved. 3. The specific task that snapd is running when the failure happens seems to be either setup-profiles for the snapd snap OR running the install hook for lxd, although I don't think it is related at all to the specific install hook for the lxd snap since that doesn't seem to do anything real and it fails in different ways, sometimes it's a segmentation fault and sometimes it just says the hook exited 1. 4. If I modify the seed.yaml to not seed the lxd snap and then obliterate state.json and restart snapd, it now proceeds to be able to seed properly, so I think there is something about the lxd snap + the state of the system which implies to snapd that it needs to setup the udev backend which runs the failing command, most likely the fact that the lxd snap uses interfaces (even though it's interfaces are rather pointless in that they don't really have any policy). Indeed I can also successfully seed a snap like jq in the seed.yaml which has no interfaces used and it doesn't trigger snapd to run udev things. So part of the story is definitely that snapd thinks it needs to generate udev backend things for the lxd snap while seeding and that causes it to run that udevadm command which fails. Why this doesn't affect amd64 though is unclear to me. 5. The two rootfs' provided above are both preseeded with the same set of snaps with the same assertions and same seed.yaml file, so it doesn't appear to be a snapd regression or some trigger from the snaps themselves. Finally, I also note that this is also reproducible on a Raspberry Pi too if anyone wants to debug on their own, just run on a Pi: lxc launch ubuntu-daily:21.10 impish-testing and then you can see the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847340] Re: ext4 journal recovery fails w/ data=journal + mmap
** Changed in: linux (Ubuntu Focal) Status: In Progress => 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/1847340 Title: ext4 journal recovery fails w/ data=journal + mmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942902] Re: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
** Changed in: linux (Ubuntu Focal) Status: In Progress => 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/1942902 Title: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851378] Re: -R option missing and traceback visible in manpage
I got confused using rpl in 20.04, thanks to this page it is clarified. What was the reason changing to a different source? Using -R option in the original package was more reliable. SF.net version did not have issues while the Ubuntu version did. aa0001@test:~/projects/biospectra/cvs$ find . -name '*.php' | xargs rpl -s "\$form->ACTION = \$conf['paths']['http'] . \$_SERVER['REQUEST_URI']" "\$form->ACTION = comHttpProtocolUrl( \$conf['paths']['serverName'] . \$_SERVER['REQUEST_URI'] )" rpl: Simulating replacement of "$form->ACTION = $conf['paths']['http'] . $_SERVER['REQUEST_URI']" with "$form->ACTION = comHttpProtocolUrl( $conf['paths']['serverName'] . $_SERVER['REQUEST_URI'] )" (case sensitive; partial words matched) rpl: The files listed below would be modified in a replace operation rpl: could not guess encoding; using locale default 'UTF-8' ... Traceback (most recent call last): File "/usr/bin/rpl", line 377, in matches = replace(f, o, regex, old_str, new_str, encoding) File "/usr/bin/rpl", line 178, in replace parts = regex.split(tonext + block) TypeError: can only concatenate str (not "bytes") to str -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851378 Title: -R option missing and traceback visible in manpage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpl/+bug/1851378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Changed in: linux (Ubuntu Focal) Status: In Progress => 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944778] [NEW] Installer desktop icon has the wrong version number in Lubuntu Impish daily
Public bug reported: The wrong version is reported on the Lubuntu desktop icon. It shows "Install Lubuntu 21.04" and it should be "Install Lubuntu 21.10". ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: calamares-settings-lubuntu 1:21.10.1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: LXQt Date: Thu Sep 23 22:46:57 2021 LiveMediaBuild: Lubuntu 21.10 "Impish Indri" - Beta amd64 (20210923) PackageArchitecture: all SourcePackage: calamares-settings-ubuntu UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: calamares-settings-ubuntu (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug impish ** Changed in: calamares-settings-ubuntu (Ubuntu) Milestone: None => ubuntu-21.10 ** Changed in: calamares-settings-ubuntu (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944778 Title: Installer desktop icon has the wrong version number in Lubuntu Impish daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/1944778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944212] Re: Focal update: v5.4.143 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => 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/1944212 Title: Focal update: v5.4.143 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944777] [NEW] g++10.3 Segmentation fault when compiling CUDA code
Public bug reported: > lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 >apt-cache policy gcc-10 gcc-10: Installed: 10.3.0-1ubuntu1~20.04 Candidate: 10.3.0-1ubuntu1~20.04 Version table: *** 10.3.0-1ubuntu1~20.04 500 500 http://fr.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 100 /var/lib/dpkg/status 10-20200411-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages I expect to be able to compile CUDA code with gcc-10. It was working with gcc 10.2 and failed with gcc-10.3 When compiling CUDA code g++-10.3 failed with following error message /usr/include/c++/10/chrono: In substitution of ‘template template using __is_harmonic = std::__bool_constant<(std::ratio<((_Period2::num / std::chrono::duration<_Rep, _Period>::_S_gcd(_Period2::num, _Period::num)) * (_Period::den / std::chrono::duration<_Rep, _Period>::_S_gcd(_Period2::den, _Period::den))), ((_Period2::den / std::chrono::duration<_Rep, _Period>::_S_gcd(_Period2::den, _Period::den)) * (_Period::num / std::chrono::duration<_Rep, _Period>::_S_gcd(_Period2::num, _Period::num)))>::den == 1)> [with _Period2 = _Period2; _Rep = _Rep; _Period = _Period]’: /usr/include/c++/10/chrono:473:154: required from here /usr/include/c++/10/chrono:428:27: internal compiler error: Segmentation fault 428 | _S_gcd(intmax_t __m, intmax_t __n) noexcept | ^~ This bug has been corrected in gcc-10.4 : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100102 Could it be possible to make Ubuntu 20.04 gcc-10 package use gcc-10.4 instead of 10.3 ? ** Affects: gcc-10 (Ubuntu) Importance: Undecided Status: New ** Tags: cuda upgrade-software-version ** Description changed: > lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 >apt-cache policy gcc-10 gcc-10: - Installed: 10.3.0-1ubuntu1~20.04 - Candidate: 10.3.0-1ubuntu1~20.04 - Version table: - *** 10.3.0-1ubuntu1~20.04 500 - 500 http://fr.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages - 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages - 100 /var/lib/dpkg/status - 10-20200411-0ubuntu1 500 - 500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages + Installed: 10.3.0-1ubuntu1~20.04 + Candidate: 10.3.0-1ubuntu1~20.04 + Version table: + *** 10.3.0-1ubuntu1~20.04 500 + 500 http://fr.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages + 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages + 100 /var/lib/dpkg/status + 10-20200411-0ubuntu1 500 + 500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages I expect to be able to compile CUDA code with gcc-10. It was working with gcc 10.2 and failed with gcc-10.3 When compiling CUDA code g++-10.3 failed with following error message /usr/include/c++/10/chrono: In substitution of ‘template template using __is_harmonic = std::__bool_constant<(std::ratio<((_Period2::num / std::chrono::duration<_Rep, _Period>::_S_gcd(_Period2::num, _Period::num)) * (_Period::den / std::chrono::duration<_Rep, _Period>::_S_gcd(_Period2::den, _Period::den))), ((_Period2::den / std::chrono::duration<_Rep, _Period>::_S_gcd(_Period2::den, _Period::den)) * (_Period::num / std::chrono::duration<_Rep, _Period>::_S_gcd(_Period2::num, _Period::num)))>::den == 1)> [with _Period2 = _Period2; _Rep = _Rep; _Period = _Period]’: /usr/include/c++/10/chrono:473:154: required from here /usr/include/c++/10/chrono:428:27: internal compiler error: Segmentation fault - 428 | _S_gcd(intmax_t __m, intmax_t __n) noexcept - | ^~ - + 428 | _S_gcd(intmax_t __m, intmax_t __n) noexcept + | ^~ This bug has been corrected in gcc-10.4 : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100102 - Could it be possible to make Ubuntu gcc-10 package use gcc-10.4 instead - of 10.3 ? + Could it be possible to make Ubuntu 20.04 gcc-10 package use gcc-10.4 + instead of 10.3 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944777 Title: g++10.3 Segmentation fault when compiling CUDA code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1944777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944202] Re: Focal update: v5.4.142 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => 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/1944202 Title: Focal update: v5.4.142 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943484] Re: Focal update: v5.4.141 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Focal) Status: Fix Released => 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/1943484 Title: Focal update: v5.4.141 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1943484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931004] Re: Add support for Pacific to RBD driver
Reviewed: https://review.opendev.org/c/openstack/cinder/+/809181 Committed: https://opendev.org/openstack/cinder/commit/06b32da4be8b69e626eb7eb8091f695cbdcd92e7 Submitter: "Zuul (22348)" Branch:stable/ussuri commit 06b32da4be8b69e626eb7eb8091f695cbdcd92e7 Author: Jon Bernard Date: Wed Apr 14 11:14:13 2021 -0400 RBD: use correct stripe unit in clone operation The recent release of Ceph Pacific saw a change to the clone() logic where invalid values of stripe unit would cause an error to be returned where previous versions would correct the value at runtime. This becomes a problem when creating a volume from an image, where the source RBD image may have a larger stripe unit than cinder's RBD driver is configured for. When this happens, clone() is called with a stripe unit that is too small given that of the source image and the clone fails. The RBD driver in Cinder has a configuration parameter 'rbd_store_chunk_size' that stores the preferred object size for cloned images. If clone() is called without a stripe_unit passed in, the stripe unit defaults to the object size, which is 4MB by default. The issue arises when creating a volume from a Glance image, where Glance is creating images with a default stripe unit of 8MB (distinctly larger than that of Cinder). If we do not consider the incoming stripe unit and select the larger of the two, Ceph cannot clone an RBD image with a smaller stripe unit and raises an error. This patch adds a function in our driver's clone logic to select the larger of the two stripe unit values so that the appropriate stripe unit is chosen. It should also be noted that we're determining the correct stripe unit, but using the 'order' argument to clone(). Ceph will set the stripe unit equal to the object size (order) by default and we rely on this behaviour for the following reason: passing stripe-unit alone or with an order argument causes an invalid argument exception to be raised in pre-pacific releases of Ceph, as it's argument parsing appears to have limitations. Closes-Bug: #1931004 Change-Id: Iec111ab83e9ed8182c9679c911e3d90927d5a7c3 (cherry picked from commit 49a2c85eda9fd3cddc75fd904fe62c87a6b50735) (cherry picked from commit 5db58159feec3d2d39d1abf3637310f5ac60a3cf) Conflicts: cinder/tests/unit/volume/drivers/test_rbd.py (cherry picked from commit 07ead73eec0ac6b962b533b07861d6a81226fa37) ** Tags added: in-stable-ussuri -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931004 Title: Add support for Pacific to RBD driver To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1931004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944412] Re: Nautilus keeps spawning new window when clicking on the launcher icon
Thanks for the update, the description is a bit confusing now though. When you wrote 'the launcher icon' you didn't talk about the dock which is the default ubuntu configuration? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944412 Title: Nautilus keeps spawning new window when clicking on the launcher icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944767] Re: During install, panel content is missing
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1944767 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944767 Title: During install, panel content is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944763] Re: sed temp file appears in nautilus but not in ls -a
Thank you for your bug report, could you share the output of $ gio monitor (where is the path to the directory where you are doing the change) which filesystem are you using? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (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/1944763 Title: sed temp file appears in nautilus but not in ls -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1944763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944772] [NEW] rigctld -m 1 segfaulting
Public bug reported: socket connection polling for f, m, l RF, l RFPOWER, l RFPOWER_METER_WATTS repeatedly causes segfault. here's -v output from rigctld -m 1 command Connection opened from localhost:38710 Connection closed from localhost:38708 sync_callback: client lock engaged sync_callback: client lock disengaged handle_socket: vfo_mode=0 rigctl_parse: called, interactive=1 rigctl_parse: cmd=f(66) rigctl_parse: cmd==0x66 rigctl_parse: vfo_opt=0 rigctl_parse: debug1 rigctl_parse: debug5 rigctl_parse: debug10 sync_callback: client lock engaged rigctl(d): f 'currVFO' '' '' '' rigctl_parse: vfo_opt=0 rig_get_freq called vfo=currVFO vfo_fixup: vfo=currVFO vfo_fixup: Leaving currVFO alone get_cache_freq: vfo=currVFO, freq=1.45e+08 elapsed_ms: start = 1632429847,35908074 elapsed_ms: elapsed_msecs=981 rig_get_freq: cache check age=980ms rig_get_freq: cache miss age=980ms, cached_vfo=currVFO, asked_vfo=currVFO dummy_get_freq called: VFOA dummy_get_freq: freq=14500 elapsed_ms: start = 0,0 elapsed_ms: after gettime, start = 1632429848,37036370 elapsed_ms: start = 0,0 elapsed_ms: after gettime, start = 1632429848,37046168 rig_get_freq: cache reset age=999000ms, vfo=currVFO, freq=14500 elapsed_ms: start = 0,0 elapsed_ms: after gettime, start = 1632429848,37068707 rigctl_parse: vfo_opt=0 rigctl_parse: retcode=0 sync_callback: client lock disengaged handle_socket: vfo_mode=0 rigctl_parse: called, interactive=1 rigctl_parse: cmd==0x0a rigctl_parse: cmd=m(6d) rigctl_parse: cmd==0x6d rigctl_parse: vfo_opt=0 rigctl_parse: debug1 rigctl_parse: debug5 rigctl_parse: debug10 sync_callback: client lock engaged rigctl(d): m 'currVFO' '' '' '' rigctl_parse: vfo_opt=0 rig_get_mode called elapsed_ms: start = 1632429847,56284811 elapsed_ms: elapsed_msecs=981 rig_get_mode: cache check age=981ms rig_get_mode: cache miss age=981ms dummy_get_mode called: currVFO rig_get_mode: retcode after get_mode=0 rig_get_mode(1909): debug elapsed_ms: start = 0,0 elapsed_ms: after gettime, start = 1632429848,57462182 rigctl_parse: vfo_opt=0 rigctl_parse: retcode=0 sync_callback: client lock disengaged handle_socket: vfo_mode=0 rigctl_parse: called, interactive=1 rigctl_parse: cmd==0x0a rigctl_parse: cmd=l(6c) rigctl_parse: cmd==0x6c rigctl_parse: vfo_opt=0 rigctl_parse: debug1 rigctl_parse: debug3 rigctl_parse: debug4 c=20 rigctl_parse: debug5 rigctl_parse: debug10 sync_callback: client lock engaged rigctl(d): l 'currVFO' 'RF' '' '' rigctl_parse: vfo_opt=0 rig_parse_level called rig_setting2idx called rig_setting2idx: idx=4 rig_strlevel called rig_strlevel called dummy_get_level called: RF rigctl_parse: vfo_opt=0 rigctl_parse: retcode=0 sync_callback: client lock disengaged handle_socket: vfo_mode=0 rigctl_parse: called, interactive=1 rigctl_parse: cmd==0x0a rigctl_parse: cmd=l(6c) rigctl_parse: cmd==0x6c rigctl_parse: vfo_opt=0 rigctl_parse: debug1 rigctl_parse: debug3 rigctl_parse: debug4 c=20 rigctl_parse: debug5 rigctl_parse: debug10 sync_callback: client lock engaged rigctl(d): l 'currVFO' 'RFPOWER' '' '' rigctl_parse: vfo_opt=0 rig_parse_level called rig_setting2idx called rig_setting2idx: idx=12 rig_strlevel called rig_strlevel called dummy_get_level called: RFPOWER rigctl_parse: vfo_opt=0 rigctl_parse: retcode=0 sync_callback: client lock disengaged handle_socket: vfo_mode=0 rigctl_parse: called, interactive=1 rigctl_parse: cmd==0x0a rigctl_parse: cmd=l(6c) rigctl_parse: cmd==0x6c rigctl_parse: vfo_opt=0 rigctl_parse: debug1 rigctl_parse: debug3 rigctl_parse: debug4 c=20 rigctl_parse: debug5 rigctl_parse: debug10 sync_callback: client lock engaged rigctl(d): l 'currVFO' 'RFPOWER_METER_WATTS' '' '' rigctl_parse: vfo_opt=0 rig_parse_level called rig_setting2idx called rig_setting2idx: idx=39 rig_strlevel called rig_strlevel called dummy_get_level called: RFPOWER_METER_WATTS rigctl_parse: vfo_opt=0 rigctl_parse: retcode=0 sync_callback: client lock disengaged handle_socket: vfo_mode=0 rigctl_parse: called, interactive=1 rigctl_parse: cmd==0x0a scanfc: ret=-1 rigctl_parse: nothing to scan#1? retcode=-1 handle_socket: rigctl_parse retcode=-1 Connection closed from localhost:38710 Connection opened from localhost:38712 fdopen(0x4) in: Bad file descriptor Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libhamlib-utils 4.0-4 ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 23 14:40:38 2021 InstallationDate: Installed on 2020-04-07 (534 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: hamlib UpgradeStatus: Upgraded to hirsute on 2021-05-12 (134 days ago) ** Affects: hamlib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug
[Bug 1942699] Re: SRU: Update Telegram Desktop to 2.9.2
The SRU team discussed this between themselves on 9 September. We don't think that "new features" are appropriate in telegram-desktop in stable Ubuntu releases, and so this is not sufficient justification for an SRU in itself. Users generally don't expect new features to appear in stable Ubuntu releases, and we don't think an exception is appropriate here. If you want to continuously ship the latest telegram-desktop features to Ubuntu users, we think that snaps would be a more appropriate solution. If you don't want to use snaps, then you might consider the backports pocket - subject to requirements from the backporters team as they get their process refined and restarted. If, however, there are specific bugs that need fixing in telegram- desktop in a stable release, or a specific change in the Telegram protocol that results in regressed functionality for users, then we can consider an SRU to fix that. If this is the case then such an SRU needs to be justified on those merits. I'm therefore going to set the stable tasks to Won't Fix and reject the uploads. Feel free however to repurpose this bug to fix some specific issue that is SRU-able - in which case please provide that justification and then reopen the bug. ** Changed in: libtgowt (Ubuntu Focal) Status: In Progress => Won't Fix ** Changed in: libtgowt (Ubuntu Hirsute) Status: In Progress => Won't Fix ** Changed in: telegram-desktop (Ubuntu Focal) Status: In Progress => Won't Fix ** Changed in: telegram-desktop (Ubuntu Hirsute) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 2.9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944771] [NEW] package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy-installer script pre-removal devolvió el código de salida
Public bug reported: Don't allow install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firmware-b43legacy-installer 1:019-4 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.20 AptOrdering: bcmwl-kernel-source:amd64: Purge firmware-b43legacy-installer:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 23 16:24:53 2021 ErrorMessage: el subproceso instalado paquete firmware-b43legacy-installer script pre-removal devolvió el código de salida de error 123 InstallationDate: Installed on 2021-04-10 (166 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all 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: b43-fwcutter Title: package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy-installer script pre-removal devolvió el código de salida de error 123 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal 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/1944771 Title: package firmware-b43legacy-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43legacy- installer script pre-removal devolvió el código de salida de error 123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1944771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364091] Re: xrandr error with delmode
I am also still experiencing this problem with 20.04. $ xrandr --delmode DP-1 1024x768 X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 19 (RRDeleteOutputMode) Serial number of failed request: 32 Current serial number in output stream: 33 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/364091 Title: xrandr error with delmode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/364091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944767] Re: During install, panel content is missing
Maybe worth mentioning that this did not happen on any of the previous spins of 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/1944767 Title: During install, panel content is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944475] Re: DistUpgradeViewNonInteractive is now interactive
** Patch added: "Hirsute Patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1944475/+attachment/5527444/+files/lp1944475_hirsute.debdiff ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944475 Title: DistUpgradeViewNonInteractive is now interactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1944475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335391] Re: etckeeper with git breaks update-manager
Hi, my workaround was to no longer use etckeeper. So I currently cannot answer your other questions. As you said the bug is quite old and it is possible, that in the mean time the issue was fixed. As you have tested it, I would treat it as solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335391 Title: etckeeper with git breaks update-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1335391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944459] Re: systemd-udevd NamePolicy= warning issue
> "ubuntu systemd-udevd[911]: Network interface NamePolicy= disabled on kernel command line, ignoring." yes..you have disabled it on the kernel command line. I don't understand what the bug is here? ** Changed in: systemd (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/1944459 Title: systemd-udevd NamePolicy= warning issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1944459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944475] Re: DistUpgradeViewNonInteractive is now interactive
** Description changed: - With the change to show the release notes when using the "Text" view of - the release upgrader (LP: #1925529) a yes / no question regarding - upgrading is also displayed when using the NonInteractive view. This - ends up making the upgrade process interactive and breaks automatic - upgrade testing as seen in this log file: + [Impact] + * The non-interactive release upgrades ask a question and wait for + an interaction from the user. This makes the "NonInteractive" + process interactive, and therefore breaks automatic upgrades. + + [Test Case] + * On a hirsute VM, make sure all packages are up to date + by running `sudo apt update && sudo apt upgrade -y` + * `sudo do-release-upgrade -d --frontend=DistUpgradeViewNonInteractive` + * Observe that the the upgrader displays the release notes followed + by a question in the form of "Continue [yN]" + * Type N and press enter to cancel the upgrade + * Install ubuntu-release-upgrader from hirsute-proposed + * `sudo do-release-upgrade -d --frontend=DistUpgradeViewNonInteractive` + * Observe that the release upgrade completes successfully without + any interaction from the user. + + [Regression Potential] + * If the check for the specific frontend is not + properly written it may be possible that + the other frontends no longer display the release + notes and ask the user if they want to continue. + * This can be tested by running "do-release-upgrade" + with --frontend=DistUpgradeViewGtk3 and + --frontend=DistUpgradeViewText + + [Original Description] + With the change to show the release notes when using the "Text" view of the release upgrader (LP: #1925529) a yes / no question regarding upgrading is also displayed when using the NonInteractive view. This ends up making the upgrade process interactive and breaks automatic upgrade testing as seen in this log file: == More Information == You can find out more about Ubuntu on the Ubuntu website and Ubuntu wiki. - http://www.ubuntu.com/ - http://wiki.ubuntu.com/ - + http://www.ubuntu.com/ + http://wiki.ubuntu.com/ To sign up for Ubuntu development announcements, please subscribe to Ubuntu's development announcement list at: - http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce - + http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce Continue [yN] auto-upgrade [13:48:19]: Rebooting the system. bash: line 1: 889 Killed /tmp/autopkgtest.u4eodP/build.JbM/real-tree/debian/tests/upgrade 2> >(tee -a /tmp/autopkgtest.u4eodP/upgrade-stderr >&2) > >(tee -a /tmp/autopkgtest.u4eodP/upgrade-stdout) autopkgtest: DBG: testbed command exited with code 137 ** Description changed: [Impact] - * The non-interactive release upgrades ask a question and wait for - an interaction from the user. This makes the "NonInteractive" - process interactive, and therefore breaks automatic upgrades. + * The non-interactive release upgrades ask a question and wait for + an interaction from the user. This makes the "NonInteractive" + process interactive, and therefore breaks automatic upgrades. [Test Case] - * On a hirsute VM, make sure all packages are up to date - by running `sudo apt update && sudo apt upgrade -y` - * `sudo do-release-upgrade -d --frontend=DistUpgradeViewNonInteractive` - * Observe that the the upgrader displays the release notes followed - by a question in the form of "Continue [yN]" - * Type N and press enter to cancel the upgrade - * Install ubuntu-release-upgrader from hirsute-proposed - * `sudo do-release-upgrade -d --frontend=DistUpgradeViewNonInteractive` - * Observe that the release upgrade completes successfully without - any interaction from the user. + * On a hirsute VM, make sure all packages are up to date + by running `sudo apt update && sudo apt upgrade -y` + * `sudo do-release-upgrade -d --frontend=DistUpgradeViewNonInteractive` + * Observe that the the upgrader displays the release notes followed + by a question in the form of "Continue [yN]" + * Type N and press enter to cancel the upgrade + * Install ubuntu-release-upgrader from hirsute-proposed + * `sudo do-release-upgrade -d --frontend=DistUpgradeViewNonInteractive` + * Observe that the release upgrade completes successfully without + any interaction from the user. [Regression Potential] - * If the check for the specific frontend is not - properly written it may be possible that - the other frontends no longer display the release - notes and ask the user if they want to continue. - * This can be tested by running "do-release-upgrade" - with --frontend=DistUpgradeViewGtk3 and - --frontend=DistUpgradeViewText + * If the check for the specific frontend is not + properly written it may be possible that + the other frontends no longer display the release +
[Bug 1944769] [NEW] [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound
Public bug reported: Hey! I installed Ubuntu with VM yesturday and it turned out that the sound is still fine on Windows, but when i use Ubuntu via VM, it sounds like endless crackers every single second, i could also compared it to hickups. Tried to find a solution in the internet, but it didn't help at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timcpau 20990 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Sep 23 23:49:13 2021 InstallationDate: Installed on 2021-09-22 (1 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH successful Symptom_Card: Built-in Audio - Intel 82801AA-ICH Symptom_PulseAudioLog: сен 22 09:37:53 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=815 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") сен 22 09:37:53 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.34' (uid=1000 pid=815 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") сен 23 23:06:05 timcpau-VirtualBox dbus-daemon[459]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.233' (uid=1000 pid=20990 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944769 Title: [ICH - Intel 82801AA-ICH, playback] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1944769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944767] Re: During install, panel content is missing
** Attachment added: "shot during install" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944767/+attachment/5527437/+files/nopanelcontent.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944767 Title: During install, panel content is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944767] [NEW] During install, panel content is missing
Public bug reported: During install, there is nothing in the panel, no wifi icon, nothing at all ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.5 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: Budgie Date: Thu Sep 23 20:42:39 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-budgie.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-Budgie 21.10 "Impish Indri" - Beta amd64 (20210923) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.10.5 ubuntu-budgie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944767 Title: During install, panel content is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1944767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944642] Re: Xenial (ESM) - 4.15.0-156 creates event storm when ejecting DVD-ROM media
Thanks very much for the info and assistance. I won't have the time to get to this today, but absolutely will have the time tomorrow. Hopefully that works with your schedule. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944642 Title: Xenial (ESM) - 4.15.0-156 creates event storm when ejecting DVD-ROM media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
@Peabody Yes, I have ran into the same problems on 21.04 and reported that separately at https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1927337 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944397] Re: HDMI does not display anything with Impish RPi desktop image
Thanks. This will break Wayland though, no? "The full KMS overlay is required for X11 application support under wayland." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944397 Title: HDMI does not display anything with Impish RPi desktop image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944397] Re: HDMI does not display anything with Impish RPi desktop image
** Summary changed: - hdmi broken on 5.13.0-1007-raspi + HDMI does not display anything with Impish RPi desktop image ** Description changed: + Workaround + -- + With media which you will boot off of change the line dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d in /system-boot/config.txt + + Original Description + Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. - ProblemType: Bug - DistroRelease: Ubuntu 21.10 + ProblemType: BugDistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: - SHELL=/bin/bash - LANG=en_US.UTF-8 - TERM=vt100 - XDG_RUNTIME_DIR= - PATH=(custom, user) - SourcePackage: linux-raspi + SHELL=/bin/bash + LANG=en_US.UTF-8 + TERM=vt100 + XDG_RUNTIME_DIR= + PATH=(custom, user)SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944397 Title: HDMI does not display anything with Impish RPi desktop image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942908] Re: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS
** Tags added: focal hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942908 Title: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1942908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944004] Re: snapd.seeded.service never finishes on non-amd64
We have reproducers on arm64 and s390x now. I'm seeing the same things as the snapd.log in https://bugs.launchpad.net/cloud-images/+bug/1944004/comments/1 any attempts to restart the service do the same thing. So something has set up snapd with incorrect permissions. At this point, I'm going to have to defer to someone on the snapd team for further debugging help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942908] Re: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS
s390-tools-signed sru debdiff (focal) ** Patch added: "s390-tools-signed sru debdiff (focal)" https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1942908/+attachment/5527430/+files/debdiff_lp1942908_s390-tools-signed_sru_focal.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942908 Title: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1942908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837040] Re: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on ARM64 / B-hwe P9
Spotted with hirsute/linux-azure 5.11.0-1017.18 on a single instance. ** Tags added: sru-20210906 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837040 Title: function traceon/off triggers in ftace from ubuntu_kernel_selftests failed on ARM64 / B-hwe P9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891673] Re: qrouter ns ip rules not deleted when fip removed from vm
Reviewed: https://review.opendev.org/c/openstack/neutron/+/810425
Committed:
https://opendev.org/openstack/neutron/commit/7eaa84a0cd48adb2ecd7653640d32aea8096e786
Submitter: "Zuul (22348)"
Branch:stable/ussuri
commit 7eaa84a0cd48adb2ecd7653640d32aea8096e786
Author: Rodolfo Alonso Hernandez
Date: Thu Jun 3 14:49:45 2021 +
Populate self.floating_ips_dict using "ip rule" information
When the L3 agent starts, reads the floating IP rule priority from
a state file created by "FipRulePriorityAllocator". In case of not
having all floating IPs registers in this file, the method:
- Creates a new priority for this floating IP.
- Creates the "ip rule" in the namespace.
- Adds a new entry in "self.floating_ips_dict".
All "ip rules" present in the namespace that do not match the
registered fixed IP address ("from") and the priority assigned
are deleted.
Closes-Bug: #1891673
Closes-Bug: #1929821
Conflicts:
neutron/tests/unit/agent/l3/test_dvr_local_router.py
Change-Id: Ia3fbde3304ab5f3c309dc62dbf58274afbcf4614
(cherry picked from commit a03c240ef4ea1d4b874b618dbd0163a3a2f7024c)
(cherry picked from commit b4ad1a2775d00cd6d14bd4766a0a1c5c41332d89)
** Tags added: in-stable-ussuri
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891673
Title:
qrouter ns ip rules not deleted when fip removed from vm
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1891673/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
Same problem on Ubuntu 21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933092] Re: snat arp entry missing in qrouter namespace
Reviewed: https://review.opendev.org/c/openstack/neutron/+/807244 Committed: https://opendev.org/openstack/neutron/commit/c689ac5a661a15ec7ad1098d21dc5affce97fb04 Submitter: "Zuul (22348)" Branch:stable/train commit c689ac5a661a15ec7ad1098d21dc5affce97fb04 Author: Hemanth Nakkina Date: Fri Jul 2 17:01:55 2021 +0530 Update arp entry of snat port on qrouter ns In some cases, the arp entry of snat port is not updated in qrouter namespace. l3-agent calls get_ports_by_subnet() while setting arps for the subnet. And the snat port is not returned if it is still unbound. One of the scenario this is observed is when router is created, external gateway set and internal subnet attached to router in quick succession. This patch retrieves snat port details from router info as well and updates arp entry for snat port. Conflicts: neutron/agent/l3/dvr_local_router.py Closes-Bug: #1933092 Change-Id: I7ee797b4b930306cf6360922d855f8b24f1b813d (cherry picked from commit be7d0bb6abc893e53dfc864c52506928b1d38fa3) (cherry picked from commit f1a9f4ed62fd2567cac174f80f87de53148ea7b9) ** Tags added: in-stable-train -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933092 Title: snat arp entry missing in qrouter namespace To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1933092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943049] Re: Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
Hi. I am sorry to ask this, but: Has the solution already become available for "normal" users? (If not, I can just wait a bit, no problem.) What would I need to do to get it working on my system? The reason why I am asking is that I have already updated my system just now (apt-get update) and re-downloaded the ubuntu:21.10 image and my duplicated bug as reported in https://bugs.launchpad.net/cloud- images/+bug/1943293 still persists. I am running Ubuntu 21.04 on my host system and use the ubuntu:21.10 container. > sudo docker run --rm -it --entrypoint=/bin/bash "ubuntu:21.10" # apt-get update && apt-get install -y curl # curl https://www.bing.com curl: (6) getaddrinfo() thread failed to start Many thanks, Thomas. P.S.: Argh, just now I see that under "affects", for "docker.io (Ubuntu)", it just says "confirmed", not "fix released" ... that explains it ^_^ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943049 Title: Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1943049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944764] Re: APN command line : 'username' and 'user' are transposed
I see the last command line example at the following URL also shows "username" and "user" are transposed: https://ubuntu.com/core/docs/networkmanager/configure-cellular- connections The page currently shows: $ nmcli c add type gsm ifname con-name apn username password pin The page should show: $ nmcli c add type gsm ifname con-name apn user password pin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944764 Title: APN command line : 'username' and 'user' are transposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1944764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942908] Re: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS
** Merge proposal linked: https://code.launchpad.net/~fheimes/ubuntu/+source/s390-tools-signed/+git/s390-tools-signed/+merge/409096 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942908 Title: Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1942908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944762] Re: misleading motd after support ends
Thanks Lucas, that's the trouble with looking at nine-year-old software, sometimes which package is responsible for which files changes over time. :) ** Also affects: update-notifier (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/1944762 Title: misleading motd after support ends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1944762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944764] [NEW] APN command line : 'username' and 'user' are transposed
Public bug reported: Pertains to the following man page's Connection Management Commands section : https://manpages.ubuntu.com/manpages/xenial/man1/nmcli.1.html Man page currently shows: type gsm [apn APN] [username user] [password passwd] apn APN - GSM Access Point Name. user user name. password password. type cdma [username user] [password passwd] user user name. password password. The man page should be corrected to show: type gsm [apn APN] [user username] [password passwd] type cdma [user username] [password passwd] I suggest correcting the man page so it's correct for people trying to use this version of Ubuntu. ** Affects: network-manager (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/1944764 Title: APN command line : 'username' and 'user' are transposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1944764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944642] Re: Xenial (ESM) - 4.15.0-156 creates event storm when ejecting DVD-ROM media
Kenneth - I'm anticipating that you might have version issues with your installed kernels. Here is the same kernel but with a higher version number so that it should be the default boot kernel: wget https://kernel.ubuntu.com/~rtg/dvd-event-storm-lp1944642/4.15.0-160.0_1.da738569aabed1847bf462f9b75c3d952fd37cad/amd64/linux-image-unsigned-4.15.0-160-generic_4.15.0-160.0~1.da738569aabed1847bf462f9b75c3d952fd37cad_amd64.deb wget https://kernel.ubuntu.com/~rtg/dvd-event-storm-lp1944642/4.15.0-160.0_1.da738569aabed1847bf462f9b75c3d952fd37cad/amd64/linux-modules-4.15.0-160-generic_4.15.0-160.0~1.da738569aabed1847bf462f9b75c3d952fd37cad_amd64.deb sudo dpkg -i linux-image*.deb linux-modules*.deb sudo reboot I will take care that subsequent test kernels have an increasing version number so that once installed they always become the default boot kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944642 Title: Xenial (ESM) - 4.15.0-156 creates event storm when ejecting DVD-ROM media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944763] [NEW] sed temp file appears in nautilus but not in ls -a
Public bug reported: **Expected behaviour**: Temp files created by sed should disappear from Nautilus after automatic deletion **Observed behaviour**: Temp files showed in Nautilus for some time. **Description**: After using: sed -i 's/CAD/cad/g' FILENAME The temp files created by sed (sed#) continued showing in Nautilus for some minutes (they disappear if I close and reopen Nautilus), and I could interact with them (see permissions, double click to open (which errored out by not finding an app to open it), but couldn't change them (move, change permissions, delete) These temp files did not appear with ls -a. The file is 3.6kb long. The behaviour doesn't happen with: sed -i 's/cad/CAD/g' FILENAME but only with: sed -i 's/CAD/cad/g' FILENAME **Outputs**: >>>df . Sist. Arq. Blocos de 1K Usado Disponível Uso% Montado em /dev/sda2 459924552 235486388 201005512 54% / >>>lsb_release -rd: Description:Ubuntu 21.04 Release:21.04 >>>apt-cache policy nautilus nautilus: Instalado: 1:3.38.2-1ubuntu2 Candidato: 1:3.38.2-1ubuntu2 Tabela de versão: *** 1:3.38.2-1ubuntu2 500 500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.38.2-1ubuntu1 500 500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 23 15:51:04 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(860, 495)' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-04-20 (155 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-08 (107 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Description changed: **Expected behaviour**: Temp files created by sed should disappear from Nautilus after automatic deletion **Observed behaviour**: Temp files showed in Nautilus for some time. **Description**: After using: sed -i 's/CAD/cad/g' FILENAME The temp files created by sed (sed#) continued showing in Nautilus - for some time (about 20m), and I could interact with them (see - permissions, double click to open (which errored out by not finding an - app to open it), but couldn't change them (move, change permissions, - delete) + for some minutes (they disappear if I close and reopen Nautilus), and I + could interact with them (see permissions, double click to open (which + errored out by not finding an app to open it), but couldn't change them + (move, change permissions, delete) These temp files did not appear with ls -a. The file is 3.6kb long. The behaviour doesn't happen with: sed -i 's/cad/CAD/g' FILENAME but only with: sed -i 's/CAD/cad/g' FILENAME **Outputs**: >>>df . Sist. Arq. Blocos de 1K Usado Disponível Uso% Montado em /dev/sda2 459924552 235486388 201005512 54% / >>>lsb_release -rd: Description: Ubuntu 21.04 Release: 21.04 >>>apt-cache policy nautilus nautilus: - Instalado: 1:3.38.2-1ubuntu2 - Candidato: 1:3.38.2-1ubuntu2 - Tabela de versão: - *** 1:3.38.2-1ubuntu2 500 - 500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:3.38.2-1ubuntu1 500 - 500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages + Instalado: 1:3.38.2-1ubuntu2 + Candidato: 1:3.38.2-1ubuntu2 + Tabela de versão: + *** 1:3.38.2-1ubuntu2 500 + 500 http://mirror.ufscar.br/ubuntu hirsute-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:3.38.2-1ubuntu1 500 + 500 http://mirror.ufscar.br/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown
[Bug 1851232] Re: Laptop does not suspend when using open-iscsi
A good thing to try is to use Hirsute or Impish, which has a different upstream version than Focal, and see if the behave is the same. In case the bug is fixed in a newer version we could bisect and try to find the needed patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851232 Title: Laptop does not suspend when using open-iscsi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1851232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944762] Re: misleading motd after support ends
Hi Seth, although ubuntu-advantage-tools does generate some MOTD messages, we are not currently generating the message you are describing here. I think it is better to tag the update-notifier package in this bug. However, if you think there is something we can still do on our side, please let me know. ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944762 Title: misleading motd after support ends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1944762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524635] Re: haproxy syslog configuration causes double logging
The package in the PPA was not tested by any affected people for 5 years, moreover, Trusty now reached the end of the standard support. Due to that I am unsubscribing ubuntu-server from 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/1524635 Title: haproxy syslog configuration causes double logging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1524635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944642] Re: Xenial (ESM) - 4.15.0-156 creates event storm when ejecting DVD-ROM media
Hi Kenneth - yes, I'll build kernels and you tell me which ones are good or bad. Here is the first kernel: wget https://kernel.ubuntu.com/~rtg/dvd-event-storm-lp1944642/4.15.0-155.162_1.da738569aabed1847bf462f9b75c3d952fd37cad/amd64/linux-image-unsigned-4.15.0-155-generic_4.15.0-155.162~1.da738569aabed1847bf462f9b75c3d952fd37cad_amd64.deb wget https://kernel.ubuntu.com/~rtg/dvd-event-storm-lp1944642/4.15.0-155.162_1.da738569aabed1847bf462f9b75c3d952fd37cad/amd64/linux-modules-4.15.0-155-generic_4.15.0-155.162~1.da738569aabed1847bf462f9b75c3d952fd37cad_amd64.deb sudo dpkg -i linux-image*.deb linux-modules*.deb sudo reboot Make sure you're running the right version by checking 'uname -a', e.g., Linux ip-172-31-3-147 4.15.0-155-generic #162~1.da738569aabed1847bf462f9b75c3d952fd37cad SMP Thu Sep 23 1 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944642 Title: Xenial (ESM) - 4.15.0-156 creates event storm when ejecting DVD-ROM media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753329] Re: deprecate and stop packaging?
This bug is quite old and in the past we had some issue in keeping docker.io up-to-date following upstream closely. Nowadays, the situation is different and we have been able to provide almost always the latest upstream version to our users across all the supported releases. Since this is not a problem anymore, I'll be setting the Status to Invalid and unsubscribe ubuntu-server from this bug. ** Changed in: docker.io (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1753329 Title: deprecate and stop packaging? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1753329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944397] Re: hdmi broken on 5.13.0-1007-raspi
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1944397 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944397 Title: hdmi broken on 5.13.0-1007-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944397/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944761] plasmashell crashed with SIGSEGV in QThreadStorageData::get() - crashed after going to endless loop and issuing "plasmashell --replace"
StacktraceTop: QThreadStorageData::get (this=this@entry=0x0) at thread/qthreadstorage.cpp:122 qThreadStorage_localData (d=...) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:69 QThreadStorage::localData (this=0x0) at ../../include/QtCore/../../src/corelib/thread/qthreadstorage.h:145 QOpenGLContext::currentContext () at kernel/qopenglcontext.cpp:422 QOpenGLShader::QOpenGLShader (this=0x7f4e1c1ff680, type=..., parent=0x7f4e1c08ed58) at opengl/qopenglshaderprogram.cpp:445 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944761 Title: plasmashell crashed with SIGSEGV in QThreadStorageData::get() - crashed after going to endless loop and issuing "plasmashell --replace" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1944761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944762] [NEW] misleading motd after support ends
Public bug reported: Hello, 12.04 ESM support has ended; however, on a 12.04 machine, the MOTD still says: This Ubuntu 12.04 system is configured to receive extended security updates from Canonical: * https://www.ubuntu.com/esm I think the MOTD should clearly state that ESM support has ended for this machine. It's a bit late to do anything about this for precise; can we address this before we retire trusty? Thanks ** Affects: ubuntu-advantage-tools (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/1944762 Title: misleading motd after support ends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1944762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944761] [NEW] plasmashell crashed with SIGSEGV in QThreadStorageData::get() - crashed after going to endless loop and issuing "plasmashell --replace"
Public bug reported: well, i do not know what exactly happened this time, but in the recent days plasmashell seemed to enter a long or endless loop after some time of high system load. this leads to sluggish reaction to mouse clicks (1-2s delay after clicking a different window until it is put to front). "plasmashell --replace" usually fixes that. this time the runaway plasmashell also crashed after issuing the replace-command. i hope that helps. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: plasma-workspace 4:5.22.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-lowlatency 5.13.13 Uname: Linux 5.13.0-16-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Sep 23 20:40:15 2021 ExecutablePath: /usr/bin/plasmashell InstallationDate: Installed on 2020-09-09 (379 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcCmdline: /usr/bin/plasmashell --replace ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= LANGUAGE= SegvAnalysis: Segfault happened at: 0x7f4e464cd91a <__strlen_sse2+42>: movdqu (%rax),%xmm4 PC (0x7f4e464cd91a) ok source "(%rax)" (0x5621f2452772) not located in a known VMA region (needed readable region)! destination "%xmm4" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: plasma-workspace StacktraceTop: QThreadStorageData::get() const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 QOpenGLContext::currentContext() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 QOpenGLShader::QOpenGLShader(QFlags, QObject*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 Title: plasmashell crashed with SIGSEGV in QThreadStorageData::get() UpgradeStatus: Upgraded to impish on 2021-06-05 (109 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers separator: ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash impish ** Information type changed from Private to Public ** Summary changed: - plasmashell crashed with SIGSEGV in QThreadStorageData::get() + plasmashell crashed with SIGSEGV in QThreadStorageData::get() - crashed after going to endless loop and issuing "plasmashell --replace" -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1944761 Title: plasmashell crashed with SIGSEGV in QThreadStorageData::get() - crashed after going to endless loop and issuing "plasmashell --replace" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1944761/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1412548] Re: OCF Resource Agent "Filesystem" is still CMAN dependent
As stated in comment #4, this bug seems to no apply to Ubuntu Xenial and Ubuntu Trusty already reached end of standard support a couple of years ago. Due to that I am removing the server-next tag and unsubscribing ubuntu-server from this bug. ** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412548 Title: OCF Resource Agent "Filesystem" is still CMAN dependent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1412548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915218] Re: plasmashell crashed with SIGSEGV in std::__atomic_base::load() - crashed after display resolution change
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915218 Title: plasmashell crashed with SIGSEGV in std::__atomic_base::load() - crashed after display resolution change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1915218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
