[Bug 2066275] Re: [SRU] Fix black screen on second boot due to video drivers not being ready.
Alright, found the issue. So it seems we ship a custom sddm.service in debian/ and we do not use the provided sddm.service from upstream, and thus my patch has no significance. I have now patched the custom sddm.service file that is shipped. Unfortunately I do not have upload rights here and have asked Rik to please upload the new version. Sorry for any inconvenience. Scarlett -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066275 Title: [SRU] Fix black screen on second boot due to video drivers not being ready. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2066275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055409] Re: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page
** Also affects: cloud-archive/caracal Importance: Undecided Status: New ** Changed in: cloud-archive/caracal 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/2055409 Title: [SRU] config OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES does not apply to instance detail page To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2055409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054799] Please test proposed package
Hello Hua, or anyone else affected, Accepted horizon into caracal-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:caracal-proposed sudo apt-get update 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, and change the tag from verification-caracal-needed to verification-caracal-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-caracal-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-archive/caracal Status: New => Fix Committed ** Tags added: verification-caracal-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054799 Title: [SRU] Issue with Project administration at Cloud Admin level To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2054799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054799] Please test proposed package
Hello Hua, or anyone else affected, Accepted horizon into caracal-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository. Please help us by testing this new package. To enable the -proposed repository: sudo add-apt-repository cloud-archive:caracal-proposed sudo apt-get update 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, and change the tag from verification-caracal-needed to verification-caracal-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-caracal-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054799 Title: [SRU] Issue with Project administration at Cloud Admin level To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2054799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054799] Re: [SRU] Issue with Project administration at Cloud Admin level
@zhhuabj need lunar/antelope debdiff ** Changed in: cloud-archive/zed 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/2054799 Title: [SRU] Issue with Project administration at Cloud Admin level To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2054799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070095] Re: apt_news.py download forced unsandboxed
Hello, Dominic. Thanks for reporting this. To be able to better assess the root of the problem, could you please collect and share the output of `sudo pro collect-logs`? Please, make sure that no sensitive information (as the pro token) is attached, or making this issue private. Could you also run `sudo ls -hal /run/ubuntu-advantage/`? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070095 Title: apt_news.py download forced unsandboxed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2070095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071621] [NEW] Noble update: v6.8.12 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.8.12 upstream stable release from git://git.kernel.org/ sunrpc: use the struct net as the svc proc private x86/tsc: Trust initial offset in architectural TSC-adjust MSRs selftests/ftrace: Fix BTFARG testcase to check fprobe is enabled correctly ftrace: Fix possible use-after-free issue in ftrace_location() Revert "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" arm64/fpsimd: Avoid erroneous elide of user state reload Reapply "arm64: fpsimd: Implement lazy restore for kernel mode FPSIMD" tty: n_gsm: fix missing receive state reset after mode switch speakup: Fix sizeof() vs ARRAY_SIZE() bug serial: sc16is7xx: fix bug in sc16is7xx_set_baud() when using prescaler serial: 8250_bcm7271: use default_mux_rate if possible serial: 8520_mtk: Set RTS on shutdown for Rx in-band wakeup Input: try trimming too long modalias strings io_uring: fail NOP if non-zero op flags is passed in Revert "r8169: don't try to disable interrupts if NAPI is, scheduled already" r8169: Fix possible ring buffer corruption on fragmented Tx packets. ring-buffer: Fix a race between readers and resize checks net: mana: Fix the extra HZ in mana_hwc_send_request tools/latency-collector: Fix -Wformat-security compile warns tools/nolibc/stdlib: fix memory error in realloc() net: ti: icssg_prueth: Fix NULL pointer dereference in prueth_probe() net: lan966x: remove debugfs directory in probe() error path net: smc91x: Fix m68k kernel compilation for ColdFire CPU nilfs2: fix use-after-free of timer for log writer thread nilfs2: fix unexpected freezing of nilfs_segctor_sync() nilfs2: fix potential hang in nilfs_detach_log_writer() fs/ntfs3: Remove max link count info display during driver init fs/ntfs3: Taking DOS names into account during link counting fs/ntfs3: Fix case when index is reused during tree transformation fs/ntfs3: Break dir enumeration if directory contents error ksmbd: avoid to send duplicate oplock break notifications ksmbd: ignore trailing slashes in share paths ALSA: core: Fix NULL module pointer assignment at card init ALSA: Fix deadlocks with kctl removals at disconnection KEYS: asymmetric: Add missing dependency on CRYPTO_SIG UBUNTU: [Config] updateconfigs for CRYPTO_SIG KEYS: asymmetric: Add missing dependencies of FIPS_SIGNATURE_SELFTEST HID: nintendo: Fix N64 controller being identified as mouse dmaengine: xilinx: xdma: Clarify kdoc in XDMA driver wifi: mac80211: don't use rate mask for scanning wifi: mac80211: ensure beacon is non-S1G prior to extracting the beacon timestamp field wifi: cfg80211: fix the order of arguments for trace events of the tx_rx_evt class dt-bindings: rockchip: grf: Add missing type to 'pcie-phy' node HID: mcp-2221: cancel delayed_work only when CONFIG_IIO is enabled net: usb: qmi_wwan: add Telit FN920C04 compositions drm/amd/display: Set color_mgmt_changed to true on unsuspend drm/amdgpu: Update BO eviction priorities drm/amd/pm: Restore config space after reset drm/amdkfd: Add VRAM accounting for SVM migration drm/amdgpu: Fix the ring buffer size for queue VM flush Revert "net: txgbe: fix i2c dev name cannot match clkdev" Revert "net: txgbe: fix clk_name exceed MAX_DEV_ID limits" cpu: Ignore "mitigations" kernel parameter if CPU_MITIGATIONS=n LoongArch: Lately init pmu after smp is online drm/etnaviv: fix tx clock gating on some GC7000 variants selftests: sud_test: return correct emulated syscall value on RISC-V riscv: thead: Rename T-Head PBMT to MAE UBUNTU: [Config] updateconfigs for ERRATA_THEAD_MAE riscv: T-Head: Test availability bit before enabling MAE errata sched/isolation: Fix boot crash when maxcpus < first housekeeping CPU ASoC: Intel: bytcr_rt5640: Apply Asus T100TA quirk to Asus T100TAM too regulator: irq_helpers: duplicate IRQ name ALSA: hda: cs35l56: Exit cache-only after cs35l56_wait_for_firmware_boot() ASoC: SOF: ipc4-pcm: Use consistent name for snd_sof_pcm_stream pointer ASoC: SOF: ipc4-pcm: Use consistent name for sof_ipc4_timestamp_info pointer ASoC: SOF: ipc4-pcm: Introduce generic sof_ipc4_pcm_stream_priv ASoC: SOF: pcm: Restrict DSP D0i3 during S0ix to IPC3 ASoC: acp: Support microphone from device Acer 315-24p ASoC: rt5645: Fix the electric noise due to the CBJ contacts floating ASoC: dt-bindings: rt5645: add cbj sleeve gpio property ASoC: rt722-sdca: modify channel number to support 4 channels ASoC: rt722-sdca: add headset microphone vrefo setting regulator: qcom-refgen: fix module autoloading regulator: vqmmc-ipq4019: fix module autoloading ASoC: cs35l41: Update DSP1RX5/6 Sourc
[Bug 2069357] Re: Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo Thunderbolt 3 Gen 2 USB-C dock
I think you mean 1025.26, and yes, it is still broken in that release. My team has also experienced other monitor related issues on the 6.8.0-38-generic kernel, so we are still hoping for a fix on 6.5 oem. We are using 6.5.0-1023 for the time being. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069357 Title: Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo Thunderbolt 3 Gen 2 USB-C dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2069357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070367] Re: FTBFS with new poppler
fixed. ** Changed in: inkscape (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070367 Title: FTBFS with new poppler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/2070367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
Did I understand correctly that this bug will be fixed after kernel 5.15.0-113? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068738 Title: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053243] Re: Confusing description of package
This was fixed in Debian in 2024041801 and was automatically sync'd in oracular. ** Changed in: dns-root-data (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053243 Title: Confusing description of package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dns-root-data/+bug/2053243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071476] Re: open-vm-tools version 12.4.5 has been released - please rebase
Thanks for the announcement, John. As open-vm-tools is currently in sync with Debian, I added a tracker to the related Debian bug here so this may likely be closed once the Debian bug gets addressed. ** Bug watch added: Debian Bug tracker #1074436 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074436 ** Also affects: open-vm-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074436 Importance: Unknown Status: Unknown ** Changed in: open-vm-tools (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071476 Title: open-vm-tools version 12.4.5 has been released - please rebase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2071476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054103] Re: grub-pc reinstallation throws a prompt asking the device it should install on for Noble
** Merge proposal linked: https://code.launchpad.net/~mkukri/ubuntu-release-upgrader/+git/ubuntu-release-upgrader-1/+merge/468504 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054103 Title: grub-pc reinstallation throws a prompt asking the device it should install on for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2054103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071625] [NEW] FTBFS against requests 2.32.3
Public bug reported: With the new release of requests 2.32.3 in oracular, requests-unixsocket fails to build as all requests to http+unix:// URLs fail with: requests.exceptions.InvalidURL: Not supported URL scheme http+unix. This can be fixed by including the patch provided here - https://github.com/msabramo/requests-unixsocket/pull/72 ** Affects: python-requests-unixsocket (Ubuntu) Importance: Undecided Assignee: Lena Voytek (lvoytek) Status: In Progress ** Changed in: python-requests-unixsocket (Ubuntu) Status: New => In Progress ** Changed in: python-requests-unixsocket (Ubuntu) Assignee: (unassigned) => Lena Voytek (lvoytek) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071625 Title: FTBFS against requests 2.32.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-requests-unixsocket/+bug/2071625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068562] Re: [SRU] libreoffice 24.2.4 for noble
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-5261 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068562 Title: [SRU] libreoffice 24.2.4 for noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2068562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071624] Re: CVE-2024-5261
** Patch added: "libreoffice_7.6.7-0ubuntu0.23.10.2.diff" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2071624/+attachment/5793805/+files/libreoffice_7.6.7-0ubuntu0.23.10.2.diff ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-5261 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071624 Title: CVE-2024-5261 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2071624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071624] [NEW] CVE-2024-5261
*** This bug is a security vulnerability *** Public security bug reported: CVE-2024-5261: "TLS certificate are not properly verified when utilizing LibreOfficeKit" https://www.libreoffice.org/about-us/security/advisories/cve-2024-5261/ https://cgit.freedesktop.org/libreoffice/core/commit/?id=fa4ceeb487f89671efc8bf533192bf237c35b51e https://gerrit.libreoffice.org/c/core/+/167753 https://ubuntu.com/security/CVE-2024-5261 * Noble 24.04: - Fix is included in 24.2.4 SRU - https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2068562 * Mantic 23.10: - Backport of patch to 7.6.7 required - https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/mantic-7.6 * Jammy 22.04: - 7.3.7 not affected * Focal 20.04: - 6.4.7 not affected ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libreoffice (Ubuntu Mantic) Importance: Medium Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Affects: libreoffice (Ubuntu Noble) Importance: Medium Status: In Progress ** Affects: libreoffice (Ubuntu Oracular) Importance: Undecided Status: Fix Released ** Also affects: libreoffice (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Mantic) Status: New => Fix Released ** Changed in: libreoffice (Ubuntu Noble) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Oracular) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Mantic) Status: Fix Released => In Progress ** Changed in: libreoffice (Ubuntu Oracular) Status: In Progress => Fix Released ** Changed in: libreoffice (Ubuntu Mantic) Assignee: (unassigned) => Rico Tzschichholz (ricotz) ** Changed in: libreoffice (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: libreoffice (Ubuntu Noble) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071624 Title: CVE-2024-5261 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2071624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069875] Re: [needs-packaging] cmocka-mocks
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069875 Title: [needs-packaging] cmocka-mocks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2069875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071627] [NEW] Merge dash 0.5.12-9 from debian unstable
Public bug reported: This is a tracking bug to merge dash 0.5.12-9 from debian unstable into the current 0.5.12-6ubuntu6 package. ** Affects: dash (Ubuntu) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Affects: dash (Ubuntu Oracular) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Tags: foundations-todo ** Changed in: dash (Ubuntu) Status: New => In Progress ** Tags added: foundations-todo ** Changed in: dash (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Also affects: dash (Ubuntu Oracular) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) 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/2071627 Title: Merge dash 0.5.12-9 from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2071627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071627] Re: Merge dash 0.5.12-9 from debian unstable
Also incorporate LP: #2028868 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071627 Title: Merge dash 0.5.12-9 from debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2071627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071628] [NEW] Fix QEMU/KVM support for EPT paging level 4/5
Public bug reported: This is a public version of: - https://bugs.launchpad.net/bugs/2055747 - https://bugs.launchpad.net/bugs/2058092 [ Impact ] * Fix EPT paging level 4 using incorrectly memory range. * Expose support of EPT paging level 5 for compatible hardware (e.g. Sierra Forest) [ Fix ] Clean cherry pick for the fix and associated self-tests. [ Test Plan ] On compatible hardware * Verify level 5 flag * Execute self-tests [ Where problems could occur ] * Regression in KVM features. [ Other info ] Context: https://lore.kernel.org/all/170864656017.3080257.14048100709856204250.b4...@google.com/ https://lore.kernel.org/all/171754268137.2777430.1222935014468693201.b4...@google.com/ ** Affects: linux-intel (Ubuntu) Importance: Undecided Status: New ** Affects: linux-intel (Ubuntu Noble) Importance: Undecided Assignee: Thibf (thibf) Status: In Progress ** Also affects: linux-intel (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-intel (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-intel (Ubuntu Noble) Assignee: (unassigned) => Thibf (thibf) ** Description changed: This is a public version of: - https://bugs.launchpad.net/bugs/2055747 - https://bugs.launchpad.net/bugs/2058092 [ Impact ] - * Fix EPT paging level 4 using incorrectly memory range. - * Expose support of EPT paging level 5 for compatible hardware (e.g. Sierra Forest) + * Fix EPT paging level 4 using incorrectly memory range. + * Expose support of EPT paging level 5 for compatible hardware (e.g. Sierra Forest) [ Fix ] - Clean cherry pick from next for the fix and associated self-tests. + Clean cherry pick for the fix and associated self-tests. [ Test Plan ] On compatible hardware - * Verify level 5 flag - * Execute self-tests + * Verify level 5 flag + * Execute self-tests [ Where problems could occur ] - * Regression in KVM features. - + * Regression in KVM features. [ Other info ] Context: https://lore.kernel.org/all/170864656017.3080257.14048100709856204250.b4...@google.com/ https://lore.kernel.org/all/171754268137.2777430.1222935014468693201.b4...@google.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071628 Title: Fix QEMU/KVM support for EPT paging level 4/5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel/+bug/2071628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071476] Re: open-vm-tools version 12.4.5 has been released - please rebase
** Changed in: open-vm-tools (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071476 Title: open-vm-tools version 12.4.5 has been released - please rebase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/2071476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1992643] Re: Implement boot-complete.target
This bug was fixed in the package grub2 - 2.12-1ubuntu9 --- grub2 (2.12-1ubuntu9) oracular; urgency=medium * Cherry-pick upstream efi mm patches to avoid crashing at exit on Mu * peimage: Improve section consistency checks, use grub_dprintf for errors * peimage: Make sure partially loaded images are unloaded on error * Implement support for UEFI NX mitigation * Cherry-pick missing TDX measurements fix (LP: #2069232) * grub-common.service: Add After/Requires=boot-complete.target (LP: #1992643) * d/postinst.in: Remove upgrade check for GRUB version we can no longer upgrade from * Cherry-pick fdtdump patch -- Mate Kukri Wed, 19 Jun 2024 11:47:16 +0100 ** Changed in: grub2 (Ubuntu) Status: In Progress => 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/1992643 Title: Implement boot-complete.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1992643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs (if autologin is enabled and Xorg is used)
While this is being investigated and a fix will be pushed, by disabling auto login (For the moment) fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs (if autologin is enabled and Xorg is used) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2064177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064177] Re: Window borders and shadows missing from GTK3 dialogs (if autologin is enabled and Xorg is used)
While this is being investigated and a fix will be pushed, by disabling auto login (For the moment) fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs (if autologin is enabled and Xorg is used) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2064177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071565] Re: Xorg freeze
I believe this error could be related https://errors.ubuntu.com/oops/e248144a-310e-11ef-9e7f-fa163ec44ecd Other crashes seem to be unrelated, however the date from this crash seems a bit earlier than my latest crash. Most often the game causes a freeze and no crash, and hangs the entire desktop environment (KDE) until it closes with no indication of why it closed. The freezes I get usually: Entire desktop goes unresponsive (not just team fortress 2) I swap to tty to kill the process, or wait, and it does close after a while. To kill the process in tty I use 'kill -kill $(pidof tf_linux64)' Randomly it is possible to get the errors after killing the process. I swap back to my X session. Firefox crashes, and Thunderbird doesn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071565 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2071565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067815] Re: dbmanage sync fails to run
Digging into this further as the autopkgtests for this package validate the db migrations against MySQL so I'm surprised they fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067815 Title: dbmanage sync fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/watcher/+bug/2067815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039368] Re: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
** Description changed:
+ [Impact]
+
+ Currently there are UBSAN warnings that show up when running bcache on
+ jammy HWE, Mantic and noble. For now no side effects have been observed
+ but such an issue could potentially cause a crash or corrupt data.
+
+ [Fix]
+
+ There is currently a fix upstream provided by the following patch:
+
+ * 3a861560ccb3 "bcache: fix variable length array abuse in btree_iter"
+
+ [Test Case]
+
+ - Setup bcache on a jammy HWE kernel or mantic or noble machine.
+ This can be done following the steps in this wiki:
https://wiki.ubuntu.com/ServerTeam/Bcache
+ - Restart the machine
+ - After restarting the machine UBSAN warnings and call traces can be seen in
dmesg.
+
+ [Where problems could occur]
+
+ -The patch modifies the way bcache allocates space to the btree
+ iterator. The main problems that could occur are different UBSAN
+ warnings showing up that could possibly trigger a crash much easier than
+ the current array index-out-of-bounds being observed.
+
+
+ Thank you @illwieckz for the original bug report
+ [original description]
+
Since I upgraded from lunar to mantic I get a load of those errors (41
on a fresh boot) in dmesg:
```
[4.277343] UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
[4.277728] index 4 is out of range for type 'btree_iter_set [4]'
[4.277925] CPU: 7 PID: 247 Comm: kworker/7:1 Not tainted 6.5.0-9-generic
#9-Ubuntu
[4.278132] Hardware name: Default string Default string/Default string,
BIOS WRX80SU8-F6 06/08/2023
[4.278531] Workqueue: events register_cache_worker [bcache]
[4.278754] Call Trace:
[4.278949]
[4.279143] dump_stack_lvl+0x48/0x70
[4.279337] dump_stack+0x10/0x20
[4.279526] __ubsan_handle_out_of_bounds+0xc6/0x110
[4.279721] bch_btree_iter_push+0x4e6/0x4f0 [bcache]
[4.279929] bch_btree_node_read_done+0xcb/0x410 [bcache]
[4.280142] bch_btree_node_read+0xf8/0x1e0 [bcache]
[4.280349] ? __pfx_closure_sync_fn+0x10/0x10 [bcache]
[4.280557] bch_btree_node_get.part.0+0x15c/0x330 [bcache]
[4.280764] ? __bch_btree_ptr_invalid+0x66/0xe0 [bcache]
[4.280975] ? __pfx_up_write+0x10/0x10
[4.281170] bch_btree_node_get+0x16/0x30 [bcache]
[4.281375] run_cache_set+0x596/0x850 [bcache]
[4.281578] ? srso_return_thunk+0x5/0x10
[4.281773] register_cache_set+0x1a2/0x210 [bcache]
[4.281984] register_cache+0x11a/0x1a0 [bcache]
[4.282187] register_cache_worker+0x22/0x80 [bcache]
[4.282387] process_one_work+0x223/0x440
[4.282573] worker_thread+0x4d/0x3f0
[4.282753] ? srso_return_thunk+0x5/0x10
[4.282931] ? _raw_spin_lock_irqsave+0xe/0x20
[4.283113] ? __pfx_worker_thread+0x10/0x10
[4.283286] kthread+0xf2/0x120
[4.283458] ? __pfx_kthread+0x10/0x10
[4.283631] ret_from_fork+0x47/0x70
[4.283800] ? __pfx_kthread+0x10/0x10
[4.283972] ret_from_fork_asm+0x1b/0x30
[4.284143]
```
This system has 4 bcache backing devices and 4 bcache cache devices,
though they are not associated for now and caching is disabled. It was
already like that when I upgraded, so the kernel only uses the backing
code, not the caching one.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Oct 14 23:16:33 2023
HibernationDevice: RESUME=none
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB:
- 0 amdgpudrmfb
- 1 astdrmfb
+ 0 amdgpudrmfb
+ 1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
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.5.0-9-generic N/A
- linux-backports-modules-6.5.0-9-generic N/A
- linux-firmware 20230919.git3672ccab-0ubuntu2.1
+ linux-restricted-modules-6.5.0-9-generic N/A
+ linux-backports-modules-6.5.0-9-generic N/A
+ linux-firmware 20230919.git3672ccab-0ubuntu2.1
RfKill:
-
+
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: De
[Bug 2069081] Re: idxd: NULL pointer dereference reading wq op_config attribute
** Tags removed: verification-needed-jammy-linux-nvidia ** Tags added: verification-done-jammy-linux-nvidia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069081 Title: idxd: NULL pointer dereference reading wq op_config attribute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049529] Re: Ubuntu delta causes `can't open /dev/null: No such file or directory` errors in minimal environments (chroot/unshare)
Can we deliver a fix (or workaround) to this that consists in checking
if /dev/null is a char device?
if (-c "/dev/null") {
append ">/dev/null" to command
}
Not great, but should fix adduser and useradd in environments where /dev
is not populated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049529
Title:
Ubuntu delta causes `can't open /dev/null: No such file or directory`
errors in minimal environments (chroot/unshare)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2049529/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039368] Re: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039368 Title: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297025] Re: Either the changelog.gz is missing or there is an erroneous link in the libssl1.0.0 package
** Changed in: openssl (Ubuntu) Status: Triaged => 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/1297025 Title: Either the changelog.gz is missing or there is an erroneous link in the libssl1.0.0 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1297025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071459] Re: Respect CC and CFLAGS environment variables (frame pointer)
** Patch added: "2-gobi-loader_0.7-0ubuntu7.diff" https://bugs.launchpad.net/ubuntu/+source/gobi-loader/+bug/2071459/+attachment/5793862/+files/2-gobi-loader_0.7-0ubuntu7.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071459 Title: Respect CC and CFLAGS environment variables (frame pointer) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobi-loader/+bug/2071459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067672] Re: [SRU] Openssl copyright/changelog.Debian.gz file points at non-existent location
Hey, a quick update. With openssl 3.2.1 uploaded to Oracular, I've prepared the subsequent 3.2.2 (doing it so soon wasn't planned initially). I'm including a fix for this and for #1297025 : https://git.launchpad.net/~adrien/ubuntu/+source/openssl/commit/?id=5f94de31126ae59f2481fe77a397df9fb0941bd8 This will satisfy the SRU requirement that the fix is first included in the development release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067672 Title: [SRU] Openssl copyright/changelog.Debian.gz file points at non- existent location To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2067672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install 060
** Description changed: [ Impact ] When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u - Time (mean ± σ): 402.751 s ± 5.592 s[User: 166.316 s, System: 228.909 s] - Range (min … max): 394.380 s … 411.445 s10 runs + Time (mean ± σ): 402.751 s ± 5.592 s[User: 166.316 s, System: 228.909 s] + Range (min … max): 394.380 s … 411.445 s10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible regressions (see comment #15). Only miniramfs needs to be adjusted to also call `apply_add_modules`. But this change could break consumers of the `manual_add_modules` function that are outside of the Ubuntu archive. I googled for `apply_add_modules` but found no public outside users. + [ Benchmarks ] + + Stock noble on a Raspberry Pi Zero 2W: + + ``` + bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" + Benchmark 1: update-initramfs -u + Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] + Range (min … max): 409.139 s … 422.632 s 5 runs + ``` + [ Other Info ] $ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 $ apt-cache policy dracut-install dracut-install: Installed: 060+5-1ubuntu3 Candidate: 060+5-1ubuntu3 Version table: *** 060+5-1ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install 060 To manage notifications about this bug go to: https://bugs.launchpad.net/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054222] Re: virtiofsd is no longer installed by default in 24.04 when virt-manager/qemu is installed.
I added the rust-virtiofsd package to my Ubuntu 24.04 install, which I upgraded from 22.04. Still not working as virtiofsd cannot write a log file to var/log/libvirt/qemu even when folder is RW for everyone -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054222 Title: virtiofsd is no longer installed by default in 24.04 when virt- manager/qemu is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-virtiofsd/+bug/2054222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068804] Re: very very very slow even though a quite well system
Ubuntu Studio 24.04 LTS, i was using and the reinstalled system is also the same one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068804 Title: very very very slow even though a quite well system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068804] Re: very very very slow even though a quite well system
I could finally reinstall the system: and testing since ~ an hour. No problem, everything is well, running as usually expected. Ubuntu 24.04 LTS with full packages installed. Meaning, the visibly no errors -as it can be in the best "ideal case". Since that means the defined conditions of errors are not satisfied by the current interactions of different hardware and the software, issue is closed. It was because of the problematic update from the old system. 23.10 to 24.04. All Hardware is running fine, as there was no material traces of hardware problem. And whatever unknown unavoidable "errors" happening, is not causing any visible problems. If i see a problematic symptoms or visible errors, i will be updating. Thanks for brainstorming together Daniel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068804 Title: very very very slow even though a quite well system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719169] Re: hp-toolbox cannot start
Still have the problem with: Ubuntu 24.04 LTS kernel Linux 6.8.0-36-generic HPLIP 3.24.4 HP Device Manager ver. 15.0 Anyone who got it working on this configuration ? -- 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/1719169 Title: hp-toolbox cannot start To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1719169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071560] Re: chromium not visible to user, system says it's both intalled and not installed
Thanks for responding. the words in parentheses are the error messages that pop up. As described, I tried reinstalling and it didn't work. The system thinks it's both installed and not installed, but won't uninstall it or reinstall it. Firefox is working fine, but some websites don't like it, so I used Chromium as a backup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071560 Title: chromium not visible to user, system says it's both intalled and not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2071560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066035] Re: KWM Switch causes logout
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: meta-gnome3 (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/2066035 Title: KWM Switch causes logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/2066035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
== History == Prior to nvidia 545 the driver did not provide a framebuffer and instead relied on framebuffers from CONFIG_EFI_FB and CONFIG_VESA_FB alike. SimpleDRM (required on a modern Wayland-only system) can also provide a framebuffer (simplefb), and indeed Ubuntu does not use EFI_FB and VESA_FB anymore, relying purely on SimpleDRM to provide a fallback framebuffer. However SimpleDRM also provides a DRM device which creates this phantom display. Since nvidia 545, the driver has gained the capability to provide a framebuffer device, currently opt-in with the option `nvidia- drm.fbdev=1`. Enabling this makes SimpleDRM go away like it would with amdgpu or i915 (*currently racy, see [1]). == Solutions == 1. The first option is to enable fbdev=1 by default, like we do for nvidia-drm.modeset=1. This is still considered to be in test-stage by nvidia, and unfortunately on my Ubuntu machine it breaks any graphical session with bug [2]. NB: somehow this bug does not happen on my Fedora install, where fbdev=1 is already the default. 2. Prior to having the nvidia-drm.fbdev option in Fedora we would instead disable SimpleDRM if-and-only-if the nvidia driver is installed. You may achieve this either by appending `initcall_blacklist=simpledrm_platform_driver_init` to the kernel commandline through a package install-time script, or through a patch like [3]. But we are now left with no framebuffer device, so switching VT leaves you with a black screen (imho unacceptable). The solution to that issue is to enable CONFIG_EFI_FB/CONFIG_VESA_FB again so that nvidia systems will keep access to VTs, albeit low-res ones compared to simplefb. [1]: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/2063143 [2]: https://forums.developer.nvidia.com/t/545-29-06-18-1-flip-event-timeout-error-on-startup-shutdown-and-sometimes-suspend-wayland-unusable/274788 [3]: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1788/diffs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064850] Re: ubuntu noble install error warnings in noble
This is likely due to missing Python 3.12 support upstream: $ python3 -c '"(\r\n|\r|\n)\Z"' :1: SyntaxWarning: invalid escape sequence '\Z' $ python3.11 -c '"(\r\n|\r|\n)\Z"' # installed via pyenv $ It was added in 1.0.0: https://github.com/PythonCharmers/python-future/pull/632 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064850 Title: ubuntu noble install error warnings in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-future/+bug/2064850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310789] Re: bash-completion crash
** Changed in: bash (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/310789 Title: bash-completion crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/310789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071640] [NEW] python3-future 0.18.2 is not compatible with Python 3.12
Public bug reported: $ python3 -c 'from future import standard_library' Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/future/standard_library/__init__.py", line 65, in import imp ModuleNotFoundError: No module named 'imp' Python 3.12 support was added upstream in v1.0.0: https://github.com/PythonCharmers/python-future/commit/ba1cc505f1cb8eb0dfe495174f05aaec5a01eef3 ** Affects: python-future (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/2071640 Title: python3-future 0.18.2 is not compatible with Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-future/+bug/2071640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install 060
** Description changed: [ Impact ] When compared to Ubuntu 23.10, creating intramfs files with update- initramfs takes 2 to 5 times more time on ARM devices. IIUC, dracut-install usage was added to initramfs-tools to speed up the process. But now its way slower. Even running update-initramfs on jammy, which doesn't use dracut-install, is way faster then the time taken on Noble. first bad commit - https://github.com/dracutdevs/dracut/commit/3de4c7313260fb600507c9b87f780390b874c870 Updating the initrd on a Raspberry Pi Zero 2W on Ubuntu 24.04 (noble) with initramfs-tools 0.142ubuntu25.1 takes over six minutes: ``` bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 402.751 s ± 5.592 s[User: 166.316 s, System: 228.909 s] Range (min … max): 394.380 s … 411.445 s10 runs ``` [ Test Plan ] 1. Measure `update-initramfs -u` before the update. 2. Log the content of the initrd before the update: `lsinitramfs /boot/initrd.img` 3. update dracut-install / initramfs-tools-core 4. Measure `update-initramfs -u`. It should be faster (the performance improvements on amd64 should be very small and might be within the measurement uncertainty). 5. Check with lsinitramfs that the content of the newly generated initrd hasn't changed. [ Where problems could occur ] The code that is responsible for including the kernel modules into the initrd is touched. Negative consequences could be that some needed kernel modules will not be included any more (should be covered by the test case) or that building new initrds will fail. The initramfs-tools fix changes how manual_add_modules behaves. `manual_add_modules` does not copy kernel modules, but queues them for being copied when the newly added function `apply_add_modules` is called. I checked all instances of calls to `manual_add_modules` for possible regressions (see comment #15). Only miniramfs needs to be adjusted to also call `apply_add_modules`. But this change could break consumers of the `manual_add_modules` function that are outside of the Ubuntu archive. I googled for `apply_add_modules` but found no public outside users. [ Benchmarks ] Stock noble on a Raspberry Pi Zero 2W: ``` bdrung@zero2w:~$ sudo hyperfine -r 5 "update-initramfs -u" Benchmark 1: update-initramfs -u - Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] - Range (min … max): 409.139 s … 422.632 s 5 runs + Time (mean ± σ): 415.664 s ± 6.015 s [User: 166.728 s, System: 232.523 s] + Range (min … max): 409.139 s … 422.632 s 5 runs + ``` + + noble with dracut-install 060+5-1ubuntu3.1 (with linux 6.8.0-1006.6 on + 2024-07-01): + + ``` + bdrung@zero2w:~$ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" + Benchmark 1: update-initramfs -u + Time (mean ± σ): 248.054 s ± 5.569 s[User: 67.410 s, System: 169.412 s] + Range (min … max): 238.909 s … 257.384 s10 runs ``` [ Other Info ] $ lsb_release -rd No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 $ apt-cache policy dracut-install dracut-install: Installed: 060+5-1ubuntu3 Candidate: 060+5-1ubuntu3 Version table: *** 060+5-1ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install 060 To manage notifications about this bug go to: https://bugs.launchpad.net/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071625] Re: FTBFS against requests 2.32.3
** Merge proposal linked: https://code.launchpad.net/~lvoytek/ubuntu/+source/python-requests-unixsocket/+git/python-requests-unixsocket/+merge/468520 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071625 Title: FTBFS against requests 2.32.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-requests-unixsocket/+bug/2071625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071537] Re: kubuntu 24.04 freezes when AC plug into laptop
My laptop froze again and I found more error message: krillavilla@Omen:~$ journalctl -p 3 -xb Journal file /var/log/journal/851d1be6b61f4acd90c605f9fd5b4e62/system@00061bf712ad6b62-83453c078195276f.journal~ is truncated, ignoring file. Jul 01 09:19:37 Omen kernel: x86/cpu: SGX disabled by BIOS. Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: x86/cpu: SGX disabled by BIOS. Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230628/psobject-220) Jul 01 09:19:37 Omen kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_E> Jul 01 09:19:37 Omen kernel: ACPI Error: AE_
[Bug 2071537] Re: kubuntu 24.04 freezes when AC plug into laptop
krillavilla@Omen:~$ sudo journalctl -k | sudo grep ACPI sudo dmesg | grep ACPI Journal file /var/log/journal/851d1be6b61f4acd90c605f9fd5b4e62/system@00061bf712ad6b62-83453c078195276f.journal~ is truncated, ignoring file. Jul 01 09:19:37 Omen kernel: BIOS-e820: [mem 0x377ab000-0x37833fff] ACPI data Jul 01 09:19:37 Omen kernel: BIOS-e820: [mem 0x37834000-0x37d8bfff] ACPI NVS Jul 01 09:19:37 Omen kernel: reserve setup_data: [mem 0x377ab000-0x37833fff] ACPI data Jul 01 09:19:37 Omen kernel: reserve setup_data: [mem 0x37834000-0x37d8bfff] ACPI NVS Jul 01 09:19:37 Omen kernel: efi: ACPI 2.0=0x377ce000 ACPI=0x377ce000 TPMFinalLog=0x37cf2000 SMBIOS=0x3a9b9000 SMBIOS 3.0=0x3a9b8000 MEMATTR=0x346f5018 ESRT=0x34349818 MOKvar=0x3a9d1000 INITRD=0x2d8c2518 RNG=0x377c5018 TPMEventLog=0x2d8b7018 Jul 01 09:19:37 Omen kernel: ACPI: Early table checksum verification disabled Jul 01 09:19:37 Omen kernel: ACPI: RSDP 0x377CE000 24 (v02 HPQOEM) Jul 01 09:19:37 Omen kernel: ACPI: XSDT 0x377CE0C8 000114 (v01 HPQOEM SLIC-MPC 01072009 HP 00010013) Jul 01 09:19:37 Omen kernel: ACPI: FACP 0x37821060 000114 (v06 HPQOEM SLIC-MPC 01072009 HP 00010013) Jul 01 09:19:37 Omen kernel: ACPI: DSDT 0x377CE270 052DEE (v02 HPQOEM 8466 01072009 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: FACS 0x37D87080 40 Jul 01 09:19:37 Omen kernel: ACPI: APIC 0x37821178 F4 (v04 HPQOEM 8466 01072009 HP 00010013) Jul 01 09:19:37 Omen kernel: ACPI: FPDT 0x37821270 44 (v01 HPQOEM 8466 01072009 HP 00010013) Jul 01 09:19:37 Omen kernel: ACPI: FIDT 0x378212B8 9C (v01 HPQOEM 8466 01072009 HP 00010013) Jul 01 09:19:37 Omen kernel: ACPI: MCFG 0x37821358 3C (v01 HPQOEM 8466 01072009 HP 0097) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x37821398 0035F5 (v02 HPQOEM 8466 1000 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x37824990 001B5A (v02 HPQOEM 8466 3000 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: MSDM 0x378264F0 55 (v03 HPQOEM SLIC-MPC 0001 HP 00010013) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x37826548 0031C6 (v02 HPQOEM 8466 3000 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x37829710 0025D8 (v02 HPQOEM 8466 1000 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: HPET 0x3782BCE8 38 (v01 HPQOEM 8466 0002 HP 0113) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x3782BD20 002999 (v02 HPQOEM 8466 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: UEFI 0x3782E6C0 42 (v01 HPQOEM 8466 0002 HP 0113) Jul 01 09:19:37 Omen kernel: ACPI: LPIT 0x3782E708 5C (v01 HPQOEM 8466 0002 HP 0113) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x3782E768 001423 (v02 HPQOEM 8466 1000 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x3782FB90 0005C7 (v02 HPQOEM 8466 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: DBGP 0x37830158 34 (v01 HPQOEM 8466 0002 HP 0113) Jul 01 09:19:37 Omen kernel: ACPI: DBG2 0x37830190 54 (v00 HPQOEM 8466 0002 HP 0113) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x378301E8 000DEA (v02 HPQOEM 8466 1000 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: DMAR 0x37830FD8 A8 (v01 HPQOEM 8466 0002 HP 0113) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x37831080 000144 (v02 HPQOEM 8466 1000 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x378311C8 AE (v02 HPQOEM 8466 1000 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x37831278 5E (v01 HPQOEM 8466 0001 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x378312D8 60 (v01 HPQOEM 8466 0001 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: UEFI 0x37831338 00063A (v01 HPQOEM 8466 HP ) Jul 01 09:19:37 Omen kernel: ACPI: UEFI 0x37831978 5C (v01 HPQOEM 8466 HP ) Jul 01 09:19:37 Omen kernel: ACPI: TPM2 0x378319D8 34 (v04 HPQOEM 8466 0001 HP ) Jul 01 09:19:37 Omen kernel: ACPI: SSDT 0x37831A10 002111 (v01 HPQOEM 8466 1000 ACPI 20160527) Jul 01 09:19:37 Omen kernel: ACPI: WSMT 0x37833B28 28 (v01 HPQOEM 8466 01072009 HP 00010013) Jul 01 09:19:37 Omen kernel: ACPI: BGRT 0x37833B50 38 (v01 HPQOEM 8466 01072009 HP 00010013) Jul 01 09:19:37 Omen kernel: ACPI: Reserving FACP table memory at [mem 0x37821060-0x37821173] Jul 01 09:19:37 Omen kernel: ACPI: Reserving DSDT table memory at [mem 0x377ce270-0x3782105d] Jul 01 09:19:37 Omen kernel: ACPI: Reserving FACS table memory at [mem 0x37d87080-0x37d870bf] Jul 01 09:19:37 Omen kernel: ACPI: Reservin
[Bug 2054222] Re: virtiofsd is no longer installed by default in 24.04 when virt-manager/qemu is installed.
Quick hint from investigating.
I installed the librust-virtiofsd-dev and virtiofsd as in 24.04 it is not
standard anymore via apt.
Still VMs are not working.
Problem: for the older VM which had posix=on and flock=on in the virtiofsd
section in the XML file I had to remove it --> Solved the issue
Problem: virtualfsd cannot write to /var/log/libvirt/qemu
Not working: rw right on the /var/log/libvirt/qemu
Disabling AppArmor for libvirtd -> reboot -> solved the problem but is only a
workaround
Still, reason unknown as in the apparmor profile: "libvirtd" the permissions
for virtiofsd are good:
/usr/{lib,lib64,lib/qemu,libexec}/virtiofsd PUx,
is in and should include the new /usr/libexec/virtiofsd as ok to run.
As I am not an AppArmor specalist, no glue why this was the issue.
I hope my short analysis is helping you as with this I got my machines running
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054222
Title:
virtiofsd is no longer installed by default in 24.04 when virt-
manager/qemu is installed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-virtiofsd/+bug/2054222/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024258] Re: Performance degradation archiving DB with large numbers of FK related records
** Description changed: [Impact] Originally, Nova archives deleted rows in batches consisting of a maximum number of parent rows (max_rows) plus their child rows, all within a single database transaction. This approach limits the maximum value of max_rows that can be specified by the caller due to the potential size of the database transaction it could generate. Additionally, this behavior can cause the cleanup process to frequently encounter the following error: oslo_db.exception.DBError: (pymysql.err.InternalError) (3100, "Error on observer while running replication hook 'before_commit'.") The error arises when the transaction exceeds the group replication transaction size limit, a safeguard implemented to prevent potential MySQL crashes [1]. The default value for this limit is approximately 143MB. [Fix] An upstream commit has changed the logic to archive one parent row and its related child rows in a single database transaction. This change allows operators to choose more predictable values for max_rows and achieve more progress with each invocation of archive_deleted_rows. Additionally, this commit reduces the chances of encountering the issue where the transaction size exceeds the group replication transaction size limit. commit 697fa3c000696da559e52b664c04cbd8d261c037 Author: melanie witt CommitDate: Tue Jun 20 20:04:46 2023 + - database: Archive parent and child rows "trees" one at a time + database: Archive parent and child rows "trees" one at a time [Test Plan] 1. Create an instance and delete it in OpenStack. 2. Log in to the Nova database and confirm that there is an entry with a deleted_at value that is not NULL. select display_name, deleted_at from instances where deleted_at <> 0; 3. Execute the following command, ensuring that the timestamp specified in --before is later than the deleted_at value: nova-manage db archive_deleted_rows --before "XXX-XX-XX XX:XX:XX" --verbose --until-complete 4. Log in to the Nova database again and confirm that the entry has been archived and removed. select display_name, deleted_at from instances where deleted_at <> 0; [Where problems could occur] The commit changes the logic for archiving deleted entries to reduce the size of transactions generated during the operation. If the patch contains errors, it will only impact the archiving of deleted entries and will not affect other functionalities. [1] https://bugs.mysql.com/bug.php?id=84785 + + [Original Bug Description] + + Observed downstream in a large scale cluster with constant create/delete + server activity and hundreds of thousands of deleted instances rows. + + Currently, we archive deleted rows in batches of max_rows parents + + their child rows in a single database transaction. Doing it that way + limits how high a value of max_rows can be specified by the caller + because of the size of the database transaction it could generate. + + For example, in a large scale deployment with hundreds of thousands of + deleted rows and constant server creation and deletion activity, a + value of max_rows=1000 might exceed the database's configured maximum + packet size or timeout due to a database deadlock, forcing the operator + to use a much lower max_rows value like 100 or 50. + + And when the operator has e.g. 500,000 deleted instances rows (and + millions of deleted rows total) they are trying to archive, being + forced to use a max_rows value several orders of magnitude lower than + the number of rows they need to archive is a poor user experience and + makes it unclear if archive progress is actually being made. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024258 Title: Performance degradation archiving DB with large numbers of FK related records To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/2024258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071620] Re: Subiquity segfaults in extract_ssid
Hi and thank you for your report. Could you please also attach the logs in /var/log/installer? ** Also affects: subiquity Importance: Undecided Status: New ** Changed in: subiquity 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/2071620 Title: Subiquity segfaults in extract_ssid To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2071620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071613] Re: gcc-13 fails to build
** Description changed: gcc-13 fails to build. This is blocking the octave transition. plplot needs to migrate for the transition to complete. plplot has gained a dependency on gcc-13 in oracular-proposed. If this is not easily fixable, maybe it would help if gcc-13 were - temporarily removed from -proposed and plplot rebuild to not depend on - the newer gcc-13. + temporarily removed from -proposed and then we rebuild plplot to not + depend on the newer gcc-13. There is also an ada transition entangled in the new gcc-13 but I don't think that's as annoying. octave is showing up on the NBS report for gdal (and therefore poppler). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071613 Title: gcc-13 fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2071613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071537] Re: kubuntu 24.04 freezes when AC plug into laptop
I added quiet splash acpi=off to my grub file. I will provide an update if that helps with my freezing issue. # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT_STYLE=menu GRUB_TIMEOUT=1 GRUB_DISTRIBUTOR='Kubuntu' GRUB_CMDLINE_LINUX_DEFAULT='quiet splash acpi=0ff' GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0" # If your computer has multiple operating systems installed, then you # probably want to run os-prober. However, if your computer is a host # for guest OSes installed via LVM or raw disk devices, running # os-prober can cause damage to those guest OSes as it mounts # filesystems to look for things. #GRUB_DISABLE_OS_PROBER=false # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal #GRUB_TERMINAL=console # The resolution used on graphical terminal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071537 Title: kubuntu 24.04 freezes when AC plug into laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/2071537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
I can work on this after I finish a couple of other work items I have on my plate right now. I think an estimation would be next month. If anyone else is willing to fix this before I have the time, I'd happily hand it over to you :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
Hello Tasmiya, many thanks that you retried with latest kernel -36. So we'll focus then on incl. commit 8e948c365d9c nfsd: fix oops when reading pool_stats before server is started I just noticed that it's now upstream with v6.10-rc5. ** Changed in: sosreport (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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2070358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865177] Re: There is an erroneous extra dot in package name
** Changed in: gnome-calendar (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865177 Title: There is an erroneous extra dot in package name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1865177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071643] [NEW] Blue box appear on half of the screen when switching between windows
Public bug reported: When I switch between two windows using alt-tab a blue window overlap half of the screen (I think it's the same type of window than the one displayed when a window is dragged to the edge of the screen). This started after I updated from 22.04 to 24.04 To reproduce the issue: Open two program, Maximize the two program Switch using alt-tab between the two window What happens: A blue square overlap half of the screen What I expect Switch between the two program without the blue square Release 24.04 xorg: Installed: 1:7.7+23ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4 Uname: Linux 6.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.183.01 Sun May 12 19:39:15 UTC 2024 GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 19:37:20 2024 DistUpgraded: 2024-06-15 01:16:48,692 INFO cache.commit() DistroCodename: noble DistroVariant: ubuntu DkmsStatus: nvidia/535.183.01, 6.8.0-35-generic, x86_64: installed nvidia/535.183.01, 6.8.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell TigerLake-H GT1 [UHD Graphics] [1028:0a82] Subsystem: Dell GA107M [GeForce RTX 3050 Ti Mobile] [1028:0a82] InstallationDate: Installed on 2022-02-08 (874 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Vostro 15 7510 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=7335a34d-d830-4310-a913-c6f78b94c751 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-06-14 (17 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0TW2DN dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd11/05/2021:br1.3:svnDellInc.:pnVostro157510:pvr:rvnDellInc.:rn0TW2DN:rvrA01:cvnDellInc.:ct10:cvr:sku0A82: dmi.product.family: Vostro dmi.product.name: Vostro 15 7510 dmi.product.sku: 0A82 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ubuntu wayland-session ** Attachment added: "Screenshot showing the blue rectangle" https://bugs.launchpad.net/bugs/2071643/+attachment/5793884/+files/Screenshot%20from%202024-07-01%2019-44-17.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071643 Title: Blue box appear on half of the screen when switching between windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2071643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071644] [NEW] sometimes takes ~5 seconds to _dma_fmt_to_dma_drm_fmts: assertion 'fmt != GST_VIDEO_FORMAT_UNKNOWN' failed
Public bug reported:
since upgrading to noble, sometimes the following bit of code works
instantaneously, and sometimes it takes ~5 seconds to report:
** (gst-plugin-scanner:692358): CRITICAL **: 10:55:31.508:
_dma_fmt_to_dma_drm_fmts: assertion 'fmt != GST_VIDEO_FORMAT_UNKNOWN'
failed
code:
>>> import cv2
>>> vc = cv2.VideoCapture('/dev/video2')
when it takes a long time and reports the assertion error, I see the
following in journalctl logs (so maybe an amd/kernel bug instead of an
opencv bug? -- also fwiw am on a hybrid amd/intel system where
DRI_PRIME=1 generally activates the amd card but this should be running
w/out DRI_PRIME set):
Jul 01 10:55:29 taplop kernel: [drm] scheduler comp_1.2.1 is not ready, skipping
Jul 01 10:55:29 taplop kernel: [drm] PCIE GART of 256M enabled (table at
0x00F4).
Jul 01 10:55:30 taplop kernel: amdgpu :01:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.1.0 test failed
(-110)
Jul 01 10:55:30 taplop kernel: amdgpu :01:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.2.0 test failed
(-110)
Jul 01 10:55:30 taplop kernel: amdgpu :01:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.3.0 test failed
(-110)
Jul 01 10:55:30 taplop kernel: amdgpu :01:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.0.1 test failed
(-110)
Jul 01 10:55:30 taplop kernel: amdgpu :01:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.1.1 test failed
(-110)
Jul 01 10:55:31 taplop kernel: amdgpu :01:00.0:
[drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring comp_1.2.1 test failed
(-110)
Jul 01 10:55:31 taplop kernel: [drm] UVD and UVD ENC initialized successfully.
Jul 01 10:55:31 taplop kernel: [drm] VCE initialized successfully.
Jul 01 10:55:31 taplop kernel: [drm] scheduler comp_1.1.0 is not ready, skipping
Jul 01 10:55:31 taplop kernel: [drm] scheduler comp_1.2.0 is not ready, skipping
Jul 01 10:55:31 taplop kernel: [drm] scheduler comp_1.3.0 is not ready, skipping
Jul 01 10:55:31 taplop kernel: [drm] scheduler comp_1.0.1 is not ready, skipping
<<< not ready skipping lines repeat a whole bunch of times >>>
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: python3-opencv 4.6.0+dfsg-13.1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
Uname: Linux 6.8.0-35-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Jul 1 10:59:12 2024
InstallationDate: Installed on 2019-08-17 (1781 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: opencv
UpgradeStatus: Upgraded to noble on 2024-03-23 (100 days ago)
** Affects: opencv (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071644
Title:
sometimes takes ~5 seconds to _dma_fmt_to_dma_drm_fmts: assertion 'fmt
!= GST_VIDEO_FORMAT_UNKNOWN' failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/2071644/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726548] Re: Windows resized after resume
I'm on a newly installed ubuntu 24.04 (assuming Wayland) and gnome- shell, and also have this issue with at least firefox and open office (don't run most of my other apps fullscreen). `gsettings set org.gnome.desktop.interface scaling-factor 1` doesn't seem to help. It also seems to me that some reports here, e.g. by Jens Glathe (glathe), seem to be a different issue where the whole desktop gets rendered in the wrong size/resolution/position after suspend & resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726548 Title: Windows resized after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071645] [NEW] resize.f2fs fails with "Error: Device size is not sufficient for F2FS volume, more segment needed"
Public bug reported: Terminal transcript of a simple reproduction: kuebi@twobuntu:/tmp$ truncate -s 512M testfs # create a (sparse) file to hold a test filesystem kuebi@twobuntu:/tmp$ mkfs.f2fs testfs F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24) Info: Disable heap-based policy Info: Debug level = 0 Info: Trim is enabled Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 1048576 (512 MB) Info: zone aligned segment0 blkaddr: 512 Info: format version with "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" Info: [testfs] Discarding device Info: Overprovision ratio = 10.000% Info: Overprovision segments = 50 (GC reserved = 28) Info: format successful kuebi@twobuntu:/tmp$ truncate -s 1G testfs # grow the backing storage kuebi@twobuntu:/tmp$ resize.f2fs testfs # try to resize to fit Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 2097152 (1024 MB) Info: MKFS version "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" Info: FSCK version from "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" to "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" Info: superblock features = 0 : Info: superblock encrypt level = 0, salt = Info: total FS sectors = 1048576 (512 MB) Info: CKPT version = 420523bb Info: Duplicate valid checkpoint to mirror position 512 -> 1024 Info: Write valid nat_bits in checkpoint Error: Device size is not sufficient for F2FS volume, more segment needed =19508kuebi@twobuntu:/tmp$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: f2fs-tools 1.14.0-2build1 ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 19:39:01 2024 InstallationDate: Installed on 2021-07-14 (1083 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: f2fs-tools UpgradeStatus: Upgraded to jammy on 2022-05-14 (779 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2021-03-24T15:58:15 ** Affects: f2fs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: - Ubuntu 22.04.4 LTS, f2fs-tools 1.14.0-2build1. - Terminal transcript of a simple reproduction: kuebi@twobuntu:/tmp$ truncate -s 512M testfs # create a (sparse) file to hold a test filesystem kuebi@twobuntu:/tmp$ mkfs.f2fs testfs - F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24) + F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24) Info: Disable heap-based policy Info: Debug level = 0 Info: Trim is enabled Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 1048576 (512 MB) Info: zone aligned segment0 blkaddr: 512 Info: format version with - "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" + "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" Info: [testfs] Discarding device Info: Overprovision ratio = 10.000% Info: Overprovision segments = 50 (GC reserved = 28) Info: format successful kuebi@twobuntu:/tmp$ truncate -s 1G testfs # grow the backing storage kuebi@twobuntu:/tmp$ resize.f2fs testfs # try to resize to fit Info: Segments per section = 1 Info: Sections per zone = 1 Info: sector size = 512 Info: total sectors = 2097152 (1024 MB) Info: MKFS version - "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May 7 09:00:52 UTC 2" + "Linux version 6.5.0-35-generic (buildd@lcy02-amd64-079) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
[Bug 2071445] Re: Ubuntu 24.04 for Azure unable to run 32bit binaries
** Also affects: linux-azure (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/2071445 Title: Ubuntu 24.04 for Azure unable to run 32bit binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2071445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054811] Re: Turned on comp, a lot notifications in KDE from chrome, notification left 1-2 px line stayed
Another new screenshot- still exists ** Attachment added: "Screenshot_20240616_175642.png" https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/2054811/+attachment/5793914/+files/Screenshot_20240616_175642.png ** Changed in: plasma-workspace (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/2054811 Title: Turned on comp, a lot notifications in KDE from chrome, notification left 1-2 px line stayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/2054811/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install 060
There are 51 dracut-install calls on my Raspberry Pi Zero 2W on Ubuntu 24.04: ``` dracut-install -m -P /hid-(a4tech|cypress|dr|elecom|gyration|icade|kensington|kye|lcpower|magicmouse|ntrig|petalynx|picolcd|pl|ps3remote|quanta|roccat-ko.*|roccat-pyra|saitek|sensor-hub|sony|speedlink|tivo|twinhan|uclogic|wacom|waltop|wiimote|zydacron|.*ff)\.ko =drivers/hid dracut-install -m =drivers/usb/host -P /(hwa-hc|sl811_cs|sl811-hcd|u132-hcd|whci-hcd)\.ko dracut-install -m -P /((cdc_mbim|ipheth|qmi_wwan|sierra_net|veth|xen-netback)\.ko|(isdn|net/ethernet|net/phy|net/team|uwb|wan|wireless)/) -s eth_type_trans|register_virtio_device|usbnet_open =drivers/net dracut-install -m -s ahci_platform_get_resources|ata_scsi_ioctl|scsi_add_host|blk_cleanup_queue|register_mtd_blktrans|scsi_esp_register|register_virtio_device|usb_stor_disconnect|mmc_add_host|sdhci_add_host|scsi_add_host_with_dma|blk_mq_alloc_disk|blk_mq_alloc_request|blk_mq_destroy_queue|blk_cleanup_disk|dw_mc_probe|dw_mci_pltfm_register|nvme_init_ctrl|iscsi_register_transport =drivers/scsi =drivers/ufs dracut-install -m -s ahci_platform_get_resources|ata_scsi_ioctl|scsi_add_host|blk_cleanup_queue|register_mtd_blktrans|scsi_esp_register|register_virtio_device|usb_stor_disconnect|mmc_add_host|sdhci_add_host|scsi_add_host_with_dma|blk_mq_alloc_disk|blk_mq_alloc_request|blk_mq_destroy_queue|blk_cleanup_disk|dw_mc_probe|dw_mci_pltfm_register|nvme_init_ctrl =drivers/block =drivers/nvme =drivers/dax vmd dracut-install -m -s nvdimm_bus_register =drivers/nvdimm =drivers/acpi dracut-install -m -s ahci_platform_get_resources|ata_scsi_ioctl|scsi_add_host|blk_cleanup_queue|register_mtd_blktrans|scsi_esp_register|register_virtio_device|usb_stor_disconnect|mmc_add_host|sdhci_add_host|scsi_add_host_with_dma|blk_mq_alloc_disk|blk_mq_alloc_request|blk_mq_destroy_queue|blk_cleanup_disk|dw_mc_probe|dw_mci_pltfm_register|nvme_init_ctrl =drivers/ata dracut-install -m btrfs ext2 ext3 ext4 f2fs isofs jfs reiserfs squashfs udf xfs nfs nfsv2 nfsv3 nfsv4 af_packet atkbd i8042 psmouse virtio_pci virtio_mmio vfat nls_cp437 nls_iso8859-1 ehci-hcd ehci-pci ehci-platform ohci-hcd ohci-pci uhci-hcd usbhid xhci-hcd xhci-pci xhci-plat-hcd =drivers/usb/typec =drivers/usb/c67x00 =drivers/usb/renesas_usbhs extcon-usb-gpio extcon-usbc-cros-ec =drivers/input/keyboard cros_ec_spi intel_lpss_pci spi_pxa2xx_platform surface_aggregator_registry =drivers/tty/serial =drivers/bus =drivers/i2c/muxes =drivers/pci/controller =drivers/pinctrl =drivers/clk =drivers/i2c/busses =drivers/gpio =drivers/mfd =drivers/nvmem =drivers/phy =drivers/power =drivers/regulator =drivers/reset =drivers/spi =drivers/spmi =drivers/soc =drivers/usb/chipidea =drivers/usb/dwc2 =drivers/usb/dwc3 =drivers/usb/isp1760 =drivers/usb/musb =drivers/usb/phy =drivers/rtc axp20x_usb_power =drivers/char/hw_random =drivers/net/ethernet =drivers/net/mdio =drivers/net/phy 8021q ipvlan =drivers/ide be2iscsi bnx2i cxgb3i cxgb4i qedi qla4xxx scsi_dh_alua scsi_dh_emc scsi_dh_rdac mptfc mptsas mptscsih mptspi zfcp scsi_transport_srp dax_pmem nd_pmem dasd_diag_mod dasd_eckd_mod dasd_fba_mod firewire-ohci firewire-sbp2 =drivers/mmc =drivers/usb/storage rockchipdrm pwm-cros-ec pwm_bl pwm-rockchip panel-simple analogix-anx6345 pwm-sun4i sun4i-drm sun8i-mixer panel-edp pwm_imx27 nwl-dsi ti-sn65dsi86 imx-dcss mux-mmio mxsfb imx8mq-interconnect hv_vmbus hv_utils hv_netvsc hv_mouse hv_storvsc hyperv-keyboard nx-compress nx-compress-crypto nx-compress-platform nx-compress-pseries nx-compress-powernv 842-decompress dracut-install -m crc32c vmd mlx5_ib mlx4_ib crc32c crc32 dracut-install -m dm_mod dracut-install -m dm_crypt dracut-install -m sm3-ce ghash-ce aes-ce-ccm sm4-ce-cipher aes-neon-blk sm4-ce aes-ce-cipher sha2-ce aes-arm64 chacha-neon aes-ce-blk sha256-arm64 sha512-ce aes-neon-bs sha512-arm64 sha3-ce poly1305-neon sha1-ce sm4-neon sm3-neon polyval-ce crct10dif-ce nhpoly1305-neon sm4-ce-gcm sm4-ce-ccm dracut-install -m blowfish_generic cts algif_hash algif_aead chacha_generic cmac chacha20poly1305 polyval-generic xcbc ansi_cprng blowfish_common ccm 842 xts ecdh_generic ecc gcm hctr2 lrw pkcs8_key_parser pkcs7_test_key xor des_generic authenc sm4_generic twofish_common fcrypt sm4 ecrdsa_generic pcbc tcrypt cast5_generic aria_generic af_alg lz4hc adiantum zstd poly1305_generic crypto_engine michael_mic crypto_null xctr algif_skcipher sm3_generic cast6_generic cast_common md4 curve25519-generic cryptd camellia_generic seqiv keywrap xxhash_generic streebog_generic aegis128 aes_ti authencesn nhpoly1305 serpent_generic async_tx async_xor async_raid6_recov async_pq async_memcpy geniv essiv crypto_user algif_rng echainiv rmd160 ghash-generic lz4 crc32_generic pcrypt twofish_generic sm2_generic vmac ecdsa_generic blake2b_generic sm3 wp512 dracut-install -m -s drm_privacy_screen_register =drivers/platform/x86 dracut-install -m efifb fbcon simplefb vesafb vga16fb =drivers/gpu/drm/tiny vboxvideo virtio-gpu dracut-install -
[Bug 2071471] Re: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads
Hi Niklas, thanks for the backgrounds. So to sum it up: The Ubuntu kernel config options for IOMMU_DEFAULT_DMA_LAZY and IOMMU_DEFAULT_DMA_STRICT haven't changed since jammy/22.04: 5.15.0-1.1 to 5.15.0-115.125 CONFIG_IOMMU_DEFAULT_DMA_STRICT=y # CONFIG_IOMMU_DEFAULT_DMA_LAZY is not set 6.8.0-6.6 to 6.8.0-38.38 CONFIG_IOMMU_DEFAULT_DMA_STRICT=y # CONFIG_IOMMU_DEFAULT_DMA_LAZY is not set But with the introduction of c76c067e488c s390/pci: Use dma-iommu layer which moves to a different dma-iommu implementation and 92bce97f0c34 s390/pci: Fix reset of IOMMU software counters (both available since 6.7(rc-1) the IOMMU_DEFAULT_DMA_LAZY kernel config option should be set to 'yes' by default for s390x. Does CONFIG_IOMMU_DEFAULT_DMA_STRICT need to be set to No on top? I don't think so - if lazy is 'yes'. So I believe we can go with 'IOMMU_DEFAULT_DMA_LAZY=y' for s390x only and should be good again. I assume that such situations happen not very often, so it would be ideal if IBM could give us a quick heads-up in such cases (where a kernel config default value for s390x is changed upstream), so that we can double check and potentially take over changes into the Ubuntu config by hand. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071471 Title: [UBUNTU 24.04] IOMMU DMA mode changed in kernel config causes massive throughput degradation for PCI-related network workloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2071471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen
Still no fix as of July 1, 2024. Have to boot manually with the 107 to get my Acer laptop up and running. Hope someone can fix this problem soon. Thanks for all the hard work on this issue. On Mon, Jul 1, 2024 at 8:10 AM Daniel <2068...@bugs.launchpad.net> wrote: > Did I understand correctly that this bug will be fixed after kernel > 5.15.0-113? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2068738 > > Title: > AMD GPUs fail with null pointer dereference when IOMMU enabled, > leading to black screen > > Status in linux package in Ubuntu: > Fix Released > Status in linux source package in Jammy: > Fix Committed > > Bug description: > BugLink: https://bugs.launchpad.net/bugs/2068738 > > [Impact] > > On systems with AMD Picasso/Raven 2 GPU devices, when the IOMMU is > enabled, the system fails to boot correctly, and all users see is a > black screen. > > This is caused by a null pointer dereference when enabling the IOMMU > after the device has been initialised. It should happen the other way > around. > > AMD-Vi: AMD IOMMUv2 loaded and initialized > ... > amdgpu: Topology: Add APU node [0x15d8:0x1002] > kfd kfd: amdgpu: added device 1002:15d8 > kfd kfd: amdgpu: Failed to resume IOMMU for device 1002:15d8 > ... > amdgpu :06:00.0: amdgpu: amdgpu_device_ip_init failed > amdgpu :06:00.0: amdgpu: Fatal error during GPU init > amdgpu :06:00.0: amdgpu: amdgpu: finishing device. > ... > BUG: kernel NULL pointer dereference, address: 013c > ... > CPU: 1 PID: 223 Comm: systemd-udevd Not tainted 5.15.0-112-generic > #122-Ubuntu > ... > RIP: 0010:amdgpu_dm_fini+0x149/0x1f0 [amdgpu] > ... > Call Trace: > >? srso_return_thunk+0x5/0x10 >? show_trace_log_lvl+0x28e/0x2ea >? show_trace_log_lvl+0x28e/0x2ea >? dm_hw_fini+0x23/0x30 [amdgpu] >? show_regs.part.0+0x23/0x29 >? __die_body.cold+0x8/0xd >? __die+0x2b/0x37 >? page_fault_oops+0x13b/0x170 >? srso_return_thunk+0x5/0x10 >? do_user_addr_fault+0x321/0x670 >? srso_return_thunk+0x5/0x10 >? __free_pages_ok+0x34a/0x4f0 >? exc_page_fault+0x77/0x170 >? asm_exc_page_fault+0x27/0x30 >? amdgpu_dm_fini+0x149/0x1f0 [amdgpu] >dm_hw_fini+0x23/0x30 [amdgpu] >amdgpu_device_ip_fini_early.isra.0+0x278/0x312 [amdgpu] >amdgpu_device_fini_hw+0x156/0x208 [amdgpu] >amdgpu_driver_unload_kms+0x69/0x90 [amdgpu] >amdgpu_driver_load_kms.cold+0x81/0x107 [amdgpu] >amdgpu_pci_probe+0x1d1/0x290 [amdgpu] >local_pci_probe+0x4b/0x90 >? srso_return_thunk+0x5/0x10 >pci_device_probe+0x119/0x200 >really_probe+0x222/0x420 >__driver_probe_device+0xe8/0x140 >driver_probe_device+0x23/0xc0 >__driver_attach+0xf7/0x1f0 >? __device_attach_driver+0x140/0x140 >bus_for_each_dev+0x7f/0xd0 >driver_attach+0x1e/0x30 >bus_add_driver+0x148/0x220 >? srso_return_thunk+0x5/0x10 >driver_register+0x95/0x100 >__pci_register_driver+0x68/0x70 >amdgpu_init+0x7c/0x1000 [amdgpu] >? 0xc0e0b000 >do_one_initcall+0x49/0x1e0 >? srso_return_thunk+0x5/0x10 >? kmem_cache_alloc_trace+0x19e/0x2e0 >do_init_module+0x52/0x260 >load_module+0xb45/0xbe0 >__do_sys_finit_module+0xbf/0x120 >__x64_sys_finit_module+0x18/0x20 >x64_sys_call+0x1ac3/0x1fa0 >do_syscall_64+0x56/0xb0 > ... >entry_SYSCALL_64_after_hwframe+0x67/0xd1 > > A workaround does exist. Users can set "nomodeset" or "amd_iommu=off" > to GRUB_CMDLINE_LINUX_DEFAULT, update-grub and reboot. > > [Fix] > > The regression was caused by the following commit that landed in > 5.15.0-112-generic, and 5.15.150 upstream: > > commit 3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd ubuntu-jammy > Author: Yifan Zhang > Date: Tue Sep 28 15:42:35 2021 +0800 > Subject: drm/amdgpu: init iommu after amdkfd device init > Link: > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=3c7e53c0d4b43ffe6e7715414b5f2b3177881ecd > > The fix is to revert this patch, as it was not suppose to be > backported to 5.15 stable. > > The mailing list discussion with AMD developers is: > > https://lore.kernel.org/amd-gfx/20240523173031.4212-1-w_ar...@gmx.de/ > > The fix hasn't been acknowledged by Greg KH or Sasha Levin yet, so > sending as a Ubuntu SAUCE patch. If the upstream status changes, we > can NAK and resend. > > [Testcase] > > You need a system with an AMD Picasso/Raven 2 device. It will likely > be an APU, and not a discrete graphics card, but any AMD Picasso/Raven > 2 device is affected. > > Install the kernel and boot. Make sure full modesetting is enabled. > > There is a test kernel available in the ppa below: > > https://launchpad.net/~mruffell/+archive/ubuntu/lp2068738-test > > If you install the test kernel, your system should boot successfully. > > [Where problems could occur] > >
[Bug 2065180] Re: performance regression in dracut-install 060
There is another performance improvement upstream: https://github.com/dracut-ng/dracut-ng/pull/408 I tested this change a Raspberry Pi Zero 2W, but it had no measurable performance improvement: ``` $ sudo hyperfine --warmup 1 -r 10 "update-initramfs -u" Benchmark 1: update-initramfs -u Time (mean ± σ): 249.595 s ± 7.243 s[User: 66.584 s, System: 170.342 s] Range (min … max): 240.879 s … 260.506 s10 runs ``` Dave, can you test dracut 060+5-1ubuntu3.2~ppa1 from https://launchpad.net/~bdrung/+archive/ubuntu/ppa to see if that would improve the situation on the other Pis? Viraniac, could you test that version on your VIM4? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065180 Title: performance regression in dracut-install 060 To manage notifications about this bug go to: https://bugs.launchpad.net/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726548] Re: Windows resized after resume
Maybe mine is completely different, since its the whole screen resolution that changes. In my case its msm as driver (Adreno 690), where dp link issues are aready confirmed and it's worked on. Still, I have the hpd pin disabled, and it mitigates the behaviour. There are some other odd issues. If I extend the screen resolution to 4k@60, the longer suspend / resume will deliver a blue screen (how fitting), unrecoverable. If I set the resolution to 2k (2560x1440@60) it will resume without lots of fuss. Sometimes the Display Power off is not permanent, but screen doesn't come up completely (only backlight is on). This is the same on XOrg and Wayland, but reducing resolution appears to mitigate the issue. For me it looks like some race condition that interrupts dpu / dp setup and operation, but its hard to debug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726548 Title: Windows resized after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1726548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067900] Re: apparmor unconfined profile blocks pivot_root
It looks like the same issue happens with "kill" syscall: Jul 01 15:52:45 kernel: audit: type=1400 audit(1719849165.951:291): apparmor="DENIED" operation="signal" class="signal" profile="lxd-v1_" pid=15369 comm="lxd" requested_mask="receive" denied_mask="receive" signal=kill peer="snap.lxd.daemon" this started to appear after LXD was enabled to use unconfined profile mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067900 Title: apparmor unconfined profile blocks pivot_root To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2067900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065180] Re: performance regression in dracut-install 060
** Also affects: open-iscsi (Ubuntu) Importance: Undecided Status: New ** Changed in: open-iscsi (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/2065180 Title: performance regression in dracut-install 060 To manage notifications about this bug go to: https://bugs.launchpad.net/dracut/+bug/2065180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054222] Re: virtiofsd is no longer installed by default in 24.04 when virt-manager/qemu is installed.
I do not have rust-virtiofsd package, in fact it does not seem to be available in the repos though rust-virtiofsd-dev is available. Sharing of folders works well on my Xubuntu-24.04 systems simply by installing the virtiofsd package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054222 Title: virtiofsd is no longer installed by default in 24.04 when virt- manager/qemu is installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rust-virtiofsd/+bug/2054222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071486] Re: intel-vsc-dkms FTBS on jammy with the latest 6.8 hwe kernel
Please amend the Test Plan to make it clear that testing both the GA and HWE kernels is required. I expect to see this in the Test Plan for every HWE backport fix (and if it's not required then an explanation as to why). I understand that I could just do this myself but it feels like every time I look at an HWE backport fix this isn't in the Test Plan, so I'm pushing back now to get this done properly from the beginning. That way there will be less effort for everyone at a time that the SRU queues are quite large and efficiency matters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071486 Title: intel-vsc-dkms FTBS on jammy with the latest 6.8 hwe kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ivsc-driver/+bug/2071486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071651] [NEW] Upgrade to 22.04 LTS fails
Public bug reported: I am unable to upgrade from Ubuntu 22.04.4 LTS" to 24.04LTS. It gives me error message about possible PPA being installed but I dont see any in the update center. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13 Uname: Linux 6.5.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 12:56:42 2024 InstallationDate: Installed on 2023-05-02 (426 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-07-01 (0 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-05-02T07:51:31.819172 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071651 Title: Upgrade to 22.04 LTS fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2071651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070096] Re: [amdgpu] Graphics driver issue: Display goes black for a second at random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c
Here's at least part of the problem.
commit 15c983d0cbb5a158eafb9cb88e6d8dfc4477d9c2
Author: Melissa Wen
Date: Fri Dec 29 15:25:00 2023 -0100
drm/amd/display: fix bandwidth validation failure on DCN 2.1
BugLink: https://bugs.launchpad.net/bugs/2059068
commit 3a0fa3bc245ef92838a8296e0055569b8dff94c4 upstream.
IGT `amdgpu/amd_color/crtc-lut-accuracy` fails right at the beginning of
the test execution, during atomic check, because DC rejects the
bandwidth state for a fb sizing 64x64. The test was previously working
with the deprecated dc_commit_state(). Now using
dc_validate_with_context() approach, the atomic check needs to perform a
full state validation. Therefore, set fast_validation to false in the
dc_validate_global_state call for atomic check.
Cc: sta...@vger.kernel.org
Fixes: b8272241ff9d ("drm/amd/display: Drop dc_commit_state in favor of
dc_commit_streams")
Signed-off-by: Melissa Wen
Signed-off-by: Hamza Mahfooz
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Portia Stephens
Signed-off-by: Stefan Bader
That commit was reverted upstream.
https://github.com/torvalds/linux/commit/c2ab9ce0ee7225fc05f58a6671c43b8a3684f530
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070096
Title:
[amdgpu] Graphics driver issue: Display goes black for a second at
random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR*
link_enc_cfg_validate: Invalid link encoder assignments - 0x1c
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2070096/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071644] Re: sometimes takes ~5 seconds to _dma_fmt_to_dma_drm_fmts: assertion 'fmt != GST_VIDEO_FORMAT_UNKNOWN' failed
can reproduce this without opencv using: gst-launch-1.0 v4l2src device="/dev/video2" ! videoconvert ! ximagesink ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: opencv (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071644 Title: sometimes takes ~5 seconds to _dma_fmt_to_dma_drm_fmts: assertion 'fmt != GST_VIDEO_FORMAT_UNKNOWN' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2071644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071654] [NEW] PR for: "PCI: Clear Secondary Status errors after enumeration"
Public bug reported: We enumerate devices by attempting config reads to the Vendor ID of each possible device. On conventional PCI, if no device responds, the read terminates with a Master Abort (PCI r3.0, sec 6.1). On PCIe, the config read is terminated as an Unsupported Request (PCIe r6.0, sec 2.3.2, 7.5.1.3.7). In either case, if the read addressed a device below a bridge, it is logged by setting "Received Master Abort" in the bridge Secondary Status register. Clear any errors logged in the Secondary Status register after enumeration. ** Affects: linux-nvidia (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/2071654 Title: PR for: "PCI: Clear Secondary Status errors after enumeration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2071654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070409] Re: please update openjdk-21 to 21.0.4+5 early access
** Changed in: openjdk-21 (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/2070409 Title: please update openjdk-21 to 21.0.4+5 early access To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-21/+bug/2070409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071204] Re: openjdk fails to build due to dpkg changes
** Summary changed: - openjdk-22 fails to build due to dpkg changes + openjdk fails to build due to dpkg changes ** Also affects: openjdk-21 (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/openjdk-21/+git/openjdk-21/+merge/468540 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071204 Title: openjdk fails to build due to dpkg changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-21/+bug/2071204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071655] [NEW] PR for: "IB/mlx5: Use __iowrite64_copy() for write combining stores"
Public bug reported: mlx5 has a built in self-test at driver startup to evaluate if the platform supports write combining to generate a 64 byte PCIe TLP or not. This has proven necessary because a lot of common scenarios end up with broken write combining (especially inside virtual machines) and there is other way to learn this information. This self test has been consistently failing on new ARM64 CPU designs (specifically with NVIDIA Grace's implementation of Neoverse V2). The C loop around writeq() generates some pretty terrible ARM64 assembly, but historically this has worked on a lot of existing ARM64 CPUs till now. We see it succeed about 1 time in 10,000 on the worst effected systems. The CPU architects speculate that the load instructions interspersed with the stores makes the WC buffers statistically flush too often and thus the generation of large TLPs becomes infrequent. This makes the boot up test unreliable in that it indicates no write-combining, however userspace would be fine since it uses a ST4 instruction. Further, S390 has similar issues where only the special zpci_memcpy_toio() will actually generate large TLPs, and the open coded loop does not trigger it at all. Fix both ARM64 and S390 by switching to __iowrite64_copy() which now provides architecture specific variants that have a high change of generating a large TLP with write combining. x86 continues to use a similar writeq loop in the generate __iowrite64_copy(). ** Affects: linux-nvidia (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/2071655 Title: PR for: "IB/mlx5: Use __iowrite64_copy() for write combining stores" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2071655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039368] Re: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
** Description changed: [Impact] Currently there are UBSAN warnings that show up when running bcache on jammy HWE, Mantic and noble. For now no side effects have been observed but such an issue could potentially cause a crash or corrupt data. [Fix] There is currently a fix upstream provided by the following patch: * 3a861560ccb3 "bcache: fix variable length array abuse in btree_iter" [Test Case] - Setup bcache on a jammy HWE kernel or mantic or noble machine. - This can be done following the steps in this wiki: https://wiki.ubuntu.com/ServerTeam/Bcache + This can be done following the steps in this wiki: https://wiki.ubuntu.com/ServerTeam/Bcache - Restart the machine - - After restarting the machine UBSAN warnings and call traces can be seen in dmesg. + - After restarting the machine, the following UBSAN warnings and call traces can be seen in dmesg: + + [3.824281] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-QmAt2N/linux-hwe-6.5-6.5.0/drivers/md/bcache/bset.c:1098:3 + [3.826338] index 4 is out of range for type 'btree_iter_set [4]' + [3.826812] CPU: 13 PID: 184 Comm: kworker/13:1 Not tainted 6.5.0-41-generic #41~22.04.2-Ubuntu + [3.827817] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 + [3.828835] Workqueue: events register_cache_worker [bcache] + [3.829429] Call Trace: + [3.830626] + [3.831638] dump_stack_lvl+0x48/0x70 + [3.832227] dump_stack+0x10/0x20 + [3.832785] __ubsan_handle_out_of_bounds+0xc6/0x110 + [3.833357] bch_btree_iter_push+0x4e6/0x4f0 [bcache] + [3.834052] bch_btree_node_read_done+0xfc/0x450 [bcache] + [3.834653] ? mempool_kfree+0xe/0x20 + [3.835211] bch_btree_node_read+0xf8/0x1e0 [bcache] + [3.835832] ? __pfx_closure_sync_fn+0x10/0x10 [bcache] + [3.836474] bch_btree_node_get.part.0+0x160/0x340 [bcache] + [3.837161] ? __bch_btree_ptr_invalid+0x60/0xd0 [bcache] + [3.837838] ? __pfx_up_write+0x10/0x10 + [3.838739] bch_btree_node_get+0x16/0x30 [bcache] + [3.839506] run_cache_set+0x596/0x840 [bcache] + [3.840197] register_cache_set+0x1a2/0x210 [bcache] + [3.840748] register_cache+0x11a/0x1a0 [bcache] + [3.841303] register_cache_worker+0x22/0x80 [bcache] + [3.841840] process_one_work+0x23d/0x450 + [3.842297] worker_thread+0x50/0x3f0 + [3.842698] ? __pfx_worker_thread+0x10/0x10 + [3.843081] kthread+0xef/0x120 + [3.843521] ? __pfx_kthread+0x10/0x10 + [3.843892] ret_from_fork+0x44/0x70 + [3.844264] ? __pfx_kthread+0x10/0x10 + [3.844611] ret_from_fork_asm+0x1b/0x30 + [3.844949] + + [4.029242] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-QmAt2N/linux-hwe-6.5-6.5.0/drivers/md/bcache/bset.c:1207:3 + [4.030496] index 14 is out of range for type 'btree_iter_set [4]' + [4.030930] CPU: 13 PID: 184 Comm: kworker/13:1 Not tainted 6.5.0-41-generic #41~22.04.2-Ubuntu + [4.031841] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 + [4.032650] Workqueue: events register_cache_worker [bcache] + [4.033149] Call Trace: + [4.033549] + [4.033972] dump_stack_lvl+0x48/0x70 + [4.034418] dump_stack+0x10/0x20 + [4.034839] __ubsan_handle_out_of_bounds+0xc6/0x110 + [4.035279] btree_mergesort+0x4d4/0x520 [bcache] + [4.035730] ? __pfx_bch_ptr_invalid+0x10/0x10 [bcache] + [4.036191] ? __pfx_bch_extent_sort_cmp+0x10/0x10 [bcache] + [4.036691] __btree_sort+0x96/0x2d0 [bcache] + [4.037182] bch_btree_sort_and_fix_extents+0x1d/0x40 [bcache] + [4.037674] bch_btree_node_read_done+0x34d/0x450 [bcache] + [4.038172] ? mempool_kfree+0xe/0x20 + [4.038617] bch_btree_node_read+0xf8/0x1e0 [bcache] + [4.039120] ? __pfx_closure_sync_fn+0x10/0x10 [bcache] + [4.039659] bch_btree_node_get.part.0+0x160/0x340 [bcache] + [4.040220] ? __bch_btree_ptr_invalid+0x60/0xd0 [bcache] + [4.040806] ? __pfx_up_write+0x10/0x10 + [4.041371] bch_btree_node_get+0x16/0x30 [bcache] + [4.041921] run_cache_set+0x596/0x840 [bcache] + [4.042497] register_cache_set+0x1a2/0x210 [bcache] + [4.043089] register_cache+0x11a/0x1a0 [bcache] + [4.043715] register_cache_worker+0x22/0x80 [bcache] + [4.044348] process_one_work+0x23d/0x450 + [4.044887] worker_thread+0x50/0x3f0 + [4.045422] ? __pfx_worker_thread+0x10/0x10 + [4.045936] kthread+0xef/0x120 + [4.046445] ? __pfx_kthread+0x10/0x10 + [4.046942] ret_from_fork+0x44/0x70 + [4.047423] ? __pfx_kthread+0x10/0x10 + [4.047878] ret_from_fork_asm+0x1b/0x30 + [4.048339] + + [4.227653] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-QmAt2N/linux-hwe-6.5-6.5.0/drivers/md/bcache/extents.c:281:4 + [4.228847] index 4 is out of range for type 'btree_iter_set [4]' + [4.229472] CPU: 13 PID: 184 Comm: kworker/13:1 Not tainted 6.5.0-4
[Bug 2070096] Re: [amdgpu] Graphics driver issue: Display goes black for a second at random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c
And that commit did go back to stable: https://git.kernel.org/stable/c/6266b3a312b7f69c883c2d7c82d85772464421d2 So I guess Canonical team missed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070096 Title: [amdgpu] Graphics driver issue: Display goes black for a second at random: [drm:link_enc_cfg_validate [amdgpu]] *ERROR* link_enc_cfg_validate: Invalid link encoder assignments - 0x1c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2070096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070020] Re: Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
I don't know if it's the same issue; but there is another relatively
similar issue that occurred very recently: bug #2070096
As I mentioned there, this commit is at least PART of the problem:
commit 15c983d0cbb5a158eafb9cb88e6d8dfc4477d9c2
Author: Melissa Wen
Date: Fri Dec 29 15:25:00 2023 -0100
drm/amd/display: fix bandwidth validation failure on DCN 2.1
BugLink: https://bugs.launchpad.net/bugs/2059068
commit 3a0fa3bc245ef92838a8296e0055569b8dff94c4 upstream.
IGT `amdgpu/amd_color/crtc-lut-accuracy` fails right at the beginning of
the test execution, during atomic check, because DC rejects the
bandwidth state for a fb sizing 64x64. The test was previously working
with the deprecated dc_commit_state(). Now using
dc_validate_with_context() approach, the atomic check needs to perform a
full state validation. Therefore, set fast_validation to false in the
dc_validate_global_state call for atomic check.
Cc: sta...@vger.kernel.org
Fixes: b8272241ff9d ("drm/amd/display: Drop dc_commit_state in favor of
dc_commit_streams")
Signed-off-by: Melissa Wen
Signed-off-by: Hamza Mahfooz
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Portia Stephens
Signed-off-by: Stefan Bader
That commit was reverted upstream:
https://git.kernel.org/torvalds/c//c2ab9ce0ee7225fc05f58a6671c43b8a3684f530
And that commit did go back to stable:
https://git.kernel.org/stable/c/6266b3a312b7f69c883c2d7c82d85772464421d2
So I guess Canonical team missed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070020
Title:
Lenovo dock no longer working after upgrade from 6.5.0-35 to 6.5.0-41
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070020/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069357] Re: Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo Thunderbolt 3 Gen 2 USB-C dock
Canonical 6.5 series seems to have picked up at least one bad commit
that was reverted upstream.
commit 15c983d0cbb5a158eafb9cb88e6d8dfc4477d9c2
Author: Melissa Wen
Date: Fri Dec 29 15:25:00 2023 -0100
drm/amd/display: fix bandwidth validation failure on DCN 2.1
BugLink: https://bugs.launchpad.net/bugs/2059068
commit 3a0fa3bc245ef92838a8296e0055569b8dff94c4 upstream.
IGT `amdgpu/amd_color/crtc-lut-accuracy` fails right at the beginning of
the test execution, during atomic check, because DC rejects the
bandwidth state for a fb sizing 64x64. The test was previously working
with the deprecated dc_commit_state(). Now using
dc_validate_with_context() approach, the atomic check needs to perform a
full state validation. Therefore, set fast_validation to false in the
dc_validate_global_state call for atomic check.
Cc: sta...@vger.kernel.org
Fixes: b8272241ff9d ("drm/amd/display: Drop dc_commit_state in favor of
dc_commit_streams")
Signed-off-by: Melissa Wen
Signed-off-by: Hamza Mahfooz
Signed-off-by: Alex Deucher
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Portia Stephens
Signed-off-by: Stefan Bader
Mainline revert:
https://git.kernel.org/torvalds/c/c2ab9ce0ee7225fc05f58a6671c43b8a3684f530
Stable revert:
https://git.kernel.org/stable/c/6266b3a312b7f69c883c2d7c82d85772464421d2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069357
Title:
Multimonitor support broken on kernel 6.5.0-1024.25_oem on Lenovo
Thunderbolt 3 Gen 2 USB-C dock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2069357/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049206] Re: DeprecationWarning using nohang commandline options
This bug was fixed in the package nohang - 0.2.0-2 --- nohang (0.2.0-2) unstable; urgency=medium * Ack NMU. * Bump standards version to 4.7.0. * Apply upstream fix for DeprecationWarning. (LP: #2049206) * d/rules: fix path. (Closes: #1073732) -- Alex Myczko Mon, 01 Jul 2024 09:12:42 + ** Changed in: nohang (Ubuntu) Status: In Progress => 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/2049206 Title: DeprecationWarning using nohang commandline options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nohang/+bug/2049206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071657] [NEW] nvidia-kernel-source-550 550.90.07-0ubuntu0.22.04.1: nvidia kernel module failed to build
Public bug reported: cannot inatall nvidia driver ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-kernel-source-550 550.90.07-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13 Uname: Linux 6.5.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: fail DKMSKernelVersion: 6.5.0-41-generic Date: Tue Jul 2 02:17:21 2024 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-550:550.90.07-0ubuntu0.22.04.1:cc: error: unrecognized command-line option ‘-ftrivial-auto-var-init=zero’ InstallationDate: Installed on 2024-05-18 (44 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) PackageVersion: 550.90.07-0ubuntu0.22.04.1 Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: nvidia-graphics-drivers-550 Title: nvidia-kernel-source-550 550.90.07-0ubuntu0.22.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071657 Title: nvidia-kernel-source-550 550.90.07-0ubuntu0.22.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2071657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071657] Re: nvidia-kernel-source-550 550.90.07-0ubuntu0.22.04.1: nvidia kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071657 Title: nvidia-kernel-source-550 550.90.07-0ubuntu0.22.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2071657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2039368] Re: UBSAN: array-index-out-of-bounds in /build/linux-D15vQj/linux-6.5.0/drivers/md/bcache/bset.c:1098:3
** Description changed: [Impact] Currently there are UBSAN warnings that show up when running bcache on jammy HWE, Mantic and noble. For now no side effects have been observed but such an issue could potentially cause a crash or corrupt data. [Fix] There is currently a fix upstream provided by the following patch: * 3a861560ccb3 "bcache: fix variable length array abuse in btree_iter" [Test Case] 1. Setup bcache on a jammy HWE kernel or mantic or noble machine. This can be done following the steps in this wiki: https://wiki.ubuntu.com/ServerTeam/Bcache 2. Restart the machine 3. After restarting the machine, the following UBSAN warnings and call traces can be seen in dmesg: [3.824281] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-QmAt2N/linux-hwe-6.5-6.5.0/drivers/md/bcache/bset.c:1098:3 [3.826338] index 4 is out of range for type 'btree_iter_set [4]' [3.826812] CPU: 13 PID: 184 Comm: kworker/13:1 Not tainted 6.5.0-41-generic #41~22.04.2-Ubuntu [3.827817] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [3.828835] Workqueue: events register_cache_worker [bcache] [3.829429] Call Trace: [3.830626] [3.831638] dump_stack_lvl+0x48/0x70 [3.832227] dump_stack+0x10/0x20 [3.832785] __ubsan_handle_out_of_bounds+0xc6/0x110 [3.833357] bch_btree_iter_push+0x4e6/0x4f0 [bcache] [3.834052] bch_btree_node_read_done+0xfc/0x450 [bcache] [3.834653] ? mempool_kfree+0xe/0x20 [3.835211] bch_btree_node_read+0xf8/0x1e0 [bcache] [3.835832] ? __pfx_closure_sync_fn+0x10/0x10 [bcache] [3.836474] bch_btree_node_get.part.0+0x160/0x340 [bcache] [3.837161] ? __bch_btree_ptr_invalid+0x60/0xd0 [bcache] [3.837838] ? __pfx_up_write+0x10/0x10 [3.838739] bch_btree_node_get+0x16/0x30 [bcache] - [3.839506] run_cache_set+0x596/0x840 [bcache] - [3.840197] register_cache_set+0x1a2/0x210 [bcache] - [3.840748] register_cache+0x11a/0x1a0 [bcache] - [3.841303] register_cache_worker+0x22/0x80 [bcache] - [3.841840] process_one_work+0x23d/0x450 - [3.842297] worker_thread+0x50/0x3f0 - [3.842698] ? __pfx_worker_thread+0x10/0x10 - [3.843081] kthread+0xef/0x120 - [3.843521] ? __pfx_kthread+0x10/0x10 - [3.843892] ret_from_fork+0x44/0x70 - [3.844264] ? __pfx_kthread+0x10/0x10 - [3.844611] ret_from_fork_asm+0x1b/0x30 [3.844949] [4.029242] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-QmAt2N/linux-hwe-6.5-6.5.0/drivers/md/bcache/bset.c:1207:3 [4.030496] index 14 is out of range for type 'btree_iter_set [4]' [4.030930] CPU: 13 PID: 184 Comm: kworker/13:1 Not tainted 6.5.0-41-generic #41~22.04.2-Ubuntu [4.031841] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [4.032650] Workqueue: events register_cache_worker [bcache] [4.033149] Call Trace: [4.033549] [4.033972] dump_stack_lvl+0x48/0x70 [4.034418] dump_stack+0x10/0x20 [4.034839] __ubsan_handle_out_of_bounds+0xc6/0x110 [4.035279] btree_mergesort+0x4d4/0x520 [bcache] [4.035730] ? __pfx_bch_ptr_invalid+0x10/0x10 [bcache] [4.036191] ? __pfx_bch_extent_sort_cmp+0x10/0x10 [bcache] [4.036691] __btree_sort+0x96/0x2d0 [bcache] [4.037182] bch_btree_sort_and_fix_extents+0x1d/0x40 [bcache] [4.037674] bch_btree_node_read_done+0x34d/0x450 [bcache] [4.038172] ? mempool_kfree+0xe/0x20 [4.038617] bch_btree_node_read+0xf8/0x1e0 [bcache] [4.039120] ? __pfx_closure_sync_fn+0x10/0x10 [bcache] [4.039659] bch_btree_node_get.part.0+0x160/0x340 [bcache] [4.040220] ? __bch_btree_ptr_invalid+0x60/0xd0 [bcache] [4.040806] ? __pfx_up_write+0x10/0x10 [4.041371] bch_btree_node_get+0x16/0x30 [bcache] - [4.041921] run_cache_set+0x596/0x840 [bcache] - [4.042497] register_cache_set+0x1a2/0x210 [bcache] - [4.043089] register_cache+0x11a/0x1a0 [bcache] - [4.043715] register_cache_worker+0x22/0x80 [bcache] - [4.044348] process_one_work+0x23d/0x450 - [4.044887] worker_thread+0x50/0x3f0 - [4.045422] ? __pfx_worker_thread+0x10/0x10 - [4.045936] kthread+0xef/0x120 - [4.046445] ? __pfx_kthread+0x10/0x10 - [4.046942] ret_from_fork+0x44/0x70 - [4.047423] ? __pfx_kthread+0x10/0x10 - [4.047878] ret_from_fork_asm+0x1b/0x30 [4.048339] [4.227653] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-QmAt2N/linux-hwe-6.5-6.5.0/drivers/md/bcache/extents.c:281:4 [4.228847] index 4 is out of range for type 'btree_iter_set [4]' [4.229472] CPU: 13 PID: 184 Comm: kworker/13:1 Not tainted 6.5.0-41-generic #41~22.04.2-Ubuntu [4.230680] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [4.231954] Workqueue: events register_cac
[Bug 2067900] Re: apparmor unconfined profile blocks pivot_root
This issue is now occuring in lxd latest/edge builds after we merged initial support for restricted user namespaces. Is there an eta on a fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067900 Title: apparmor unconfined profile blocks pivot_root To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2067900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068944] Re: ubuntu-advantage-desktop-daemon (pro client in general) may expose the pro token to other users
** Changed in: ubuntu-advantage-tools (Ubuntu) Assignee: Sebastien Bacher (seb128) => (unassigned) ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Fix Committed => Invalid ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Invalid => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068944 Title: ubuntu-advantage-desktop-daemon (pro client in general) may expose the pro token to other users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/2068944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071547] Re: [SRU] gnome-activity-journal fails to run
** Summary changed: - gnome-activity-journal fails to run + [SRU] gnome-activity-journal fails to run ** Description changed: + [ Impact ] + + gnome-activity-journal fails to run and crashes immediately with the + error (even though python3-zeitgeist is aleady installed): + + $ gnome-activity-journal + ERROR: No module named 'imp'. + The 'zeitgeist' python3 module was not found. Please install 'python3-zeitgeist' package. + + + [ Test Plan ] + + install gnome-activity-journal. + + Execute "gnome-activity-journal" + + If the package is not fixed, it will fail with the above error. + + With the fixed package, it will display the interface. + + [ Where problems could occur ] + + The 'imp' module is not available in Python3.12. 'imp' was used previously to find and load the module. Now, its being replaced with 'importlib' to load the module. + In the worst case, if 'importlib' fails to load the module then the user will not see any new regression, but will see the same problem as this bug. + + [ Other Info ] + + It has been fixed in Debian and has synced with Oracular. + + [ Original Bug Description ] + gnome-activity-journal fails to run and crashed immediately. - $ gnome-activity-journal + $ gnome-activity-journal ERROR: No module named 'imp'. The 'zeitgeist' python3 module was not found. Please install 'python3-zeitgeist' package. See the README.md file for more information. python3-zeitgeist is aleady installed. $ apt-cache policy python3-zeitgeist python3-zeitgeist: - Installed: 1.0.4-5ubuntu5 - Candidate: 1.0.4-5ubuntu5 - Version table: - *** 1.0.4-5ubuntu5 500 - 500 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.0.4-5ubuntu5 + Candidate: 1.0.4-5ubuntu5 + Version table: + *** 1.0.4-5ubuntu5 500 + 500 http://gb.archive.ubuntu.com/ubuntu noble/universe amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071547 Title: [SRU] gnome-activity-journal fails to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-activity-journal/+bug/2071547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1982483]
Are there any updates regarding this issue? I’m still experiencing no sound from the speakers on Manjaro with kernel 6.9.5-1. The sound from headphones works, but only if I first boot into Windows 11. However, this only lasts for one session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1982483 Title: No sound from built-in speakers HP Pavilion All-in-One Desktop 27-ca1xxx (ALC274) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1982483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069170] Re: [SRU] gnome-activity-journal instantly fails
** Summary changed: - gnome-activity-journal instantly fails + [SRU] gnome-activity-journal instantly fails ** Description changed: - $ gnome-activity-journal + [ Impact ] + + gnome-activity-journal fails to run and crashes immediately with the + error: + + $ gnome-activity-journal Using the "zeitgeist" python module from /usr/lib/python3/dist-packages/zeitgeist Traceback (most recent call last): File "/bin/gnome-activity-journal", line 119, in from src import config + ModuleNotFoundError: No module named 'src' + + [ Test Plan ] + + install gnome-activity-journal. + + Open a terminal and try to execute "/bin/gnome-activity-journal". + + If the package is not fixed, it will fail with the above error. + + With the fixed package, it will display the interface. + + As a sanity check: + 1. Open gnome-activity-journal from the menu. + 2. From a terminal execute "gnome-activity-journal" + 3. From a terminal execute "/usr/bin/gnome-activity-journal". + + In all the cases gnome-activity-journal should start wthout any crash. + + [ Where problems could occur ] + + If 'gnome-activity-journal' was started as '/bin/gnome-activity-journal' then it tries to find its internal module at '/share' folder but '/share' does not exist. The current fix modifes the path and prefixes 'usr' to the path. + Users should not see any new regression to this change, but if the users have copied 'gnome-activity-journal' to some other folder and tries to start from there then the user will face the same problem as this bug and might think that the bug has not been fixed. + + [ Other Info ] + + It has been fixed in Debian and has synced with Oracular. + + [ Original Bug Description ] + + $ gnome-activity-journal + Using the "zeitgeist" python module from /usr/lib/python3/dist-packages/zeitgeist + Traceback (most recent call last): + File "/bin/gnome-activity-journal", line 119, in + from src import config ModuleNotFoundError: No module named 'src' I have zeitgeist installed and zeitgeist-daemon is running. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-activity-journal 1.0.0-3build1 ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Wed Jun 12 17:25:26 2024 PackageArchitecture: all SourcePackage: gnome-activity-journal UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-08-06T11:56:22.315382 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069170 Title: [SRU] gnome-activity-journal instantly fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-activity-journal/+bug/2069170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945701] Re: [MIR] oem-somerville-mankey-meta
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945701 Title: [MIR] oem-somerville-mankey-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966177] Re: [MIR] oem-somerville-kakuna-adl-meta
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966177 Title: [MIR] oem-somerville-kakuna-adl-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953583] Re: [MIR] oem-somerville-minccino-meta
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953583 Title: [MIR] oem-somerville-minccino-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1953583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931686] Re: [MIR] oem-somerville-delibird-meta
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931686 Title: [MIR] oem-somerville-delibird-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945702] Re: [MIR] oem-somerville-olly-adl-meta
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945702 Title: [MIR] oem-somerville-olly-adl-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957162] Re: [MIR] oem-somerville-pansage-meta
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957162 Title: [MIR] oem-somerville-pansage-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934463] Re: [MIR] oem-somerville-onix-adl-meta
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934463 Title: [MIR] oem-somerville-onix-adl-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1934463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896206] Re: [MIR] oem-somerville-targaryen-meta
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896206 Title: [MIR] oem-somerville-targaryen-meta To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
