[Bug 1960171] Re: [SRU] virtualbox 6.1.32 virtualbox-guest-dkms build failure on focal with linux 5.15
Also all autopkgtests are now good! ** Tags removed: verification-needed verification-needed-focal verification-needed-impish ** Tags added: verification-done verification-done-focal verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960171 Title: [SRU] virtualbox 6.1.32 virtualbox-guest-dkms build failure on focal with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1960171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960747] Re: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X
If you are able to wipe the machine and test 22.04 early then it can be downloaded here: http://cdimage.ubuntu.com/daily-live/current/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960747 Title: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1960747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960747] Re: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X
It looks like there were a few rotation fixes upstream in mutter in the past year or so, so maybe this has been fixed already. Unfortunately you can't test it in a live session because live sessions use Xorg still. We'll need to wait until you are able and willing to try Ubuntu 22.04, which will be formally released in April. ** Tags added: amdgpu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960747 Title: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1960747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1484039] Re: yoga 3 screen does not rotate
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: unity-settings-daemon (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484039 Title: yoga 3 screen does not rotate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1484039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957026] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958153] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958153 Title: [SRU][F] Add firmware of MT7922 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958283] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958283 Title: linux-firmware missing renoir_ta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959064] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959064 Title: [SRU][F] Add mt8183 SCP firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954300] Re: mt7921e: Failed to start WM firmware
This bug was fixed in the package linux-firmware - 1.201.4 --- linux-firmware (1.201.4) impish; urgency=medium * mt7921e: Failed to start WM firmware (LP: #1954300) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * mt7921e :02:00.0: PM: failed to resume async: error -110 (LP: #1958286) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip(MT7921) -- Juerg Haefliger Fri, 28 Jan 2022 11:12:51 +0100 ** Changed in: linux-firmware (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954300 Title: mt7921e: Failed to start WM firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
This bug was fixed in the package linux-firmware - 1.187.26 --- linux-firmware (1.187.26) focal; urgency=medium * [SRU][F] Add firmware of MT7922 (LP: #1958153) - linux-firmware: add firmware for MT7922 - linux-firmware: add frimware for mediatek bluetooth chip (MT7922) * linux-firmware missing renoir_ta (LP: #1958283) - amdgpu: update renoir firmware for 20.10 - amdgpu: update renoir firmware from 20.20 release - amdgpu: update renoir firmware for 20.30 - amdgpu: update renoir firmware for 20.40 - amdgpu: update renoir firmware for 20.45 - amdgpu: update renoir firmware for 20.50 - amdgpu: update renoir firmware from 21.10 - amdgpu: update renoir firmware from 21.20 - amdgpu: update vcn firmware for renoir for 21.20 - amdgpu: update renoir firmware from 21.30 - amdgpu: update VCN firmware for renoir * mt7921e :02:00.0: PM: failed to resume async: error -110 (LP: #1958286) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip(MT7921) * [SRU][F] Add mt8183 SCP firmware (LP: #1959064) - mediatek: Add mt8183 SCP firmware * AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes (LP: #1957026) - amdgpu: update yellow carp dmcub firmware -- Juerg Haefliger Fri, 28 Jan 2022 10:54:30 +0100 ** Changed in: linux-firmware (Ubuntu Focal) 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/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958153] Re: [SRU][F] Add firmware of MT7922
This bug was fixed in the package linux-firmware - 1.187.26 --- linux-firmware (1.187.26) focal; urgency=medium * [SRU][F] Add firmware of MT7922 (LP: #1958153) - linux-firmware: add firmware for MT7922 - linux-firmware: add frimware for mediatek bluetooth chip (MT7922) * linux-firmware missing renoir_ta (LP: #1958283) - amdgpu: update renoir firmware for 20.10 - amdgpu: update renoir firmware from 20.20 release - amdgpu: update renoir firmware for 20.30 - amdgpu: update renoir firmware for 20.40 - amdgpu: update renoir firmware for 20.45 - amdgpu: update renoir firmware for 20.50 - amdgpu: update renoir firmware from 21.10 - amdgpu: update renoir firmware from 21.20 - amdgpu: update vcn firmware for renoir for 21.20 - amdgpu: update renoir firmware from 21.30 - amdgpu: update VCN firmware for renoir * mt7921e :02:00.0: PM: failed to resume async: error -110 (LP: #1958286) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip(MT7921) * [SRU][F] Add mt8183 SCP firmware (LP: #1959064) - mediatek: Add mt8183 SCP firmware * AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes (LP: #1957026) - amdgpu: update yellow carp dmcub firmware -- Juerg Haefliger Fri, 28 Jan 2022 10:54:30 +0100 ** Changed in: linux-firmware (Ubuntu Focal) 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/1958153 Title: [SRU][F] Add firmware of MT7922 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958283] Re: linux-firmware missing renoir_ta
This bug was fixed in the package linux-firmware - 1.187.26 --- linux-firmware (1.187.26) focal; urgency=medium * [SRU][F] Add firmware of MT7922 (LP: #1958153) - linux-firmware: add firmware for MT7922 - linux-firmware: add frimware for mediatek bluetooth chip (MT7922) * linux-firmware missing renoir_ta (LP: #1958283) - amdgpu: update renoir firmware for 20.10 - amdgpu: update renoir firmware from 20.20 release - amdgpu: update renoir firmware for 20.30 - amdgpu: update renoir firmware for 20.40 - amdgpu: update renoir firmware for 20.45 - amdgpu: update renoir firmware for 20.50 - amdgpu: update renoir firmware from 21.10 - amdgpu: update renoir firmware from 21.20 - amdgpu: update vcn firmware for renoir for 21.20 - amdgpu: update renoir firmware from 21.30 - amdgpu: update VCN firmware for renoir * mt7921e :02:00.0: PM: failed to resume async: error -110 (LP: #1958286) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip(MT7921) * [SRU][F] Add mt8183 SCP firmware (LP: #1959064) - mediatek: Add mt8183 SCP firmware * AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes (LP: #1957026) - amdgpu: update yellow carp dmcub firmware -- Juerg Haefliger Fri, 28 Jan 2022 10:54:30 +0100 ** Changed in: linux-firmware (Ubuntu Focal) 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/1958283 Title: linux-firmware missing renoir_ta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958286] Re: mt7921e 0000:02:00.0: PM: failed to resume async: error -110
This bug was fixed in the package linux-firmware - 1.187.26 --- linux-firmware (1.187.26) focal; urgency=medium * [SRU][F] Add firmware of MT7922 (LP: #1958153) - linux-firmware: add firmware for MT7922 - linux-firmware: add frimware for mediatek bluetooth chip (MT7922) * linux-firmware missing renoir_ta (LP: #1958283) - amdgpu: update renoir firmware for 20.10 - amdgpu: update renoir firmware from 20.20 release - amdgpu: update renoir firmware for 20.30 - amdgpu: update renoir firmware for 20.40 - amdgpu: update renoir firmware for 20.45 - amdgpu: update renoir firmware for 20.50 - amdgpu: update renoir firmware from 21.10 - amdgpu: update renoir firmware from 21.20 - amdgpu: update vcn firmware for renoir for 21.20 - amdgpu: update renoir firmware from 21.30 - amdgpu: update VCN firmware for renoir * mt7921e :02:00.0: PM: failed to resume async: error -110 (LP: #1958286) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip(MT7921) * [SRU][F] Add mt8183 SCP firmware (LP: #1959064) - mediatek: Add mt8183 SCP firmware * AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes (LP: #1957026) - amdgpu: update yellow carp dmcub firmware -- Juerg Haefliger Fri, 28 Jan 2022 10:54:30 +0100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958286 Title: mt7921e :02:00.0: PM: failed to resume async: error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958286] Re: mt7921e 0000:02:00.0: PM: failed to resume async: error -110
This bug was fixed in the package linux-firmware - 1.201.4 --- linux-firmware (1.201.4) impish; urgency=medium * mt7921e: Failed to start WM firmware (LP: #1954300) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) * mt7921e :02:00.0: PM: failed to resume async: error -110 (LP: #1958286) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip(MT7921) -- Juerg Haefliger Fri, 28 Jan 2022 11:12:51 +0100 ** Changed in: linux-firmware (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Focal) 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/1958286 Title: mt7921e :02:00.0: PM: failed to resume async: error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958286] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958286 Title: mt7921e :02:00.0: PM: failed to resume async: error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959064] Re: [SRU][F] Add mt8183 SCP firmware
This bug was fixed in the package linux-firmware - 1.187.26 --- linux-firmware (1.187.26) focal; urgency=medium * [SRU][F] Add firmware of MT7922 (LP: #1958153) - linux-firmware: add firmware for MT7922 - linux-firmware: add frimware for mediatek bluetooth chip (MT7922) * linux-firmware missing renoir_ta (LP: #1958283) - amdgpu: update renoir firmware for 20.10 - amdgpu: update renoir firmware from 20.20 release - amdgpu: update renoir firmware for 20.30 - amdgpu: update renoir firmware for 20.40 - amdgpu: update renoir firmware for 20.45 - amdgpu: update renoir firmware for 20.50 - amdgpu: update renoir firmware from 21.10 - amdgpu: update renoir firmware from 21.20 - amdgpu: update vcn firmware for renoir for 21.20 - amdgpu: update renoir firmware from 21.30 - amdgpu: update VCN firmware for renoir * mt7921e :02:00.0: PM: failed to resume async: error -110 (LP: #1958286) - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip(MT7921) * [SRU][F] Add mt8183 SCP firmware (LP: #1959064) - mediatek: Add mt8183 SCP firmware * AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes (LP: #1957026) - amdgpu: update yellow carp dmcub firmware -- Juerg Haefliger Fri, 28 Jan 2022 10:54:30 +0100 ** Changed in: linux-firmware (Ubuntu Focal) 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/1959064 Title: [SRU][F] Add mt8183 SCP firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1959064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960742] Re: System freeze
Please also check for crashes using these steps: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960742 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960742] Re: System freeze
Thanks for the bug report. Next time the freeze happens please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960742 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960747] Re: Autorotation of screen does not work on wayland, but on X
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Summary changed: - Autorotation of screen does not work on wayland, but on X + [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960747 Title: [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1960747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
BTW, "ConditionPathIsDirectory" is not new. It's been there for two years already in Ubuntu 20.04. If you have experienced a regression then more often that would come from a kernel update so please try some different kernel versions. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960709] Re: Recent bluez update broke Bluetooth for setups using a BT dongle
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1960709 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal regression-update ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960709 Title: Recent bluez update broke Bluetooth for setups using a BT dongle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960679] Re: Dekstop icon extension can't handle moving icons to a to-be-empty spot
At first this seems to work fine in 22.04 (much newer version of desktop-icons-ng), but then I could get it to fail if I dragged a group by a folder in the top left of the group. Please try the latest version by booting this from USB: http://cdimage.ubuntu.com/daily-live/current/ If the problem is still present then please report it to the developer at: https://gitlab.com/rastersoft/desktop-icons-ng/-/issues although it might be the same issue as: https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/193 ** Bug watch added: gitlab.com/rastersoft/desktop-icons-ng/-/issues #193 https://gitlab.com/rastersoft/desktop-icons-ng/-/issues/193 ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960679 Title: Dekstop icon extension can't handle moving icons to a to-be-empty spot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1960679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920205] Re: [MIR] oem-somerville-weedle-meta
Attach oem-somerville-weedle-meta_20.04~ubuntu1.debdiff by oem-scripts 1.29. ** Summary changed: - [DRAFT][MIR] oem-somerville-weedle-meta + [MIR] oem-somerville-weedle-meta ** Description changed: - [DRAFT][Availability] + [Background] + + Please see https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM and + https://wiki.ubuntu.com/StableReleaseUpdates/OEMMeta for details. + + [Impact] + + 1. Upgrade path: Users will be upgrading from a package in the associated OEM archive, not the Ubuntu archive. + 2. The background and impact of the situation for this change, and it's impact. + + [Testing] + + 1. Test that `ubuntu-drivers list-oem` lists the meta-package on the relevant hardware + 2. Test that fully installing the meta-package (upgrading to the OEM archive if relevant) works properly on the hardware + 3. Do an offline install. Boot the system. Run update-manager. Check that an upgrade to the OEM package is offered and that it completes successfully and the hardware works properly. + + [Regression Potential] + + Most potential regressions will live in the package set that will be + installed via dependency of this package, which live in OEM archive + (outside of Ubuntu) and control by OEM team. OEM team and other + corresponding team need take responsibility of those dependency + installed. + + [When switching kernel flavour] Check that the new kernel flavour works + on the target platform. + + [Availability] This is a meta package for https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM that means the package doesn't exist in Debian or Ubuntu archive yet. The source code of the oem-somerville-weedle-meta for focal: git clone -b weedle-focal-ubuntu https://git.launchpad.net/~oem-solutions-engineers/pc-enablement/+git/oem-somerville-projects-meta [Rationale] We want to improve the hardware support for some Dell platforms. [Security] No CVE/known security issue. [Quality assurance] I have used ppa:oem-solutions-engineers/oem-projects-meta to check this package on some Dell platforms. - oem-somerville-weedle-meta will be upgraded to 20.04ubuntu1 or latest version from OEM archive. + oem-somerville-weedle-meta will be upgraded to 20.04ubuntu1 or the later version from OEM archive. [Dependencies] It only depends on ubuntu-oem-keyring. [Standards compliance] This package should have met all requirements of https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM. [Maintenance] Canonical OEM Enablement Team will take care of the maintenance. [Background information] Please check https://wiki.ubuntu.com/MIRTeam/Exceptions/OEM for details. Please use "oem-metapackage-mir-check" in lp:ubuntu-archive-tools to verify this MIR against the reference package in the archive. + + https://ubuntu.com/certified/202010-28295 + https://ubuntu.com/certified/202012-28569 + https://ubuntu.com/certified/202012-28584 + https://ubuntu.com/certified/202107-29292 + https://ubuntu.com/certified/202107-29293 ** Changed in: oem-priority Status: Confirmed => Fix Committed ** Changed in: ubuntu Status: New => Confirmed ** Patch added: "oem-somerville-weedle-meta_20.04~ubuntu1.debdiff" https://bugs.launchpad.net/bugs/1920205/+attachment/5560728/+files/oem-somerville-weedle-meta_20.04~ubuntu1.debdiff ** Tags removed: oem-scripts-0.8 ** Tags added: oem-needs-upload oem-scripts-1.29 ubuntu-certified -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920205 Title: [MIR] oem-somerville-weedle-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960679] Re: Dekstop icon extension can't handle moving icons to a to-be-empty spot
** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960679 Title: Dekstop icon extension can't handle moving icons to a to-be-empty spot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1960679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960448] Re: Sony WF-XB700 Bluetooth headset not detected
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960171] Re: [SRU] virtualbox 6.1.32 virtualbox-guest-dkms build failure on focal with linux 5.15
Tested virtualbox-ext-pack (as well as the latest virtualbox-guest-dkms) on focal with linux-hwe-5.15. Everything is working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960171 Title: [SRU] virtualbox 6.1.32 virtualbox-guest-dkms build failure on focal with linux 5.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1960171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960777] [NEW] Bail out when USB port is stuck in reset loop
Public bug reported:
[Impact]
USB port stops working after unplug an USB device.
[Fix]
Commit c89686118c786a523eee3ef68ed38330319626d8 ("usb: core: Bail out when port
is stuck in reset loop")
[Test]
Affected vendor confirmed the patch can fix the issue after numerous round of
tests.
[Where problems could occur]
If there's any peculiar USB hub depends on the old (and buggy) behavior, this
can potentially bring a regression to the hub.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux-intel-5.13 (Ubuntu)
Importance: Undecided
Assignee: Jesse Sung (wenchien)
Status: New
** Tags: murcia oem-priority originate-from-1950235
** Changed in: linux-intel-5.13 (Ubuntu)
Assignee: (unassigned) => Jesse Sung (wenchien)
** Tags added: murcia oem-priority originate-from-1950235
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960777
Title:
Bail out when USB port is stuck in reset loop
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1960777/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960605] Re: Xorg freeze
Thanks for the bug report. I can see two problems here, though am not sure if either is the main issue: * Timeout, server 21.0.0.52 not responding. Whatever that is, if it's a server the machine depends on then it might cause a startup failure. * CurrentDmesg.txt seems to suggest file system corruption on /dev/sdb1. If that's something the machine depends on then it might cause a startup failure. ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960605 Title: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960776] [NEW] i386 installer crashes
Public bug reported: This was an issue which occurred during setup and brought me to this bug report page. I need an older Ubuntu install for the GMA500 driver which has not been updated for newer distros sadly. (Should I open another bug for no 3D acceleration with GMA500 on 20.04 or 22.04?) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8.13 ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167 Uname: Linux 4.4.0-142-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 CasperVersion: 1.340.2 Date: Sun Feb 13 22:58:37 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ubiquity-2.18.8.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960776 Title: i386 installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1960776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960602] Re: Ubuntu 20.04 shows blank upon resuming from resume. Requires hard shutdown using the h/w power button
Thanks for the bug report. The final entry in your kernel log shows that the Intel GPU tried and failed to update the screen: [ 1216.206745] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=73567 end=73568) time 940 us, min 1073, max 1079, scanline start 1033, end 1097 So maybe that's the issue... Please try (separately): 1. Selecting 'Ubuntu on Wayland' on the login screen just before logging in. 2. Edit /etc/environment and add a line: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 Then reboot and select 'Ubuntu on Wayland' again. ** Tags added: resume suspend-resume ** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu) ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960602 Title: Ubuntu 20.04 shows blank upon resuming from resume. Requires hard shutdown using the h/w power button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934643] Re: infinite loop in patched cJSON_Minify function
This bug causes severe problems for multiple of our users. The fix is really small. Can someone please apply the patch. ** Changed in: cjson (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/1934643 Title: infinite loop in patched cJSON_Minify function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cjson/+bug/1934643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954300] Re: mt7921e: Failed to start WM firmware
Test on Troy-MTE-DVT, BIOS 1.0.0 steps: 1. Install ubuntu impish 2. Enable proposed channel 3. Wi-Fi/BT works well after installation ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954300/+attachment/5560719/+files/dmesg.txt ** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954300 Title: mt7921e: Failed to start WM firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660309] Re: packaged strace does not decode all arguments for bpf() syscall
Ubuntu 20.04 LTS ships with 5.5, 22.04 LTS will ship with 5.16. There are no plans to backport these to 16.04 LTS ** Changed in: strace (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/1660309 Title: packaged strace does not decode all arguments for bpf() syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strace/+bug/1660309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935709] Re: grpc++-dev doesn't install gRPCConfig.cmake
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grpc (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/1935709 Title: grpc++-dev doesn't install gRPCConfig.cmake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grpc/+bug/1935709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935709] Re: grpc++-dev doesn't install gRPCConfig.cmake
Not having this is super inconvenient. Please include the cmake config files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935709 Title: grpc++-dev doesn't install gRPCConfig.cmake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grpc/+bug/1935709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955882] Re: MT7921[14c3:7961] ASPM is disabled and it affects power consumption
We also need below commit to fix the issue introduced by this patch https://patchwork.kernel.org/project/linux-mediatek/patch/70e27cbc652cbdb78277b9c691a3a5ba02653afb.1641540175.git.obj...@gmail.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955882 Title: MT7921[14c3:7961] ASPM is disabled and it affects power consumption To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942789] Re: On-demand and RTD3 need to be separated
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + based on the Nvidia README, this case shall not happened. [Other Info] - - X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). ** Changed
[Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + based on the Nvidia README, this case shall not happened. [Other Info] - - X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). -- You
[Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + based on the Nvidia README, this case shall not happened. [Other Info] - - X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949412] Re: Upgrade fwupd for Atomic Docking Support
per test, if fwupd-unsigned is not installed, then re-install bios will be failed if secure boot is not turned on. We need a patch around https://github.com/fwupd/fwupd/blob/main/plugins/uefi-capsule/fu-uefi- common.c#L89 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949412 Title: Upgrade fwupd for Atomic Docking Support To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1949412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960768] Re: fwupd crash on stop
** Also affects: libusb (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/1960768 Title: fwupd crash on stop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894796] Re: [MIR] oem-somerville-charmander-14-meta
** Changed in: oem-priority 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/1894796 Title: [MIR] oem-somerville-charmander-14-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1894796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894795] Re: [MIR] oem-somerville-charmander-meta
** Changed in: oem-priority 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/1894795 Title: [MIR] oem-somerville-charmander-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1894795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920195] Re: [MIR] oem-somerville-pidgeot-14-meta
** Changed in: oem-priority 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/1920195 Title: [MIR] oem-somerville-pidgeot-14-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920196] Re: [MIR] oem-somerville-pidgeot-meta
** Changed in: oem-priority 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/1920196 Title: [MIR] oem-somerville-pidgeot-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937223] Re: [MIR] oem-somerville-kakuna-meta
** Changed in: oem-priority 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/1937223 Title: [MIR] oem-somerville-kakuna-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946839] Re: Merge samba from Debian unstable for 22.04
Just a quick note to mention that Samba in Jammy is a lesser version than in focal-updates and impish-updates, which should probably be addressed before Jammy is released. samba | 2:4.13.14+dfsg-0ubuntu2 | jammy | source, amd64, arm64, armhf, ppc64el, riscv64, s390x samba | 2:4.13.14+dfsg-0ubuntu5 | jammy-proposed | source, amd64, arm64, armhf, ppc64el, riscv64, s390x samba | 2:4.13.17~dfsg-0ubuntu0.21.04.1 | focal-security | source, amd64, arm64, armhf, ppc64el, riscv64, s390x samba | 2:4.13.17~dfsg-0ubuntu0.21.04.1 | focal-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x samba | 2:4.13.17~dfsg-0ubuntu0.21.10.1 | impish-security | source, amd64, arm64, armhf, ppc64el, riscv64, s390x samba | 2:4.13.17~dfsg-0ubuntu0.21.10.1 | impish-updates | source, amd64, arm64, armhf, ppc64el, riscv64, s390x Jammy has 4.13.14+dfsg-0ubuntu5 versus 4.13.17~dfsg-0ubuntu0.21.04.1 in focal-updates. Maybe we should try and ship 4.15.x since it has a complete implementation of CVE-2021-20316? https://lwn.net/Articles/884052/ ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-20316 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946839 Title: Merge samba from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1946839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960771] Re: Use EC GPE for s2idle wakeup on AMD platforms
** Tags added: oem-priority originate-from-1958974 stella ** Tags added: originate-from-1959354 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960771 Title: Use EC GPE for s2idle wakeup on AMD platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1960771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960771] [NEW] Use EC GPE for s2idle wakeup on AMD platforms
Public bug reported: [Impact] Opening lid doesn't wakeup some AMD platforms from s2idle. [Fix] Use EC GPE for lid events to wakeup the laptops. [Test] Close and only the lid. The affected laptop now can be woken up by lid. [Where problems could occur] The original issue was later fixed by "pinctrl: amd: Fix wakeups when IRQ is shared with SCI". However, EC GPE is prone to cause spurious wakeup, so we still need to keep an eye on the regression reports. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Low Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Low Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Low Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1958974 originate-from-1959354 stella ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960771 Title: Use EC GPE for s2idle wakeup on AMD platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1960771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953573] Re: 1_5_X: No Prometheus IOTA Config on HP laptop with version 1.5.11
jeremyszu: the pkg was withdrawn and needs rework. ** Changed in: fwupd (Ubuntu Focal) Status: Fix Committed => Confirmed ** Changed in: fwupd (Ubuntu Impish) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953573 Title: 1_5_X: No Prometheus IOTA Config on HP laptop with version 1.5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1953573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953628] Re: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10
[Expired for qemu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: qemu (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/1953628 Title: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960768] Re: fwupd crash on stop
I happened to install an impish iso with the previous libusb. It seems to me that: after upgrading libusb, then this can be reproduced. more information will be provided. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754945] Re: update homepage metadata to https://strace.io
fixed in the 5.13 packaging ** Changed in: strace (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/1754945 Title: update homepage metadata to https://strace.io To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strace/+bug/1754945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953573] Re: 1_5_X: No Prometheus IOTA Config on HP laptop with version 1.5.11
Hi Łukasz, I didn't see the targeted fwupd in focal-proposed and impish-proposed. $ apt policy fwupd fwupd: Installed: 1.7.4-1ubuntu1 Candidate: 1.7.4-1ubuntu1 Version table: *** 1.7.4-1ubuntu1 500 500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 1.5.11-0ubuntu2 500 500 http://tw.archive.ubuntu.com/ubuntu impish/main amd64 Packages 1.5.11-0ubuntu1~20.04.2 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1.3.9-4 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages Are they published correctly? ** Tags removed: verification-needed verification-needed-focal verification-needed-impish ** Tags added: verification-failed verification-failed-focal verification-failed-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953573 Title: 1_5_X: No Prometheus IOTA Config on HP laptop with version 1.5.11 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1953573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960768] [NEW] fwupd crash on stop
Public bug reported: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. ** Affects: oem-priority Importance: Critical Assignee: Yuan-Chen Cheng (ycheng-twn) Status: In Progress ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: jammy oem-priority ** Tags added: jammy ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Changed in: oem-priority Status: New => In Progress ** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959847] Re: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet]
Hi Frode, I went through the captures I have and effectively, if we filter out the packets where the srcport != 53 or dstport != 6081 , we end up only with valid dns traffic. I believe this explains what we are seeing, and the other findings you did regards the missing flows, we can say with certainty that the DNS issues we are seeing are only a symptom of instances losing North-South traffic. I'm closing the bug as Invalid. $ for PCAP in *.pcap; do echo -e "$PCAP\t$(tshark -r $PCAP | grep -i "unknown" | wc -l)\t$(tshark -r $PCAP 'udp.dstport ne 6081' | grep -i unknown | wc -l)\t$(tshark -r $PCAP 'udp.srcport ne 53' | grep -i unknown | wc -l)";done dns-port-machine-0.pcap 90 0 0 dns-port-machine-10.pcap104 0 0 dns-port-machine-11.pcap26 0 0 dns-port-machine-12.pcap0 0 0 dns-port-machine-13.pcap0 0 0 dns-port-machine-2.pcap 6 0 0 dns-port-machine-3.pcap 72 0 0 dns-port-machine-4.pcap 0 0 0 dns-port-machine-5.pcap 59 0 0 dns-port-machine-6.pcap 68 0 0 dns-port-machine-7.pcap 46 0 0 dns-port-machine-8.pcap 104 0 0 dns-port-machine-9.pcap 32 0 0 ** Changed in: ovn (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959847 Title: Unknown operation (12) 0x0240 Unknown (7680)[Malformed Packet] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1959847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951033] Re: 20.04 SRU
I wrote a script for making a core20 with glibc from proposed in it:
#!/bin/sh
set -eux
snap download --basename core20_prehax core20
unsquashfs -d core20 core20_prehax.snap
a=$(dpkg --print-architecture)
v=2.31-0ubuntu9.5
build=https://launchpad.net/ubuntu/+source/glibc/${v}/+latestbuild/${a}/+files
for p in libc6 libc-bin; do
deb=${p}_${v}_${a}.deb
wget $build/$deb
dpkg-deb --fsys-tarfile $deb | sudo chroot core20 tar
--keep-directory-symlink -x
done
curl
https://raw.githubusercontent.com/snapcore/core20/master/hooks/029-fix-ld-so-symlink.chroot
> core20/hook.sh
chroot core20 bash hook.sh
rm core20/hook.sh
snap pack --filename core20_posthax.snap core20
snap install --dangerous ./core20_posthax.snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951033
Title:
20.04 SRU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1951033/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960729] Re: Thinkpad T14 gen2 AMD - spontaneous reboot
** Description changed: After my Thinkpad T14 gen2 AMD spontaneously rebooted I found this in the kernel log: [6.211553] === [6.211556] UBSAN: invalid-load in /build/linux-PqLDBN/linux-5.15.15/drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:5882:84 [6.211558] load of value 187 is not a valid value for type '_Bool' [6.211560] CPU: 2 PID: 414 Comm: plymouthd Tainted: G OE 5.15.15-76051515-generic #202201160435~1642693824~21.10~97db1bb [6.211561] Hardware name: LENOVO 20XKCTO1WW/20XKCTO1WW, BIOS R1MET43W (1.13 ) 11/05/2021 [6.211562] Call Trace: [6.211563] [6.211565] show_stack+0x52/0x58 [6.211569] dump_stack_lvl+0x4a/0x5f [6.211573] dump_stack+0x10/0x12 [6.211574] ubsan_epilogue+0x9/0x45 [6.211575] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [6.211577] create_stream_for_sink.cold+0x5d/0xbb [amdgpu] [6.211697] ? __free_pages_ok+0x31b/0x470 [6.211699] create_validate_stream_for_sink+0x59/0x150 [amdgpu] [6.211802] dm_update_crtc_state+0x235/0x7b0 [amdgpu] [6.211894] amdgpu_dm_atomic_check+0x596/0xcd0 [amdgpu] [6.211983] ? dm_plane_format_mod_supported+0x1f/0x100 [amdgpu] [6.212069] ? drm_plane_check_pixel_format+0x45/0x90 [drm] [6.212084] ? drm_atomic_plane_check+0x12f/0x360 [drm] [6.212095] drm_atomic_check_only+0x253/0x4b0 [drm] [6.212103] ? handle_conflicting_encoders+0x26b/0x2a0 [drm_kms_helper] [6.212113] drm_atomic_commit+0x18/0x50 [drm] [6.212122] drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper] [6.212128] drm_mode_setcrtc+0x1f9/0x7c0 [drm] [6.212137] ? drm_mode_getcrtc+0x1c0/0x1c0 [drm] [6.212146] drm_ioctl_kernel+0xae/0xf0 [drm] [6.212155] drm_ioctl+0x264/0x4b0 [drm] [6.212163] ? drm_mode_getcrtc+0x1c0/0x1c0 [drm] [6.212172] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] [6.212231] __x64_sys_ioctl+0x91/0xc0 [6.212234] do_syscall_64+0x5c/0xc0 [6.212235] ? amdgpu_drm_ioctl+0x6f/0x80 [amdgpu] [6.212294] ? exit_to_user_mode_prepare+0x37/0xb0 [6.212296] ? syscall_exit_to_user_mode+0x27/0x50 [6.212298] ? do_syscall_64+0x69/0xc0 [6.212299] ? exit_to_user_mode_prepare+0x37/0xb0 [6.212300] ? irqentry_exit_to_user_mode+0x9/0x20 [6.212301] ? irqentry_exit+0x19/0x30 [6.212302] ? exc_page_fault+0x89/0x160 [6.212303] ? asm_exc_page_fault+0x8/0x30 [6.212305] entry_SYSCALL_64_after_hwframe+0x44/0xae [6.212306] RIP: 0033:0x7fc4c316a9cb [6.212308] Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 35 a4 0f 00 f7 d8 64 89 01 4 8 [6.212309] RSP: 002b:7b5d2fb8 EFLAGS: 0246 ORIG_RAX: 0010 [6.212310] RAX: ffda RBX: 7b5d2ff0 RCX: 7fc4c316a9cb [6.212311] RDX: 7b5d2ff0 RSI: c06864a2 RDI: 0009 [6.212312] RBP: c06864a2 R08: R09: 5566798141f0 [6.212312] R10: R11: 0246 R12: 0067 [6.212313] R13: 0009 R14: 556679814140 R15: 556679814180 [6.212314] [6.212314] === --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 21.10 Package: linux (not installed) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh Tags: impish Uname: Linux 5.15.15-76051515-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: pop:GNOME + DistroRelease: Pop!_OS 21.10 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/usr/bin/zsh + Tags: impish + Uname: Linux 5.15.15-76051515-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm lpadmin sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1960729/+attachment/5560715/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960729 Title: Thinkpad T14 gen2
[Bug 1960766] [NEW] Introduce 510 NVIDIA driver series
Public bug reported: The nvidia-settings packages is needed for the new Nvidia 510 series driver from 20.04 for OEM customer. ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Introduce Nvidia the 510 series + Introduce 510 NVIDIA driver series -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960766 Title: Introduce 510 NVIDIA driver series To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1960766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960569] Re: Screen goes dim
Nothing in regular Ubuntu calls 'xrandr --brightness' that I know of. Hence I recommend uninstalling 'brightness-controller' because it's the most suspicious package right now. Also I would expect 'GNOME' to avoid the problem more than 'GNOME on Xorg' because 'GNOME' has no Xorg server and no support for 'xrandr --brightness'. But still it would be very helpful to test both 'GNOME' and 'GNOME on Xorg'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960569 Title: Screen goes dim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1960569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949075] Status changed to Confirmed
This change was made by a bot. ** 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/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960403] Re: Kubuntu constantly freezing on ThinkPad T510
Jonas, In comment #5 do you mean the fix was released to Ubuntu, or the fix is only in the Mesa PPA from comment #3? ** No longer affects: xserver-xorg-video-intel (Ubuntu) ** No longer affects: linux (Ubuntu) ** No longer affects: kubuntu-meta (Ubuntu) ** No longer affects: xorg (Ubuntu) ** Tags added: arrandale i915 ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1960403 Title: Kubuntu constantly freezing on ThinkPad T510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960403/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1960448] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1960448 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767542] Re: Turning off WiFi enables Airplane mode
Same issue in home desktop computer. Wifi not turn on. I have to restart wifi-dongle and computer. Ubuntu 18.04 LTS. I dont find any options in turned to off. Settings are same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767542 Title: Turning off WiFi enables Airplane mode To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1767542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960336] Re: No login screen after recent update
I think most likely the problem is a side effect of the customizations this machine has experienced over the years. Like switching display managers multiple times, or using a non-standard kernel. I would suggest the fastest way to a fix might be to just reinstall fresh: http://cdimage.ubuntu.com/daily-live/current/ If you need DisplayLink support for kernel 5.13 then I can confirm the 5.5 beta driver works well: https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949075] Re: Sony WI-C310 Bluetooth headset not autoconnecting on power-on on 21.10
Given the message in your kernel log: Bluetooth: hci0: Ignoring error of Inquiry Cancel command A similar problem with the same message was a kernel regression: https://bbs.archlinux.org/viewtopic.php?id=259954 Maybe not related to this bug, but still a reminder that it might be a kernel regression. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Sony WI-C310 Bluetooth headset not autoconnecting on power-on on 21.10 + [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960448] Re: Sony WF-XB700 Bluetooth headset not detected
** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Changed in: gnome-bluetooth (Ubuntu) Status: Incomplete => New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949075] Re: Bluetooth headset not autoconnecting on power-on on 21.10
This is still on my TODO list but low priority. The reason being this kind of bug has been observed with every release on a variety of hardware. I think it fails in more cases than it succeeds, and has always done so. If by chance a developer has access to the same specific headset then the problem could be bisected and a specific cause identified. ** Summary changed: - Bluetooth headset not autoconnecting on power-on on 21.10 + Sony WI-C310 Bluetooth headset not autoconnecting on power-on on 21.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: Sony WI-C310 Bluetooth headset not autoconnecting on power-on on 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1942 https://gitlab.gnome.org/GNOME/mutter/-/issues/1942 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1942 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676203] Re: Strange pixels after wakeup
*** This bug is a duplicate of bug 1876632 *** https://bugs.launchpad.net/bugs/1876632 This is an ongoing problem with the Nvidia drivers. Now tracking in bug 1876632. ** This bug has been marked a duplicate of bug 1876632 [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676203 Title: Strange pixels after wakeup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1676203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563083] Re: Desktop file broken
Seem that this bug has been solved in 20210415-1 version for Jammy, so should be closed. Thanks and best regards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563083 Title: Desktop file broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gprename/+bug/1563083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
Sorry, this bug is very old and this version of Ubuntu isn't supported any more. If you think you have a similar issue, please file a new bug. ** Package changed: fedora => libgweather4 (Ubuntu) ** No longer affects: libgweather4 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
** Changed in: gnome-desktop (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-desktop (Ubuntu) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libgweather4 (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/980519 Title: Random log off in Ubuntu 12.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72172] Re: wishlist: support for recently used applications
** Changed in: gnome-desktop (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/72172 Title: wishlist: support for recently used applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/72172/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 465764] Re: gnome-about crashed with KeyError: u'values'
gnome-about doesn't exist any more. ** Changed in: gnome-desktop (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/465764 Title: gnome-about crashed with KeyError: u'values' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/465764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960633] Re: Create linux-modules-extra-generic metapackage
The Ubuntu kernel mailing list is a better place to discuss adding a new package: https://lists.ubuntu.com/archives/kernel-team/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960633 Title: Create linux-modules-extra-generic metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960703] Re: USB TASCAM US-122L audio interface crashes when system load increases
Is it possible to bisect the kernel to find the offending commit? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960703 Title: USB TASCAM US-122L audio interface crashes when system load increases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960753] Re: Remove the gnome-user-guide binary from jammy
The Ubuntu Archive team will remove gnome-user-guide soon since it's in green at https://people.canonical.com/~ubuntu-archive/nbs.html ** Changed in: gnome-user-docs (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/1960753 Title: Remove the gnome-user-guide binary from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1960753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954300] Re: mt7921e: Failed to start WM firmware
Hey You-Sheng Yang @vicamo, Friendly poke :) Could you please verify linux-firmware in impish- proposed? This verification seems to block the linux-firmware SRU on impish, and that blocks a larger SRU on focal. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954300 Title: mt7921e: Failed to start WM firmware To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959115] Re: update backportpackage and requestbackport scripts to behave according to new backport process
Which version have you tested? backportpackge in u-d-t 0.187+ should already be using the ~bp suffix. Notably, note that 0.187 is available in focal-bpo. On Sun, 13 Feb 2022, 8:35 pm Ross Gammon, <1959...@bugs.launchpad.net> wrote: > Regarding the requestbackport package, it is really only the template > for the bug report that needs to change from memory. I don't think it > had any other workflow related information. Once that is fixed, it just > needs a reference from the backports process wiki again (like it used to > have). > > Regarding the backportpackage script, I just tried it, and it is fine for > testing in a ppa. I think we could already recommend using this on the wiki > with a ppa specified in the -u option. Perhaps a warning not to upload to > the archive with it yet would be required though. I had hoped I could > specify the new "bpo" version string with the suffix option, but according > to the manpage, the "~ubuntu" bit is hardwired: > -S SUFFIX, --suffix=SUFFIX > Add the specified suffix to the version number when > backporting. > backportpackage will always append ~ubuntuDESTINATION.1 to > the > original version number, and if SUFFIX is specified, it is > ap‐ > pended to that, to get version numbers of the form > ORIGINAL_VER‐ > SION~ubuntuDESTINATION.1SUFFIX. If the backported package is > be‐ > ing uploaded to a PPA, then SUFFIX defaults to ~ppa1, > otherwise > the default is blank. > > Now that a bug is always required, I suppose the script should prompt > for that, and the "-c/--close" options be taken away. > > -- > You received this bug notification because you are a member of Ubuntu > Backporters, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1959115 > > Title: > update backportpackage and requestbackport scripts to behave according > to new backport process > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1959115/+subscriptions > > > -- > ubuntu-backports mailing list > ubuntu-backpo...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959115 Title: update backportpackage and requestbackport scripts to behave according to new backport process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1959115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
Debhelper 13 is available in focal-backports already. Please make sure your build environment enables the backports pocket (and that your dependency solver handles it appropriately). If you are building in a PPA, there is an extra flag to check in the PPA settings. On Sun, 13 Feb 2022, 9:45 pm Ross Gammon, <1960...@bugs.launchpad.net> wrote: > Uploaded 5.1.4~bpo21.04.1 to impish-backports > > -- > You received this bug notification because you are a member of Ubuntu > Backporters, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1960752 > > Title: > [BPO] gramps/5.1.4-1 from Jammy > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions > > > -- > ubuntu-backports mailing list > ubuntu-backpo...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960757] [NEW] installation of ubuntu stopped right at the end and an error message said install was unsuccessful
Public bug reported: i am completely new with the linux os so i am not sure how else to describe the error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 00:47:35 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960757 Title: installation of ubuntu stopped right at the end and an error message said install was unsuccessful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1960757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
Uploaded 5.1.4~bpo21.04.1 to impish-backports -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960756] [NEW] VNC connection to Wayland / PipeWire aborts
Public bug reported: Connecting to a modern installation of Ubuntu 21.10 Impish Indri using the Wayland display server (and PipeWire / gnome-remote-desktop) does not work from the current LTS release 20.04 Focal Fossa. It aborts immediately after authentication. The bug appears directly related to the version 1.4.2 in focal, as building the up-to-date remmina version 1.4.23 package (from jammy) under focal does not exhibit the faulty behavior. Since future versions of Ubuntu itself will likely stick with Wayland and therefore cannot be used with Remmina from the LTS release anymore, I think an SRU might be in order. As a workaround, other VNC viewers such as Vinagre are able to connect to the same server under focal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina-plugin-vnc 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-lowlatency 5.13.19 Uname: Linux 5.13.0-28-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Feb 13 21:17:06 2022 InstallationDate: Installed on 2012-10-22 (3400 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-30 (531 days ago) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960756 Title: VNC connection to Wayland / PipeWire aborts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1960756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960749] Re: dpkg incorrectly installs singular-doc in jammy Docker container
And if you want to keep this behaviour, at least make sure `dpkg -V` reports that files are missing due to a policy, not cause it's a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960749 Title: dpkg incorrectly installs singular-doc in jammy Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960749] Re: dpkg incorrectly installs singular-doc in jammy Docker container
This was discovered during the run of a CI, and interactive steps are provided for the ease of reproduction, not because it's the way it was found. If you don't know how to use Docker images interactively, it doesn't mean they are not used this way. Also, even if I'd agree that Docker containers are useless for interactive work (I don't) note that the steps still install broken symbolic links into /usr/share/doc. One sees # ls -l /usr/share/doc/singular/html/ total 0 lrwxrwxrwx 1 root root 13 Dec 17 20:20 sing_1068.png -> sing_1008.png ... root@c9df22f5e5ab:/sage# ls -l /usr/share/doc/singular/html/ | wc -l 71 And I really think that it's up to the user to decide how to use Docker containers, and you should not break things like this. By the way, Jammy lxc container does not show this bug - are you telling me that lxc images are OK for interactive work, but Docker containers are not? Containers/images are very useful for quick testing of whatever pops up, and breaking system packages like this is very bad. I wasted a day chasing this weirdness up - dpkg should at the very least emit a warning that it drops things in such a case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960749 Title: dpkg incorrectly installs singular-doc in jammy Docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960264] Re: 503 errors for Jammy PPAs
Julian - correct I was using apt-cacher-ng as per sbuild instructions here https://wiki.ubuntu.com/SimpleSbuild Sorry - I've no idea how to configure squid-deb-proxy with sbuild. So I've deleted my sbuild chroots & disabled using the .mk-sbuildrc proxy. Installing from a ppa no longer shows 503 errors. ** Changed in: apt (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960264 Title: 503 errors for Jammy PPAs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960733] Re: install successful but crashed with CalledProcessError - subiquity 290
** Summary changed: - install crashed with CalledProcessError - subiquity 290 + install successful but crashed with CalledProcessError - subiquity 290 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960733 Title: install successful but crashed with CalledProcessError - subiquity 290 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1960733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960727] Re: When apt holds back updates, it fails to inform the user of the reason
For over a decade now, at least, users have continually been puzzled by this silent refusal. Again, in most contexts, that indicates a failure of the interface. Viewed 1.1M times https://askubuntu.com/questions/601/the-following-packages-have-been-kept-back-why-and-how-do-i-solve-it Viewed 62k times https://unix.stackexchange.com/questions/38837/what-does-the-following-packages-have-been-kept-back-mean Viewed 87k times https://superuser.com/questions/1107334/apt-says-packages-have-been-kept-back-what-to-do/1108268 etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960727 Title: When apt holds back updates, it fails to inform the user of the reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377338] Re: apparmor may fail to load some profiles if one is corrupted
It should be fixed as of the AppArmor 3.0 release. With 3.0 the handling of jobs doesn't stop with an error unless --abort-on-error is specified. Instead the parser will keep track of the last error and return that there was an error, but it will keep processing the rest of the jobs. We did not close this for 3.0 as we wanted more time, to make sure we have it fixed. But we are considering it fixed on the dev branch. Though christian did turn up another corner case the other day https://gitlab.com/apparmor/apparmor/-/issues/215 that we need to finish fixing. ** Bug watch added: gitlab.com/apparmor/apparmor/-/issues #215 https://gitlab.com/apparmor/apparmor/-/issues/215 ** Changed in: apparmor Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377338 Title: apparmor may fail to load some profiles if one is corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1377338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959115] Re: update backportpackage and requestbackport scripts to behave according to new backport process
Regarding the requestbackport package, it is really only the template for the bug report that needs to change from memory. I don't think it had any other workflow related information. Once that is fixed, it just needs a reference from the backports process wiki again (like it used to have). Regarding the backportpackage script, I just tried it, and it is fine for testing in a ppa. I think we could already recommend using this on the wiki with a ppa specified in the -u option. Perhaps a warning not to upload to the archive with it yet would be required though. I had hoped I could specify the new "bpo" version string with the suffix option, but according to the manpage, the "~ubuntu" bit is hardwired: -S SUFFIX, --suffix=SUFFIX Add the specified suffix to the version number when backporting. backportpackage will always append ~ubuntuDESTINATION.1 to the original version number, and if SUFFIX is specified, it is ap‐ pended to that, to get version numbers of the form ORIGINAL_VER‐ SION~ubuntuDESTINATION.1SUFFIX. If the backported package is be‐ ing uploaded to a PPA, then SUFFIX defaults to ~ppa1, otherwise the default is blank. Now that a bug is always required, I suppose the script should prompt for that, and the "-c/--close" options be taken away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959115 Title: update backportpackage and requestbackport scripts to behave according to new backport process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1959115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960754] [NEW] gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied
Public bug reported: Getting the following error gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied I seen this was also an issue in redhat https://bugzilla.redhat.com/show_bug.cgi?id=1908506 Description:Ubuntu 20.04.3 LTS Release:20.04 ** Affects: samba (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/1960754 Title: gencache_init: Failed to create directory: /var/www/.cache/samba - Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1960754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960727] Re: When apt holds back updates, it fails to inform the user of the reason
Nearly anything would be better than the current state of silent failure. At present, probably many thousands of Ubuntu systems are reporting the following: root@system:/home# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: libnvidia-cfg1-470 libnvidia-compute-470 libnvidia-compute-470:i386 libnvidia-decode-470 libnvidia-decode-470:i386 libnvidia-encode-470 libnvidia-encode-470:i386 libnvidia-extra-470 libnvidia-fbc1-470 libnvidia-fbc1-470:i386 libnvidia-gl-470 libnvidia-gl-470:i386 libnvidia-ifr1-470 libnvidia-ifr1-470:i386 linux-modules-nvidia-470-5.13.0-28-generic linux-modules-nvidia-470-generic-hwe-20.04 linux-objects-nvidia-470-5.13.0-28-generic linux-signatures-nvidia-5.13.0-28-generic nvidia-compute-utils-470 nvidia-driver-470 nvidia-kernel-common-470 nvidia-kernel-source-470 nvidia-utils-470 xserver-xorg-video-nvidia-470 0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded. Providing not even a hint as to which of those packages is uninstallable, or why, would be unacceptable in most development contexts. In this case, with preceding versions of most or all of those packages already installed, it is far from clear to end-users why their system refuses to install official upgrades. Not many software tools respond to user instructions with a simple "No", and that's generally considered bad practice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960727 Title: When apt holds back updates, it fails to inform the user of the reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960264] Re: 503 errors for Jammy PPAs
It seems you use apt-cacher-ng, please try if the issue reproduces without it, and if so, if it happens with a known good proxy like squid (e.g. using deb-squid-proxy). ** Changed in: apt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960264 Title: 503 errors for Jammy PPAs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
Gramps 5.1.4 from my ppa upgrades fine, and runs as normal on Impish. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960727] Re: When apt holds back updates, it fails to inform the user of the reason
Marking as Opinion as David explained why that is not a thing we can reasonably determine. ** Changed in: apt (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960727 Title: When apt holds back updates, it fails to inform the user of the reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
Gramps 5.1.4 builds fine in Impish. Unfortunately, it fails to build in Focal The following packages have unmet dependencies: sbuild-build-depends-gramps-dummy : Depends: debhelper-compat (= 13) It would be great if the latest debhelper was backported to Focal. Otherwise I will have to drop the debhelper compatibility back to 12. https://launchpad.net/~rosco2/+archive/ubuntu/backports/+packages ** Also affects: gramps (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gramps (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960753] [NEW] Remove the gnome-user-guide binary from jammy
Public bug reported: Not sure if this needs to be dealt with manually, but to be safe: The gnome-user-guide binary is a transitional dummy package which has been built by the gnome-user-docs source package and which is not longer needed. It was not built by the latest gnome-user-docs upload (41.2-1ubuntu1). But even if gnome-user-docs 41.2-1ubuntu1 migrated successfully, gnome- user-guide 41.1-1ubuntu1 seems to be kept in the jammy archive. So I'm asking for the removal of the latter. $ apt rdepends gnome-user-guide gnome-user-guide Reverse Depends: |Suggests: unity-control-center It's my understanding that no explicit request is needed for the equivalent removal at Debian: https://www.debian.org/doc/manuals/developers- reference/pkgs.en.html#removing-packages ** Affects: gnome-user-docs (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960753 Title: Remove the gnome-user-guide binary from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1960753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
