[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus
The cloud-init.service file is provided by livecd-rootfs, but we aren't sure what triggered this issue. ** Also affects: livecd-rootfs (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/2081124 Title: systemd service dependency loop between cloud-init, NetworkManager and dbus To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081124] Re: systemd service dependency loop between cloud-init, NetworkManager and dbus
** Summary changed: - systemd service dependency loop between cloud-init, NetworkManager an dbus + systemd service dependency loop between cloud-init, NetworkManager and dbus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081124 Title: systemd service dependency loop between cloud-init, NetworkManager and dbus To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081124] [NEW] systemd service dependency loop between cloud-init, NetworkManager an dbus
Public bug reported: We got errors that some services like snapd and NetworkManager is not started when running cloud-init or desktop, excerpt from journal below: Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found ordering cycle on NetworkManager-wait-online.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on basic.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on sockets.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on cloud-init-hotplugd.socket/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on cloud-config.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on cloud-init.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Job NetworkManager-wait-online.service/start deleted to break ordering cycle starting with cloud-init.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found ordering cycle on dbus.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on basic.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on sockets.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on cloud-init-hotplugd.socket/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on cloud-config.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on cloud-init.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on NetworkManager.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Job dbus.service/start deleted to break ordering cycle starting with NetworkManager.service/start Related logs and service files are attached in sosreport. Internal reference: NANTOU-473 ** Affects: oem-priority Importance: Critical Status: New ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Attachment added: "sosreport-a-STELLA-191-2024-09-16-ilbirhd.tar.xz" https://bugs.launchpad.net/bugs/2081124/+attachment/5819090/+files/sosreport-a-STELLA-191-2024-09-16-ilbirhd.tar.xz ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Tags added: oem-priority ** Description changed: We got errors that some services like snapd and NetworkManager is not started when running cloud-init or desktop, excerpt from journal below: Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found ordering cycle on NetworkManager-wait-online.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on basic.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on sockets.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on cloud-init-hotplugd.socket/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on cloud-config.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Found dependency on cloud-init.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: cloud-init.service: Job NetworkManager-wait-online.service/start deleted to break ordering cycle starting with cloud-init.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found ordering cycle on dbus.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on basic.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on sockets.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on cloud-init-hotplugd.socket/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on cloud-config.target/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on cloud-init.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Found dependency on NetworkManager.service/start Sep 13 12:37:41 localhost.localdomain systemd[1]: NetworkManager.service: Job dbus.service/start deleted to break ordering cycle starting with NetworkManager.service/start + Related logs and service files are attached in sosreport. + Internal reference: NANTOU-473 ** Summary changed: - systemd service dependency between clo
[Bug 2076164] Re: List of "Scan new fingerprint" is incorrect when one or more finger is enrolled
Should we fix this issue by bumping minor version, or adding a patch to this package? I see 46.3 is in Noble at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076164 Title: List of "Scan new fingerprint" is incorrect when one or more finger is enrolled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069408] Re: OOBE has a blue background
This issue won't appear in stock Ubuntu install, because in stock Ubuntu we do not use gnome-initial-setup to set up the first user. This issue only occurs on OEM images and Raspberry Pi image (idk whether we have them, but that's what I've told) To enter gnome-initial-setup to set up first user, please refer to the wiki article: https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeInitialSetup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069408 Title: OOBE has a blue background To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2069408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069408] Re: OOBE has a blue background
The issue still persists by default on gnome-initial-setup 46.3-1ubuntu3~24.04.1 I received messages from Desktop Team that this issue will only be fixed on 24.10 onwards. However, it is possible to workaround with a patch in /usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override # for GDM/DM # FIXME: move to :Ubuntu-Greeter once upstream supports this, see LP: #1788 [org.gnome.desktop.interface:GNOME-Greeter] gtk-theme = 'Yaru' icon-theme = 'Yaru' cursor-theme = 'Yaru' font-name = 'Ubuntu 11' monospace-font-name = 'Ubuntu Mono 13' font-antialiasing = 'rgba' [org.gnome.login-screen] logo='/usr/share/plymouth/ubuntu-logo.png' + [org.gnome.desktop.background:GNOME-Greeter] + picture-uri = 'file:///usr/share/backgrounds/warty-final-ubuntu.png' + picture-uri-dark = 'file:///usr/share/backgrounds/ubuntu-wallpaper-d.png' + show-desktop-icons = false -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069408 Title: OOBE has a blue background To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2069408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077603] Re: debsum of /usr/sbin/start-stop-daemon failed
Tested livecd.ubuntu.minimal.squashfs from https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/oracular/ubuntu/+build/676054 (oracular) by `sudo debsums --root [squashfs_root] -c`, it replied no error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077603 Title: debsum of /usr/sbin/start-stop-daemon failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077603] Re: debsum of /usr/sbin/start-stop-daemon failed
** Description changed: [ Impact ] The bug causes debsums to fail on the binary file "/usr/sbin/start-stop- daemon" from package "dpkg", which is updated during live-build building livecd rootfs. [ Test Plan ] 1. Use Launchpad livefs feature and enable proposed 2. Build a Ubuntu livefs - 3. Chroot into minimal.squashfs + 3. Mount minimal.squashfs - 4. run debsums -c to check the checksum, there should be no output - (which indicates files failed to match the package) + 4. run "debsums --root [mount dir] -c", there should be no output (which + indicates files failed to match the package) [ Where problems could occur ] For now, no idea where it could go wrong, as we are not using live-build across releases. [ Original Report ] The image generated by the live-build version in noble has an error that checksum of /usr/sbin/start-stop-daemon mismatched. According to build log, dpkg has been updated from 1.22.6ubuntu6 to 1.22.6ubuntu6.1, however the checksum of the file "start-stop-daemon" matches the one from 1.22.6ubuntu6. Checking the log of live-build in Debian, they have fixed this issue by changing the dpkg-divert path from /sbin/start-stop-daemon to /usr/sbin/start-stop-daemon. I am trying to fix this issue in this direction. Related: https://bugs.debian.org/1064408 ** Description changed: [ Impact ] The bug causes debsums to fail on the binary file "/usr/sbin/start-stop- daemon" from package "dpkg", which is updated during live-build building livecd rootfs. [ Test Plan ] 1. Use Launchpad livefs feature and enable proposed 2. Build a Ubuntu livefs 3. Mount minimal.squashfs - 4. run "debsums --root [mount dir] -c", there should be no output (which - indicates files failed to match the package) + 4. run "sudo debsums --root [mount dir] -c", there should be no output + (which indicates files failed to match the package) [ Where problems could occur ] For now, no idea where it could go wrong, as we are not using live-build across releases. [ Original Report ] The image generated by the live-build version in noble has an error that checksum of /usr/sbin/start-stop-daemon mismatched. According to build log, dpkg has been updated from 1.22.6ubuntu6 to 1.22.6ubuntu6.1, however the checksum of the file "start-stop-daemon" matches the one from 1.22.6ubuntu6. Checking the log of live-build in Debian, they have fixed this issue by changing the dpkg-divert path from /sbin/start-stop-daemon to /usr/sbin/start-stop-daemon. I am trying to fix this issue in this direction. Related: https://bugs.debian.org/1064408 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077603 Title: debsum of /usr/sbin/start-stop-daemon failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077603] Re: debsum of /usr/sbin/start-stop-daemon failed
** Description changed: [ Impact ] The bug causes debsums to fail on the binary file "/usr/sbin/start-stop- daemon" from package "dpkg", which is updated during live-build building livecd rootfs. [ Test Plan ] 1. Use Launchpad livefs feature and enable proposed 2. Build a Ubuntu livefs - 3. Install the image into a system + 3. Chroot into minimal.squashfs - 4. Install debsums and run "debsums -c" into the installed system, there - should be no output (which indicates the mismatched files) + 4. run debsums -c to check the checksum, there should be no output + (which indicates files failed to match the package) [ Where problems could occur ] For now, no idea where it could go wrong, as we are not using live-build across releases. [ Original Report ] The image generated by the live-build version in noble has an error that checksum of /usr/sbin/start-stop-daemon mismatched. According to build log, dpkg has been updated from 1.22.6ubuntu6 to 1.22.6ubuntu6.1, however the checksum of the file "start-stop-daemon" matches the one from 1.22.6ubuntu6. Checking the log of live-build in Debian, they have fixed this issue by changing the dpkg-divert path from /sbin/start-stop-daemon to /usr/sbin/start-stop-daemon. I am trying to fix this issue in this direction. Related: https://bugs.debian.org/1064408 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077603 Title: debsum of /usr/sbin/start-stop-daemon failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077603] Re: debsum of /usr/sbin/start-stop-daemon failed
Reattaching debdiff to target oracular ** Description changed: + [ Impact ] + + The bug causes debsums to fail on the binary file "/usr/sbin/start-stop- + daemon" from package "dpkg", which is updated during live-build building + livecd rootfs. + + [ Test Plan ] + + 1. Use Launchpad livefs feature and enable proposed + + 2. Build a Ubuntu livefs + + 3. Install the image into a system + + 4. Install debsums and run "debsums -c" into the installed system, there + should be no output (which indicates the mismatched files) + + [ Where problems could occur ] + + For now, no idea where it could go wrong, as we are not using live-build + across releases. + + [ Original Report ] + The image generated by the live-build version in noble has an error that checksum of /usr/sbin/start-stop-daemon mismatched. According to build log, dpkg has been updated from 1.22.6ubuntu6 to 1.22.6ubuntu6.1, however the checksum of the file "start-stop-daemon" matches the one from 1.22.6ubuntu6. Checking the log of live-build in Debian, they have fixed this issue by changing the dpkg-divert path from /sbin/start-stop-daemon to /usr/sbin/start-stop-daemon. I am trying to fix this issue in this direction. Related: https://bugs.debian.org/1064408 ** Patch removed: "live-build_3.0~a57-1ubuntu49_3.0~a57-1ubuntu50.debdiff" https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+attachment/5808172/+files/live-build_3.0~a57-1ubuntu49_3.0~a57-1ubuntu50.debdiff ** Patch added: "live-build_3.0~a57-1ubuntu49_3.0~a57-1ubuntu50.debdiff" https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+attachment/5808173/+files/live-build_3.0~a57-1ubuntu49_3.0~a57-1ubuntu50.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077603 Title: debsum of /usr/sbin/start-stop-daemon failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077603] Re: debsum of /usr/sbin/start-stop-daemon failed
Attaching debdiff that I can confirm the issue can be fixed. Will convert this into SRU soon. ** Patch added: "live-build_3.0~a57-1ubuntu49_3.0~a57-1ubuntu50.debdiff" https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+attachment/5808172/+files/live-build_3.0~a57-1ubuntu49_3.0~a57-1ubuntu50.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077603 Title: debsum of /usr/sbin/start-stop-daemon failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2034481] Re: Cannot verify fingerprint if the storage is empty (Synaptics)
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2034481 Title: Cannot verify fingerprint if the storage is empty (Synaptics) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2034481] Re: Cannot verify fingerprint if the storage is empty (Synaptics)
Tested version: 1:1.94.3+tod1-0ubuntu2~22.04.08 Test Plan: * Enroll one random finger * Reboot and enter BIOS to reset fingerprint device (HP laptops) * Boot into system and re-enroll the finger * Login system with enrolled finger === Test passed if the first enrolled finger and the re-enrolled finger are the same finger. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2034481 Title: Cannot verify fingerprint if the storage is empty (Synaptics) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077603] [NEW] debsum of /usr/sbin/start-stop-daemon failed
Public bug reported: The image generated by the live-build version in noble has an error that checksum of /usr/sbin/start-stop-daemon mismatched. According to build log, dpkg has been updated from 1.22.6ubuntu6 to 1.22.6ubuntu6.1, however the checksum of the file "start-stop-daemon" matches the one from 1.22.6ubuntu6. Checking the log of live-build in Debian, they have fixed this issue by changing the dpkg-divert path from /sbin/start-stop-daemon to /usr/sbin/start-stop-daemon. I am trying to fix this issue in this direction. Related: https://bugs.debian.org/1064408 ** Affects: live-build (Ubuntu) Importance: Undecided Status: New ** Summary changed: - debsum of start-stop-daemon failed due to usr-is-merged + debsum of start-stop-daemon failed ** Summary changed: - debsum of start-stop-daemon failed + debsum of /usr/sbin/start-stop-daemon failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077603 Title: debsum of /usr/sbin/start-stop-daemon failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2077603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076164] Re: List of "Scan new fingerprint" is incorrect when one or more finger is enrolled
** Description changed: [ Impact ] * This issue causes other random fingers not able to enroll for authentication, once one or more fingers are enrolled. - * This issue is going to be fixed by SRUing minor updates of gnome- + * This issue is going to be fixed by SRUing minor updates of gnome- control-center. [ Test Plan ] - 1. Install Ubuntu 24.04 with a fingerprint reader enabled + 1. Install Ubuntu Desktop with a fingerprint reader enabled - 2. In Fingerprints page, enroll a finger, then the list in "Scan new + 2. In Fingerprints page, enroll a finger, then the list in "Scan new fingerprint" should hide the finger enrolled - 3. Repeat 2 until all fingers are enrolled + 3. Repeat 2 until all fingers are enrolled [ Where problems could occur ] * Regressions due to other fixes from gnome-control-center might be introduced. [ Original description ] In Ubuntu 24.04 OS, we are unable to enroll 10 fingerprints for a user through the GUI. Generally, the GUI displays the names of all 10 fingers, such as left little finger, left index finger, etc. Before enrolling any fingerprint, it correctly shows all 10 finger names. However, once a fingerprint is enrolled, the order becomes clumsy. For example, if we select 'left little finger' for fingerprint enrollment, the enrollment is successful, and the enrolled finger name is shown as 'left little finger' (same as selected). However, in the remaining list of fingers, a different finger name (like 'right index finger') is removed, and 'left little finger' still appears in the list. If we select 'left little finger' again from the list, the existing enrolled fingerprint gets overwritten with the new one. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04b-edge-20240621-8 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-08-01 (5 days ago) InstallationMedia: Ubuntu OEM 24.04 LTS "Noble Numbat" - Release amd64 (20240621) Package: gnome-control-center 1:46.0.1-1ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.10.0-1005.5-oem 6.10.0-rc4 Tags: noble third-party-packages Uname: Linux 6.10.0-1005-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076164 Title: List of "Scan new fingerprint" is incorrect when one or more finger is enrolled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076164] Re: fingerprint mismatch and disconnect with name
.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04b-edge-20240621-8 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-08-01 (5 days ago) InstallationMedia: Ubuntu OEM 24.04 LTS "Noble Numbat" - Release amd64 (20240621) Package: gnome-control-center 1:46.0.1-1ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.10.0-1005.5-oem 6.10.0-rc4 Tags: noble third-party-packages Uname: Linux 6.10.0-1005-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True ** Summary changed: - fingerprint mismatch and disconnect with name + List of "Scan new fingerprint" are incorrect when one or more finger is enrolled ** Changed in: oem-priority Importance: Undecided => Medium ** Changed in: oem-priority Assignee: (unassigned) => Yao Wei (medicalwei) ** Summary changed: - List of "Scan new fingerprint" are incorrect when one or more finger is enrolled + List of "Scan new fingerprint" is incorrect when one or more finger is enrolled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076164 Title: List of "Scan new fingerprint" is incorrect when one or more finger is enrolled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076164] Re: fingerprint mismatch and disconnect with name
from Bug #2076142: A known commit exists to fix this issue: https://gitlab.gnome.org/GNOME/gnome-control- center/-/commit/3b7ea05d43c0dce4201279d5945488795b66bce7 ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: oem-priority ** Changed in: oem-priority 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/2076164 Title: fingerprint mismatch and disconnect with name To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076142] Re: List of unenrolled fingerprint to add shows wrong fingers
*** This bug is a duplicate of bug 2076164 *** https://bugs.launchpad.net/bugs/2076164 ** This bug has been marked a duplicate of bug 2076164 fingerprint mismatch and disconnect with name -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076142 Title: List of unenrolled fingerprint to add shows wrong fingers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071449] Re: Fixes and improvements for 'new user creation'
** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071449 Title: Fixes and improvements for 'new user creation' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2071449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076142] [NEW] List of unenrolled fingerprint to add shows wrong fingers
Public bug reported: On gnome-control-center 1:46.0.1-1ubuntu7 in Ubuntu 24.04, the list of unenrolled fingers are wrong due to a filtering bug Reproducible steps: Enroll "Left ring finger" in a fingerprint-enabled system. Expected: The list in "Scan new fingerprint" hides "Left ring finger". Actual: The list in "Scan new fingerprint" shows "Left ring finger", instead "Left index finger" is hidden. A known patch exists to fix this issue: https://gitlab.gnome.org/GNOME/gnome-control- center/-/commit/3b7ea05d43c0dce4201279d5945488795b66bce7 ** Affects: oem-priority Importance: Undecided Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076142 Title: List of unenrolled fingerprint to add shows wrong fingers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071449] Re: Fixes and improvements for 'new user creation'
> Given that "ppas" were mentioned in the bug description as having been used before for testing, prior to upload, I feel that this information is important. The test was independent than the "ppa" one mentioned in the description. This is done using stock Ubuntu image, then installed gnome-initial-setup 46.2-1ubuntu0.24.04.1 from noble-proposed. Should I redo the tests again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071449 Title: Fixes and improvements for 'new user creation' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2071449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071449] Re: Fixes and improvements for 'new user creation'
New user feature is verified according to https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeInitialSetup ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071449 Title: Fixes and improvements for 'new user creation' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2071449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069391] Re: debsums reports file changed /usr/lib/systemd/system/cloud-init.service
This seems to be the issue caused by livecd-rootfs: livecd-rootfs (2.816) lunar; urgency=medium [ Chad Smith ] * Replace cloud-init.service on NetworkManager images to address an ordering cycle interfering with autoinstall with ubuntu-desktop-installer. (LP: #2008952) -- Dan Bungert Fri, 24 Mar 2023 18:35:46 -0600 Is there something to be fixed on either side? ** Also affects: livecd-rootfs (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/2069391 Title: debsums reports file changed /usr/lib/systemd/system/cloud- init.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2069391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067979] Re: Language selection is skipped for new installations
Here's Salsa MR: https://salsa.debian.org/gnome-team/gnome-initial- setup/-/merge_requests/31 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067979 Title: Language selection is skipped for new installations To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067979] Re: Language selection is skipped for new installations
Here's the debdiff (against noble, since I am testing on noble and we plan to move away from g-i-s on oracular or 26.04 at least) that enables language page, and fixes segfault when language is selected. The reason why it is not using ubuntu_page_table, is that at the time it runs gnome-initial-setup to create the first user, XDG_CURRENT_DESKTOP is set to "GNOME-Greeter:GNOME", which has no "ubuntu" or "unity" in it. Also, although gnome-initial-setup is maintained under Salsa, there's no ubuntu/noble branch we can merge to. If there is such a branch, I am happy to do it on Salsa. ** Patch added: "gnome-initial-setup_46.0-1ubuntu7.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2067979/+attachment/5786205/+files/gnome-initial-setup_46.0-1ubuntu7.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067979 Title: Language selection is skipped for new installations To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067979] Re: Language selection is skipped for new installations
OK I tried to install g-i-s within the installation of OEM image, now it went like: - Language Selection - Ubuntu Pro - Metrics Permission - User Account - Password - Store - Enter Desktop prompt It is missing location permission (if we don't disable that) and timezone selection, and it didn't enter desktop after that, and the account wasn't created as I couldn't login in the console. journal is attached ** Attachment added: "lp2067979-rebuild-1-log" https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2067979/+attachment/5786075/+files/lp2067979-rebuild-1-log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067979 Title: Language selection is skipped for new installations To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067979] Re: Language selection is skipped for new installations
> What do you mean? The language and welcome pages are different, they cannot be added one inside another. Sorry I don't mean the welcome page, I mean another gnome-initial-setup screen when user is greeted into the desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067979 Title: Language selection is skipped for new installations To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067979] Re: Language selection is skipped for new installations
Correct, we have most (if not all) language packs installed instead of having only the one chosen. However I also discovered that the language packs in the image are not installed as many as we thought to be, but this is out of scope of this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067979 Title: Language selection is skipped for new installations To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067979] Re: Language selection is skipped for new installations
That MR fixed the missing language page, but also added language page in the desktop welcome. I suppose that "ubuntu_page_table" is used when user enters the desktop for the first time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067979 Title: Language selection is skipped for new installations To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068000] Re: Cannot get timezone automatically recognized despite geoclue is available in the desktop
** Description changed: Cannot get timezone automatically recognized despite geoclue is available in the desktop. Reproduction steps: 1. Install stock Ubuntu desktop - 2. Change /etc/geoclue/geoclue.conf to use Google as source (I took API key from Arch Linux for testing purpose, see https://gitlab.archlinux.org/archlinux/packaging/packages/geoclue/-/commit/561b66e7e965f5a2e9f5b0597367243d43bbfa0f). This is in case of MLS shutdown. + 2. Change /etc/geoclue/geoclue.conf to use Google as source (I took API key from Arch Linux for testing purpose, but taking the key from Chromium snap seems to be fine: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/build/args.gn). This is in case of MLS shutdown. 3. Confirm the geolocation is working (by using /usr/libexec/geoclue-2.0/demos/where-am-i in geoclue-2-demo package) 4. Reboot and add gnome.initial-setup=1 in kernel command line (according to https://github.com/GNOME/gnome-initial-setup/blob/master/DEBUGGING.md) 5. Check whether there is internet connection in the beginning, or connect if not. 6. Turn on Location services 7. Wait and check that timezone is automatically selected Expected result: Timezone is automatically selected Actual result: Timezone is not automatically selected ** Also affects: oem-priority 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/2068000 Title: Cannot get timezone automatically recognized despite geoclue is available in the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2068000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067979] Re: Language selection is skipped for new installations
> Just for confirmation: In your OEM case, gnome-initial-setup currently does ask for account and password creation, right? Affirmative. There are realname/username and password/confirm pages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067979 Title: Language selection is skipped for new installations To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068000] Re: Cannot get timezone automatically recognized despite geoclue is available in the desktop
** Attachment added: "lp2068000-journal" https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2068000/+attachment/5785790/+files/lp2068000-journal ** Description changed: Cannot get timezone automatically recognized despite geoclue is available in the desktop. Reproduction steps: 1. Install stock Ubuntu desktop - 2. Change /etc/geoclue/geoclue.conf to use Google as source (I took API key from Arch Linux for testing purpose, see https://gitlab.archlinux.org/archlinux/packaging/packages/geoclue/-/commit/561b66e7e965f5a2e9f5b0597367243d43bbfa0f) + 2. Change /etc/geoclue/geoclue.conf to use Google as source (I took API key from Arch Linux for testing purpose, see https://gitlab.archlinux.org/archlinux/packaging/packages/geoclue/-/commit/561b66e7e965f5a2e9f5b0597367243d43bbfa0f). This is in case of MLS shutdown. 3. Confirm the geolocation is working (by using /usr/libexec/geoclue-2.0/demos/where-am-i in geoclue-2-demo package) 4. Reboot and add gnome.initial-setup=1 in kernel command line (according to https://github.com/GNOME/gnome-initial-setup/blob/master/DEBUGGING.md) 5. Check whether there is internet connection in the beginning, or connect if not. 6. Turn on Location services 7. Wait and check that timezone is automatically selected Expected result: Timezone is automatically selected Actual result: Timezone is not automatically selected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068000 Title: Cannot get timezone automatically recognized despite geoclue is available in the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2068000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068000] [NEW] Cannot get timezone automatically recognized despite geoclue is available in the desktop
Public bug reported: Cannot get timezone automatically recognized despite geoclue is available in the desktop. Reproduction steps: 1. Install stock Ubuntu desktop 2. Change /etc/geoclue/geoclue.conf to use Google as source (I took API key from Arch Linux for testing purpose, see https://gitlab.archlinux.org/archlinux/packaging/packages/geoclue/-/commit/561b66e7e965f5a2e9f5b0597367243d43bbfa0f). This is in case of MLS shutdown. 3. Confirm the geolocation is working (by using /usr/libexec/geoclue-2.0/demos/where-am-i in geoclue-2-demo package) 4. Reboot and add gnome.initial-setup=1 in kernel command line (according to https://github.com/GNOME/gnome-initial-setup/blob/master/DEBUGGING.md) 5. Check whether there is internet connection in the beginning, or connect if not. 6. Turn on Location services 7. Wait and check that timezone is automatically selected Expected result: Timezone is automatically selected Actual result: Timezone is not automatically selected ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Description changed: Cannot get timezone automatically recognized despite geoclue is available in the desktop. Reproduction steps: 1. Install stock Ubuntu desktop 2. Change /etc/geoclue/geoclue.conf to use Google as source (I took API key from Arch Linux for testing purpose, see https://gitlab.archlinux.org/archlinux/packaging/packages/geoclue/-/commit/561b66e7e965f5a2e9f5b0597367243d43bbfa0f) - 3. Confirm the geolocation is working (by using /usr/libexec/geoclue-2.0/demos/where-ami-i in geoclue-2-demo package) + 3. Confirm the geolocation is working (by using /usr/libexec/geoclue-2.0/demos/where-am-i in geoclue-2-demo package) 4. Reboot and add gnome.initial-setup=1 in kernel command line (according to https://github.com/GNOME/gnome-initial-setup/blob/master/DEBUGGING.md) 5. Check whether there is internet connection in the beginning, or connect if not. 6. Turn on Location services 7. Wait and check that timezone is automatically selected Expected result: Timezone is automatically selected Actual result: Timezone is not automatically selected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068000 Title: Cannot get timezone automatically recognized despite geoclue is available in the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2068000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067979] [NEW] Language selection is skipped for new installations
Public bug reported:
For OEM use case, we need language selection in the gnome-initial-setup
account creation. We created an autoinstall to install Ubuntu that does
not create a user, so that it boots into first boot screen when booting
into the system:
user-data:
users: {}
I found that there's a file in the Debian package:
https://salsa.debian.org/gnome-team/gnome-initial-setup/-/blob/ubuntu/latest/debian/vendor.conf
Which, this disables language selection for the first boot. I have an
assumption that because the language selection is done when installing
the system. This is not the case for OEM or for embedded system image.
** Affects: oem-priority
Importance: Undecided
Status: New
** Affects: gnome-initial-setup (Ubuntu)
Importance: Undecided
Status: New
** Also affects: oem-priority
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/2067979
Title:
Language selection is skipped for new installations
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2067979/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061073] Re: When setting up RAID installation, curtin failed to wipe imsm RAID block device
** Summary changed: - When setting up RAID installation, curtin tried to run partprobe on imsm container and failed + When setting up RAID installation, curtin failed to wipe imsm RAID block device ** Summary changed: - When setting up RAID installation, curtin failed to wipe imsm RAID block device + When setting up RAID installation, curtin failed on/after wiping RAID block device backed by IMSM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061073 Title: When setting up RAID installation, curtin failed on/after wiping RAID block device backed by IMSM To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2061073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061073] [NEW] When setting up RAID installation, curtin tried to run partprobe on imsm container and failed
Public bug reported:
The following error in curtin is captured when using ubuntu-desktop-
installer to install noble:
Running command ['partprobe', '/dev/md127'] with allowed return codes
[0, 1] (capture=False)
Warning: Error fsyncing/closing /dev/md127: Input/output error
Running command ['udevadm', 'settle'] with allowed return codes [0]
(capture=False)
TIMED udevadm_settle(): 0.002
devsync happy - path /dev/md127 now exists
return volume path /dev/md127
RAID validation: name=/dev/md126 raidlevel=raid1 devices=[] spares=[]
container=/dev/md127
Running command ['mdadm', '--query', '--detail', '--export',
'/dev/md126'] with allowed return codes [0] (capture=True)
Running command ['mdadm', '--query', '--detail', '--export',
'/dev/md126'] with allowed return codes [0] (capture=True)
RAID array OK: /dev/md126
Verified /dev/md126 raid composition, raid is OK
raid /dev/md126 already present, skipping create
Wiping raid device /dev/md126 mode=superblock-recursive
Running command ['wipefs', '--all', '--force', '/dev/md126'] with
allowed return codes [0] (capture=False)
/dev/md126: 8 bytes were erased at offset 0x0200 (gpt): 45 46 49 20
50 41 52 54
/dev/md126: 8 bytes were erased at offset 0x3b9dc7ffe00 (gpt): 45 46 49
20 50 41 52 54
/dev/md126: 2 bytes were erased at offset 0x01fe (PMBR): 55 aa
An error occured handling 'raid-md126': KeyError - 'partition'
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL:
configuring raid: raid-md126
TIMED BLOCK_META: 1.442
finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL:
curtin command block-meta
Traceback (most recent call last):
File
"/snap/ubuntu-desktop-bootstrap/113/lib/python3.10/site-packages/curtin/commands/main.py",
line 202, in main
ret = args.func(args)
File
"/snap/ubuntu-desktop-bootstrap/113/lib/python3.10/site-packages/curtin/log.py",
line 97, in wrapper
return log_time("TIMED %s: " % msg, func, *args, **kwargs)
File
"/snap/ubuntu-desktop-bootstrap/113/lib/python3.10/site-packages/curtin/log.py",
line 79, in log_time
return func(*args, **kwargs)
File
"/snap/ubuntu-desktop-bootstrap/113/lib/python3.10/site-packages/curtin/commands/block_meta.py",
line 127, in block_meta
return meta_custom(args)
File
"/snap/ubuntu-desktop-bootstrap/113/lib/python3.10/site-packages/curtin/commands/block_meta.py",
line 2278, in meta_custom
handler(command, storage_config_dict, context)
File
"/snap/ubuntu-desktop-bootstrap/113/lib/python3.10/site-packages/curtin/commands/block_meta.py",
line 1853, in raid_handler
block.wipe_volume(md_devname, mode=wipe_mode, exclusive=False)
File
"/snap/ubuntu-desktop-bootstrap/113/lib/python3.10/site-packages/curtin/block/__init__.py",
line 1345, in wipe_volume
quick_zero(path, partitions=True, exclusive=exclusive)
File
"/snap/ubuntu-desktop-bootstrap/113/lib/python3.10/site-packages/curtin/block/__init__.py",
line 1245, in quick_zero
ptdata = sysfs_partition_data(path)
File
"/snap/ubuntu-desktop-bootstrap/113/lib/python3.10/site-packages/curtin/block/__init__.py",
line 1014, in sysfs_partition_data
data['partition'],
KeyError: 'partition'
'partition'
All logs attached in the attachment.
** Affects: oem-priority
Importance: Undecided
Status: New
** Affects: curtin (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-priority
** Attachment added: "curtin-partprobe-imsm.tar.xz"
https://bugs.launchpad.net/bugs/2061073/+attachment/5764056/+files/curtin-partprobe-imsm.tar.xz
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061073
Title:
When setting up RAID installation, curtin tried to run partprobe on
imsm container and failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2061073/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2047796] Re: autoinstall: user-data validation fails for users or packages if they contain list of object
I retried these configurations in cloud-init 24.1.2-0ubuntu1 in noble and this seems to be resolved. Thanks, and sorry for the noise! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047796 Title: autoinstall: user-data validation fails for users or packages if they contain list of object To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2047796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056730] Re: noble-daily (20240310) cannot be installed offline
** Changed in: oem-priority Assignee: (unassigned) => Yao Wei (medicalwei) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056730 Title: noble-daily (20240310) cannot be installed offline To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2056730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056730] Re: noble-daily (20240310) cannot be installed offline
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056730 Title: noble-daily (20240310) cannot be installed offline To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2056730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931686] Re: [MIR] oem-somerville-delibird-meta
Attach oem-somerville-delibird-meta_20.04~ubuntu1.debdiff by oem-scripts 1.40. ** Summary changed: - [DRAFT][MIR] oem-somerville-delibird-meta + [MIR] oem-somerville-delibird-meta ** Description changed: - [DRAFT][Availability] + [Background] + + Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and + https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details. + + [Impact] + + 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive. + 2. The background and impact of the situation for this change, and it's impact. + + [Testing] + + 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware + 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware + 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly. + + [Regression Potential] + + Most potential regressions will live in the package set that will be + installed via dependency of this package, which live in OEM archive + (outside of Ubuntu) and control by OEM team. OEM team and other + corresponding team need take responsibility of those dependency + installed. + + [When switching kernel flavour] Check that the new kernel flavour works + on the target platform. + + [Availability] This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. The source code of the oem-somerville-delibird-meta for focal: git clone -b delibird-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta [Rationale] We want to improve the hardware support for some Dell platforms. [Security] No CVE/known security issue. [Quality assurance] I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms. - oem-somerville-delibird-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive. + oem-somerville-delibird-meta will be upgraded to 20.04ubuntu1 or the later version from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. + + https://ubuntu.com/certified/202108-29378 + https://ubuntu.com/certified/202108-29379 + https://ubuntu.com/certified/202108-9378 + https://ubuntu.com/certified/202110-29500 ** Changed in: oem-priority Status: Confirmed => Fix Committed ** Changed in: ubuntu Status: New => Confirmed ** Patch added: "oem-somerville-delibird-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1931686/+attachment/5593260/+files/oem-somerville-delibird-meta_20.04~ubuntu1.debdiff ** Tags removed: oem-scripts-0.98 ** Tags added: oem-needs-upload oem-scripts-1.40 ubuntu-certified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931686 Title: [MIR] oem-somerville-delibird-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970826] Re: Translations involved with "Wi-Fi" are not applied due to capitalization changes
Thanks. These are reported by our OEM customers, and (IMO more importantly) is visible during installation, so it has certain kind of priority here. I am trying to do the part in Traditional Chinese translations (unreviewed), and calling for translation should be quite helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970826 Title: Translations involved with "Wi-Fi" are not applied due to capitalization changes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1970826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970928] Re: Doesn't work with ibus (perhaps only in X11?)
Could you report which version of Ubuntu and kitty are you using? Thanks. ** Bug watch added: Debian Bug tracker #990316 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990316 ** Also affects: kitty (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990316 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970928 Title: Doesn't work with ibus (perhaps only in X11?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kitty/+bug/1970928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970826] [NEW] Translations involved with "Wi-Fi" are not applied due to capitalization changes
Public bug reported: Because there was a change that made the string "wi-fi" to "Wi-Fi" (changeset 2a8983ca), this made all translations involving with "wi-fi" unable to match the translation string. diff --git a/debian/ubiquity.templates b/debian/ubiquity.templates index c7ad49cb9c..4c4a8a840b 100644 --- a/debian/ubiquity.templates +++ b/debian/ubiquity.templates @@ -1058,7 +1058,7 @@ _Description: Wireless Template: ubiquity/text/wireless_section_label Type: text _Description: - Connecting this computer to a wi-fi network allows you to install + Connecting this computer to a Wi-Fi network allows you to install third-party software, download updates, automatically detect your timezone, and install full support for your language. @@ -1073,7 +1073,7 @@ _Description: Display password Template: ubiquity/text/no_wireless Type: text _Description: - I don't want to connect to a wi-fi network right now + I don't want to connect to a Wi-Fi network right now Template: ubiquity/text/use_wireless Type: text @@ -1628,7 +1628,7 @@ Template: ubiquity/text/efi_secureboot_info Type: text _Description: You have chosen to enable third-party software as part of your install, - which for this system includes hardware drivers for graphics and/or wi-fi + which for this system includes hardware drivers for graphics and/or Wi-Fi hardware. Your system also has UEFI Secure Boot enabled. UEFI Secure Boot needs to be configured to allow the use of these third-party drivers. . The translations of these strings are affected. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Summary changed: - Translation involved with "Wi-Fi" are not applied due to capitalization changes + Translations involved with "Wi-Fi" are not applied due to capitalization changes ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970826 Title: Translations involved with "Wi-Fi" are not applied due to capitalization changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1970826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system
** Attachment added: "lp1967067-bt-test.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967067/+attachment/5579243/+files/lp1967067-bt-test.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967067 Title: WCN6856 BT keep in OFF state after coldboot system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system
With linux-oem-5.14/5.14.0-1033.36, this issue is not reproducible within 20 cold reboots. A script is used to run rtcwake to cold boot 20 times and attach `bluetoothctl scan on` result to a log file. If the bluetooth device cannot be probed, the scan should output "No default controller available". There was no such error when using 5.14.0-1033.36 kernel. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967067 Title: WCN6856 BT keep in OFF state after coldboot system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Updating debdiff for focal to correct the bug number and use the upstream fix. ** Patch added: "iio-sensor-proxy_2.8-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5575435/+files/iio-sensor-proxy_2.8-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963628 Title: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system
Can confirm that 5.14.0-9031.34+exp.62 fixed this bug. cold-boot 50 times by script and BT can scan normally in all reboots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967067 Title: WCN6856 BT keep in OFF state after coldboot system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966356] Re: ibus input method not working
Could you give us steps to reproduce? It works for me after adding Others/Chewing in keyboard setup in the jammy VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963628 Title: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
I'd like to add another debdiff to jammy which resolves the issue from the patch upstream Upstream MR: https://gitlab.freedesktop.org/hadess/iio-sensor- proxy/-/merge_requests/355 ** Patch added: "iio-sensor-proxy_3.3-0ubuntu6.debdiff" https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5570270/+files/iio-sensor-proxy_3.3-0ubuntu6.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963628 Title: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921906] Re: [MIR] oem-somerville-hotpie-meta
The following tests has been done: 1. Use a clean install image, and enable -proposed repo, run `ubuntu-drivers list`, oem-somerville-hotpie-meta is shown 2. `ubuntu-drivers install` installs oem-somerville-hotpie-meta 20.04~ubuntu1, and then bootstrapped into oem-somerville-hotpie-meta 20.04ubuntu3 (from oem archive) along with its dependencies ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921906 Title: [MIR] oem-somerville-hotpie-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921905] Re: [MIR] oem-somerville-ellaria-meta
The following tests has been done: 1. Use a clean install image, and enable -proposed repo, run `ubuntu-drivers list`, oem-somerville-ellaria-meta is shown 2. `ubuntu-drivers install` installs oem-somerville-ellaria-meta 20.04~ubuntu1, and then bootstrapped into oem-somerville-ellaria-meta 20.04ubuntu3 (from oem archive) along with its dependencies ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921905 Title: [MIR] oem-somerville-ellaria-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921907] Re: [MIR] oem-somerville-matira-5-7-meta
The following tests has been done 1. ubuntu-drivers list-oem lists this package on the target platform 2. apt install oem-somerville-matira-5-7-meta can install the package, and can be upgraded into the one in the oem archive. 3. Installed oem-somerville-matira-5-7-meta through `ubuntu-drivers install`, and can be bootstrapped into the one in the oem archive. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921907 Title: [MIR] oem-somerville-matira-5-7-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920206] Re: [MIR] oem-somerville-zuma-p-meta
Attach oem-somerville-zuma-p-meta_20.04~ubuntu1.debdiff by oem-scripts 1.29. ** Patch added: "oem-somerville-zuma-p-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1920206/+attachment/5566384/+files/oem-somerville-zuma-p-meta_20.04~ubuntu1.debdiff ** Tags added: oem-needs-upload ubuntu-certified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920206 Title: [MIR] oem-somerville-zuma-p-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920206] Re: [MIR] oem-somerville-zuma-p-meta
** Tags removed: oem-scripts-0.8 ** Tags added: oem-scripts-1.29 ** Changed in: oem-priority Status: Confirmed => Fix Committed ** Changed in: 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/1920206 Title: [MIR] oem-somerville-zuma-p-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920194] Re: [MIR] oem-somerville-pearl-meta
Checked the following: 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly. Installation log attached ** Attachment added: "oem-somerville-pearl-meta_20.04~ubuntu1-mir-verification" https://bugs.launchpad.net/oem-priority/+bug/1920194/+attachment/5566382/+files/oem-somerville-pearl-meta_20.04~ubuntu1-mir-verification ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920194 Title: [MIR] oem-somerville-pearl-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
> isn't that the real issue? is that an hardware or firmware bug? could it be fixed rather than worked around in udev rules? It's their hardware limitation that vendors are unable to handle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963628 Title: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
This is debdiff for iio-sensor-proxy for jammy, which is also based on the same version in impish. ** Patch added: "iio-sensor-proxy_3.3-0ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5565596/+files/iio-sensor-proxy_3.3-0ubuntu4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963628 Title: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
This is debdiff for iio-sensor-proxy for focal ** Patch added: "iio-sensor-proxy_2.8-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+attachment/5565591/+files/iio-sensor-proxy_2.8-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963628 Title: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963628] [NEW] Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Public bug reported:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als", and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test whether
it's ambient light sensors are working properly without unexpected
brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
** Affects: iio-sensor-proxy (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1963628/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921907] Re: [MIR] oem-somerville-matira-5-7-meta
Attaching debdiff from 20.04~ubuntu1 to 20.04~ubuntu2 ** Patch added: "oem-somerville-matira-5-7-meta_20.04~ubuntu2.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1921907/+attachment/5565427/+files/oem-somerville-matira-5-7-meta_20.04~ubuntu2.debdiff ** Changed in: ubuntu Status: In Progress => Confirmed ** Changed in: oem-somerville-matira-5-7-meta (Ubuntu Focal) Status: Fix Committed => Confirmed ** Tags added: oem-needs-upload ** Tags removed: oem-done-upload -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921907 Title: [MIR] oem-somerville-matira-5-7-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support
With Linux kernel 5.14.0-1024-oem and linux-firmware 1.187.27 (in -proposed), it is confirmed that both WiFi and Bluetooth on WCN6856 A00 can be probed and used. Excerpt from dmesg: [6.188795] kernel: ath11k_pci :02:00.0: BAR 0: assigned [mem 0x7520-0x753f 64bit] [6.188815] kernel: ath11k_pci :02:00.0: enabling device ( -> 0002) [6.189145] kernel: ath11k_pci :02:00.0: wcn6855 hw2.0 [7.244333] kernel: ath11k_pci :02:00.0: chip_id 0x12 chip_family 0xb board_id 0xff soc_id 0x400c1211 [7.244347] kernel: ath11k_pci :02:00.0: fw_version 0x11080bbb fw_build_timestamp 2021-12-16 03:42 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HSP.1.1-03003-QCAHSPSWPL_V1_V2_SILICONZ_LITE-2 [7.552211] kernel: ath11k_pci :02:00.0 wlp2s0: renamed from wlan0 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954938 Title: Include the QCA WCN 6856 v2.1 support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921907] Re: [MIR] oem-somerville-matira-5-7-meta
** Tags removed: verification-failed verification-failed-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921907 Title: [MIR] oem-somerville-matira-5-7-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921907] Re: [MIR] oem-somerville-matira-5-7-meta
There are missing BIOS IDs in this package. We are attaching another with missing IDs added. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-failed verification-failed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921907 Title: [MIR] oem-somerville-matira-5-7-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925017] Re: [MIR] oem-stella.cmit-deoxys-meta
Confirmed that after enabling focal-proposed: 1. `ubuntu-drivers list-oem` lists the package `oem-stella.cmit-deoxys-meta` 2. `ubuntu-drivers install` installs the package `oem-stella.cmit-deoxys-meta` 3. Clean install stock Ubuntu then enable focal-proposed, update-manager offers installation to `oem-stella.cmit-deoxys-meta` and installs kernel from the OEM archive ** Attachment added: "log-oem-stella.cmit-deoxys-meta" https://bugs.launchpad.net/oem-priority/+bug/1925017/+attachment/5553223/+files/log-oem-stella.cmit-deoxys-meta ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925017 Title: [MIR] oem-stella.cmit-deoxys-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1925017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
** Tags removed: verification-needed verification-needed-focal verification-needed-impish ** Tags added: verification-done verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Tested on SKU 0A36 (Latitude 7420) and is PASS for both focal and impish. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Tested on SKU 0B0B for both impish and focal. Both fixed. Waiting for results from other SKUs. The following logs are from impish: # before upgrade udev ubuntu@CANONICALID:~$ cat /sys/devices/virtual/dmi/id/product_sku 0B0B ubuntu@CANONICALID:~$ dpkg -l udev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--=== ii udev 248.3-1ubuntu8 amd64/dev/ and hotplug management daemon ubuntu@CANONICALID:~$ dbus-send --system --print-reply --dest=net.hadess.SensorProxy /net/hadess/SensorProxy org.freedesktop.DBus.Properties.Get string:net.hadess.SensorProxy string:HasAccelerometer method return time=1639566406.463914 sender=:1.8 -> destination=:1.77 serial=80 reply_serial=2 variant boolean true # note that when this boolean is true, the accelerometer for changing screen orientation is enabled # after adding impish-proposed then apt install udev ubuntu@CANONICALID:~$ dpkg -l udev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== ii udev 248.3-1ubuntu8.1 amd64/dev/ and hotplug management daemon ubuntu@CANONICALID:~$ dbus-send --system --print-reply --dest=net.hadess.SensorProxy /net/hadess/SensorProxy org.freedesktop.DBus.Properties.Get string:net.hadess.SensorProxy string:HasAccelerometer method return time=163952.416519 sender=:1.9 -> destination=:1.78 serial=15 reply_serial=2 variant boolean false # the accelerometer is disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling
Could you try updating the BIOS firmware, and see whether this issue is still reproducible? I cannot observe the issue with BIOS firmware version 1.13.0 with docking station DA310. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944409 Title: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1944409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925017] Re: [MIR] oem-stella.cmit-deoxys-meta
Attach oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff by oem-scripts 1.25. ** Changed in: oem-priority Status: In Progress => Fix Committed ** Changed in: ubuntu Status: New => Confirmed ** Patch removed: "oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1925017/+attachment/5546374/+files/oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff ** Patch added: "oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1925017/+attachment/5546431/+files/oem-stella.cmit-deoxys-meta_20.04~ubuntu1.debdiff ** Tags added: oem-needs-upload ubuntu-certified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925017 Title: [MIR] oem-stella.cmit-deoxys-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1925017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
> Could you please clarify this situation for Impish, or ideally provide a debdiff as you did for the other series? Thanks! After looking into linux-source in impish, I can determine that it should be safe removing the modalias names. The reply saying that it had regression was my mistake. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Attachment added: "lp1952823.webm" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+attachment/5544516/+files/lp1952823.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Description changed: [Summary] - The system screen turns on for a moment after entering suspend. + The screen turns on for a moment when laptop is entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Tags added: oem-priority originate-from-1952020 somerville ** Tags added: originate-from-1945730 ** Tags added: originate-from-1949668 ** Tags added: originate-from-1947975 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Description changed: [Summary] The system screen turns on for a moment after entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] - The system should not turn back on if the system is going to suspend. + The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] Re: Screen blinks when entering suspend
** Attachment added: "nvidia-bug-report.log.gz" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+attachment/5544481/+files/nvidia-bug-report.log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952823] [NEW] Screen blinks when entering suspend
Public bug reported: [Summary] The system screen turns on for a moment after entering suspend. This issue happens on Dell Latitude 5421. [Steps to reproduce] 1. Enter suspend via power menu 2. Observe the display (Note that `rtcwake` may not able to reproduce this issue. `systemctl suspend` may reproduce this.) [Expected result] The screen should not turn back on if the system is going to suspend. [Actual result] When "Suspend" is clicked, screen turns off, then turns back on for a moment, then turns off before laptop entering suspend. ** Affects: nvidia-graphics-drivers-470 (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/1952823 Title: Screen blinks when entering suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951861] Re: Fix non-working e1000e device after resume
** Tags added: originate-from-1947661 ** Tags added: originate-from-1947678 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951861 Title: Fix non-working e1000e device after resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
** Tags added: originate-from-1933628 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950042] Re: Let NVMe with HMB use native power control again
Verified pass on focal that the system can enter PC10 and SLP_S0. On 5.14.0-1007-oem: turbostat --quiet -S --show Pkg%pc2,Pkg%pc3,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m freeze -s 15 | tee s0ix-diag.txt rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "freeze" using /dev/rtc0 at Thu Nov 11 01:39:29 2021 16.659672 sec Pkg%pc2 Pkg%pc3 Pk%pc10 CPU%LPI SYS%LPI 1.5986.66 0.000.000.00 On 5.14.0-1008-oem (proposed): turbostat --quiet -S --show Pkg%pc2,Pkg%pc3,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m freeze -s 15 | tee s0ix-diag.txt rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "freeze" using /dev/rtc0 at Thu Nov 11 01:53:24 2021 16.661935 sec Pkg%pc2 Pkg%pc3 Pk%pc10 CPU%LPI SYS%LPI 0.821.9686.22 87.40 85.27 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950042 Title: Let NVMe with HMB use native power control again To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949652] [NEW] Improve performance by changing the block size to 8M
Public bug reported: This issue is found in usb-creator 0.3.11 in impish. I found that creating USB disks in GNOME Disks is 2x faster than Startup Disk Creator, and here's the comparison: Startup Disk Creator: 1:52 GNOME Disks: 0:37 With a Sandisk Extreme Pro USB drive (CZ880) and a 4.0G image After I changed the default block_size from 100 to 8388608 in USBCreator._builtin_dd function in the Python file /usr/share/usb- creator/usb-creator-helper, this can improve the writing speed and making it about 0:30 to write the same disk image. ** Affects: usb-creator (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/1949652 Title: Improve performance by changing the block size to 8M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1949652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Any updates to this SRU? What's the expected date to include this patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945186] Re: Update the hardware support for HP Z2 Mini G5 Workstation, SFF G5 Workstation, TWR G5 Workstation in oem-stella.cmit-ivysaur-meta
** Tags added: oem-needs-upload ** Changed in: oem-priority Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945186 Title: Update the hardware support for HP Z2 Mini G5 Workstation, SFF G5 Workstation, TWR G5 Workstation in oem-stella.cmit-ivysaur-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945186] Re: Update the hardware support for HP Z2 Mini G5 Workstation, SFF G5 Workstation, TWR G5 Workstation in oem-stella.cmit-ivysaur-meta
** Summary changed: - [DRAFT] Update the hardware support for HP Z2 Mini G5 Workstation, SFF G5 Workstation, TWR G5 Workstation in oem-stella.cmit-ivysaur-meta + Update the hardware support for HP Z2 Mini G5 Workstation, SFF G5 Workstation, TWR G5 Workstation in oem-stella.cmit-ivysaur-meta ** Description changed: - [DRAFT][Impact] + [Impact] * It should have no impact at all because these changes shall have been applied and verified in the corresponding OEM archive before this SRU process. [Test Plan] * Install Ubuntu 20.04.x LTS on HP Z2 Mini G5 Workstation, SFF G5 Workstation, TWR G5 Workstation and remove oem-stella.cmit-ivysaur-meta manually if any. * Enable focal-proposed and execute the update-manager. * The update-manager should show "Hardware support for HP Z2 Mini G5 Workstation, SFF G5 Workstation, TWR G5 Workstation". If not, please change "When there are security updates" and "When there are other updates" in the Updates of software-properties-gtk to "Display immediately", install the older firefox by `sudo apt install firefox=75.0+build3-0ubuntu1` and reboot the system to wait for the update-manager pop up automatically. * After it installed oem-stella.cmit-ivysaur-meta by update-manager and reboot the system, you should see the system booting from the linux- generic-hwe-20.04 kernel. [Where problems could occur] * oem-stella.cmit-ivysaur-meta is installed but it is not updated to the version in the corresponding OEM archive. * The update-manager didn't show "Hardware support for HP Z2 Mini G5 Workstation, SFF G5 Workstation, TWR G5 Workstation" at all. [Other Info] * You can see all oem-stella.cmit-ivysaur-meta versions on https://people.ubuntu.com/~fourdollars/oem-meta-packages/. * I have used ppa:oem-solutions-engineers/oem-projects-meta to verify it before this SRU process. ** Tags removed: oem-scripts-1.15 ** Tags added: oem-needs-upload oem-scripts-1.16 ** Changed in: oem-priority Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945186 Title: Update the hardware support for HP Z2 Mini G5 Workstation, SFF G5 Workstation, TWR G5 Workstation in oem-stella.cmit-ivysaur-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
** Changed in: oem-priority Status: In Progress => New ** Changed in: systemd (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models
New SRU bug has been opened at LP: #1943561 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938259 Title: Add ACCEL_LOCATION=base property for Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
** Changed in: systemd (Ubuntu) Status: New => In Progress ** Changed in: oem-priority 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/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models
** Changed in: oem-priority Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938259 Title: Add ACCEL_LOCATION=base property for Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
** Patch added: "debdiff for hirsute from 247.3-3ubuntu3.6" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943561/+attachment/5525169/+files/systemd_247.3-3ubuntu3.6-247.3-3ubuntu3.7.debdiff ** Tags added: oem-priority originate-from-1895110 somerville ** Tags added: originate-from-1942976 ** Tags added: originate-from-1943099 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
** Patch added: "debdiff for focal from 245.4-4ubuntu3.13" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943561/+attachment/5525168/+files/systemd_245.4-4ubuntu3.13-245.4-4ubuntu3.14.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models
** Description changed: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. + + This is the update to the previously rolled back SRU LP: #1938259 [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943561] [NEW] Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Public bug reported: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. [Impact] * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. * Screen should be correct side up in login screen and desktop. * Tilt the laptop and the screen should not be rotated. [Where problems could occur] * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: This hwdb update is to avoid unwanted screen rotation when tilting the laptop. [Impact] - * This fixes unwanted rotations on certain Dell clamshell laptop models + * This fixes unwanted rotations on certain Dell clamshell laptop models with accelerometer. [Test Plan] - * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. - * Screen should be correct side up in login screen and desktop. - * Tilt the laptop and the screen should not be rotated. + * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install this package and ensure the kernel is updated to the latest. + * Screen should be correct side up in login screen and desktop. + * Tilt the laptop and the screen should not be rotated. [Where problems could occur] - * This is to add parameters for certain models in hwdb, and does not + * This is to add parameters for certain models in hwdb, and does not affect any other part of systemd. - * This fix would only take effect with kernel 5.13 or the above patch - backported. - - * Only models with the same Dell SKU would be affected. + * Only models with the same Dell SKU would be affected. [scope] this is needed for all releases this is being added to upstream by https://github.com/systemd/systemd/pull/20314 and https://github.com/systemd/systemd/pull/20661 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943561 Title: Add ACCEL_LOCATION=base property for 6 Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930754] Re: e1000e extremly slow
** Tags added: originate-from-1942834 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930754] Re: e1000e extremly slow
** Tags added: fossa-edge-staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models
We found that Dell Latitude 7420 is not actually fixed, and may cause Impish to have regression due to the removal of the product name modalias. ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => In Progress ** Changed in: systemd (Ubuntu Hirsute) Status: Fix Committed => In Progress ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => In Progress ** Tags added: verification-failed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938259 Title: Add ACCEL_LOCATION=base property for Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models
** Tags added: verification-failed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938259 Title: Add ACCEL_LOCATION=base property for Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models
Is it possible to respin the SRU for now? I need to correct the sku number, that 0B0B isn't correct one. The correct one is 0A36. I will upstream the fix first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938259 Title: Add ACCEL_LOCATION=base property for Dell clamshell models To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940262] Re: The modalias in 470 is not compatible to 460
Splitting RTX A5000 from Dell to LP: #1942080 ** Tags removed: originate-from-1941823 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940262 Title: The modalias in 470 is not compatible to 460 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942080] [NEW] ubuntu-driver should suggest nvidia-driver-470 for RTX A5000
Public bug reported: Split from bug LP: #1940262 The following modalias of RTX A5000 (notably, for Dell OEM) is missing: pci:v10DEd2231sv1028sd147Ebc03sc00i00 This results in ubuntu-drivers not suggesting nvidia-driver-470. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1941823 somerville ** Tags added: oem-priority originate-from-1941823 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942080 Title: ubuntu-driver should suggest nvidia-driver-470 for RTX A5000 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940262] Re: The modalias in 470 is not compatible to 460
Reuploading the script ** Attachment removed: "nvidia_supported" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521045/+files/nvidia_supported ** Attachment added: "nvidia_supported" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521048/+files/nvidia_supported -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940262 Title: The modalias in 470 is not compatible to 460 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
