[Touch-packages] [Bug 2048914] Re: System program problem detected at every login Xubuntu Update Notifier
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2048914/+attachment/5738098/+files/apport.log shows thermald having crashed. If you disable the thermald service with `sudo systemctl disable thermald; sudo systemctl stop thermald` does the problem persist after the next couple of logins? ** Changed in: whoopsie (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2048914 Title: System program problem detected at every login Xubuntu Update Notifier Status in update-notifier package in Ubuntu: New Status in whoopsie package in Ubuntu: Incomplete Bug description: Every time I log in to my new installation of Xubuntu 24.04 (daily ISO) after a reboot, I get an error message that says, "System program problem detected." Clicking either Cancel or Report Problem only dismisses the pop-up without any further action. This has occurred on multiple computers. This began with the first boot after installation and occurs at each subsequent reboot upon logging in. Logging out and back in does not cause the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: update-notifier 3.192.66 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Jan 10 09:57:25 2024 ExecutablePath: /usr/bin/update-notifier InstallationDate: Installed on 2024-01-10 (0 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240110) ProcEnviron: LANG=C.UTF-8 LANGUAGE=en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2048914/+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 2040011] Proposed package upload rejected
An upload of vim to lunar-proposed has been rejected from the upload queue for the following reason: "lunar EOL in 9 days; no more SRUs". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2040011 Title: [SRU] Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Released Status in vim source package in Focal: In Progress Status in vim source package in Jammy: In Progress Status in vim source package in Lunar: Won't Fix Status in vim source package in Mantic: In Progress Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+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 2040011] Re: [SRU] Ensure supported codenames are accurate
lunar EOLs in 7 days. Not accepting any more SRUs. ** Changed in: vim (Ubuntu Lunar) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/2040011 Title: [SRU] Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Released Status in vim source package in Focal: In Progress Status in vim source package in Jammy: In Progress Status in vim source package in Lunar: Won't Fix Status in vim source package in Mantic: In Progress Bug description: In several stable releases of Ubuntu, Vim has information regarding releases that are outdated. It would be optimal for Vim to grab this data from distro-info-data (or similar), but unfortunately that is not the case. Therefore, the list needs to be updated. There is a minimal regression potential here; Vim simply reads a statically-set Perl array to determine if the release in the changelog and sources.list is supported or not. Any regression would present itself in external tooling that detects text highlighting, which is not a case I think we support in Ubuntu. A simple way to test this update is to download a package from the Lunar archive, and open the changelog with Vim. Instead of the changelog release (e.g. "noble") showing as red, it should show as blue. I would also suggest editing sources.list, to ensure e.g. Eoan shows as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+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 2048914] Re: System program problem detected at every login Xubuntu Update Notifier
** Also affects: whoopsie (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/2048914 Title: System program problem detected at every login Xubuntu Update Notifier Status in update-notifier package in Ubuntu: New Status in whoopsie package in Ubuntu: New Bug description: Every time I log in to my new installation of Xubuntu 24.04 (daily ISO) after a reboot, I get an error message that says, "System program problem detected." Clicking either Cancel or Report Problem only dismisses the pop-up without any further action. This has occurred on multiple computers. This began with the first boot after installation and occurs at each subsequent reboot upon logging in. Logging out and back in does not cause the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: update-notifier 3.192.66 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Jan 10 09:57:25 2024 ExecutablePath: /usr/bin/update-notifier InstallationDate: Installed on 2024-01-10 (0 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240110) ProcEnviron: LANG=C.UTF-8 LANGUAGE=en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/2048914/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
** Tags added: rls-nn-incoming -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2043915] Re: Booting into live session results in try/install page white screen
** Changed in: ubuntu-desktop-installer Importance: Undecided => Unknown -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2049555] [NEW] [SOF - sof-bytcht rt5640, playback] fails after a while
Public bug reported: Playing music or watching videos for couple minutes, like on Youtube. Sound will be cracked with long beep. And player will be stopped. But if I reload the page, sound will be resumed again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 16 22:44:25 2024 InstallationDate: Installed on 2024-01-14 (1 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller - Intel HDMI/DP LPE Audio Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [SOF - sof-bytcht rt5640, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Gummi CHT dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd11/20/2015:br1.10:svnAcer:pnAspireSW3-016P:pvrV1.10:rvnAcer:rnGummiCHT:rvrV1.10:cvnAcer:ct9:cvrChassisVersion:skuAspireSwitch10E_106E_1.10: dmi.product.family: CHT-CR dmi.product.name: Aspire SW3-016P dmi.product.sku: Aspire Switch 10 E_106E_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2049555 Title: [SOF - sof-bytcht rt5640, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Playing music or watching videos for couple minutes, like on Youtube. Sound will be cracked with long beep. And player will be stopped. But if I reload the page, sound will be resumed again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 16 22:44:25 2024 InstallationDate: Installed on 2024-01-14 (1 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller - Intel HDMI/DP LPE Audio Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [SOF - sof-bytcht rt5640, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Gummi CHT dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd11/20/2015:br1.10:svnAcer:pnAspireSW3-016P:pvrV1.10:rvnAcer:rnGummiCHT:rvrV1.10:cvnAcer:ct9:cvrChassisVersion:skuAspireSwitch10E_106E_1.10: dmi.product.family: CHT-CR dmi.product.name: Aspire SW3-016P dmi.product.sku: Aspire Switch 10 E_106E_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2049555/+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 2049552] [NEW] [noble] ftbfs with new zlib 1.3
Public bug reported:
The zlib detection code seems faulty:
checking for possibly buggy zlib... yes
configure: error: *** zlib too old - check config.log ***
Your reported zlib version has known security problems. It's possible your
vendor has fixed these problems without changing the version number. If you
are sure this is the case, you can disable the check by running
"./configure --without-zlib-version-check".
If you are in doubt, upgrade zlib to version 1.2.3 or greater.
See http://www.gzip.org/zlib/ for details.
| #include
| #include
| #include
|
| int
| main (void)
| {
|
| int a=0, b=0, c=0, d=0, n, v;
| n = sscanf(ZLIB_VERSION, "%d.%d.%d.%d", , , , );
| if (n != 3 && n != 4)
| exit(1);
| v = a*100 + b*1 + c*100 + d;
| fprintf(stderr, "found zlib version %s (%d)\n", ZLIB_VERSION, v);
|
| /* 1.1.4 is OK */
| if (a == 1 && b == 1 && c >= 4)
| exit(0);
|
| /* 1.2.3 and up are OK */
| if (v >= 1020300)
| exit(0);
|
| exit(2);
|
| ;
| return 0;
| }
Upstream bug report: https://bugzilla.mindrot.org/show_bug.cgi?id=3604
Upstream fix (untested): https://github.com/openssh/openssh-
portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621
** Affects: openssh (Ubuntu)
Importance: High
Status: Triaged
** Tags: bitesize ftbfs server-todo
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Description changed:
The zlib detection code seems faulty:
checking for possibly buggy zlib... yes
configure: error: *** zlib too old - check config.log ***
Your reported zlib version has known security problems. It's possible your
vendor has fixed these problems without changing the version number. If you
are sure this is the case, you can disable the check by running
"./configure --without-zlib-version-check".
If you are in doubt, upgrade zlib to version 1.2.3 or greater.
See http://www.gzip.org/zlib/ for details.
| #include
| #include
| #include
|
| int
| main (void)
| {
|
| int a=0, b=0, c=0, d=0, n, v;
| n = sscanf(ZLIB_VERSION, "%d.%d.%d.%d", , , , );
| if (n != 3 && n != 4)
| exit(1);
| v = a*100 + b*1 + c*100 + d;
| fprintf(stderr, "found zlib version %s (%d)\n", ZLIB_VERSION, v);
|
| /* 1.1.4 is OK */
| if (a == 1 && b == 1 && c >= 4)
| exit(0);
|
| /* 1.2.3 and up are OK */
| if (v >= 1020300)
| exit(0);
|
| exit(2);
|
| ;
| return 0;
| }
+ Upstream bug report: https://bugzilla.mindrot.org/show_bug.cgi?id=3604
- Upstream fix (untested):
https://github.com/openssh/openssh-portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621
+ Upstream fix (untested): https://github.com/openssh/openssh-
+ portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621
** Summary changed:
- noble ftbfs with new zlib 1.3
+ [noble] ftbfs with new zlib 1.3
** Tags added: bitesize
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2049552
Title:
[noble] ftbfs with new zlib 1.3
Status in openssh package in Ubuntu:
Triaged
Bug description:
The zlib detection code seems faulty:
checking for possibly buggy zlib... yes
configure: error: *** zlib too old - check config.log ***
Your reported zlib version has known security problems. It's possible your
vendor has fixed these problems without changing the version number. If you
are sure this is the case, you can disable the check by running
"./configure --without-zlib-version-check".
If you are in doubt, upgrade zlib to version 1.2.3 or greater.
See http://www.gzip.org/zlib/ for details.
| #include
| #include
| #include
|
| int
| main (void)
| {
|
| int a=0, b=0, c=0, d=0, n, v;
| n = sscanf(ZLIB_VERSION, "%d.%d.%d.%d", , , , );
| if (n != 3 && n != 4)
| exit(1);
| v = a*100 + b*1 + c*100 + d;
| fprintf(stderr, "found zlib version %s (%d)\n", ZLIB_VERSION, v);
|
| /* 1.1.4 is OK */
| if (a == 1 && b == 1 && c >= 4)
| exit(0);
|
| /* 1.2.3 and up are OK */
| if (v >= 1020300)
| exit(0);
|
| exit(2);
|
| ;
| return 0;
| }
Upstream bug report: https://bugzilla.mindrot.org/show_bug.cgi?id=3604
Upstream fix (untested): https://github.com/openssh/openssh-
portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2049552/+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 2049318] Re: [SRU] free(): double free detected in tcache 2
Modified debdiff attached which is now cherry-picked from upstream and dep3 headers added. Also added a simple test plan based on the upstream testcase. ** Description changed: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] + 1. Simple test plan based on upstream test case: + + sudo nft -f - < rules.txt + - sudo iptables-save > rules.txt * Convert the rule to nftables ruleset - - sudo iptables-nft-restore < rules.txt + - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - - sudo nft list ruleset + - sudo nft list ruleset * Also confirm that iptables can list the old rule - - sudo iptables -L + - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
** Attachment added: "0.142ubuntu11.log" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+attachment/5740004/+files/0.142ubuntu11.log -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
** Attachment added: "0.142ubuntu19.log" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+attachment/5740005/+files/0.142ubuntu19.log -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
** Attachment added: "0.142ubuntu10.log" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+attachment/5740003/+files/0.142ubuntu10.log -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2049540] [NEW] hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11
Public bug reported: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Sample container builder to generate a list of kernel modules" https://bugs.launchpad.net/bugs/2049540/+attachment/5740002/+files/testcase.tar -- 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/2049540 Title: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11 Status in initramfs-tools package in Ubuntu: New Bug description: When analyzing the kernel modules present in the current initrd, I have found that there are hundreds of such differences, and that this started with the move to dracut. I believe that the move to dracut was intended to be relatively module neutral - see LP: #2031841 and LP: #2042710 for more details on that. I'm attaching here a test case based on podman, where different versions of the initramfs-tools package are installed, and then the list of modules present in the initrd is analyzed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2046488] Re: test-execute fails on arhmf because of exec-basic.service
I think this is actually due to the recent AppArmor change too; exec- basic.service has PrivateTmp=yes which implies PrivateUsers=yes for user managers. -- 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/2046488 Title: test-execute fails on arhmf because of exec-basic.service Status in systemd package in Ubuntu: New Bug description: This was observed during a PPA autopkgtest[1] while prepping v255 for Ubuntu. Here is the relevant part from that log: 2158s [31mFAIL: test-execute[0m 2158s Bus n/a: changing state UNSET → OPENING 2158s sd-bus: starting bus by connecting to /run/dbus/system_bus_socket... 2158s Bus n/a: changing state OPENING → AUTHENTICATING 2158s Bus n/a: changing state AUTHENTICATING → HELLO 2158s Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a 2158s Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a 2158s Got message type=method_return sender=org.freedesktop.DBus destination=:1.18 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a 2158s Bus n/a: changing state HELLO → RUNNING 2158s Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=StartTransientUnit cookie=3 reply_cookie=0 signature=ssa(sv)a(sa(sv)) error-name=n/a error-message=n/a 2158s Got message type=method_return sender=:1.2 destination=:1.18 path=n/a interface=n/a member=n/a cookie=1667 reply_cookie=3 signature=o error-name=n/a error-message=n/a 2158s Got message type=signal sender=org.freedesktop.DBus destination=:1.18 path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 signature=s error-name=n/a error-message=n/a 2158s Got message type=method_return sender=org.freedesktop.DBus destination=:1.18 path=n/a interface=n/a member=n/a cookie=3 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a 2158s Match type='signal',sender='org.freedesktop.systemd1',path='/org/freedesktop/systemd1',interface='org.freedesktop.systemd1.Manager',member='JobRemoved' successfully installed. 2158s Got message type=signal sender=:1.2 destination=n/a path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=1674 reply_cookie=0 signature=uoss error-name=n/a error-message=n/a 2158s Got result done/Success for job test-execute-28edb5b6cd3eae1c.scope 2158s Bus n/a: changing state RUNNING → CLOSED 2158s Found cgroup2 on /sys/fs/cgroup/unified, unified hierarchy for systemd controller 2158s /* test_run_tests_unprivileged */ 2158s Successfully forked off '(test-execute-unprivileged)' as PID 1662. 2158s PR_SET_MM_ARG_START failed: Operation not permitted 2158s Changing mount flags / (MS_RDONLY|MS_REMOUNT|MS_BIND "")... 2158s Changing mount propagation / (MS_REC|MS_SHARED "") 2158s Mounting tmpfs (tmpfs) on /run/test-execute-unit-dir (MS_NOSUID|MS_NODEV "")... 2158s Reading /usr/lib/systemd/tests/unit-tests/systemd-runtest.env failed: No such file or directory 2158s Mounting tmpfs (tmpfs) on /dev/shm (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /root (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /tmp (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /var/tmp (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /var/lib (MS_NOSUID|MS_NODEV "")... 2158s Mounting tmpfs (tmpfs) on /run/credstore (MS_NOSUID|MS_NODEV "mode=")... 2158s Mounting tmpfs (tmpfs) on /run/credstore.encrypted (MS_NOSUID|MS_NODEV "mode=")... 2158s Found cgroup2 on /sys/fs/cgroup/unified, unified hierarchy for systemd controller 2158s Unified cgroup hierarchy is located at /sys/fs/cgroup/unified/system.slice/test-execute-28edb5b6cd3eae1c.scope/b8fc9c86c5b12c35. Controllers are on legacy hierarchies. 2158s bpf-firewall: Can't load kernel CGROUP SKB BPF program, BPF firewalling is not supported: Operation not permitted 2158s Can't load kernel CGROUP DEVICE BPF program, BPF device control is not supported: Operation not permitted 2158s Controller 'cpu' supported: yes 2158s Controller 'cpuacct' supported: yes 2158s Controller 'cpuset' supported: no 2158s Controller 'io' supported: no 2158s Controller 'blkio' supported: yes 2158s Controller 'memory' supported: yes 2158s Controller 'devices' supported: yes 2158s Controller 'pids' supported: yes 2158s Controller 'bpf-firewall' supported: no 2158s Controller
[Touch-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
** Changed in: ubuntu-desktop-installer Importance: Unknown => Undecided ** Changed in: ubuntu-desktop-installer Status: New => Fix Released -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2049352] Re: Package BlueZ 5.72 for Noble
** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: Fix Committed Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2049529] [NEW] Extra ZFS-related log line with `useradd -m -R /path`
Public bug reported: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? >From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/2049529 Title: Extra ZFS-related log line with `useradd -m -R /path` Status in shadow package in Ubuntu: New Bug description: Hi, I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the rabbit hole led me here. Here is a very quick reproducer, first: Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine: ``` $ cd /tmp $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img ``` Now in the VM: ``` $ sudo apt install -y mmdebstrap $ mmdebstrap noble /tmp/rootfs [...] $ sudo useradd --create-home --root /tmp/rootfs user1 can't open /dev/null: No such file or directory ``` The line `can't open /dev/null: No such file or directory` is printed on `stderr`, and that's unexpected by the part of the code I was debugging in the first place. Digging a bit led me to that line that does the printing: https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69 There seem to me that there are multiple issues with that patch: * Why try to call `zsysctl` in every case without first checking that it would be relevant: ZFS is not even installed on the VM we just created, less alone it has any ZFS volume/pool/whatever. * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist unless mapped, and `useradd` is perfectly aware of that, because it even does the `chroot` call itself! But why even try to mess with ZFS in the `chroot` case in the first place? From what history @brian-murray told me, this patch was part of some ZFS experimentation in the past. Maybe that experimentation is now finished, and that patch could be dropped? At the very least it needs improvements, imho. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2049529/+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 2049352] Re: Package BlueZ 5.72 for Noble
This was missing a build dependency on python3-pygments (which is in Main), I added it. Testing well with my Beats Flex, YouTube Music with the Firefox Nightly snap. I can adjust the latency offset with no issue, and blueman DTRT with connecting and disconnecting. Popped open journalctl and syslog, no errors presented on either front. As usual, here are the Lintian flags raised (that I don't plan on blocking on, but you should at least be aware of.) Regardless, great work, thank you! W: bluez source: illegal-runtime-test-name bluez_response [debian/tests/control:1] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:11] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:14] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:21] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:25] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:28] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:31] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [postinst:5] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:16] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:22] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:25] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:32] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:39] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:43] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:46] W: bluez: maintainer-script-should-not-use-dpkg-maintscript-helper "dpkg-maintscript-helper" [preinst:49] W: bluez-test-tools: no-manual-page [usr/bin/hfp] W: bluez-test-tools: no-manual-page [usr/bin/ioctl-tester] W: bluez-test-tools: no-manual-page [usr/bin/iso-tester] W: bluez-test-tools: no-manual-page [usr/bin/mesh-tester] W: bluez source: superfluous-file-pattern obexd/plugins/messages-tracker.c [debian/copyright:632] W: bluez source: superfluous-file-pattern obexd/plugins/syncevolution.c [debian/copyright:511] W: bluez: systemd-service-file-refers-to-unusual-wantedby-target bluetooth.target [usr/lib/systemd/system/bluetooth.service] W: bluez-meshd: systemd-service-file-refers-to-unusual-wantedby-target bluetooth.target [usr/lib/systemd/system/bluetooth-mesh.service] W: bluez: unusual-interpreter /usr/bin/python [usr/share/apport/package-hooks/source_bluez.py] I: bluez source: adopted-extended-field (in section for source) XSBC-Original-Maintainer [debian/control:3]
[Touch-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
I used build 20240116 today and was able to install normally. Thank you all! -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2049318] Re: [SRU] free(): double free detected in tcache 2
Hi and thanks for working at this SRU. I have some comments on the debdiff: - Please specify the patch Author in the DEP-3 headers. See [1] for more info on the header format. - The patch description should not be "apply upstream patch", because the patch is just the patch, it contains no information on where/how it's applied. It is fine (actually: good) to use the original commit message as the patch description. A multi-line description is OK, again see [1]. - I see you dropped a tests which was present in the original patch. If the test works fine on Jammy, let's keep it. If the test doesn't work on Jammy, please explain why in the patch Description header. - Please call the patch file something like 0002-nft-cache-avoid-double- free-of-unrecognized-base-chains.patch to follow the naming style used by other patches. If the added upstream test (0004extra-base_0) allows the easy verification that this fix works, it would be nice to have that in the SRU test plan. [1] https://dep-team.pages.debian.net/deps/dep3/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: Confirmed Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] * Add an iptables rule. - sudo iptables -A OUTPUT -p tcp --dport -j REJECT * save the rules in a file - sudo iptables-save > rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Since the discussion is no more only covering Desktop I updated the title (thanks Seb128 for suggesting) ** Summary changed: - Consider removing irqbalance from default install on desktop images + Please consider no more having irqbalance enabled by default (per image/use-case/TBD) -- 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: 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 -- 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 2045033] Re: Merge rsyslog 8.2312.0-2 from Debian
Merge request resubmitted: https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/458718 ** Changed in: rsyslog (Ubuntu) Assignee: Heinrich Schuchardt (xypron) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2045033 Title: Merge rsyslog 8.2312.0-2 from Debian Status in Rsyslog: Unknown Status in rsyslog package in Ubuntu: In Progress Bug description: Debian has released rsyslog 8.2310.0-4. Merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/rsyslog/+bug/2045033/+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 2049244] Re: linuxx64.efi.stub missing on Ubuntu 23.10 installation
This is shipped in the systemd-boot-efi package. Please install that. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/2049244 Title: linuxx64.efi.stub missing on Ubuntu 23.10 installation Status in systemd package in Ubuntu: Invalid Bug description: I installed Ubuntu 23.10 server and converted it to UKI boot, but in the process of doing so I discovered that /usr/lib/systemd/boot/efi/linuxx64.efi.stub is for some reason missing on this installation even though it was supposed to come with systemd. I checked two Ubuntu 22.04 installations (desktop and server) and the file is present on both. For now I copied the file from one of those systems for my purposes as a workaround, but I believe it is a bug that the file is missing in the first place and should be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049244/+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 2049433] Re: [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6
I see the crash happening on the following kernels, so that seems unlikely: 5.15.0 -89-generic #99~20.04.1-Ubuntu SMP Thu Nov 2 15:16:47 UTC 2023 x86_64 38.41% 5.15.0 -91-generic #101~20.04.1-Ubuntu SMP Thu Nov 16 14:22:28 UTC 2023 x86_64 21.38% 5.11.0 -37-generic #41~20.04.2-Ubuntu SMP Fri Sep 24 09:06:38 UTC 2021 x86_64 10.51% 5.13.0 -30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 7.25% 5.15.0 -46-lowlatency #49~20.04.1-Ubuntu SMP PREEMPT Mon Aug 8 11:51:19 UTC 2022 x86_64 5.43% 5.15.0 -76-generic #83~20.04.1-Ubuntu SMP Wed Jun 21 20:23:31 UTC 2023 x86_64 5.07% 5.15.0 -88-generic #98~20.04.1-Ubuntu SMP Mon Oct 9 16:43:45 UTC 2023 x86_64 3.26% 5.14.21 -150500 #1 SMP PREEMPT_DYNAMIC Wed Oct 4 16:52:05 UTC 2023 (5dc23e0) x86_64 2.17% ... But thank you for the info, at least we can rule out a change in mesa having broken things. We can perhaps close this bug then, at least until I can investigate further what the root cause is. If any RADV user is reading this and has a repro step, please comment on http://crbug.com/1508940 -- 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/2049433 Title: [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6 Status in mesa package in Ubuntu: New Bug description: Hi, Chrome/ANGLE developer here. We've started observing crashes on Ubuntu 20.04.6 in libvulkan_radeon.so since December 5, 2023. So far, all crashes seem to come from that specific Ubuntu version, and with RADV 21.2.6. Speaking with a mesa RADV developer, that version hasn't had an update since Nov 2021. While there's always a chance that an update in ANGLE has hit a bug, the timing does not work out (Chrome Beta has been fine since November 1, but the crashes started happening on Dec 5). Has there been an update to this driver around Dec 5, 2023 in Ubuntu specifically? I'm wondering if there has been a (security) update done by the Ubuntu team that upstream mesa may not be aware of. I can't find a public history of updates to ubuntu packages (with associated dates), is it possible to look at / provide that info and see what happened around Dec 5? Additional context is crbug.com/1508940, but I'm afraid not much is visible publicly. The crash stack is nonsense unfortunately. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2049433/+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 2031229] Re: [ProArt Studiobook H7604JV_H7604JV, Realtek ALC294, Speaker, Internal] No sound at all
As of Linux kernel 6.7 sounds works. No patch needed! Marked as "fixed" as this has been fixed by the afromentioned kernel version. Not an Ubuntu specific issue anyway. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Committed -- 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/2031229 Title: [ProArt Studiobook H7604JV_H7604JV, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Bug description: No sound on clean install. Sound works through jack and bluetooth. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 2360 F pulseaudio /dev/snd/pcmC0D0p: mblack 2360 F...m pulseaudio /dev/snd/controlC1: mblack 2360 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 12 21:45:33 2023 InstallationDate: Installed on 2023-08-13 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 2360 F pulseaudio /dev/snd/pcmC0D0p: mblack 2360 F...m pulseaudio /dev/snd/controlC1: mblack 2360 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [ProArt Studiobook H7604JV_H7604JV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: H7604JV.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: H7604JV dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrH7604JV.203:bd02/08/2023:br5.27:svnASUSTeKCOMPUTERINC.:pnProArtStudiobookH7604JV_H7604JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnH7604JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ProArt Studiobook dmi.product.name: ProArt Studiobook H7604JV_H7604JV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2031229/+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 2049318] Re: [SRU] free(): double free detected in tcache 2
Yes, but Standard Support for Lunar is going to end in 9 days and I don't think there is enough time to fix it in Lunar now as it has to go via sponsors queue and then to SRU queue and then it need to be in lunar-proposed for atleast 7 days before it can reach lunar-updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/2049318 Title: [SRU] free(): double free detected in tcache 2 Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Jammy: Confirmed Bug description: [ Impact ] iptables is unable to list the iptables rules or save the iptables rules if a nftables ruleset is defined which iptables does not recognize. [ Test Plan ] * Add an iptables rule. - sudo iptables -A OUTPUT -p tcp --dport -j REJECT * save the rules in a file - sudo iptables-save > rules.txt * Convert the rule to nftables ruleset - sudo iptables-nft-restore < rules.txt * List the nftables ruleset - sudo nft list ruleset * Also confirm that iptables can list the old rule - sudo iptables -L * Now add another nftables rule (this rule is taken from upstream test case) sudo nft -f -
[Touch-packages] [Bug 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later
I’m unsure this is the right way but adding linux package as this was also caused by kernel upgrade. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2049234 Title: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101=1dcafa2582f335f0d929f3e9e736775a95271c43 https://bugs.launchpad.net/bugs/2029401 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049234/+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 2043915] Re: Booting into live session results in try/install page white screen
Thanks, yes any failure to install now needs a separate bug report. -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2043915] Re: Booting into live session results in try/install page white screen
Today install from ISO dated 24-01-16 created a working system despite install ends with "install failed" see bugs 2049491,2049495 (I tried 2 times) -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2043915] Re: Booting into live session results in try/install page white screen
@vanvugt just tested in gnome-boxes on a Dell XPS laptop and it works as it should now again :) -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2049433] Re: [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6
it might've been a kernel update that triggers it, mesa hasn't changed. -- 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/2049433 Title: [radeon] Chrome crashes in RADV 21.2.6 on Ubuntu 20.04.6 Status in mesa package in Ubuntu: New Bug description: Hi, Chrome/ANGLE developer here. We've started observing crashes on Ubuntu 20.04.6 in libvulkan_radeon.so since December 5, 2023. So far, all crashes seem to come from that specific Ubuntu version, and with RADV 21.2.6. Speaking with a mesa RADV developer, that version hasn't had an update since Nov 2021. While there's always a chance that an update in ANGLE has hit a bug, the timing does not work out (Chrome Beta has been fine since November 1, but the crashes started happening on Dec 5). Has there been an update to this driver around Dec 5, 2023 in Ubuntu specifically? I'm wondering if there has been a (security) update done by the Ubuntu team that upstream mesa may not be aware of. I can't find a public history of updates to ubuntu packages (with associated dates), is it possible to look at / provide that info and see what happened around Dec 5? Additional context is crbug.com/1508940, but I'm afraid not much is visible publicly. The crash stack is nonsense unfortunately. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2049433/+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 2049352] Re: Package BlueZ 5.72 for Noble
** Attachment added: "bluez_5.72-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739878/+files/bluez_5.72-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: In Progress Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2049352] Re: Package BlueZ 5.72 for Noble
** Patch added: "bluez_5.72-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739879/+files/bluez_5.72-0ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: In Progress Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2049352] Re: Package BlueZ 5.72 for Noble
** Attachment added: "bluez_5.72.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+attachment/5739877/+files/bluez_5.72.orig.tar.xz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: In Progress Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+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 2043915] Re: Booting into live session results in try/install page white screen
Confirmed fix released in https://cdimage.ubuntu.com/daily- live/20240116/ -- 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/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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
