Re: [Touch-packages] [Bug 1998309] Re: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo.
Follow-up: I don't think the bug report actually went through. I was never brought to the website like before. Should I attempt to post a new bug for this, or did the request send through my user acc around the time I depicted steps and mentioned sending it? Sent with Proton Mail secure email. --- Original Message --- On Thursday, December 1st, 2022 at 11:38 PM, ke7in.dev wrote: > Side note: I hit ctrl+c to cancel terminal after and got this: > > ``` > ^CException ignored in: '/usr/lib/python3.10/threading.py'> > > Traceback (most recent call last): > File "/usr/lib/python3.10/threading.py", line 1567, in _shutdown > lock.acquire() > KeyboardInterrupt: > ``` > > > > > Sent with Proton Mail secure email. > > > --- Original Message --- > On Thursday, December 1st, 2022 at 11:34 PM, ke7in.dev ke7in@proton.me > wrote: > > > > > Steps to achieve hang (or crash on the 1st attempt, before updating system > > packages -- not sure if that's unrelated to the change in the behavior or > > not, but worth mentioning): > > > > 1. type 'ubuntu-bug' in konsole > > > > 2. click audio related > > > > 3. click "It's not listed here" > > > > 4. don't click "OK", click "Cancel" > > > > These are the same exact steps to achieve issue 3x now. > > > > This last time I did the commands on my 2nd system to the same effect. > > > > I ran "ubuntu-bug --hanging 4675" in the same konsole as the original req > > and my cursor went to a new line (that is blank, no pathnames) > > > > I checked the /var/crash folder and no new .crash files have been created. > > > > I followed up with the same command in a new konsole, bug report is being > > sent (YES!), however, this is on a different machine than the inital bug > > report, should I also run this bug report on the original? > > > > Sent with Proton Mail secure email. > > > > --- Original Message --- > > On Thursday, December 1st, 2022 at 12:35 PM, Benjamin Drung > > 1998...@bugs.launchpad.net wrote: > > > > > 1. I can confirm this behavior. You can run "ubuntu-bug ". If > > > > > > you want to suggest a different behavior, please open a separate bug > > > report for it. > > > > > > 2. Can you recreate the hang? Then run "ubuntu-bug --hanging " > > > > > > where is the process ID of the hanging ubuntu-bug. > > > > > > -- > > > You received this bug notification because you are subscribed to the bug > > > report. > > > https://bugs.launchpad.net/bugs/1998309 > > > > > > Title: > > > attempted to report a few of the bugs I'm experiencing using 22.10 > > > (I'm using on 2 machines)...and the bug reporter crashed when I tried > > > to exit / redo. > > > > > > Status in apport package in Ubuntu: > > > Incomplete > > > > > > Bug description: > > > 1. Ubuntu 22.10 (studio install) > > > > > > 2. 2.23.1-0ubuntu3 500 > > > > > > 3. I was on generic bug selection screen and picked the "best fitting" > > > one (konsole popped up 1319), but realized there were no great options > > > and went to 'x' it out to dig a little more... > > > > > > 4. crash. > > > > > > ProblemType: Bug > > > DistroRelease: Ubuntu 22.10 > > > Package: apport-kde 2.23.1-0ubuntu3 > > > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > > > Uname: Linux 5.19.0-1009-lowlatency x86_64 > > > ApportVersion: 2.23.1-0ubuntu3 > > > Architecture: amd64 > > > CasperMD5CheckResult: unknown > > > CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 > > > -0500:2022-11-30 02:13:35.548841973 > > > -0500:/var/crash/_usr_bin_avplayer.1000.crash > > > CurrentDesktop: KDE > > > Date: Wed Nov 30 03:11:50 2022 > > > InstallationDate: Installed on 2022-11-29 (0 days ago) > > > InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 > > > (20221017.1) > > > PackageArchitecture: all > > > SourcePackage: apport > > > UpgradeStatus: No upgrade log present (probably fresh install) > > > > > > To manage notifications about this bug go to: > > > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1998309 Title: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo. Status in apport package in Ubuntu: Incomplete Bug description: 1. Ubuntu 22.10 (studio install) 2. 2.23.1-0ubuntu3 500 3. I was on generic bug selection screen and picked the "best fitting" one (konsole popped up 1319), but realized there were no great options and went to 'x' it out to dig a little more... 4. crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport-kde 2.23.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3
[Touch-packages] [Bug 1998415] Re: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install)
Hi Nick Not able to install, after run 'apt update' attached console logs FYR, intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt update Hit:1 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/ubuntu/jammy/jammy/1108-2146 jammy InRelease Ign:2 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ InRelease Ign:3 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Release Hit:4 http://in.archive.ubuntu.com/ubuntu jammy InRelease Hit:5 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Packages Ign:6 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en Ign:7 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en_US Ign:6 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en Ign:7 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en_US Get:8 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB] Ign:6 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en Ign:7 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en_US Ign:6 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en Ign:7 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en_US Ign:6 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en Ign:7 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en_US Ign:6 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en Get:9 http://in.archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB] Ign:7 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en_US Ign:6 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en Ign:7 https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/rtcm ./ Translation-en_US Ign:10 https://ubit-artifactory-or.intel.com/artifactory/turtle-creek-debian-local jammy InRelease Hit:11 https://ubit-artifactory-or.intel.com/artifactory/turtle-creek-debian-local jammy Release Ign:12 https://ubit-artifactory-or.intel.com/artifactory/turtle-creek-debian-local jammy Release.gpg Get:13 http://in.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB] Reading package lists... Done N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/ubuntu/jammy/jammy/1108-2146 jammy InRelease' doesn't support architecture 'i386' N: Skipping acquire of configured file 'non-free/binary-i386/Packages' as repository 'https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/ubuntu/jammy/jammy/1108-2146 jammy InRelease' doesn't support architecture 'i386' N: Skipping acquire of configured file 'multimedia/binary-i386/Packages' as repository 'https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/ubuntu/jammy/jammy/1108-2146 jammy InRelease' doesn't support architecture 'i386' N: Skipping acquire of configured file 'internal/binary-i386/Packages' as repository 'https://af01p-png.devtools.intel.com/artifactory/hspe-edge-png-local/ubuntu/jammy/jammy/1108-2146 jammy InRelease' doesn't support architecture 'i386' E: Release file for http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease is not valid yet (invalid for another 10h 24min 10s). Updates for this repository will not be applied. E: Release file for http://in.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease is not valid yet (invalid for another 10h 24min 28s). Updates for this repository will not be applied. E: Release file for http://in.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease is not valid yet (invalid for another 10h 24min 59s). Updates for this repository will not be applied. intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt-get install libsystemd-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsystemd-dev : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed E: Unable to correct problems, you have held broken packages. intel@intel-Raptor-Lake-Client-Platform:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.
Re: [Touch-packages] [Bug 1998309] Re: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo.
Side note: I hit ctrl+c to cancel terminal after and got this: ``` ^CException ignored in: Traceback (most recent call last): File "/usr/lib/python3.10/threading.py", line 1567, in _shutdown lock.acquire() KeyboardInterrupt: ``` Sent with Proton Mail secure email. --- Original Message --- On Thursday, December 1st, 2022 at 11:34 PM, ke7in.dev wrote: > Steps to achieve hang (or crash on the 1st attempt, before updating system > packages -- not sure if that's unrelated to the change in the behavior or > not, but worth mentioning): > > 1. type 'ubuntu-bug' in konsole > > 2. click audio related > > 3. click "It's not listed here" > > 4. don't click "OK", click "Cancel" > > These are the same exact steps to achieve issue 3x now. > > This last time I did the commands on my 2nd system to the same effect. > > > I ran "ubuntu-bug --hanging 4675" in the same konsole as the original req and > my cursor went to a new line (that is blank, no pathnames) > > I checked the /var/crash folder and no new .crash files have been created. > > I followed up with the same command in a new konsole, bug report is being > sent (YES!), however, this is on a different machine than the inital bug > report, should I also run this bug report on the original? > > > > > > > > > Sent with Proton Mail secure email. > > > --- Original Message --- > On Thursday, December 1st, 2022 at 12:35 PM, Benjamin Drung > 1998...@bugs.launchpad.net wrote: > > > > > 1. I can confirm this behavior. You can run "ubuntu-bug ". If > > > > you want to suggest a different behavior, please open a separate bug > > report for it. > > > > 2. Can you recreate the hang? Then run "ubuntu-bug --hanging " > > > > where is the process ID of the hanging ubuntu-bug. > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1998309 > > > > Title: > > attempted to report a few of the bugs I'm experiencing using 22.10 > > (I'm using on 2 machines)...and the bug reporter crashed when I tried > > to exit / redo. > > > > Status in apport package in Ubuntu: > > Incomplete > > > > Bug description: > > 1. Ubuntu 22.10 (studio install) > > > > 2. 2.23.1-0ubuntu3 500 > > > > 3. I was on generic bug selection screen and picked the "best fitting" > > one (konsole popped up 1319), but realized there were no great options > > and went to 'x' it out to dig a little more... > > > > 4. crash. > > > > ProblemType: Bug > > DistroRelease: Ubuntu 22.10 > > Package: apport-kde 2.23.1-0ubuntu3 > > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > > Uname: Linux 5.19.0-1009-lowlatency x86_64 > > ApportVersion: 2.23.1-0ubuntu3 > > Architecture: amd64 > > CasperMD5CheckResult: unknown > > CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 > > -0500:2022-11-30 02:13:35.548841973 > > -0500:/var/crash/_usr_bin_avplayer.1000.crash > > CurrentDesktop: KDE > > Date: Wed Nov 30 03:11:50 2022 > > InstallationDate: Installed on 2022-11-29 (0 days ago) > > InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 > > (20221017.1) > > PackageArchitecture: all > > SourcePackage: apport > > UpgradeStatus: No upgrade log present (probably fresh install) > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1998309 Title: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo. Status in apport package in Ubuntu: Incomplete Bug description: 1. Ubuntu 22.10 (studio install) 2. 2.23.1-0ubuntu3 500 3. I was on generic bug selection screen and picked the "best fitting" one (konsole popped up 1319), but realized there were no great options and went to 'x' it out to dig a little more... 4. crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport-kde 2.23.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 -0500:2022-11-30 02:13:35.548841973 -0500:/var/crash/_usr_bin_avplayer.1000.crash CurrentDesktop: KDE Date: Wed Nov 30 03:11:50 2022 InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+subscriptions --
Re: [Touch-packages] [Bug 1998309] Re: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo.
Steps to achieve hang (or crash on the 1st attempt, before updating system packages -- not sure if that's unrelated to the change in the behavior or not, but worth mentioning): 1. type 'ubuntu-bug' in konsole 2. click audio related 3. click "It's not listed here" 4. don't click "OK", click "Cancel" These are the same exact steps to achieve issue 3x now. This last time I did the commands on my 2nd system to the same effect. I ran "ubuntu-bug --hanging 4675" in the same konsole as the original req and my cursor went to a new line (that is blank, no pathnames) I checked the /var/crash folder and no new .crash files have been created. I followed up with the same command in a new konsole, bug report is being sent (YES!), however, this is on a different machine than the inital bug report, should I also run this bug report on the original? Sent with Proton Mail secure email. --- Original Message --- On Thursday, December 1st, 2022 at 12:35 PM, Benjamin Drung <1998...@bugs.launchpad.net> wrote: > 1. I can confirm this behavior. You can run "ubuntu-bug ". If > > you want to suggest a different behavior, please open a separate bug > report for it. > > 2. Can you recreate the hang? Then run "ubuntu-bug --hanging " > > where is the process ID of the hanging ubuntu-bug. > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1998309 > > Title: > attempted to report a few of the bugs I'm experiencing using 22.10 > (I'm using on 2 machines)...and the bug reporter crashed when I tried > to exit / redo. > > Status in apport package in Ubuntu: > Incomplete > > Bug description: > 1. Ubuntu 22.10 (studio install) > > 2. 2.23.1-0ubuntu3 500 > > 3. I was on generic bug selection screen and picked the "best fitting" > one (konsole popped up 1319), but realized there were no great options > and went to 'x' it out to dig a little more... > > 4. crash. > > ProblemType: Bug > DistroRelease: Ubuntu 22.10 > Package: apport-kde 2.23.1-0ubuntu3 > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > Uname: Linux 5.19.0-1009-lowlatency x86_64 > ApportVersion: 2.23.1-0ubuntu3 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 > -0500:2022-11-30 02:13:35.548841973 > -0500:/var/crash/_usr_bin_avplayer.1000.crash > CurrentDesktop: KDE > Date: Wed Nov 30 03:11:50 2022 > InstallationDate: Installed on 2022-11-29 (0 days ago) > InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 > (20221017.1) > PackageArchitecture: all > SourcePackage: apport > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1998309 Title: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo. Status in apport package in Ubuntu: Incomplete Bug description: 1. Ubuntu 22.10 (studio install) 2. 2.23.1-0ubuntu3 500 3. I was on generic bug selection screen and picked the "best fitting" one (konsole popped up 1319), but realized there were no great options and went to 'x' it out to dig a little more... 4. crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport-kde 2.23.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 -0500:2022-11-30 02:13:35.548841973 -0500:/var/crash/_usr_bin_avplayer.1000.crash CurrentDesktop: KDE Date: Wed Nov 30 03:11:50 2022 InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+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 1998551] Re: Please merge gmp 2:6.2.1+dfsg1-1.1 into lunar
** Changed in: gmp (Ubuntu) Assignee: (unassigned) => Vladimir Petko (vpa1977) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gmp in Ubuntu. https://bugs.launchpad.net/bugs/1998551 Title: Please merge gmp 2:6.2.1+dfsg1-1.1 into lunar Status in gmp package in Ubuntu: In Progress Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gmp/+bug/1998551/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
** Tags added: originate-from-1998320 somerville
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Workaround]
Some workarounds have been suggested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package,
[Touch-packages] [Bug 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu8 --- openssh (1:9.0p1-1ubuntu8) lunar; urgency=medium * debian/openssh-server.postinst: Fix handling of ListenAddress when a port is specified (LP: #1993478): - Strip port before converting hostnames to numerical addresses. - Only append ports when the ListenAddress does not already specify a port. - Revert socket migration on upgrade if a previous version did the migration when it should not have. * debian/openssh-server.postinst: Ignore empty directory failure from rmdir when skipping socket migration (LP: #1995294). -- Nick Rosbrook Tue, 25 Oct 2022 11:57:43 -0400 ** Changed in: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1993478 Title: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Kinetic: Fix Released Bug description: [Impact] Users with /etc/ssh/sshd_config's that contain ListenAddress entries with the port specified will not be migrated to socket-activated ssh correctly, or may be migrated when they should not be (e.g. if ListenAddress, with a port number, is specified more than once). This leaves users with a broken sshd configuration. [Test Plan] There are 4 tests that should be used to verify the fix: 1. Upgrade to Kinetic with just one ListenAddress entry, which specifies port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, ssh.socket will be active/listening, and /etc/systemd/system/ssh.socket.d/addresses.conf will contain the following: [Socket] ListenStream= ListenStream=0.0.0.0:1234 2. Upgrade to Kinetic with multiple ListenAddress entries, each specifying port number. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 ListenAddress [::]:4321 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Before running the upgrade, make sure -proposed is enabled. * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, and then running apt dist-upgrade (-proposed is disabled when using ubuntu-release-upgrader). * On an affected system, migration will be attempted despite the multiple ListenAddress options, and ssh.socket will fail with `bad-setting` because /etc/systemd/system/ssh.socket.d/address.conf contains: [Socket] ListenStream= * On a patched system, the ListenAddress option will be parsed correctly, and migration will not be attempted. 3. On a Kinetic system which was migrated, but with errors (e.g. test case #1, prior to being patched), installing the new package should correct the ssh.socket configuration. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the following: [...defaults everywhere else...] #Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: ListenAddress 0.0.0.0:1234 [...defaults everywhere else...] * Run `systemctl restart ssh.service` and confirm that the new configuration works as expected. * Do NOT enable -proposed before the upgrade. * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in /etc/update-manager/release-upgrades if needed). * After the openssh-server configuration fails, enable -proposed, and upgrade openssh-server. * The ssh.socket configuration should be fixed, and /etc/systemd/system/ssh.socket.d/addresses.conf should contain: [Socket] ListenStream= ListenStream=0.0.0.0:1234 4. On a Kinetic system which was incorrectly migrated to ssh socket activation (e.g. test case #2, prior to being patched), installing the new package reverts to the previous behavior. * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
[Touch-packages] [Bug 1995294] Re: rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty
This bug was fixed in the package openssh - 1:9.0p1-1ubuntu8 --- openssh (1:9.0p1-1ubuntu8) lunar; urgency=medium * debian/openssh-server.postinst: Fix handling of ListenAddress when a port is specified (LP: #1993478): - Strip port before converting hostnames to numerical addresses. - Only append ports when the ListenAddress does not already specify a port. - Revert socket migration on upgrade if a previous version did the migration when it should not have. * debian/openssh-server.postinst: Ignore empty directory failure from rmdir when skipping socket migration (LP: #1995294). -- Nick Rosbrook Tue, 25 Oct 2022 11:57:43 -0400 ** Changed in: openssh (Ubuntu) Status: Triaged => Fix Released -- 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/1995294 Title: rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Kinetic: Fix Released Bug description: [Impact] If a user a has an existing drop-in config for ssh.socket in /etc/systemd/system/ssh.socket.d upgrades to kinetic, and openssh- server.postint determines it should *not* perform migration to socket- activated ssh, they will receive an error from dpkg: Errors were encountered while processing: openssh-server Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Please report this bug in a browser at http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug and attach the files in /var/log/dist-upgrade/ to the bug report. E:Sub-process /usr/bin/dpkg returned an error code (1) Setting up openssh-server (1:9.0p1-1ubuntu7) ... rmdir: failed to remove '/etc/systemd/system/ssh.socket.d': Directory not empty dpkg: error processing package openssh-server (--configure): installed openssh-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: openssh-server [Test Plan] * On a Jammy machine, install openssh-server if necessary. Edit /etc/ssh/sshd_config to contain the following: $ cat /etc/ssh/sshd_config [... defaults everywhere else ...] #Port 22 #AddressFamily any ListenAddress 0.0.0.0 ListenAddress :: [... defaults everywhere else ...] * Create a trivial drop-in override for ssh.socket: $ systemctl edit ssh.socket $ cat /etc/systemd/system/ssh.socket.d/override.conf [Unit] Description=Testing * Now perform an upgrade to Kinetic, and observe the dpkg error. [Where problems could occur] The solution should be to use rmdir's --ignore-fail-on-empty flag. If the flag was mis-spelled, that would produce a new error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1995294/+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 1998551] [NEW] Please merge gmp 2:6.2.1+dfsg1-1.1 into lunar
Public bug reported: tracking bug ** Affects: gmp (Ubuntu) Importance: Undecided Status: In Progress ** Changed in: gmp (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gmp in Ubuntu. https://bugs.launchpad.net/bugs/1998551 Title: Please merge gmp 2:6.2.1+dfsg1-1.1 into lunar Status in gmp package in Ubuntu: In Progress Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gmp/+bug/1998551/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
** Tags added: originate-from-1982919 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Confirmed Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1774419] Re: easy_install command is missing
** Changed in: python-setuptools (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1774419 Title: easy_install command is missing Status in python-setuptools package in Ubuntu: Confirmed Status in python-setuptools package in Debian: Fix Released Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 Package: python-setuptools Version: 39.0.1-2 This package installs the easy_install module, but the command is missing: deploy@controller0:~$ which easy_install deploy@controller0:~$ echo $? 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1774419/+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 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: modemmanager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Confirmed Bug description: :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:8914] https://lore.kernel.org/linux- wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/ Modemmanager requires >= 1.19.1, the detail info is in lp:1962525 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-07-13 (119 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.20+staging.31 PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9007-oem N/A linux-backports-modules-5.14.0-9007-oem N/A linux-firmware 1.187.20+staging.31 Tags: focal Uname: Linux 5.14.0-9007-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/23/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-M LP5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 01010002 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950282/+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 1998321] Autopkgtest regression report (tzdata/2022g-0ubuntu0.22.04.1)
All autopkgtests for the newly accepted tzdata (2022g-0ubuntu0.22.04.1) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
chrony/4.2-2ubuntu2 (armhf, s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Re: tzdata 2022g release
Ack from the Ubuntu Security team for these updates to go to the
security pocket as well, as per
https://wiki.ubuntu.com/StableReleaseUpdates#tzdata .
Thanks.
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Autopkgtest regression report (tzdata/2022g-0ubuntu0.22.10.1)
All autopkgtests for the newly accepted tzdata (2022g-0ubuntu0.22.10.1) for
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
chrony/4.2-2ubuntu2 (arm64)
php8.1/8.1.7-1ubuntu3.1 (arm64, s390x)
mtail/3.0.0~rc50-1 (amd64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Autopkgtest regression report (tzdata/2022g-0ubuntu0.20.04.1)
All autopkgtests for the newly accepted tzdata (2022g-0ubuntu0.20.04.1) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
libical3/3.0.8-1 (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Re: tzdata 2022g release
Verified focal:
(focal)root@deep-thought:~# dpkg -s tzdata | grep ^Version
Version: 2022g-0ubuntu0.20.04.1
(focal)root@deep-thought:~# zdump -v America/Ciudad_Juarez | grep -v NULL |
tail -n 1
America/Ciudad_Juarez Sun Nov 1 08:00:00 2499 UT = Sun Nov 1 01:00:00 2499
MST isdst=0 gmtoff=-25200
(focal)root@deep-thought:~# python3 -c 'from datetime import datetime,
timedelta; from icu import ICUtzinfo, TimeZone; tz =
ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"));
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))'
(focal)root@deep-thought:~# diff <(zdump -v America/Phoenix | cut -d' ' -f2-)
<(zdump -v SystemV/MST7 | cut -d' ' -f2-)
(focal)root@deep-thought:~#
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1823721] Re: systemctl fstrim.timer freeze computer with a SSD on a dual boot system Windows 10/Ubuntu 18.04
The util-linux package is responsible for
/lib/systemd/system/fstrim.{timer,service}.
** Package changed: systemd (Ubuntu) => util-linux (Ubuntu)
--
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/1823721
Title:
systemctl fstrim.timer freeze computer with a SSD on a dual boot
system Windows 10/Ubuntu 18.04
Status in util-linux package in Ubuntu:
Confirmed
Bug description:
The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
computer once a week (usually on Monday midnight) in the case of a
dual boot system installed on a SSD (Windows/Ubuntu) due to high IO
overhead. I also had several freeze at boot due to the same problem.
When the freeze occur I can open a tty terminal and type the command
iotop to see the process which use that amount of IO. It was
mount.ntfs-3g which point to my mount point to my Windows 10 install
on my SSD.
When the freeze occur the system is not responsive for about 10-15
minutes.
I solved my issue by disabling the fstrim.timer entirely with this
command:
sudo systemctl disable fstrim.timer
I can reproduce the problem on my installation by launching the
fstrim-timer:
sudo systemctl start fstrim.timer
Imediately after launching fstrim.timer, iotop display this line at
top, with my Windows 10 mount point:
TID PRIO USER DISK READ DISK WRITE SWAPIN IO>COMMAND
893 be/4 root0.00 B/s0.00 B/s 0.00 % 99.10 % mount.ntfs-3g
/dev/sda1 /media/systeme_windows -o
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user
And a few minutes later:
TID PRIO USER DISK READ DISK WRITE SWAPIN IO>COMMAND
20077 be/4 root0.00 B/s0.00 B/s 0.00 % 99.45 % fstrim -av
Systemd 237-3ubuntu10.19
Ubuntu 18.04.2
Linux 4.18.0-17-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1823721/+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 1998415] Re: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install)
It seems like your apt sources or local package information is out of date. The libsystemd-dev package depends on libsystemd0 such that they have the same version: $ apt-cache show libsystemd-dev Package: libsystemd-dev Architecture: amd64 Version: 249.11-0ubuntu3.6 Multi-Arch: same Priority: optional Section: libdevel Source: systemd Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian systemd Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1166 Depends: libsystemd0 (= 249.11-0ubuntu3.6) Filename: pool/main/s/systemd/libsystemd-dev_249.11-0ubuntu3.6_amd64.deb Size: 306372 MD5sum: 438e2a7c5a198073278bdc39a991ff81 SHA1: baddefadfb1c2aefa3c23fa875705809274f8c55 SHA256: 59f861c984ec3912a579dedf71b4c476b9fff605e869fcdd90ccc88fd91b61c8 SHA512: 15e260a9ff0b4080fb3349916c369dcc1dffc9a2301a50166eae6963aea6942d0f64da9a3b34f9fca3227d9aa508eb8e270f588a8413cfe820528813327799e0 Homepage: https://www.freedesktop.org/wiki/Software/systemd Description-en: systemd utility library - development files The libsystemd0 library provides interfaces to various systemd components. . This package contains the development files. Description-md5: 7122bf9ab5ca8703093117a2cda0fe22 Package: libsystemd-dev Architecture: amd64 Version: 249.11-0ubuntu3 Multi-Arch: same Priority: optional Section: libdevel Source: systemd Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian systemd Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 1164 Depends: libsystemd0 (= 249.11-0ubuntu3) Filename: pool/main/s/systemd/libsystemd-dev_249.11-0ubuntu3_amd64.deb Size: 306280 MD5sum: ac890b5993685d2df2cfe57adab50893 SHA1: f8904527872e2735952261e6434b132071b3afdf SHA256: 6429f316a8af1f7f9df5ae3a79e714eeda8a45512c49bd2ea1d25a4468b71e6e SHA512: 9e2632131a591f500abfa913a0b1f6e7c3c97f9955ba4c1aeb7fdb01c4f098c2188a3feb6686eb9426c07e1a0b7e4dbdde47338622237a520ab5382fb012eb14 Homepage: https://www.freedesktop.org/wiki/Software/systemd Description-en: systemd utility library - development files The libsystemd0 library provides interfaces to various systemd components. . This package contains the development files. Description-md5: 7122bf9ab5ca8703093117a2cda0fe22 Please run `apt update` before trying to install libsystemd-dev again. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1998415 Title: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install) Status in systemd package in Ubuntu: Incomplete Bug description: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install) libsystemd-dev wants libsystemd0 = 249.11-0ubuntu3 but 249.11-0ubuntu3.6 is installed. installation currently fails: intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt-get install libsystemd-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsystemd-dev : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed E: Unable to correct problems, you have held broken packages. FYI, intel@intel-Raptor-Lake-Client-Platform:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Customized image Release:22.04 Codename: jammy intel@intel-Raptor-Lake-Client-Platform:~$ dpkg -l libsystemd0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=--= ii libsystemd0:amd64 249.11-0ubuntu3.6 amd64systemd utility library intel@intel-Raptor-Lake-Client-Platform:~$ intel@intel-Raptor-Lake-Client-Platform:~$ apt-cache madison libsystemd0 libsystemd0 | 249.11-0ubuntu3 | http://in.archive.ubuntu.com/ubuntu jammy/main amd64 Packages intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt search libsystemd Sorting... Done Full Text Search... Done librust-libsystemd-dev/jammy,now 0.2.1-2build1 amd64 [installed] Pure-Rust client library to interact with systemd - Rust source code libsystemd-dev/jammy 249.11-0ubuntu3 amd64 systemd utility library - development files libsystemd0/jammy 249.11-0ubuntu3 i386
[Touch-packages] [Bug 1998321] Re: tzdata 2022g release
Verified jammy and kinetic:
(jammy)root@deep-thought:~# dpkg -s tzdata | grep ^Version
Version: 2022g-0ubuntu0.22.04.1
(jammy)root@deep-thought:~# zdump -v America/Ciudad_Juarez | grep -v NULL |
tail -n 1
America/Ciudad_Juarez Sun Nov 1 08:00:00 2499 UT = Sun Nov 1 01:00:00 2499
MST isdst=0 gmtoff=-25200
(jammy)root@deep-thought:~# python3 -c 'from datetime import datetime,
timedelta; from icu import ICUtzinfo, TimeZone; tz =
ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"));
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))'
(jammy)root@deep-thought:~#
(kinetic)root@deep-thought:~# dpkg -s tzdata | grep ^Version
Version: 2022g-0ubuntu0.22.10.1
(kinetic)root@deep-thought:~# zdump -v America/Ciudad_Juarez | grep -v NULL |
tail -n 1
America/Ciudad_Juarez Sun Nov 1 08:00:00 2499 UT = Sun Nov 1 01:00:00 2499
MST isdst=0 gmtoff=-25200
(kinetic)root@deep-thought:~# python3 -c 'from datetime import datetime,
timedelta; from icu import ICUtzinfo, TimeZone; tz =
ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"));
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))'
(kinetic)root@deep-thought:~#
** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-jammy verification-done-kinetic
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
Hello everyone subscribed to this topic, I totally edited my previous comment because it was a misconception. Now I noticed, the problem depends on whether the printer is connected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1998444] Re: Backport security fix for CVE-2022-3970
The fix for CVE-2022-3970 has been released in the following versions: Ubuntu 22.10: 4.4.0-4ubuntu3.2 Ubuntu 22.04 LTS: 4.3.0-6ubuntu0.3 Ubuntu 20.04 LTS: 4.1.0+git191117-2ubuntu0.20.04.7 Ubuntu 18.04 LTS: 4.0.9-5ubuntu0.9 ** Changed in: tiff (Ubuntu) Status: In Progress => Fix Released ** Changed in: tiff (Ubuntu Bionic) Status: New => Fix Released ** Changed in: tiff (Ubuntu Focal) Status: New => Fix Released ** Changed in: tiff (Ubuntu Jammy) Status: New => Fix Released ** Changed in: tiff (Ubuntu Kinetic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1998444 Title: Backport security fix for CVE-2022-3970 Status in tiff package in Ubuntu: Fix Released Status in tiff source package in Bionic: Fix Released Status in tiff source package in Focal: Fix Released Status in tiff source package in Jammy: Fix Released Status in tiff source package in Kinetic: Fix Released Bug description: This CVE patch is desperately needed to fix a build failure caused by a crash in the testsuite of the current libreoffice/kinetic SRU Testing load file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff: *** stack smashing detected ***: terminated Fatal exception: Signal 6 Stack: /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2] /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc] /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a] /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636] /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386] /lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc] /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1] /lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10] /<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6] /<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5] /<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c] /<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07] /<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f] /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9] /<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5] Aborted (core dumped)
[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
** Tags added: jammy kinetic -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1998309] Re: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo.
1. I can confirm this behavior. You can run "ubuntu-bug ". If you want to suggest a different behavior, please open a separate bug report for it. 2. Can you recreate the hang? Then run "ubuntu-bug --hanging " where is the process ID of the hanging ubuntu-bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1998309 Title: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo. Status in apport package in Ubuntu: Incomplete Bug description: 1. Ubuntu 22.10 (studio install) 2. 2.23.1-0ubuntu3 500 3. I was on generic bug selection screen and picked the "best fitting" one (konsole popped up 1319), but realized there were no great options and went to 'x' it out to dig a little more... 4. crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport-kde 2.23.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 -0500:2022-11-30 02:13:35.548841973 -0500:/var/crash/_usr_bin_avplayer.1000.crash CurrentDesktop: KDE Date: Wed Nov 30 03:11:50 2022 InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+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 1998321] Autopkgtest regression report (tzdata/2022g-0ubuntu0.22.04.0)
All autopkgtests for the newly accepted tzdata (2022g-0ubuntu0.22.04.0) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
chrony/4.2-2ubuntu2 (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998415] Re: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install)
** Package changed: ubuntu => systemd (Ubuntu) -- 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/1998415 Title: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install) Status in systemd package in Ubuntu: New Bug description: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install) libsystemd-dev wants libsystemd0 = 249.11-0ubuntu3 but 249.11-0ubuntu3.6 is installed. installation currently fails: intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt-get install libsystemd-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsystemd-dev : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed E: Unable to correct problems, you have held broken packages. FYI, intel@intel-Raptor-Lake-Client-Platform:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Customized image Release:22.04 Codename: jammy intel@intel-Raptor-Lake-Client-Platform:~$ dpkg -l libsystemd0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=--= ii libsystemd0:amd64 249.11-0ubuntu3.6 amd64systemd utility library intel@intel-Raptor-Lake-Client-Platform:~$ intel@intel-Raptor-Lake-Client-Platform:~$ apt-cache madison libsystemd0 libsystemd0 | 249.11-0ubuntu3 | http://in.archive.ubuntu.com/ubuntu jammy/main amd64 Packages intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt search libsystemd Sorting... Done Full Text Search... Done librust-libsystemd-dev/jammy,now 0.2.1-2build1 amd64 [installed] Pure-Rust client library to interact with systemd - Rust source code libsystemd-dev/jammy 249.11-0ubuntu3 amd64 systemd utility library - development files libsystemd0/jammy 249.11-0ubuntu3 i386 systemd utility library lua-systemd/jammy,now 0~git20160517-2 amd64 [installed] Systemd bindings for Lua python3-systemd/jammy,now 234-3ubuntu2 amd64 [installed,automatic] Python 3 bindings for systemd intel@intel-Raptor-Lake-Client-Platform:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1998415/+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 1998415] [NEW] jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install)
You have been subscribed to a public bug: jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install) libsystemd-dev wants libsystemd0 = 249.11-0ubuntu3 but 249.11-0ubuntu3.6 is installed. installation currently fails: intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt-get install libsystemd-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libsystemd-dev : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed E: Unable to correct problems, you have held broken packages. FYI, intel@intel-Raptor-Lake-Client-Platform:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Customized image Release:22.04 Codename: jammy intel@intel-Raptor-Lake-Client-Platform:~$ dpkg -l libsystemd0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=--= ii libsystemd0:amd64 249.11-0ubuntu3.6 amd64systemd utility library intel@intel-Raptor-Lake-Client-Platform:~$ intel@intel-Raptor-Lake-Client-Platform:~$ apt-cache madison libsystemd0 libsystemd0 | 249.11-0ubuntu3 | http://in.archive.ubuntu.com/ubuntu jammy/main amd64 Packages intel@intel-Raptor-Lake-Client-Platform:~$ sudo apt search libsystemd Sorting... Done Full Text Search... Done librust-libsystemd-dev/jammy,now 0.2.1-2build1 amd64 [installed] Pure-Rust client library to interact with systemd - Rust source code libsystemd-dev/jammy 249.11-0ubuntu3 amd64 systemd utility library - development files libsystemd0/jammy 249.11-0ubuntu3 i386 systemd utility library lua-systemd/jammy,now 0~git20160517-2 amd64 [installed] Systemd bindings for Lua python3-systemd/jammy,now 234-3ubuntu2 amd64 [installed,automatic] Python 3 bindings for systemd intel@intel-Raptor-Lake-Client-Platform:~$ ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- jammy libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install) https://bugs.launchpad.net/bugs/1998415 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
still present in 22.10. Newest ubuntu still work against old version of snap. # probe for assertions, must run before udisks2 ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \ RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k" in my rule file -- 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 Status in snapd: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+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 1998321] Autopkgtest regression report (tzdata/2022g-0ubuntu0.22.04.0)
All autopkgtests for the newly accepted tzdata (2022g-0ubuntu0.22.04.0) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
chrony/4.2-2ubuntu2 (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Re: tzdata 2022g release
Hello Benjamin, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022g-0ubuntu0.20.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-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. 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.
** Tags removed: verification-done-focal
** Tags added: verification-needed-focal
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1992369] Re: DejaVu Serif Italic capital letters and digits broken
** Also affects: fontforge (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1998309] Re: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo.
Hi Benjamin, Thanks for getting back to me. There is unfortunately no crash report available for apport. I went and tinkered with the ubuntu-bug command as you suggested to try and close in on the issue here. I want to note 2 things: 1. The generic bug reporter was not allowing me to select "other" it spat back that I needed to include the package in questions (when the command specifically told me to run generic ubuntu-bug, strange?) 2. even after replicating this to the best of my ability, it did not crash this time. Instead it hung up / froze so I took a screen shot of everything involved. File is attached. If you also want the avplayer.1000.crash file (not sure this issue is related), let me know! Sent with Proton Mail secure email. --- Original Message --- On Wednesday, November 30th, 2022 at 5:01 AM, Benjamin Drung <1998...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Sadly the attached logs do not contain the crash > information. Do you have an apport crash file in /var/crash? If not, can > you run ubuntu-bug in a terminal to capture the crash there? > > ** Changed in: apport (Ubuntu) > Status: New => Incomplete > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1998309 > > Title: > attempted to report a few of the bugs I'm experiencing using 22.10 > (I'm using on 2 machines)...and the bug reporter crashed when I tried > to exit / redo. > > Status in apport package in Ubuntu: > Incomplete > > Bug description: > 1. Ubuntu 22.10 (studio install) > > 2. 2.23.1-0ubuntu3 500 > > 3. I was on generic bug selection screen and picked the "best fitting" > one (konsole popped up 1319), but realized there were no great options > and went to 'x' it out to dig a little more... > > 4. crash. > > ProblemType: Bug > DistroRelease: Ubuntu 22.10 > Package: apport-kde 2.23.1-0ubuntu3 > ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 > Uname: Linux 5.19.0-1009-lowlatency x86_64 > ApportVersion: 2.23.1-0ubuntu3 > Architecture: amd64 > CasperMD5CheckResult: unknown > CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 > -0500:2022-11-30 02:13:35.548841973 > -0500:/var/crash/_usr_bin_avplayer.1000.crash > CurrentDesktop: KDE > Date: Wed Nov 30 03:11:50 2022 > InstallationDate: Installed on 2022-11-29 (0 days ago) > InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 > (20221017.1) > PackageArchitecture: all > SourcePackage: apport > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+subscriptions ** Attachment added: "ubuntu-bug issue.png" https://bugs.launchpad.net/bugs/1998309/+attachment/5633759/+files/ubuntu-bug%20issue.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1998309 Title: attempted to report a few of the bugs I'm experiencing using 22.10 (I'm using on 2 machines)...and the bug reporter crashed when I tried to exit / redo. Status in apport package in Ubuntu: Incomplete Bug description: 1. Ubuntu 22.10 (studio install) 2. 2.23.1-0ubuntu3 500 3. I was on generic bug selection screen and picked the "best fitting" one (konsole popped up 1319), but realized there were no great options and went to 'x' it out to dig a little more... 4. crash. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: apport-kde 2.23.1-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-1009.10-lowlatency 5.19.7 Uname: Linux 5.19.0-1009-lowlatency x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:1000:124:25603405:2022-11-30 02:13:38.032846897 -0500:2022-11-30 02:13:35.548841973 -0500:/var/crash/_usr_bin_avplayer.1000.crash CurrentDesktop: KDE Date: Wed Nov 30 03:11:50 2022 InstallationDate: Installed on 2022-11-29 (0 days ago) InstallationMedia: Ubuntu-Studio 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1998309/+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 1998321] Re: tzdata 2022g release
Hello Benjamin, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022g-0ubuntu0.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.
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998321] Re: tzdata 2022g release
Hello Benjamin, or anyone else affected,
Accepted tzdata into kinetic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022g-0ubuntu0.22.10.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-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. 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.
** Tags removed: verification-done verification-done-kinetic
** Tags added: verification-needed verification-needed-kinetic
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import datetime, timedelta
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1998497] [NEW] "Always on top" window prevents new windows from taking focus
Public bug reported: 1. Launch a terminal 2. Launch something from it, say 'xlogo &' 3. Put xlogo always on top by right clicking its title bar and selecting that option. 4. Back to the terminal, open a new window, preferentially something whose lack of input focus is evident, e.g. 'zenity --password'. Expected: New window has focus (you can type right away into zenity). Observed: Old window has focus. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libglib2.0-0 2.74.0-3 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:58:34 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998497 Title: "Always on top" window prevents new windows from taking focus Status in glib2.0 package in Ubuntu: New Bug description: 1. Launch a terminal 2. Launch something from it, say 'xlogo &' 3. Put xlogo always on top by right clicking its title bar and selecting that option. 4. Back to the terminal, open a new window, preferentially something whose lack of input focus is evident, e.g. 'zenity --password'. Expected: New window has focus (you can type right away into zenity). Observed: Old window has focus. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libglib2.0-0 2.74.0-3 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.475 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 1 12:58:34 2022 LiveMediaBuild: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1998497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1958019]
https://wiki.archlinux.org/title/DSDT#Using_modified_code: We should be able to override it. From here, using early patching should allow you to specify using a quirk to support CSC3551. From there's a question of using safe values in your override. Also, you won't have suspend/resume for the support for the amp chips with the Gen 6 unless you're using a 6.1 kernel. On 11/30/22 03:40, bugzilla-dae...@kernel.org wrote: > I wish the kernel guys weren't so dead set against loadable DSDTs. There's > still so many reasons why we need to be able to patch these ourselves and > there's no good reason to have to rebuild an entire kernel just to add > missing > table entries. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
Works for me too on 22.04 (for a Canon TS8350 on the network) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY 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.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY 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/cups/+bug/1973441/+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 828756] Re: getting "connection is untrusted" warnings
** Changed in: telepathy-gabble (Debian) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to p11-kit in Ubuntu. https://bugs.launchpad.net/bugs/828756 Title: getting "connection is untrusted" warnings Status in ca-certificates-java package in Ubuntu: Invalid Status in empathy package in Ubuntu: Invalid Status in icedtea-web package in Ubuntu: Invalid Status in p11-kit package in Ubuntu: Fix Released Status in p11-kit source package in Oneiric: Fix Released Status in telepathy-gabble package in Debian: Fix Released Bug description: Since updating to Oneiric, empathy is giving me "connection is untrusted" warning dialogs. For some reason, it's not verifying the certificate properly. For security reasons, this needs to get fixed. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 Architecture: amd64 Date: Thu Aug 18 09:36:06 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302) ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-08-16 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/828756/+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 1998325] Re: Please merge sysvinit 3.05-7 (main) from Debian unstable (main)
** Changed in: sysvinit (Ubuntu) Assignee: Julian Andres Klode (juliank) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998325 Title: Please merge sysvinit 3.05-7 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: Fix Released Bug description: Debian moved to a new upstream version 3.04 => 3.05. Since bionic, we only build sysvinit-utils because it is the only package marked [essential]. sysvinit-utils will surely gain more reverse depends because scripts that used to be provided by lsb-base are now provided by sysvinit-utils. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1998325] Re: Please merge sysvinit 3.05-7 (main) from Debian unstable (main)
Uploaded. ** Changed in: sysvinit (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: sysvinit (Ubuntu) Status: New => In Progress ** Changed in: sysvinit (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1998325 Title: Please merge sysvinit 3.05-7 (main) from Debian unstable (main) Status in sysvinit package in Ubuntu: Fix Released Bug description: Debian moved to a new upstream version 3.04 => 3.05. Since bionic, we only build sysvinit-utils because it is the only package marked [essential]. sysvinit-utils will surely gain more reverse depends because scripts that used to be provided by lsb-base are now provided by sysvinit-utils. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1998325/+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 1998488] Re: Wrong type annotation in apt.progress.text.AcquireProgress
I'm setting Lunar to fix released as the fix is in 2.5.0. Despite it not being released yet, we'd otherwise just forget about it. ** Changed in: python-apt (Ubuntu Jammy) Status: New => Triaged ** Changed in: python-apt (Ubuntu Kinetic) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998488 Title: Wrong type annotation in apt.progress.text.AcquireProgress Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Jammy: Triaged Status in python-apt source package in Kinetic: Triaged Status in python-apt source package in Lunar: Fix Released Bug description: [Impact] Type checking fails in CI [Test plan] Have CI type check successfully [Where problems could occur] It's only a comment *inside* the function, so not really anywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998488/+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 1998488] [NEW] Wrong type annotation in apt.progress.text.AcquireProgress
Public bug reported: [Impact] Type checking fails in CI [Test plan] Have CI type check successfully [Where problems could occur] It's only a comment *inside* the function, so not really anywhere. ** Affects: python-apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: python-apt (Ubuntu Jammy) Importance: Undecided Status: Triaged ** Affects: python-apt (Ubuntu Kinetic) Importance: Undecided Status: Triaged ** Affects: python-apt (Ubuntu Lunar) Importance: Undecided Status: Fix Released ** Also affects: python-apt (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998488 Title: Wrong type annotation in apt.progress.text.AcquireProgress Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Jammy: Triaged Status in python-apt source package in Kinetic: Triaged Status in python-apt source package in Lunar: Fix Released Bug description: [Impact] Type checking fails in CI [Test plan] Have CI type check successfully [Where problems could occur] It's only a comment *inside* the function, so not really anywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998488/+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 1998265] Re: OverFlow error when using cnf-extractor
** Description changed: + [Impact] + Large files can't be downloaded as we use a 32-bit integer in AcquireFile constructor, this breaks e.g. command-not-found generator: + I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. + + [Test plan] + I have included a test for the AcquireFile constructor to accept a large file size, and then a test that ensures it can read the file size. + + Run the autopkgtest suite. + + [Where problems could occur] + It could fail in other places now. + + [Other info] + Also including some auxiliary changes as we move back to proper upstream releases to enable testing, mostly around + + d/gbp.conf, .gitlab-ci.yml - being updated to point at right places + d/t/control - adding a missing test dependency + data/ - updated mirror lists + + The mirror lists are standard updates; the debian/tests/control change + is needed to enable testing on more minimal autopkgtest images (our images + accidentally include binutils); the other changes have zero impact on the Ubuntu infra or end user side as they only run during development. ** Changed in: python-apt (Ubuntu Focal) Status: New => In Progress ** Description changed: [Impact] Large files can't be downloaded as we use a 32-bit integer in AcquireFile constructor, this breaks e.g. command-not-found generator: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. [Test plan] I have included a test for the AcquireFile constructor to accept a large file size, and then a test that ensures it can read the file size. Run the autopkgtest suite. [Where problems could occur] It could fail in other places now. + For kinetic, the package was copied in from lunar without changes. This + upload is actually built in kinetic and hence there is additional + regression potential from toolchain changes. + [Other info] Also including some auxiliary changes as we move back to proper upstream releases to enable testing, mostly around d/gbp.conf, .gitlab-ci.yml - being updated to point at right places d/t/control - adding a missing test dependency data/ - updated mirror lists The mirror lists are standard updates; the debian/tests/control change is needed to enable testing on more minimal autopkgtest images (our images accidentally include binutils); the other changes have zero impact on the Ubuntu infra or end user side as they only run during development. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: In Progress Status in python-apt source package in Bionic: In Progress Status in python-apt source package in Focal: In Progress Status in python-apt source package in Jammy: New Status in python-apt source package in Kinetic: New Bug description: [Impact] Large files can't be downloaded as we use a 32-bit integer in
[Touch-packages] [Bug 1998321] Re: tzdata 2022g release
** Description changed:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets changed
in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed. If
those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
+
+ [Test case for releases >= 20.04 LTS]
+
+ from datetime import datetime, timedelta
+ from icu import ICUtzinfo, TimeZone
+ tz = ICUtzinfo(TimeZone.createTimeZone("America/Ciudad_Juarez"))
+ assert(tz.utcoffset(datetime(2022, 12, 1)) == timedelta(hours=-7))
+
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
--
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/1998321
Title:
tzdata 2022g release
Status in tzdata package in Ubuntu:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Jammy:
Fix Committed
Status in tzdata source package in Kinetic:
Fix Committed
Bug description:
The 2022g release contains the following changes:
* The northern edge of Chihuahua changes to US timekeeping.
* Much of Greenland stops changing clocks after March 2023.
* Fix some pre-1996 timestamps in northern Canada.
* C89 is now deprecated; please use C99 or later.
* Portability fixes for AIX, libintl, MS-Windows, musl, z/OS
* In C code, use more C23 features if available.
* C23 timegm now supported by default
* Fixes for unlikely integer overflows
Changes to future timestamps:
In the Mexican state of Chihuahua, the border strip near the US will
change to agree with nearby US locations on 2022-11-30. The strip's
western part, represented by Ciudad Juárez, switches from -06 all year
to -07/-06 with US DST rules, like El Paso, TX. The eastern part,
represented by Ojinaga, will observe US DST next year, like Presidio,
TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez
splits from America/Ojinaga.
Much of Greenland, represented by America/Nuuk, stops observing winter
time after March 2023, so its daylight saving time becomes standard
time. (Thanks to Jonas Nyrup and Jürgen Appel.)
ICU change: https://unicode-org.atlassian.net/browse/ICU-22217
CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[ Test Case for all releases ]
1) dpkg -s tzdata | grep ^Version
2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1
-> should have output, last dates should be in 2499
[Test case for releases >= 20.04 LTS]
from datetime import
[Touch-packages] [Bug 1998265] Re: OverFlow error when using cnf-extractor
** Changed in: python-apt (Ubuntu Bionic) Status: New => In Progress ** Also affects: python-apt (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: python-apt (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1998265 Title: OverFlow error when using cnf-extractor Status in python-apt package in Ubuntu: In Progress Status in python-apt source package in Bionic: In Progress Status in python-apt source package in Focal: New Status in python-apt source package in Jammy: New Status in python-apt source package in Kinetic: New Bug description: I'm trying to update the command-not-found indexes (bin/cnf-extract.py $MIRROR $suite $component $arch) on the production cnf extractor system (running bionic) and have encountered Tracebacks when generating them for Jammy and Lunar. This is causing the command not found indexes to be out of date for all(?) releases of Ubuntu. The lunar failure: Get:1 dotnet-sdk-6.0_6.0.111-0ubuntu3_amd64.deb [79.1 MB] Fetched 79.1 MB in 0s (0 B/s) Traceback (most recent call last):64... 7% File "./bin/cnf-extract.py", line 54, in mirror_root, suite, component, arch) File "/srv/cnf-extractor/extractor/extractor.py", line 174, in command_not_found_extract debpath = pkg.candidate.fetch_binary(destdir=tmpdir) File "/usr/lib/python3/dist-packages/apt/package.py", line 883, in fetch_binary self.size, base, destfile=destfile) OverflowError: signed integer is greater than maximum I'll get more context for the Jammy failure but it wouldn't surprise me if it was the same package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1998265/+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 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar
** Changed in: zlib (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-z-systems Status: New => Triaged ** 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/1998470 Title: re-add s390x vectorized crc32 support to zlib in lunar Status in Ubuntu on IBM z Systems: In Progress Status in zlib package in Ubuntu: Triaged Bug description: At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from Debian sid to Ubuntu lunar. At this time it was already clear that this new version is no longer compatible with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. Hence this patch was dropped and it was decided to backport (or better 'forward port'?) this vectorized crc32 implementation for s390x. https://launchpad.net/ubuntu/+source/zlib/+changelog The new patch is now available as crc32vx-v4: "s390x: vectorize crc32" https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839 This LP bug is now to track the re-integration of the vectorized crc32 implementation for s390x. So a few things needed to happen (from the changelog): * Re-add vectorized crc32 support for s390x by adding d/p/s390x-vectorize-crc32.patch (crc32vx-v4: s390x: vectorize crc32). This replaces the previously dropped patch: lp1932010-ibm-z-add-vectorized-crc32-implementation.patch * Remove option '--crc32-vx' for s390x in d/rules, that was previously just commented out, since it's no longer needed with the new s390x crc32 code. And since I bumped into a little build issue, I've also needed to: * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 due to unused "const char *endptr;". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+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 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar
Test builds of the updated package are currently running in this PPA: https://launchpad.net/~fheimes/+archive/ubuntu/lp1998470 ** Description changed: At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from Debian sid to Ubuntu lunar. At this time it was already clear that this new version is no longer compatible with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch - since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. + since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. Hence this patch was dropped and it was decided to backport (or better 'forward port'?) this vectorized crc32 implementation for s390x. + https://launchpad.net/ubuntu/+source/zlib/+changelog - This new patch is now available as + The new patch is now available as crc32vx-v4: "s390x: vectorize crc32" https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839 This LP bug is now to track the re-integration of the vectorized crc32 implementation for s390x. So a few things needed to happen (from the changelog): - * Re-add vectorized crc32 support for s390x by adding - d/p/s390x-vectorize-crc32.patch - (crc32vx-v4: s390x: vectorize crc32). - This replaces the previously dropped patch: - lp1932010-ibm-z-add-vectorized-crc32-implementation.patch - * Remove option '--crc32-vx' for s390x in d/rules, that was previously just - commented out, since it's no longer needed with the new s390x crc32 code. + * Re-add vectorized crc32 support for s390x by adding + d/p/s390x-vectorize-crc32.patch + (crc32vx-v4: s390x: vectorize crc32). + This replaces the previously dropped patch: + lp1932010-ibm-z-add-vectorized-crc32-implementation.patch + * Remove option '--crc32-vx' for s390x in d/rules, that was previously just + commented out, since it's no longer needed with the new s390x crc32 code. And since I bumped into a little build issue, I've also needed to: - * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 - due to unused "const char *endptr;". + * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 + due to unused "const char *endptr;". -- 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/1998470 Title: re-add s390x vectorized crc32 support to zlib in lunar Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from Debian sid to Ubuntu lunar. At this time it was already clear that this new version is no longer compatible with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. Hence this patch was dropped and it was decided to backport (or better 'forward port'?) this vectorized crc32 implementation for s390x. https://launchpad.net/ubuntu/+source/zlib/+changelog The new patch is now available as crc32vx-v4: "s390x: vectorize crc32" https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839 This LP bug is now to track the re-integration of the vectorized crc32 implementation for s390x. So a few things needed to happen (from the changelog): * Re-add vectorized crc32 support for s390x by adding d/p/s390x-vectorize-crc32.patch (crc32vx-v4: s390x: vectorize crc32). This replaces the previously dropped patch: lp1932010-ibm-z-add-vectorized-crc32-implementation.patch * Remove option '--crc32-vx' for s390x in d/rules, that was previously just commented out, since it's no longer needed with the new s390x crc32 code. And since I bumped into a little build issue, I've also needed to: * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 due to unused "const char *endptr;". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+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 1998444] Re: Backport security fix for CVE-2022-3970
** Changed in: tiff (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1998444 Title: Backport security fix for CVE-2022-3970 Status in tiff package in Ubuntu: In Progress Status in tiff source package in Bionic: New Status in tiff source package in Focal: New Status in tiff source package in Jammy: New Status in tiff source package in Kinetic: New Bug description: This CVE patch is desperately needed to fix a build failure caused by a crash in the testsuite of the current libreoffice/kinetic SRU Testing load file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff: *** stack smashing detected ***: terminated Fatal exception: Signal 6 Stack: /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2] /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc] /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a] /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636] /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386] /lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc] /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1] /lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10] /<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6] /<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5] /<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c] /<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07] /<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f] /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9] /<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5] Aborted (core dumped) make[4]: *** [/<>/solenv/gbuild/CppunitTest.mk:121: /<>/workdir/CppunitTest/vcl_filters_test.test] Error 134 For the log of the failed amd64 kinetic archive build, see https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.3-0ubuntu0.22.10.1/+build/24883181 For the log of the successful amd64 kinetic PPA build with the updated tiff present, see https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+build/24886085 Lunar already includes this fix with the last merge from debian
[Touch-packages] [Bug 1998470] [NEW] re-add s390x vectorized crc32 support to zlib in lunar
Public bug reported: At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from Debian sid to Ubuntu lunar. At this time it was already clear that this new version is no longer compatible with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. Hence this patch was dropped and it was decided to backport (or better 'forward port'?) this vectorized crc32 implementation for s390x. This new patch is now available as crc32vx-v4: "s390x: vectorize crc32" https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839 This LP bug is now to track the re-integration of the vectorized crc32 implementation for s390x. So a few things needed to happen (from the changelog): * Re-add vectorized crc32 support for s390x by adding d/p/s390x-vectorize-crc32.patch (crc32vx-v4: s390x: vectorize crc32). This replaces the previously dropped patch: lp1932010-ibm-z-add-vectorized-crc32-implementation.patch * Remove option '--crc32-vx' for s390x in d/rules, that was previously just commented out, since it's no longer needed with the new s390x crc32 code. And since I bumped into a little build issue, I've also needed to: * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 due to unused "const char *endptr;". ** Affects: ubuntu-z-systems Importance: Medium Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Affects: zlib (Ubuntu) Importance: Medium Assignee: Frank Heimes (fheimes) Status: New ** Tags: s390x ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/1998470 Title: re-add s390x vectorized crc32 support to zlib in lunar Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Bug description: At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from Debian sid to Ubuntu lunar. At this time it was already clear that this new version is no longer compatible with patch d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch since this depends on zlib upstream PR 335 which has been superseded by upstream PR 478 with significant refactoring. Hence this patch was dropped and it was decided to backport (or better 'forward port'?) this vectorized crc32 implementation for s390x. This new patch is now available as crc32vx-v4: "s390x: vectorize crc32" https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839 This LP bug is now to track the re-integration of the vectorized crc32 implementation for s390x. So a few things needed to happen (from the changelog): * Re-add vectorized crc32 support for s390x by adding d/p/s390x-vectorize-crc32.patch (crc32vx-v4: s390x: vectorize crc32). This replaces the previously dropped patch: lp1932010-ibm-z-add-vectorized-crc32-implementation.patch * Remove option '--crc32-vx' for s390x in d/rules, that was previously just commented out, since it's no longer needed with the new s390x crc32 code. And since I bumped into a little build issue, I've also needed to: * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390 due to unused "const char *endptr;". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1998470/+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 1971712] Re: Add support for Intel DG2
** Tags added: verification-done-kinetic -- 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/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Confirmed Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Committed Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1998321] Re: tzdata 2022g release
The ICU update for 2022g is available. I will to another round of SRU uploads referencing this bug. -- 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/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [ Test Case for all releases ] 1) dpkg -s tzdata | grep ^Version 2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1 -> should have output, last dates should be in 2499 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1998321/+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 1997979] Re: Merge grilo-plugins 0.3.15-1 from Debian unstable
This bug was fixed in the package grilo-plugins - 0.3.15-1ubuntu1 --- grilo-plugins (0.3.15-1ubuntu1) lunar; urgency=medium * Merge with Debian (LP: #1997979). Remaining change: - Split package into -base and -extra (Closes: #805609) grilo-plugins (0.3.15-1) unstable; urgency=medium [ Alberto Garcia ] * New upstream release. * debian/control: - Update debhelper-compat from 12 to 13 (Closes: #1003134). - Update Standards-Version to 4.6.1.0 (no changes). * debian/grilo-plugins-0.3.lintian-overrides: - Update format of hardening-no-fortify-functions. * debian/copyright: - Update copyright years. [ Debian Janitor ] * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on libgdata-dev, libglib2.0-dev, libgoa-1.0-dev and libtotem-plparser-dev. -- Nathan Pratta Teodosio Fri, 25 Nov 2022 11:31:46 -0300 ** Changed in: grilo-plugins (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 grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1997979 Title: Merge grilo-plugins 0.3.15-1 from Debian unstable Status in grilo-plugins package in Ubuntu: Fix Released Bug description: Built successfully locally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1997979/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise
22.10 with latest kernel at the moment (5.19.0-26-generic) speakers still do not work (hp envy 16 Alder Lake-P and Realtek ALC245) -- 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/1980937 Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise Status in alsa-driver package in Ubuntu: Confirmed Bug description: New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake- LP audio controller. When playing any audio, the internal speaker plays no sound except periodic loud crackling noise. The 3.5mm jack does not work either, producing the same craclking noise alongside some eletrical noise. HDMI audio skimmishly tested, but also gave no sound. Curiously, USB headphone (along with microphone) works perfectly, also the internal microphone. As attempts to fix the problem, I have tried the following separately, with no avail: - Installing some Ubuntu OEM version of the 5.17 kernel - Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject on github), reverted afterwards I found exactly the same problem reported in the Fedora community: https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086 As the pre-installed Windows has been destroyed, no further test on Windows has been done. Since USB headphone and internal microphone work, I think that there is no problem on the Intel Tiger Lake-LP controller and its driver. The bug probably lies elsewhere, like in the handling of ALC245 on this new laptop model. Thank you very much for your time and effort in advance. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Jul 7 10:59:22 2022 InstallationDate: Installed on 2022-06-29 (7 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fwjmath2810 F pulseaudio fwjmath 72467 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T37 Ver. 01.09.01 dmi.board.name: 8AB8 dmi.board.vendor: HP dmi.board.version: KBC Version 58.03.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 88.3 dmi.modalias: dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G8 Notebook PC dmi.product.sku: 6A3P3AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1998321] Re: tzdata 2022g release
Verified kinetic, jammy, focal, bionic: (kinetic)root@host:~# dpkg -s tzdata | grep ^Version Version: 2022g-0ubuntu0.22.10.0 (kinetic)root@host:~# zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1 America/Ciudad_Juarez Sun Nov 1 08:00:00 2499 UT = Sun Nov 1 01:00:00 2499 MST isdst=0 gmtoff=-25200 (jammy)root@host:~# dpkg -s tzdata | grep ^Version Version: 2022g-0ubuntu0.22.04.0 (jammy)root@host:~# zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1 America/Ciudad_Juarez Sun Nov 1 08:00:00 2499 UT = Sun Nov 1 01:00:00 2499 MST isdst=0 gmtoff=-25200 (focal)root@host:~# dpkg -s tzdata | grep ^Version Version: 2022g-0ubuntu0.20.04.0 (focal)root@host:~# zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1 America/Ciudad_Juarez Sun Nov 1 08:00:00 2499 UT = Sun Nov 1 01:00:00 2499 MST isdst=0 gmtoff=-25200 (bionic)root@host:~# dpkg -s tzdata | grep ^Version Version: 2022g-0ubuntu0.18.04 (bionic)root@host:~# zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1 America/Ciudad_Juarez Sun Nov 7 08:00:00 2038 UT = Sun Nov 7 01:00:00 2038 MST isdst=0 gmtoff=-25200 (bionic)root@host:~# diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) (bionic)root@deep-thought:~# ** Description changed: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US locations on 2022-11-30. The strip's western part, represented by Ciudad Juárez, switches from -06 all year to -07/-06 with US DST rules, like El Paso, TX. The eastern part, represented by Ojinaga, will observe US DST next year, like Presidio, TX. (Thanks to Heitor David Pinto.) A new Zone America/Ciudad_Juarez splits from America/Ojinaga. Much of Greenland, represented by America/Nuuk, stops observing winter time after March 2023, so its daylight saving time becomes standard time. (Thanks to Jonas Nyrup and Jürgen Appel.) ICU change: https://unicode-org.atlassian.net/browse/ICU-22217 CLDR: https://unicode-org.atlassian.net/browse/CLDR-16181 Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. [ Test Case for all releases ] - 1) zdump -v America/Ciudad_Juarez | grep -v NULL | tail + 1) dpkg -s tzdata | grep ^Version + 2) zdump -v America/Ciudad_Juarez | grep -v NULL | tail -n 1 -> should have output, last dates should be in 2499 [Test Case for releases <= 20.04 LTS] Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-jammy verification-done-kinetic -- 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/1998321 Title: tzdata 2022g release Status in tzdata package in Ubuntu: New Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Jammy: Fix Committed Status in tzdata source package in Kinetic: Fix Committed Bug description: The 2022g release contains the following changes: * The northern edge of Chihuahua changes to US timekeeping. * Much of Greenland stops changing clocks after March 2023. * Fix some pre-1996 timestamps in northern Canada. * C89 is now deprecated; please use C99 or later. * Portability fixes for AIX, libintl, MS-Windows, musl, z/OS * In C code, use more C23 features if available. * C23 timegm now supported by default * Fixes for unlikely integer overflows Changes to future timestamps: In the Mexican state of Chihuahua, the border strip near the US will change to agree with nearby US
[Touch-packages] [Bug 1996937] Re: "install vim failed"package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller ava
Terminal log: Ajout de « détournement de /usr/share/vim/vim82/doc/help.txt en /usr/share/vim/vim82/doc/help.txt.vim-tiny par vim-runtime » Ajout de « détournement de /usr/share/vim/vim82/doc/tags en /usr/share/vim/vim82/doc/tags.vim-tiny par vim-runtime » Dépaquetage de vim-runtime (2:8.2.3995-1ubuntu2.1) ... [1mdpkg:[0m erreur de traitement du paquet tzdata (--configure) : le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. Translation: Added "diversion of /usr/share/vim/vim82/doc/help.txt to /usr/share/vim/vim82/doc/help.txt.vim-tiny by vim-runtime" Added "diversion of /usr/share/vim/vim82/doc/tags to /usr/share/vim/vim82/doc/tags.vim-tiny by vim-runtime" Unpacking vim-runtime (2:8.2.3995-1ubuntu2.1) ... [1mdpkg: [0m error processing package tzdata (--configure): the package is in a really inconsistent state; you should reinstall it before attempting to configure it. -- 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/1996937 Title: "install vim failed"package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. Status in tzdata package in Ubuntu: New Bug description: trying to install vim but i occured an error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tzdata 2022f-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: vim-runtime:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Nov 17 20:00:11 2022 ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. InstallationDate: Installed on 2022-11-12 (4 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: tzdata Title: package tzdata 2022f-0ubuntu0.22.04.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le configurer. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1996937/+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 1997989] Re: Merge new Debian release
Thank you! After the riscv64 build passed inside your PPA as well I moved ahead and uploaded this merge, as it LGTM. A few small fixes that I applied before uploading: - rebased on top of 2.38.1-4, which was published in Debian the same day. (Small change, which seemed easy enough) - Fixed a typo in your d/changelog: We should be using "Merge from Debian unstable (LP: #1997989)" to actually close this merge bug automatically. Thanks! https://launchpad.net/ubuntu/+source/util-linux/2.38.1-4ubuntu1 ** Changed in: util-linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1997989 Title: Merge new Debian release Status in util-linux package in Ubuntu: Fix Committed Bug description: Debian has provided util-linux 2.38.1-3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1997989/+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 1998444] Re: Backport security fix for CVE-2022-3970
** Changed in: tiff (Ubuntu) Assignee: (unassigned) => David Fernandez Gonzalez (litios) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1998444 Title: Backport security fix for CVE-2022-3970 Status in tiff package in Ubuntu: New Status in tiff source package in Bionic: New Status in tiff source package in Focal: New Status in tiff source package in Jammy: New Status in tiff source package in Kinetic: New Bug description: This CVE patch is desperately needed to fix a build failure caused by a crash in the testsuite of the current libreoffice/kinetic SRU Testing load file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff: *** stack smashing detected ***: terminated Fatal exception: Signal 6 Stack: /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2] /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc] /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a] /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636] /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386] /lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc] /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1] /lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10] /<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6] /<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5] /<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c] /<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07] /<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f] /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9] /<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5] Aborted (core dumped) make[4]: *** [/<>/solenv/gbuild/CppunitTest.mk:121: /<>/workdir/CppunitTest/vcl_filters_test.test] Error 134 For the log of the failed amd64 kinetic archive build, see https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.3-0ubuntu0.22.10.1/+build/24883181 For the log of the successful amd64 kinetic PPA build with the updated tiff present, see https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+build/24886085 Lunar already includes this fix with the last merge from debian
[Touch-packages] [Bug 1998444] Re: Backport security fix for CVE-2022-3970
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1998444 Title: Backport security fix for CVE-2022-3970 Status in tiff package in Ubuntu: New Status in tiff source package in Bionic: New Status in tiff source package in Focal: New Status in tiff source package in Jammy: New Status in tiff source package in Kinetic: New Bug description: This CVE patch is desperately needed to fix a build failure caused by a crash in the testsuite of the current libreoffice/kinetic SRU Testing load file:///<>//vcl/qa/cppunit/graphicfilter/data/tiff/fail/CVE-2017-9936-1.tiff: *** stack smashing detected ***: terminated Fatal exception: Signal 6 Stack: /<>/instdir/program/libuno_sal.so.3(+0x417b2)[0x7fd45563a7b2] /<>/instdir/program/libuno_sal.so.3(+0x4196a)[0x7fd45563a96a] /lib/x86_64-linux-gnu/libc.so.6(+0x3bcf0)[0x7fd4550facf0] /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x11b)[0x7fd45515126b] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x16)[0x7fd4550fac46] /lib/x86_64-linux-gnu/libc.so.6(abort+0xd7)[0x7fd4550e17fc] /lib/x86_64-linux-gnu/libc.so.6(+0x850be)[0x7fd4551440be] /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x2a)[0x7fd4551ee66a] /lib/x86_64-linux-gnu/libc.so.6(+0x12f636)[0x7fd4551ee636] /lib/x86_64-linux-gnu/libtiff.so.5(+0x34386)[0x7fd44e8a3386] /lib/x86_64-linux-gnu/libtiff.so.5(_TIFFReadEncodedStripAndAllocBuffer+0xcc)[0x7fd44e8bc1cc] /lib/x86_64-linux-gnu/libtiff.so.5(+0x300e1)[0x7fd44e89f0e1] /lib/x86_64-linux-gnu/libtiff.so.5(TIFFReadRGBAImageOriented+0x100)[0x7fd44e8a2c10] /<>/instdir/program/libmergedlo.so(_Z23ImportTiffGraphicImportR8SvStreamR7Graphic+0x237)[0x7fd45367b357] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1be0d)[0x7fd44a1a1e0d] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest13recursiveScanENS_12filterStatusERKN3rtl8OUStringES5_S5_14SfxFilterFlags20SotClipboardFormatIdjb+0x679)[0x7fd44a142479] /<>/workdir/LinkTarget/CppunitTest/../Library/libunotest.so(_ZN4test11FiltersTest7testDirERKN3rtl8OUStringESt17basic_string_viewIDsSt11char_traitsIDsEES4_14SfxFilterFlags20SotClipboardFormatIdjb+0xd6)[0x7fd44a142fe6] /<>/workdir/LinkTarget/CppunitTest/libtest_vcl_filters_test.so(+0x1bc7b)[0x7fd44a1a1c7b] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(+0x1e4e6)[0x7fd4556844e6] /<>/workdir/LinkTarget/Library/unoexceptionprotector.so(+0x2835)[0x7fd4556ac835] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit16DefaultProtector7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x34)[0x7fd455684434] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit14ProtectorChain7protectERKNS_7FunctorERKNS_16ProtectorContextE+0x3b0)[0x7fd45567ea50] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7protectERKNS_7FunctorEPNS_4TestERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x63)[0x7fd455685be3] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit8TestCase3runEPNS_10TestResultE+0x124)[0x7fd45568eb24] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite15doRunChildTestsEPNS_10TestResultE+0x9d)[0x7fd45568484d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit13TestComposite3runEPNS_10TestResultE+0x3d)[0x7fd45568465d] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestResult7runTestEPNS_4TestE+0x27)[0x7fd455685077] /lib/x86_64-linux-gnu/libcppunit-1.15.so.1(_ZN7CppUnit10TestRunner3runERNS_10TestResultERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x55)[0x7fd45568b6a5] /<>/workdir/LinkTarget/Executable/cppunittester(+0x711c)[0x55d4d4a1411c] /<>/workdir/LinkTarget/Executable/cppunittester(+0x7c07)[0x55d4d4a14c07] /<>/workdir/LinkTarget/Executable/cppunittester(+0x537f)[0x55d4d4a1237f] /lib/x86_64-linux-gnu/libc.so.6(+0x23510)[0x7fd4550e2510] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x89)[0x7fd4550e25c9] /<>/workdir/LinkTarget/Executable/cppunittester(+0x53c5)[0x55d4d4a123c5] Aborted (core dumped) make[4]: *** [/<>/solenv/gbuild/CppunitTest.mk:121: /<>/workdir/CppunitTest/vcl_filters_test.test] Error 134 For the log of the failed amd64 kinetic archive build, see https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.3-0ubuntu0.22.10.1/+build/24883181 For the log of the successful amd64 kinetic PPA build with the updated tiff present, see https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+build/24886085 Lunar already includes this fix with the last merge from debian https://launchpad.net/ubuntu/+source/tiff/4.4.0-6ubuntu1 Presumably this fix is required for all
