[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy, mantic and noble
** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - feat: Add support for FTP and FTP over TLS (#4834) - feature(schema): add networkv2 schema (#4892) - feat: Add new distro 'azurelinux' for Microsoft Azure Linux. (#4931) - feat: Use NetworkManager renderer by default in RHEL family - feat(ca_certs): Add AlmaLinux OS and CloudLinux OS support (#5264) - feat(sysconfig): Add DNS from interface config to resolv.conf (#5401) - feat(alpine): add support for Busybox adduser/addgroup (#5176) - feat(disk_setup): Add support for nvme devices (#5263) - fix: Make DataSourceOracle more resilient to early network issues (LP: #2056194) - bug(wait_for_url): when exceptions occur url is unset, use url_exc (LP: #2055077) - bug(vmware): initialize new DataSourceVMware attributes at unpickle (#5021) (LP: #2056439) - bug(maas): register the correct DatasourceMAASLocal in init-local (#5068) (LP: #2057763) - fix(net): klibc ipconfig PROTO compatibility (#5437) [Alexsander de Souza] (LP: #2065787) - fix(snapd): ubuntu do not snap refresh when snap absent (LP: #2064300) Downstream Packaging changes: - downstream ubuntu packaging will now pin a feature DEPRECATION_INFO_BOUNDARY to match the first version of cloud-init released on each series. This boundary gates whether cloud-init will raise only INFO level logs or DEPRECATED logs (which result in an exit 2 on cloud-init status) based on whether the defined deprecation_version defined for each key in json schema. - drop all debian/cpick-* patches now included due to pulling all commits from upstream - drop package dependency on netifaces - logrotate config added - enable WSL datasource for discovery - shuffle common logic for apport out of debian/apport-general-hook.py and into the main repo to get better test coverage. - drop now unnecessary d/p/do-not-block-user-login.patch because upstream systemd ordering now aligns with previous downstream unit ordering - - Focal-only: redact unsupported ConditionEnvironment config from hotplug units. systemd in focal doesn't support this key anyway which results in a warning log in journalctl. - - This allows stable releases to retain original behavior for keys which - are recently deprecated in a newer version of cloud-init. + - Focal-only: redact unsupported ConditionEnvironment config from hotplug units. systemd in focal doesn't support this key anyway which results in a warning log in journalctl. + NOTE: This config setting was a supplemental gate in systemd units to prevent the individual units from being loaded in boot target if the environment provides "KERNEL_CMDLINE=cloud-init=disabled" and was only provided as a short-circuit to ds-identify which also checks for KERNEL_CMDLINE in /proc/cmdline during systemd generator timeframe to disable loading cloud-init systemd units. + + + This allows stable releases to retain original behavior for keys which are recently deprecated in a newer version of cloud-init. The feature.DEPRECATION_INFO_BOUNDARY for each targeted series: - focal: 20.1 - jammy: 22.1 - noble: 24.1 See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results * Manual Test Results [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] - Given that this SRU packaging is touching systemd unit ordering we want an additional manual test performed to validate/assert that there is not a degradation to time to SSH and perceived boot time. This can likely be performed in KVM to aensure a clean boot scenario with and without cloud-init 24.2 installed in the base image. [ChangeLog] 24.2 - test: Fix no default user in test_status.py (#5478) - fix: correct deprecated_version=22.2 for users.sudo - test: Add jsonschema guard in test_cc_ubuntu_pro.py (#5479) - fix(test): Fix pycloudlib types in integration tests (#5350) - fix(test): Fix ip printing for non-lxd instances (#5350) - chore(mypy): Drop unused missing import exclusions (#5350) - type: Add stub types for network v1/v2 config (#5350) - chore: Auto-format network jsonschema in ci (#5350) - fix(tox): Update tox.ini (#5350) - chore(typing): Remove type ignores and casts (#5350) - refactor(typing):
[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy, mantic and noble
** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - feat: Add support for FTP and FTP over TLS (#4834) - feature(schema): add networkv2 schema (#4892) - feat: Add new distro 'azurelinux' for Microsoft Azure Linux. (#4931) - feat: Use NetworkManager renderer by default in RHEL family - feat(ca_certs): Add AlmaLinux OS and CloudLinux OS support (#5264) - feat(sysconfig): Add DNS from interface config to resolv.conf (#5401) - feat(alpine): add support for Busybox adduser/addgroup (#5176) - feat(disk_setup): Add support for nvme devices (#5263) - fix: Make DataSourceOracle more resilient to early network issues (LP: #2056194) - bug(wait_for_url): when exceptions occur url is unset, use url_exc (LP: #2055077) - bug(vmware): initialize new DataSourceVMware attributes at unpickle (#5021) (LP: #2056439) - bug(maas): register the correct DatasourceMAASLocal in init-local (#5068) (LP: #2057763) - fix(net): klibc ipconfig PROTO compatibility (#5437) [Alexsander de Souza] (LP: #2065787) - fix(snapd): ubuntu do not snap refresh when snap absent (LP: #2064300) Downstream Packaging changes: - downstream ubuntu packaging will now pin a feature DEPRECATION_INFO_BOUNDARY to match the first version of cloud-init released on each series. This boundary gates whether cloud-init will raise only INFO level logs or DEPRECATED logs (which result in an exit 2 on cloud-init status) based on whether the defined deprecation_version defined for each key in json schema. - drop all debian/cpick-* patches now included due to pulling all commits from upstream - - drop package dependency on netifaces + - drop package dependency on netifaces - logrotate config added - enable WSL datasource for discovery - shuffle common logic for apport out of debian/apport-general-hook.py and into the main repo to get better test coverage. - drop now unnecessary d/p/do-not-block-user-login.patch because upstream systemd ordering now aligns with previous downstream unit ordering + - Focal-only: redact unsupported ConditionEnvironment config from hotplug units. systemd in focal doesn't support this key anyway which results in a warning log in journalctl. This allows stable releases to retain original behavior for keys which are recently deprecated in a newer version of cloud-init. The feature.DEPRECATION_INFO_BOUNDARY for each targeted series: - focal: 20.1 - jammy: 22.1 - noble: 24.1 See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results * Manual Test Results [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] - Given that this SRU packaging is touching systemd unit ordering we want an additional manual test performed to validate/assert that there is not a degradation to time to SSH and perceived boot time. This can likely be performed in KVM to aensure a clean boot scenario with and without cloud-init 24.2 installed in the base image. [ChangeLog] 24.2 - test: Fix no default user in test_status.py (#5478) - fix: correct deprecated_version=22.2 for users.sudo - test: Add jsonschema guard in test_cc_ubuntu_pro.py (#5479) - fix(test): Fix pycloudlib types in integration tests (#5350) - fix(test): Fix ip printing for non-lxd instances (#5350) - chore(mypy): Drop unused missing import exclusions (#5350) - type: Add stub types for network v1/v2 config (#5350) - chore: Auto-format network jsonschema in ci (#5350) - fix(tox): Update tox.ini (#5350) - chore(typing): Remove type ignores and casts (#5350) - refactor(typing): Remove unused code paths (#5350) - fix(typing): Add / update type annotations (#5350) - fix(typing): Remove type annotation for unused variable (#5350) - fix(typing): Remove invalid type annotations (#5350) - ci(mypy): Set default follow_imports value (#5350) - test: Update integration tests to pass on focal (#5476) - tests: update ubuntu_pro test to account for info-level deprecations (#5475) - tests: update nocloud deprecation test for boundary version (#5474) - fix(rh_subscription): add string type to org (#5453) - tests: integration tests aware of features.DEPRECATION_INFO_BOUNDARY - tests: update keyserver PPA key fur curtin-dev
[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy, mantic and noble
** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - feat: Add support for FTP and FTP over TLS (#4834) - feature(schema): add networkv2 schema (#4892) - feat: Add new distro 'azurelinux' for Microsoft Azure Linux. (#4931) - feat: Use NetworkManager renderer by default in RHEL family - feat(ca_certs): Add AlmaLinux OS and CloudLinux OS support (#5264) - feat(sysconfig): Add DNS from interface config to resolv.conf (#5401) - feat(alpine): add support for Busybox adduser/addgroup (#5176) - feat(disk_setup): Add support for nvme devices (#5263) - fix: Make DataSourceOracle more resilient to early network issues (LP: #2056194) - bug(wait_for_url): when exceptions occur url is unset, use url_exc (LP: #2055077) - bug(vmware): initialize new DataSourceVMware attributes at unpickle (#5021) (LP: #2056439) - bug(maas): register the correct DatasourceMAASLocal in init-local (#5068) (LP: #2057763) - fix(net): klibc ipconfig PROTO compatibility (#5437) [Alexsander de Souza] (LP: #2065787) - fix(snapd): ubuntu do not snap refresh when snap absent (LP: #2064300) Downstream Packaging changes: - downstream ubuntu packaging will now pin a feature DEPRECATION_INFO_BOUNDARY to match the first version of cloud-init released on each series. This boundary gates whether cloud-init will raise only INFO level logs or DEPRECATED logs (which result in an exit 2 on cloud-init status) based on whether the defined deprecation_version defined for each key in json schema. - - drop package dependency on netifaces + - drop all debian/cpick-* patches now included due to pulling all commits from upstream + - drop package dependency on netifaces - logrotate config added - enable WSL datasource for discovery - shuffle common logic for apport out of debian/apport-general-hook.py and into the main repo to get better test coverage. - drop now unnecessary d/p/do-not-block-user-login.patch because upstream systemd ordering now aligns with previous downstream unit ordering This allows stable releases to retain original behavior for keys which are recently deprecated in a newer version of cloud-init. The feature.DEPRECATION_INFO_BOUNDARY for each targeted series: - focal: 20.1 - jammy: 22.1 - noble: 24.1 See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results * Manual Test Results [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] - Given that this SRU packaging is touching systemd unit ordering we want an additional manual test performed to validate/assert that there is not a degradation to time to SSH and perceived boot time. This can likely be performed in KVM to aensure a clean boot scenario with and without cloud-init 24.2 installed in the base image. - [ChangeLog] - 24.2 - test: Fix no default user in test_status.py (#5478) - fix: correct deprecated_version=22.2 for users.sudo - test: Add jsonschema guard in test_cc_ubuntu_pro.py (#5479) - fix(test): Fix pycloudlib types in integration tests (#5350) - fix(test): Fix ip printing for non-lxd instances (#5350) - chore(mypy): Drop unused missing import exclusions (#5350) - type: Add stub types for network v1/v2 config (#5350) - chore: Auto-format network jsonschema in ci (#5350) - fix(tox): Update tox.ini (#5350) - chore(typing): Remove type ignores and casts (#5350) - refactor(typing): Remove unused code paths (#5350) - fix(typing): Add / update type annotations (#5350) - fix(typing): Remove type annotation for unused variable (#5350) - fix(typing): Remove invalid type annotations (#5350) - ci(mypy): Set default follow_imports value (#5350) - test: Update integration tests to pass on focal (#5476) - tests: update ubuntu_pro test to account for info-level deprecations (#5475) - tests: update nocloud deprecation test for boundary version (#5474) - fix(rh_subscription): add string type to org (#5453) - tests: integration tests aware of features.DEPRECATION_INFO_BOUNDARY - tests: update keyserver PPA key fur curtin-dev (#5472) - test: Fix deprecation test failures (#5466) - chore: fix schema.py formatting (#5465) - fix: dont double-log deprecated INFOs (#5465) - fix(test): Mock
[Bug 2071762] Re: sru cloud-init (24.2 update) to focal, jammy, mantic and noble
Not targeting Mantic for release due to expected EOL 2024-07-11 not leaving enough time to SRU verify this release. ** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: -* : Create list with LP: # included> + - feat: Add support for FTP and FTP over TLS (#4834) + - feature(schema): add networkv2 schema (#4892) + - feat: Add new distro 'azurelinux' for Microsoft Azure Linux. (#4931) + - feat: Use NetworkManager renderer by default in RHEL family + - feat(ca_certs): Add AlmaLinux OS and CloudLinux OS support (#5264) + - feat(sysconfig): Add DNS from interface config to resolv.conf (#5401) + - feat(alpine): add support for Busybox adduser/addgroup (#5176) + - feat(disk_setup): Add support for nvme devices (#5263) + + Downstream Packaging changes: + - downstream ubuntu packaging will now pin a feature DEPRECATION_INFO_BOUNDARY to match the first version of cloud-init released on each series. This boundary gates whether cloud-init will raise only INFO level logs or DEPRECATED logs (which result in an exit 2 on cloud-init status) based on whether the defined deprecation_version defined for each key in json schema. + + - drop package dependency on netifaces + - logrotate config added + - enable WSL datasource for discovery + - shuffle common logic for apport out of debian/apport-general-hook.py and into the main repo to get better test coverage. + - drop now unnecessary d/p/do-not-block-user-login.patch because upstream systemd ordering now aligns with previous downstream unit ordering + + This allows stable releases to retain original behavior for keys which + are recently deprecated in a newer version of cloud-init. + + The feature.DEPRECATION_INFO_BOUNDARY for each targeted series: +- focal: 20.1 +- jammy: 22.1 +- noble: 24.1 + See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results * Manual Test Results [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] - + - Given that this SRU packaging is touching systemd unit ordering we want an additional manual test performed to validate/assert that there is not a degradation to time to SSH and perceived boot time. This can likely be performed in KVM to aensure a clean boot scenario with and without cloud-init 24.2 installed in the base image. + == End SRU Template == - + 24.2 + - test: Fix no default user in test_status.py (#5478) + - fix: correct deprecated_version=22.2 for users.sudo + - test: Add jsonschema guard in test_cc_ubuntu_pro.py (#5479) + - fix(test): Fix pycloudlib types in integration tests (#5350) + - fix(test): Fix ip printing for non-lxd instances (#5350) + - chore(mypy): Drop unused missing import exclusions (#5350) + - type: Add stub types for network v1/v2 config (#5350) + - chore: Auto-format network jsonschema in ci (#5350) + - fix(tox): Update tox.ini (#5350) + - chore(typing): Remove type ignores and casts (#5350) + - refactor(typing): Remove unused code paths (#5350) + - fix(typing): Add / update type annotations (#5350) + - fix(typing): Remove type annotation for unused variable (#5350) + - fix(typing): Remove invalid type annotations (#5350) + - ci(mypy): Set default follow_imports value (#5350) + - test: Update integration tests to pass on focal (#5476) + - tests: update ubuntu_pro test to account for info-level deprecations +(#5475) + - tests: update nocloud deprecation test for boundary version (#5474) + - fix(rh_subscription): add string type to org (#5453) + - tests: integration tests aware of features.DEPRECATION_INFO_BOUNDARY + - tests: update keyserver PPA key fur curtin-dev (#5472) + - test: Fix deprecation test failures (#5466) + - chore: fix schema.py formatting (#5465) + - fix: dont double-log deprecated INFOs (#5465) + - fix(test): Mock version boundary (#5464) + - fix(schema): Don't report changed keys as deprecated (#5464) + - test: fix unit test openstack vlan mac_address (#5367) + - fix: Ensure properties for bonded interfaces are properly translated +(#5367) [Curt Moore] + - fix(schema): permit deprecated hyphenated keys under users key (#5456) + - fix: Do not add the vlan_mac_address field into the VLAN object (#5365) +[Curt Moore] + - doc(refactor): Convert module docs to new system (#5427) [Sally] + - test: Add unit
[Bug 2071762] [NEW] sru cloud-init (24.2 update) to focal, jammy, mantic and noble
Public bug reported: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * : Create list with LP: # included> See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results * Manual Test Results [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Discussion] == End SRU Template == ** Affects: cloud-init (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/2071762 Title: sru cloud-init (24.2 update) to focal, jammy, mantic and noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2071762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071363] Re: netplan apply triggers udev add events for every network interface
** Summary changed: - netplan apply triggers udev add events for every network interfdace + netplan apply triggers udev add events for every network interface -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071363 Title: netplan apply triggers udev add events for every network interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2071363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069694] [NEW] "Flip event timeout on head 1" shutdown hang
Public bug reported: Ubuntu 24.04 LTS with 2 monitor setup, NVIDIA 4070TI graphics card using the 550 driver and Wayland. Shutting down after the end of a session the machine hung reporting a 'Flip event timeout on head 1' Let me know what additional logs would be useful for debugging this as I appreciate it's not very detailed. Photo of monitor screen attached. ** Affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "PXL_20240614_182059150.jpg" https://bugs.launchpad.net/bugs/2069694/+attachment/5790456/+files/PXL_20240614_182059150.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069694 Title: "Flip event timeout on head 1" shutdown hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2069694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069286] [NEW] "No proprietary drivers are in use" when using NVIDIA 550
Public bug reported: After apt installing nvidia-550 the driver does not get listed under 'Additional Drivers' and reports 'No proprietary drivers are in use' which is misleading. nvidia-smi confirms the correct driver is being used. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot showing discrepancy in messaging" https://bugs.launchpad.net/bugs/2069286/+attachment/5789169/+files/Screenshot%20from%202024-06-12%2015-53-00.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069286 Title: "No proprietary drivers are in use" when using NVIDIA 550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2069286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
Haven't had a crash yet since disabling the tiling-assistant extension. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068869] Re: Filepicker + screensharing do not function on NVIDIA with Walyand
** Description changed: On a Lenovo Legion T5 desktop with AMD CPU and NVIDIA graphics and two monitors connected, I cannot open the filepicker (for example when - trying to upload a new profile picture to Discourse, or upload crash - logs to this bug) or share screens (in Google Meet on Firefox). Nautilus - also does not open. + trying to upload a new profile picture to Discourse) or share screens + (in Google Meet on Firefox). Nautilus also does not open. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xdg-desktop-portal-gnome 46.0-1build1 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 08:35:40 2024 InstallationDate: Installed on 2024-06-04 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068869 Title: Filepicker + screensharing do not function on NVIDIA with Walyand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2068869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068869] Re: Filepicker + screensharing do not function on NVIDIA with Walyand
** Attachment added: "_usr_libexec_xdg-desktop-portal-gnome.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2068869/+attachment/5787828/+files/_usr_libexec_xdg-desktop-portal-gnome.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068869 Title: Filepicker + screensharing do not function on NVIDIA with Walyand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2068869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068869] Re: Filepicker + screensharing do not function on NVIDIA with Walyand
** Attachment added: "_usr_bin_nautilus.1000.crash" https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2068869/+attachment/5787829/+files/_usr_bin_nautilus.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068869 Title: Filepicker + screensharing do not function on NVIDIA with Walyand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2068869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068869] [NEW] Filepicker + screensharing do not function on NVIDIA with Walyand
Public bug reported: On a Lenovo Legion T5 desktop with AMD CPU and NVIDIA graphics and two monitors connected, I cannot open the filepicker (for example when trying to upload a new profile picture to Discourse, or upload crash logs to this bug) or share screens (in Google Meet on Firefox). Nautilus also does not open. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xdg-desktop-portal-gnome 46.0-1build1 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 08:35:40 2024 InstallationDate: Installed on 2024-06-04 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068869 Title: Filepicker + screensharing do not function on NVIDIA with Walyand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2068869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
Disabled now. I will give an update after some time whether the crashing stopped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066985] Re: EC2 multi-nic ENI rendering fails if ENI activator not used
** Description changed: [ Impact ] Cloud-init recently added policy-based routing for netplan-only systems on EC2. In order to gate the netplan-specific code, it checked to see in the netplan activator was being used. However, if the datasource is fetched in init-local timeframe (such as on EC2), it is possible to specify a different renderer without also changing the activator. This means the netplan-gating no longer works, even when rendering to a non- netplan system. The fix is to instead check if we're using the netplan renderer before rendering the netplan-specific code. [ Test Plan ] Launch an Ubuntu instance on EC2 having two NICs attached. Run "apt update; apt install ifupdown" In /etc/cloud/cloud.cfg, update the `renderers` line to start with `eni` rather than `netplan` `cloud-init clean --logs --reboot` Connect to instance Verify no networking related tracebacks exist in logs Verify /etc/network/interfaces.d/ contains valid networking information for both NICs. Run tests/integration_tests/modules/test_hotplug.py and tests/integration_tests/test_networking.py to ensure no regression to existing multinic rendering behavior. Specifically this test per series is known to assert proper behavior and show potential regressions for netplan-based environments - CLOUD_INIT_OS_IMAGE=jammy CLOUD_INIT_CLOUD_INIT_SRCE=ppa:cloud-init-dev/daily CLOUD_INIT_PLATFORM=ec2 .tox/integration-tests/bin/pytest tests/integration_tests/modules/test_hotplug.py::test_multi_nic_hotplug_vpc - + CLOUD_INIT_OS_IMAGE=jammy CLOUD_INIT_CLOUD_INIT_SOURCE= CLOUD_INIT_PLATFORM=ec2 tox -e integration-tests -- tests/integration_tests/modules/test_hotplug.py::test_multi_nic_hotplug_vpc [ Where problems could occur ] If the renderer is still somehow mis-detecting a netplan or non-netplan based system, we could still attempt to render netplan config where we shouldn't be, or instead skip rendering the config where we shouldn't be. + Problems cloud also occur in netplan-based images if cloud-init + incorrectly determines that netplan is not the configured renderer and + skips adding supplmental policy based routes with route-metrics when + rendering netplan config for secondary NIC route-metrics. + [ Other Info ] Upstream bug: https://github.com/canonical/cloud-init/issues/5318 Upstream fix: https://github.com/canonical/cloud-init/pull/5321 ** Description changed: [ Impact ] Cloud-init recently added policy-based routing for netplan-only systems on EC2. In order to gate the netplan-specific code, it checked to see in the netplan activator was being used. However, if the datasource is fetched in init-local timeframe (such as on EC2), it is possible to specify a different renderer without also changing the activator. This means the netplan-gating no longer works, even when rendering to a non- netplan system. The fix is to instead check if we're using the netplan renderer before rendering the netplan-specific code. [ Test Plan ] Launch an Ubuntu instance on EC2 having two NICs attached. Run "apt update; apt install ifupdown" In /etc/cloud/cloud.cfg, update the `renderers` line to start with `eni` rather than `netplan` `cloud-init clean --logs --reboot` Connect to instance Verify no networking related tracebacks exist in logs Verify /etc/network/interfaces.d/ contains valid networking information for both NICs. Run tests/integration_tests/modules/test_hotplug.py and tests/integration_tests/test_networking.py to ensure no regression to existing multinic rendering behavior. Specifically this test per series is known to assert proper behavior and show potential regressions for netplan-based environments CLOUD_INIT_OS_IMAGE=jammy CLOUD_INIT_CLOUD_INIT_SOURCE= CLOUD_INIT_PLATFORM=ec2 tox -e integration-tests -- tests/integration_tests/modules/test_hotplug.py::test_multi_nic_hotplug_vpc [ Where problems could occur ] - If the renderer is still somehow mis-detecting a netplan or non-netplan - based system, we could still attempt to render netplan config where we - shouldn't be, or instead skip rendering the config where we shouldn't - be. + On EC2 only, if the renderer is still somehow mis-detecting a netplan or + non-netplan based system, we could still attempt to render netplan + config where we shouldn't be, or instead skip rendering the config where + we shouldn't be. - Problems cloud also occur in netplan-based images if cloud-init - incorrectly determines that netplan is not the configured renderer and - skips adding supplmental policy based routes with route-metrics when + Problems cloud also occur on Ec2 only in netplan-based images if cloud- + init incorrectly determines that netplan is not the configured renderer + and skips adding supplmental policy based routes with route-metrics when rendering netplan config for secondary NIC route-metrics. [ Other
[Bug 2066985] Re: EC2 multi-nic ENI rendering fails if ENI activator not used
This bug was fixed in the package cloud-init - 24.2~4g5f40426f-0ubuntu1 --- cloud-init (24.2~4g5f40426f-0ubuntu1) oracular; urgency=medium * Upstream snapshot based on upstream/main at 5f40426f. - Bugs fixed in this snapshot: (LP: #2066985) The fix for this bug in the previous release was only a partial fix. -- James Falcon Wed, 05 Jun 2024 12:52:40 -0500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066985 Title: EC2 multi-nic ENI rendering fails if ENI activator not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066985] Re: EC2 multi-nic ENI rendering fails if ENI activator not used
** Description changed: [ Impact ] Cloud-init recently added policy-based routing for netplan-only systems on EC2. In order to gate the netplan-specific code, it checked to see in the netplan activator was being used. However, if the datasource is fetched in init-local timeframe (such as on EC2), it is possible to specify a different renderer without also changing the activator. This means the netplan-gating no longer works, even when rendering to a non- netplan system. The fix is to instead check if we're using the netplan renderer before rendering the netplan-specific code. [ Test Plan ] Launch an Ubuntu instance on EC2 having two NICs attached. Run "apt update; apt install ifupdown" In /etc/cloud/cloud.cfg, update the `renderers` line to start with `eni` rather than `netplan` `cloud-init clean --logs --reboot` Connect to instance Verify no networking related tracebacks exist in logs Verify /etc/network/interfaces.d/ contains valid networking information for both NICs. Run tests/integration_tests/modules/test_hotplug.py and tests/integration_tests/test_networking.py to ensure no regression to existing multinic rendering behavior. + Specifically this test per series is known to assert proper behavior and show potential regressions for netplan-based environments + CLOUD_INIT_OS_IMAGE=jammy CLOUD_INIT_CLOUD_INIT_SRCE=ppa:cloud-init-dev/daily CLOUD_INIT_PLATFORM=ec2 .tox/integration-tests/bin/pytest tests/integration_tests/modules/test_hotplug.py::test_multi_nic_hotplug_vpc + + [ Where problems could occur ] - If the renderer is still somehow misdetecting a netplan or non-netplan + If the renderer is still somehow mis-detecting a netplan or non-netplan based system, we could still attempt to render netplan config where we shouldn't be, or instead skip rendering the config where we shouldn't be. [ Other Info ] Upstream bug: https://github.com/canonical/cloud-init/issues/5318 Upstream fix: https://github.com/canonical/cloud-init/pull/5321 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066985 Title: EC2 multi-nic ENI rendering fails if ENI activator not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066985] Re: EC2 multi-nic ENI rendering fails if ENI activator not used
Setting this task back to new for oracular as the fix provided in https://github.com/canonical/cloud-init/pull/5321 ended up breaking policy-based routing rendering for the netplan-based renderers on multi- nic instance types on Ec2. Upstream fix https://github.com/canonical/cloud-init/pull/5361 resolves this network rendering issue for multi-nic environments which make use of policy-based routing. Upload 24.2~4... will resolve this issue fully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066985 Title: EC2 multi-nic ENI rendering fails if ENI activator not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
If you have a step-by-step, I'm happy to try and get the information you need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
Yes I can see a corresponding .upload and .uploaded file. Unique ID is: f8601c66-2247-11ef-8ba3-fa163ec8ca8c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
I have a crash report from the latest crash today and have run ubuntu- bug to upload it. It's not showing on errors.ubuntu.com yet, but maybe it takes some time? ``` ubuntu-bug /var/crash/_usr_bin_gnome-shell.8046.crash ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
I have these mutter package versions: ``` ii gir1.2-mutter-14:amd64 46.1-2ubuntu1 amd64GObject introspection data for Mutter ii libmutter-14-0:amd64 46.1-2ubuntu1 amd64window manager library from the Mutter window manager ii mutter-common 46.1-2ubuntu1 all shared files for the Mutter window manager ii mutter-common-bin 46.1-2ubuntu1 amd64shared programs for the Mutter window manager ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
``` Jun 04 08:55:59 ubu-n-c3c04f314633 gnome-shell[4176]: libmutter:ERROR:../src/core/window.c:5941:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Jun 04 08:55:59 ubu-n-c3c04f314633 gnome-shell[4176]: Bail out! libmutter:ERROR:../src/core/window.c:5941:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Jun 04 08:55:59 ubu-n-c3c04f314633 gnome-shell[4176]: GNOME Shell crashed with signal 6 ``` As far as I can tell, it's the same error. I'll report it as a new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
I just had this same crash again on 24.04 with the patched mutter packages installed. Although, I will say I haven't experienced the issue as frequently as before installing the patched versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062951] Re: Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04)
I think I'm having the same issue I am running TPM+FDE on Ubuntu 24.04. I tried to apply the workaround suggested with following command: snap set system system.kernel.dangerous-cmdline-append="i915.enable_dc=0 intel_idle.max_cstate=2" But I'm still seeing the same after a reboot. In my case, I have my laptop screen and external monitor in extend mode. The "flickering" is occurring only on the laptop screen (which is NOT set as the primary). As others have described, mouse position seems to be a trigger for this, but not always in the same position. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062951 Title: Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067660] [NEW] deprecate ubuntu_advantage config key from user-data in favor of ubuntu_pro
Public bug reported: In upstream cloud-init ubuntu_advantage user-data cloud-config key is deprecated in favor of ubuntu_pro to better align with current Ubuntu Pro product naming and to avoid confusion in howtos, tutorials or tooling when interacting with Ubuntu Pro offerings. In an effort to standardize product naming across all Ubuntu supported releases, we will target a backport of this key deprecation to Xenial and Bionic to ensure Ubuntu Pro's releases covered by Extended Security Maintenance will also align with active Ubuntu Long Term Support(LTS) and interim release configuration keys. This bug is an SRU process bug representing the intent to backport a limited scope of functionality related to the cc_ubuntu_advantage module for better Ubuntu Pro support ESM releases. No other functional changes are intended beyond logged messages, user- data schema and config-key deprecation. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067660 Title: deprecate ubuntu_advantage config key from user-data in favor of ubuntu_pro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2067660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 988696] Catch up
*** This bug is a duplicate of bug 958751 *** https://bugs.launchpad.net/bugs/958751 Hi. Hope you are well. Sorry to bother you. do you often shop on John Lewis or Amazon? Alan Smith -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988696 Title: Me TV. Program opens and then becomes completely unresponsive to mouse or keyboard . Cannot change channels or quit. I have to use xkill to close program. Program was working well until update to 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/me-tv/+bug/988696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066314] Re: Please update the agent to upstream tag 20240307.00
** Description changed: + === SRU === + Following on from previous similar package update requests @ LP: #2064580, LP: #2020762, LP: #1996735, LP: #1938553 and LP: #1911689 this bug is a request to update `gce-compute-image-packages` to the new upstream version `20240307.00` @ https://github.com/GoogleCloudPlatform/guest- configs/releases/tag/20240307.00 This package has an SRU exception @ https://wiki.ubuntu.com/StableReleaseUpdates#gce-compute-image-packages including an ageing exception detailed @ https://wiki.ubuntu.com/gce- compute-image-packages-Updates [Impact] This package is provided by Google for installation within guests that run on Google Compute Engine. It is part of a collection of tools and daemons, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating this package to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of this package is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Vendored Dependency] - There a no new vendor dependencies needed so far (in oracular) + There a no new vendor dependencies needed (in any of the in-life suites) [Where Problems Could Occur] There are many upstream changes in `20230808.00-0ubuntu2` vs. `20240307.00-0ubuntu1`; however between the guest-test-infra suite [0] (which is run for validation by CPC _and_ Google) and CPC's own internal test harness (CTF) there is confidence that most if not all "edge cases" and/or obvious regressions concerns can be dismissed before the new version lands in `-updates` [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates The updated package is not built for armhf and riscv64 due to upstream regressions, but the package is not used on those architectures anyways thus please release the SRU without the armhf and risc64 binaries. The package does not build for powerpc on Xenial, but this is also fine as it is not used on powerpc either. [0]: https://github.com/GoogleCloudPlatform/guest-test-infra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066314 Title: Please update the agent to upstream tag 20240307.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2066314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
I've finally had time to test this on a non TPM-FDE machine and can confirm that services like cups are now working after installing the systemd version from noble-proposed. Testing: - Install clean Ubuntu 24.04 (no TPM-FDE) - Install dracut & reboot - Check cups status (failing to start) - Install systemd 255.4-1ubuntu8.1 from noble-proposed - Run 'dracut --regenerate-all --force - Reboot After doing this, services like cups and rsyslog now are starting without issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066985] Re: EC2 multi-nic ENI rendering fails if ENI activator not used
** Summary changed: - Mutli-nic ENI rendering fails if ENI activator not used + EC2 multi-nic ENI rendering fails if ENI activator not used -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066985 Title: EC2 multi-nic ENI rendering fails if ENI activator not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066979] Re: EC2: cloud-init network fails in ipv6-only subnet with multi-NICs
** Summary changed: - cloud-init network fails in ipv6-only subnet with multi-NICs + EC2: cloud-init network fails in ipv6-only subnet with multi-NICs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066979 Title: EC2: cloud-init network fails in ipv6-only subnet with multi-NICs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876716] Re: Error transferring track: "could not open resource for writing" when copying tracks to library
I am currently having this problem ...again. It is with a single disk I am trying to extract. Ubuntu 22.04.2 LTS RhythmBox 3.4.4 There is no other instance of the files anywhere in the directories I am attempting to send the extraction. The file names are all within the legal characters (which I have had problems with in the past). I have 1.x TB of space on the drive. I can play the CD with RhythmBox, but it won't extract. I have been extracting files all morning till I hit this one CD. I will continue extracting files if the program will permit with 'other' CD's. Is this a problem if the CD has DRM protection on it? I don't think this CD does, but sometimes one never knows. And, if so, is there a way to find out? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876716 Title: Error transferring track: "could not open resource for writing" when copying tracks to library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1876716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
Hi Łukasz, Here is the testing I have performed. - Enabled noble-proposed - Installed latest systemd from noble-proposed (255.4-1ubuntu8.1) - removed all systemd drop-in files for cups - Rebooted the device After rebooting I monitored the cups.service but it still is failing to start. I can see the following in the systemd journal: ``` May 22 14:43:15 ubu-n-b5c04f594433 kernel: audit: type=1400 audit(1716385395.378:290): apparmor="DENIED" operation="sendmsg" class="file" profile="/usr/sbin/cupsd" name="/systemd/notify" pid=10265 comm="cupsd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066352] [NEW] Desktop session crashes randomly
Public bug reported: On a test laptop running Ubuntu 24.04, I am occasionally seeing my desktop session crash and return to the login screen. I haven't identified a pattern for these crashes yet but seems to occur randomly regardless of which app i have open or if I'm interacting with the system or it's idle. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5.1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 22 10:38:31 2024 DisplayManager: gdm3 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "This journalctl log contains logs for the most recent crash. Crash occurred at around 10:05AM" https://bugs.launchpad.net/bugs/2066352/+attachment/5781146/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066352 Title: Desktop session crashes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2066352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066314] Re: Please update the agent to upstream tag 20240307.00
** Description changed: Following on from previous similar package update requests @ LP: #2064580, LP: #2020762, LP: #1996735, LP: #1938553 and LP: #1911689 this bug is a request to update `gce-compute-image-packages` to the new upstream version `20240307.00` @ https://github.com/GoogleCloudPlatform/guest- configs/releases/tag/20240307.00 This package has an SRU exception @ https://wiki.ubuntu.com/StableReleaseUpdates#gce-compute-image-packages including an ageing exception detailed @ https://wiki.ubuntu.com/gce- compute-image-packages-Updates [Impact] This package is provided by Google for installation within guests that run on Google Compute Engine. It is part of a collection of tools and daemons, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating this package to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of this package is uploaded to -proposed, the following will be done: - * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project - * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. + * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project + * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Vendored Dependency] - There a no new vendor dependencies need (in oracular) + There a no new vendor dependencies needed so far (in oracular) [Where Problems Could Occur] There are many upstream changes in `20230808.00-0ubuntu2` vs. `20240307.00-0ubuntu1`; however between the guest-test-infra suite [0] (which is run for validation by CPC _and_ Google) and CPC's own internal test harness (CTF) there is confidence that most if not all "edge cases" and/or obvious regressions concerns can be dismissed before the new version lands in `-updates` [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates The updated package is not built for armhf and riscv64 due to upstream regressions, but the package is not used on those architectures anyways thus please release the SRU without the armhf and risc64 binaries. The package does not build for powerpc on Xenial, but this is also fine as it is not used on powerpc either. [0]: https://github.com/GoogleCloudPlatform/guest-test-infra ** Changed in: gce-compute-image-packages (Ubuntu) Assignee: (unassigned) => Chloé Smith (kajiya) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066314 Title: Please update the agent to upstream tag 20240307.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2066314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066314] Re: Please update the agent to upstream tag 20240307.00
** Merge proposal linked: https://code.launchpad.net/~kajiya/+git/gce-compute-image-packages/+merge/466197 ** Merge proposal linked: https://code.launchpad.net/~kajiya/+git/gce-compute-image-packages/+merge/466199 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066314 Title: Please update the agent to upstream tag 20240307.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2066314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066314] Re: Please update the agent to upstream tag 20240307.00
** Description changed: - . + Following on from previous similar package update requests @ LP: + #2064580, LP: #2020762, LP: #1996735, LP: #1938553 and LP: #1911689 this + bug is a request to update `gce-compute-image-packages` to the new + upstream version `20240307.00` @ + https://github.com/GoogleCloudPlatform/guest- + configs/releases/tag/20240307.00 + + This package has an SRU exception @ + https://wiki.ubuntu.com/StableReleaseUpdates#gce-compute-image-packages + including an ageing exception detailed @ https://wiki.ubuntu.com/gce- + compute-image-packages-Updates + + [Impact] + + This package is provided by Google for installation within guests that + run on Google Compute Engine. It is part of a collection of tools and + daemons, that ensure that the Ubuntu images published to GCE run + properly on their platform. + + Cloud platforms evolve at a rate that can't be handled in six-month + increments, and they will often develop features that they would like to + be available to customers who don't want to upgrade from earlier Ubuntu + releases. As such, updating this package to more recent upstream + releases is required within all Ubuntu releases, so they continue to + function properly in their environment. + + [Test Case] + + When a new version of this package is uploaded to -proposed, the + following will be done: + + * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project + * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. + + If all the testing indicates that the image containing the new package + is acceptable, verification will be considered to be done. + + [Vendored Dependency] + + There a no new vendor dependencies need (in oracular) + + [Where Problems Could Occur] + + There are many upstream changes in `20230808.00-0ubuntu2` vs. + `20240307.00-0ubuntu1`; however between the guest-test-infra suite [0] + (which is run for validation by CPC _and_ Google) and CPC's own internal + test harness (CTF) there is confidence that most if not all "edge cases" + and/or obvious regressions concerns can be dismissed before the new + version lands in `-updates` + + [Other Information] + + This bug is used for tracking of releasing the new upstream version for + all supported series, as per the approved policy mentioned in the + following MRE: + + https://wiki.ubuntu.com/gce-compute-image-packages-Updates + + The updated package is not built for armhf and riscv64 due to upstream + regressions, but the package is not used on those architectures anyways + thus please release the SRU without the armhf and risc64 binaries. + + The package does not build for powerpc on Xenial, but this is also fine + as it is not used on powerpc either. + + [0]: https://github.com/GoogleCloudPlatform/guest-test-infra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066314 Title: Please update the agent to upstream tag 20240307.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2066314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066314] [NEW] Please update the agent to upstream tag 20240307.00
Public bug reported: Following on from previous similar package update requests @ LP: #2064580, LP: #2020762, LP: #1996735, LP: #1938553 and LP: #1911689 this bug is a request to update `gce-compute-image-packages` to the new upstream version `20240307.00` @ https://github.com/GoogleCloudPlatform/guest- configs/releases/tag/20240307.00 This package has an SRU exception @ https://wiki.ubuntu.com/StableReleaseUpdates#gce-compute-image-packages including an ageing exception detailed @ https://wiki.ubuntu.com/gce- compute-image-packages-Updates [Impact] This package is provided by Google for installation within guests that run on Google Compute Engine. It is part of a collection of tools and daemons, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating this package to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of this package is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Vendored Dependency] There a no new vendor dependencies need (in oracular) [Where Problems Could Occur] There are many upstream changes in `20230808.00-0ubuntu2` vs. `20240307.00-0ubuntu1`; however between the guest-test-infra suite [0] (which is run for validation by CPC _and_ Google) and CPC's own internal test harness (CTF) there is confidence that most if not all "edge cases" and/or obvious regressions concerns can be dismissed before the new version lands in `-updates` [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates The updated package is not built for armhf and riscv64 due to upstream regressions, but the package is not used on those architectures anyways thus please release the SRU without the armhf and risc64 binaries. The package does not build for powerpc on Xenial, but this is also fine as it is not used on powerpc either. [0]: https://github.com/GoogleCloudPlatform/guest-test-infra ** Affects: gce-compute-image-packages (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/2066314 Title: Please update the agent to upstream tag 20240307.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2066314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066035] [NEW] KWM Switch causes logout
Public bug reported: I have a 2x1 KVM switch between my work laptop (win10) and my Ubuntu 24.04 (noble) desktop. When I switch from Ubuntu to the work laptop - whether I have locked the screen or not - the Ubuntu session logs me out. I had originally thought it was rebooting the desktop, but using the uptime command, I can see that the machine have been online since my last manual reboot (this morning - I have rebooted a number of times over the last few days to try to clear the issue). Everything worked fine when the desktop was on Ubuntu 23.10. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 17 11:56:54 2024 InstallationDate: Installed on 2024-04-13 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: meta-gnome3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066035 Title: KWM Switch causes logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/2066035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
This bug affects me on 24.04 noble too. It did not on 23.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721428 Title: Artful (17.10) Session logout after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065874] [NEW] Can't update firmware on TPM-backed FDE systems
Public bug reported: This was previously reported here: https://github.com/canonical/ubuntu-desktop-installer/issues/2371 But I think that bug report and those posted in other projects don't seem to be getting attention. With the new TPM-backed FDE storage layout for Ubuntu 24.04, it is seemingly impossible to perform firmware updates using fwupd. Attempting to upgrade the firmware with `fwupdmgr upgrade XX` gives the attached error message. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: fwupd 1.9.16-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 16 11:25:24 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/usr/local/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.fwupd.fwupd.conf: [inaccessible: [Errno 13] Permission denied: '/etc/fwupd/fwupd.conf'] ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "fwupd_error.txt" https://bugs.launchpad.net/bugs/2065874/+attachment/5778971/+files/fwupd_error.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065874 Title: Can't update firmware on TPM-backed FDE systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2065874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055728] Re: update-notifier notifies on unactionable "Pro" updates
This is a valid bug and the intended behaviour is as described by the reporter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055728 Title: update-notifier notifies on unactionable "Pro" updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2055728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2065644] Re: Right click Rename file or folder freeze
Hi Sebastien, it freezes at first i just logout then i actually open process to kill the process then i figure if i click on the location bar /home/Documents on the same window, it allows me to get back control but i have to tap a few times which is still annoying and this is just to regain back control of the ui i then went to settings touch-pad and disable the tap to click i now have to push every time to execute an event in any part of the ui but at least i don't run into that issue where it just freeze i install ubuntu on a macbook pro 2012 13' On 5/14/24 02:38, Sebastien Bacher wrote: > Thank you for your bug report.So is the issue just the tapping not > working as expected or is it really freezing, the description is a bit > confusing > > ** Changed in: nautilus (Ubuntu) > Importance: Undecided => Low > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065644 Title: Right click Rename file or folder freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065644] Re: Right click Rename file or folder freeze
It appears when you right click and the context menu appears, you can not tap on the Rename item, you need to do a hard click, meaning, if you have a system with touch-pad, like a laptop, and you are use to tapping and not clicking on the touch-pad, it is actually 2 different functions on the Ubuntu OS, or at least Ubuntu treats it that way since i was able to `click` on the context menu item Rename and make it work versus the first time when i was just tapping on the context item menu Rename...this really sucks since you are used to tapping everywhere on the ui but all of the sudden you start finding out that tapping does not work everywhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065644 Title: Right click Rename file or folder freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065644] [NEW] Right click Rename file or folder freeze
Public bug reported: Ubuntu 24.04 All Updates as of 2024-05-13 Open Files Right click on a file Select Rename from context menu Does not popup or allow to rename file Same with folder F2 key does works though but I want to use Right click if that is an option ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 13 22:48:45 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2024-05-12 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065644 Title: Right click Rename file or folder freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065567] [NEW] Vague error message for invalid sources
Public bug reported: This is more like a quality-of-life issue. If you have a source configured which is broken (gpg key error, no release information, etc.), update-manager will provide a vague error message that doesn't really help users identify the problem. See attached screenshot. Ideally, update-manager should at least display which sources are causing the error to help track down the problem. The error message also isn't clear that this doesn't prevent you from updating the system. If you click OK you can still upgrade packages from the remaining correctly configured sources. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: update-manager 1:24.04.6 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Aptdaemon: Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 13 09:32:10 2024 DpkgTerminalLog.txt: Error: [Errno 13] Permission denied: '/var/log/apt/term.log' GsettingsChanges: b'com.ubuntu.update-manager' b'launch-count' b'5' b'com.ubuntu.update-manager' b'launch-time' b'int64 1715589118' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-width' b'593' PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Screenshot from 2024-05-13 09-30-54.png" https://bugs.launchpad.net/bugs/2065567/+attachment/5777831/+files/Screenshot%20from%202024-05-13%2009-30-54.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065567 Title: Vague error message for invalid sources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2065567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `upgrade_packages: true` user-data
sru validation complete noble csmith@downtown:~$ bash ./sru-2064132.sh + cat + cat + for SERIES in "noble" + echo '-- SRU verification: noble' -- SRU verification: noble + name=test-no-snap-noble + lxc launch ubuntu-daily:noble test-no-snap-noble Creating test-no-snap-noble Starting test-no-snap-noble + sleep 6 + lxc exec test-no-snap-noble -- cloud-init status --wait . status: done + lxc exec test-no-snap-noble -- apt-get update Hit:1 http://archive.ubuntu.com/ubuntu noble InRelease Get:2 http://security.ubuntu.com/ubuntu noble-security InRelease [89.7 kB] Get:3 http://archive.ubuntu.com/ubuntu noble-updates InRelease [89.7 kB] Get:4 http://archive.ubuntu.com/ubuntu noble-backports InRelease [89.7 kB] Get:5 http://security.ubuntu.com/ubuntu noble-security/main amd64 Packages [26.7 kB] Get:6 http://security.ubuntu.com/ubuntu noble-security/main Translation-en [8124 B] Get:7 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Packages [10.6 kB] Get:8 http://security.ubuntu.com/ubuntu noble-security/universe Translation-en [4596 B] Get:9 http://security.ubuntu.com/ubuntu noble-security/universe amd64 c-n-f Metadata [112 B] Get:10 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64 c-n-f Metadata [116 B] Get:11 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages [15.0 MB] Get:12 http://archive.ubuntu.com/ubuntu noble/universe Translation-en [5982 kB] Get:13 http://archive.ubuntu.com/ubuntu noble/universe amd64 Components [3871 kB] Get:14 http://archive.ubuntu.com/ubuntu noble/universe amd64 c-n-f Metadata [301 kB] Get:15 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 Packages [269 kB] Get:16 http://archive.ubuntu.com/ubuntu noble/multiverse Translation-en [118 kB] Get:17 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 Components [35.0 kB] Get:18 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 c-n-f Metadata [8328 B] Get:19 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages [28.4 kB] Get:20 http://archive.ubuntu.com/ubuntu noble-updates/main Translation-en [8996 B] Get:21 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages [17.6 kB] Get:22 http://archive.ubuntu.com/ubuntu noble-updates/universe Translation-en [6096 B] Get:23 http://archive.ubuntu.com/ubuntu noble-updates/universe amd64 c-n-f Metadata [112 B] Get:24 http://archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 c-n-f Metadata [116 B] Get:25 http://archive.ubuntu.com/ubuntu noble-backports/main amd64 c-n-f Metadata [112 B] Get:26 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 Packages [3936 B] Get:27 http://archive.ubuntu.com/ubuntu noble-backports/universe Translation-en [1392 B] Get:28 http://archive.ubuntu.com/ubuntu noble-backports/universe amd64 c-n-f Metadata [116 B] Get:29 http://archive.ubuntu.com/ubuntu noble-backports/restricted amd64 c-n-f Metadata [116 B] Get:30 http://archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 c-n-f Metadata [116 B] Fetched 26.0 MB in 5s (5274 kB/s) Reading package lists... Done + lxc exec test-no-snap-noble -- apt-get install cloud-init -y Reading package lists... Done Building dependency tree... Done Reading state information... Done cloud-init is already the newest version (24.1.3-0ubuntu3). 0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded. + lxc exec test-no-snap-noble -- cloud-init --version /usr/bin/cloud-init 24.1.3-0ubuntu3 + '[' noble = focal ']' ++ cat pkg-update.yaml + lxc config set test-no-snap-noble 'cloud-init.user-data=#cloud-config package_upgrade: true' + lxc exec test-no-snap-noble -- cloud-init clean --logs --reboot + sleep 6 + lxc exec test-no-snap-noble -- cloud-init status --wait .. status: done + lxc exec test-no-snap-noble -- egrep 'snap.*refresh' /var/log/cloud-init.log 2024-05-10 20:31:07,434 - subp.py[DEBUG]: Running command ['snap', 'refresh'] with allowed return codes [0] (shell=False, capture=True) 2024-05-10 20:31:07,676 - subp.py[DEBUG]: command ['snap', 'refresh'] took 0.2s to run + echo 'SUCCESS: found snap refresh on system with snapd' SUCCESS: found snap refresh on system with snapd + lxc exec test-no-snap-noble -- apt-get remove snapd -y Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: squashfs-tools Use 'apt autoremove' to remove it. The following packages will be REMOVED: snapd 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 107 MB disk space will be freed. (Reading database ... 34376 files and directories currently installed.) Removing snapd (2.62+24.04build1) ... Stopping 'snapd.service', but its triggering units are still active: snapd.socket Processing triggers for dbus (1.14.10-4ubuntu4) ... Processing triggers for
[Bug 2064132] Re: images without snapd installed error on `upgrade_packages: true` user-data
=== SRU verification complete jammy === csmith@downtown:~$ bash ./sru-2064132.sh + cat + cat + for SERIES in "jammy" + echo '-- SRU verification: jammy' -- SRU verification: jammy + name=test-no-snap-jammy + lxc launch ubuntu-daily:jammy test-no-snap-jammy Creating test-no-snap-jammy Starting test-no-snap-jammy + sleep 6 + lxc exec test-no-snap-jammy -- cloud-init status --wait .. status: done + lxc exec test-no-snap-jammy -- apt-get update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB] Get:5 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1427 kB] Get:6 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB] Get:7 http://security.ubuntu.com/ubuntu jammy-security/main Translation-en [247 kB] Get:8 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [1807 kB] Get:9 http://security.ubuntu.com/ubuntu jammy-security/restricted Translation-en [307 kB] Get:10 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [852 kB] Get:11 http://security.ubuntu.com/ubuntu jammy-security/universe Translation-en [164 kB] Get:12 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 c-n-f Metadata [16.8 kB] Get:13 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [37.2 kB] Get:14 http://security.ubuntu.com/ubuntu jammy-security/multiverse Translation-en [7588 B] Get:15 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 c-n-f Metadata [260 B] Get:16 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5652 kB] Get:17 http://archive.ubuntu.com/ubuntu jammy/universe amd64 c-n-f Metadata [286 kB] Get:18 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB] Get:19 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB] Get:20 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 c-n-f Metadata [8372 B] Get:21 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1638 kB] Get:22 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [307 kB] Get:23 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [1864 kB] Get:24 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [316 kB] Get:25 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1074 kB] Get:26 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [245 kB] Get:27 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f Metadata [22.1 kB] Get:28 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [42.7 kB] Get:29 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en [10.4 kB] Get:30 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 c-n-f Metadata [472 B] Get:31 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [67.1 kB] Get:32 http://archive.ubuntu.com/ubuntu jammy-backports/main Translation-en [11.0 kB] Get:33 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 c-n-f Metadata [388 B] Get:34 http://archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 c-n-f Metadata [116 B] Get:35 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [27.2 kB] Get:36 http://archive.ubuntu.com/ubuntu jammy-backports/universe Translation-en [16.2 kB] Get:37 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 c-n-f Metadata [644 B] Get:38 http://archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 c-n-f Metadata [116 B] Fetched 31.2 MB in 4s (8043 kB/s) Reading package lists... Done + lxc exec test-no-snap-jammy -- apt-get install cloud-init -y Reading package lists... Done Building dependency tree... Done Reading state information... Done cloud-init is already the newest version (24.1.3-0ubuntu1~22.04.1). 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. + lxc exec test-no-snap-jammy -- cloud-init --version /usr/bin/cloud-init 24.1.3-0ubuntu1~22.04.1 + '[' jammy = focal ']' ++ cat pkg-update.yaml + lxc config set test-no-snap-jammy 'cloud-init.user-data=#cloud-config package_upgrade: true' + lxc exec test-no-snap-jammy -- cloud-init clean --logs --reboot + sleep 6 + lxc exec test-no-snap-jammy -- cloud-init status --wait ... status: done + lxc exec test-no-snap-jammy -- egrep 'snap.*refresh' /var/log/cloud-init.log 2024-05-10 18:41:42,962 - subp.py[DEBUG]: Running command ['snap', 'refresh'] with allowed return codes [0] (shell=False, capture=True) 2024-05-10 18:41:44,046 -
[Bug 2064132] Re: images without snapd installed error on `upgrade_packages: true` user-data
focal SRU verification complete === echo '-- SRU verification: focal' -- SRU verification: focal + name=test-no-snap-focal + lxc launch ubuntu-daily:focal test-no-snap-focal Creating test-no-snap-focal Starting test-no-snap-focal + sleep 6 + lxc exec test-no-snap-focal -- cloud-init status --wait status: done + lxc exec test-no-snap-focal -- apt-get update Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB] Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Get:4 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [2919 kB] Get:5 http://security.ubuntu.com/ubuntu focal-security/main Translation-en [438 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB] Get:7 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [2799 kB] Get:8 http://security.ubuntu.com/ubuntu focal-security/restricted Translation-en [391 kB] Get:9 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [959 kB] Get:10 http://security.ubuntu.com/ubuntu focal-security/universe Translation-en [202 kB] Get:11 http://security.ubuntu.com/ubuntu focal-security/universe amd64 c-n-f Metadata [19.2 kB] Get:12 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [24.0 kB] Get:13 http://security.ubuntu.com/ubuntu focal-security/multiverse Translation-en [5904 B] Get:14 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 c-n-f Metadata [548 B] Get:15 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8628 kB] Get:16 http://archive.ubuntu.com/ubuntu focal/universe Translation-en [5124 kB] Get:17 http://archive.ubuntu.com/ubuntu focal/universe amd64 c-n-f Metadata [265 kB] Get:18 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [144 kB] Get:19 http://archive.ubuntu.com/ubuntu focal/multiverse Translation-en [104 kB] Get:20 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 c-n-f Metadata [9136 B] Get:21 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [3296 kB] Get:22 http://archive.ubuntu.com/ubuntu focal-updates/main Translation-en [521 kB] Get:23 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [2916 kB] Get:24 http://archive.ubuntu.com/ubuntu focal-updates/restricted Translation-en [407 kB] Get:25 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1185 kB] Get:26 http://archive.ubuntu.com/ubuntu focal-updates/universe Translation-en [284 kB] Get:27 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 c-n-f Metadata [25.7 kB] Get:28 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages [26.2 kB] Get:29 http://archive.ubuntu.com/ubuntu focal-updates/multiverse Translation-en [7880 B] Get:30 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 c-n-f Metadata [620 B] Get:31 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages [45.7 kB] Get:32 http://archive.ubuntu.com/ubuntu focal-backports/main Translation-en [16.3 kB] Get:33 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 c-n-f Metadata [1420 B] Get:34
[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand
# verification complete mantic #
csmith@midtown:~$ lxc launch ubuntu-daily:mantic test-m
Creating test-m
Starting test-m file push myfile.yaml
csmith@midtown:~$ lxc file push myfile.yaml test-m/
csmith@midtown:~$ lxc file push setup_proposed.sh test-m/
csmith@midtown:~$ lxc exec test-m bash
root@test-m:~# hostname # confirm test-jammy from standard meta-data
test-m
root@test-m:~# cloud-init clean # allow running init stage again
root@test-m:~# # confirm usage failure
root@test-m:~# cloud-init -f /myfile.yaml init
usage: /usr/bin/cloud-init [-h] [--version] [--debug] [--force]
{init,modules,single,query,features,analyze,devel,collect-logs,clean,status,schema}
...
/usr/bin/cloud-init: error: argument subcommand: invalid choice: '/myfile.yaml'
(choose from 'init', 'modules', 'single', 'query', 'features', 'analyze',
'devel', 'collect-logs', 'clean', 'status', 'schema')
root@test-m:~# # upgrade cloud-init to confirm --file support
root@test-m:~# sh /setup_proposed.sh
deb http://archive.ubuntu.com/ubuntu mantic-proposed main
Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
Get:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease [109 kB]
Get:3 http://security.ubuntu.com/ubuntu mantic-security InRelease [109 kB]
Get:4 http://archive.ubuntu.com/ubuntu mantic-backports InRelease [90.8 kB]
Get:5 http://archive.ubuntu.com/ubuntu mantic-proposed InRelease [256 kB]
Get:6 http://archive.ubuntu.com/ubuntu mantic/universe amd64 Packages [15.2 MB]
Get:7 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages
[355 kB]
Get:8 http://archive.ubuntu.com/ubuntu mantic/universe Translation-en [5951 kB]
Get:9 http://archive.ubuntu.com/ubuntu mantic/universe amd64 DEP-11 Metadata
[3793 kB]
Get:10 http://security.ubuntu.com/ubuntu mantic-security/main Translation-en
[91.5 kB]
Get:11 http://security.ubuntu.com/ubuntu mantic-security/universe amd64
Packages [274 kB]
Get:12 http://archive.ubuntu.com/ubuntu mantic/universe amd64 c-n-f Metadata
[303 kB]
Get:13 http://archive.ubuntu.com/ubuntu mantic/multiverse amd64 Packages [239
kB]
Get:14 http://archive.ubuntu.com/ubuntu mantic/multiverse Translation-en [113
kB]
Get:15 http://archive.ubuntu.com/ubuntu mantic/multiverse amd64 DEP-11 Metadata
[31.6 kB]
Get:16 http://archive.ubuntu.com/ubuntu mantic/multiverse amd64 c-n-f Metadata
[8356 B]
Get:17 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages [415
kB]
Get:18 http://archive.ubuntu.com/ubuntu mantic-updates/main Translation-en [110
kB]
Get:19 http://archive.ubuntu.com/ubuntu mantic-updates/universe amd64 Packages
[360 kB]
Get:20 http://archive.ubuntu.com/ubuntu mantic-updates/universe Translation-en
[138 kB]
Get:21 http://archive.ubuntu.com/ubuntu mantic-updates/universe amd64 DEP-11
Metadata [3864 B]
Get:22 http://archive.ubuntu.com/ubuntu mantic-updates/universe amd64 c-n-f
Metadata [820 B]
Get:23 http://archive.ubuntu.com/ubuntu mantic-updates/multiverse amd64
Packages [8568 B]
Get:24 http://archive.ubuntu.com/ubuntu mantic-updates/multiverse
Translation-en [2824 B]
Get:25 http://archive.ubuntu.com/ubuntu mantic-updates/multiverse amd64 c-n-f
Metadata [232 B]
Get:26 http://archive.ubuntu.com/ubuntu mantic-backports/main amd64 c-n-f
Metadata [112 B]
Get:27 http://archive.ubuntu.com/ubuntu mantic-backports/restricted amd64 c-n-f
Metadata [116 B]
Get:28 http://archive.ubuntu.com/ubuntu mantic-backports/universe amd64
Packages [3940 B]
Get:29 http://archive.ubuntu.com/ubuntu mantic-backports/universe
Translation-en [1392 B]
Get:30 http://archive.ubuntu.com/ubuntu mantic-backports/universe amd64 c-n-f
Metadata [116 B]
Get:31 http://security.ubuntu.com/ubuntu mantic-security/universe
Translation-en [115 kB]
Get:32 http://archive.ubuntu.com/ubuntu mantic-backports/multiverse amd64 c-n-f
Metadata [116 B]
Get:33 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages
[84.9 kB]
Get:34 http://archive.ubuntu.com/ubuntu mantic-proposed/main Translation-en
[23.9 kB]
Get:35 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 DEP-11
Metadata [7592 B]
Get:36 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 c-n-f
Metadata [1028 B]
Get:37 http://security.ubuntu.com/ubuntu mantic-security/universe amd64 DEP-11
Metadata [3860 B]
Get:38 http://security.ubuntu.com/ubuntu mantic-security/universe amd64 c-n-f
Metadata [788 B]
Get:39 http://security.ubuntu.com/ubuntu mantic-security/multiverse amd64
Packages [5588 B]
Get:40 http://security.ubuntu.com/ubuntu mantic-security/multiverse
Translation-en [1732 B]
Get:41 http://security.ubuntu.com/ubuntu mantic-security/multiverse amd64 c-n-f
Metadata [232 B]
Fetched 28.2 MB in 3s (8593 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
cloud-init
1 upgraded, 0 newly installed, 0 to remove and 13 not upgraded.
Need to get 598 kB of archives.
After this
[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand
test verification complete jammy
csmith@midtown:~$ lxc launch ubuntu-daily:jammy test-jammy
Creating test-jammy
Starting test-jammy
csmith@midtown:~$ lxc file push myfile.yaml test-jammy/
csmith@midtown:~$ lxc file push setup_proposed.sh test-jammy/
csmith@midtown:~$
csmith@midtown:~$ lxc exec test-jammy bash
root@test-jammy:~# hostname # confirm test-jammy from standard meta-data
test-jammy
root@test-jammy:~# cloud-init clean # allow running init stage again
root@test-jammy:~# # confirm usage failure
root@test-jammy:~# cloud-init -f /myfile.yaml init
usage: /usr/bin/cloud-init [-h] [--version] [--debug] [--force]
{init,modules,single,query,features,analyze,devel,collect-logs,clean,status,schema}
...
/usr/bin/cloud-init: error: argument subcommand: invalid choice: '/myfile.yaml'
(choose from 'init', 'modules', 'single', 'query', 'features', 'analyze',
'devel', 'collect-logs', 'clean', 'status', 'schema')
root@test-jammy:~# # upgrade cloud-init to confirm --file support
root@test-jammy:~# sh /setup_proposed.sh
deb http://archive.ubuntu.com/ubuntu jammy-proposed main
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
Get:5 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
[1427 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy-proposed InRelease [270 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB]
Get:8 http://security.ubuntu.com/ubuntu jammy-security/main Translation-en [247
kB]
Get:9 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64
Packages [1807 kB]
Get:10 http://security.ubuntu.com/ubuntu jammy-security/restricted
Translation-en [307 kB]
Get:11 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages
[852 kB]
Get:12 http://security.ubuntu.com/ubuntu jammy-security/universe Translation-en
[164 kB]
Get:13 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 c-n-f
Metadata [16.8 kB]
Get:14 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64
Packages [37.2 kB]
Get:15 http://security.ubuntu.com/ubuntu jammy-security/multiverse
Translation-en [7588 B]
Get:16 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 c-n-f
Metadata [260 B]
Get:17 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5652 kB]
Get:18 http://archive.ubuntu.com/ubuntu jammy/universe amd64 c-n-f Metadata
[286 kB]
Get:19 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB]
Get:20 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB]
Get:21 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 c-n-f Metadata
[8372 B]
Get:22 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1638
kB]
Get:23 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [307
kB]
Get:24 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages
[1864 kB]
Get:25 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en
[316 kB]
Get:26 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages
[1074 kB]
Get:27 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en
[245 kB]
Get:28 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f
Metadata [22.1 kB]
Get:29 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages
[42.7 kB]
Get:30 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en
[10.4 kB]
Get:31 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 c-n-f
Metadata [472 B]
Get:32 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages
[67.1 kB]
Get:33 http://archive.ubuntu.com/ubuntu jammy-backports/main Translation-en
[11.0 kB]
Get:34 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 c-n-f
Metadata [388 B]
Get:35 http://archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 c-n-f
Metadata [116 B]
Get:36 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages
[27.2 kB]
Get:37 http://archive.ubuntu.com/ubuntu jammy-backports/universe Translation-en
[16.2 kB]
Get:38 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 c-n-f
Metadata [644 B]
Get:39 http://archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 c-n-f
Metadata [116 B]
Get:40 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages [227
kB]
Get:41 http://archive.ubuntu.com/ubuntu jammy-proposed/main Translation-en
[51.1 kB]
Get:42 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 c-n-f
Metadata [2740 B]
Fetched 31.8 MB in 3s (10.9 MB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state
[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand
Thanks Timo!
focal verification complete =
csmith@midtown:~$ lxc launch ubuntu-daily:focal test-focal
Creating test-focal
Starting test-focal
csmith@midtown:~$ lxc exec test-focal bash
root@test-focal:~# hostname # confirm test-focal from standard meta-data
test-focal
root@test-focal:~# cloud-init clean # allow running init stage again
root@test-focal:~# exit
csmith@midtown:~$ lxc file push myfile.yaml test-focal/
csmith@midtown:~$ lxc exec test-focal bash
root@test-focal:~# apt update; apt install cloud-init -y; cloud-init --version
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:3 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Get:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Get:5 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8628 kB]
Get:6 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
[2919 kB]
Get:7 http://archive.ubuntu.com/ubuntu focal/universe Translation-en [5124 kB]
Get:8 http://archive.ubuntu.com/ubuntu focal/universe amd64 c-n-f Metadata [265
kB]
Get:9 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [144 kB]
Get:10 http://archive.ubuntu.com/ubuntu focal/multiverse Translation-en [104 kB]
Get:11 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 c-n-f Metadata
[9136 B]
Get:12 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [3296
kB]
Get:13 http://archive.ubuntu.com/ubuntu focal-updates/main Translation-en [521
kB]
Get:14 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages
[2916 kB]
Get:15 http://archive.ubuntu.com/ubuntu focal-updates/restricted Translation-en
[407 kB]
Get:16 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages
[1185 kB]
Get:17 http://archive.ubuntu.com/ubuntu focal-updates/universe Translation-en
[284 kB]
Get:18 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 c-n-f
Metadata [25.7 kB]
Get:19 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages
[26.2 kB]
Get:20 http://archive.ubuntu.com/ubuntu focal-updates/multiverse Translation-en
[7880 B]
Get:21 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 c-n-f
Metadata [620 B]
Get:22 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages
[45.7 kB]
Get:23 http://archive.ubuntu.com/ubuntu focal-backports/main Translation-en
[16.3 kB]
Get:24 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 c-n-f
Metadata [1420 B]
Get:25 http://archive.ubuntu.com/ubuntu focal-backports/restricted amd64 c-n-f
Metadata [116 B]
Get:26 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages
[25.0 kB]
Get:27 http://archive.ubuntu.com/ubuntu focal-backports/universe Translation-en
[16.3 kB]
Get:28 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 c-n-f
Metadata [880 B]
Get:29 http://archive.ubuntu.com/ubuntu focal-backports/multiverse amd64 c-n-f
Metadata [116 B]
Get:30 http://security.ubuntu.com/ubuntu focal-security/main Translation-en
[438 kB]
Get:31 http://security.ubuntu.com/ubuntu focal-security/restricted amd64
Packages [2799 kB]
Get:32 http://security.ubuntu.com/ubuntu focal-security/restricted
Translation-en [391 kB]
Get:33 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages
[959 kB]
Get:34 http://security.ubuntu.com/ubuntu focal-security/universe Translation-en
[202 kB]
Get:35 http://security.ubuntu.com/ubuntu focal-security/universe amd64 c-n-f
Metadata [19.2 kB]
Get:36 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64
Packages [24.0 kB]
Get:37 http://security.ubuntu.com/ubuntu focal-security/multiverse
Translation-en [5904 B]
Get:38 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 c-n-f
Metadata [548 B]
Fetched 31.1 MB in 4s (8328 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
7 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
cloud-init is already the newest version (24.1.3-0ubuntu1~20.04.1).
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
/usr/bin/cloud-init 24.1.3-0ubuntu1~20.04.1
root@test-focal:~## confirm usage failure
root@test-focal:~# cloud-init -f /myfile.yaml init
usage: /usr/bin/cloud-init [-h] [--version] [--debug] [--force]
{init,modules,single,query,features,analyze,devel,collect-logs,clean,status,schema}
...
/usr/bin/cloud-init: error: argument subcommand: invalid choice: '/myfile.yaml'
(choose from 'init', 'modules', 'single', 'query', 'features', 'analyze',
'devel', 'collect-logs', 'clean', 'status', 'schema')
root@test-focal:~# exit
csmith@midtown:~$ lxc file push setup_proposed.sh test-focal/
csmith@midtown:~$ lxc
[Bug 2064580] Re: Please update the package to 20240320.00
All suites (X, B, F, J, M, N, O) have passed CPC's internal testing (CTF) and were shared with Google. Google have came back to us today and confirmed that all the images passed their internal testing as well, so I've marked the bug as verification-done :) ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-mantic verification-needed-noble ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-jammy verification-done-mantic verification-done-noble verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064580 Title: Please update the package to 20240320.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064580] Re: Please update the package to 20240320.00
** Description changed: Following on from previous similar package update requests @ LP: #2020762, LP: #1996735, LP: #1938553 and LP: #1911689 this bug is a request to update the google-osconfig-agent to the upstream version `20240320.00` @ https://github.com/GoogleCloudPlatform/osconfig/releases/tag/20240320.00 This package has an SRU exception @ https://wiki.ubuntu.com/StableReleaseUpdates#google-osconfig-agent including an ageing exception detailed @ https://wiki.ubuntu.com/google- osconfig-agent-Updates There is some urgency in landing these changes to accommodate planned infrastructure changes on the Google Compute Platform. [Impact] This package is provided by Google for installation within guests that run on Google Compute Engine. It is part of a collection of tools and daemons, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating this package to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of this package is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Vendored Dependency] In this update, the vendored dependencies have changed. Here's the diff of what's changing and their version bumps: https://paste.ubuntu.com/p/ChcV6YB2CN/ There are some vendored dependencies changing in the tests, too. Here's the diff of that: https://paste.ubuntu.com/p/dwMPT675Rg/ Furthermore, the actual vendored changes are here: https://git.launchpad.net/~ubuntu-core-dev/+git/google-osconfig- agent/commit/?h=ubuntu/master=04c6d100f1d2a63c41456d04d0d3331e29199127 This also shows the exact files changed and the number of lines changed in those files. + [Where Problems Could Occur] + + There are many upstream changes in `20230504.00-0ubuntu3` vs. + `20240320.00-0ubuntu1`; however between the guest-test-infra suite [0] + (which is run for validation by CPC _and_ Google) and CPC's own internal + test harness (CTF) there is confidence that most if not all "edge cases" + and/or obvious regressions concerns can be dismissed before the new + version lands in `-updates` + [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/google-osconfig-agent-Updates The updated package is not built for armhf and riscv64 due to upstream regressions but the package is not used on those architectures thus please release the SRU without the armhf and risc64 binaries. The package does not build for powerpc on Xenial, but this is OK since it is not used on powerpc either. + + [0]: https://github.com/GoogleCloudPlatform/guest-test-infra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064580 Title: Please update the package to 20240320.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948714] Re: After reboot, the password set at install time doesn't work.
*** This bug is a duplicate of bug 1875062 *** https://bugs.launchpad.net/bugs/1875062 This bug is back in 24.04 (noble). Same issue - Set the keyboard to UK at install, but the keyboard used is US layout so special characters e.g. # & £ are transposed, and therefore doesn't work at first login. (At least I could see the error now) Tried on a Desktop install from the Beta, and also on a laptop install using the full release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948714 Title: After reboot, the password set at install time doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1948714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `upgrade_packages: true` user-data
This fix is also uploaded for SRU to noble in cloud-init version 24.1.3-0ubuntu3.2 ** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-mantic verification-needed-noble ** Tags added: verification-failed-focal verification-failed-jammy verification-failed-mantic verification-failed-noble ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `upgrade_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `upgrade_packages: true` user-data
** Tags added: regression-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `upgrade_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `upgrade_packages: true` user-data
Upload to oracular 24.2~2g51c6569f-0ubuntu1 released upstream commit 51c6569f96bee4f91aad5db58765c7abab7ffcdf which resolves this issue. Uploads are in the unapproved queue which resolve the SRU verification failures discovered in comment #13: - mantic: 24.1.3-0ubuntu1~23.10.5 - jammy: 24.1.3-0ubuntu1~22.04.4 - focal: 24.1.3-0ubuntu1~20.04.4 Will SRU re-run verification script when these uploads are available in -proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `upgrade_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand
mantic verification complete csmith@midtown:~$ lxc launch ubuntu-daily:mantic test-mantic Creating test-mantic Starting test-mantic csmith@midtown:~$ lxc file push myfile.yaml test-mantic/ csmith@midtown:~$ lxc file push setup_proposed.sh test-mantic/ csmith@midtown:~$ lxc exec test-mantic bash root@test-mantic:~# apt update; apt install cloud-init -y; cloud-init --version Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease Get:2 http://security.ubuntu.com/ubuntu mantic-security InRelease [109 kB] Get:3 http://archive.ubuntu.com/ubuntu mantic-updates InRelease [109 kB] Get:4 http://archive.ubuntu.com/ubuntu mantic-backports InRelease [90.8 kB] Get:5 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages [352 kB] Get:6 http://archive.ubuntu.com/ubuntu mantic/universe amd64 Packages [15.2 MB] Get:7 http://security.ubuntu.com/ubuntu mantic-security/main Translation-en [90.8 kB] Get:8 http://security.ubuntu.com/ubuntu mantic-security/restricted amd64 Packages [337 kB] Get:9 http://security.ubuntu.com/ubuntu mantic-security/restricted Translation-en [60.3 kB] Get:10 http://security.ubuntu.com/ubuntu mantic-security/universe amd64 Packages [273 kB] Get:11 http://security.ubuntu.com/ubuntu mantic-security/universe Translation-en [114 kB] Get:12 http://security.ubuntu.com/ubuntu mantic-security/universe amd64 DEP-11 Metadata [3860 B] Get:13 http://security.ubuntu.com/ubuntu mantic-security/universe amd64 c-n-f Metadata [788 B] Get:14 http://security.ubuntu.com/ubuntu mantic-security/multiverse amd64 Packages [5588 B] Get:15 http://security.ubuntu.com/ubuntu mantic-security/multiverse Translation-en [1732 B] Get:16 http://security.ubuntu.com/ubuntu mantic-security/multiverse amd64 c-n-f Metadata [232 B] Get:17 http://archive.ubuntu.com/ubuntu mantic/universe Translation-en [5951 kB] Get:18 http://archive.ubuntu.com/ubuntu mantic/universe amd64 DEP-11 Metadata [3793 kB] Get:19 http://archive.ubuntu.com/ubuntu mantic/universe amd64 c-n-f Metadata [303 kB] Get:20 http://archive.ubuntu.com/ubuntu mantic/multiverse amd64 Packages [239 kB] Get:21 http://archive.ubuntu.com/ubuntu mantic/multiverse Translation-en [113 kB] Get:22 http://archive.ubuntu.com/ubuntu mantic/multiverse amd64 DEP-11 Metadata [31.6 kB] Get:23 http://archive.ubuntu.com/ubuntu mantic/multiverse amd64 c-n-f Metadata [8356 B] Get:24 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages [413 kB] Get:25 http://archive.ubuntu.com/ubuntu mantic-updates/main Translation-en [110 kB] Get:26 http://archive.ubuntu.com/ubuntu mantic-updates/restricted amd64 Packages [354 kB] Get:27 http://archive.ubuntu.com/ubuntu mantic-updates/restricted Translation-en [62.7 kB] Get:28 http://archive.ubuntu.com/ubuntu mantic-updates/universe amd64 Packages [357 kB] Get:29 http://archive.ubuntu.com/ubuntu mantic-updates/universe Translation-en [138 kB] Get:30 http://archive.ubuntu.com/ubuntu mantic-updates/universe amd64 DEP-11 Metadata [3864 B] Get:31 http://archive.ubuntu.com/ubuntu mantic-updates/universe amd64 c-n-f Metadata [820 B] Get:32 http://archive.ubuntu.com/ubuntu mantic-updates/multiverse amd64 Packages [8568 B] Get:33 http://archive.ubuntu.com/ubuntu mantic-updates/multiverse Translation-en [2824 B] Get:34 http://archive.ubuntu.com/ubuntu mantic-updates/multiverse amd64 c-n-f Metadata [232 B] Get:35 http://archive.ubuntu.com/ubuntu mantic-backports/main amd64 c-n-f Metadata [112 B] Get:36 http://archive.ubuntu.com/ubuntu mantic-backports/restricted amd64 c-n-f Metadata [116 B] Get:37 http://archive.ubuntu.com/ubuntu mantic-backports/universe amd64 Packages [3936 B] Get:38 http://archive.ubuntu.com/ubuntu mantic-backports/universe Translation-en [1392 B] Get:39 http://archive.ubuntu.com/ubuntu mantic-backports/universe amd64 c-n-f Metadata [116 B] Get:40 http://archive.ubuntu.com/ubuntu mantic-backports/multiverse amd64 c-n-f Metadata [116 B] Fetched 28.6 MB in 5s (5810 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 18 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: cloud-init 1 upgraded, 0 newly installed, 0 to remove and 17 not upgraded. Need to get 597 kB of archives. After this operation, 55.3 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 cloud-init all 24.1.3-0ubuntu1~23.10.2 [597 kB] Fetched 597 kB in 0s (1535 kB/s) Preconfiguring packages ... (Reading database ... 33578 files and directories currently installed.) Preparing to unpack .../cloud-init_24.1.3-0ubuntu1~23.10.2_all.deb ... Unpacking cloud-init (24.1.3-0ubuntu1~23.10.2) over (23.4.4-0ubuntu0~23.10.1) ... Setting up cloud-init (24.1.3-0ubuntu1~23.10.2) ... Installing new version of config file
[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand
= jammy verification complete
csmith@midtown:~$ lxc launch ubuntu-daily:jammy test-jammy
Creating test-jammy
Starting test-jammy
csmith@midtown:~$ lxc file push myfile.yaml test-jammy/
csmith@midtown:~$ lxc file push setup_proposed.sh test-jammy/
csmith@midtown:~$ lxc exec test-jammy bash
root@test-jammy:~# hostname # confirm test-jammy from standard meta-data
test-jammy
root@test-jammy:~# cloud-init clean # allow running init stage again
root@test-jammy:~# # confirm usage failure
root@test-jammy:~# cloud-init -f /myfile.yaml init
usage: /usr/bin/cloud-init [-h] [--version] [--debug] [--force]
{init,modules,single,query,features,analyze,devel,collect-logs,clean,status,schema}
...
/usr/bin/cloud-init: error: argument subcommand: invalid choice: '/myfile.yaml'
(choose from 'init', 'modules', 'single', 'query', 'features', 'analyze',
'devel', 'collect-logs', 'clean', 'status', 'schema')
root@test-jammy:~# # upgrade cloud-init to confirm --file support
root@test-jammy:~# sh /setup_proposed.sh
deb http://archive.ubuntu.com/ubuntu jammy-proposed main
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Get:3 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy-proposed InRelease [270 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [14.1 MB]
Get:7 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
[1394 kB]
Get:8 http://archive.ubuntu.com/ubuntu jammy/universe Translation-en [5652 kB]
Get:9 http://security.ubuntu.com/ubuntu jammy-security/main Translation-en [243
kB]
Get:10 http://archive.ubuntu.com/ubuntu jammy/universe amd64 c-n-f Metadata
[286 kB]
Get:11 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [217 kB]
Get:12 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages
[848 kB]
Get:13 http://archive.ubuntu.com/ubuntu jammy/multiverse Translation-en [112 kB]
Get:14 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 c-n-f Metadata
[8372 B]
Get:15 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1612
kB]
Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [304
kB]
Get:17 http://archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en
[311 kB]
Get:18 http://security.ubuntu.com/ubuntu jammy-security/universe Translation-en
[163 kB]
Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages
[1072 kB]
Get:20 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 c-n-f
Metadata [16.8 kB]
Get:21 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64
Packages [37.2 kB]
Get:22 http://security.ubuntu.com/ubuntu jammy-security/multiverse
Translation-en [7588 B]
Get:23 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 c-n-f
Metadata [260 B]
Get:24 http://archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en
[245 kB]
Get:25 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f
Metadata [22.1 kB]
Get:26 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages
[42.7 kB]
Get:27 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse Translation-en
[10.4 kB]
Get:28 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 c-n-f
Metadata [472 B]
Get:29 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages
[67.1 kB]
Get:30 http://archive.ubuntu.com/ubuntu jammy-backports/main Translation-en
[11.0 kB]
Get:31 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 c-n-f
Metadata [388 B]
Get:32 http://archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 c-n-f
Metadata [116 B]
Get:33 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages
[27.2 kB]
Get:34 http://archive.ubuntu.com/ubuntu jammy-backports/universe Translation-en
[16.2 kB]
Get:35 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 c-n-f
Metadata [644 B]
Get:36 http://archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 c-n-f
Metadata [116 B]
Get:37 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages [262
kB]
Get:38 http://archive.ubuntu.com/ubuntu jammy-proposed/main Translation-en
[55.7 kB]
Get:39 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 c-n-f
Metadata [2740 B]
Fetched 27.7 MB in 3s (8312 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
cloud-init
1 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
Need to get 560 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 cloud-init all
24.1.3-0ubuntu1~22.04.3 [560 kB]
Fetched 560 kB in
[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand
focal verification complete
csmith@midtown:~$ lxc file push myfile.yaml test-focal/
csmith@midtown:~$ lxc exec test-focal bash
root@test-focal:~# # confirm usage failure
root@test-focal:~# cloud-init -f /myfile.yaml init
usage: /usr/bin/cloud-init [-h] [--version] [--debug] [--force]
{init,modules,single,query,features,analyze,devel,collect-logs,clean,status,schema}
...
/usr/bin/cloud-init: error: argument subcommand: invalid choice: '/myfile.yaml'
(choose from 'init', 'modules', 'single', 'query', 'features', 'analyze',
'devel', 'collect-logs', 'clean', 'status', 'schema')
root@test-focal:~# exit
csmith@midtown:~$ # upgrade cloud-init to proposed
csmith@midtown:~$ lxc file push setup_proposed.sh test-focal/
csmith@midtown:~$ lxc exec test-focal -- sh /setup_proposed.sh
deb http://archive.ubuntu.com/ubuntu focal-proposed main
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Get:2 http://security.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Get:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Get:5 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
[2892 kB]
Get:6 http://archive.ubuntu.com/ubuntu focal-proposed InRelease [267 kB]
Get:7 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages [8628 kB]
Get:8 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages
[957 kB]
Get:9 http://security.ubuntu.com/ubuntu focal-security/universe Translation-en
[201 kB]
Get:10 http://security.ubuntu.com/ubuntu focal-security/universe amd64 c-n-f
Metadata [19.2 kB]
Get:11 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64
Packages [24.0 kB]
Get:12 http://security.ubuntu.com/ubuntu focal-security/multiverse
Translation-en [5904 B]
Get:13 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 c-n-f
Metadata [548 B]
Get:14 http://archive.ubuntu.com/ubuntu focal/universe Translation-en [5124 kB]
Get:15 http://archive.ubuntu.com/ubuntu focal/universe amd64 c-n-f Metadata
[265 kB]
Get:16 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages [144 kB]
Get:17 http://archive.ubuntu.com/ubuntu focal/multiverse Translation-en [104 kB]
Get:18 http://archive.ubuntu.com/ubuntu focal/multiverse amd64 c-n-f Metadata
[9136 B]
Get:19 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [3269
kB]
Get:20 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages
[1183 kB]
Get:21 http://archive.ubuntu.com/ubuntu focal-updates/universe Translation-en
[284 kB]
Get:22 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 c-n-f
Metadata [25.7 kB]
Get:23 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 Packages
[26.2 kB]
Get:24 http://archive.ubuntu.com/ubuntu focal-updates/multiverse Translation-en
[7880 B]
Get:25 http://archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 c-n-f
Metadata [620 B]
Get:26 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages
[45.7 kB]
Get:27 http://archive.ubuntu.com/ubuntu focal-backports/main Translation-en
[16.3 kB]
Get:28 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 c-n-f
Metadata [1420 B]
Get:29 http://archive.ubuntu.com/ubuntu focal-backports/restricted amd64 c-n-f
Metadata [116 B]
Get:30 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 Packages
[25.0 kB]
Get:31 http://archive.ubuntu.com/ubuntu focal-backports/universe Translation-en
[16.3 kB]
Get:32 http://archive.ubuntu.com/ubuntu focal-backports/universe amd64 c-n-f
Metadata [880 B]
Get:33 http://archive.ubuntu.com/ubuntu focal-backports/multiverse amd64 c-n-f
Metadata [116 B]
Get:34 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages [326
kB]
Get:35 http://archive.ubuntu.com/ubuntu focal-proposed/main Translation-en
[66.2 kB]
Get:36 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 c-n-f
Metadata [1324 B]
Fetched 24.3 MB in 3s (7769 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be upgraded:
cloud-init
1 upgraded, 0 newly installed, 0 to remove and 27 not upgraded.
Need to get 563 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 cloud-init all
24.1.3-0ubuntu1~20.04.3 [563 kB]
Fetched 563 kB in 0s (1435 kB/s)
Preconfiguring packages ...
(Reading database ... 32192 files and directories currently installed.)
Preparing to unpack .../cloud-init_24.1.3-0ubuntu1~20.04.3_all.deb ...
Unpacking cloud-init (24.1.3-0ubuntu1~20.04.3) over (24.1.3-0ubuntu1~20.04.1)
...
Setting up cloud-init (24.1.3-0ubuntu1~20.04.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for rsyslog (8.2001.0-1ubuntu1.3) ...
csmith@midtown:~$# Assert cloud-init -f
[Bug 2064132] Re: images without snapd installed error on `upgrade_packages: true` user-data
SRU verification determined that the fix in -proposed was not complete enough to fix the package_ugprade: true case. Upstream commit has landed fixing this issue:https://github.com/canonical/cloud- init/commit/51c6569f96bee4f91aad5db58765c7abab7ffcdf Uploads will be pushed to focal/jammy/mantic-proposed shortly cherry- picking this fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `upgrade_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064580] Re: Please update the package to 20240320.00
We'll also need ubuntu/mantic and ubuntu/noble branches created in preparation for the looming SRU :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064580 Title: Please update the package to 20240320.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064580] Re: Please update the package to 20240320.00
oracular (master) debdiff ** Merge proposal linked: https://code.launchpad.net/~kajiya/+git/google-osconfig-agent/+merge/465503 ** Merge proposal linked: https://code.launchpad.net/~kajiya/+git/google-osconfig-agent/+merge/465504 ** Patch added: "20230504.00-vs-20240320.00.diff" https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+attachment/5774570/+files/20230504.00-vs-20240320.00.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064580 Title: Please update the package to 20240320.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2064580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `upgrade_packages: true` user-data
Sru validation script ** Attachment removed: "sru-2064132.sh" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+attachment/5774506/+files/sru-2064132.sh ** Attachment added: "sru-2064132.sh" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+attachment/5774571/+files/sru-2064132.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `upgrade_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `upgrade_packages: true` user-data
** Summary changed: - images without snapd installed error on `update_packages: true` user-data + images without snapd installed error on `upgrade_packages: true` user-data -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `upgrade_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `update_packages: true` user-data
** Description changed:
[ Impact ]
* SRU of cloud-init 24.1.3 to Focal, Jammy and Mantic introduced a
regression where cloud-init will attempt to call `snap refresh` on new
Ubuntu instance launches if the Ubuntu image does not contain snapd deb
package and optional #cloud-config user-data is provided which contains
`upgrade_packages: true`.
* Such optional user-data on custom ubuntu images will result in cloud-init
exiting in error condition as seen from cloud-init status due to the following
error message:
- ('package_update_upgrade_install', ProcessExecutionError("Unexpected error
while running command.\nCommand: ['snap', 'refresh']\nExit code: -\nReason:
[Errno 2] No such file or directory: b'snap'\nStdout: -\nStderr: -"))
This only affects new custom Ubuntu image launches where both of the
following conditions are met:
1. image is a custom ubuntu image which does not contain snapd deb package
2. At instance launch, optional #cloud-config user-data contains
`package_upgrade: true`
Ubuntu cloudimages published by Canonical for Focal, Jammy and Mantic
all currently have the snapd deb package installed.
Even for custom Ubuntu images without snapd deb package installed, this
issue is only triggered when #cloud-config contains the optional
`package_upgrade: true` during instance launch.
This error log does cause cloud-init status to exit non-zero, but it
doesn't affect the integrity of the configuration applied to the system.
It is just an undesirable error log message for an unsupported (snap)
package manager within the environment.
[ Test Plan ]
* # launch ubuntu cloud images in LXC, remove snapd, provide
"#cloud-config\npackage_upgrade:true" as user-data and clean reboot to force
cloud-init to attempt to upgrade any package managers (snap and apt) where
applicable.
* confirm no snap command present in image
* check cloud-init status --format=yaml to ensure no errors
* grep snap.*refresh /var/log/cloud-init.log to assert no stray snap refresh
is attempted on an image without snap
#!/bin/bash
+ set -ex
SERIES=$1
+
cat > pkg-update.yaml < setup_proposed.sh
[Bug 2064132] Re: images without snapd installed error on `update_packages: true` user-data
** Description changed:
[ Impact ]
* SRU of cloud-init 24.1.3 to Focal, Jammy and Mantic introduced a
regression where cloud-init will attempt to call `snap refresh` on new
Ubuntu instance launches if the Ubuntu image does not contain snapd deb
package and optional #cloud-config user-data is provided which contains
`upgrade_packages: true`.
* Such optional user-data on custom ubuntu images will result in cloud-init
exiting in error condition as seen from cloud-init status due to the following
error message:
- ('package_update_upgrade_install', ProcessExecutionError("Unexpected error
while running command.\nCommand: ['snap', 'refresh']\nExit code: -\nReason:
[Errno 2] No such file or directory: b'snap'\nStdout: -\nStderr: -"))
This only affects new custom Ubuntu image launches where both of the
following conditions are met:
1. image is a custom ubuntu image which does not contain snapd deb package
2. At instance launch, optional #cloud-config user-data contains
`package_upgrade: true`
Ubuntu cloudimages published by Canonical for Focal, Jammy and Mantic
all currently have the snapd deb package installed.
Even for custom Ubuntu images without snapd deb package installed, this
issue is only triggered when #cloud-config contains the optional
`package_upgrade: true` during instance launch.
This error log does cause cloud-init status to exit non-zero, but it
doesn't affect the integrity of the configuration applied to the system.
It is just an undesirable error log message for an unsupported (snap)
package manager within the environment.
-
[ Test Plan ]
* # launch ubuntu cloud images in LXC, remove snapd, provide
"#cloud-config\npackage_upgrade:true" as user-data and clean reboot to force
cloud-init to attempt to upgrade any package managers (snap and apt) where
applicable.
* confirm no snap command present in image
* check cloud-init status --format=yaml to ensure no errors
* grep snap.*refresh /var/log/cloud-init.log to assert no stray snap refresh
is attempted on an image without snap
#!/bin/bash
- lxc launch ubuntu-daily:jammy test-no-snap
- sleep 3
- lxc exec test-no-snap -- cloud-init status --wait
- lxc exec test-no-snap -- apt remove snapd -y
-
+ SERIES=$1
cat > pkg-update.yaml < pkg-update.yaml
[Bug 2061026] Re: Copy file within cifs network share hangs with cp
Exactly the same for me, just started after installing updates today -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061026 Title: Copy file within cifs network share hangs with cp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/2061026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
On my test VM I can see the cupsd profile DOES have 'attach_disconnected' flag, but not 'attach_disconnected.path=/run/' If I add it and restart the cups.service, it starts successfully. rsyslogd and sssd apparmor profiles do not have either these flags. Could an apparmor abstraction work for this? i.e. if the system has 'boot-managed-by-snapd' package we could pull in an apparmor abstraction which adds these flags? Not sure what would be appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
Answering questions from #2064088 Q: Did you install this fde/tpm setup using the ubuntu desktop noble installer? Or was hit some manual setup? A: The install was performed using autoinstall with the desktop ISO. Attached is a copy of the autoinstall yaml ** Attachment added: "autoinstall user-data YAML" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+attachment/5774010/+files/user-data -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: Services fail to start in noble deployed with TPM+FDE
Answering questions from #2064088 Q: Can you also show the output of: ps fauxwZ A: See attached ** Attachment added: "ps" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+attachment/5774011/+files/ps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: Services fail to start in noble deployed with TPM+FDE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand
** Summary changed: - cli behavior changed + cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064300 Title: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: rsyslog service timeout on noble numbat
Do you think we should mark #2064088 as a duplicate of this (or vice- versa), if we're confident this is the same underlying issue? There are some outstanding questions for me on that bug, but it might make sense to focus our comments in one place going forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: rsyslog service timeout on noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064300] Re: cli behavior changed
** Description changed: - Originally reported on Github[1], cloud-init released a change in the - cli[2] that broke former cloud-init cli commands. + [ Impact ] - Previously `cloud-init -f init` was allowed, but after the 24.1 SRU release to Jammy, this broke and + * Environments or scripts which directly call cloud-init subcommands and +provide an optional -f or --file argument to inject supplemental +configuration after first boot will receive usage errors on the command +line which will break any supplemental scripted setup of configuration. +This affects some platforms which may provide secondary configuration after +cloud-init's first boot. + +Workaround: +Upstream cloud-init requires -f/--file arguments come after the +subcommand instead of before. Change the order of these parameters, placing +-f or --file after the subcommand as a workaround while awaiting an SRU fix. + + * Direct calls to cloud-init init, modules or single are atypical for most +deployments because automated configuration generally relies on +cloud-init systemd units running the various boot stages invoking the +cloud-init CLI directly. But, to better support custom environments which +need to provide an additional layer of configuration after first boot, this +change in behavior is something we would like to resolve on stable releases. + + [ Test Plan ] + + * Launch daily images in LXC and confirm usage failure inf cloud-init 24.1.3 +when providing supplemental file config before the init subcommand: +cloud-init -f myfile.yaml init + +$ cat > myfile.yaml < setup_proposed.sh
[Bug 2064088] Re: sssd service fails to start in noble numbat
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088/+attachment/5773256/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064088 Title: sssd service fails to start in noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064088] Re: sssd service fails to start in noble numbat
Here is the dmesg output when trying to start sssd. I'll attach syslog as well from the same time period ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088/+attachment/5773255/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064088 Title: sssd service fails to start in noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] Re: rsyslog service timeout on noble numbat
I've just found that the cups.service is also experiencing the same behaviour. Again it has the service type 'notify'. I suspect other services using this type will have the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: rsyslog service timeout on noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `update_packages: true` user-data
** Also affects: cloud-init (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `update_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `update_packages: true` user-data
Given that all Canonical Ubuntu images (including server minimal and cloud minimal images) contain snapd deb package, this is not a critical path concern for Canonical stable supported Ubuntu images. So, `regression-update` tag is dropped for our specific support paths as this doesn't regress image streams we claim to support. This SRU remains queued in unapproved queue for Focal, Jammy, Mantic and Novble with priority for next SRU reviewer when time is available as we do want this fixed shortly to better support any derivative Ubuntu images which may have dropped snapd from their images in an effect to shrink that image size even further. ** Tags removed: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `update_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `update_packages: true` user-data
** Description changed:
- In Ubuntu images that do not have snapd debian package installed
- launching with the following user-data triggers cloud-init to run `snap
- refresh` when that command doesn't exist.
+ [ Impact ]
+ * SRU of cloud-init 24.1.3 to Focal, Jammy and Mantic introduced a
+ regression where cloud-init will attempt to call `snap refresh` on new
+ Ubuntu instance launches the Ubuntu image does not contain snapd deb
+ package installed and optional #cloud-config user-data is provided
+ which contains `upgrade_packages: true`.
+
+ * Such optional user-data on custom ubuntu images will result in cloud-init
exiting in error condition as seen from cloud-init status due to the following
error message:
+ - ('package_update_upgrade_install', ProcessExecutionError("Unexpected
error while running command.\nCommand: ['snap', 'refresh']\nExit code:
-\nReason: [Errno 2] No such file or directory: b'snap'\nStdout: -\nStderr: -"))
+
+
+ This only affects new custom Ubuntu image launches where both of the
following conditions are met:
+ 1. image is a custom ubuntu image which does not contain snapd deb package
+ 2. At instance launch, optional #cloud-config user-data contains
`package_upgrade: true`
+
+
+ Ubuntu cloudimages published by Canonical for Focal, Jammy and Mantic all
currently snapd deb package.
+
+ And even for custom Ubuntu images without snapd installed, only when
+ package operations are provided via #cloud-config is the instance launch
+ affected.
+
+
+ [ Test Plan ]
+ * # launch ubuntu cloud images in LXC, remove snapd, provide
"#cloud-config\npackage_upgrade:true" as user-data and clean reboot to force
cloud-init to attempt to upgrade any package managers (snap and apt) where
applicable.
+
+ * confirm no snap command present in image
+ * check cloud-init status --format=yaml to ensure no errors
+ * grep snap.*refresh /var/log/cloud-init.log to assert no stray snap refresh
is attempted on an image without snap
+
+
+ #!/bin/bash
+ lxc launch ubuntu-daily:jammy test-no-snap
+ sleep 3
+ lxc exec test-no-snap -- cloud-init status --wait
+ lxc exec test-no-snap -- apt remove snapd -y
+
+ cat > pkg-update.yaml < pkg-update.yaml < pkg-update.yaml < pkg-update.yaml
[Bug 2064136] Re: Please add a new entry for Ubuntu 24.10 Oracular Oriole
@bdrung I think those are the only places it's been announced publicly, and don't worry I know there isn't much you can do right now - I'm just getting our (CPC's) ducks in a row :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064136 Title: Please add a new entry for Ubuntu 24.10 Oracular Oriole To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/2064136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064136] [NEW] Please add a new entry for Ubuntu 24.10 Oracular Oriole
Public bug reported: [ Impact ] Several tools rely on the `distro-info` package to tell them which releases are available. This package just contains data, with no format changes. [ Regression Potential ] Minimal, as long as we are only adding new entries (we do this every release). [ Test Case ] "ubuntu-distro-info -df" should name the release in full: Ubuntu 24.10 "Oracular Oriole" ** Affects: distro-info-data (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/2064136 Title: Please add a new entry for Ubuntu 24.10 Oracular Oriole To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/2064136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `update_packages: true` user-data
Upstream commit merged https://github.com/canonical/cloud- init/commit/a6f7577d582aa51d51ca129fcff65313e210d47b ** Changed in: cloud-init (Ubuntu) Status: New => Fix Committed ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Chad Smith (chad.smith) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `update_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] Re: images without snapd installed error on `update_packages: true` user-data
Upstream github issue re-opened representing this fix: https://github.com/canonical/cloud-init/issues/5143 upstream Pull request fixing this issue: https://github.com/canonical/cloud-init/pull/5224 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064132 Title: images without snapd installed error on `update_packages: true` user- data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2064132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064132] [NEW] images without snapd installed error on `update_packages: true` user-data
Public bug reported: In Ubuntu images that do not have snapd debian package installed launching with the following user-data triggers cloud-init to run `snap refresh` when that command doesn't exist. reproducer: lxc launch ubuntu-daily:jammy test-no-snap sleep 3 lxc exec test-no-snap -- cloud-init status --wait lxc exec test-no-snap -- apt remove snapd -y cat > pkg-update.yaml
[Bug 2053157] Re: Jammy: netplan permissions warnings
Just because tags show verification needed. I ran through and validated
the netplan on jammy has right limited perms as root-rw and no warnings
emitted by netplan apply due to permissions
## test logs
csmith@midtown:~$ lxc launch ubuntu-daily:jammy t-j
Creating t-j
Starting t-j
csmith@midtown:~$ lxc exec t-j -- cloud-init status --wait --format=yaml
---
_schema_version: '1'
boot_status_code: enabled-by-generator
datasource: lxd
detail: DataSourceLXD
errors: []
extended_status: done
init:
errors: []
finished: 1714400907.8807135
recoverable_errors: {}
start: 1714400907.4610379
init-local:
errors: []
finished: 1714400906.754673
recoverable_errors: {}
start: 1714400906.4037504
last_update: Mon, 29 Apr 2024 14:28:33 +
modules-config:
errors: []
finished: 1714400913.6523855
recoverable_errors: {}
start: 1714400913.5117085
modules-final:
errors: []
finished: 1714400913.9227617
recoverable_errors: {}
start: 1714400913.8417974
recoverable_errors: {}
schemas:
'1':
boot_status_code: enabled-by-generator
datasource: lxd
detail: DataSourceLXD
errors: []
extended_status: done
init:
errors: []
finished: 1714400907.8807135
recoverable_errors: {}
start: 1714400907.4610379
init-local:
errors: []
finished: 1714400906.754673
recoverable_errors: {}
start: 1714400906.4037504
last_update: Mon, 29 Apr 2024 14:28:33 +
modules-config:
errors: []
finished: 1714400913.6523855
recoverable_errors: {}
start: 1714400913.5117085
modules-final:
errors: []
finished: 1714400913.9227617
recoverable_errors: {}
start: 1714400913.8417974
recoverable_errors: {}
stage: null
status: done
stage: null
status: done
...
csmith@midtown:~$ echo $?
0
csmith@midtown:~$ lxc exec t-j -- ls -ltr /etc/netplan/50-cloud-init.yaml
-rw--- 1 root root 389 Apr 29 14:28 /etc/netplan/50-cloud-init.yaml
csmith@midtown:~$ lxc exec t-j -- netplan apply
WARNING:root:Cannot call Open vSwitch: ovsdb-server.service is not running.
csmith@midtown:~$ lxc exec t-j -- cloud-init --version
/usr/bin/cloud-init 24.1.3-0ubuntu1~22.04.1
** Tags removed: verification-needed
** Tags added: verification-done
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2053157
Title:
Jammy: netplan permissions warnings
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2053157/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064096] [NEW] rsyslog service timeout on noble numbat
Public bug reported: This might be related to #2064088 The rsyslog service is continually timing out and restarting. If I use a service drop-in file and change the 'Type' from 'notify' to 'simple', the service starts and appears to work normally. In the journal, I can see the attached apparmor errors. I can't make sense of them, but if it's a similar issue to #2064088, then I suspect apparmor is preventing the systemd notify function from alerting systemd that the service is up and running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsyslog 8.2312.0-3ubuntu9 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 10:37:46 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "rsyslog.log" https://bugs.launchpad.net/bugs/2064096/+attachment/5772453/+files/rsyslog.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064096 Title: rsyslog service timeout on noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2064096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064088] Re: sssd service fails to start in noble numbat
I should add that this is a system built with TPM-backed FDE if that has any relevance. I haven't tested on a non-encrypted system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064088 Title: sssd service fails to start in noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064088] [NEW] sssd service fails to start in noble numbat
Public bug reported: On a fresh build of Ubuntu 24.04, attempting to run the sssd service is failing continuously with a systemd service 'timeout' error. The same /etc/sssd/sssd.conf file is working in 20.04 and 22.04 I believe this issue is specifically related to the sssd systemd service. In the default sssd.service file, the service 'Type' is 'notify' (It's the same in 20.04 and 22.04). However, the service is getting 'permission denied' errors when notifying systemd that the service is up. See attached. If I use a service drop-in to change the service 'Type' to 'simple', the service starts immediately and works as intended. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: sssd 2.9.4-1.1ubuntu6 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 09:20:02 2024 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: sssd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sssd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "/var/log/sssd/sssd.log" https://bugs.launchpad.net/bugs/2064088/+attachment/5772395/+files/sssd.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064088 Title: sssd service fails to start in noble numbat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2064088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063961] [NEW] Microsoft 365 account keeps disconnecting
Public bug reported: When I use the new (24.04) settings and 'Online Accounts' to connect to Microsoft 365, it authenticates, works well for about 5 minutes and then disconnects. I have to remove that account and redo it every time I want to use it. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-settings 24.04.3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 19:04:06 2024 InstallationDate: Installed on 2024-04-27 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) PackageArchitecture: all SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063961 Title: Microsoft 365 account keeps disconnecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2063961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059337] Re: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded
** Changed in: cloud-init (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059337 Title: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2059337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062042] Re: "No valid sources.list entry found" and "An upgrade might not succeed" when running "sudo do-dist-upgrade -d" on Ubuntu 23.10
This fixed the problem. Thanks! Although, I wonder if this will affect others who try to upgrade to 24.04 when it releases tomorrow? That's part of the reason that I went ahead and posted the bug rather than just waiting for the release date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062042 Title: "No valid sources.list entry found" and "An upgrade might not succeed" when running "sudo do-dist-upgrade -d" on Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2062042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063315] Re: Suspend & Resume functionality broken/timesout in GCE
** Description changed: - Suspend/Resume capability is broken in all noble images with kernel - version + [Impact] + + Suspend/Resume capability is broken in all noble images with kernel version 6.8.0-1007-gcp. + + GCE offers the capability to "Suspend" a VM to conserve power/lower + costs when the instance is not in use [0]. It uses ACPI S3 signals to + tell the guest to power down. This capability no longer works in the + latest kernel with the following error: + + ``` + Operation type [suspend] failed with message "Instance suspend failed due to guest timeout." + ``` + + which points to the following [1]. + + + + Refs: + + [0]: https://cloud.google.com/compute/docs/instances/suspend-resume- + instance + + [1]: + https://cloud.google.com/compute/docs/troubleshooting/troubleshooting- + suspend-resume#there_was_a_guest_timeout -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063315 Title: Suspend & Resume functionality broken/timesout in GCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2063315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063315] [NEW] Suspend & Resume functionality broken/timesout in GCE
Public bug reported: Suspend/Resume capability is broken in all noble images with kernel version ** Affects: linux-gcp (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/2063315 Title: Suspend & Resume functionality broken/timesout in GCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2063315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062607] Re: google-guest-agent and google-osconfig-agent security update and tests
Images with these changes (installed from the above PPA) passed CPC's own internal validation (CTF), and Google tested the candidate images and said they were fine to proceed with! ** Tags added: verification-done verification-done-jammy verification- done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062607 Title: google-guest-agent and google-osconfig-agent security update and tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2062607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944746] Re: LibreOffice from Ubuntu Store/snaps broken GNOME integration for remote smb shares
This issue is still present with the current latest Libreoffice Snap version (24.2.2.2) both in Ubuntu 22.04 LTS and in the 24.04 Beta. SMB shares and other GVFS mounted network locations are not visible in the Open/Save file window. If I try to manually navigate to the files under `/run/user//gvfs/` I'm getting a 'Permission denied' error. If I open the file directly from Nautilus using right-click 'Open With', instead I get the attached error. ** Attachment added: "Screenshot from 2024-04-22 15-34-32.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1944746/+attachment/5769396/+files/Screenshot%20from%202024-04-22%2015-34-32.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944746 Title: LibreOffice from Ubuntu Store/snaps broken GNOME integration for remote smb shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1944746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image
Thanks Lukas: +1 on this changeset not degrading early boot install scenarios where systemd services are ordered After=systemd-networkd- wait-online.service Preliminary testing on Azure platform look good with accelerated networking enabled have confirmed dual-nic tests correctly configure the primary network devices brought and blocking systemd-networkd-wait-online awaiting the matching hv_netsvc devices. The tests confirm systemd-networkd-wait-online.service properly awaits the individual devices Also, initial cloud-init integration test runs on Azure noble w/ netplan.io v.1.0-2ubuntu1 do not seem to expose any regressions for our integration tests so far. cloud-init Ec2 testing of this same proposed netplan.io package doesn't show any degradation of behavior in detecting Ec2's IMDS in early boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060311 Title: Setting "optional: true" to overcome he timeout "Job systemd-networkd- wait-online" does no longer work with latest noble image To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2060311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059337] Re: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded
Marking won't fix as the resolution was in needrestart not cloud-init -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059337 Title: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2059337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059337] Re: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded
Closing cloud-init task for this bug as cloudimages created after 20240408 contain appropriate needrestart to defer cloud-final.service during cloud-init package upgrade. ** Changed in: cloud-init (Ubuntu Noble) Status: Confirmed => 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/2059337 Title: noble: needrestart triggering SIGTERM of cloud-final.service preventing apt packages from being installed when cloud-init is also being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2059337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
