[Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.8 (Ubuntu Oracular) Status: New => Invalid ** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072679 Title: Regression: unable to reach low idle states on Tiger Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079936] Re: PCI/internal sound card not detected
please upgrade the package firmware-sof-signed to the latest version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079936 Title: PCI/internal sound card not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2079936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077690] Re: alsa: Headphone and Speaker couldn't output sound intermittently
@Qian Fu, For jammy, the 2 patches could be cleanly applied to 5.15 kernel, hence the community will cherry-pick these 2 commits into stable-5.15.y, and canonical will merge these 2 commits into jammy kernel with stable SRU cycle automatically. In summary, the 2 patches will be merged to jammy kernel sooner or later. And for jammy, users could also update the kernel to 6.8-hwe, 6.8-hwe kernel has these 2 commits. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077690 Title: alsa: Headphone and Speaker couldn't output sound intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077690] Re: alsa: Headphone and Speaker couldn't output sound intermittently
The patches are already in the Oracular kernel, set it to fix_released. ** Changed in: linux (Ubuntu Oracular) 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/2077690 Title: alsa: Headphone and Speaker couldn't output sound intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076151] Re: [SRU] Support new hardware system in mediatek_scalar plugin
5.1.d is acceptable, the production version for mediatek graphic controller will be managed to lower than 10. And a later fwupd version will include this fix: https://github.com/fwupd/fwupd/commit/e1cd72494b359d52d64baef62d9c334127488e73 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076151 Title: [SRU] Support new hardware system in mediatek_scalar plugin To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2076151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077690] Re: alsa: Headphone and Speaker couldn't output sound intermittently
** Description changed: - This bug is for tracking purpose. + The patches are in the linux-next already, it will be in the unstable + kernel automatically, and the patches will be in stable sooner or + later, so it will be in the Jammy kernel automatically in the future. + + And our oem project requires the patches to be in the hwe-6.8 ASAP, + Here I submit the SRU to Noble and Oracular. + + [Impact] + On a Dell machine, we plug a speaker or headset into the front audio + port, play sound to the speaker or headset, we get a 1/6 chance that + the speaker or headset couldn't output sound. + + + [Fix] + pick 2 commits from linux-next + + [Test] + booting with the patched kernel, + 1. plug a speaker or headset in the front port + 2. play sound + 3. check if we can hear the sound or not + 4. repeat the step 1 ~ 3 20 times + 5. there is no failure + + [Where problems could occur] + The patches change the depop and headset_type_detect routine, so it + is possible to introduce regression on pop noise and headset detection, + for realtek codec of alc285 and alc256 family, but the regression + possibility is very low, we tested the patches on a couple of Dell and + Lenovo machines, everything worked as well as before. ** Changed in: linux (Ubuntu Jammy) 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/2077690 Title: alsa: Headphone and Speaker couldn't output sound intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077690] [NEW] alsa: Headphone and Speaker couldn't output sound intermittently
Public bug reported: This bug is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Oracular) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Tags: oem-priority originate-from-2077191 somerville ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-2077191 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077690 Title: alsa: Headphone and Speaker couldn't output sound intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
** Description changed: + In the v2: + Thanks for Timo to point out, there is the same problem for + lunar-generic and mantic-generic kernels, and we applied to similar + UBUNTU SAUCE patches to those kernels, but somehow we forgot to + apply the patches to unstable at that time, hence we have regression + for this issue in N/O/..., the tracking bug for L/M is: + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034504 + + short-term plan: + SRU the SAUCE patches to N/O/unstable, fix the regression on those + Dell machines ASAP. + long-term plan: + Kai-heng will ping and discuss with linux-pci maintainers, modify + the patch as maintainers request, once the formal patches are merged + to upstream kernel, I will revert the SAUCE patches from N/O/unstable + and SRU the formal patches to these kernels. + + + [Impact] + The NVME controller works in RAID on mode by default on some Dell + machines, and in this case, the PCIE ASPM couldn't be enabled, and + as a result the system idle can't enter deep idle states. This issue + not only impacts ubuntu users but also impacts our Dell OEM projects. + + + [Fix] + pick 2 commits from linux-pci mailist + + [Test] + After running the patched kernel, we could run 'sudo lspci -nnvv' + and check "Non-Volatile memory controller": +LnkCtl: ASPM L1 Enabled; + + And check idle states, we could see the system could enter deep idle: + $ sudo cat /sys/kernel/debug/pmc_core/package_cstate_show + Package C2 : 55740989 + Package C3 : 4656373 + Package C6 : 43325041 + Package C7 : 6687655 + Package C8 : 44948950 + Package C9 : 1693 + Package C10 : 92865596 + + [Where problems could occur] + Because the patchset is not accepted by upstream yet, it is a bit + risky to merge the patchset to ubuntu kernel. And the patch only + impacts vmd driver, hence if there is regression, it could only be + in the nvme driver with RAID on mode. The regression possibility is + very low because we already tested the patch on many Dell, lenovo + machines, there is no regression so far. + + After upgrading to Ubuntu 24.04 the CPU is unable to hit lower idle states. The device is a HP Spectre x360 14 (14-ea1000) with a Tiger Lake CPU. This is a regression introduced somewhere 6.5.0-42 and 6.8.0-36. The issue is not observed when booting the same OS with 6.5.0-42. Some debug output: - root@hp-spectre-x360:/sys/kernel/debug/pmc_core# cat package_cstate_show + root@hp-spectre-x360:/sys/kernel/debug/pmc_core# cat package_cstate_show Package C2 : 36087003 Package C3 : 69314350 Package C6 : 0 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 0 - $ sudo cat /sys/kernel/debug/pmc_core/substate_requirements -Element |S0i2.0 |Status | + Element |S0i2.0 |Status | pmc0:USB2PLL_OFF_STS | Required | Yes | pmc0: PCIe/USB3.1_Gen2PLL_OFF_STS | Required | | pmc0: PCIe_Gen3PLL_OFF_STS | Required | Yes | pmc0:OPIOPLL_OFF_STS | Required | Yes | pmc0: OCPLL_OFF_STS | Required | Yes | pmc0:MIPIPLL_OFF_STS | Required | Yes | pmc0:AC_Ring_Osc_OFF_STS | Required | Yes | pmc0:SATAPLL_OFF_STS | Required | Yes | pmc0:CSME_PG_STS | Required | Yes | pmc0:SATA_PG_STS | Required | Yes | pmc0:xHCI_PG_STS | Required | Yes | pmc0: UFSX2_PG_STS | Required | Yes | pmc0: OTG_PG_STS | Required | Yes | pmc0: SPA_PG_STS | Required | Yes | pmc0: SPB_PG_STS | Required | Yes | pmc0: SPC_PG_STS | Required | | pmc0:THC0_PG_STS | Required | Yes | pmc0:THC1_PG_STS | Required | Yes | pmc0: GBETSN_PG_STS | Required | Yes | pmc0: GBE_PG_STS | Required | Yes | pmc0:LPSS_PG_STS | Required | Yes | pmc0: xHCI0_D3_STS | Required | Yes | pmc0: xDCI1_D3_STS | Required | Yes | pmc0: IS_D3_STS | Required | Yes | pmc0: GBE_TSN_D3_STS | Required | Yes | pmc0: CPU_C10_REQ_STS_0 | Required | Yes | pmc0:MPHY_Core_DL_REQ_STS_16 | Required | | pmc0: Break-even_En_REQ_STS_17 | Required | Yes | pmc0:Auto-demo_En_REQ_STS_18 | Required | Yes | pmc0: Int_Timer_SS_Wake0_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake1_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake2_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake3_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake4_Pol_STS | Required | | pmc0: Int_Timer_SS_Wake5_Pol_STS | Required | | - On 6.5:
[Bug 2072679] Re: Regression: unable to reach low idle states on Tiger Lake
We have the same bug in the past, it is: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034504 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072679 Title: Regression: unable to reach low idle states on Tiger Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
I am affected by this bug as well. I have a Windows system on internal drive and installed Ubuntu on an external drive. GRUB installs to the internal drive even if I chose the external drive. Here is what I did: 1. Boot Ubuntu from my bootable USB drive used for installing the system. 2. Download a tool called boot-repair. Use it to install GRUB to my external drive. 3. Remove the GRUB in the wrong location by following the top answer [here](https://askubuntu.com/questions/429610/uninstall-grub-and-use-windows-bootloader). Alternatively, mount the partition mentioned in the link using the Disks app in Ubuntu and remove the GRUB files for Ubuntu in the wrong location. 4. In the BIOS, remove the option in boot menu that no longer works. This bug is fixed in the 24.04 installer, but 24.04 did not work for me. You can prevent it by disconnecting your irrelevant drives before installing. Some BIOS allows you to disconnect them, if it does not, do it by physically pulling out the drives. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-efi-amd64-signed/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077112] Re: Missing Huc/Gsc support for Intel GFX Xe driver for Lunar Lake
What kernel version is for Oracular? 6.10 or 6.11? If it is 6.10, do we still need to backport the patch to oracular kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077112 Title: Missing Huc/Gsc support for Intel GFX Xe driver for Lunar Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076216] Re: Ubuntu 24.04 LTS kernel 6.8.0-35 fails to boot up and get stuck at efi stub measured initrd data into pcr 9
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-ubuntu-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076216 Title: Ubuntu 24.04 LTS kernel 6.8.0-35 fails to boot up and get stuck at efi stub measured initrd data into pcr 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076114] [NEW] Pollen 4.22-0ubuntu2 installs deprecated Upstart files
Public bug reported: Pollen 4.22-0ubuntu2 installs upstart files (/etc/init/pollen.conf and /etc/init/pollen-restart.conf), while systemd has replaced upstart in the targeted ubuntu release. This should be caused by the debian/pollen.upstart and debian/pollen- restart.upstart files. The added files in /etc/init are probably okay to stay as they are not effective, but it would be better to remove them. See: https://manpages.debian.org/testing/debhelper/dh_installinit.1.en.html#debian/~3 ** Affects: pollen (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/2076114 Title: Pollen 4.22-0ubuntu2 installs deprecated Upstart files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/2076114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070158] Re: RFIM and SAGV Linux Support for G10 models
** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070158 Title: RFIM and SAGV Linux Support for G10 models To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2070158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1983181] Re: Cheese Internal data stream error
This still happens on my system as well (Ubuntu-Server 22.04.4 2024.05.04 (Cubic 2024-05-04 16:39)) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1983181 Title: Cheese Internal data stream error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1983181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071633] Re: [81DE, Realtek ALC236, Mic, Internal] No sound at all
And could you try a workaround: edit /etc/modprobe.d/alsa-base.conf, add "options snd-hda-intel model=aspire-headset-mic" reboot the machine and redo the test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071633 Title: [81DE, Realtek ALC236, Mic, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2071633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071633] Re: [81DE, Realtek ALC236, Mic, Internal] No sound at all
@Akhil,
I found the headset mic is not detected by kernel driver at all, so it
will not show in the pulseaudio/gnome.
control.12 {
iface CARD
name 'Headset Mic Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
Is this problem a regression? Does the headset mic ever work with other linux
kernels or other linux distributions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071633
Title:
[81DE, Realtek ALC236, Mic, Internal] No sound at all
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2071633/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072432] Re: Loud, brief speaker popping/distortion occurs when clicking on empty or white screen areas
And there are 3 lineout and 1 headphone jacks, what jacks have this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072432 Title: Loud, brief speaker popping/distortion occurs when clicking on empty or white screen areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2072432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072432] Re: Loud, brief speaker popping/distortion occurs when clicking on empty or white screen areas
Is this problem a regression of ubuntu 24.04? Did you try the 22.04 or sth else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072432 Title: Loud, brief speaker popping/distortion occurs when clicking on empty or white screen areas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2072432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070158] Re: RFIM and SAGV Linux Support for G10 models
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070158 Title: RFIM and SAGV Linux Support for G10 models To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2070158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071549] [NEW] 22.04 upgrade to 24.04 bug
Public bug reported: There is a bug stopping upgrade to 24.04 when I run do-release-upgrade -d under ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 644:1000:116:0:2024-06-25 09:12:06.488576162 +0800:2024-06-25 09:12:06.488576162 +0800:/var/crash/_opt_kingsoft_wps-office_office6_wpscloudsvr.1000.upload 640:1000:116:15574363:2024-06-25 09:12:06.488576162 +0800:2024-06-25 09:12:06.512603319 +0800:/var/crash/_opt_kingsoft_wps-office_office6_wpscloudsvr.1000.crash 600:109:116:37:2024-06-25 09:12:09.095468088 +0800:2024-06-25 09:12:09.095468088 +0800:/var/crash/_opt_kingsoft_wps-office_office6_wpscloudsvr.1000.uploaded CurrentDesktop: ubuntu:GNOME Date: Sun Jun 30 21:06:42 2024 InstallationDate: Installed on 2017-12-04 (2399 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-06-30 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-06-30 21:06:04 Requested-By: linger (1000) End-Date: 2024-06-30 21:06:04 VarLogDistupgradeAptlog: Log time: 2024-06-30 21:05:56.303129 Log time: 2024-06-30 21:06:02.373623 Log time: 2024-06-30 21:06:41.621303 Log time: 2024-06-30 21:06:45.284324 VarLogDistupgradeApttermlog: Log started: 2024-06-30 21:06:04 Log ended: 2024-06-30 21:06:04 ** 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/2071549 Title: 22.04 upgrade to 24.04 bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2071549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071479] [NEW] Can't upgrade from 22.04 to 24.04
Public bug reported: Hi Ubuntu folks, I can't upgrade my laptop from 22.04 to 24.04 when i excute the command "sudo do-release-upgrade --allow-third-party -d". Could you help me to guide how to upgrade my laptop. Thanks a lot. ProblemType: Bug DistroRelease: Ubuntu Kylin 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.15.0-115.125-generic 5.15.158 Uname: Linux 5.15.0-115-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: UKUI Date: Fri Jun 28 22:52:02 2024 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-06-28 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages ** Summary changed: - Can't upgrade from 22.04 from 24.04 + Can't upgrade from 22.04 to 24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071479 Title: Can't upgrade from 22.04 to 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2071479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070434] [NEW] Configurate a IPv6 only and IPv4 disabled networking by netplan
Public bug reported: Hi all, We want to set up an IPv6-only network in a lab, and some Ubuntu ( release >=18.04) needs to be configured according to the networking requirements. I found a Netplan doc about disabling ipv6 by editing the Netplan YAML file: https://github.com/canonical/netplan/blob/main/doc/netplan-tutorial.md#editing-netplan-yaml-files-to-disable-ipv6 === When you finish, the whole configuration in second-interface.yaml should look like this: network: version: 2 ethernets: enp6s0: dhcp4: true accept-ra: false link-local: [] === can I use the same way to disable IPv4? e.g. network: version: 2 ethernets: eth0: dhcp4: false dhcp6: true accept-ra: false link-local: [ipv6] Or are there other ways to disable ipv4 on Ubuntu? In addition, Ubuntu 18.04 uses ifupdown with /etc/network/interfaces to configure the networking e.g. === iface lo inet loopback auto lo auto eth0 iface eth0 inet manual iface eth0 inet6 dhcp netmask 16 accept_ra 1 autoconf 1 === Can I add 'iface eth0 inet manual' in this file to disable IPv4? Thanks, Thanks, ** Affects: netplan.io (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/2070434 Title: Configurate a IPv6 only and IPv4 disabled networking by netplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2070434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070166] Re: tablet screen rotation doesn't work as expected
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070166 Title: tablet screen rotation doesn't work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/2070166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070158] Re: RFIM and SAGV Linux Support for G10 models
** Description changed: - This is for tracking purpose. + BugLink: https://bugs.launchpad.net/bugs/2070158 + + [Impact] + This is a feature request from HP, RFIM is for frequency, SAGV is for voltage. + They are used as dynamic switching to reduce RF noise. RFIM is already + supported in the kernel, this patchset adds the SAGV feature. + + [Fix] + Cherry-pick 6 commits from mainline kernel + + [Test] + Enable the SAGV from the BIOS, booting with the patched kernel, after booting + up, run 'systemctl status dtt.service', we will get: service is enabled and + service is running + run 'cat /sys/kernel/debug/dri/:00:02.0/i915_sagv_status', we will get: + SAGV available: Yes + SAGV status: enabled + + [Where problems could occur] + Because the fix is for i915, it is likely introduce regression on graphic, + but this possibility is very low. These 6 commits are merged to + mainline kernel from v6.10-rc1, so far there is no regression reported + on them. And we tested the patched kernel on different Intel machines, all + worked well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070158 Title: RFIM and SAGV Linux Support for G10 models To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2070158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070158] [NEW] RFIM and SAGV Linux Support for G10 models
Public bug reported: This is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux (Ubuntu Noble) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1978770 stella ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1978770 stella -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070158 Title: RFIM and SAGV Linux Support for G10 models To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2070158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
I removed verification-done-jammy-linux-oem-6.5, I already verified the SRU with the jammy and noble, and the tag has been added accordingly. ** Tags removed: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067580] [NEW] cannot disable livepatch when /etc/lsb-release is edited
Public bug reported:
I use the wechat program which will detect whether the system is
"Kylin", if not, the program cannot run correctly. So I modify the
/etc/lsb-release and then the wechat program could use normally.
However, I cannot use Ubuntu Pro livepatch because it says “livepatchd
error: The platform Kylin V10 is not supported. exiting.”
Then I re-modified the /etc/lsb-release and try to re-install livepatch,
but failed.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 32.3~22.04
ProcVersionSignature: Ubuntu 6.5.0-35.35~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 30 16:45:42 2024
InstallationDate: Installed on 2024-04-23 (37 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64
(20240220)
PackageArchitecture: all
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)
cloud-id.txt-error: Invalid command specified 'cloud-id'.
jobs-status.json: {"metering": {"last_run": "2024-05-30T08:28:05.567778+00:00",
"next_run": "2024-05-30T12:28:05.567778+00:00"}, "update_contract_info": null,
"update_messaging": {"last_run": "2024-05-30T08:28:05.567778+00:00",
"next_run": "2024-05-30T14:28:05.567778+00:00"}}
livepatch-status.txt-error: Failed running command
'/snap/bin/canonical-livepatch status' [exit(1)]. Message: error executing
status: open /var/snap/canonical-livepatch/278/livepatchd.err: permission denied
uaclient.conf:
contract_url: https://contracts.canonical.com
log_level: debug
** Affects: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067580
Title:
cannot disable livepatch when /etc/lsb-release is edited
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2067580/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065096] Re: [i915] Display is Laggy/Unresponsive when PSR is enabled
OK, got it. The testing kernel is for fixing another psr related issue. I thought this could fix your problem too, but looks like it couldn't fix the issue on your side. You could file a bug to Intel: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065096 Title: [i915] Display is Laggy/Unresponsive when PSR is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065096] Re: [i915] Display is Laggy/Unresponsive when PSR is enabled
Download linux-image-unsigned-6.8.0-1001-oem_6.8.0-1001.1+psr2_amd64.deb and linux-modules-6.8.0-1001-oem_6.8.0-1001.1+psr2_amd64.deb to a local folder (like /tmp/test), then $cd /tmp/test; $sudo dpkg -i *.deb, reboot the sytem, in the grub, select linux-6.8.0-1001 to boot up (don't forget remove i915.enable_psr=0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065096 Title: [i915] Display is Laggy/Unresponsive when PSR is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065096] Re: [i915] Display is Laggy/Unresponsive when PSR is enabled
@Jonathon, Could you help test this kernel? https://people.canonical.com/~hwang4/psr2-oem68/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065096 Title: [i915] Display is Laggy/Unresponsive when PSR is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2065096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065524] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2065524/+attachment/5778287/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065524 Title: DMAR: DRHD error with black screen while wake from sleep mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2065524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065524] Re: DMAR: DRHD error with black screen while wake from sleep mode
apport information ** Tags added: apport-collected noble wayland-session ** Description changed: It happens all the time on my Alienware x14 laptop, every time while wake form sleep mode the screen always goes black and all the keys don't work. I could only solve it by force shutting down and restarting with the power button. I've tried https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040 solutions but none of them worked, so I suspect this is a different problem. I have attached the relevant logs, the approximate time is around 20:44-20:45. ``` Alienware Alienware x14 Ubuntu 24.04 LTS 12th Gen Intel® Core™ i7-12700H × 20 Intel® Graphics (ADL GT2) NV177 NVIDIA Graphics Wayland ``` + --- + ProblemType: Bug + ApportVersion: 2.28.1-0ubuntu3 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 24.04 + InstallationDate: Installed on 2024-04-27 (17 days ago) + InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) + Package: mutter 46.0-1ubuntu9 + PackageArchitecture: amd64 + ProcEnviron: + LANG=zh_CN.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= + ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 + Tags: noble wayland-session + Uname: Linux 6.8.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sudo users + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2065524/+attachment/5778286/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065524 Title: DMAR: DRHD error with black screen while wake from sleep mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2065524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065524] [NEW] DMAR: DRHD error with black screen while wake from sleep mode
Public bug reported: It happens all the time on my Alienware x14 laptop, every time while wake form sleep mode the screen always goes black and all the keys don't work. I could only solve it by force shutting down and restarting with the power button. I've tried https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040 solutions but none of them worked, so I suspect this is a different problem. I have attached the relevant logs, the approximate time is around 20:44-20:45. ``` Alienware Alienware x14 Ubuntu 24.04 LTS 12th Gen Intel® Core™ i7-12700H × 20 Intel® Graphics (ADL GT2) NV177 NVIDIA Graphics Wayland ``` ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Attachment added: "log_message_all.txt" https://bugs.launchpad.net/bugs/2065524/+attachment/5777643/+files/log_message_all.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065524 Title: DMAR: DRHD error with black screen while wake from sleep mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2065524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063096] Re: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle
** Tags removed: verification-needed-jammy-linux verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063096 Title: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
I also have same problems on Ubuntu 24.04 LTS maybe, it will black screen when wake up from sleep mode. only prees power button to force shutdown. ** Attachment added: "log_files.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5776302/+files/log_files.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
About the #3, the so-called regression has nothing to do with this SRU: For arm64: 682s : failure: setup script failed with code 1: /home/ubuntu/autopkgtest/ssh-setup/nova open --flavor autopkgtest-big --security-groups ... For armhf: 345s Error: Failed to fetch instance "autopkgtest-lxd-rdqntd" in project "default": Instance not found ** Tags added: verification-done-jammy verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063096] Re: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle
** Tags removed: verification-needed-noble-linux ** Tags added: verification-done-noble-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063096 Title: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063815] Re: No microphone available
*** This bug is a duplicate of bug 2061254 *** https://bugs.launchpad.net/bugs/2061254 Please refer to #2061254 ** This bug has been marked a duplicate of bug 2061254 No mic detected - Ubuntu 24.04 Beta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063815 Title: No microphone available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2063815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
About the enable proposed ppa: It was the actual official proposed pocket for mantic and jammy. sth like this: deb [arch=amd64] http://archive.ubuntu.com/ubuntu/ jammy-proposed main restricted About the two additional steps: I did run them in mantic and jammy in my verification (#3 and #4). Thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063096] Re: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle
** Description changed: - This is for tracking purpose + [Impact] + + On a Dell laptop, When we do suspend/resume test, we found the + realtek wifi couldn't work after resume, from the dmesg, we found + the error log as below: + Log: + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: fw security fail + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: download firmware fail + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x1E0 = 0x62 + 三 05 15:08:02 u-Precision-3591 kernel: rtw89_8852be :02:00.0: [ERR]fwdl 0x83F2 = 0x8 + + [Fix] + + Backport a commit from mainline kernel (linux-next), this will retry firmware + loading for 5 times. + + [Test Case] + + run suspend/resume test case for over 100 times, the wifi still + works. + + [Where problems could occur] + + This commit comes from mailine kernel, and it doesn't change existing + driver except loading firmware a couple of more times if there is an error. + In theory this will not introduce regression. ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063096 Title: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063096] [NEW] RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle
Public bug reported: This is for tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Medium Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2056141 somerville ** Package changed: linux-firmware (Ubuntu) => linux-oem-6.5 (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-2056141 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063096 Title: RTL8852BE fw security fail then lost WIFI function during suspend/resume cycle To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062499] Re: nfs mount over VPN tunnel does not work
** Description changed: nfs mount over VPN tunnel does not work while other nfs mount works. I have physical network interface eth0 on 192.168.101.1, and OpenVPN tunnel tun0 on 20.8.0.1. If I try to nfs mount over VPN, I get the following error: ``` root@wxc-dell:/# mount -v 20.8.0.1:/netboot/nfs /mnt/a mount.nfs: timeout set for Fri Apr 19 13:27:51 2024 mount.nfs: trying text-based options 'vers=4.2,addr=20.8.0.1,clientaddr=20.8.0.1' mount.nfs: mount(2): No such file or directory mount.nfs: trying text-based options 'addr=20.8.0.1' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: trying 20.8.0.1 prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying 20.8.0.1 prog 15 vers 3 prot UDP port 49387 mount.nfs: mount(2): Permission denied mount.nfs: mounting 20.8.0.1:/netboot/nfs failed, reason given by server: No such file or directory ``` If I downgrade nfs-kernel-server from 2.6.1-1ubuntu1.2 to Debian - Bullseye's version (1.3.4-6), then everything works. + Bullseye's version (1.3.4-6), together with dependencies, then + everything works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nfs-kernel-server 1:2.6.1-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .etc.request-key.d.id_resolver.conf: create id_resolver * * /usr/sbin/nfsidmap -t 600 %k %d ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 19 13:23:40 2024 InstallationDate: Installed on 2024-04-08 (10 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) NFSMounts: - + NFSv4Mounts: - + SourcePackage: nfs-utils UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062499 Title: nfs mount over VPN tunnel does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Description changed: + This is SRU template for linux kernel: + + [Impact] + + On a Dell laptop, let it connect to a WiFi router, connect a BT + device, then disconnect it, connect the bt device again, we expect + the device could be connected successfully, but it couldn't and + the BT firmeware crashed. + + [Fix] + + Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel + patches, here we send the MR for 2 kernel patches. The firmware PR was + already sent out. And one of the patches is from linux-next, the other is + from rtw.git and is going to be merged to linux-next soon. + + [Test Case] + + + With the upgraded firmware + kernel with the 2 kernel patches, bt + firmware will not crash anymore and bt could connect / disconnect + many many bt devices. + + [Where problems could occur] + + This MR comes from upstream commits, it has low possibility to + introduce regression. If the bt or wifi on this laptop couldn't + work as well as before, it is possible that this MR introduces + regression. According to our test, the wifi and bt could work well + with upgraded firmware. + + === This SRU template is for linux-firmware: BugLink: https://bugs.launchpad.net/bugs/2060904 [Impact] On a Dell laptop, let it connect to a WiFi router, connect a BT device, then disconnect it, connect the bt device again, we expect the device could be connected successfully, but it couldn't and the BT firmeware crashed. [Fix] Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel patches, here we send the MR for firmware first. And it is backward compatible, the upgraded firmware could work with kernel without those 2 patches as well as before. [Test Case] With the upgraded firmware + kernel without the 2 kernel patches, the wifi and bt could work as well / bad as before. With the upgraded firmware + kernel with the 2 kernel patches, bt firmware will not crash anymore and bt could connect / disconnect many many bt devices. [Where problems could occur] This MR comes from upstream commit, it has low possibility to introduce regression. If the bt or wifi on this laptop couldn't work as well as before, it is possible that this MR introduces regression. According to our test, the wifi and bt could work well with upgraded firmware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062412] Re: No input through internal microphone (Ryzen 6000)
*** This bug is a duplicate of bug 2061254 *** https://bugs.launchpad.net/bugs/2061254 This issue was already reported in #2061254. ** This bug has been marked a duplicate of bug 2061254 No mic detected - Ubuntu 24.04 Beta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062412 Title: No input through internal microphone (Ryzen 6000) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062499] [NEW] nfs mount over VPN tunnel does not work
Public bug reported: nfs mount over VPN tunnel does not work while other nfs mount works. I have physical network interface eth0 on 192.168.101.1, and OpenVPN tunnel tun0 on 20.8.0.1. If I try to nfs mount over VPN, I get the following error: ``` root@wxc-dell:/# mount -v 20.8.0.1:/netboot/nfs /mnt/a mount.nfs: timeout set for Fri Apr 19 13:27:51 2024 mount.nfs: trying text-based options 'vers=4.2,addr=20.8.0.1,clientaddr=20.8.0.1' mount.nfs: mount(2): No such file or directory mount.nfs: trying text-based options 'addr=20.8.0.1' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: trying 20.8.0.1 prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying 20.8.0.1 prog 15 vers 3 prot UDP port 49387 mount.nfs: mount(2): Permission denied mount.nfs: mounting 20.8.0.1:/netboot/nfs failed, reason given by server: No such file or directory ``` If I downgrade nfs-kernel-server from 2.6.1-1ubuntu1.2 to Debian Bullseye's version (1.3.4-6), then everything works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nfs-kernel-server 1:2.6.1-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .etc.request-key.d.id_resolver.conf: create id_resolver * * /usr/sbin/nfsidmap -t 600 %k %d ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Apr 19 13:23:40 2024 InstallationDate: Installed on 2024-04-08 (10 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) NFSMounts: NFSv4Mounts: SourcePackage: nfs-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062499 Title: nfs mount over VPN tunnel does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046315] Re: panel flickering after the i915.psr2 is enabled
** Description changed: + SRU verificaton for Noble and oem-6.8-noble: + + [Impact] + In Dell oem project, we found the graphic is flickering on some + machines, finally we narrowed down the issue on (some specific panels + + i915.psr2 enabled), and the issue was reported to Intel, Intel fixed + the issue in the most recent mainline kernel. Here backporting the + patches to Noble kernel. + + It is hard to backport the patches to mantic and oem-6.5, so we wrote + a workaround patch to disable the psr2 for those pannels in the oem-6.5. + + https://gitlab.freedesktop.org/drm/intel/-/issues/9739 + + [Fix] + cherry-pick 8 patches from mainline kernel + + [Test] + I applied the patches to Noble kernel and built a testing kernel, and + Dell validated the testing kernel on those machines, the graphic + didn't flicker anymore. + + I installed the testing kernel on some machines with Intel 13th, 12th + 11th and 10th gen cpu, the grahic worked well too. + + [Where problems could occur] + This patchset changes the fast wake settings for some gpu, it is + possible to make the graphic flicker, but this possibility is very + low, since the patchset comes from mainline kernel and we validated + the patchset on different gens of Intel cpus. + + === + BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: panel flickering after the i915.psr2 is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046315] Re: panel flickering after the i915.psr2 is enabled
** Summary changed: - panel flickering after enabling the psr2 + panel flickering after the i915.psr2 is enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: panel flickering after the i915.psr2 is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046315] Re: panel flickering after enabling the psr2
** Summary changed: - oem-6.5: disable psr2 for some panels according to edid + panel flickering after enabling the psr2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046315 Title: panel flickering after enabling the psr2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046681] Re: jammy-oem-6.5: one more panel needs to disable psr2
For oem-6.8 and noble kernels, the fix will be merged by https://bugs.launchpad.net/ubuntu/jammy/+source/linux- oem-6.8/+bug/2046315 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046681 Title: jammy-oem-6.5: one more panel needs to disable psr2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046315] Re: oem-6.5: disable psr2 for some panels according to edid
** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.8 (Ubuntu Jammy) 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/2046315 Title: oem-6.5: disable psr2 for some panels according to edid To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061254] Re: No mic detected - Ubuntu 24.04 Beta
I checked the latest ubuntu noble kernel, the fix is already merged to
this kernel through this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060531
Please wait for the upcoming release version of noble kernel.
commit 6a9156867a5ce4ded2967ca46b0a8d755d9a1ee7
Author: Jiawei Wang
Date: Wed Mar 13 09:58:53 2024 +0800
ASoC: amd: yc: Revert "add new YC platform variant (0x63) support"
BugLink: https://bugs.launchpad.net/bugs/2060531
commit 37bee1855d0e3b6dbeb8de71895f6f68cad137be upstream.
This reverts commit 316a784839b21b122e1761cdca54677bb19a47fa,
that enabled Yellow Carp (YC) driver for PCI revision id 0x63.
Mukunda Vijendar [1] points out that revision 0x63 is Pink
Sardine platform, not Yellow Carp. The YC driver should not
be enabled for this platform. This patch prevents the YC
driver from being incorrectly enabled.
Link:
https://lore.kernel.org/linux-sound/023092e1-689c-4b00-b93f-4092c3724...@amd.com/
[1]
Signed-off-by: Jiawei Wang
Link: https://msgid.link/r/20240313015853.3573242-3...@jwang.link
Signed-off-by: Mark Brown
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Paolo Pisati
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Noble)
Importance: Medium
Assignee: Hui Wang (hui.wang)
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061254
Title:
No mic detected - Ubuntu 24.04 Beta
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061254/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061254] Re: No mic detected - Ubuntu 24.04 Beta
@alef & @Burnarz, I reproduced the issue on a thinkpad x13-amd laptop. And the most recent mainline kernel already fixed this regression, I will backport the fix to ubuntu kernel. thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061254 Title: No mic detected - Ubuntu 24.04 Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2061254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061254] Re: No mic detected - Ubuntu 24.04 Beta
According to #3, the sound card for dmic is not created. please run this command: $cd /sys/devices $find . -iname acp_* $find . -iname dmic-* and paste the output of 2 commands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061254 Title: No mic detected - Ubuntu 24.04 Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2061254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061254] Re: No mic detected - Ubuntu 24.04 Beta
Please cat /proc/asound/cards, this could show how many sound cards are detected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061254 Title: No mic detected - Ubuntu 24.04 Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2061254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Noble) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] Re: Fix the RTL8852CE BT FW Crash based on SER false alarm
** Description changed: - This bug is for tracking purpose + This SRU template is for linux-firmware: + + BugLink: https://bugs.launchpad.net/bugs/2060904 + + [Impact] + + On a Dell laptop, let it connect to a WiFi router, connect a BT + device, then disconnect it, connect the bt device again, we expect + the device could be connected successfully, but it couldn't and + the BT firmeware crashed. + + [Fix] + + Need to upgrade the firmware for RTL8852CE and cherry-pick 2 kernel + patches, here we send the MR for firmware first. And it is backward + compatible, the upgraded firmware could work with kernel without + those 2 patches as well as before. + + [Test Case] + + With the upgraded firmware + kernel without the 2 kernel patches, + the wifi and bt could work as well / bad as before. + + With the upgraded firmware + kernel with the 2 kernel patches, bt + firmware will not crash anymore and bt could connect / disconnect + many many bt devices. + + [Where problems could occur] + + This MR comes from upstream commit, it has low possibility to + introduce regression. If the bt or wifi on this laptop couldn't + work as well as before, it is possible that this MR introduces + regression. According to our test, the wifi and bt could work well + with upgraded firmware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
Installed the linux/6.5.0-33.33 kernel in -proposed, and the issue is fixed by the kernel. ** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
Installed the linux/5.15.0-104.114 kernel in -proposed, and the issue is fixed by this kernel. ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060904] [NEW] Fix the RTL8852CE BT FW Crash based on SER false alarm
Public bug reported: This bug is for tracking purpose ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.8 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.8 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Tags: oem-priority originate-from-2059397 somerville ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux-oem-6.8 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.8 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.8 (Ubuntu Noble) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-2059397 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060904 Title: Fix the RTL8852CE BT FW Crash based on SER false alarm To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059898] Re: ubuntu-24.04 daily build install failed with netwok cable connected
Hi Olivier, Additional info about the lastest daily build 2024/4/7 8:26 version, Our QA used this version on several machines and found this version can install successfully with the cable connected. Dong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059898 Title: ubuntu-24.04 daily build install failed with netwok cable connected To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2059898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060450] Re: ubuntu-24.04: cannot recoginze vroc RAID device during installtation
** Attachment added: "error screen" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060450/+attachment/5762117/+files/screen.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060450 Title: ubuntu-24.04: cannot recoginze vroc RAID device during installtation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060450] [NEW] ubuntu-24.04: cannot recoginze vroc RAID device during installtation
Public bug reported: lsb_release -rd: Description:Untun Noble Numbat(development branch) Release: 24.04 What you expected to happen: Using two nvme disks create VROC RAID by uefi, than install os on RAID device and when choose "Use an entire disk", os can found VROC RAID device and install os on it. What happened instead: Os cannot found VROC RAID which has already created by uefi. Extra verification: we use redhat9 have a try, os can recognize VROC RAID device successfully. we use ubuntu 22.04 have a try, os can recognize VROC RAID device successfully. Only the latest ubuntu 24.04 version has this issue. ** Affects: subiquity (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/2060450 Title: ubuntu-24.04: cannot recoginze vroc RAID device during installtation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060450] Re: ubuntu-24.04: cannot recoginze vroc RAID device during installtation
** Attachment added: "lspci -nvvv info" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060450/+attachment/5762115/+files/lspcibad.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060450 Title: ubuntu-24.04: cannot recoginze vroc RAID device during installtation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060450] Re: ubuntu-24.04: cannot recoginze vroc RAID device during installtation
** Attachment added: "journal log" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060450/+attachment/5762116/+files/journalbad.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060450 Title: ubuntu-24.04: cannot recoginze vroc RAID device during installtation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060450] Re: ubuntu-24.04: cannot recoginze vroc RAID device during installtation
** Attachment added: "vmd driver info" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060450/+attachment/5762114/+files/vmdinfobad.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060450 Title: ubuntu-24.04: cannot recoginze vroc RAID device during installtation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060442] Re: ubuntu-24.04 install fail due to "finish: cmd-in-target: FAIL: curtin command in-target"
Added journalctl -xb log. ** Attachment added: "journalctl log" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060442/+attachment/5762109/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060442 Title: ubuntu-24.04 install fail due to "finish: cmd-in-target: FAIL: curtin command in-target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060442] [NEW] ubuntu-24.04 install fail due to "finish: cmd-in-target: FAIL: curtin command in-target"
Public bug reported: lsb_release -rd: Description:Untun Noble Numbat(development branch) Release: 24.04 What you expected to happen: Install os on nvme,expected to install succefully. What happened instead: Install os on nvme, install always failed.mount and umount operation failed and exit the installation process. The error log: Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2923]: Reading package lists... Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2923]: E: The repository 'http://security.ubuntu.com/ubuntu noble-security Release' no longer has a Release file. Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: TIMED subp(['udevadm', 'settle']): 0.007 Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['mount', '--make-private', '/tmp/tmptrdn_sng/mount/usr/bin/ischroot'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['umount', '/tmp/tmptrdn_sng/mount/usr/bin/ischroot'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['mount', '--make-private', '/tmp/tmptrdn_sng/mount/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['umount', '/tmp/tmptrdn_sng/mount/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['mount', '--make-private', '/tmp/tmptrdn_sng/mount/sys'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['umount', '/tmp/tmptrdn_sng/mount/sys'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['mount', '--make-private', '/tmp/tmptrdn_sng/mount/run'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['umount', '/tmp/tmptrdn_sng/mount/run'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['mount', '--make-private', '/tmp/tmptrdn_sng/mount/proc'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['umount', '/tmp/tmptrdn_sng/mount/proc'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['mount', '--make-private', '/tmp/tmptrdn_sng/mount/dev'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: Running command ['umount', '/tmp/tmptrdn_sng/mount/dev'] with allowed return codes [0] (capture=False) Apr 08 07:04:28 ubuntu-server subiquity_log.2151[2910]: finish: cmd-in-target: FAIL: curtin command in-target Apr 08 07:04:28 ubuntu-server curtin_event.2151.3[2910]: finish: cmd-in-target: FAIL: curtin command in-target Apr 08 07:04:28 ubuntu-server systemd[1]: run-u31.service: Main process exited, code=exited, status=100/n/a ** Affects: subiquity (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/2060442 Title: ubuntu-24.04 install fail due to "finish: cmd-in-target: FAIL: curtin command in-target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2060442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059898] Re: ubuntu-24.04 daily build install failed with netwok cable connected
hi, i noticed the latest daily build verisonnoble-live-server-amd64.iso 2024-04-07 08:262.6G. Does this version include the bug fixes? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059898 Title: ubuntu-24.04 daily build install failed with netwok cable connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2059898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059898] Re: ubuntu-24.04 daily build install failed with netwok cable connected
Hi jeff, Here are the answers: 1: NO network cable connected, installation is successful yes, after removing network cable, installation is successfully whatever disks(SATA,NVME...) we used. And when cable disconnected, they can install successfully. 2.Network cable connected and internet is available, installation is successful The machine's network is our local area network, i think it cannot connect to ubuntu mirror address and cannot connect to internet. And our network proxy is broken, so i am not sure whether it can install successfully when our network can connect to internet. We only confirm when it connect to local area network without internet, it is always failed. 3.Network cable connected, network is available, INTERNET is unavailable (airgapped lab), installation fails yes in this case, it fails. I believe from what you described elsewhere #3 is the case you are seeing, because you are in a lab with no external access, is that correct? yes, correct, and i also confirm #1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059898 Title: ubuntu-24.04 daily build install failed with netwok cable connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2059898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059898] Re: ubuntu-24.04 daily build install failed with netwok cable connected
** Attachment added: "journalctl log" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2059898/+attachment/5760996/+files/jour.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059898 Title: ubuntu-24.04 daily build install failed with netwok cable connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2059898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059898] [NEW] ubuntu-24.04 daily build install failed with netwok cable connected
Public bug reported:
verison：ubuntu 24.04 subiquity version
OS:noble-live-server-amd64.iso
CPU:AMD EPYC 9634 84-Core Processor*1
MEMORY: M321R2GA3BB6-CQKVG*2
ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
UEFI MODE
lsb_release -rd: Description:Untun Noble Numbat(development branch)
Release: 24.04
What you expected to happen:
Install os on disk with with netwok cable connected,expected to install
succefully.
What happened instead:
Install os with netwok cable connected, install always failed.
we opened this case
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057996 to solve nvme
disk install fail issue before and we use daily build which build on 3/26 have
a try and that version is good working at both of netwok cable connected and
disconnected case.
But for 3/29 daily build version, our QA found when connect cable(It's a local
area network (LAN) and it cannot connect to the mirror source), it is always
failed and report error：
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command
curthooks
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: Traceback (most
recent call last):
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/commands/main.py",
line 202, in main
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: ret =
args.func(args)
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 2224, in curthooks
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]:
builtin_curthooks(cfg, target, state)
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 2048, in builtin_curthooks
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]:
install_kernel(cfg, target)
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 393, in install_kernel
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]:
install(kernel_package)
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 369, in install
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]:
distro.install_packages([pkg], target=target, env=env)
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/distro.py", line 473,
in install_packages
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: return
install_cmd('install', args=pkglist, opts=opts, target=target,
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/distro.py", line 255,
in run_apt_command
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: cmd_rv =
apt_install(mode, args, opts=opts, env=env, target=target,
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/distro.py", line 303,
in apt_install
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: cmd_rv =
inchroot.subp(cmd + dl_opts + packages, env=env,
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/util.py", line 843,
in subp
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: return
subp(*args, **kwargs)
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/util.py", line 323,
in subp
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: return
_subp(*args, **kwargs)
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: File
"/snap/subiquity/5645/lib/python3.10/site-packages/curtin/util.py", line 172,
in _subp
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: raise
ProcessExecutionError(stdout=out, stderr=err,
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]:
curtin.util.ProcessExecutionError: Unexpected error while running command.
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: Command:
['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot',
'/target', 'apt-get', '--quiet', '--assume-yes',
'--option=Dpkg::options::=--force-unsafe-io',
'--option=Dpkg::Options::=--force-confold', 'install', '--download-only',
'linux-generic']
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: Exit code: 100
Apr 01 07:15:35 ubuntu-server subiquity_log.3119[4902]: Reason:
[Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
The content in the pulseaudio.log (#9) is not helpful. Could you edit /usr/lib/systemd/user/pulseaudio.service: change the line "ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal" to "ExecStart=/usr/bin/pulseaudio - --daemonize=no --log-target=file:/home/$user/pulse.txt" reboot connect your bt headset and try to change profile from A2DP to HSP/HFP, then upload the pulse.txt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051570 Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
About the issue of Redmi buds 4 active, what version of ubuntu are you using? If it is 22.04, you need to collect pulseaudio log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051570 Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
Tested the latest daily images at https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/. All types of disks are good working and pass the install test now. Request this fix patch add on next 24.04 ubuntu release. Thanks for support! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057996 Title: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme- stas,shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
Verification for jammy: Install the ubuntu jammy on the machine in question, enable proposed ppa, run sudo apt-get update, run sudo apt install linux-firmware, the inux-firmware/20230919.git3672ccab-0ubuntu2.10 is installed. reboot the machine, check dmesg, there is no "loading firmware failure" log, connect a bt headset (PLT_BBTGO2), the bt headset could pair, play sound and capture sound. Verification done on jammy. ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
Verification for mantic: Install the ubuntu mantic on the machine in question, enable proposed ppa, run sudo apt-get update, run sudo apt install linux-firmware, the linux-firmware/20230919.git3672ccab-0ubuntu2.10 is installed. reboot the machine, check dmesg, there is no "loading firmware failure" log, connect a bt headset (PLT_BBTGO2), the bt headset could pair, play sound and capture sound. Verification done on mantic. ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Please upload a complete dmesg with the kernel you updated on 19/03/2024 (dummy output). And could you also test the latest upstream mainline kernel or ubuntu 24.04 (just put the iso to usb flash drive, boot from it and try ubuntu 24.04, no need to install). https://kernel.ubuntu.com/mainline/v6.8/ And also, it looks like a hardware issue to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051570 Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051570] Re: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound
Hi aminesaka, About the #4, if you want to use the mic of bluetooth headset, please set output Configuration to HSP/HFP instead of A2DP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051570 Title: [Vostro 3400, Cirrus Logic CS8409/CS42L42, Speaker, Internal] Underruns, dropouts or crackling sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
** Description changed: - This is for tracking purpose. + [Impact] + In an oem project, we found the max playback volume of the headphone + is too high on 2 LG machines, it could bring harm to listeners. As + requested by OEM customer, we need to decrease the max volume. + + + [Fix] + Cherry-pick a mainline kernel patch, this could fix this issue. + + [Test] + Booting with the patched kernel, plug the headphone, set the playback + volue to max, run: + amixer -c1 contents | grep -n2 "Headphone Playback Volume" + + The value is 77,77 instead of 87,87 like below: + numid=1,iface=MIXER,name='Headphone Playback Volume' + ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 + : values=77,77 + + + [Where problems could occur] + This patch changes the amplifier's default value, probably + will make the audio malfunction, but this change is specific + to those 2 LG machines (by SSID), will not bring regression + to other machines. For those 2 machines, we already tested patch, + the audio worked well. ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
** Summary changed: - alsa/realtek: adjust headphone max output valume on 2 LG machines + alsa/realtek: adjust max output valume for headphone on 2 LG machines -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058573] [NEW] alsa/realtek: adjust headphone max output valume on 2 LG machines
Public bug reported: This is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: jinju oem-priority originate-from-2055127 ** Package changed: linux-oem-6.5 (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Tags added: jinju oem-priority originate-from-2055127 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058573 Title: alsa/realtek: adjust headphone max output valume on 2 LG machines To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
verification on Jammy: Enabled the jammy-propsed from "Software & Updates". ran 'sudo apt-get update; sudo apt install pulseaudio', the pulseaudio 1:15.99.1+dfsg1-1ubuntu2.2 was installed, reboot the system: non-audio bt devices (pairing, reconnect, functional test all pass): - piano2 (bt keyboard) - bluetooth laser travel mouse (logic bt mouse) audio bt devices (pairing, reconect, set a2dp and hsp/hfp, playback and capture, all test pass) - xt99 (lenovo thinkplus bt headset) - plt_btgo2 (bt headset) - soaiy s18 (bt sound bar) - i7mini (bt headset) Verification done for Jammy ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
verification on mantic: Install UBUNTU 23.10 on the Lenovo Thinkpad X1C 12Gen, and enable the mantic-propsed from "Software & Updates". By default, the pulseaudio is not installed, in the manic, the pipewire replaced the pulseaudio in the audio stack. I installed the pulseaudio manually by running 'sudo apt- get update; sudo apt install pulseaudio', the pulseaudio 1:16.1+dfsg1-2ubuntu4 was installed and pipewire-alsa was removed. Increased the priority to 510 for all packages in proposed by adding proposed-updates in the /etc/apt/preferences.d/, the upgraded the pulesaudio to 1:16.1+dfsg1-2ubuntu4.1: non-audio bt devices (pairing, reconnect, functional test all pass): - piano2 (bt keyboard) - bluetooth laser travel mouse (logic bt mouse) audio bt devices (pairing, reconect, set a2dp and hsp/hfp, playback and capture, all test pass) - xt99 (lenovo thinkplus bt headset) - plt_btgo2 (bt headset) - soaiy s18 (bt sound bar) - i7mini (bt headset) Verification done for mantic. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
Hi, Could you tell me when the fix will ready? And how we can get the fixed version? Our QA's test item is blocking on this issue, Will the fixed version be released in the next few days:)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057996 Title: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme- stas,shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
Analysis of autpkgtest failure for Mantic (about comment #16): 1) For libopenmpt/0.7.2-1 (i386), it is a building erorr which has nothing to do with pulesaudio: 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: /tmp/ccQalxLn.o: in function `main': 755s pattern-dump-c.c:(.text+0x458): undefined reference to `openmpt_error_func_default' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x461): undefined reference to `openmpt_log_func_default' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x473): undefined reference to `openmpt_module_create2' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x4be): undefined reference to `openmpt_module_get_num_orders' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x4f8): undefined reference to `openmpt_module_get_order_pattern' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x509): undefined reference to `openmpt_module_get_num_channels' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x544): undefined reference to `openmpt_module_get_pattern_row_channel_command' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x55f): undefined reference to `openmpt_module_get_pattern_row_channel_command' 755s /usr/lib/gcc-cross/i686-linux-gnu/13/../../../../i686-linux-gnu/bin/ld: pattern-dump-c.c:(.text+0x58e): undefined reference to `openmpt_module_destroy' 755s collect2: error: ld returned 1 exit status 2) For libsdl2/2.28.3+dfsg-2 (i386), it is a buliding error which has nothing to do with pusleaudio: 440s use-ttf.c:7:11: fatal error: SDL_ttf.h: No such file or directory 440s 7 | # include 440s | ^~~ 440s compilation terminated. 440s + rm -rf /tmp/tmp.CcXjR8RPS6 440s autopkgtest [21:27:55]: test deprecated-use: ---] 440s deprecated-use FAIL non-zero exit status 1 3) For pipewire/0.3.79-2 (i386), it is a buliding error which has nothing to do with pusleaudio: 1333s + i686-linux-gnu-gcc -otrivial trivial.c -lm 1333s trivial.c:1:10: fatal error: pipewire/pipewire.h: No such file or directory 1333s 1 | #include 1333s | ^ 1333s compilation terminated. 1333s autopkgtest [21:42:52]: test libpipewire-0.3-dev: ---] 1333s libpipewire-0.3-dev FAIL non-zero exit status 1 So in my opinion, these 3 failure have nothing to do with pulseaudio, probably we should hint them in the tests on i386 enviroment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
Analysis of autpkgtest failure for Jammy (about comment #15): 1) For libsdl2/2.0.20+dfsg-2ubuntu1.22.04.1 (i386), It is a building failure which has nothing to do with the pulseaudio: 275s + i686-linux-gnu-gcc -o use-pkg-config use-ttf.c 275s use-ttf.c:7:11: fatal error: SDL_ttf.h: No such file or directory 275s 7 | # include 275s | ^~~ 275s compilation terminated. 2) For pipewire/0.3.48-1ubuntu3 (i386), it is the gstreamer1.0-pipewire's issue, it doesn't have the plugin libgstpipewire.so: 1170s autopkgtest [21:40:06]: test gstreamer1.0-pipewire: [--- 1170s + export GST_INSPECT_NO_COLORS=1 1170s + export PAGER=cat 1170s + gst-inspect-1.0 pipewire 1170s No such element or plugin 'pipewire' 1170s autopkgtest [21:40:06]: test gstreamer1.0-pipewire: ---] So in my opinion, these 2 failure have nothing to do with pulseaudio, probably we should hint them in the tests on i386 enviroment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
Upload installer log ** Attachment added: "installer.tar.gz" https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057996/+attachment/5756189/+files/installer.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057996 Title: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme- stas,shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
Hi Olivier Gayot, Thanks for supporting this case. >>Could you share the content of the /var/log/installer directory? yes, i will provide this directory later. >>Looking at the journal, it looks like apt could not connect to the archive. >>Is the network connected to the Internet? What was the result of mirror >>testing? Network didn't connect to Internet, we use the default configuration install ubuntu os. When installing os, it indeed wants to connect to the network, but it is not possible to download successfully. We use the same method on other types of disk install same ubuntu version, it can be installed successfully. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057996 Title: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme- stas,shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
** Package changed: linux-hwe (Ubuntu) => subiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057996 Title: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme- stas,shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2057996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057996] Re: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
i add the journal log to attachment, and we also test another ubuntu version, ubuntu 22.04 can install successfully. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2057996/+attachment/5756122/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057996 Title: ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed,nvme-cli,nvme- stas,shim-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/2057996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057996] [NEW] ubuntu-24.04 version: cmd-curthooks/:Fail:Installing packages on target system:efibootmgr, grub-efi-amd64-signed, nvme-cli, nvme-stas, shim-signed
Public bug reported:
verison：ubuntu 24.04 subiquity version
OS:noble-live-server-amd64-0222.iso
CPU:AMD EPYC 9634 84-Core Processor*1
MEMORY: M321R2GA3BB6-CQKVG*2
ThinkSystem E1.S 5.9mm 7450 PRO 3.84TB Read Intensive NVMe PCIe 4.0 x4 HS SSD
UEFI MODE
lsb_release -rd: Description:Untun Noble Numbat(development branch)
Release: 24.04
What you expected to happen:
Install os on nvme,expected to install succefully.
What happened instead:
Install os on nvme, install always failed.
Before installation, we cleaned up all our nvme disk by dd if=/dev/zero
of=/dev/sda bs=1M count=5
The error log:
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: Installing packages on
target system: ['efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed',
'nvme-cli', 'nvme-stas', 'shim-signed']
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks/installing-missing-packages:
FAIL: installing missing packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: finish:
cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin command
curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Traceback (most
recent call last):
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/main.py",
line 202, in main
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: ret =
args.func(args)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1998, in curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
builtin_curthooks(cfg, target, state)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1803, in builtin_curthooks
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
install_missing_packages(cfg, target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/commands/curthooks.py",
line 1362, in install_missing_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
distro.install_packages(to_add, target=target, osfamily=osfamily)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 472,
in install_packages
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
install_cmd('install', args=pkglist, opts=opts, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 254,
in run_apt_command
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
apt_install(mode, args, opts=opts, env=env, target=target,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/distro.py", line 302,
in apt_install
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: cmd_rv =
inchroot.subp(cmd + dl_opts + packages, env=env,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 791,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 283,
in subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: return
_subp(*args, **kwargs)
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: File
"/snap/subiquity/5511/lib/python3.10/site-packages/curtin/util.py", line 147,
in _subp
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: raise
ProcessExecutionError(stdout=out, stderr=err,
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]:
curtin.util.ProcessExecutionError: Unexpected error while running command.
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Command:
['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'apt-get', '--quiet',
'--assume-yes', '--option=Dpkg::options::=--force-unsafe-io',
'--option=Dpkg::Options::=--force-confold', 'install', '--download-only',
'efibootmgr', 'grub-efi-amd64', 'grub-efi-amd64-signed', 'nvme-cli',
'nvme-stas', 'shim-signed']
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Exit code: 100
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Reason: -
Mar 15 03:03:05 ubuntu-server subiquity_log.4279[6373]: Stdout: ''
Mar 15 03:03:05 ubuntu-serv
[Bug 2056751] [NEW] Error compiling with glibc2.35 in Ubuntu22.04.3 LTS
Public bug reported: When compiling code on Ubuntu 22.04.3 LTS, a glibc2.35 error message appears as follows: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:110: error: macro "__fortified_attr_access" requires 3 arguments, but only 1 given The cause is an error with __fortified_attr_access at line 110 in string_fortified.h, which should be modified to: > @@ -107,7 +107,7 @@ __NTH (stpncpy (char *__dest, const char *__src, size_t > __n)) > # else > extern char *__stpncpy_chk (char *__dest, const char *__src, size_t __n, > size_t __destlen) __THROW > - __fortified_attr_access ((__write_only__, 1, 3)) > + __fortified_attr_access (__write_only__, 1, 3) > __attr_access ((__read_only__, 2)); > extern char *__REDIRECT_NTH (__stpncpy_alias, (char *__dest, const char > *__src, > size_t __n), stpncpy); It has been noted that this error has been corrected in newer versions of glibc. It is recommended to update to the latest version of glibc. ** Affects: glibc (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/2056751 Title: Error compiling with glibc2.35 in Ubuntu22.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2056751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily
hey Olivier Gayot, One further question, we are indeed using "user-data" automated installer methodology, so we can simply append it(i did notice the last line is version :1) with the following to our user-data file to work around this issue, right? debconf-selections: | grub-pc grub-efi/cloud_style_installation boolean false interactive-sections: ["*"] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055294 Title: /usr/lib/grub/grub-multi-install fails on noble-daily To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile
I applied the patch and built the binary for jammy and mantic in my ppa (https://launchpad.net/~hui.wang/+archive/ubuntu/pa-testing) I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my change only affects bluetooth audio devices, it will not bring any impact to non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices and 2 non-audio devices: BT audio devices (pairing, connection, re-connection, playback and capture all worked well): PLT_BBTGO2 (headset) Xiaomi Air3 SE (headset) Crusher Wireless (headset) SOAIY S18 (sound box) HK Soho Wireless (headset) Thinkplus XT99 (headset) Wl-1000X (headset) BT non-audio devices (pairing, connection, re-connection, key input all worked well): BT3.0 Keyboard The Pinao 2 keyboard ** Description changed: [Summary] When use the ThinkPluse xt99 bluetooth head set to run the test com.canonical.certification::bluetooth/audio_record_playback, it cannot record the sound and playback. It seems this device cannot switch to Hand free mode in this platform. [Steps to reproduce] Connect the ThinkPluse xt99, use the Handfree mode, then try to record some voice. [Expected result] The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound. [Actual result] The bluetooth headset xt99 cannot work in the Handfree mode. [Failure rate] 100% - [Impact] With the current Ubuntu 22.04 oem image, we try to connect the LENOVO XT99 bt headset and let it work in HFP mode, we select HFP profile from gnome sound-setting, but the microphone will not auto change to bt microphone and the bt output could not work too. So this BT headset could only work in A2DP mode with the current 22.04 OEM image. And we tried ubuntu 22.04 generic image, mantic image and noble image, none of them could make the headset work in HFP mode. - + [Fix] Cherry-pick a pulseaudio commit from upstream. [Test] - Install the patched pulseaudio and reboot, connect to the LENOVO XT99 - bt headset, select it to work in HFP mode, tested playback and capture, - all worked well. + I installed ubuntu 22.04 and 23.10 on 2 different Thinkpad laptops, then upgraded the pulseaudio from my ppa (ppa:hui.wang/pa-testing), in theory my change only affects bluetooth audio devices, it will not bring any impact to non-audio bluetooth devices, here I did the test with 7 bluetooth audio devices and 2 non-audio devices: + + BT audio devices (pairing, connection, re-connection, playback and capture all worked well): + PLT_BBTGO2 (headset) + Xiaomi Air3 SE (headset) + Crusher Wireless (headset) + SOAIY S18 (sound box) + HK Soho Wireless (headset) + Thinkplus XT99 (headset) + Wl-1000X (headset) + + BT non-audio devices (pairing, connection, re-connection, key input all worked well): + BT3.0 Keyboard + The Pinao 2 keyboard + [Where problems could occur] This change will impact bt headset negotiation process in the pulseaudio, so the possiblity of regression is limited to bt headset, it could make the bt headset fail to connect, but this possibility is very low, we tested the patch with different bt headset and bt speaker, all worked well. ** Changed in: pulseaudio (Ubuntu Mantic) Status: Incomplete => In Progress ** Changed in: pulseaudio (Ubuntu Jammy) Status: Incomplete => 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/2051895 Title: Lenovo XT99 BT headset can't work in HFP profile To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily
hey Olivier Gayot, The workaround you provided works like a charm, also thanks for the elaboration. I finally got Ubuntu 24.04 Beta installed successfully on my system. You are my lifesaver! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055294 Title: /usr/lib/grub/grub-multi-install fails on noble-daily To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily
Couple of questions: 1.sounds like this is a catastrophic issue that block fresh Ubuntu 24.04 Beta installation, isn't it? 2. so we have to wait for the new ISO image that includes the new grub2? If yes, when do we expect to get the new ISO image. Now we are doing some early evaluation work for Ubuntu 24.04 Beta with a tight schedule. It would be greatly helpful if there is a workaround. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055294 Title: /usr/lib/grub/grub-multi-install fails on noble-daily To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily
looks like i am hitting the exact same issue, may i know what can i do to get the Ubuntu 24.04 daily build installation to complete successfully instead of trying new ISO? Thanks a lot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055294 Title: /usr/lib/grub/grub-multi-install fails on noble-daily To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
