[Touch-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
** Also affects: libnl3 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libnl3 (Ubuntu) Status: New => Fix Released ** Also affects: libnl3 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libnl3 (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Focal: New Status in libnl3 source package in Jammy: Invalid Bug description: [ Impact ] When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly. After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is identified as the root cause. According to the commit, the "NLA_F_NESTED" flag should be set for kernel later than 5.2. [ Test Plan ] Verify with the updated version, the WIFI module can: 1. scan WIFI networks 2. connect to an available network 3. access to the connected network [ Where problems could occur ] 1. kernel versions without NLA_F_NESTED flag defined This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have it). It would not be a problem for an older kernel to understand/work with this change. Since the GA kernel is 5.4, so a generic image would still work. 2. Drivers don't use the NESTED flag. According to hui.wang's input, this change should not affect drivers which don't use the NESTED flag. But, it'd be better to cover more Wifi modules. [ Other Info ] 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+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 772024] Re: tzdata update keeps changing my timezone
This bug was fixed in the package tzdata - 2022g-2ubuntu1 --- tzdata (2022g-2ubuntu1) lunar; urgency=medium * Merge with Debian unstable. Remaining changes: - Ship ICU 2022g timezone data files which are utilized by PHP - Do not rename NEWS into changelog.gz, this fixes a build failure on moment-timezone.js - Point Vcs-Browser/Git to Launchpad tzdata (2022g-2) unstable; urgency=medium [ Benjamin Drung ] * Update Czech debconf translation. Thanks to Miroslav Kuře (Closes: #1027862) * Update Korean debconf translation. Thanks to Changwoo Ryu (Closes: #1027983) * d/tzdata.config: Update Mideast/Riyadh8[789] to Asia/Riyadh * Address shellcheck complaints in postinst and tzdata.config * d/tzdata.config: Rename Pacific/Enderbury to Pacific/Kanton * Replace obsolete two-level American timezones by three-level timezones * Translate area "America" as "Americas" in English (Closes: #508118, LP: #599466) [ Aurelien Jarno ] * Update Spanish debconf translation. Thanks to Jonatan Porras * Update Polish debconf translation. Thanks to Łukasz Dulny * Update French debconf translation. Thanks to Baptiste Jammet * Update Hebrew debconf translation. Thanks to Omer Zak * Update Swedish debconf translation. Thanks to Luna Jernberg * Drop wrong conversion of the Pacific/Enderbury timezone [ Benjamin Drung ] * d/rules: Exclude obsolete Uzhgorod and Zaporozhye from debconf * Generate debconf templates with Python * Drop obsolete tzconfig command (use "dpkg-reconfigure tzdata" instead) * Do not update US/* timezones to their America/* counterparts (Closes: #688318, LP: #772024) * Fix German translation of "Indian" to "Indischer Ozean" -- Benjamin Drung Tue, 10 Jan 2023 23:50:27 +0100 ** Changed in: tzdata (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 tzdata in Ubuntu. https://bugs.launchpad.net/bugs/772024 Title: tzdata update keeps changing my timezone Status in tzdata package in Ubuntu: Fix Released Status in tzdata package in Debian: New Bug description: Binary package hint: tzdata Other than the fact that Chicago, Illinois is in US Central Timezone, I have no relationship to Chicago. I am not in Chicago. I do not want to be in Chicago. I am in the Central Timezone. I am physically closer to other cities mentioned in tzdata. Selecting America/Chicago versus US/Central is not easier for me nor is it more intuitive. I understand that the upstream tzdata package goes a long way in documenting all of the weirdness associated with timezones and different localities' treatment of timezones and daylight "savings" time. However, from an end-user perspective, the distribution should place no special importance or preference on one timezone specification or another. Likewise, if a user chooses a timezone, the system should never change it. To reproduce the issue: # Manually select US/Central me@ubuntu:~$ sudo dpkg-reconfigure tzdata [sudo] password for me: Current default time zone: 'US/Central' Local time is now: Wed Apr 27 16:05:02 CDT 2011. Universal Time is now: Wed Apr 27 21:05:02 UTC 2011. # Validation that selection was accepted me@ubuntu:~$ cat /etc/timezone US/Central me@ubuntu:~$ md5sum /etc/localtime /usr/share/zoneinfo/US/Central 6540624294b1193e22ed7a15692f2de7 /etc/localtime 6540624294b1193e22ed7a15692f2de7 /usr/share/zoneinfo/US/Central me@ubuntu:~$ debconf-show tzdata debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied tzdata/Zones/Australia: * tzdata/Zones/US: Central tzdata/Zones/Asia: * tzdata/Zones/Etc: UTC tzdata/Zones/SystemV: tzdata/Zones/Arctic: tzdata/Zones/Pacific: tzdata/Zones/Antarctica: tzdata/Zones/Europe: tzdata/Zones/Africa: * tzdata/Zones/America: Chicago * tzdata/Areas: US tzdata/Zones/Atlantic: tzdata/Zones/Indian: # Force the package to reinstall me@ubuntu:~$ aptitude reinstall tzdata The following packages will be REINSTALLED: tzdata 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/658 kB of archives. After unpacking 0 B will be used. Preconfiguring packages ... (Reading database ... 168356 files and directories currently installed.) Preparing to replace tzdata 2011g-0ubuntu0.11.04 (using .../tzdata_2011g-0ubuntu0.11.04_all.deb) ... Unpacking replacement tzdata ... Setting up tzdata (2011g-0ubuntu0.11.04) ... Current default time zone: 'America/Chicago' Local time is now: Wed Apr 27 16:05:22 CDT 2011. Universal Time is now: Wed Apr 27 21:05:22 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. # Now previous indicators are reset to
[Touch-packages] [Bug 599466] Re: tzdata refers to Americas as "America"
This bug was fixed in the package tzdata - 2022g-2ubuntu1 --- tzdata (2022g-2ubuntu1) lunar; urgency=medium * Merge with Debian unstable. Remaining changes: - Ship ICU 2022g timezone data files which are utilized by PHP - Do not rename NEWS into changelog.gz, this fixes a build failure on moment-timezone.js - Point Vcs-Browser/Git to Launchpad tzdata (2022g-2) unstable; urgency=medium [ Benjamin Drung ] * Update Czech debconf translation. Thanks to Miroslav Kuře (Closes: #1027862) * Update Korean debconf translation. Thanks to Changwoo Ryu (Closes: #1027983) * d/tzdata.config: Update Mideast/Riyadh8[789] to Asia/Riyadh * Address shellcheck complaints in postinst and tzdata.config * d/tzdata.config: Rename Pacific/Enderbury to Pacific/Kanton * Replace obsolete two-level American timezones by three-level timezones * Translate area "America" as "Americas" in English (Closes: #508118, LP: #599466) [ Aurelien Jarno ] * Update Spanish debconf translation. Thanks to Jonatan Porras * Update Polish debconf translation. Thanks to Łukasz Dulny * Update French debconf translation. Thanks to Baptiste Jammet * Update Hebrew debconf translation. Thanks to Omer Zak * Update Swedish debconf translation. Thanks to Luna Jernberg * Drop wrong conversion of the Pacific/Enderbury timezone [ Benjamin Drung ] * d/rules: Exclude obsolete Uzhgorod and Zaporozhye from debconf * Generate debconf templates with Python * Drop obsolete tzconfig command (use "dpkg-reconfigure tzdata" instead) * Do not update US/* timezones to their America/* counterparts (Closes: #688318, LP: #772024) * Fix German translation of "Indian" to "Indischer Ozean" -- Benjamin Drung Tue, 10 Jan 2023 23:50:27 +0100 ** Changed in: tzdata (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 tzdata in Ubuntu. https://bugs.launchpad.net/bugs/599466 Title: tzdata refers to Americas as "America" Status in tzdata package in Ubuntu: Fix Released Status in tzdata package in Debian: Fix Released Bug description: Binary package hint: tzdata The time zone configuration scripts refer to the Americas as "America". To view this bug, enter "dpkg-reconfigure tzdata". The first page displayed asks you to choose your geographic area, and shows a list that starts with: Africa America ... I'm using Ubuntu 10.04 server. $ lsb_release -rd Description: Ubuntu 10.04 LTS Release: 10.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/599466/+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 1985887] Re: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s)
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1985887 Title: systemd kills gnome-shell or gnome-terminal if gnome-terminal uses much memory (50% over 20s) Status in OEM Priority Project: Invalid Status in systemd package in Ubuntu: Expired Bug description: [Steps to reproduce] 0. Install Jammy image 1. open gnome terminal 2. issue stress_ng or Canonical certification tool checkbox as "checkbox-cli run com.canonical.certification::memory/memory_stress_ng" or "stress-ng --stack 0 --timeout 300" 3. Terminal or Gnome-shell will be killed by systemd-oomd It's because all stressors are under same cgroup belongs to terminal. Both Wayland and Xorg can reproduce. over ssh and in multi-user.target work good. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985887/+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 1798400]
Noticed that among the many tips of the day, LibO also suggests to use Android or IPhone to remotely control an Impress presentation. The "more info" page then excplicitly declares that the feature is cross platform "GNU/Linux, Windows or macOS." either via Bluetooth or Wifi. However to use the feature with bluetooth on linux has been impossible for the last 5 years, because the feature is broken on this platform (this bug provides a diagnosis of the underlying issue). Using the feature with wifi is equally problematic, because those places where you need to deliver a presentation are typically those very places where you do not control the wifi network that may make it impossible for the computer and the phone to communicate. As a consequence, this tip of the day looks inappropriate on linux, making many users waste a significant amount of time trying to use a feature that simply cannot work. May I suggest removing this tip of the day on linux? -- 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/1798400 Title: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: Confirmed Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1996087] Re: Ensure supported codenames are accurate
This bug was fixed in the package vim - 2:8.1.2269-1ubuntu5.11 --- vim (2:8.1.2269-1ubuntu5.11) focal-security; urgency=medium * SECURITY UPDATE: illegal memory access with bracketed paste in Ex mode - debian/patches/CVE-2022-0392.patch: reverse space for the trailing NUL - CVE-2022-0392 * SECURITY UPDATE: retab may cause illegal memory access - debian/patches/CVE-2022-0417.patch: limit the value of tabstop - CVE-2022-0417 -- Mark Esler Wed, 11 Jan 2023 17:54:11 -0600 ** Changed in: vim (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1996087 Title: Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Committed Status in vim source package in Focal: Fix Released Status in vim source package in Jammy: Fix Released Status in vim source package in Kinetic: Fix Committed Status in vim source package in Lunar: Fix Committed 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. "lunar") 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/1996087/+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 1996087] Re: Ensure supported codenames are accurate
This bug was fixed in the package vim - 2:8.2.3995-1ubuntu2.3 --- vim (2:8.2.3995-1ubuntu2.3) jammy-security; urgency=medium * SECURITY UPDATE: illegal memory access with bracketed paste in Ex mode - debian/patches/CVE-2022-0392.patch: reverse space for the trailing NUL - CVE-2022-0392 * SECURITY UPDATE: retab may cause illegal memory access - debian/patches/CVE-2022-0417.patch: limit the value of tabstop - CVE-2022-0417 -- Mark Esler Wed, 11 Jan 2023 17:53:12 -0600 ** Changed in: vim (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0392 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0417 -- 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/1996087 Title: Ensure supported codenames are accurate Status in vim package in Ubuntu: Fix Committed Status in vim source package in Focal: Fix Committed Status in vim source package in Jammy: Fix Released Status in vim source package in Kinetic: Fix Committed Status in vim source package in Lunar: Fix Committed 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. "lunar") 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/1996087/+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 2002691] [NEW] package linux-image-generic-hwe-22.04 5.19.0.29.26 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: j ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-image-generic-hwe-22.04 5.19.0.29.26 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pafleury 3252 F wireplumber /dev/snd/controlC2: pafleury 3252 F wireplumber /dev/snd/controlC1: pafleury 3252 F wireplumber /dev/snd/seq:pafleury 3249 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jan 12 20:13:39 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2023-01-06 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s0no wireless extensions. enxb04f13f51dd2 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=UUID=c85917c3-d792-4a15-8eb4-df2aa2266795 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-generic-hwe-22.04 5.19.0.29.26 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4408 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4408:bd10/27/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic -- 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/2002691 Title: package linux-image-generic-hwe-22.04 5.19.0.29.26 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in initramfs-tools package in Ubuntu: New Bug description: j ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-image-generic-hwe-22.04 5.19.0.29.26 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pafleury 3252 F wireplumber /dev/snd/controlC2: pafleury 3252 F wireplumber /dev/snd/controlC1: pafleury 3252 F wireplumber /dev/snd/seq:pafleury 3249 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jan 12 20:13:39 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2023-01-06 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s0no wireless extensions. enxb04f13f51dd2 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=UUID=c85917c3-d792-4a15-8eb4-df2aa2266795 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-generic-hwe-22.04 5.19.0.29.26 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4408 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string
[Touch-packages] [Bug 2002690] [NEW] package linux-generic-hwe-22.04 5.19.0.29.26 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: kjl ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-generic-hwe-22.04 5.19.0.29.26 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pafleury 3252 F wireplumber /dev/snd/controlC2: pafleury 3252 F wireplumber /dev/snd/controlC1: pafleury 3252 F wireplumber /dev/snd/seq:pafleury 3249 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jan 12 20:13:39 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2023-01-06 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s0no wireless extensions. enxb04f13f51dd2 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=UUID=c85917c3-d792-4a15-8eb4-df2aa2266795 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-generic-hwe-22.04 5.19.0.29.26 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4408 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4408:bd10/27/2022:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic -- 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/2002690 Title: package linux-generic-hwe-22.04 5.19.0.29.26 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in initramfs-tools package in Ubuntu: New Bug description: kjl ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-generic-hwe-22.04 5.19.0.29.26 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pafleury 3252 F wireplumber /dev/snd/controlC2: pafleury 3252 F wireplumber /dev/snd/controlC1: pafleury 3252 F wireplumber /dev/snd/seq:pafleury 3249 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jan 12 20:13:39 2023 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2023-01-06 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp6s0no wireless extensions. enxb04f13f51dd2 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=UUID=c85917c3-d792-4a15-8eb4-df2aa2266795 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-generic-hwe-22.04 5.19.0.29.26 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4408 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default
[Touch-packages] [Bug 2002210] Re: package linux-image-5.15.0-57-generic 5.15.0-57.63~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/2002210 Title: package linux-image-5.15.0-57-generic 5.15.0-57.63~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I have dual boot. It happened a while after rebooted from Windows 11. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-57-generic 5.15.0-57.63~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jan 7 14:08:55 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-02 (980 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-57-generic 5.15.0-57.63~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2002210/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: Fix Committed Status in llvm-toolchain-15 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: In Progress Status in spirv-llvm-translator-15 source package in Jammy: Fix Committed Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 2002511] Re: zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2002511
Title:
zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
Status in Ubuntu on IBM z Systems:
In Progress
Status in zlib:
In Progress
Status in zlib package in Ubuntu:
In Progress
Status in zlib source package in Focal:
New
Status in zlib source package in Jammy:
New
Status in zlib source package in Kinetic:
New
Status in zlib source package in Lunar:
In Progress
Bug description:
SRU Justification:
--
[ Impact ]
* zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
the patch from LP#1990379, break libxml2 and lxml on s390x.
* The problem appears during loading a gzipped XML file.
* Disabling hw compression with 'export DFLTCC=0' solves this,
hence it's a problem with the hardware acceleration patches DFLTCC.
* For more info see:
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
[ Test Plan ]
* Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
* Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py",
line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
* Expected results:
Loaded file.
[ Where problems could occur ]
* Since this is limited to s390x and DFLTCC / hw acceleration active,
any possible problems are limited to such environments.
* Fix can be broken if the state handling (state->wrap),
or the states mixed.
* The translation from stream to parameter block could be broken
(again due to wrong states) and the inflate as well.
[ Other Info ]
* The official upstream fix is here:
https://github.com/zlib-ng/zlib-ng/pull/1390
but it's for zlib-ng.
* For zlib this needs to be adjusted and was done by the author here:
https://launchpadlibrarian.net/641454325/patch-1.2.11
* And again slightly adjusted by me (renamed, some white-space fixes
and conversion into a quilt patch with proper dep3 header):
https://launchpadlibrarian.net/645435847/1390.patch
* The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
__
It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks
libxml2 (and libxml) on s390x:
(https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch
should fix the issue.
The upstream author proposed a fix and a new test for zlib-ng
(https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
breakages in the future.
___
This was initially reported as part of LP#1990379,
especially:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
but needs a separate LP bug (number) - this one.
___
The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
needed some tweaks regarding white-spaces, but then applied fine on focal,
jammy, kinetic and also 1.2.13, which is what we currently have in
lunar-proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 1971932] Re: error in rsync protocol data stream
That's consistent with the comments above as the USB->SSD transfer doesn't use the rsync protocol. What we need to move this forward is a verification that applying [1] to the version of rsync in Bionic (3.1.2) or Focal (3.1.3) fixes the issue. If any of you affected users is available for testing an experimental package we can prepare one and publish it to a PPA. Once the fix is verified we can start the actual SRU process, which will require more feedback (verification) from affected users. [1] https://bugzilla.opensuse.org/attachment.cgi?id=853856=diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: Confirmed Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+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 2002660] [NEW] networkx incompatible with numpy 1.24
Public bug reported:
The nipype autopkgtests have started failing with the following stack
trace:
ERROR collecting pipeline/plugins/tests/test_tools.py _
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:1006: in _find_and_load_unlocked
???
:688: in _load_unlocked
???
:883: in exec_module
???
:241: in _call_with_frames_removed
???
nipype/pipeline/plugins/__init__.py:5: in
from .debug import DebugPlugin
nipype/pipeline/plugins/debug.py:7: in
import networkx as nx
/usr/lib/python3/dist-packages/networkx/__init__.py:115: in
import networkx.readwrite
/usr/lib/python3/dist-packages/networkx/readwrite/__init__.py:15: in
from networkx.readwrite.graphml import *
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:314: in
class GraphML(object):
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:346: in GraphML
(np.int, "int"), (np.int8, "int"),
/usr/lib/python3/dist-packages/numpy/__init__.py:284: in __getattr__
raise AttributeError("module {!r} has no attribute "
E AttributeError: module 'numpy' has no attribute 'int'
The problematic code is in the networkx package, and seems to have been
fixed in
https://github.com/networkx/networkx/commit/207147ee179554a33f10f25032054d3e01f96188
(which is in 2.5 onwards).
Debian currently ships with 2.8.8, we might want to merge?
This is currently blocking the python3-defaults transition.
** Affects: networkx (Ubuntu)
Importance: Undecided
Status: New
** Affects: nipype (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Tags added: update-excuse
** Also affects: nipype (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nipype (Ubuntu)
Status: New => Invalid
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2002660
Title:
networkx incompatible with numpy 1.24
Status in networkx package in Ubuntu:
New
Status in nipype package in Ubuntu:
Invalid
Status in python3-defaults package in Ubuntu:
New
Bug description:
The nipype autopkgtests have started failing with the following stack
trace:
ERROR collecting pipeline/plugins/tests/test_tools.py
_
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:992: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1050: in _gcd_import
???
:1027: in _find_and_load
???
:1006: in _find_and_load_unlocked
???
:688: in _load_unlocked
???
:883: in exec_module
???
:241: in _call_with_frames_removed
???
nipype/pipeline/plugins/__init__.py:5: in
from .debug import DebugPlugin
nipype/pipeline/plugins/debug.py:7: in
import networkx as nx
/usr/lib/python3/dist-packages/networkx/__init__.py:115: in
import networkx.readwrite
/usr/lib/python3/dist-packages/networkx/readwrite/__init__.py:15: in
from networkx.readwrite.graphml import *
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:314: in
class GraphML(object):
/usr/lib/python3/dist-packages/networkx/readwrite/graphml.py:346: in GraphML
(np.int, "int"), (np.int8, "int"),
/usr/lib/python3/dist-packages/numpy/__init__.py:284: in __getattr__
raise AttributeError("module {!r} has no attribute "
E AttributeError: module 'numpy' has no attribute 'int'
The problematic code is in the networkx package, and seems to have
been fixed in
https://github.com/networkx/networkx/commit/207147ee179554a33f10f25032054d3e01f96188
(which is in 2.5 onwards).
Debian currently ships with 2.8.8, we might want to merge?
This is currently blocking the python3-defaults transition.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkx/+bug/2002660/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 2002511]
It seems that the latest version of zlib fixed the problem we found in
lxml. Thanks! I think you can ship it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/2002511
Title:
zlib 1.2.13 (and patched 1.2.11) breaks libxml2 on s390x
Status in Ubuntu on IBM z Systems:
Triaged
Status in zlib:
In Progress
Status in zlib package in Ubuntu:
In Progress
Status in zlib source package in Focal:
New
Status in zlib source package in Jammy:
New
Status in zlib source package in Kinetic:
New
Status in zlib source package in Lunar:
In Progress
Bug description:
SRU Justification:
--
[ Impact ]
* zlib version 1.2.13, as well as patched zlib versions 1.2.11 with
the patch from LP#1990379, break libxml2 and lxml on s390x.
* The problem appears during loading a gzipped XML file.
* Disabling hw compression with 'export DFLTCC=0' solves this,
hence it's a problem with the hardware acceleration patches DFLTCC.
* For more info see:
https://bugzilla.redhat.com/show_bug.cgi?id=2155328
[ Test Plan ]
* Steps to Reproduce:
1. echo "" > file.xml
2. gzip file.xml
3. python3
>>> import libxml2
>>> libxml2.parseFile("file.xml.gz")
* Actual results:
file.xml.gz:1: parser error : Document is empty
^
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/libxml2.py",
line 1362, in parseFile
if ret is None:raise parserError('xmlParseFile() failed')
^^
libxml2.parserError: xmlParseFile() failed
* Expected results:
Loaded file.
[ Where problems could occur ]
* Since this is limited to s390x and DFLTCC / hw acceleration active,
any possible problems are limited to such environments.
* Fix can be broken if the state handling (state->wrap),
or the states mixed.
* The translation from stream to parameter block could be broken
(again due to wrong states) and the inflate as well.
[ Other Info ]
* The official upstream fix is here:
https://github.com/zlib-ng/zlib-ng/pull/1390
but it's for zlib-ng.
* For zlib this needs to be adjusted and was done by the author here:
https://launchpadlibrarian.net/641454325/patch-1.2.11
* And again slightly adjusted by me (renamed, some white-space fixes
and conversion into a quilt patch with proper dep3 header):
https://launchpadlibrarian.net/645435847/1390.patch
* The zlib version in Focal, Jammy, Kinetic and Lunar are affected.
__
It has been reported that 1.2.13 as well as the patch from LP#1990379 breaks
libxml2 (and libxml) on s390x:
(https://bugzilla.redhat.com/show_bug.cgi?id=2155328). The attached patch
should fix the issue.
The upstream author proposed a fix and a new test for zlib-ng
(https://github.com/zlib-ng/zlib-ng/pull/1390) in order to detect such
breakages in the future.
___
This was initially reported as part of LP#1990379,
especially:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1990379/comments/12
but needs a separate LP bug (number) - this one.
___
The proposed patch at https://launchpadlibrarian.net/641454325/patch-1.2.11
needed some tweaks regarding white-spaces, but then applied fine on focal,
jammy, kinetic and also 1.2.13, which is what we currently have in
lunar-proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2002511/+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 1983794] Re: Evolution not deleting autosave files
** Changed in: evolution (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Fix Released
Status in evolution package in Ubuntu:
Invalid
Status in libcanberra package in Ubuntu:
Fix Released
Status in libcanberra source package in Jammy:
In Progress
Status in evolution source package in Kinetic:
New
Status in libcanberra source package in Kinetic:
In Progress
Bug description:
[ Impact ]
Autosave files are not removed from evolution local state directories
(and windows leaked)
[ Test case ]
1. Open evolution, and start to compose a new email
2. Write enough text and wait few minutes so that this command returns a file
ls -l ~/.local/share/evolution/.evolution-composer.autosave-*
3. Close the email composer window, hitting "Do not save"
4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list
no files
5. Opening and closing again evolution should not ask to restore the previous
email
[ Regression potential ]
No sounds could be performed during some UI actions
---
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+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 868395] Re: localtime_r multiple times slower for Europe/Moscow timezone
Launchpad has imported 7 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=15943.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2013-09-11T02:20:10+00:00 Qd-feng wrote:
There is one thread in our application frequently call the localtime_r. We
found the thread performance has 20% drop when change the timezone from the
America/New_york to Asia/Shanghai from the system(Redhat 6,). After profile, we
found it is the localtime_r cause the difference.
When set the timezone as America/New_york, the __tzfile_compute mainly call the
__tzstring. While when set the timezone as the Asia/Shanghai the
__tzfile_compute call the __tzset_parse_tz which consume most of the CPU time.
I also do an simple test on our HP G8 server.
1 #include
2 #include
3
4 int main(void)
5 {
6 struct tm newtime;
7time_t ltime;
8 char buf[50];
9
10 for(int i=0;i<=100;i++)
11 {
12 ltime=time();
13
14 localtime_r(, );
15 }
16 }
After compile and run command time ./a.out with the timezone as Asia/Shanghai
or
America/New_York.
Asia/Shanghai
real 0m1.838s
user 0m1.628s
sys 0m0.206s
America/New_York
real 0m0.608s
user 0m0.395s
sys 0m0.211s
There is no TZ env been set on both cases. I wonder what causes the
performance so difference, is it an designed behavior?
Steven
Reply at:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395/comments/7
On 2013-09-11T08:02:40+00:00 Andreas Schwab wrote:
How do you set the timezone?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395/comments/8
On 2013-09-11T08:16:23+00:00 Qd-feng wrote:
link the /etc/localtime to time zone under usr/share/zoneinfo/
e.g.
ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime
Reply at:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395/comments/9
On 2016-05-17T12:26:29+00:00 Anat-mazurov wrote:
Please, have a look at this thread:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395
Don't know if it's the same bug, but seems to be very similar.
There is a workaround that involves patching tzdata package (comment
#6), which helped in that case with Russian timezones, and maybe will
do for you. But I really think that fixing glibc is a correct way to
resolve the problem, as it significantly affects performance under some
workloads.
Also there is some technical info mentioned in comment #4 that may help
in resolving this bug.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395/comments/12
On 2016-05-17T13:16:21+00:00 Andreas Schwab wrote:
The difference between America/New_York and Asia/Shanghai is that the
former has transitions until far in the future, whereas the last
transition of the latter was 1991, and later timestamps are computed
from the embedded POSIX TZ string.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395/comments/13
On 2023-01-11T19:17:04+00:00 Paul Eggert wrote:
This glibc performance bug came up recently on the tz mailing list; see
the thread "[tz] localtime_r multiple times slower for Europe/Moscow
timezone" starting here:
https://mm.icann.org/pipermail/tz/2023-January/032522.html
That thread stems from the following Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395
Guy Harris diagnosed the problem as glibc not properly caching the
expansion of the TZ string at the end of the TZif file. See:
https://mm.icann.org/pipermail/tz/2023-January/032529.html
This problem has grown in importance as many jurisdictions are now like
Moscow, as they formerly had daylight saving but now no longer do. So
this performance bug is more important now than it was years ago.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395/comments/19
On 2023-01-12T00:43:09+00:00 Guy Harris wrote:
Most if not all of China and India are also now no longer on DST, which
is why it happens with Asia/Shanghai.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/868395/comments/20
** Changed in: glibc
Status: Unknown => Confirmed
** Changed in: glibc
Importance: Unknown => Medium
--
You received this bug notification because
