[Touch-packages] [Bug 2053289] Re: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1)
The solution listed here works for my case above: https://github.com/thesofproject/linux/issues/2460#issuecomment-779212719 ** Bug watch added: github.com/thesofproject/linux/issues #2460 https://github.com/thesofproject/linux/issues/2460 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2053289 Title: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1) Status in alsa-driver package in Ubuntu: New Bug description: I tried to record sound with my internal Mic. Nothing is working. I use arecord. ``` bagus:~$ arecord test.wav arecord: main:834: audio open error: Operation not supported bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM copy arecord: main:834: audio open error: No such file or directory bagus:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 bagus:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 bagus:~$ apt-cache policy alsa-base alsa-base: Installed: (none) Candidate: 1.0.25+dfsg-0ubuntu7 Version table: 1.0.25+dfsg-0ubuntu7 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2053289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all
** Bug watch added: github.com/PJungkamp/yoga9-linux/issues #11 https://github.com/PJungkamp/yoga9-linux/issues/11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to thornley.david from comment #819) > I am running an 14IRP8 (Yoga Pro/Slim 9i), specifically this model > (https://psref.lenovo.com/Detail/Yoga/Yoga_Pro_9_14IRP8?M=83BU0024AU). > > I have the laptop running Ubuntu 23.10 and I run mainline kernels from > Ubuntu. I have tried almost every recent kernel build up until 6.8-rc5 today > (I had read that 6.8 was supposed to fix this issue). Audio is still running > only the tweaters, zero bass. > > I've tried many things, notably the snd.conf (options > snd-sof-intel-hda-common hda_model=alc287-yoga9-bass-spk-pin) to no avail. > Also tried noble's firmware-sof-signed package, manually tweaking the amixer > configuration. > > My alsa info -> > https://alsa-project.org/db/?f=634d31445ad5a7c4a023cdb15a07dea2a4048437 > > Thanks!! Do you have full volume sound? I have a similar model (https://psref.lenovo.com/Detail/Lenovo/Lenovo_Slim_Pro_9_14IRP8?M=83BV0002US) and had to do a few things to make the amplifier work in the first place, but I still don't have any bass. To get sound on linux 6.7 I had to update the firmware files and use `options snd-sof-intel-hda-common hda_model=17aa:38be`, which had a different effect to alc287-yoga9-bass-spk-pin (not sure why). I described with more details at https://github.com/PJungkamp/yoga9-linux/issues/11#issuecomment-1899400594 I didn't try a lot on 6.8 but my current config doesn't fix the bass there too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
Could you share your acpidump output? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
I noticed that patch is present in the kernel I am running... "dmesg | grep 2781" yields nothing. "lsmod" indicates snd_hda_scodec_tas2781_i2c is loaded. I'm quite green with the audio subsystem in linux, so pretty overwhelmed and suprised how complicated it is :) I'm not 100% sure, but it sounds like there is firmware and associated tuning values present in the EFI system that are also required. One other thing I noticed, running "i2cdetect -r 3" doesn't report any probed addresses. -r 1 has one at 0x14, -r 2 has at 0x2c, less that I think expected based on other similar posts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
(In reply to thornley.david from comment #819) > I am running an 14IRP8 (Yoga Pro/Slim 9i), specifically this model > (https://psref.lenovo.com/Detail/Yoga/Yoga_Pro_9_14IRP8?M=83BU0024AU). Not sure what the cause of this is, but there is no specific mention of "14IRP8" in any of the kernel code, so I guess there is still no specific support for your issue, unfortunately. Possibly the fix would be as simple as the commit which fixed it for the 16IRH8 (just several lines of code https://github.com/torvalds/linux/commit/99af5b11c57d33c32d761797f6308b40936c22ed), but I don't know enough about any of this to say for sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
Based on alsa-info, its subsystem ID is: 0x17aa38be It's here in the patch_realtek.c: SND_PCI_QUIRK(0x17aa, 0x38be, "Yoga S980-14.5 proX YC Dual", ALC287_FIXUP_TAS2781_I2C), snd_hda_scodec_tas2781_i2c loaded. Could you run this as well? dmesg|grep 2781 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034298] Re: [82YU, Realtek ALC257, Mic, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2034298 Title: [82YU, Realtek ALC257, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Though playback works fine through inbuilt speakers, the inbuilt microphone in Ubuntu 22.04.3 installed in Lenovo V15 Gen4 AMN (AMD Ryzen 5 7520U with Radeon Graphics) laptop does not work. For now, the work is being managed by attaching an external headphohe set to listen to and record audio. Hence, please look into this matter and provide a solution.By the way, to confirm that there is defect the hardware, Windows Home was installed and microphone was found to be working absolutely fine there. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pradip 1503 F pulseaudio /dev/snd/controlC0: pradip 1503 F pulseaudio /dev/snd/controlC1: pradip 1503 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 00:24:21 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pradip 1503 F pulseaudio /dev/snd/controlC0: pradip 1503 F pulseaudio /dev/snd/controlC1: pradip 1503 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [82YU, Realtek ALC257, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2023 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: L1CN30WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V15 G4 AMN dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrL1CN30WW:bd04/27/2023:br1.30:efr1.30:svnLENOVO:pn82YU:pvrLenovoV15G4AMN:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoV15G4AMN:skuLENOVO_MT_82YU_BU_idea_FM_V15G4AMN: dmi.product.family: V15 G4 AMN dmi.product.name: 82YU dmi.product.sku: LENOVO_MT_82YU_BU_idea_FM_V15 G4 AMN dmi.product.version: Lenovo V15 G4 AMN dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2034298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2053289] Re: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1)
** Summary changed: - Internal microphone is not working in 24.04 (Fujitsu WU4/H1) + Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1) ** Tags added: alc257 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2053289 Title: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1) Status in alsa-driver package in Ubuntu: New Bug description: I tried to record sound with my internal Mic. Nothing is working. I use arecord. ``` bagus:~$ arecord test.wav arecord: main:834: audio open error: Operation not supported bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM copy arecord: main:834: audio open error: No such file or directory bagus:~$ arecord -l List of CAPTURE Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 bagus:~$ lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 bagus:~$ apt-cache policy alsa-base alsa-base: Installed: (none) Candidate: 1.0.25+dfsg-0ubuntu7 Version table: 1.0.25+dfsg-0ubuntu7 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2053289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054560] Re: Xorg freeze: i915 flips and commits are timing out
Next time the problem happens please: 1. Reboot. 2. Run: journalctl -b-1 > prevboot.txt 3. Attach the resulting text file here. ** Summary changed: - Xorg freeze + Xorg freeze: i915 flips and commits are timing out ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Changed in: linux-hwe-6.5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2054560 Title: Xorg freeze: i915 flips and commits are timing out Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Random freezes occur since the installation of 6.5.x kernel. Freeze occur several times a day, probably after touching the mouse or keyboard, but I'm not sure. App continue to work sound is OK, there is just no dispay updated. Booting to old 6.2 kernel solves the problem. I have tried all 6.5 updates since the first released, but each time, I had a freeze after a few hours. Example of last mesg in dmesg when freeze occur : Feb 21 11:03:59 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:04:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:53 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:06:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out or : Feb 13 10:37:18 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:22:09 pf46avw7 kernel: perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 Feb 13 11:35:00 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:35:31 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:36:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit
[Touch-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
Please use 'ubuntu-bug' to report each crash file so the robots can analyse and classify them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2053235] Re: Upgrade libwayland to 1.22.0
Same for Weston 13.0. But since it's Nvidia asking, maybe we can help some other way? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2053235 Title: Upgrade libwayland to 1.22.0 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Jammy: New Status in wayland source package in Mantic: Fix Released Status in wayland source package in Noble: Fix Released Bug description: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions
*** This bug is a duplicate of bug 2037015 *** https://bugs.launchpad.net/bugs/2037015 If it's just appeared in 22.04.4 then Mesa might be to blame, but this looks more likely: https://launchpad.net/ubuntu/+source/webkit2gtk/2.42.5-0ubuntu0.22.04.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2054517 Title: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions Status in mesa package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions. Assuming it doesn't crash first. You first see the corruption in the initial setup wizard on first boot of noble-preinstalled-desktop-arm64+raspi.img.xz but the same corruption is then visible in the Help app on Xorg. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.43.3-1 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu7 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Feb 21 14:38:56 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs
I have been running the test packages on AWS with the reproducer running for 20 days now, and they are still running great. The change to direct IO really does fix this issue, and my testing has removed any and all concerns of causing a regression. Previously focal wouldn't last more than 20 minutes, and jammy onward, a week. I will get these patches sponsored now. Sorry for the delay Krister. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2036467 Title: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs Status in cloud-images: New Status in e2fsprogs package in Ubuntu: In Progress Status in e2fsprogs source package in Trusty: Won't Fix Status in e2fsprogs source package in Xenial: Won't Fix Status in e2fsprogs source package in Bionic: Won't Fix Status in e2fsprogs source package in Focal: In Progress Status in e2fsprogs source package in Jammy: In Progress Status in e2fsprogs source package in Lunar: Won't Fix Status in e2fsprogs source package in Mantic: In Progress Bug description: [Impact] This is a long running bug plaguing cloud-images, where on a rare occasion resize2fs would fail and the image would not resize to fit the entire disk. Online resizes would fail due to a superblock checksum mismatch, where the superblock in memory differs from what is currently on disk due to changes made to the image. $ resize2fs /dev/nvme1n1p1 resize2fs 1.47.0 (5-Feb-2023) resize2fs: Superblock checksum does not match superblock while trying to open /dev/nvme1n1p1 Couldn't find valid filesystem superblock. Changing the read of the superblock to Direct I/O solves the issue. [Testcase] Start an c5.large instance on AWS, and attach a 60gb gp3 volume for use as a scratch disk. Run the following script, courtesy of Krister Johansen and his team: #!/usr/bin/bash set -euxo pipefail while true do parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s sleep .5 mkfs.ext4 /dev/nvme1n1p1 mount -t ext4 /dev/nvme1n1p1 /mnt stress-ng --temp-path /mnt -D 4 & STRESS_PID=$! sleep 1 growpart /dev/nvme1n1 1 resize2fs /dev/nvme1n1p1 kill $STRESS_PID wait $STRESS_PID umount /mnt wipefs -a /dev/nvme1n1p1 wipefs -a /dev/nvme1n1 done Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test If you install the test packages, the race no longer occurs. [Where problems could occur] We are changing how resize2fs reads the superblock from underlying disks. If a regression were to occur, resize2fs could fail to resize offline or online volumes. As all cloud-images are online resized during their initial boot, this could have a large impact to public and private clouds should a regression occur. [Other info] Upstream mailing list discussion: https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/ https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/ This was fixed in the below commit upstream: commit 43a498e938887956f393b5e45ea6ac79cc5f4b84 Author: Theodore Ts'o Date: Thu, 15 Jun 2023 00:17:01 -0400 Subject: resize2fs: use Direct I/O when reading the superblock for online resizes Link: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84 The commit has not been tagged to any release. All supported Ubuntu releases require this fix, and need to be published in standard non- ESM archives to be picked up in cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2036467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037015] Re: Screen corruption of slides during install on Raspberry Pi 4
Same issue in Yelp (the Help app) when in Xorg sessions. So I think this is a webkit2gtk bug that only manifests on Xorg (like our installer/live sessions). Also I have removed the series targets because they were getting cluttered and likely targeting the wrong package anyway. ** Also affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags added: noble ** No longer affects: ubiquity (Ubuntu Jammy) ** No longer affects: ubiquity (Ubuntu Mantic) ** No longer affects: ubiquity (Ubuntu Noble) ** No longer affects: webkit2gtk (Ubuntu Jammy) ** No longer affects: webkit2gtk (Ubuntu Mantic) ** No longer affects: webkit2gtk (Ubuntu Noble) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Changed in: webkit2gtk (Ubuntu) Status: New => Confirmed ** Tags added: raspi raspigfx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of slides during install on Raspberry Pi 4 Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions
*** This bug is a duplicate of bug 2037015 *** https://bugs.launchpad.net/bugs/2037015 ** This bug has been marked a duplicate of bug 2037015 Screen corruption of slides during install on Raspberry Pi 4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2054517 Title: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions Status in mesa package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions. Assuming it doesn't crash first. You first see the corruption in the initial setup wizard on first boot of noble-preinstalled-desktop-arm64+raspi.img.xz but the same corruption is then visible in the Help app on Xorg. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.43.3-1 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu7 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Feb 21 14:38:56 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found
Merge request opened at https://code.launchpad.net/~bluca/ubuntu/+source/lvm2/+git/lvm2/+merge/460984 ** Tags added: patch patch-accepted-upstream ** Merge proposal linked: https://code.launchpad.net/~bluca/ubuntu/+source/lvm2/+git/lvm2/+merge/460984 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: New Status in lvm2 source package in Noble: New Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054620] [NEW] libdm returns wrong error code when dm-verity key cannot be found
Public bug reported: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Affects: lvm2 (Ubuntu Noble) Importance: Undecided Status: New ** Tags: patch patch-accepted-upstream ** Also affects: lvm2 (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/2054620 Title: libdm returns wrong error code when dm-verity key cannot be found Status in lvm2 package in Ubuntu: New Status in lvm2 source package in Noble: New Bug description: When libcryptsetup tries to activate a signed dm-verity volume, and the key is not in the kernel keyring, libdevicemapper does not return the appropriate ENOKEY, so the failure cannot be distinguished from other generic issues. This is fixed in the lvm2 version 2.03.23 upstream release. Please consider backporting this patch for Noble. Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3 Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892225] Re: apport-gtk consumes 100% CPU for way too long after something crashes
Encountered this on `Ubuntu 22.04.3 LTS` as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1892225 Title: apport-gtk consumes 100% CPU for way too long after something crashes Status in apport package in Ubuntu: Confirmed Bug description: Something (related to Cinnamon) crashes, so the usual popup appears telling me that something crashed, and asking me whether I wanted to send a report. I choose Send. Every time this happens, then a process called apport-gtk starts consuming 100% CPU and it goes on for several minutes, so long that I end up killing it. There's no way there is a good reason for consuming so much CPU for so long. If you need to do such an amount of processing just to generate and send a bug report, something is deeply broken. But if the operation actually had to be that computationally expensive, then you must do it in a less intensive way so that it can go on in the background, for no matter how long, without rendering me unable to use my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: called for pid 2405, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: executable: /usr/bin/cinnamon (command line "cinnamon --replace") ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: debug: session gdbus call: (true,) ERROR: apport (pid 2908) Wed Aug 19 18:39:34 2020: wrote report /var/crash/_usr_bin_cinnamon.1000.crash ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 640:1000:110:69556:2020-08-19 18:39:33.732794284 +0200:2020-08-19 18:39:34.732794284 +0200:/var/crash/_usr_bin_cinnamon-launcher.1000.crash 640:1000:110:15432562:2020-08-19 18:39:34.466977487 +0200:2020-08-19 18:42:42.722667813 +0200:/var/crash/_usr_bin_cinnamon.1000.crash CurrentDesktop: X-Cinnamon Date: Wed Aug 19 18:42:34 2020 InstallationDate: Installed on 2013-10-11 (2503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-07-12 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1892225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054609] [NEW] package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1
Public bug reported: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: fips-updates jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2054609 Title: package ntp Jammy 1:4.2.8p15+dfsg-1ubuntu2 failed to install/upgrade: installed ntp package post-installation script subprocess returned error exit status 1 Status in ntp package in Ubuntu: New Bug description: ntp postinstall attempts to perform a MD5 sum, which is a no-no with FIPS. I have not encountered this bug on previous LTS versions of Ubuntu with FIPS. Description: Ubuntu 22.04.4 LTS Release: 22.04 ntp: Installed: 1:4.2.8p15+dfsg-1ubuntu2 Candidate: 1:4.2.8p15+dfsg-1ubuntu2 Version table: *** 1:4.2.8p15+dfsg-1ubuntu2 500 500 file:/home... 100 /var/libdpkg/status [Actions performed] I attempted to install ntp onto jammy 22.04.4 LTS with FIPS. $ sudo pro attach key-goes-here $ sudo pro enable fips-updates $ reboot --after reboot-- $ sudo apt update $ sudo apt install ntp [What you expected to happen] ntp tool installs prior to personal configuration, does not report anything in red [What happened instead] Job for ntp.service failed because the control process exited with error code. [...] Feb 21 15:53:32 user ntpd[35638]: MD5 init failed Feb 21 15:53:32 user ntpd[35632]: daemon child exited with code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/2054609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052739] Re: tzdata 2024a release
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu Mantic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Mantic: Confirmed Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052739] Re: tzdata 2024a release
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Mantic: Confirmed Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052739] Re: tzdata 2024a release
A few hours ago I uploaded the tzdata updates for the stable releases. They are waiting in the unapproved queue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Mantic: Confirmed Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054602] Re: update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan
*** This bug is a duplicate of bug 2052739 *** https://bugs.launchpad.net/bugs/2052739 Thank you for taking the time to report this bug and contributing to Ubuntu. A few hours ago I uploaded the tzdata updates for the stable releases. Hopefully tomorrow they will be accepted in the proposed pocket. See https://wiki.ubuntu.com/StableReleaseUpdates and bug #2052739. ** This bug has been marked a duplicate of bug 2052739 tzdata 2024a release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2054602 Title: update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan Status in tzdata package in Ubuntu: New Bug description: Please prioritize tzdata-2024a update for all supported Ubuntu versions. Among others, this update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan, which will happen 2024-03-01 at 00:00. Release information: https://mm.icann.org/pipermail/tz-announce/2024-February/81.html We need some time in advance to be prepared for changes and update systems before March To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2054602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052739] Re: tzdata 2024a release
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2052739 Title: tzdata 2024a release Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Mantic: Confirmed Bug description: [ Impact ] The 2024a release contains the following changes: * Kazakhstan unifies on UTC+5 beginning 2024-03-01. * Palestine springs forward a week later after Ramadan. * zic no longer pretends to support indefinite-past DST. * localtime no longer mishandles Ciudad Juárez in 2422. [ Test Plan ] Test cases were added to the autopkgtest to cover the testing: * python: test_2024a * python-icu: test_2024a (only for focal and newer) So the test plan is to check that the autopkgtest succeeds. [ Other Info ] The autopkgtest for chrony is flaky on jammy and newer (see bug #2002910). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This bug was fixed in the package plasma-welcome - 5.27.10-1ubuntu1 --- plasma-welcome (5.27.10-1ubuntu1) noble; urgency=low [ Ubuntu Merge-o-Matic ] * Merge from Debian unstable. Remaining changes: - Kubuntu Vcs and maintainer fields. [ Scarlett Moore ] * Add apparmor profile to fix userns. Ref: LP: #2046844 * Release to archive. plasma-welcome (5.27.10-1) unstable; urgency=medium [ Patrick Franz ] * New upstream release (5.27.10). -- Scarlett Moore Wed, 21 Feb 2024 04:23:15 -0700 ** Changed in: plasma-welcome (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: In Progress Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Committed Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: In Progress Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054171] Re: dhcpcd hook breaks when using libc6-prof's libc.so.6
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2054171 Title: dhcpcd hook breaks when using libc6-prof's libc.so.6 Status in initramfs-tools package in Ubuntu: Triaged Bug description: I have the libc6-prof package installed to provide a frame pointer enabled libc.so.6. I have a custom configuration file in /etc/ld.so.conf.d putting /lib/libc6-prof/x86_64-linux-gnu at the front of the dynamic linker search paths. (I really like having frame pointers!) This confuses the `multiarch_dir=$(ldd /usr/sbin/dhcpcd | sed -En 's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p')` line in /usr/share/initramfs- tools/hooks/dhcpcd because the libc.so.6 path is different. Default ldd output: ``` ldd /usr/sbin/dhcpcd linux-vdso.so.1 (0x7fff9a735000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7f50d280) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240) /lib64/ld-linux-x86-64.so.2 (0x7f50d2f27000) ``` My ldd output: ``` ldd /usr/sbin/dhcpcd linux-vdso.so.1 (0x7fff802db000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7fce87e0) libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 (0x7fce87a0) /lib64/ld-linux-x86-64.so.2 (0x7fce88514000) ``` ``` -libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240) +libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 (0x7fce87a0) ``` When running the modified search paths, `ldd /usr/sbin/dhcpcd | sed -En 's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p'` evaluates to an empty string and exits 0. This results in `copy_exec "/usr/lib//dhcpcd/dev/udev.so"`, which breaks that script. This in turn breaks initramfs. ``` Processing triggers for linux-image-6.5.0-17-generic (6.5.0-17.17) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.5.0-17-generic E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1. update-initramfs: failed for /boot/initrd.img-6.5.0-17-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-6.5.0-17-generic (--configure): installed linux-image-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.5.0-17-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ``` I can work around the issue by hacking up the dhcpcd hook or by modifying the dynamic link path search order, running `ldconfig`, then `update-initramfs -u`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2054171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982336] Re: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16)
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1982336 Title: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16) Status in Ubuntu on IBM z Systems: Fix Committed Status in gdb package in Ubuntu: Fix Committed Bug description: GDB Support for new IBM Z Hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
My personal thoughts are that the proposal is nothing if not carefully considered...! Lots of great discussion and input. There is plenty of opportunity for people to provide feedback on whether or how the change impacts them in ways we were unable to foresee. On Tue, Feb 20, 2024 at 11:31 PM Christian Ehrhardt < 1833...@bugs.launchpad.net> wrote: > While there was sadly neither enough time not enough resources to do all > the deep dive analysis that could have been done, we succeeded by > reaching out to many more parties and got their input as well. Thank you > all! > > Since Noble feature freeze is coming we need to make a call either way. > I proposed the underlying seed change [1]. > And even once accepted that has to be followed by an update to ubuntu-meta. > Furthermore we'd have more follow up, like enabling it in special cases > like the AWS images for the reasons Fabio mentioned. > > Of course this is just a proposal. There are many other options left, > from not changing anything to more subtle counters to my proposal like > only doing so in 24.10 to give things more time, to holding back until > someone found time/resource to gather more data. > > But for now, I feel "Not enabling it by default, but enabling > selectively where identified to be wanted" seems to be the better choice > - and that is what I proposed. > > [1]: https://code.launchpad.net/~paelzer/ubuntu- > seeds/+git/platform/+merge/460904 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1833322 > > Title: > Please consider no more having irqbalance enabled by default (per > image/use-case/TBD) > > Status in Ubuntu on IBM z Systems: > Confirmed > Status in irqbalance package in Ubuntu: > Confirmed > Status in ubuntu-meta package in Ubuntu: > Confirmed > > Bug description: > as per https://github.com/pop-os/default-settings/issues/60 > > Distribution (run cat /etc/os-release): > > $ cat /etc/os-release > NAME="Pop!_OS" > VERSION="19.04" > ID=ubuntu > ID_LIKE=debian > PRETTY_NAME="Pop!_OS 19.04" > VERSION_ID="19.04" > HOME_URL="https://system76.com/pop; > SUPPORT_URL="http://support.system76.com; > BUG_REPORT_URL="https://github.com/pop-os/pop/issues; > PRIVACY_POLICY_URL="https://system76.com/privacy; > VERSION_CODENAME=disco > UBUNTU_CODENAME=disco > > Related Application and/or Package Version (run apt policy $PACKAGE > NAME): > > $ apt policy irqbalance > irqbalance: > Installed: 1.5.0-3ubuntu1 > Candidate: 1.5.0-3ubuntu1 > Version table: > *** 1.5.0-3ubuntu1 500 > 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages > 100 /var/lib/dpkg/status > > $ apt rdepends irqbalance > irqbalance > Reverse Depends: > Recommends: ubuntu-standard > gce-compute-image-packages > > Issue/Bug Description: > > as per konkor/cpufreq#48 and > http://konkor.github.io/cpufreq/faq/#irqbalance-detected > > irqbalance is technically not needed on desktop systems (supposedly it > is mainly for servers), and may actually reduce performance and power > savings. It appears to provide benefits only to server environments > that have relatively-constant loading. If it is truly a server- > oriented package, then it shouldn't be installed by default on a > desktop/laptop system and shouldn't be included in desktop OS images. > > Steps to reproduce (if you know): > > This is potentially an issue with all default installs. > > Expected behavior: > > n/a > > Other Notes: > > I can safely remove it via "sudo apt purge irqbalance" without any > apparent adverse side-effects. If someone is running a situation where > they need it, then they always have the option of installing it from > the repositories. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance:
[Touch-packages] [Bug 2054602] [NEW] update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan
Public bug reported: Please prioritize tzdata-2024a update for all supported Ubuntu versions. Among others, this update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan, which will happen 2024-03-01 at 00:00. Release information: https://mm.icann.org/pipermail/tz-announce/2024-February/81.html We need some time in advance to be prepared for changes and update systems before March ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2054602 Title: update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan Status in tzdata package in Ubuntu: New Bug description: Please prioritize tzdata-2024a update for all supported Ubuntu versions. Among others, this update features UTC+6 to UTC+5 transition for all time zones in Kazakhstan, which will happen 2024-03-01 at 00:00. Release information: https://mm.icann.org/pipermail/tz-announce/2024-February/81.html We need some time in advance to be prepared for changes and update systems before March To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2054602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982336] Re: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16)
** Changed in: gdb (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1982336 Title: [24.04 FEAT] GDB: Support for new IBM Z Hardware (IBM z16) Status in Ubuntu on IBM z Systems: In Progress Status in gdb package in Ubuntu: Fix Committed Bug description: GDB Support for new IBM Z Hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046336] Re: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs
** Changed in: klibc (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/2046336 Title: initramfs-tools: After updating coreutils cp: not replacing in console when running update-initramfs Status in klibc package in Ubuntu: Fix Released Status in klibc package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/1055694: Package: initramfs-tools Version: 0.142 Severity: normal X-Debbugs-Cc: konomikit...@gmail.com Dear Maintainer, After updating coreutils from 9.1-1 to 9.4-1+b1 the following lines appear when running update-initramfs -u: cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cat' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/cpio' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dd' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/dmesg' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/false' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/gunzip' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/kill' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ln' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/ls' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkdir' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mkfifo' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mknod' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/mv' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/nuke' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/readlink' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/resume' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sh' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sleep' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/sync' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/true' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/umount' cp: not replacing '/var/tmp/mkinitramfs_vZS3YW/bin/uname' The lines seem to be a cosmetic issue only, but I cannot be entirely sure. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-3-amd64 -rw-r--r-- 1 root root 78M Nov 10 19:13 /boot/initrd.img-6.5.0-4-amd64 -- /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.5.0-4-amd64 root=UUID=e7b71052-3dff-454b-9730-7b146ebdf115 ro preempt=full quiet -- /proc/filesystems btrfs fuseblk vfat -- lsmod Module Size Used by tcp_diag 12288 0 inet_diag 28672 1 tcp_diag vboxnetadp 28672 0 vboxnetflt 40960 0 vboxdrv 716800 2 vboxnetadp,vboxnetflt nvme_fabrics 32768 0 ccm20480 9 rfcomm102400 16 snd_seq_dummy 12288 0 snd_hrtimer12288 1 snd_seq 114688 7 snd_seq_dummy qrtr 57344 4 cmac 12288 3 algif_hash 12288 1 algif_skcipher 12288 1 af_alg 36864 6 algif_hash,algif_skcipher bnep 36864 2 zstd 12288 12 zram 40960 2 zsmalloc 36864 1 zram btusb 81920 0 btrtl 28672 1 btusb btbcm 24576 1 btusb intel_rapl_msr 20480 0 btintel57344 1 btusb intel_rapl_common 36864 1 intel_rapl_msr btmtk 12288 1 btusb binfmt_misc28672 1 bluetooth1126400 44 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm edac_mce_amd 40960 0 kvm_amd 184320 0 iwlmvm589824 0 kvm 1359872 1 kvm_amd mac80211 1392640 1 iwlmvm sha3_generic 16384 1 jitterentropy_rng 20480 1 snd_hda_codec_realtek 192512 1 irqbypass 12288 1 kvm snd_hda_codec_generic 114688 1 snd_hda_codec_realtek ledtrig_audio 12288 1 snd_hda_codec_generic snd_hda_codec_hdmi 90112 1 libarc412288 1 mac80211 ghash_clmulni_intel16384 0 sha512_ssse3 53248 1 snd_hda_intel 61440 4 sha512_generic 16384 1 sha512_ssse3 snd_usb_audio 417792 3 ctr12288 3 snd_intel_dspcfg 32768 1 snd_hda_intel snd_usbmidi_lib49152 1 snd_usb_audio snd_intel_sdw_acpi 16384 1 snd_intel_dspcfg drbg 49152 1 snd_rawmidi53248 1 snd_usbmidi_lib aesni_intel 360448 10 ansi_cprng 12288 0 iwlwifi 544768 1 iwlmvm snd_hda_codec 225280 4
[Touch-packages] [Bug 2054574] Re: Bash completion
Ok. I have found the issue The bash-completion package is missing on that ubuntu node. Once that file is copied from a working server, it started working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2054574 Title: Bash completion Status in lxc package in Ubuntu: New Bug description: Hi, We have ubuntu 20.04 . We have installed lxc-utils as shown below: --- # dpkg-query -W lxc-utils lxc-utils 1:4.0.12-0ubuntu1~20.04.1 But when we try to use bash completion for lxc-attach commands, it is not working or prompting the list of containers. How to fix this ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2054574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054171] Re: dhcpcd hook breaks when using libc6-prof's libc.so.6
Thank you for taking the time to report this bug and contributing to Ubuntu. That is a well prepared bug report. Attached a proposed patch to fix it. Can you have a look and test it? ** Patch added: "0001-Fix-determing-multiarch-dir-when-using-libc6-prof-s-.patch" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2054171/+attachment/5748235/+files/0001-Fix-determing-multiarch-dir-when-using-libc6-prof-s-.patch ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2054171 Title: dhcpcd hook breaks when using libc6-prof's libc.so.6 Status in initramfs-tools package in Ubuntu: Triaged Bug description: I have the libc6-prof package installed to provide a frame pointer enabled libc.so.6. I have a custom configuration file in /etc/ld.so.conf.d putting /lib/libc6-prof/x86_64-linux-gnu at the front of the dynamic linker search paths. (I really like having frame pointers!) This confuses the `multiarch_dir=$(ldd /usr/sbin/dhcpcd | sed -En 's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p')` line in /usr/share/initramfs- tools/hooks/dhcpcd because the libc.so.6 path is different. Default ldd output: ``` ldd /usr/sbin/dhcpcd linux-vdso.so.1 (0x7fff9a735000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7f50d280) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240) /lib64/ld-linux-x86-64.so.2 (0x7f50d2f27000) ``` My ldd output: ``` ldd /usr/sbin/dhcpcd linux-vdso.so.1 (0x7fff802db000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7fce87e0) libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 (0x7fce87a0) /lib64/ld-linux-x86-64.so.2 (0x7fce88514000) ``` ``` -libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f50d240) +libc.so.6 => /lib/libc6-prof/x86_64-linux-gnu/libc.so.6 (0x7fce87a0) ``` When running the modified search paths, `ldd /usr/sbin/dhcpcd | sed -En 's;^.*/lib/([^/]+)/libc\.so\..*$;\1;p'` evaluates to an empty string and exits 0. This results in `copy_exec "/usr/lib//dhcpcd/dev/udev.so"`, which breaks that script. This in turn breaks initramfs. ``` Processing triggers for linux-image-6.5.0-17-generic (6.5.0-17.17) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-6.5.0-17-generic E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1. update-initramfs: failed for /boot/initrd.img-6.5.0-17-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-6.5.0-17-generic (--configure): installed linux-image-6.5.0-17-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.5.0-17-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ``` I can work around the issue by hacking up the dhcpcd hook or by modifying the dynamic link path search order, running `ldconfig`, then `update-initramfs -u`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2054171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2047268] Re: package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-boot package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Mantic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2047268 Title: package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-boot package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Mantic: Confirmed Bug description: package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-boot package post-installation script subprocess returned error exit status 1 upgraded stuff through sudo ap-get and it gave me this error, i was also copying music and browsing the web at the time ProblemType: Package DistroRelease: Ubuntu 23.10 Package: systemd-boot 253.5-1ubuntu6.1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Fri Dec 22 15:58:01 2023 DuplicateSignature: package:systemd-boot:253.5-1ubuntu6.1 Setting up systemd-boot (253.5-1ubuntu6.1) ... dpkg: error processing package systemd-boot (--configure): installed systemd-boot package post-installation script subprocess returned error exit status 1 ErrorMessage: installed systemd-boot package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-12-20 (2 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: systemd Title: package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-boot package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions
This may be a duplicate of LP: #2037015 -- we saw this on mantic first, then noble, in the oem-config process (the first-time setup wizard). Previously it *didn't* affect jammy, but I'm currently running through the ISO tests for the jammy .4 release and it's cropped up there now as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2054517 Title: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions Status in mesa package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions. Assuming it doesn't crash first. You first see the corruption in the initial setup wizard on first boot of noble-preinstalled-desktop-arm64+raspi.img.xz but the same corruption is then visible in the Help app on Xorg. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.43.3-1 ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3 Uname: Linux 6.5.0-1005-raspi aarch64 ApportVersion: 2.27.0-0ubuntu7 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Feb 21 14:38:56 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2053235] Re: Upgrade libwayland to 1.22.0
I have doubts this will happen, as that's a new major upstream version and doesn't really fit the stable release update rules. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2053235 Title: Upgrade libwayland to 1.22.0 Status in wayland package in Ubuntu: Fix Released Status in wayland source package in Jammy: New Status in wayland source package in Mantic: Fix Released Status in wayland source package in Noble: Fix Released Bug description: We look to use / upgrade to Weston 13.0 on Ubuntu 22.04.3 LTS. We see the following Weston-13.0 dependencies are not met for the same. libwayland*: required version >= 1.22.0 So we request to upgrade these packages on Ubuntu 22.04.3 LTS. The release of Ubuntu we are using: - Ubuntu 22.04.3 LTS Current version of the libwayland* packages: - libwayland-bin/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-client0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-cursor0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-dev/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-egl1/now 1.20.0-1ubuntu0.1 arm64 [installed,local] - libwayland-server0/now 1.20.0-1ubuntu0.1 arm64 [installed,local] What we expect to happen: - We want the upgrade of libwayland* packages to 1.22.0 on Ubuntu 22.04.3 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2053235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable
I tested the flock-based solution with some of the CPC pipelines in jammy and saw consistently clean builds (30 successful images built yesterday). Thank you very much for everyone's hard work debugging and fixing this race condition! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in linux source package in Jammy: New Status in livecd-rootfs source package in Jammy: Fix Released Status in util-linux source package in Jammy: New Status in linux source package in Mantic: New Status in livecd-rootfs source package in Mantic: New Status in util-linux source package in Mantic: New Status in linux source package in Noble: New Status in livecd-rootfs source package in Noble: Fix Released Status in util-linux source package in Noble: New Bug description: [impact] In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race-free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. The losetup usage has been backported to Jammy, and sees frequent failures there. [test case] The autopkgtests will provide enough confidence that the changes are not completely broken. Whether the change helps with the races on riscv can be "tested in prod" just as well as any other way. [regression potential] If the backport has been done incorrectly, image builds can fail (and the autopkgtests will fail if it has been completely bungled). This can be quickly handled. There is no foreseeable way for this to result in successful builds but broken images, which would be a much more difficult failure mode to unpick. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054574] [NEW] Bash completion
Public bug reported: Hi, We have ubuntu 20.04 . We have installed lxc-utils as shown below: --- # dpkg-query -W lxc-utils lxc-utils 1:4.0.12-0ubuntu1~20.04.1 But when we try to use bash completion for lxc-attach commands, it is not working or prompting the list of containers. How to fix this ? ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/2054574 Title: Bash completion Status in lxc package in Ubuntu: New Bug description: Hi, We have ubuntu 20.04 . We have installed lxc-utils as shown below: --- # dpkg-query -W lxc-utils lxc-utils 1:4.0.12-0ubuntu1~20.04.1 But when we try to use bash completion for lxc-attach commands, it is not working or prompting the list of containers. How to fix this ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2054574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054319] Re: System installed from jammy point release iso cannot upgrade to noble
** Also affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Also affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/2054319 Title: System installed from jammy point release iso cannot upgrade to noble Status in gnome-shell package in Ubuntu: New Status in policykit-1 package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: We have different crashes being encountered. In our auto-upgrade- testing, we see gnome-shell crash, however, when testing locally, I didn't experience this. @hyask did experience the gnome-shell crash though. When running an upgrade from jammy to noble in a virsh vm, about halfway through the upgrade process my gui dies. I then ran the upgrade from a console, to which it revealed that just the gui dies - the upgrade process, for me, continues and then laterally fails. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu7 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash 600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 14:34:19.370597600 +:/var/crash/polkitd.0.crash Date: Mon Feb 19 14:53:39 2024 InstallationDate: Installed on 2024-02-19 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 127: pkexec must be setuid root VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Description changed: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. + [ Workaround ] + + On most machines you can hide the problem by using these kernel parameters together: + quiet splash loglevel=2 fastboot + [ Test Plan ] - 1. Boot Ubuntu on a number of laptops that have the problem and verify - no console text messages appear during boot. - - 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them - still. - - 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages - should appear. + 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. + 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. + 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2054560] [NEW] Xorg freeze
Public bug reported: Random freezes occur since the installation of 6.5.x kernel. Freeze occur several times a day, probably after touching the mouse or keyboard, but I'm not sure. App continue to work sound is OK, there is just no dispay updated. Booting to old 6.2 kernel solves the problem. I have tried all 6.5 updates since the first released, but each time, I had a freeze after a few hours. Example of last mesg in dmesg when freeze occur : Feb 21 11:03:59 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:04:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:04:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:05:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:05:53 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:03 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 21 11:06:13 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:274:DP-5] commit wait timed out Feb 21 11:06:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out or : Feb 13 10:37:18 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 10:39:06 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:22:09 pf46avw7 kernel: perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 Feb 13 11:35:00 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:10 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:21 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:35:31 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:41 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:35:51 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:36:01 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:12 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:36:22 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CONNECTOR:282:DP-5] commit wait timed out Feb 13 11:36:32 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 13 11:37:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 13 11:37:42 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out or Feb 01 09:37:11 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] flip_done timed out Feb 01 09:37:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* flip_done timed out Feb 01 09:37:23 pf46avw7 kernel: i915 :00:02.0: [drm] *ERROR* [CRTC:131:pipe B] commit wait timed out Feb 01 09:37:45 pf46avw7 kernel: rfkill: input handler enabled Feb 01 09:37:55 pf46avw7 kernel: i915 :00:02.0: [drm]
[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
** Description changed: + [ Impact ] + + Kernel (and systemd) log messages appear during boot for many machines, + when the user should be seeing only the BIOS logo and/or Plymouth splash + screens. + + [ Test Plan ] + + 1. Boot Ubuntu on a number of laptops that have the problem and verify + no console text messages appear during boot. + + 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them + still. + + 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages + should appear. + + [ Where problems could occur ] + + Since the fix works by deferring fbcon's takeover of the console, the + main problem encountered during its development was the inability to VT + switch. + + [ Original Description ] + Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2052982] Re: regression in debconf-copydb when writing to stdout
This bug was fixed in the package debconf - 1.5.86 --- debconf (1.5.86) unstable; urgency=medium * Fix stdin/stdout handling regression in Debconf::DbDriver::Pipe (thanks, Dan Bungert; closes: #1063817, LP: #2052982). -- Colin Watson Tue, 13 Feb 2024 09:35:03 + ** Changed in: debconf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/2052982 Title: regression in debconf-copydb when writing to stdout Status in debconf package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Invalid Status in debconf package in Debian: Fix Released Bug description: While debugging a FTBFS in Ubiquity, I observed that the usage of debconf-copydb regressed when using version 1.5.85 of debconf. The previous-in-ubuntu version 1.5.82 of debconf was OK. That invocation looks roughly like: debconf-copydb templatedb pipe --config=Name:pipe --config=Driver:Pipe --config=InFd:none ... Bisecting debconf from there found commit 5db857ade00953496bfdb7edb884296bebc41885: "Avoid two-argument open" Further tracing found the following change to Debconf/DbDriver/Pipe.pm around line 120: - open ($fh, '>-'); + open ($fh, '>', \*STDOUT); An additional symptom of this problem is GLOB files with names that look like: GLOB(0x0123456789ab) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/2052982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051420] Re: Error in dash(1) manual in <& and >& descriptions
** Package changed: boinc (Ubuntu) => dash (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2051420 Title: Error in dash(1) manual in <& and >& descriptions Status in dash package in Ubuntu: New Bug description: $ man dash | grep '[<>]' [n1]Copy file descriptor n2 as stdin (or fd n1). fd n2. The text looks mangled with orphaned "fd n2" not making any sense. The text has stdout and stdin confused/swapped. dash.1 says "stdout" for <& - compare: NetBSD sh.1 says [n1]<& n2 Redirect standard input (or n1) from a duplicate of file descriptor n2. OpenGroup text says: 2.7.5 Duplicating an Input File Descriptor The redirection operator: [n]< shall duplicate one input file descriptor from another, or shall close one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2051420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051420] [NEW] Error in dash(1) manual in <& and >& descriptions
You have been subscribed to a public bug: $ man dash | grep '[<>]' [n1]Copy file descriptor n2 as stdin (or fd n1). fd n2. The text looks mangled with orphaned "fd n2" not making any sense. The text has stdout and stdin confused/swapped. dash.1 says "stdout" for <& - compare: NetBSD sh.1 says [n1]<& n2 Redirect standard input (or n1) from a duplicate of file descriptor n2. OpenGroup text says: 2.7.5 Duplicating an Input File Descriptor The redirection operator: [n]< shall duplicate one input file descriptor from another, or shall close one. ** Affects: dash (Ubuntu) Importance: Undecided Status: New -- Error in dash(1) manual in <& and >& descriptions https://bugs.launchpad.net/bugs/2051420 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
