[Bug 1569289] Re: glance should support the root-tar disk format
This was dropped in 2:29.0.0~rc1-0ubuntu1: * d/p/add-root-tar-support.patch: Drop as lxd driver is no longer supported in Nova. So I guess we won't fix this. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569289 Title: glance should support the root-tar disk format To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1569289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103609] Re: Extension crashes and forces log out on lock screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: multimonitor noble ** 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/2103609 Title: Extension crashes and forces log out on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2103609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth crashes with SIGSEGV if Nvidia 570.124 is installed
Please follow steps 2 and 3 in comment #2. ** Tags added: nvidia ** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #288 https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/288 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth crashes with SIGSEGV in ply_terminal_set_disabled_input() if Nvidia 570.124 is installed To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth crashes with SIGSEGV if Nvidia 570.124 is installed
Your stack trace seems to match this one: https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/288 ** Also affects: plymouth via https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/288 Importance: Unknown Status: Unknown ** Summary changed: - plymouth crashes with SIGSEGV if Nvidia 570.124 is installed + plymouth crashes with SIGSEGV in ply_terminal_set_disabled_input() if Nvidia 570.124 is installed ** Changed in: plymouth (Ubuntu) Status: Incomplete => Confirmed ** Changed in: plymouth (Ubuntu) Importance: Undecided => High ** Bug watch added: Red Hat Bugzilla #2350956 https://bugzilla.redhat.com/show_bug.cgi?id=2350956 ** Also affects: plymouth (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2350956 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/2103533 Title: plymouth crashes with SIGSEGV in ply_terminal_set_disabled_input() if Nvidia 570.124 is installed To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078467] Re: [SRU] App armor crashes on aa-enforce due to "Profile not found"
The attachment "lp_2078467_noble.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078467 Title: [SRU] App armor crashes on aa-enforce due to "Profile not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2078467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920201] Re: [MIR] oem-somerville-stantler-meta
Hello Shih-Yuan, or anyone else affected, Accepted oem-somerville-stantler-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-somerville-stantler- meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal ** Also affects: oem-somerville-stantler-meta (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu ** Also affects: oem-somerville-stantler-meta (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/1920201 Title: [MIR] oem-somerville-stantler-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1992415] Re: [MIR] oem-somerville-spearow-meta
Hello OEM, or anyone else affected, Accepted oem-somerville-spearow-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-somerville-spearow- meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: oem-somerville-spearow-meta (Ubuntu) Importance: Undecided Status: New ** Tags added: verification-needed verification-needed-focal ** No longer affects: ubuntu ** Also affects: oem-somerville-spearow-meta (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: oem-somerville-spearow-meta (Ubuntu Focal) Status: New => Fix Committed ** Changed in: oem-somerville-spearow-meta (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/1992415 Title: [MIR] oem-somerville-spearow-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1992415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103370] Re: [p-m] Please demote phpunit reverse dependencies with failing autopkgtests
** Description changed: phpunit has been in plucky-proposed for 32 days now, and has a handful of reverse dependencies waiting for it to migrate (this list is not clearly stated by Britney.) All of these packages have been removed from Debian Testing. I have attached all of the relevant RC bugs. There seems to be two options here, please proceed with the preferable option: - - Ask the Release Team to explicitly skiptest phpunit so it migrates, regressing all these packages in the release pocket. - - Ask the Archive Administrators to demote all of these packages to proposed, which allows phpunit to migrate, but might allow some or all of the demoted packages to re-migrate if the block-proposed tag is not set on this bug. + - Ask the Release Team to explicitly skiptest phpunit so it migrates, regressing all these packages in the release pocket. + - Ask the Archive Administrators to demote all of these packages to proposed, which allows phpunit to migrate, but might allow some or all of the demoted packages to re-migrate if the block-proposed tag is not set on this bug. Please only mark phpunit as Fix Release once it's migrated. Thank you in advance. + + $ for i in libphp-swiftmailer pdepend php-codesniffer php-fxsl php-gettext php-sabredav php-sql-formatter phpcpd phploc phpmd; do reverse-depends -lb src:$i >> /tmp/phpunit-rms; reverse-depends -l src:$i >> /tmp/phpunit-rms; done && cat /tmp/phpunit-rms | sort -u >> /tmp/phpunit-binpkg-rdeps && rm /tmp/phpunit-rms && for i in $(cat /tmp/phpunit-binpkg-rdeps); do out=$(apt show "$i" 2>/dev/null); echo "$out" | grep -q '^Source:' && echo "$out" | sed -n 's/^Source: //p' >> /tmp/phpunit-rms || echo "$out" | sed -n 's/^Package: //p' >> /tmp/phpunit-rms; done && cat /tmp/phpunit-rms | sort -u && rm /tmp/phpunit-rms + phing (added to list) + php-fdomdocument (added to list) + php-fxsl (in list) + phpmd (in list) + tt-rss (added to list) + zabbix (added to list) ** Also affects: phing (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1091520 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091520 ** Also affects: phing (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091520 Importance: Unknown Status: Unknown ** Changed in: phing (Ubuntu) Importance: Undecided => High ** Changed in: phing (Ubuntu) Status: New => Triaged ** Also affects: php-fdomdocument (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #1082448 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082448 ** Also affects: php-fdomdocument (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082448 Importance: Unknown Status: Unknown ** Changed in: php-fdomdocument (Ubuntu) Importance: Undecided => High ** Changed in: php-fdomdocument (Ubuntu) Status: New => Triaged ** Bug watch added: Debian Bug tracker #1021656 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021656 ** Also affects: tt-rss (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021656 Importance: Unknown Status: Unknown ** Also affects: tt-rss (Ubuntu) Importance: Undecided Status: New ** Changed in: tt-rss (Ubuntu) Importance: Undecided => High ** Changed in: tt-rss (Ubuntu) Status: New => Triaged ** Description changed: phpunit has been in plucky-proposed for 32 days now, and has a handful of reverse dependencies waiting for it to migrate (this list is not clearly stated by Britney.) All of these packages have been removed from Debian Testing. I have attached all of the relevant RC bugs. There seems to be two options here, please proceed with the preferable option: - Ask the Release Team to explicitly skiptest phpunit so it migrates, regressing all these packages in the release pocket. - Ask the Archive Administrators to demote all of these packages to proposed, which allows phpunit to migrate, but might allow some or all of the demoted packages to re-migrate if the block-proposed tag is not set on this bug. Please only mark phpunit as Fix Release once it's migrated. Thank you in advance. $ for i in libphp-swiftmailer pdepend php-codesniffer php-fxsl php-gettext php-sabredav php-sql-formatter phpcpd phploc phpmd; do reverse-depends -lb src:$i >> /tmp/phpunit-rms; reverse-depends -l src:$i >> /tmp/phpunit-rms; done && cat /tmp/phpunit-rms | sort -u >> /tmp/phpunit-binpkg-rdeps && rm /tmp/phpunit-rms && for i in $(cat /tmp/phpunit-binpkg-rdeps); do out=$(apt show "$i" 2>/dev/null); echo "$out" | grep -q '^Source:' && echo "$out" | sed -n 's/^Source: //p' >> /tmp/phpunit-rms || echo "$out" | sed -n 's/^Package: //p' >> /tmp/phpunit-rms; done && cat /tmp/phpunit-rms | sort -u && rm /tmp/phpunit-rms phing (added to list) php-fdomdocument (added to list) php-fxsl (in list) phpmd (in list) tt-rss (added to list) zabbix
[Bug 2073676] Re: after update of kernel HDMI audio is not working
I have found out that the docking station (Dell) was the root cause for the problem. This has now been replaced with a new. This topic can be closed. ** Description changed: after update of kernel the Audio output via dock - HDMI is no longer working. the display is showing that the audio i receving but there is no audio. If I switch to normal speakers on the laptop the audio is working. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-38-generic 6.8.0-38.38 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 20 18:45:44 2024 InstallationDate: Installed on 2024-03-11 (131 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) - MachineType: LENOVO 20XK007DMX + ProcEnviron: LANG=da_DK.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic root=UUID=735a8489-6e61-48ac-a281-46d43115ef53 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-38-generic N/A linux-backports-modules-6.8.0-38-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-05-22 (59 days ago) dmi.bios.date: 10/30/2023 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET55W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XK007DMX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 - dmi.modalias: dmi:bvnLENOVO:bvrR1MET55W(1.25):bd10/30/2023:br1.25:efr1.25:svnLENOVO:pn20XK007DMX:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XK007DMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XK_BU_Think_FM_ThinkPadT14Gen2a: - dmi.product.family: ThinkPad T14 Gen 2a - dmi.product.name: 20XK007DMX + dmi.modalias: dmi.product.family: ThinkPad T14 Gen 2a dmi.product.sku: LENOVO_MT_20XK_BU_Think_FM_ThinkPad T14 Gen 2a dmi.product.version: ThinkPad T14 Gen 2a dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073676 Title: after update of kernel HDMI audio is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103526] Re: [FFe] Allow 'AptSolverDump' field for apt solver 3 reports
This bug was fixed in the package whoopsie - 0.2.79 --- whoopsie (0.2.79) plucky; urgency=medium * Enable `AptSolverDump` field (LP: #2103526). * Add some additional logging for more discoverable behavior. * Update maintainer, since in practice, I'm now in charge. * lintian: aliased-location file-without-copyright-information missing-build-dependency-for-dh-addon * Raise debhelper-compat to 13. -- Florent 'Skia' Jacquet Wed, 12 Mar 2025 17:09:36 +0100 ** Changed in: whoopsie (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/2103526 Title: [FFe] Allow 'AptSolverDump' field for apt solver 3 reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2103526/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2093624] Re: thousands messages "budgie-wm[2928]: Can't update stage views actor [:0x56457fdc98f0] is on because it needs an allocation"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: budgie-desktop (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/2093624 Title: thousands messages "budgie-wm[2928]: Can't update stage views actor [:0x56457fdc98f0] is on because it needs an allocation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2093624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065685] Re: aa-logprof fails with 'runbindable' error
This issue is fixed by 1f33fc9b29c174698fdf0116a4a9f50680ec4fdb, however it is not included in the 4.0 branch used by noble. Oracular and Plucky are not affected by this bug. To fix that locally, you can either: - Replace `mount "" -> "/tmp/",` by `mount -> "/tmp/",` (and similarly for other empty mount sources), as pointed out by @jyrg. - Use a more recent version of AppArmor that includes this commit (or cherry-pick it). @jjohansen Do you think it is worth applying a fix for this in noble? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065685 Title: aa-logprof fails with 'runbindable' error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103524] Re: lsblk apparmor profile denies block device lookup on Azure
** Tags added: sec-5988 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103524 Title: lsblk apparmor profile denies block device lookup on Azure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2103524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2093624] Re: thousands messages "budgie-wm[2928]: Can't update stage views actor [:0x56457fdc98f0] is on because it needs an allocation"
I get this bug too in Ubuntu 24.04, and freezes the browser after switch any browser video to fullscreen, either Youtube, or other video sites. I have the standard Ubuntu which uses gnome-shell, but the bug happens with budgie-wm as reported here. As far as I remember, I did not have this bug on Ubuntu 23.04 or 23.10 Also happens with mpv video player, whenever fullscreen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2093624 Title: thousands messages "budgie-wm[2928]: Can't update stage views actor [:0x56457fdc98f0] is on because it needs an allocation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2093624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1051863] Re: atftpd: can't bind port
[Expired for atftp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: atftp (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/1051863 Title: atftpd: can't bind port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atftp/+bug/1051863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2101889] Re: MIR: node-mathjax-full, node-mj-context-menu
I'm in agreement; it seems much better to demote sphinx-doc in this case. Thank you both! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2101889 Title: MIR: node-mathjax-full, node-mj-context-menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/node-mathjax-full/+bug/2101889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2102097] Re: [SRU] Backport WPA2-PSK-SHA256 support to Ubuntu 22.04
The fixes for Oracular and Noble will be tracked as part of a full- version backport in LP: #2103603. ** Changed in: netplan.io (Ubuntu Oracular) Status: New => Invalid ** Changed in: netplan.io (Ubuntu Noble) 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/2102097 Title: [SRU] Backport WPA2-PSK-SHA256 support to Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2102097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103420] Re: Security issue with libsaml12
The attachment "debdiff for noble" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2103420 Title: Security issue with libsaml12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensaml/+bug/2103420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2102236] Re: plucky/s390x does not come up after kernel update + reboot, due to udev rules missing in initrd
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2102236 Title: plucky/s390x does not come up after kernel update + reboot, due to udev rules missing in initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2102236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103663] Re: set -x in apparmor.postinst
Fix uploaded in https://launchpad.net/ubuntu/+source/apparmor/4.1.0~beta5-0ubuntu10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103663 Title: set -x in apparmor.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2103663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103668] [NEW] Onionshare fatally crashes after Tor connection (fix seems easy)
Public bug reported:
Source package: onionshare
1) Ubuntu release version:
Description:Ubuntu 24.04.2 LTS
Release:24.04
2) Version of the package:
onionshare:
Candidate: 2.6-6ubuntu1
Version table:
2.6-6ubuntu1 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
3) What I expected to happen: Onionshare is able to start after
connecting to the Tor network.
4) What happened instead:
After connecting to the Tor network, Onionshare crashes:
```
Connecting to the Tor network: 100% - Done
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/onionshare/tor_connection.py", line 180,
in run
self.parent.onion.connect(self.settings, False, self._tor_status_update)
File "/usr/lib/python3/dist-packages/onionshare_cli/onion.py", line 661, in
connect
self.supports_v3_onions = self.tor_version >= Version("0.3.5.7")
^^
TypeError: '>=' not supported between instances of 'str' and 'Version'
```
Corresponding GitHub issue with response from maintainer:
Specifically:
> I think the Ubuntu maintainers accidentally introduced this bug in
their last change (see latest changelog entry at
https://changelogs.ubuntu.com/changelogs/pool/universe/o/onionshare/onionshare_2.6-6ubuntu1/changelog
"Use packaging.version instead of distutils.version.")
** Affects: onionshare (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/2103668
Title:
Onionshare fatally crashes after Tor connection (fix seems easy)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/onionshare/+bug/2103668/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth crashes with SIGSEGV if Nvidia 570.124 is installed
The only hint of a stack trace I can see is: https://launchpadlibrarian.net/782730377/IMG_20250319_071337923_HDR.jpg but your logs confirm plymouth is crashing with signal 11. ** Summary changed: - plymouth library crashes and doesn't show splash screen + plymouth crashes with SIGSEGV if Nvidia 570.124 is installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth crashes with SIGSEGV in ply_terminal_set_disabled_input() if Nvidia 570.124 is installed To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103682] Re: ubuntu_btrfs_kernel_fixes failed on N-oem-6.11
** Also affects: linux-oem-6.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.11 (Ubuntu Noble) 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/2103682 Title: ubuntu_btrfs_kernel_fixes failed on N-oem-6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2103682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103682] Re: ubuntu_btrfs_kernel_fixes failed on N-oem-6.11
Here is the output of a manual test against -1016: Invoking test 671415b7db49f62896f0b6d50fc4f312a0512983 fix 671415b7db49f62896f0b6d50fc4f312a0512983 Btrfs: fix deadlock caused by the nested chunk allocation Steps to reproduce: # mkfs.btrfs -m raid1 # btrfstune -S 1 # mount # btrfs device add # mount -o remount,rw # dd if=/dev/zero of=/tmpfile bs=1M count=1 Deadlock happened. btrfs-progs v6.6.3 See https://btrfs.readthedocs.io for more information. Performing full device TRIM /dev/loop1 (1.00GiB) ... Performing full device TRIM /dev/loop0 (1.00GiB) ... NOTE: several default settings have changed in version 5.15, please make sure this does not affect your deployments: - DUP for metadata (-m dup) - enabled no-holes (-O no-holes) - enabled free-space-tree (-R free-space-tree) Label: (null) UUID: 17295867-10f8-4117-b76b-9534f081ce6d Node size: 16384 Sector size:4096 Filesystem size:2.00GiB Block group profiles: Data: single8.00MiB Metadata: RAID1 102.38MiB System: RAID1 8.00MiB SSD detected: no Zoned device: no Incompat features: extref, skinny-metadata, no-holes, free-space-tree Runtime features: free-space-tree Checksum: crc32c Number of devices: 2 Devices: IDSIZE PATH 1 1.00GiB /dev/loop0 2 1.00GiB /dev/loop1 WARNING: Multiple block group profiles detected, see 'man btrfs(5)' WARNING:Metadata: single, raid1 Performing full device TRIM /dev/loop2 (1.00GiB) ... Performing full device TRIM /dev/loop3 (1.00GiB) ... PASS: 671415b7db49f62896f0b6d50fc4f312a0512983 dmesg output: [ 142.776408] Invoking test 671415b7db49f62896f0b6d50fc4f312a0512983 [ 142.787042] loop0: detected capacity change from 0 to 2097152 [ 142.789696] loop1: detected capacity change from 0 to 2097152 [ 142.794442] loop2: detected capacity change from 0 to 2097152 [ 142.798575] loop3: detected capacity change from 0 to 2097152 [ 142.876178] BTRFS: device fsid 17295867-10f8-4117-b76b-9534f081ce6d devid 1 transid 6 /dev/loop0 (7:0) scanned by mkfs.btrfs (1382) [ 142.876226] BTRFS: device fsid 17295867-10f8-4117-b76b-9534f081ce6d devid 2 transid 6 /dev/loop1 (7:1) scanned by mkfs.btrfs (1382) [ 142.910940] BTRFS info (device loop0): first mount of filesystem 17295867-10f8-4117-b76b-9534f081ce6d [ 142.910959] BTRFS info (device loop0): using crc32c (crc32c-intel) checksum algorithm [ 142.910964] BTRFS info (device loop0): using free-space-tree [ 142.948708] BTRFS info (device loop0): relocating block group 255197184 flags system [ 142.955726] BTRFS info (device loop0): relocating block group 22020096 flags system|raid1 [ 142.963884] BTRFS info (device loop0): disk added /dev/loop2 [ 142.980313] BTRFS info (device loop0): disk added /dev/loop3 [ 142.996461] BTRFS info (device loop0): last unmount of filesystem 7620511e-f685-487f-8ff0-dc63c88670a8 [ 143.007859] Test 671415b7db49f62896f0b6d50fc4f312a0512983 returned 0 ** Tags added: 6.11 noble oem sru-20250210 ubuntu-btrfs-kernel-fixes ** Description changed: Label: (null) UUID: 95a500a1-e39f-4257-97c0-c0580bdbe736 Node size: 16384 Sector size:4096 Filesystem size:2.00GiB Block group profiles: - Data: single8.00MiB - Metadata: RAID1 102.38MiB - System: RAID1 8.00MiB + Data: single8.00MiB + Metadata: RAID1 102.38MiB + System: RAID1 8.00MiB SSD detected: no Zoned device: no Incompat features: extref, skinny-metadata, no-holes, free-space-tree Runtime features: free-space-tree Checksum: crc32c Number of devices: 2 Devices: -IDSIZE PATH - 1 1.00GiB /dev/loop0 - 2 1.00GiB /dev/loop1 + IDSIZE PATH + 1 1.00GiB /dev/loop0 + 2 1.00GiB /dev/loop1 ERROR: error adding device '/dev/loop3': Read-only file system WARNING: Multiple block group profiles detected, see 'man btrfs(5)' WARNING:Metadata: single, raid1 Performing full device TRIM /dev/loop2 (1.00GiB) ... Performing full device TRIM /dev/loop3 (1.00GiB) ... btrfs device add /dev/loop2 /dev/loop3 /tmp/mnt-671415b7db49f62896f0b6d50fc4f312a0512983 failed ... - Steps to reproduce: - # mkfs.btrfs -m raid1 - # btrfstune -S 1 - # mount - # btrfs device add - # mount -o remount,rw - # dd if=/dev/zero of=/tmpfile bs=1M count=1 - Deadlock happened. - - btrfs-progs v6.6.3 - See https://btrfs.readthedocs.io for more information. - - Performing full device TRIM /dev/loop0 (1.00GiB) ... - Performing full device TRIM /dev/loop1 (1.00GiB)
[Bug 1920201] Re: [MIR] oem-somerville-stantler-meta
** Changed in: oem-somerville-stantler-meta (Ubuntu Focal) Status: New => Fix Committed ** Changed in: oem-somerville-stantler-meta (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/1920201 Title: [MIR] oem-somerville-stantler-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103596] [NEW] Activating a LVM RAID-1 volume causes a kernel BUG: "detected buffer overflow in strlen"
Public bug reported: I have a server with four disks (two HDDs, two SSDs) that use both traditional software RAID (md) and LVM with multiple volumes, most of which use LVM raid1. I've recently upgraded it to Ubuntu 22.04 LTS. The problem: activating one of the LVM logical volumes causes a Mar 19 12:18:58 fridge kernel: md/raid1:mdX: active with 2 out of 2 mirrors Mar 19 12:18:58 fridge kernel: detected buffer overflow in strlen Mar 19 12:18:58 fridge kernel: [ cut here ] Mar 19 12:18:58 fridge kernel: kernel BUG at lib/string.c:1165! Mar 19 12:18:58 fridge kernel: invalid opcode: [#1] SMP PTI Mar 19 12:18:58 fridge kernel: CPU: 1 PID: 132407 Comm: lvchange Not tainted 5.15.0-134-generic #145-Ubuntu Mar 19 12:18:58 fridge kernel: Hardware name: Gigabyte Technology Co., Ltd. H370M-DS3H/H370M DS3H-CF, BIOS F2 04/20/2018 Mar 19 12:18:58 fridge kernel: RIP: 0010:fortify_panic+0x13/0x15 Mar 19 12:18:59 fridge kernel: Code: 5c 44 88 e8 40 b5 fc ff 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 55 48 89 fe 48 c7 c7 e0 5c 44 88 48 89 e5 e8 1e b5 fc ff <0f> 0b 41 0f b6 f5 48 c7 c7 10 73 ec 88 e8 cb ee 93 ff 48 8b 45 e0 Mar 19 12:18:59 fridge kernel: RSP: 0018:be47c178f9f8 EFLAGS: 00010246 Mar 19 12:18:59 fridge kernel: RAX: 0022 RBX: 9772c4cd7058 RCX: 0027 Mar 19 12:18:59 fridge kernel: RDX: RSI: 0001 RDI: 97761e460580 Mar 19 12:18:59 fridge kernel: RBP: be47c178f9f8 R08: 0003 R09: 00cdcdcd Mar 19 12:18:59 fridge kernel: R10: 880a7980 R11: 9772cba90320 R12: Mar 19 12:18:59 fridge kernel: R13: 9774a3d19a00 R14: 9773dfa2ef00 R15: Mar 19 12:18:59 fridge kernel: FS: 7f2f2cbc58c0() GS:97761e44() knlGS: Mar 19 12:18:59 fridge kernel: CS: 0010 DS: ES: CR0: 80050033 Mar 19 12:18:59 fridge kernel: CR2: 7fd43877ce24 CR3: 000103d92005 CR4: 003726e0 Mar 19 12:18:59 fridge kernel: DR0: DR1: DR2: Mar 19 12:18:59 fridge kernel: DR3: DR6: fffe0ff0 DR7: 0400 Mar 19 12:18:59 fridge kernel: Call Trace: Mar 19 12:18:59 fridge kernel: Mar 19 12:18:59 fridge kernel: ? show_trace_log_lvl+0x1d6/0x2ea Mar 19 12:18:59 fridge kernel: ? show_trace_log_lvl+0x1d6/0x2ea Mar 19 12:18:59 fridge kernel: ? md_bitmap_read_sb.cold+0x45/0xef Mar 19 12:18:59 fridge kernel: ? show_regs.part.0+0x23/0x29 Mar 19 12:18:59 fridge kernel: ? __die_body.cold+0x8/0xd Mar 19 12:18:59 fridge kernel: ? __die+0x2b/0x37 Mar 19 12:18:59 fridge kernel: ? die+0x30/0x60 Mar 19 12:18:59 fridge kernel: ? do_trap+0xbe/0x100 Mar 19 12:18:59 fridge kernel: ? do_error_trap+0x6f/0xb0 Mar 19 12:18:59 fridge kernel: ? fortify_panic+0x13/0x15 Mar 19 12:18:59 fridge kernel: ? exc_invalid_op+0x53/0x70 Mar 19 12:18:59 fridge kernel: ? fortify_panic+0x13/0x15 Mar 19 12:18:59 fridge kernel: ? asm_exc_invalid_op+0x1b/0x20 Mar 19 12:18:59 fridge kernel: ? fortify_panic+0x13/0x15 Mar 19 12:18:59 fridge kernel: ? fortify_panic+0x13/0x15 Mar 19 12:18:59 fridge kernel: md_bitmap_read_sb.cold+0x45/0xef Mar 19 12:18:59 fridge kernel: md_bitmap_create+0x182/0x250 Mar 19 12:18:59 fridge kernel: md_run+0x3e0/0xa30 Mar 19 12:18:59 fridge kernel: ? super_validate+0x124/0x1a0 [dm_raid] Mar 19 12:18:59 fridge kernel: raid_ctr+0x4af/0xbba [dm_raid] Mar 19 12:18:59 fridge kernel: dm_table_add_target+0x17c/0x370 Mar 19 12:18:59 fridge kernel: table_load+0x127/0x350 Mar 19 12:18:59 fridge kernel: ctl_ioctl+0x1e3/0x320 Mar 19 12:18:59 fridge kernel: dm_ctl_ioctl+0xe/0x20 Mar 19 12:18:59 fridge kernel: __x64_sys_ioctl+0x92/0xd0 Mar 19 12:18:59 fridge kernel: x64_sys_call+0x1e5f/0x1fa0 Mar 19 12:18:59 fridge kernel: do_syscall_64+0x56/0xb0 Mar 19 12:18:59 fridge kernel: ? syscall_exit_to_user_mode+0x2c/0x50 Mar 19 12:18:59 fridge kernel: ? do_syscall_64+0x63/0xb0 Mar 19 12:18:59 fridge kernel: ? do_syscall_64+0x63/0xb0 Mar 19 12:18:59 fridge kernel: ? exit_to_user_mode_prepare+0x96/0xb0 Mar 19 12:18:59 fridge kernel: ? syscall_exit_to_user_mode+0x2c/0x50 Mar 19 12:18:59 fridge kernel: ? do_syscall_64+0x63/0xb0 Mar 19 12:18:59 fridge kernel: ? do_syscall_64+0x63/0xb0 Mar 19 12:18:59 fridge kernel: ? do_syscall_64+0x63/0xb0 Mar 19 12:18:59 fridge kernel: entry_SYSCALL_64_after_hwframe+0x6c/0xd6 Mar 19 12:18:59 fridge kernel: RIP: 0033:0x7f2f2d0cc94f Mar 19 12:18:59 fridge kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <41> 89 c0 3d 00 f0 ff ff 77 1f 48 8b 44 24 18 64 48 2b 04 25 28 00 Mar 19 12:18:59 fridge kernel: RSP: 002b:7ffc4ff09db0 EFLAGS: 0246 ORIG_RAX: 0010 Mar 19 12:18:59 fridge kernel: RAX: ffda RBX: 5597949ef960 RCX: 7f2f2d0cc94f Mar 19 12:18:59 fridge kernel: RDX: 5597b26b2820 RSI: 0
[Bug 2100488] Re: New upstream release 570.124.04
*** This bug is a duplicate of bug 2103552 *** https://bugs.launchpad.net/bugs/2103552 ** This bug has been marked a duplicate of bug 2103552 New upstream release 570.133.07 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100488 Title: New upstream release 570.124.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2100488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103552] Re: New upstream release 570.133.07
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-570 (Ubuntu Jammy) 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/2103552 Title: New upstream release 570.133.07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2103552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103552] Re: New upstream release 570.133.07
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-570 (Ubuntu Focal) 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/2103552 Title: New upstream release 570.133.07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2103552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103552] Re: New upstream release 570.133.07
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-570 (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/2103552 Title: New upstream release 570.133.07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2103552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103552] Re: New upstream release 570.133.07
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-570 (Ubuntu Noble) 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/2103552 Title: New upstream release 570.133.07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-570/+bug/2103552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933451] Re: [MIR] oem-somerville-tangela-jsl-meta
Hello OEM, or anyone else affected, Accepted oem-somerville-tangela-jsl-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-somerville-tangela-jsl- meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: oem-somerville-tangela-jsl-meta (Ubuntu) Importance: Undecided Status: New ** Tags added: verification-needed verification-needed-focal ** No longer affects: ubuntu ** Also affects: oem-somerville-tangela-jsl-meta (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: oem-somerville-tangela-jsl-meta (Ubuntu Focal) Status: New => Fix Committed ** Changed in: oem-somerville-tangela-jsl-meta (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/1933451 Title: [MIR] oem-somerville-tangela-jsl-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937224] Re: [MIR] oem-somerville-ygritte-meta
Hello OEM, or anyone else affected, Accepted oem-somerville-ygritte-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-somerville-ygritte- meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: oem-somerville-ygritte-meta (Ubuntu) Importance: Undecided Status: New ** Tags added: verification-needed verification-needed-focal ** No longer affects: ubuntu ** Also affects: oem-somerville-ygritte-meta (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: oem-somerville-ygritte-meta (Ubuntu Focal) Status: New => Fix Committed ** Changed in: oem-somerville-ygritte-meta (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/1937224 Title: [MIR] oem-somerville-ygritte-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2092806] Re: Xubuntu default wallpaper not respected by Xfdesktop 4.20
This bug was fixed in the package xfdesktop4 - 4.20.1-1ubuntu1 --- xfdesktop4 (4.20.1-1ubuntu1) plucky; urgency=medium * d/control, d/rules: - Override default wallpaper to xubuntu-wallpaper.png (LP: #2092806) -- Sean Davis Wed, 19 Mar 2025 22:59:25 -0400 ** Changed in: xfdesktop4 (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/2092806 Title: Xubuntu default wallpaper not respected by Xfdesktop 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/2092806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100965] Re: update manager doesn't reboot the system as requested
This is fixed in the development version (25.04). If someone encounters the issue in an older Ubuntu release, please comment here so we can prepare an SRU. ** Changed in: update-manager (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/2100965 Title: update manager doesn't reboot the system as requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2100965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2088977] Re: [FFe] Enable DTrace in php8.4
This bug was fixed in the package php8.4 - 8.4.5-1ubuntu1 --- php8.4 (8.4.5-1ubuntu1) plucky; urgency=medium * d/rules: enable DTrace (LP: #2088977) -- Athos Ribeiro Mon, 17 Mar 2025 17:35:32 -0300 ** Changed in: php8.4 (Ubuntu) Status: Triaged => 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/2088977 Title: [FFe] Enable DTrace in php8.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php8.3/+bug/2088977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920198] Re: [MIR] oem-somerville-seadra-rkl-meta
Hello Shih-Yuan, or anyone else affected, Accepted oem-somerville-seadra-rkl-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-somerville-seadra-rkl- meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920198 Title: [MIR] oem-somerville-seadra-rkl-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103673] [NEW] Black screen after login
Public bug reported: OS: Ubuntu Kylin Daily 20250319 Package: peony 4.0.0.1-1 Getting a black screen after login, and the peony-qt-desktop process is present but appears frozen. ** Affects: peony (Ubuntu) Importance: Critical Assignee: handsome_feng (feng-kylin) Status: In Progress ** Changed in: peony (Ubuntu) Assignee: (unassigned) => handsome_feng (feng-kylin) ** Changed in: peony (Ubuntu) Importance: Undecided => Critical ** Changed in: peony (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103673 Title: Black screen after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/peony/+bug/2103673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103370] Re: [p-m] Please demote phpunit reverse dependencies with failing autopkgtests
> NACK from ubuntu-release, we don't want to regress these packages in the release, they should be removed instead. Got it, thanks! I kind of figured that would be the preferable route here. :) > I think these packages should just be removed from plucky altogether. If this is agreeable, let's do it. > Please also paste your analysis of the reverse-dependencies of the packages to be removed in this bug Check the bug description shortly, all of that information should be present now. > https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Removing_Packages (I half-expected this to actually show me a really good, clean way to get rdeps, but I'm confused on why I was linked this, given that it was more of a tentative ask to start.) > PLease resubscribe us once the rdep picture gets clearer :) Will do, thanks. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103370 Title: [p-m] Please demote phpunit reverse dependencies with failing autopkgtests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libphp-swiftmailer/+bug/2103370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103680] [NEW] System hangs when running the memory stress test
Public bug reported: [Impact] While running the memory stress test, the system becomes unresponsive. [Fix] The commit in v6.11-rc1 introduce the issue. 4e63aeb5d010 blk-wbt: don't throttle swap writes in direct reclaim And we are seeking for help from the patch owner and other developers on the mailing list https://lkml.org/lkml/2025/3/20/90 Currently, we have to revert this commit, because this issue happens on many platforms. [Test] Run the following command on the machine with kernel version greater or equal to v6.11 sudo stress-ng --aggressive --verify --timeout 300 --mmapmany 0 It should finish the test in 5mins. [Where problems could occur] From the commit message reverts this commit may trigger a hang "When a process holds a lock to allocate a free page, and enters direct reclaim because there is no free memory, then it might trigger a hung due to the wbt throttling that causes other processes to fail to get the lock." ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-oem-6.11 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.11 (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Tags: jira-stella-868 oem-priority stella ** Also affects: linux-oem-6.11 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-oem-6.11 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.11 (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: jira-stella-868 oem-priority stella ** Description changed: [Impact] While running the memory stress test, the system becomes unresponsive. [Fix] The commit in v6.11-rc1 introduce the issue. 4e63aeb5d010 blk-wbt: don't throttle swap writes in direct reclaim - And we are seeking help from the patch owner and other developers on the mailing list + And we are seeking for help from the patch owner and other developers on the mailing list https://lkml.org/lkml/2025/3/20/90 Currently, we have to revert this commit, because this issue happens on many platforms. [Test] Run the following command on the machine with kernel version greater or equal to v6.11 -sudo stress-ng --aggressive --verify --timeout 300 --mmapmany 0 + sudo stress-ng --aggressive --verify --timeout 300 --mmapmany 0 It should finish the test in 5mins. [Where problems could occur] From the commit message reverts this commit may trigger a hang "When a process holds a lock to allocate a free page, and enters direct reclaim because there is no free memory, then it might trigger a hung due to the wbt throttling that causes other processes to fail to get the lock." ** Changed in: linux-oem-6.11 (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/2103680 Title: System hangs when running the memory stress test To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2103680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103681] [NEW] [p-m] Please remove tree-sitter from the proposed pocket
Public bug reported: It seems to be a better idea to back out the ongoing tree-sitter transition in the proposed pocket than to progress it further and risk release pocket breakage. Please remove the following packages only from plucky's proposed pocket; they should stay as-is in the release pocket, please: neovim tree-sitter tree-sitter-c tree-sitter-lua tree-sitter-query tree-sitter-sdml tree-sitter-vim tree-sitter-vimdoc I could certainly attempt to review the reverse-dependencies by hand, but since any affected reverse depends will have stayed in the proposed pocket. a no-change rebuild or a further removal might be necessary. `reverse-depends` doesn't support the proposed pocket (and it's a known bug), so while I can script it, on this one could we maybe let Britney tell us if there's a straggler? Thanks in advance. ** Affects: neovim (Ubuntu) Importance: High Status: Triaged ** Affects: tree-sitter (Ubuntu) Importance: High Status: Triaged ** Affects: tree-sitter-c (Ubuntu) Importance: High Status: Triaged ** Affects: tree-sitter-lua (Ubuntu) Importance: High Status: Triaged ** Affects: tree-sitter-query (Ubuntu) Importance: High Status: Triaged ** Affects: tree-sitter-sdml (Ubuntu) Importance: High Status: Triaged ** Affects: tree-sitter-vim (Ubuntu) Importance: High Status: Triaged ** Affects: tree-sitter-vimdoc (Ubuntu) Importance: High Status: Triaged ** Tags: ftbfs update-excuse ** Also affects: neovim (Ubuntu) Importance: Undecided Status: New ** Also affects: tree-sitter-c (Ubuntu) Importance: Undecided Status: New ** Also affects: tree-sitter-lua (Ubuntu) Importance: Undecided Status: New ** Also affects: tree-sitter-query (Ubuntu) Importance: Undecided Status: New ** Also affects: tree-sitter-sdml (Ubuntu) Importance: Undecided Status: New ** Also affects: tree-sitter-vim (Ubuntu) Importance: Undecided Status: New ** Also affects: tree-sitter-vimdoc (Ubuntu) Importance: Undecided Status: New ** Changed in: neovim (Ubuntu) Status: New => Triaged ** Changed in: tree-sitter-vim (Ubuntu) Status: New => Triaged ** Changed in: tree-sitter-query (Ubuntu) Status: New => Triaged ** Changed in: tree-sitter-query (Ubuntu) Importance: Undecided => High ** Changed in: tree-sitter-vim (Ubuntu) Importance: Undecided => High ** Changed in: tree-sitter-c (Ubuntu) Status: New => Triaged ** Changed in: tree-sitter-lua (Ubuntu) Status: New => Triaged ** Changed in: tree-sitter-sdml (Ubuntu) Status: New => Triaged ** Changed in: tree-sitter-vimdoc (Ubuntu) Status: New => Triaged ** Changed in: neovim (Ubuntu) Importance: Undecided => High ** Changed in: tree-sitter-c (Ubuntu) Importance: Undecided => High ** Changed in: tree-sitter-sdml (Ubuntu) Importance: Undecided => High ** Changed in: tree-sitter-lua (Ubuntu) Importance: Undecided => High ** Changed in: tree-sitter-vimdoc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103681 Title: [p-m] Please remove tree-sitter from the proposed pocket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neovim/+bug/2103681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103681] Re: [p-m] Please remove tree-sitter from the proposed pocket
Removing packages from plucky-proposed: neovim 0.10.4-7 in plucky tree-sitter 0.22.6-6 in plucky tree-sitter-c 0.21.3-4 in plucky librust-tree-sitter-c-dev 0.21.3-4 in plucky amd64 librust-tree-sitter-c-dev 0.21.3-4 in plucky arm64 librust-tree-sitter-c-dev 0.21.3-4 in plucky armhf librust-tree-sitter-c-dev 0.21.3-4 in plucky ppc64el librust-tree-sitter-c-dev 0.21.3-4 in plucky s390x tree-sitter-c-src 0.21.3-4 in plucky amd64 tree-sitter-c-src 0.21.3-4 in plucky arm64 tree-sitter-c-src 0.21.3-4 in plucky armhf tree-sitter-c-src 0.21.3-4 in plucky i386 tree-sitter-c-src 0.21.3-4 in plucky ppc64el tree-sitter-c-src 0.21.3-4 in plucky riscv64 tree-sitter-c-src 0.21.3-4 in plucky s390x tree-sitter-lua 0.1.0-3 in plucky librust-tree-sitter-lua-dev 0.1.0-3 in plucky amd64 librust-tree-sitter-lua-dev 0.1.0-3 in plucky arm64 librust-tree-sitter-lua-dev 0.1.0-3 in plucky armhf librust-tree-sitter-lua-dev 0.1.0-3 in plucky ppc64el librust-tree-sitter-lua-dev 0.1.0-3 in plucky s390x tree-sitter-lua-src 0.1.0-3 in plucky amd64 tree-sitter-lua-src 0.1.0-3 in plucky arm64 tree-sitter-lua-src 0.1.0-3 in plucky armhf tree-sitter-lua-src 0.1.0-3 in plucky i386 tree-sitter-lua-src 0.1.0-3 in plucky ppc64el tree-sitter-lua-src 0.1.0-3 in plucky riscv64 tree-sitter-lua-src 0.1.0-3 in plucky s390x tree-sitter-query 0.4.0-3 in plucky librust-tree-sitter-query-dev 0.4.0-3 in plucky amd64 librust-tree-sitter-query-dev 0.4.0-3 in plucky arm64 librust-tree-sitter-query-dev 0.4.0-3 in plucky armhf librust-tree-sitter-query-dev 0.4.0-3 in plucky ppc64el librust-tree-sitter-query-dev 0.4.0-3 in plucky s390x tree-sitter-query-src 0.4.0-3 in plucky amd64 tree-sitter-query-src 0.4.0-3 in plucky arm64 tree-sitter-query-src 0.4.0-3 in plucky armhf tree-sitter-query-src 0.4.0-3 in plucky i386 tree-sitter-query-src 0.4.0-3 in plucky ppc64el tree-sitter-query-src 0.4.0-3 in plucky riscv64 tree-sitter-query-src 0.4.0-3 in plucky s390x tree-sitter-sdml 0.4.5-1 in plucky librust-tree-sitter-sdml-dev 0.4.5-1 in plucky amd64 librust-tree-sitter-sdml-dev 0.4.5-1 in plucky arm64 librust-tree-sitter-sdml-dev 0.4.5-1 in plucky armhf librust-tree-sitter-sdml-dev 0.4.5-1 in plucky i386 librust-tree-sitter-sdml-dev 0.4.5-1 in plucky ppc64el librust-tree-sitter-sdml-dev 0.4.5-1 in plucky riscv64 librust-tree-sitter-sdml-dev 0.4.5-1 in plucky s390x python3-tree-sitter-sdml 0.4.5-1 in plucky amd64 python3-tree-sitter-sdml 0.4.5-1 in plucky arm64 python3-tree-sitter-sdml 0.4.5-1 in plucky armhf python3-tree-sitter-sdml 0.4.5-1 in plucky ppc64el python3-tree-sitter-sdml 0.4.5-1 in plucky riscv64 python3-tree-sitter-sdml 0.4.5-1 in plucky s390x tree-sitter-vim 0.4.0-3 in plucky librust-tree-sitter-vim-dev 0.4.0-3 in plucky amd64 librust-tree-sitter-vim-dev 0.4.0-3 in plucky arm64 librust-tree-sitter-vim-dev 0.4.0-3 in plucky armhf librust-tree-sitter-vim-dev 0.4.0-3 in plucky ppc64el librust-tree-sitter-vim-dev 0.4.0-3 in plucky s390x tree-sitter-vim-src 0.4.0-3 in plucky amd64 tree-sitter-vim-src 0.4.0-3 in plucky arm64 tree-sitter-vim-src 0.4.0-3 in plucky armhf tree-sitter-vim-src 0.4.0-3 in plucky i386 tree-sitter-vim-src 0.4.0-3 in plucky ppc64el tree-sitter-vim-src 0.4.0-3 in plucky riscv64 tree-sitter-vim-src 0.4.0-3 in plucky s390x tree-sitter-vimdoc 3.0.0-3 in plucky librust-tree-sitter-vimdoc-dev 3.0.0-3 in plucky amd64 librust-tree-sitter-vimdoc-dev 3.0.0-3 in plucky arm64 librust-tree-sitter-vimdoc-dev 3.0.0-3 in plucky armhf librust-tree-sitter-vimdoc-dev 3.0.0-3 in plucky ppc64el librust-tree-sitter-vimdoc-dev 3.0.0-3 in plucky s390x tree-sitter-vimdoc-src 3.0.0-3 in plucky amd64 tree-sitter-vimdoc-src 3.0.0-3 in plucky arm64 tree-sitter-vimdoc-src 3.0.0-3 in plucky armhf tree-sitter-vimdoc-src 3.0.0-3 in plucky i386 tree-sitter-vimdoc-src 3.0.0-3 in plucky ppc64el
[Bug 2103586] Re: Page 'Ubuntu Pro' has not default value when network is available
** Tags added: jira-nantou-492 oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Bin Li (binli) ** Changed in: oem-priority Status: New => In Progress ** Changed in: oem-priority Importance: Undecided => High ** Description changed: - By default, it will set ‘Skip for now’ when there is not network, + [Impact] + On 24.04, it will set ‘Skip for now’ when there is not network, But when there is a connection, then ‘Enable Ubuntu Pro’ and ‘Skip or now’ are not selected, and the ‘Next’ button is active. - [Steps] + + [Test Plan] * Make the network is offline $ rm .config/gnome-intial-setup-done $ gnome-initial-setup --existing-user * Then turn on the network + + [Where problems could occur] + + * This patch just set the check button status when network status is + changed, it's low risk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103586 Title: Page 'Ubuntu Pro' has not default value when network is available To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2103586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2102236] Re: plucky/s390x (with root disk on dm?) does not come up after kernel update + reboot
Uh, good catch Nick (with that it looks like it's since oracular ?!) And yes, the names may indeed look a bit cryptic, since these are for s390x specific (so called CCW) devices (here in this case disk devices, but there are more types; cio-ignore is to mask out a range of CCW devices). One difference between these CCW devices and devices on s390x, and let's say devices in the PC world is, that even if CCW devices are visible and available (means they got detected), they need to be explicitly enabled before usage - and that is what these rules are supposed to do (e.g. "chzdev -e 271d" enables DASD disk device #271d). I vaguely remember LP#2044104, but need to re-read it to get the full details again ... (Looks to me like this is a case on non-DPM system (that do not support auto configuration), that was not properly considered. Guess it need to somehow identified if it's an autoconfigure rule - then skip/continue - or not - then copy.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2102236 Title: plucky/s390x (with root disk on dm?) does not come up after kernel update + reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2102236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth library crashes and doesn't show splash screen
Sorry. Couldn't find any bugs. There is any way that I can configure, even temporarily, so I can see the stack trace made by plymouthd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth library crashes and doesn't show splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth library crashes and doesn't show splash screen
** Attachment added: "Updated prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+attachment/5865794/+files/prevjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth library crashes and doesn't show splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth library crashes and doesn't show splash screen
** Attachment added: "Updated file" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+attachment/5865793/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth library crashes and doesn't show splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103599] [NEW] Snap installation fails though library dependencies are in snap
Public bug reported: I tried to install snap keepalived on a riscv64 system on which the packages libsnmp40 and libipset13 were not installed and received errors Mar 19 10:42:35 node keepalived.daemon[255429]: /snap/keepalived/2945/usr/sbin/keepalived-519: error while loading shared libraries: libipset.so.13: cannot open shared object file: No such file or directory Mar 19 10:42:35 node systemd[1]: snap.keepalived.daemon.service: Control process exited, code=exited, status=127/n/a ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support Mar 19 10:45:18 node keepalived.daemon[256538]: /snap/keepalived/2945/usr/sbin/keepalived-519: error while loading shared libraries: libnetsnmpmibs.so.40: cannot open shared object file: No such file or directory Mar 19 10:45:18 node systemd[1]: snap.keepalived.daemon.service: Control process exited, code=exited, status=127/n/a ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support After installing packages libsnmp40 and libipset13 the installation succeeded. This is unexpected as libsnmp40 and libipset13 are in stage-packages and the following paths are valid: /snap/keepalived/current/usr/lib/riscv64-linux-gnu/libnetsnmpmibs.so.40 -> libnetsnmpmibs.so.40.1.0 /snap/keepalived/current/usr/lib/riscv64-linux-gnu/libipset.so.13 -> libipset.so.13.3.0 The snap source is available at https://github.com/acassen/keepalived. ** Affects: snapd (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/2103599 Title: Snap installation fails though library dependencies are in snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2103599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100003] Re: backport mofed-modules-24.10 24.10.1.1.4.0-0ubuntu2
> given that this also could qualify as an HWE upload as explained? On your "HWE exception" claims, let me be clear. If an SRU upload *contains* a hardware enablement as part of other changes, that does not automatically give the other changes a free pass. The other changes would require SRU justification on their own merits, or else they must not be included as part of the SRU. Further, the "HWE exception" merely states that hardware enablement is a valid reason for SRU. It is still subject to the usual requirement to minimise regression risk and therefore the requirement to minimise changes and specify (and have accepted) an appropriate QA plan. On "accepting this microrelease", let me be clear again. This is *not* a microrelease from our perspective, since it contains feature changes. Or at least I think it does, given the release notes you linked. I would appreciate if you could stop throwing those terms around as if they grant you free passes through SRU policy without a further explanation of how they apply, given that it appears that they do not. Further, https://docs.nvidia.com/doca/archive/2-9-1/changes+and+new+features/index.html has a section on "Backward Compatibility Breaking Changes in this Release" that says "...and therefore require customers to upgrade all DOCA software components to the latest available version to avoid anomalous behavior". mofed-modules-24.10 is just one of those software components, right? What if a user is using other software components, and then updates this one. Will they face a regression? > It is both. According to the upstream changelog [1], it contains the following HWE features: > > Added support for OVS-DOCA live upgrade of virtual switch This sounds like a new feature, not a hardware enablement. > And the following bug fixes: > > Description: rte_eth_dev_start() performs unnecessary recreation of mlx5 control flow rules, resulting in increased delay of rte_eth_dev_start(). You can get regular bug fixes qualified for SRU in one of two ways: 1) a minimal cherry-pick with a test plan that validates the specific fix being made, normally tracked in its own bug; or 2) by taking the whole upstream (not-micro, it seems)-release, but demonstrating how quality will be maintained by showing how upstream meets our quality requirements documented at https://documentation.ubuntu.com/sru/en/latest/reference/requirements/#new- upstream-microreleases On testing: We've long required that the testing to be performed can be performed by anyone suitably competent, mainly because we get so many SRUs that get accepted but then the available testers disappear. It's OK, and fairly well accepted, that if specialist hardware requires testing then only limited people are going to have access to be able to do that, and we've accepted assurances that those people are ready to perform the SRU verification as enough in the past. It's also great if a third party reports a regression with a high quality bug report, regardless of their possible use of a private test suite that alerted them to it. We should encourage this if they have that ability but cannot contribute it, just as we should encourage contributions to improve public test suites. However, I think we're in different territory if the *only* QA that can be performed is done in private. This has implications such as: is what we're shipping really Free Software, if code essential to us releasing updates is missing? If not, then should this package be in restricted or multiverse instead? This seems like an important policy question for the project. A possible mitigation might be to consider that this is being one only for packages tied to specific hardware and the private test suite is owned and operated by the hardware manufacturer, and perhaps require that we have their agreement and cooperation. In that sense, it feels similar to the type of pragmatism with which we ship non-free hardware drivers. But in that case, perhaps restricted/multiverse *is* the appropriate place? However, this is not the only outstanding question here. I think you still need to qualify the feature and potentially breaking changes you propose to make, and demonstrate that they are suitable for SRU, as I've covered above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213 Title: backport mofed-modules-24.10 24.10.1.1.4.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mofed-modules-24.10/+bug/213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2098137] Re: [SRU] 2.68.3
You say the release testing passed and link https://github.com/canonical/snapd/actions/runs/13771811525/job/38543122363; but that shows the spread tests for ubuntu-jammy and ubuntu-daily (and some other distros) failed. Please explain why that should be considered a pass. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2098137 Title: [SRU] 2.68.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2098137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100003] Re: backport mofed-modules-24.10 24.10.1.1.4.0-0ubuntu2
> as the mofed dkms is "hard" to test and can only be done in an LTS Why is this the case, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213 Title: backport mofed-modules-24.10 24.10.1.1.4.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mofed-modules-24.10/+bug/213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth library crashes and doesn't show splash screen
I have some pictures that I could take with my smartphone. I think it's some related to Nvidia GPU, because for some reason the module didn't load (I know because my external display didn't work) and then Plymouth appeared. After rebuilding the Nvidia driver module and initrd, the problem happend again. ** Attachment added: "IMG_20250319_071337923_HDR.jpg" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+attachment/5865790/+files/IMG_20250319_071337923_HDR.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth library crashes and doesn't show splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103588] Re: libgl1-amber-dri/libgl1-mesa-dri uninstallable in plucky ISO image builds. Causes build to fail
Looking into this ... ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Tim Andersson (andersson123) ** Changed in: mesa-amber (Ubuntu) Assignee: (unassigned) => Tim Andersson (andersson123) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103588 Title: libgl1-amber-dri/libgl1-mesa-dri uninstallable in plucky ISO image builds. Causes build to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2103588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103596] Re: Activating a LVM RAID-1 volume causes a kernel BUG: "detected buffer overflow in strlen"
I've found a workaround: - recover the filesystem image (either by doing math with lvdisplay -m/pvdisplay -m, correlating with dmsetup table output for other volumes, or by trying to activate the LV and looking at dmsetup table for the subvolumes directly) - possibly reboot if you tried to activate and now the kernel lock is wedged - remove the broken logical volume with lvremove - re-create a new volume of the same size, dd the recovered image onto it I still have dumps of the metadata subvolumes (jenkins_rmeta_0 and jenkins_rmeta_1, they differ by exactly one bit at offset 13 decimal) if those could be useful for debugging the kernel's md_bitmap_read_sb code. They're 4 MB each and I'm not sure I can attach them to this Launchpad bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103596 Title: Activating a LVM RAID-1 volume causes a kernel BUG: "detected buffer overflow in strlen" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2092438] Re: System fails to restart after install
In the live session, calling `systemctl reboot` (or /sbin/reboot) as root produces the following error: # systemctl reboot Operation inhibited by "ubuntu" (PID 2297 "gnome-session-b", user ubuntu, reason is "user session inhibited". User ubuntu is logged in on tty2. Please retry operation after closing inhibitors and logging out other users. 'systemd-inhibit' can be used to list active inhibitors. Alternatively, ignore inhibitors and users with `systemctl reboot -i' I was confused why the error was different from what I saw in the Subiquity logs. But curiously: # systemctl reboot > /dev/null Call to Reboot failed: Access denied -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2092438 Title: System fails to restart after install To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2092438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103599] Re: Snap installation fails though library dependencies are in snap
Wouldn't $SNAP/usr/lib/$SNAP_ARCH-gnu-linux always be in the library search path? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103599 Title: Snap installation fails though library dependencies are in snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2103599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2102113] Re: intel i219-LM on Dell 5420 with bad NVM checksum doesn't work with e1000e driver
Thank you. I hope we can find some permanent workaround for this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2102113 Title: intel i219-LM on Dell 5420 with bad NVM checksum doesn't work with e1000e driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2102113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] Re: Long waiting time for app launch with kernel 6.11
apport information ** Description changed: Since upgrading to kernel 6.11.0-17, service loading is fast, but it takes about 1 to 1.5 minutes before being able to launch applications (Settings, Update Manager, Firefox, Terminal, etc.) after restarting Ubuntu 24.04.2 LTS. No issues on previous kernels. The problem was similar with Ubuntu 24.10 as well. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.11.0-17-generic 6.11.0-17.17~24.04.2 ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11 Uname: Linux 6.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 1 20:40:54 2025 InstallationDate: Installed on 2025-01-03 (57 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: linux-signed-hwe-6.11 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:glion 3666 F pipewire /dev/snd/controlC0: glion 3670 F wireplumber /dev/snd/controlC1: glion 3666 F pipewire glion 3670 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2025-01-03 (63 days ago) InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) IwConfig: lono wireless extensions. wlp2s0f0 no wireless extensions. MachineType: Dell Inc. Precision 5690 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-17-generic root=UUID=73f10a81-c28b-4e90-9e89-3a34c3c73fa1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.11.0-17.17~24.04.2-generic 6.11.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.11.0-17-generic N/A linux-backports-modules-6.11.0-17-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.9 Tags: noble Uname: Linux 6.11.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/31/2024 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 02RYDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd12/31/2024:br1.10:efr1.18:svnDellInc.:pnPrecision5690:pvr:rvnDellInc.:rn02RYDD:rvrA00:cvnDellInc.:ct10:cvr:sku0CC8: dmi.product.family: Precision dmi.product.name: Precision 5690 dmi.product.sku: 0CC8 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.28.1-0ubuntu3.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/seq:glion 3122 F pipewire + /dev/snd/controlC0: glion 3125 F wireplumber + /dev/snd/controlC1: glion 3122 F pipewire + glion 3125 F wireplumber + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 24.04 + InstallationDate: Installed on 2025-01-03 (75 days ago) + InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + + wlp2s0f0 no wireless extensions. + MachineType: Dell Inc. Precision 5690 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + LANG=fr_FR.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-19-generic root=UUID=73f10a81-c28b-4e90-9e89-3a34c3c73fa1 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.11.0-19.19~24.04.1-generic 6.11.11 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-6.11.0-19-generic N/A + linux-backports-modules-6.11.0-19-generic N/A + linux-firmware 20240318.git3b128b60-0ubuntu2.10 + Tags: noble + Uname: L
[Bug 2100680] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865816/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865817/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865822/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865820/+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/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865815/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103599] Re: Snap installation fails though library dependencies are in snap
It looks like Snap keepalived is failing to load shared libraries (libipset.so.13 and libnetsnmpmibs.so.40), even though they are included in stage-packages and present inside the Snap package. The fact that installing the system versions (libsnmp40 and libipset13) solved the issue suggests that Snap confinement or library path resolution may be the root cause. Possible Causes & Solutions: 1. Library Path Not Being Recognized Snap packages run in a confined environment and do not use the system’s /usr/lib by default. The libraries inside the Snap package should be linked properly at runtime. Solution: Try running ldd to check where keepalived is trying to load the libraries from: sh Copy Edit ldd /snap/keepalived/current/usr/sbin/keepalived If the output shows missing libraries or points to system paths instead of Snap paths, the issue is likely related to library path resolution. You can try manually setting LD_LIBRARY_PATH when running the service: sh Copy Edit LD_LIBRARY_PATH=/snap/keepalived/current/usr/lib/riscv64-linux-gnu /snap/keepalived/current/usr/sbin/keepalived If this fixes the issue, you may need to adjust the Snap package to set the correct environment variables. 2. Snap Confinement Issues If the Snap is running in strict confinement, it may not be able to access its own libraries due to missing interfaces. Solution: Try running: sh Copy Edit snap connections keepalived If there are missing interfaces that could provide access to system libraries, connect them manually: sh Copy Edit sudo snap connect keepalived:network-control sudo snap connect keepalived:firewall-control You could also try running the Snap in classic mode (if supported) to bypass strict confinement: sh Copy Edit snap install keepalived --classic 3. Snapcraft Build Issue If stage-packages included libsnmp40 and libipset13, but the Snap still fails, the issue might be with snapcraft.yaml. Ensure that: The LD_LIBRARY_PATH is correctly set in the Snap environment. prime is correctly bundling dependencies. Solution: Modify the Snapcraft YAML to explicitly set the runtime library path: yaml Copy Edit apps: keepalived: command: usr/sbin/keepalived environment: LD_LIBRARY_PATH: $SNAP/usr/lib/riscv64-linux-gnu:$LD_LIBRARY_PATH Then rebuild the Snap and reinstall it. Next Steps Check ldd output to confirm missing libraries. Manually set LD_LIBRARY_PATH and test. Check Snap connections and try using --classic. Verify Snapcraft YAML and rebuild if needed. Would you like help debugging your Snapcraft YAML file? 🚀 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103599 Title: Snap installation fails though library dependencies are in snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2103599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865818/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865814/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865812/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2092063] Re: Graphical corruption on Zen4/RDNA3 APU
From diving into the upstream bug, these patches would be related: [PATCH 0/3] Fix some PSR/Replay stuttering issues [PATCH 1/3] drm/amd/display: Do not wait for PSR disable on vbl enable [PATCH 2/3] drm/amd/display: Do not elevate mem_type change to full update [PATCH 3/3] drm/amd/display: Disable replay and psr while VRR is enabled These would be at least in 6.12.11 https://web.git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=v6.12.11 So that would likely mean they're in plucky (6.14 kernel) but I don't want traces of them in the changelogs of oracular, noble, or jammy HWE. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: linux-hwe-6.8 (Ubuntu Oracular) Importance: Undecided Status: New ** No longer affects: linux-hwe-6.8 (Ubuntu Oracular) ** Changed in: linux (Ubuntu Oracular) 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/2092063 Title: Graphical corruption on Zen4/RDNA3 APU To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2092063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2089830] Re: [SRU] Make add-nvidia-repositories available in jammy and noble
> ...if I fix all the reported bugs and maintaining and verify checksums, it'd be worthwhile to have it in the archive But why isn't this going to be inside add-apt-repository instead, then, which is bug 2100496? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2089830 Title: [SRU] Make add-nvidia-repositories available in jammy and noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/add-nvidia-repositories/+bug/2089830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100003] Re: backport mofed-modules-24.10 24.10.1.1.4.0-0ubuntu2
PS. my previous comment is me reviewing this upload as an individual member of the SRU team. It is not an opinion of the entire SRU team or the Technical Board. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213 Title: backport mofed-modules-24.10 24.10.1.1.4.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mofed-modules-24.10/+bug/213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865824/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100003] Re: backport mofed-modules-24.10 24.10.1.1.4.0-0ubuntu2
Next steps: I think the private test suite question is still hypothetical at the moment, since there are so many other open issues that currently sound like they invalidate this SRU. Please revise the analysis in this bug to cover all other issues, so that the only review point remaining is that a private test suite is required. If and once the SRU team agrees that all other points are addressed, *then* I think it would be appropriate to open a wider discussion on the private test suite point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/213 Title: backport mofed-modules-24.10 24.10.1.1.4.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mofed-modules-24.10/+bug/213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103602] [NEW] [FFe] Please remove src:add-nvidia-repositories from Plucky
Public bug reported: Due to: Misuse of /tmp could result in root privilege escalation: bug 2100494 Poor guarantees of authenticity and origin: bug 2100495 Duplicates functionality of add-apt-repository: bug 2100496 Please remove src:add-nvidia-repositories from Plucky, as agreed in bug 2089830. Feature freeze exception justification: this never shipped in any other release, and the design itself is in question, so it is preferable to not ship something that has security issues and whose interface we intend to change. ** Affects: add-nvidia-repositories (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/2103602 Title: [FFe] Please remove src:add-nvidia-repositories from Plucky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/add-nvidia-repositories/+bug/2103602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103603] [NEW] [SRU] Backport netplan.io 1.1.2-2 to 24.04
Public bug reported:
Stable Release Update for netplan.io 1.1.2-2 to Noble (and Oracular).
This version contains bug fixes and new features we want to make
available to users of Ubuntu 24.04.
netplan.io has an SRU exception for backporting new versions with new
features https://wiki.ubuntu.com/NetplanUpdates
[ Impact ]
This release contains both bug fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
* wifi: add support for wpa-psk-sha256 by (LP: #2102097, LP#2085320,
LP#2084237)
* cli: Don't crash on udevadm trigger errors in 'netplan apply' (LP: #2095203)
* parse: fix renderer validation for nm-devices (LP: #2091755)
* networkmanager: add support for "routing-policy" (LP: #2086544)
* Improved DEP-8 WiFi testing
[ Test Plan ]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NetplanUpdates
Netplan contains an extensive integration test suite that is ran using
the SRU package for each releases. This test suite's results are available here:
http://autopkgtest.ubuntu.com/packages/n/netplan.io
A successful run is required before the proposed netplan package
can be let into -updates.
The netplan team will be in charge of attaching the artifacts and console
output of the appropriate run to the bug. Netplan team members will not
mark ‘verification-done’ until this has happened.
Noble autopkgtest logs:
- TBD (once it's in noble-proposed)
Oracular autopkgtest logs:
- TBD (once it's in oracular-proposed)
[ Where problems could occur ]
* This is not a big release and is available on Plucky & Debian for some
time now without any concerning issues reported.
* As usual, any backwards compatibility issue that prevents the new
Netplan to parse existing YAML files would leave the system without
networking configuration after a reboot or add unexpected logging
output. Therefore, we added one patch in "d/p/sru-compat/0006-*" to mute
one warning, as it used to be on Noble.
[ Other Info ]
* We've based this backport/SRU on top of Debian's 1.1.2-2 as later
version contain new wait-online logic that cannot be applied on
Noble/Oracular, due to missing systemd functionality.
* A PPA for testing can be found at
https://launchpad.net/~slyon/+archive/ubuntu/lp-2103603-backport-
netplan-1.1.2-2
[ Changelog ]
* Backport netplan.io 1.1.2-2 (LP: #2077011)
- wifi: add support for wpa-psk-sha256 (LP #2102097, #2085320, #2084237)
- networkmanager: add support for "routing-policy" (LP #2086544)
- parse: fix renderer validation for nm-devices (LP #2091755)
- d/p/lp2095203: Don't crash on udevadm trigger errors in 'netplan apply'
(LP #2095203)
- d/*.manpages: Use dh_installman and add netplan(8) manpage
- d/netplan-generator.doc-base: Register YAML reference with doc-base
- d/copyright: Update for 2025
- d/control: remove alternative dependency on deprecated pep8
- d/{rules,control}: use dh-sequence-python3
- d/t/control: Avoid flaky 'wifi' DEP8 test, instead SKIP if conditions
are not met
- d/t/control: Add test dependency on dhcpcd-base, replacing ISC dhclient
- d/patches: improve WiFi testing
+ 0002-tests-wifi-use-dhcpcd-istead-of-deprecated-ISC-dhcli.patch
+ 0003-tests-add-integration-test-for-wifi-psk-sha256.patch
* sru-compat: Mute warning if a priority is not set
- d/p/sc/0006-validation-Mute-warning-if-a-priority-is-not-set-for.patch
[ Git Changelog ]
73344e5f sru-compat: Mute warning if a priority is not set
78d309c2 upload 1.1.2-2 to unstable [skip ci]
d357abc4 d/t/control: fixup Avoid flaky 'wifi' DEP8 test
f354acff changelog
adb56c2f d/p/lp2095203: Don't crash on udevadm trigger errors in 'netplan apply'
eb6ab004 changelog
f4649dd6 d/patches: improve WiFi testing
17045dd5 changelog
6f567082 d/t/control: Add test dependency on dhcpcd-base, replacing ISC dhclient
a8261def d/t/control: Avoid flaky 'wifi' DEP8 test, instead, SKIP if conditions
are not met
13f11caf upload 1.1.2-1 to unstable [skip ci]
acd184b5 d/copyright: Update for 2025
b2978635 changelog
4322f09b d/netplan-generator.doc-base: Register YAML reference with doc-base
916c633d Use dh_installman and add netplan(8) manpage
4103d54f Update changelog
72104daf CI: cleanup spread.yml workflow now that PR#184 is fixed
5b12d0f9 wifi: add support for wpa-psk-sha256 https://pad.lv/2085320
https://pad.lv/2084237
b10f840d parse: fix renderer validation for nm-devices
6355a660 doc: Add anchor link for deprecated gateway4/6 keys
28676763 validation: use curly braces for all branches
2add62f0 nm/policy: downgrade new error to warning
9934618b ATTN: validation: warn if a priority is not set for a routing-policy
7a3861c8 validation: remove superfluous comparison
2d94dd0f ATTN: networkmanager: add support for "routing-policy"
eb89cf1b parse.c: quiet "may be used uninitialized" warnings/errors
d0edf5e3 CI: Fix fedora:latest (F41) failure
99b3aad0 use dh-sequen
[Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04
I am also experiencing this bug with the T460p on Kernal 6.10 with a new install of Linux Mint 22.1 (aka Ubuntu 24.04). When shutting down, the circular LED within the circle power off button goes dead, which in previous versions meant the laptop was shutdown. If you use the Fn key, you can see that the laptop has not entirely shutdown by leaving the Fn Lock enabled. When the laptop is supposedly completely shutdown, the LED on this keyboard key is still lit. This does not occur with the Caps Lock key. Anyway, once the circular power LED goes dead, you have to then hold the power down for another 6-8 seconds. The only indication that this has actually completely shutdown is the Fn Lock LED goes out. This isn't ideal, but I can at least shut it down properly. I tested suspend once and it didn't work. I don't want to disable Virtualisation in the BIOS (because I use it) and I have no idea what the TTL chip is and what the downsides of disabled that are. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2059738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865823/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865819/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2100680] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2100680/+attachment/5865821/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100680 Title: Long waiting time for app launch with kernel 6.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068805] Re: [SRU] "Install Now" button disappears for good if all packages unselected and Ubuntu Pro packages are shown but unavailable
Thank you, Dave, for sponsoring and for the thoughtful improvement suggestions. You seem to have taken care of it all (yes I think for Bionic and Xenial the process is special), and I edited the regression section, but let me know if it is still lacking in any form. ** Description changed: [Impact] If one deselects all packages, the "Install Now" button disappears, which makes sense (on another note it would make even more sense if it was simply grayed out). However when one or more packages are then re- selected, the button won't ever reappear, and update-manager must be restarted in order to upgrade any packages. [Test case] For each affected $series: * If 'apt list --upgradable' is empty, downgrade any one package in your system. * sudo ua detach --assume-yes * sudo apt install hello * update-manager * Verify at least one update is available, and the hello package is unavailable under the 'Ubuntu Pro security updates' section * De-select all available packages * Verify the 'install now' button disappears * Select at least one available package * Verify the 'install now' button is still absent * Close the window * Enable proposed (see https://wiki.ubuntu.com/Testing/EnableProposed) * sudo apt install -t $series-proposed update-manager * update-manager * Verify at least one update is available, and the hello package is unavailable under the 'Ubuntu Pro security updates' section * De-select all available packages * Verify the 'install now' button disappears * Select at least one available package * Verify the 'install now' button is now visible again [Where things could go wrong] Things could go wrong with the 'install now' button. It should be visible when there is any available package selected and not visible - when there is none selected. + when there is none selected. So a regression could appear as the user no + longer being able install packages via this program, or being able to + click "install now" with no packages selected to be installed. In any + case, since this program is essentially a wrapper of Apt, all the + package management functionality, including upgrading, would still be + avaialable through Apt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068805 Title: [SRU] "Install Now" button disappears for good if all packages unselected and Ubuntu Pro packages are shown but unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2068805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103588] Re: libgl1-amber-dri/libgl1-mesa-dri uninstallable in plucky ISO image builds. Causes build to fail
** Changed in: mesa (Ubuntu) Status: New => Invalid ** Changed in: mesa (Ubuntu) Importance: Critical => Undecided ** Changed in: mesa (Ubuntu) Assignee: Tim Andersson (andersson123) => (unassigned) ** Changed in: mesa-amber (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103588 Title: libgl1-amber-dri/libgl1-mesa-dri uninstallable in plucky ISO image builds. Causes build to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2103588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2075165] Re: devicexlib fails to build on armel/armhf/hppa/m68k/sh4 - invalid memory reference in dp_r4d
** Changed in: devicexlib (Debian) 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/2075165 Title: devicexlib fails to build on armel/armhf/hppa/m68k/sh4 - invalid memory reference in dp_r4d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devicexlib/+bug/2075165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103603] Re: [SRU] Backport netplan.io 1.1.2-2 to 24.04
** Also affects: netplan.io (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu Plucky) 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/2103603 Title: [SRU] Backport netplan.io 1.1.2-2 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2103603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951791] Re: [MIR] oem-somerville-oranguru-meta
Hello OEM, or anyone else affected, Accepted oem-somerville-oranguru-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-somerville-oranguru- meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal ** Also affects: oem-somerville-oranguru-meta (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu ** Also affects: oem-somerville-oranguru-meta (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: oem-somerville-oranguru-meta (Ubuntu Focal) Status: New => Fix Committed ** Changed in: oem-somerville-oranguru-meta (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/1951791 Title: [MIR] oem-somerville-oranguru-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960901] Re: [MIR] oem-somerville-oranguru-adl-meta
Hello OEM, or anyone else affected, Accepted oem-somerville-oranguru-adl-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-somerville-oranguru-adl- meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal ** Also affects: oem-somerville-oranguru-adl-meta (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu ** Also affects: oem-somerville-oranguru-adl-meta (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: oem-somerville-oranguru-adl-meta (Ubuntu) Status: New => Invalid ** Changed in: oem-somerville-oranguru-adl-meta (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960901 Title: [MIR] oem-somerville-oranguru-adl-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103578] Re: AppArmor notifications loose state when listener crashes
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: apparmor (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => John Johansen (jjohansen) ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => John Johansen (jjohansen) ** Also affects: apparmor (Ubuntu Plucky) Importance: Undecided Assignee: John Johansen (jjohansen) Status: In Progress ** Also affects: linux (Ubuntu Plucky) Importance: Undecided Assignee: John Johansen (jjohansen) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103578 Title: AppArmor notifications loose state when listener crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2103578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103371] Re: Please remove ripoff, Ubuntu-only package, ftbfs
And removed again ** Changed in: ripoff (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/2103371 Title: Please remove ripoff, Ubuntu-only package, ftbfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ripoff/+bug/2103371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2092209] Re: Can't enter passphrase for encrypted disk on splash screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: plymouth (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/2092209 Title: Can't enter passphrase for encrypted disk on splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2092209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945375] Re: [MIR] oem-somerville-pypar-adl-meta
Hello OEM, or anyone else affected, Accepted oem-somerville-pypar-adl-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem-somerville-pypar-adl- meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: oem-somerville-pypar-adl-meta (Ubuntu) Importance: Undecided Status: New ** Tags added: verification-needed verification-needed-focal ** No longer affects: ubuntu ** Also affects: oem-somerville-pypar-adl-meta (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: oem-somerville-pypar-adl-meta (Ubuntu Focal) Status: New => Fix Committed ** Changed in: oem-somerville-pypar-adl-meta (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/1945375 Title: [MIR] oem-somerville-pypar-adl-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940203] Re: [MIR] oem-somerville-paras-meta
Hello OEM, or anyone else affected, Accepted oem-somerville-paras-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/oem- somerville-paras-meta/20.04~ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Also affects: oem-somerville-paras-meta (Ubuntu) Importance: Undecided Status: New ** Tags added: verification-needed verification-needed-focal ** No longer affects: ubuntu ** Also affects: oem-somerville-paras-meta (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: oem-somerville-paras-meta (Ubuntu Focal) Status: New => Fix Committed ** Changed in: oem-somerville-paras-meta (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/1940203 Title: [MIR] oem-somerville-paras-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621367] Re: 4.4.0-36: keyboard dead at boot & full disk encryption prompt for password
A similar issue https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1621367 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621367 Title: 4.4.0-36: keyboard dead at boot & full disk encryption prompt for password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1621367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2085903] Re: [SRU] Please merge rpi-eeprom 26
AFAICT there's nothing for AAs to do here, unsubscribing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2085903 Title: [SRU] Please merge rpi-eeprom 26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpi-eeprom/+bug/2085903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 903602] Re: CIFS automount with "nounix" option create empty directories
Ubuntu 10.10 (Maverick Meerkat) with kernel 2.6.y has reached end of life, so this bug will not be fixed for that specific release. Please file a new bug if this issue still exists in a supported release. ** Changed in: linux (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/903602 Title: CIFS automount with "nounix" option create empty directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2102019] Re: DSI touchscreen fails to display anything on Pi 5 with Ubuntu Server
*** This bug is a duplicate of bug 2085903 *** https://bugs.launchpad.net/bugs/2085903 Confirmed this on noble. The root cause is an older boot EEPROM (specifically Dec 2023). On the older firmwares it appears the bootloader pre-allocates a framebuffer with an incorrect resolution for the DSI display, and (on the server images at least), the kernel attempts to re-use this framebuffer which fails. The newer bootloader (tested June 2024, and Dec 2024) honours the disable_fw_kms_setup=1 setting in config.txt, leaving the kernel to handle display setup, which it does correctly. Ultimately, this is a duplicate of LP: #2085903 which, once it lands, will update the EEPROM image to June 2024. This is already fixed in plucky (devel) which has the later package. Marking accordingly. ** Changed in: Ubuntu Noble Status: Incomplete => Confirmed ** Changed in: ubuntu Status: Incomplete => Confirmed ** Changed in: ubuntu Status: Confirmed => Fix Released ** This bug has been marked a duplicate of bug 2085903 [SRU] Please merge rpi-eeprom 26 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2102019 Title: DSI touchscreen fails to display anything on Pi 5 with Ubuntu Server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2102019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth library crashes and doesn't show splash screen
It definitely something strange because it has a whole stack trace being shown. Let me grab the files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth library crashes and doesn't show splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth library crashes and doesn't show splash screen
Sorry. Couldn't find any bugs. There is any way that I can configure, even temporarily, so I can see the stack trace made by plymouthd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth library crashes and doesn't show splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103533] Re: plymouth library crashes and doesn't show splash screen
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+attachment/5865786/+files/prevjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth library crashes and doesn't show splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2103588] [NEW] libgl1-amber-dri/libgl1-mesa-dri uninstallable in plucky ISO image builds. Causes build to fail
Public bug reported: Sources: mesa-amber 21.3.9-0ubuntu2 and mesa 25.0.1-2ubuntu1 Release: plucky release pocket In the Ubuntu desktop and flavours ISO image livefs build, the package libgl1-amber-dri fails to be installable by apt causing the build to fail. For example: https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/plucky/ubuntu/+build/765930 The build fails with the error extract at the end of this report. libgl1-mesa-dri from src:mesa recommends libgl1-amber-dri, so on a normal system libgl1-mesa-dri is installable. However, on ISO image builds recommends are enforced as depends so the failure occurs. libgl1-amber-dri : Depends: libglapi-mesa (>= 24.0.3), but from plucky libglapi-mesa is a virtual package provided by https://launchpad.net/ubuntu/plucky/amd64/mesa- libgallium/25.0.1-2ubuntu1 without any versioned Depends from build log Solving dependencies... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgl1-amber-dri : Depends: libglapi-mesa (>= 24.0.3) E: Unable to correct problems, you have held broken packages. E: The following information from --solver 3.0 may provide additional context: Unable to satisfy dependencies. Reached two conflicting decisions: 1. libgl1-amber-dri:arm64=21.3.9-0ubuntu2 is selected for install 2. libgl1-amber-dri:arm64 Depends libglapi-mesa (>= 24.0.3) but none of the choices are installable: [no choices] end of extract ** Affects: mesa (Ubuntu) Importance: Critical Status: New ** Affects: mesa-amber (Ubuntu) Importance: Critical Status: New ** Also affects: mesa (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/2103588 Title: libgl1-amber-dri/libgl1-mesa-dri uninstallable in plucky ISO image builds. Causes build to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2103588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2034705] Re: efivar fails to read variables
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2034705 Title: efivar fails to read variables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/2034705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 903602] Re: CIFS automount with "nounix" option create empty directories
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/903602 Title: CIFS automount with "nounix" option create empty directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2101944] Re: Expose bits related to SRSO vulnerability
** Merge proposal linked: https://code.launchpad.net/~slyon/ubuntu/+source/qemu/+git/qemu/+merge/483036 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2101944 Title: Expose bits related to SRSO vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2101944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
