[Bug 2065363] [NEW] snapd fucked up
Public bug reported: no further info ProblemType: Package DistroRelease: Ubuntu 24.04 Package: snapd (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 Date: Fri May 10 10:54:35 2024 ErrorMessage: installed snapd package post-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2024-05-09 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: snapd Title: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065363 Title: snapd fucked up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2065363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058227] Re: Crash during upgrade from Mantic to Noble due to Python 3.12
So, what you are saying is that https://discourse.ubuntu.com/t/noble- numbat-24-04-release-status-tracking/44043 needs an update, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058227 Title: Crash during upgrade from Mantic to Noble due to Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/2058227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064548] Re: kwallet will not accept passw; nor let me change it
If you need to reset the password and it’s not accepting the current one, you might need to delete the wallet file to reset it. The wallet file is usually located at /home//.local/share/kwalletd/kdewallet.kwl. Deleting this file will prompt the creation of a new wallet and allow you to set a new password. https://www-netbenefits.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064548 Title: kwallet will not accept passw; nor let me change it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwalletmanager/+bug/2064548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065076] Re: nvidia failure to resume from suspend; kernel fallback broken
I posted back too soon. The problem has just surfaced again. When I tried to resume my system just now, the screen would not turn on again. As pointed out before, the mouse/keyboard appear to be dead when that happens. The CPU fans also run full speed and do not stop until I reboot. Could this "regression" (if that's the proper term...) be caused by the gnome-shell updates I ran today? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065076 Title: nvidia failure to resume from suspend; kernel fallback broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 517862]
Engage in exhilarating tag matches with Tag 2. React quickly, chase down opponents, and evade being tagged to claim victory! https://tag2.netlify.app/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/517862 Title: Unhandled sense code To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/517862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999480] Re: ubuntu-unity-desktop metapackage requires pulseaudio
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-unity-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999480 Title: ubuntu-unity-desktop metapackage requires pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1999480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999480] Re: ubuntu-unity-desktop metapackage requires pulseaudio
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-sound (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999480 Title: ubuntu-unity-desktop metapackage requires pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1999480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1999480] Re: ubuntu-unity-desktop metapackage requires pulseaudio
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pipewire (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1999480 Title: ubuntu-unity-desktop metapackage requires pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1999480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058330] Re: Update amd-pmf for AMD strix series
** Description changed: + [SRU Justfication] + + [Impact] + + Missing AMD-PMF support for AMD Strix platforms. + + [Fix] + + A few commits from v6.9-rc1. + + [Test Case] + + And feature enabled message should appear in dmesg: + + [ 3.203628] amd-pmf AMDI0103:00: registered PMF device successfully + + Access via sysfs: + + root@test:/sys/devices/platform/AMDI0103:00# cat cnqf_enable + on + + [Where problems could occur] + + PMF once caused cpufreq locks or other unexpected behaviors in the past + and may take additional fix to address. + + [Other Info] + + While this is in v6.9-rc-1 now, Noble and OEM-6.8 will be nominated for + fix. + + == original bug report == + These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058330 Title: Update amd-pmf for AMD strix series To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058330] Re: Update amd-pmf for AMD strix series
** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Assignee: Anthony Wong (anthonywong) => (unassigned) ** Changed in: linux (Ubuntu Noble) Assignee: Anthony Wong (anthonywong) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.8 (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided => High ** No longer affects: linux-oem-6.8 (Ubuntu Noble) ** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Noble) ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: Fix Released ** Also affects: linux-oem-6.8 (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Oracular) ** Changed in: linux-oem-6.8 (Ubuntu Oracular) Status: New => Invalid ** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-oem-6.8 (Ubuntu Noble) Importance: Medium => High ** Changed in: linux-oem-6.8 (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Noble) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058330 Title: Update amd-pmf for AMD strix series To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058331] Re: Update amd_sfh for AMD strix series
SRU: * https://kernel.ubuntu.com/gitea/kernel/noble-linux-oem/pulls/2 (oem-6.8) ** Description changed: + [SRU Justification] + + [Impact] + + AMD MP2 controller not correctly enabled on new processors and thus the + associated sensors. + + [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 + + [Fix] + + 6 upstream commits from v6.9-rc1. + + [Test Case] + + The MP2 shall ben enabled correctly with: + + c4:00.7 MP2 I2C controller: Advanced Micro Devices, Inc. [AMD] Device + 15e6 + + [Where problems could occur] + + No. This enables MP2 on new processor families with backward support. + + [Other Info] + + While this is on v6.9-rc1 only, Noble and oem-6.8 will be nominated for + fix. + + == original bug report = + Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => Fix Released ** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058331 Title: Update amd_sfh for AMD strix series To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058333] Re: daisy chained thunderbolt devices not working at reboot on AMD strix platforms
SRU: * https://kernel.ubuntu.com/gitea/kernel/noble-linux-oem/pulls/3 (oem-6.8) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058333 Title: daisy chained thunderbolt devices not working at reboot on AMD strix platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065349] Re: [SRU] Default user created by cloud-init confuses WSLg
The attachment "Attached debdiff for wsl-setup 0.5.3 for Noble" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065349 Title: [SRU] Default user created by cloud-init confuses WSLg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2065349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056545] Re: plasma desktop freezes on wayland moving windows between displays
[Expired for kwin (Ubuntu) because there has been no activity for 60 days.] ** Changed in: kwin (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056545 Title: plasma desktop freezes on wayland moving windows between displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/2056545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056642] Re: drop down menu appears on another workspace
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056642 Title: drop down menu appears on another workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058331] Re: Update amd_sfh for AMD strix series
** Changed in: linux-oem-6.8 (Ubuntu) Assignee: AceLan Kao (acelankao) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.8 (Ubuntu Noble) Assignee: AceLan Kao (acelankao) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.8 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.8 (Ubuntu) Assignee: You-Sheng Yang (vicamo) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058331 Title: Update amd_sfh for AMD strix series To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065341] Re: Filezilla crash in upload
*** This bug is a duplicate of bug 2061954 *** https://bugs.launchpad.net/bugs/2061954 ** This bug has been marked a duplicate of bug 2061954 filezilla crashed with SIGABRT in start_thread() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065341 Title: Filezilla crash in upload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/filezilla/+bug/2065341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056686] Re: Wishlist - Backport AMD pstate support for Threadripper 3000 series CPUs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056686 Title: Wishlist - Backport AMD pstate support for Threadripper 3000 series CPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2032754] Autopkgtest regression report (containerd-app/1.7.12-0ubuntu2~22.04.1)
All autopkgtests for the newly accepted containerd-app (1.7.12-0ubuntu2~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: docker.io-app/24.0.5-0ubuntu1~22.04.1 (ppc64el) docker.io-app/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#containerd-app [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2032754 Title: FTBFS with golang-1.21: TestGenerateApparmorSpecOpts fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2032754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056154] Autopkgtest regression report (containerd-app/1.7.12-0ubuntu2~22.04.1)
All autopkgtests for the newly accepted containerd-app (1.7.12-0ubuntu2~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: docker.io-app/24.0.5-0ubuntu1~22.04.1 (ppc64el) docker.io-app/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#containerd-app [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056154 Title: Please build with golang-1.21 or golang-1.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2056154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Autopkgtest regression report (containerd-app/1.7.12-0ubuntu2~22.04.1)
All autopkgtests for the newly accepted containerd-app (1.7.12-0ubuntu2~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: docker.io-app/24.0.5-0ubuntu1~22.04.1 (ppc64el) docker.io-app/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#containerd-app [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058333] Re: daisy chained thunderbolt devices not working at reboot on AMD strix platforms
** Description changed: + [SRU Justification] + + [Impact] + + Devices on PCIe bus on some AMD based systems may not function normally. + + Boot firmware (typically BIOS) might have created tunnels of its own. + The tunnel configuration that it does might be sub-optimal. For instance + it may only support HBR2 monitors so the DisplayPort tunnels it created + may limit Linux graphics drivers. In addition there is an issue on some + AMD based systems where the BIOS does not allocate enough PCIe resources + for future topology extension. + + [Fix] + + 4 commits already in upstream linux repo that resets USB4 v1 routers in + addition to already reset v2 routes to align the behavior with Windows + Connection Manager. + + [Test Case] + + On affected platforms with monitor connected across reboots, the DUT + reboots into linux with blank screen. This should turn it back to normal + as expected. + + [Where problems could occur] + + No. The reset triggers Linux to re-allocate necessary resources for its + own, and this is what Windows does, too. + + [Other Info] + + While this is in v6.9-rc1 and backported to stable at v6.8.8, Noble and + oem-6.8 are nominated. + + == original but report == + Boot firmware (typically BIOS) might have created tunnels of its own. The tunnel configuration that it does might be sub-optimal. For instance it may only support HBR2 monitors so the DisplayPort tunnels it created may limit Linux graphics drivers. In addition there is an issue on some AMD based systems where the BIOS does not allocate enough PCIe resources for future topology extension. By resetting the USB4 topology the PCIe links will be reset as well allowing Linux to re-allocate. This aligns the behavior with Windows Connection Manager. Fixes merged to linus tree for v6.9-rc1: * 59a54c5f3dbde thunderbolt: Reset topology created by the boot firmware * ec8162b3f0683 thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4 routers * b35c1d7b11da8 thunderbolt: Introduce tb_path_deactivate_hop() * 01da6b99d49f6 thunderbolt: Introduce tb_port_reset() ** Changed in: linux-oem-6.8 (Ubuntu) Status: New => Invalid ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-oem-6.8 (Ubuntu) Assignee: Anthony Wong (anthonywong) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.8 (Ubuntu Noble) Assignee: Anthony Wong (anthonywong) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.8 (Ubuntu) Assignee: You-Sheng Yang (vicamo) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058333 Title: daisy chained thunderbolt devices not working at reboot on AMD strix platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065361] Re: Create a vanilla Ubuntu flavour without snaps like Debian
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065361 Title: Create a vanilla Ubuntu flavour without snaps like Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2065361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065361] [NEW] Create a vanilla Ubuntu flavour without snaps like Debian
Public bug reported: [CURRENT CASE] Currently users dont have the choice anymore to install Ubuntu desktop without snaps installed by default part of the system. [WISHLIST] Create a vanilla Ubuntu flavour that acts like a vanilla Debian without snaps where users can choose on their own what to install on this solid clean base. [ADVANTAGES] Users can use the vanilla Ubuntu desktop as a swiss knife and install whatever they like afterwards. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065361 Title: Create a vanilla Ubuntu flavour without snaps like Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2065361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065359] [NEW] [BPO] lsp-plugins/1.2.15-2 from ocular to noble
Public bug reported: [Impact] lsp-plugins 1.2.15 was released shortly after Noble Numbat's feature freeze and includes some features that would not justify an SRU, namely: * Experimental VST-3 Plugin Support * Added built-in presets for Compressor plugin series. among other new features. [Scope] * Backport lsp-plugins 1.2.15-2 from ocular (dev series) * Backport to 24.04 (Noble Numbat) [Other Information) Reverse dependencies: * NONE Reverse recommends: * EasyEffects: EasyEffects functionality is merely enhanced by lsp- plugins and no adverse effects by a newer version are foreseen. Furthermore, no changes to the internal MIDI Input/Output of the plugins, on which EasyEffects uses them, have changed, therefore justifying no impact. Maintenance: * Further backports of lsp-plugins will be provided by myself to noble with newer versions in the devel branch as they come. Successfully built in https://launchpad.net/~ubuntustudio- ppa/+archive/ubuntu/backports-staging ** Affects: lsp-plugins (Ubuntu) Importance: Undecided Status: Invalid ** Affects: lsp-plugins (Ubuntu Noble) Importance: Undecided Assignee: Erich Eickmeyer (eeickmeyer) Status: New ** Also affects: lsp-plugins (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: lsp-plugins (Ubuntu Noble) Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) ** Changed in: lsp-plugins (Ubuntu) Assignee: Erich Eickmeyer (eeickmeyer) => (unassigned) ** Changed in: lsp-plugins (Ubuntu) Status: New => Invalid ** Description changed: [Impact] lsp-plugins 1.2.15 was released shortly after Noble Numbat's feature freeze and includes some features that would not justify an SRU, namely: - * Experimental VST-3 Plugin Support - * Added built-in presets for Compressor plugin series. + * Experimental VST-3 Plugin Support + * Added built-in presets for Compressor plugin series. among other new features. [Scope] - * Backport lsp-plugins 1.2.15-2 from ocular (dev series) - * Backport to 24.04 (Noble Numbat) + * Backport lsp-plugins 1.2.15-2 from ocular (dev series) + * Backport to 24.04 (Noble Numbat) [Other Information) Reverse dependencies: - * NONE + * NONE Reverse recommends: - * EasyEffects: EasyEffects functionality is merely enhanced by lsp- + * EasyEffects: EasyEffects functionality is merely enhanced by lsp- plugins and no adverse effects by a newer version are foreseen. Furthermore, no changes to the internal MIDI Input/Output of the plugins, on which EasyEffects uses them, have changed, therefore justifying no impact. Maintenance: - * Further backports of lsp-plugins will be provided by myself to noble + * Further backports of lsp-plugins will be provided by myself to noble with newer versions in the devel branch as they come. + + Successfully built in https://launchpad.net/~ubuntustudio- + ppa/+archive/ubuntu/backports-staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065359 Title: [BPO] lsp-plugins/1.2.15-2 from ocular to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsp-plugins/+bug/2065359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058622] Re: [needs-packaging] lenovo-wwan-unlock
** Attachment added: "lenovo-wwan-unlock_2.0.0.orig.tar.gz" https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+attachment/5776882/+files/lenovo-wwan-unlock_2.0.0.orig.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058622 Title: [needs-packaging] lenovo-wwan-unlock To manage notifications about this bug go to: https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058622] Re: [needs-packaging] lenovo-wwan-unlock
** Attachment added: "lenovo-wwan-unlock_2.0.0-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+attachment/5776881/+files/lenovo-wwan-unlock_2.0.0-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058622 Title: [needs-packaging] lenovo-wwan-unlock To manage notifications about this bug go to: https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058622] Re: [needs-packaging] lenovo-wwan-unlock
Hi, I packed version v2.0.0 and upload to the git repo. The files under debian folder are all created by Canonical, I think it should be no problem using GPL-3 license. ** Attachment added: "lenovo-wwan-unlock_2.0.0-0ubuntu1.dsc" https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+attachment/5776880/+files/lenovo-wwan-unlock_2.0.0-0ubuntu1.dsc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058622 Title: [needs-packaging] lenovo-wwan-unlock To manage notifications about this bug go to: https://bugs.launchpad.net/lenovo-wwan-unlock/+bug/2058622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316197] Re: cant compile version from SVN
Closing as invalid as requested. ** Changed in: font-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316197 Title: cant compile version from SVN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/font-manager/+bug/1316197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2022390] Autopkgtest regression report (runc/1.1.7-0ubuntu1~20.04.4)
All autopkgtests for the newly accepted runc (1.1.7-0ubuntu1~20.04.4) for focal have finished running. The following regressions have been reported in tests triggered by the package: golang-github-containers-psgo/unknown (armhf) golang-github-containers-storage/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#runc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2022390 Title: Keep the -dev binary package in sync with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/2022390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2032754] Autopkgtest regression report (containerd-app/1.7.12-0ubuntu2~20.04.1)
All autopkgtests for the newly accepted containerd-app (1.7.12-0ubuntu2~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: docker.io-app/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#containerd-app [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2032754 Title: FTBFS with golang-1.21: TestGenerateApparmorSpecOpts fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2032754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2022390] Autopkgtest regression report (runc/1.1.7-0ubuntu2.4)
All autopkgtests for the newly accepted runc (1.1.7-0ubuntu2.4) for mantic have finished running. The following regressions have been reported in tests triggered by the package: containerd/unknown (armhf) golang-github-containers-common/unknown (armhf) golang-github-containers-psgo/1.7.1+ds1-1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#runc [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2022390 Title: Keep the -dev binary package in sync with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/2022390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Autopkgtest regression report (docker.io-app/24.0.7-0ubuntu2~20.04.1)
All autopkgtests for the newly accepted docker.io-app (24.0.7-0ubuntu2~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: docker.io-app/24.0.7-0ubuntu2~20.04.1 (arm64) docker.io-app/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#docker.io-app [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Autopkgtest regression report (containerd-app/1.7.12-0ubuntu2~20.04.1)
All autopkgtests for the newly accepted containerd-app (1.7.12-0ubuntu2~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: docker.io-app/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#containerd-app [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056154] Autopkgtest regression report (docker.io-app/24.0.7-0ubuntu2~20.04.1)
All autopkgtests for the newly accepted docker.io-app (24.0.7-0ubuntu2~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: docker.io-app/24.0.7-0ubuntu2~20.04.1 (arm64) docker.io-app/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#docker.io-app [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056154 Title: Please build with golang-1.21 or golang-1.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2056154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056154] Autopkgtest regression report (containerd-app/1.7.12-0ubuntu2~20.04.1)
All autopkgtests for the newly accepted containerd-app (1.7.12-0ubuntu2~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: docker.io-app/unknown (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#containerd-app [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056154 Title: Please build with golang-1.21 or golang-1.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2056154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061068] Re: debsums check failed
** Changed in: ubuntu Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061068 Title: debsums check failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931470] Re: wrong icon path in desktop file
This bug was fixed in the package ltris - 1.3.1-1 --- ltris (1.3.1-1) unstable; urgency=medium * New upstream version 1.3.1 * refresh patch * fix icon (LP: #1931470) * rewrite copyright in new format * bump Standards Version to 4.6.2 after review -- Alexandre Detiste Thu, 09 May 2024 00:08:55 +0200 ** Changed in: ltris (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931470 Title: wrong icon path in desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltris/+bug/1931470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060740] Re: fsattr fails to run
This bug was fixed in the package fstransform - 0.9.4-1ubuntu1 --- fstransform (0.9.4-1ubuntu1) oracular; urgency=medium * d/control: Update build-dependency to fix error with fsattr. (LP: #2060740) -- Sudip Mukherjee Wed, 01 May 2024 20:59:02 +0100 ** Changed in: fstransform (Ubuntu Oracular) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060740 Title: fsattr fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fstransform/+bug/2060740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064976] Re: Please merge 2.11.3-4 into Oracular
This bug was fixed in the package gammaray - 2.11.3-4ubuntu1 --- gammaray (2.11.3-4ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2064976). Remaining changes: - Disable LauncherTest and ClientConnectionTest that fail on Ubuntu because of ptrace protection. gammaray (2.11.3-4) unstable; urgency=medium * Team upload. * Stop depending on qtwebengine5-dev on mipsel (closes: #1041265). gammaray (2.11.3-3) unstable; urgency=medium * Team upload. [ Adrian Bunk ] * qtwebengine5-dev is now available on mips64el. [ Dmitry Shachnev ] * Update debian/watch to use GitHub API and add signature verification. - Remove no longer needed debian/source/lintian-overrides. * Bump Standards-Version to 4.6.2, no changes needed. gammaray (2.11.3-2) unstable; urgency=medium * Team upload. * Make test failures non-fatal on ppc64el (closes: #1026932). -- Zixing Liu Mon, 06 May 2024 19:15:28 -0600 ** Changed in: gammaray (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064976 Title: Please merge 2.11.3-4 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gammaray/+bug/2064976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065082] Re: Please merge 00303-23 into Oracular
This bug was fixed in the package fonts-ipafont - 00303-23ubuntu1
---
fonts-ipafont (00303-23ubuntu1) oracular; urgency=medium
* Merge with Debian unstable (LP: #2065082). Remaining changes:
+ Remove 'strong' binding and re-add LANG guards.
+ Add fontconfig files.
fonts-ipafont (00303-23) unstable; urgency=medium
* Drop debian/watch, new upstream site structure is not fit to use
uscan.
fonts-ipafont (00303-22) unstable; urgency=medium
* debian/{control,copyright}
- Deal with upstream change with copyright assignment. IPAexfont was
assigned from Information-technology Promotion Agency, Japan (IPA)
to Japanese Character Information Technology Promotion Council (CITPC).
See https://mojikiban.ipa.go.jp/ (in Japanese)
* debian/control
- Set Standards-Version: 4.5.1
-- Zixing Liu Tue, 07 May 2024 11:08:36
-0600
** Changed in: fonts-ipafont (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/2065082
Title:
Please merge 00303-23 into Oracular
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-ipafont/+bug/2065082/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065083] Re: Please merge 00401-5 into Oracular
This bug was fixed in the package fonts-ipaexfont - 00401-5ubuntu1
---
fonts-ipaexfont (00401-5ubuntu1) oracular; urgency=medium
* Merge with Debian unstable (LP: #2065083). Remaining changes:
- Add generic name & override.
- Add fontconfig configuration file.
- Fix alias for IPAex Mincho.
fonts-ipaexfont (00401-5) unstable; urgency=medium
* debian/control
- set Standards-Version: 4.6.0
* debian/source/lintian-overrides
- fix warning
fonts-ipaexfont (00401-4.1) unstable; urgency=medium
* Non-maintainer upload.
* Ensure that /usr/share/fonts/truetype/ exists when update-alternatives
runs (Closes: #1004216)
fonts-ipaexfont (00401-4) unstable; urgency=medium
* debian/control
- Set Standards-Version: 4.5.1
* debian/{copyright,control}
- Deal with upstream change with copyright assignment. IPAexfont was
assigned from Information-technology Promotion Agency, Japan (IPA)
to Japanese Character Information Technology Promotion Council (CITPC).
See https://mojikiban.ipa.go.jp/ (in Japanese)
* debian/fonts-ipaexfont-{gothic,mincho}.{dirs,lintian-overrides}
- Drop unnecessary empty *.dirs and its lintian overrides
-- Zixing Liu Tue, 07 May 2024 11:15:16
-0600
** Changed in: fonts-ipaexfont (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/2065083
Title:
Please merge 00401-5 into Oracular
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-ipaexfont/+bug/2065083/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065107] Re: Please merge 1.1.2-1.1 into Oracular
This bug was fixed in the package hasciicam - 1.1.2-1.1ubuntu1 --- hasciicam (1.1.2-1.1ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2065107). Remaining changes: - debian/patches/10_desktop-file.patch: Fix invalid desktop file, don't include extension for icons. (LP: #1198969) - Explicitly build-depend on libftp-dev instead of old ftplib-dev hasciicam (1.1.2-1.1) unstable; urgency=low * Non-maintainer upload. * Bump debhelper compat to 9. (Closes: #965578) -- Zixing Liu Tue, 07 May 2024 15:23:23 -0600 ** Changed in: hasciicam (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065107 Title: Please merge 1.1.2-1.1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hasciicam/+bug/2065107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065228] Re: Please merge 32 into Oracular
This bug was fixed in the package lxqt-metapackages - 32ubuntu1 --- lxqt-metapackages (32ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2065228). Remaining changes: - Ensure xdg-desktop-portal-lxqt is a dependency of lxqt-core. - Add lxqt-archiver to archiver Recommends. * Dropped changes: - Remove old Breaks/Replaces since we're past the LTS. lxqt-metapackages (32) unstable; urgency=medium [ ChangZhuo Chen (陳昌倬) ] * Add lxqt-archiver as archive manager (Closes: #987082) [ Andrew Lee (李健秋) ] * debian/control: update team address. * debian/control: add myself as uploader. * debian/control: drop breaks and replaces on obsoleted version. * debian/control: use nm-tray over cmst for network. (Closes: #1035411, #971076) * debian/copyright: update * debian/salsa-ci.yml: added. lxqt-metapackages (31) unstable; urgency=medium [ Debian Janitor ] * Trim trailing whitespace. * Upgrade to newer source format 3.0 (native) (Closes: #1007054). [ ChangZhuo Chen (陳昌倬) ] * Bump Standards-Version to 4.6.2. * Bump compat to 13: * Add "Rules-Requires-Root: no" in d/control. -- Zixing Liu Wed, 08 May 2024 16:41:55 -0600 ** Changed in: lxqt-metapackages (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065228 Title: Please merge 32 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-metapackages/+bug/2065228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065117] Re: Please merge 0.0.2012-06-kde4.8-6 into Oracular
This bug was fixed in the package oxygencursors - 0.0.2012-06-kde4.8-6ubuntu1 --- oxygencursors (0.0.2012-06-kde4.8-6ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2065117). Remaining changes: - Call dh_installdirs and rename debian/dirs to oxygen-cursor-theme.dirs so it's actually used and /usr/share/icons/default/ is created. - Renamed package to oxygen-cursor-theme (standard color schemes) - Added package oxygen-cursor-theme-extra (other color schemes) - Added dh_install to debian/rules - Edit wrapperthemes.sh for multiple packages - Hardcode the list of color schemes to (un)register as x-cursor-theme. Using all installed oxygen schemes doesn't work well with the split package. - Move black, blue, yellow and zion to oxygen-cursor-theme. Those would be installed by kde-workspace. -- Zixing Liu Tue, 07 May 2024 17:13:46 -0600 ** Changed in: oxygencursors (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/2065117 Title: Please merge 0.0.2012-06-kde4.8-6 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oxygencursors/+bug/2065117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065201] Re: Please merge 1.21+nmu3 into Oracular
This bug was fixed in the package pppoeconf - 1.21+nmu3ubuntu1 --- pppoeconf (1.21+nmu3ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2065201). Remaining changes: - do not install the desktop file pppoeconf (1.21+nmu3) unstable; urgency=high * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965786) -- Zixing Liu Wed, 08 May 2024 12:16:22 -0600 ** Changed in: pppoeconf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065201 Title: Please merge 1.21+nmu3 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pppoeconf/+bug/2065201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065208] Re: Please merge 0.10.10-0.4 into Oracular
This bug was fixed in the package cachefilesd - 0.10.10-0.4ubuntu1 --- cachefilesd (0.10.10-0.4ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2065208). Remaining changes: - Avoid counter underflow, leading to segfault (LP #1854054) cachefilesd (0.10.10-0.4) unstable; urgency=medium * Non-maintainer upload. * Install cachefilesd into /usr/sbin instead of /sbin (Closes: #1056909) cachefilesd (0.10.10-0.3) unstable; urgency=medium * Trim trailing whitespace. * Use secure copyright file specification URI. * Use secure URI in debian/watch. * Explicitly specify source format. * Bump debhelper from deprecated 7 to 10. * Fix field name typos in debian/copyright. -- Zixing Liu Wed, 08 May 2024 13:23:44 -0600 ** Changed in: cachefilesd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065208 Title: Please merge 0.10.10-0.4 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cachefilesd/+bug/2065208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065214] Re: Please merge 1.4.3-8 into Oracular
This bug was fixed in the package cfingerd - 1.4.3-8ubuntu1
---
cfingerd (1.4.3-8ubuntu1) oracular; urgency=medium
* Merge with Debian unstable (LP: #2065214). Remaining changes:
- debian/control: Add openbsd-inetd | inet-superserver dependencies,
as cfingerd needs an inet server to work.
cfingerd (1.4.3-8) unstable; urgency=medium
* QA upload.
* debian/control: Bump Standards-Version to 4.6.2.
* debian/rules: Also explicitly clean debian/.debhelper directory
after build. (Closes: #1043925)
cfingerd (1.4.3-7) unstable; urgency=medium
* QA upload.
* debian/rules: Add build-{arch,indep}. (Closes: #999167)
cfingerd (1.4.3-6) unstable; urgency=medium
* QA upload.
[ Debian Janitor ]
* Remove constraints unnecessary since buster:
+ cfingerd: Drop versioned constraint on netbase in Depends.
-- Zixing Liu Wed, 08 May 2024 14:24:29
-0600
** Changed in: cfingerd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065214
Title:
Please merge 1.4.3-8 into Oracular
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cfingerd/+bug/2065214/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065216] Re: Please merge 3.22.0-8.1 into Oracular
This bug was fixed in the package vinagre - 3.22.0-8.1ubuntu1 --- vinagre (3.22.0-8.1ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2065216). Remaining changes: * Fix compatibility with FreeRDP 2.1.1 security update. - debian/patches/freerdp*.patch: backport series of upstream patches to fix compatibility wither newer FreeRDP versions. - d/p/0001-Revert-Improve-FreeRDP-authentication-failure-handli.patch: removed, no longer needed. - d/p/0002-Revert-Store-credentials-for-RDP.patch: removed, no longer needed. - d/p/freerdp2017.patch: removed, replaced with upstream patches. * New Changes: - d/patches: re-import patches from the upstream and refresh the patches against the Ubuntu-patched source tree. vinagre (3.22.0-8.1) unstable; urgency=medium * Non-maintainer upload. * debian/patches: + Add 0003-fix-hangs-with-recent-FreeRDP-version.patch and 0004-fix-FreeRDP-API-usage.patch. This resolves vinagre hanging endlessly with a black screen when connecting to a remote RDP server (Closes: #983533). -- Zixing Liu Wed, 08 May 2024 15:11:43 -0600 ** Changed in: vinagre (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065216 Title: Please merge 3.22.0-8.1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/2065216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065200] Re: Please merge 1:1.2.0-2.5 into Oracular
This bug was fixed in the package nagios-plugins-rabbitmq - 1:1.2.0-2.5ubuntu1 --- nagios-plugins-rabbitmq (1:1.2.0-2.5ubuntu1) oracular; urgency=medium * Merge with Debian unstable (LP: #2065200). Remaining changes: - Avoid breaking to get stats from an idle server that has no socket descriptors open (LP: #1787110) * New Changes: - d/p/get-stats-from-idle-server.patch: move the code changes to a patch after the package switched to 3.0 format nagios-plugins-rabbitmq (1:1.2.0-2.5) unstable; urgency=medium * Non-maintainer upload. * Convert to source format 3.0. (closes: #1043216) nagios-plugins-rabbitmq (1:1.2.0-2.4) unstable; urgency=medium * Non-maintainer upload. * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. - Closes: #965742 nagios-plugins-rabbitmq (1:1.2.0-2.3) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. * No source change upload to rebuild on buildd with .buildinfo files. -- Zixing Liu Wed, 08 May 2024 12:00:31 -0600 ** Changed in: nagios-plugins-rabbitmq (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065200 Title: Please merge 1:1.2.0-2.5 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-plugins-rabbitmq/+bug/2065200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064291] Re: Ubuntu 24.04 crashed multiple times
Thank You for your assistance on this bug report. Removing the Ubuntu from virtual box. Closing this bug report. ** Changed in: linux (Ubuntu) Status: New => Invalid ** Summary changed: - Ubuntu 24.04 crashed multiple times + [closed] Ubuntu 24.04 crashed multiple times -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064291 Title: [closed] Ubuntu 24.04 crashed multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063399] Re: Add support for Quectel EM160R-GL modem [1eac:100d]
Tested on a ThinkPad that has Quectel EM160R-GL modem [1eac:100d], works fine. ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 ** Changed in: oem-priority Status: Confirmed => Fix Released ** Changed in: hwe-next Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063399 Title: Add support for Quectel EM160R-GL modem [1eac:100d] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063529] Re: Add support for Quectel RM520N-GL modem [1eac:1007]
Tested on a ThinkPad that has Quectel RM520N-GL modem [1eac:1007], works fine. ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 ** Changed in: oem-priority Status: Confirmed => Fix Released ** Changed in: hwe-next Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063529 Title: Add support for Quectel RM520N-GL modem [1eac:1007] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065349] Re: [SRU] Default user created by cloud-init confuses WSLg
** Patch added: "Attached debdiff for wsl-setup 0.5.3 for Noble" https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2065349/+attachment/5776855/+files/wsl-setup_0.5.3~24.04.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065349 Title: [SRU] Default user created by cloud-init confuses WSLg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2065349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065352] [NEW] when getting file properties of an audio file twice, file-manager freezes
Public bug reported: If I want to get the properties (alt+enter) of an audio file (e.g. mp3) the second time (even if it is a file with the same name in other directory), the file-manager freezes. It does not happen with other file types. 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: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 10 03:34:36 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-05-02 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: If I want the to get the properties (alt+enter) of an audio file (e.g. - mp3) the second time the file with the same name (even in other - directory) the filemanager freezes. It does not happen with other file - types. + mp3) the second time I want the properties of a file with the same name + (even in other directory) the file-manager freezes. It does not happen + with other file types. 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: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 10 03:34:36 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-05-02 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Description changed: - If I want the to get the properties (alt+enter) of an audio file (e.g. - mp3) the second time I want the properties of a file with the same name - (even in other directory) the file-manager freezes. It does not happen - with other file types. + If I want to get the properties (alt+enter) of an audio file (e.g. mp3) + the second time (even if it is a file with the same name in other + directory), the file-manager freezes. It does not happen with other file + types. 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: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 10 03:34:36 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-05-02 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Summary changed: - when getting file properties of an audio file twice, filemanger freezes + when getting file properties of an audio file twice, file-manger freezes ** Summary changed: - when getting file properties of an audio file twice, file-manger freezes + when getting file properties of an audio file twice, file-manager freezes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065352 Title: when getting file properties of an audio file twice, file-manager freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2065352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065265] Re: can not build linux-image-signed.deb
Hi Light_Kernel_Ops, The linux-signed package is signed with Canonical's Secure Boot Signing Key, making the kernel bootable on systems that have secure boot enabled. This key is not public for obvious reasons, and only particular Kernel team members have access to it. Where do you want to publish your kernel? Is it for regular users, does it contain a particular fix you are needing, or is it for a specific IOT hardware device? If you have your own fleet of company laptops for example, you can enroll your own secure boot key into their MOKs, and sign the built kernel with that. Let me know what you are trying to achieve, and I will see if I can help. Thanks, Matthew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065265 Title: can not build linux-image-signed.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065349] [NEW] [SRU] Default user created by cloud-init confuses WSLg
Public bug reported: [Context] wsl-setup is a package to carry pieces of configuration specifically implemented for a better experience with Ubuntu WSL. A bug reported originally by Microsoft engineers, made public via https://github.com/ubuntu/WSL/issues/468, **prevents any GUI application relying on Wayland to start**. The issue happens when cloud-init creates a default user ahead of the user's request, which can happen whenever users don't supply any user-data. WSL graphical subsystem (WSLg) expects the default user to be UID 1000, which, being taken by cloud-init, causes the subsystem to mess with runtime dir permissions. The fix was implemented in https://github.com/ubuntu/wsl-setup/pull/12 and made available in wsl-setup v0.5.3, by adding a configuration override to prevent cloud-init from creating the default "ubuntu" user. [Impact] * Only WSL users creating new instances of Ubuntu 24.04 LTS are subject to cloud-init effects. * Currently users affected by this bug are considered early-adopters. A much wider audience is expected with the release of 24.04.1. * wsl-setup is exclusive to Ubuntu WSL, so no other Ubuntu product or experience is affected. [Test plan] * Install the most recent version of Ubuntu 24.04 LTS application from MS Store with the latest wsl-setup already seeded. * Start the application on a Windows console: `ubuntu2404.exe`. * When prompted create the default user and password via the regular WSL launcher workflow. * When the setup is complete and bash is shown install the `gtk-4-examples` package with: `sudo apt update && sudo apt install -y gtk-4-examples`. * When installation is complete, run the gtk4-demo application with the default backend and ensure it opens correctly: `gtk4-demo`. * Close it and relaunch it with the GDK backend set to "wayland": `GDK_BACKEND=wayland gtk4-demo`. Assert that the application opens as before. [Where problems could occur] * Users familiar with cloud-init on Ubuntu might expect the creation of the `ubuntu` user, as it happens with clouds and LXD containers. [Other Info] * Cloud-init support on WSL is recent enough so users should not have had enough time to create expectations about such behavior by the time this SRU is finished. * A similar test workflow was proposed to ISO Tracker test case for Ubuntu WSL to check that behavior. Merge proposal: https://code.launchpad.net/~cnihelton/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/465894 ** Affects: wsl-setup (Ubuntu) Importance: Undecided Status: New ** Description changed: - wsl-setup is a package to carry pieces of confuguration specifically - implemented for a better experience with Ubuntu WSL. + [Context] + wsl-setup is a package to carry pieces of configuration specifically implemented for a better experience with Ubuntu WSL. - A bug reported originally by Microsoft engineers, made public via - https://github.com/ubuntu/WSL/issues/468, prevents any GUI application - relying on Wayland to start. The fix was implemented in - https://github.com/ubuntu/wsl-setup/pull/12 and made available in wsl- - setup v0.5.3, by adding a configuration override to prevent cloud-init - from creating the default "ubuntu" user, which confused the WSL - graphical subsystem (WSLg). + A bug reported originally by Microsoft engineers, made public via https://github.com/ubuntu/WSL/issues/468, **prevents any GUI application relying on Wayland to start**. + The issue happens when cloud-init creates a default user ahead of the user's request, which can happen whenever users don't supply any user-data. + WSL graphical subsystem (WSLg) expects the default user to be UID 1000, which, being taken by cloud-init, causes the subsystem to mess with runtime dir permissions. + The fix was implemented in https://github.com/ubuntu/wsl-setup/pull/12 and made available in wsl-setup v0.5.3, by adding a configuration override to prevent cloud-init from creating the default "ubuntu" user. [Impact] * Only WSL users creating new instances of Ubuntu 24.04 LTS are subject to cloud-init effects. * Currently users affected by this bug are considered early-adopters. A much wider audience is expected with the release of 24.04.1. * wsl-setup is exclusive to Ubuntu WSL, so no other Ubuntu product or experience is affected. [Test plan] * Install the most recent version of Ubuntu 24.04 LTS application from MS Store with the latest wsl-setup already seeded. * Start the application on a Windows console: `ubuntu2404.exe`. * When prompted create the default user and password via the regular WSL launcher workflow. * When the setup is complete and bash is shown install the `gtk-4-examples` package with: `sudo apt update && sudo apt install -y gtk-4-examples`. * When installation is complete, run the gtk4-demo application with the default backend and ensure it opens correctly: `gtk4-demo`. - * Close it and relaunch it with the GDK backend set to wayland:
[Bug 2065348] [NEW] python3-docker `from_env()` broken
Public bug reported: I have a python script that manages some docker resources. It uses the `from_env()` method to build the client. This script always runs as root. This worked in Ubuntu 22.04. However, it seems like something is mismatched in 24.04, as I now get the following error, even after a reboot (which seemed to solve this for others in the past?). It appears based on cursory googling that a library version might be out of sync. ``` Traceback (most recent call last): File "/usr/bin/oqm-captain", line 62, in ContainerUtils.ensureSharedDockerResources() File "/usr/lib/oqm/station-captain/ContainerUtils.py", line 55, in ensureSharedDockerResources client = docker.from_env() ^ File "/usr/lib/python3/dist-packages/docker/client.py", line 96, in from_env return cls( File "/usr/lib/python3/dist-packages/docker/client.py", line 45, in __init__ self.api = APIClient(*args, **kwargs) ^^ File "/usr/lib/python3/dist-packages/docker/api/client.py", line 197, in __init__ self._version = self._retrieve_server_version() ^^^ File "/usr/lib/python3/dist-packages/docker/api/client.py", line 221, in _retrieve_server_version raise DockerException( docker.errors.DockerException: Error while fetching server API version: HTTPConnection.request() got an unexpected keyword argument 'chunked' ``` This is on a fresh 24.04 install. Willing to help diagnose, but to replicate: 1. `apt install docker.io python3-docker` 2. `python3` 3. `import docker` 4. `docker.from_env()` ** Affects: python-docker (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/2065348 Title: python3-docker `from_env()` broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-docker/+bug/2065348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@jorge-lavila: technically possible yes. I want to be careful with what I promise here, as the user experience is not my area. With that said we are currently looking at using aa-notify as a bridge to improve the user experience. We would install it with a filter to only fire a notification for the user namespace denial/transition. That notification will show in your desktops notification area with a button/click action that will launch a user prompt. There will have to be an SRU to add some of the new functionality, but we can make it available before the SRU via a ppa for those who want to test. I will make sure to update this bug when we have this ready for testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046609] Re: sync request: netatalk 3.1.18~ds-1 Debian sid main
There is a netatalk metadata corruption issue in both 20.04 and 22.04
that is described here:
https://github.com/Netatalk/netatalk/issues/236
It would be nice to get this fixed in 22.04 at least, it is spewing
errors in my logs.
May 9 20:49:41 thunder afpd[3539543]: ad_header_read_ea("/datc/time-
machine-2018/."): invalid metadata EA this is now being treated as a
fatal error. if you see this log entry, please file a bug ticket with
your upstream vendor and attach the generated core file.
Debian 3.1.18~ds1 may fix this issue if you could backport it.
** Bug watch added: github.com/Netatalk/netatalk/issues #236
https://github.com/Netatalk/netatalk/issues/236
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2046609
Title:
sync request: netatalk 3.1.18~ds-1 Debian sid main
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netatalk/+bug/2046609/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054395] Re: [sru] sos upstream 4.7.0
Thanks, Arif. Thanks for fixing the typo in the focal changelog. For oracular, I see 2 new patches for cirrus (I see one of them is also present for noble). Why are we patching that file at all? AFAIU, it is a file parsed by the CI, and it is not even sipped in the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054395 Title: [sru] sos upstream 4.7.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065345] Re: Locked Screen Won't Unlock With Key Press
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065345 Title: Locked Screen Won't Unlock With Key Press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2065345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064953] Re: [needs-packaging] [needs-upgrade] nvidia-graphics-drivers-390 to version 390.157
Good luck with that. They purposely removed the Nvidia 390 driver during the previous Ubuntu (23.10) cycle: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-390/+bug/2035189/ I've tried packaging 390 for Noble, but it seems broken. The package installs correctly and builds the kernel modules, but XServer won't start. Another person also has a PPA with 390 noble package that does the same thing https://launchpad.net/~dtl131/+archive/ubuntu/nv390test https://launchpad.net/~kelebek333/+archive/ubuntu/nvidia-legacy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064953 Title: [needs-packaging] [needs-upgrade] nvidia-graphics-drivers-390 to version 390.157 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2064953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1994521] Re: HPE3PAR: Failing to clone a volume having children
I'm trying to verify this with 3par simulator. but struggling with setting up. I'll update if there is any news. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1994521 Title: HPE3PAR: Failing to clone a volume having children To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1994521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063096] Re: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle
** Tags removed: verification-needed-jammy-linux verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063096 Title: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Thanks for the detailed reply @jjohansen, Do you think it would be feasible to spawn a pop-up that says something like "This application uses namespaces which is considered vulnerable to exploits, are you sure you want to continue?" and ask for the password to allow the application to run. This would resolve the issue while still allowing portable applications to run properly. This could be achieved for example providing a tool to ask apparmor for permissions. From my side I can just detect if apparmor is used and ask apparmor to grant access to namespaces, in term, apparmor would spawn a pop-up for the user saying that my application is requesting this permission. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064638] Re: Gimp crashed when exporting to .jpg
*** This bug is a duplicate of bug 2055044 *** https://bugs.launchpad.net/bugs/2055044 ** This bug has been marked a duplicate of bug 2055044 GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064638 Title: Gimp crashed when exporting to .jpg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2064638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065177] Re: Gimp crashed when exporting to .png
*** This bug is a duplicate of bug 2055044 *** https://bugs.launchpad.net/bugs/2055044 ** This bug has been marked a duplicate of bug 2055044 GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065177 Title: Gimp crashed when exporting to .png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2065177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
Same for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@zgraft: I have added a tor item, a profile will land in an update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
@jorge-lavila, Its not a theoretical case, they have been used by multiple exploits every year (including this one) since landing in the kernel. Ubuntu is not the only ones looking at restricting them. SELinux has also picked up the ability but they haven't really rolled it out in policy, there are also discussions in other security forms (eg. the OSS security list) about how to disable them better than the giant sysctl that turns them off for everything. The apparmor solution allows doing it on a per application basis. Yes it deliberately requires a privileged operation, otherwise the restriction could be trivially by-passed by exploit code. We know the experience is not user friendly atm, and are working on improving it. Improving both the flexibility on what is mediated on how the user can by-pass/disable the restriction. On the GUI side the end goal is something similar to what you get on MacOS where the user gets notified, and has to go to the security center to enable running an untrusted application. There is in fact a profile coming for bwrap, and unshare, but not the unconfined profile that is being generically used to disable the restriction. The profile will restrict certain modes of operation, and prevent applications launch by it from having privilege within the user namespace. It will open the ubuntu shipped versions up for regular users again for many of its use cases. Unfortunately untrusted code, which is the case of code downloaded into the home dir, will require a privileged operation to be able to use user namespaces. That could be the use of sudo when using the application, or creating a profile for the application, which then allows the user to subsequently use the application without a privileged operation. ** Also affects: tor (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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
Hi! Just now I made a screencast: https://drive.google.com/file/d/1PaonPodD_v27OCFeE5m6t7PO7OM1ial0/view?usp=drive_link Operating System: Ubuntu Studio 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-31-lowlatency (64-bit) Graphics Platform: X11 On Thu, May 9, 2024 at 6:15 PM wgroiss <2055...@bugs.launchpad.net> wrote: > I have now gimp package 2.10.36-3build3 > > and i have done this 4 steps: > > + 1. Install GIMP on Ubuntu 24.04. > + 2. Create a blank image and draw a black squiggly line in it. > + 3. Export it as a PNG. > + 4. Close GIMP, and click "Discard" when prompted if you want to save > your changes. > > Gimp does not crash anymore. It closes without failure. Thanks! > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2064962). > https://bugs.launchpad.net/bugs/2055044 > > Title: > GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) > > Status in The Gimp: > Fix Released > Status in gimp package in Ubuntu: > Fix Committed > Status in gimp source package in Noble: > Fix Committed > Status in gimp source package in Oracular: > Fix Committed > > Bug description: > [ Impact ] > > GIMP is crashing when closed on Ubuntu 24.04 only. This seems to > happen if an unsaved image is present, popping up the dialog asking if > you want to save your changes. If you click "Discard", GIMP crashes. > This isn't too critical for data safety, but it is a serious papercut > and can result in data loss in certain edge cases according to the > upstream bug report in GIMP. > > There is already a one-line patch available that solves the problem: > > https://gitlab.gnome.org/GNOME/gimp/-/merge_requests/1442/diffs?commit_id=d7228727d7a4b11909001cf8fd8977d68bd29720 > This has been merged upstream. > > [ Test Plan ] > > 1. Install GIMP on Ubuntu 24.04. > 2. Create a blank image and draw a black squiggly line in it. > 3. Export it as a PNG. > 4. Close GIMP, and click "Discard" when prompted if you want to save > your changes. > 5. Observe crash. > 6. Install a patched GIMP that has the previously linked patch applied. > 7. Repeat steps 1-4 and ensure that GIMP does not crash and that the > image is saved properly. > > [ Where problems could occur ] > > The patch changes the behavior of signal handlers, meaning that a > difference between upstream GIMP and Ubuntu's GIMP could potentially > result in the patch being incompatible and causing similar or worse > crashing issues. The above test plan will likely catch such issues. > > -- > > Original bug report: > > Hello. > > I report a bug or supposed to be a bug concerning GIMP. I had worked > with GIMP without pb. > > When closing the GIMP session, I got a crash (Refer to reported info > below). > > My configuration is Kubuntu 24.04 (Dev) Noble updated daily. > > I remain available to provide further information. > Thanks to you for your support. Regards. Xavier > > > > ``` > GNU Image Manipulation Program version 2.10.36 > git-describe: GIMP_2_10_36 > Build: unknown rev 0 for linux > # C compiler # >Using built-in specs. >COLLECT_GCC=gcc >COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper >OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa >OFFLOAD_TARGET_DEFAULT=1 >Target: x86_64-linux-gnu >Configured with: ../src/configure -v --with-pkgversion='Ubuntu > 13.2.0-7ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs > --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr > --with-gcc-major-version-only --program-suffix=-13 > --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id > --libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix > --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes > --with-default-libstdcxx-abi=new --enable-gnu-unique-object > --disable-vtable-verify --enable-plugin --enable-default-pie > --with-system-zlib --enable-libphobos-checking=release > --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch > --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 > --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic > --enable-offload-targets=nvptx-none=/build/gcc-13-p2aSDx/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-p2aSDx/gcc-13-13.2.0/debian/tmp-gcn/usr > --enable-offload-defaulted --without-cuda-driver --enable-checking=release > --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu > --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 >Thread model: posix >Supported LTO compression algorithms: zlib zstd >gcc version 13.2.0 (Ubuntu 13.2.0-7ubuntu1) > > # Libraries # > using babl version 0.1.108 (compiled against version 0.1.106) > using GEGL
[Bug 2032754] Please test proposed package
Hello Shengjing, or anyone else affected, Accepted containerd-app into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd- app/1.7.12-0ubuntu2~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2032754 Title: FTBFS with golang-1.21: TestGenerateApparmorSpecOpts fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2032754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2032754] Re: FTBFS with golang-1.21: TestGenerateApparmorSpecOpts fails
Hello Shengjing, or anyone else affected, Accepted containerd-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd- app/1.7.12-0ubuntu2~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: containerd-app (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy ** Changed in: containerd-app (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2032754 Title: FTBFS with golang-1.21: TestGenerateApparmorSpecOpts fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2032754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Please test proposed package
Hello Bryce, or anyone else affected, Accepted containerd-app into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd- app/1.7.12-0ubuntu2~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Please test proposed package
Hello Bryce, or anyone else affected, Accepted containerd-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd- app/1.7.12-0ubuntu2~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: containerd-app (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Re: MRE updates of container-stack for noble
Hello Bryce, or anyone else affected, Accepted containerd-app into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd- app/1.7.12-0ubuntu2~23.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: containerd-app (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: containerd-app (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056154] Please test proposed package
Hello Shengjing, or anyone else affected, Accepted containerd-app into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd- app/1.7.12-0ubuntu2~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056154 Title: Please build with golang-1.21 or golang-1.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2056154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056154] Please test proposed package
Hello Shengjing, or anyone else affected, Accepted containerd-app into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd- app/1.7.12-0ubuntu2~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: containerd-app (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056154 Title: Please build with golang-1.21 or golang-1.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2056154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056154] Re: Please build with golang-1.21 or golang-1.22
Hello Shengjing, or anyone else affected, Accepted containerd-app into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/containerd- app/1.7.12-0ubuntu2~23.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: containerd-app (Ubuntu Mantic) Status: New => Fix Committed ** Changed in: containerd-app (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056154 Title: Please build with golang-1.21 or golang-1.22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2056154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065347] [NEW] Please merge nm-tray 0.5.0-2 into Oracular
Public bug reported: tracking bug for the merge ** Affects: nm-tray (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/2065347 Title: Please merge nm-tray 0.5.0-2 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nm-tray/+bug/2065347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065346] [NEW] nmtui and nmcli doesn't read wifi password from config files
Public bug reported: When using KDE Network Manager I can connect to wifi networks without problems. The problem appears when I want to connect to saved networks by tools like nmtui and nmcli. Both these tools can see saved networks but when I want to connect to these networks nmtui asks for a password and nmcli displays an error that the password isn't in config files. How to reproduce this problem: 1. Add network in Network Manager by GUI (KDE or Gnome). 2. Switch to virtual console (ctrl+alt+fx) 3. Use nmtui to connect to the saved network or use nmcli connection up command. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31.1-lowlatency 6.8.1 Uname: Linux 6.8.0-31-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu May 9 23:42:18 2024 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-05-04 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2024-03-17T12:22:48.566988 mtime.conffile..etc.default.apport: 2018-10-22T20:30:51 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.46.0 connected started full enabled enabled enabled missing disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065346 Title: nmtui and nmcli doesn't read wifi password from config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2065346/+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 2065345] [NEW] Locked Screen Won't Unlock With Key Press
Public bug reported: When the screen locks on its own, on-screen instructions say to click or enter a key to unlock screen. All previous versions of Ubuntu allow me to start typing my password and the password box would appear and populate as I was typing. After installing Ubuntu 24.04 I now have to click the mouse to bring up the password screen, then type my password. If I manually lock the screen the keyboard input works as expected - I can simply start typing my password to log in. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 9 17:41:31 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 1660 SUPER] [1462:c75a] InstallationDate: Installed on 2024-04-25 (14 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: ASUS System Product Name ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=b6b63c18-3c5b-415e-891d-6379fd80439b ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 14.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-V WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd09/08/2023:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-VWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065345 Title: Locked Screen Won't Unlock With Key Press To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2065345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2009071] Re: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all
Hi there, you got the device number wrong, this is the script that works for me https://pastebin.com/jT1rzQUj -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2009071 Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Re: MRE updates of container-stack for noble
Hello Bryce, or anyone else affected, Accepted docker-buildx into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker- buildx/0.12.1-0ubuntu1~23.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker-buildx (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: docker-buildx (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Please test proposed package
Hello Bryce, or anyone else affected, Accepted docker-buildx into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker- buildx/0.12.1-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Please test proposed package
Hello Bryce, or anyone else affected, Accepted docker-buildx into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker- buildx/0.12.1-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker-buildx (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Please test proposed package
Hello Bryce, or anyone else affected, Accepted docker-compose-v2 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker- compose-v2/2.24.6+ds1-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Re: MRE updates of container-stack for noble
Hello Bryce, or anyone else affected, Accepted docker-compose-v2 into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker- compose-v2/2.24.6+ds1-0ubuntu1~23.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker-compose-v2 (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: docker-compose-v2 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040460] Please test proposed package
Hello Bryce, or anyone else affected, Accepted docker-compose-v2 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker- compose-v2/2.24.6+ds1-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: docker-compose-v2 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040460 Title: MRE updates of container-stack for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd-app/+bug/2040460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065139] Re: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2: nvidia kernel module failed to build
https://forums.developer.nvidia.com/t/linux-6-7-3-545-29-06-550-40-07-error- modpost-gpl-incompatible-module-nvidia-ko-uses-gpl-only-symbol-rcu-read- lock/280908?page=2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065139 Title: nvidia-dkms-545 545.29.06-0ubuntu0.22.04.2: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2065139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065275] Re: package linux-image-5.15.0-106-generic 5.15.0-106.116 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 Thank you for taking the time to report this bug and helping to make Ubuntu better. The relevant dpkg terminal log says: cp: error writing '/var/tmp/mkinitramfs_78x5tX//usr/lib/modules/5.15.0-106-generic/kernel/drivers/scsi/isci/isci.ko': No space left on device Oder auf Deutsch: Kein Platz mehr frei auf dem Gerät. So generating the initramfs fails because your / partition is full. Please cleanup your root partition and try again. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065275 Title: package linux-image-5.15.0-106-generic 5.15.0-106.116 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065037] Re: dhcpcd is called before interfaces have carrier causing a 29 seconds boot delay
For the black screen, can you open a separate bug report and document what graphic card you use on that machine and what driver is used on the running system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065037 Title: dhcpcd is called before interfaces have carrier causing a 29 seconds boot delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065037] Re: dhcpcd is called before interfaces have carrier causing a 29 seconds boot delay
For the black screen, can you open a separate bug report and document what graphic card you use on that machine and what driver is used on the running system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065037 Title: dhcpcd is called before interfaces have carrier causing a 29 seconds boot delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2065037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064926] Re: dhcpcd stuck for 5 Minutes (300 Seconds) during Boot Process (LUKS/Clevis Autounlock)
Yes, I edited the bug description to add the SRU bug sections. There is no automation for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064926 Title: dhcpcd stuck for 5 Minutes (300 Seconds) during Boot Process (LUKS/Clevis Autounlock) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcpcd/+bug/2064926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064530] Comment bridged from LTC Bugzilla
--- Comment From jan...@us.ibm.com 2024-05-09 17:13 EDT--- Was able to successfully validate the bootstrapped dotnet8 package . Here are a few of the tests that were run: $ uname -a Linux ltcden12-lp22 6.8.0-31-generic #31-Ubuntu SMP Sat Apr 20 00:05:55 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux foo@ltcden12-lp22:~/HelloWorld$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.04 LTS Release:24.04 Codename: noble $ apt list --installed | grep dotnet WARNING: apt does not have a stable CLI interface. Use with caution in scripts. dotnet-apphost-pack-8.0/noble,now 8.0.4-0ubuntu2~ppa4 ppc64el [installed,automatic] dotnet-host-8.0/noble,now 8.0.4-0ubuntu2~ppa4 ppc64el [installed,automatic] dotnet-hostfxr-8.0/noble,now 8.0.4-0ubuntu2~ppa4 ppc64el [installed,automatic] dotnet-runtime-8.0/noble,now 8.0.4-0ubuntu2~ppa4 ppc64el [installed,automatic] dotnet-sdk-8.0/noble,now 8.0.104-0ubuntu2~ppa4 ppc64el [installed,automatic] dotnet-targeting-pack-8.0/noble,now 8.0.4-0ubuntu2~ppa4 ppc64el [installed,automatic] dotnet-templates-8.0/noble,now 8.0.104-0ubuntu2~ppa4 ppc64el [installed,automatic] dotnet8/noble,now 8.0.104-8.0.4-0ubuntu2~ppa4 ppc64el [installed] $ dotnet --info .NET SDK: Version: 8.0.104 Commit:034f91fcc0 Workload version: 8.0.100-manifests.cd97f1c9 Runtime Environment: OS Name: ubuntu OS Version: 24.04 OS Platform: Linux RID: ubuntu.24.04-ppc64le Base Path: /usr/lib/dotnet/sdk/8.0.104/ .NET workloads installed: Workload version: 8.0.100-manifests.cd97f1c9 There are no installed workloads to display. Host: Version: 8.0.4 Architecture: ppc64le Commit: 2d7eea2529 .NET SDKs installed: 8.0.104 [/usr/lib/dotnet/sdk] .NET runtimes installed: Microsoft.AspNetCore.App 8.0.4 [/usr/lib/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 8.0.4 [/usr/lib/dotnet/shared/Microsoft.NETCore.App] Other architectures found: None Environment variables: Not set global.json file: Not found Learn more: https://aka.ms/dotnet/info Download .NET: $ dotnet new console -o HelloWorld Welcome to .NET 8.0! - SDK Version: 8.0.104 Installed an ASP.NET Core HTTPS development certificate. To trust the certificate, view the instructions: https://aka.ms/dotnet-https-linux Write your first app: https://aka.ms/dotnet-hello-world Find out what's new: https://aka.ms/dotnet-whats-new Explore documentation: https://aka.ms/dotnet-docs Report issues and find source on GitHub: https://github.com/dotnet/core Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli -- The template "Console App" was created successfully. Processing post-creation actions... Restoring /home/foo/HelloWorld/HelloWorld.csproj: Determining projects to restore... Restored /home/foo/HelloWorld/HelloWorld.csproj (in 980 ms). Restore succeeded. foo@ltcden12-lp22:~$ cd HelloWorld/ foo@ltcden12-lp22:~/HelloWorld$ dotnet run Hello, World! $ dotnet new console -lang "F#" -o FSharpHelloWorld The template "Console App" was created successfully. Processing post-creation actions... Restoring /home/foo/HelloWorld/FSharpHelloWorld/FSharpHelloWorld.fsproj: Determining projects to restore... Restored /home/foo/HelloWorld/FSharpHelloWorld/FSharpHelloWorld.fsproj (in 575 ms). Restore succeeded. $ cd FSharpHelloWorld/ $ dotnet run Hello from F# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064530 Title: Include support for .NET 8 for Ubuntu on Power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2064530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061954] Re: filezilla crashed with SIGABRT in start_thread()
Hey, thanks for taking the time to make the patch! There are some problems that I noticed that I think you might want to fix so that we can get this into Ubuntu. Firstly, the SRU paperwork. The bug you're fixing may very well be a good one to SRU a fix for, but the SRU justification in your comment above is insufficient. Please read https://wiki.ubuntu.com/StableReleaseUpdates carefully, especially section 4 "Procedure". In particular: * The impact section could be made more verbose so that the SRU team has an understanding of *why* something is going wrong, not just *what* is going wrong. * The test plan is inadequate. We need a full, step-by-step list of instructions on how someone other than yourself should set up their systems for testing, and then the exact steps to take for testing. This doesn't have to be crazily detailed (you don't have to describe every single button and keystroke to use), but it needs to be detailed enough that someone else can do it themselves and verify both that the old version is broken and that the new version is fixed. * The "Where problems could occur" section has been left out entirely. This section is mandatory, as any fix, **no matter how small**, comes with regression potential. (This is slightly hard to imagine until you've mangled packages the way I have. :P) Show that you're "expecting the unexpected" here. * The "OTHER INFO" section appears to contain info that was intended for "Where problems could occur". The info in this section is insufficient for a "Where problems could occur" section as it simply states that the regression possibility is low, rather than describing what could go wrong. According to the SRU process documentation, "This (the "Where problems could occur" section) must **never** be "None" or "Low", or entirely an argument as to why your upload is low risk.". * The SRU template goes in the bug report description, not in a comment. Usually the way I do this without overwriting old changes is I edit the bug report, leave the original bug report at the bottom, and place the SRU paperwork at the top. Secondly, the patch itself has some problems: +libfilezilla (0.46.0-3.1build4) noble; urgency=medium ^^ * This version number is wrong. You're introducing an Ubuntu delta, so you need an "ubuntu" version number here, not a "build" version number. According to https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging (which is linked to from the SRU documentation), the version number that should be used here is 0.46.0-3.1ubuntu0.1. (And yes, I think that my suggested version number looks as insane as you think it does. Ubuntu version numbers are hard.) * Speaking of an Ubuntu delta, when you make Ubuntu-specific changes to a package, you need to modify debian/control to show that the package has Ubuntu changes. To do this, the 'Maintainer' field in debian/control needs to be converted to an 'XSBC-Original-Maintainer' field, and a new 'Maintainer' field put in its place identifying the Ubuntu Developers as being the maintainer, like so: Maintainer: Ubuntu Developers * The patch is missing Debian dep3 headers. See https://dep- team.pages.debian.net/deps/dep3/ for more information. You can add these pretty easily using `quilt header --dep3 -e`. I hope this is helpful! Thanks for taking the time to make and test the patch, and hopefully we'll be able to get it into Ubuntu soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061954 Title: filezilla crashed with SIGABRT in start_thread() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfilezilla/+bug/2061954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054491] Re: rust-ureq autopkgtest fails
Yeah, if it was a rust team package I'd just fix it from the Debian side, but the last time I asked Jonas to change something to help with a ubuntu specific issue he did the opposite. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054491 Title: rust-ureq autopkgtest fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-ureq/+bug/2054491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
