[Touch-packages] [Bug 2017999] Autopkgtest regression report (python-tz/2022.7.1-3ubuntu0.1)
All autopkgtests for the newly accepted python-tz (2022.7.1-3ubuntu0.1) for lunar have finished running. The following regressions have been reported in tests triggered by the package: cinder/2:22.0.0-0ubuntu1.1 (armhf) ironic/1:21.4.0-0ubuntu1 (armhf) python-caldav/0.11.0-1 (arm64) senlin/1:15.0.0-0ubuntu1 (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/lunar/update_excuses.html#python-tz [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/2017999 Title: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency Status in python-tz package in Ubuntu: Fix Released Status in tzdata package in Ubuntu: Fix Released Status in python-tz source package in Focal: New Status in tzdata source package in Focal: New Status in python-tz source package in Jammy: New Status in tzdata source package in Jammy: New Status in python-tz source package in Kinetic: New Status in tzdata source package in Kinetic: New Status in python-tz source package in Lunar: Fix Committed Status in tzdata source package in Lunar: New Bug description: [ Impact ] Recent updates have been using `PACKRATDATA=backzone` in order to add all out-of-scope lower-quality pre-1970 data back that existed in earlier tzadata releases (see bug #2003797). However it also leads to time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol, and Pacific/Enderbury to change: compared to 2023c-0ubuntu0.22.04.0 - America/Ensenada->only dst changes until 2022 are shown - Atlantic/Jan_Mayen->now valid data is shown - Europe/Tiraspol->only dst changes until 2010 are shown [ Test Plan ] Add an autopkgtest test case for post-1970 symlink consistency: Check that the timezones for today and in half a year (= to cover DST changes) do not change compared to building them without `PACKRATDATA=backzone`. The mentioned timezones that differed can also be tested manually. Running following commands should have the same output (the output mentioned here is from tzdata 2023c-0ubuntu0.22.04.1): ``` $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z" Fri Apr 28 05:49:00 PST 2023 $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z" Fri Apr 28 12:49:00 -01 2023 $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z" Fri Apr 28 16:49:00 MSK 2023 ``` [ Where problems could occur ] Timezone data could be wrong. Systems with incorrect timezone set may observe unexpected time shift when updating the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2019904] [NEW] package libgstreamer-plugins-bad1.0-0 1.20.3-0ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.
Public bug reported: Los siguientes paquetes tienen dependencias incumplidas: libcc1-0 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a ser instalado libitm1 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a ser instalado liblsan0 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a ser instalado libubsan1 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a ser instalado E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgstreamer-plugins-bad1.0-0 1.20.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 16 17:57:50 2023 ErrorMessage: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', que está también en el paquete libgstreamer-plugins-good1.0-0:amd64 1.20.3-0ubuntu1 InstallationDate: Installed on 2023-05-16 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: gst-plugins-bad1.0 Title: package libgstreamer-plugins-bad1.0-0 1.20.3-0ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', que está también en el paquete libgstreamer-plugins-good1.0-0:amd64 1.20.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2019904 Title: package libgstreamer-plugins-bad1.0-0 1.20.3-0ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux- gnu/libgstbasecamerabinsrc-1.0.so.0', que está también en el paquete libgstreamer-plugins-good1.0-0:amd64 1.20.3-0ubuntu1 Status in gst-plugins-bad1.0 package in Ubuntu: New Bug description: Los siguientes paquetes tienen dependencias incumplidas: libcc1-0 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a ser instalado libitm1 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a ser instalado liblsan0 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a ser instalado libubsan1 : Depende: gcc-12-base (= 12.1.0-2ubuntu1~22.04) pero 12.2.0-14 va a ser instalado E: No se pudieron corregir los problemas, usted ha retenido paquetes rotos. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgstreamer-plugins-bad1.0-0 1.20.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 16 17:57:50 2023 ErrorMessage: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', que está también en el paquete libgstreamer-plugins-good1.0-0:amd64 1.20.3-0ubuntu1 InstallationDate: Installed on 2023-05-16 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.9 SourcePackage: gst-plugins-bad1.0 Title: package libgstreamer-plugins-bad1.0-0 1.20.3-0ubuntu1 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', que está también en el paquete libgstreamer-plugins-good1.0-0:amd64 1.20.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2019904/+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 1992454] Autopkgtest regression report (iptables/1.8.4-3ubuntu2.1)
All autopkgtests for the newly accepted iptables (1.8.4-3ubuntu2.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nova/2:21.2.4-0ubuntu2.3 (armhf) systemd/245.4-4ubuntu3.21 (armhf, ppc64el, s390x) ufw/0.36-6ubuntu1 (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/focal/update_excuses.html#iptables [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 iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Committed Status in iptables source package in Focal: Fix Committed Status in iptables source package in Jammy: Fix Committed Status in iptables source package in Kinetic: Fix Committed Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy - Kinetic: iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 Alternatively, this test has been added to the DEP8 list of tests, and will be executed automatically once the package is accepted into proposed. The DEP8 logs can be inspected for its run. Look for a test named "0006rename-segfault". [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] The patch is also applied to lunar and mantic, but is fixed in upstream's 1.8.9 release which so far is only in debian testing/unstable. This is being uploaded together with test fixes from bug #1992454 (bionic-specific) and bug #2019023 (focal-specific), which were found and fixed while trying out the DEP8 runs for this package. To manage notifications about this bug go to:
[Touch-packages] [Bug 2019023] Autopkgtest regression report (iptables/1.8.4-3ubuntu2.1)
All autopkgtests for the newly accepted iptables (1.8.4-3ubuntu2.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nova/2:21.2.4-0ubuntu2.3 (armhf) systemd/245.4-4ubuntu3.21 (armhf, ppc64el, s390x) ufw/0.36-6ubuntu1 (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/focal/update_excuses.html#iptables [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 iptables in Ubuntu. https://bugs.launchpad.net/bugs/2019023 Title: Fix shell test suite Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Focal: Fix Committed Bug description: [ Impact ] The shell test suite (iptables/tests/shell/run-tests.sh) is currently failing on the firewalld tests in focal only: W: [FAILED] ././testcases/firewalld-restore/0001-firewalld_0: expected 0 but got 1 W: [FAILED] ././testcases/firewalld-restore/0002-firewalld-restart_0: expected 0 but got 1 After some troubleshooting, it turns out this is happening because of an unsorted order in the output of iptables-save, which was fixed[1] in later releases of iptables. The code was trying to compensate for that, but there was a small mistake[2] in a case/esac globbing: case "$XT_MULTI" in -*/xtables-nft-multi) +*xtables-nft-multi) The upstream fix includes other similar changes in other tests, but in the case of focal, the above is the minimal fix needed. Note that this shell test suite is not being run in focal, just in later ubuntu releases. But since the fix for #1992454 is adding such a test, I decided to fix the shell test run and add it to the existing DEP8 tests for focal via this bug, so we have test parity between focal and later ubuntu releases. 1. https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef 2. https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6 [ Test Plan ] Verify that the DEP8 tests now include a run-tests.sh test suite, and that it passes. [ Where problems could occur ] If the fix is incorrect, it would affect only the already-failing firewalld test. But in addition to fixing that test, we are now also including a full test run of all shell tests, something which wasn't being done for focal until now. While these tests are passing now, they could fail in a future iptables SRU, or turn out to be flaky. They are being run in ubuntu releases after focal, though, so that is a good sign. [ Other Info ] This fix is being included in the same upload as bug #1992454. [ Original Description ] The shell test suite (iptables/tests/shell/run-tests.sh) is currently failing on the firewalld tests: W: [FAILED] ././testcases/firewalld-restore/0001-firewalld_0: expected 0 but got 1 W: [FAILED] ././testcases/firewalld-restore/0002-firewalld-restart_0: expected 0 but got 1 After some troubleshooting, it turns out this is happening because of an unsorted order in the output of iptables-save, which was fixed[1] in later releases of iptables. The code was trying to compensate for that, but there was a small mistake[2] in a case/esac globbing: case "$XT_MULTI" in -*/xtables-nft-multi) +*xtables-nft-multi) 1. https://git.netfilter.org/iptables/commit/?id=e28cf12cf50b9e2e0114f04331635fc122cb8aef 2. https://git.netfilter.org/iptables/commit/?id=2b2b7948c1960ba4680677664ff58477be869de6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/2019023/+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 1302192] Re: capabilities not preserved on installation
I thought as part of this work we agreed to always unpack tar with xattrs, but i'm not sure how to check if this was done or in place. will investigate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1302192 Title: capabilities not preserved on installation Status in attr package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Confirmed Status in live-installer package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in attr source package in Trusty: Fix Released Status in iputils source package in Trusty: Confirmed Status in live-installer source package in Trusty: Fix Released Status in ubiquity source package in Trusty: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Bug description: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 time=52.2 ms --- kubuntu.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms [~]$ Related bugs: bug 1313550: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+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 1992454] Re: iptables: segfault when renaming a chain
I cleared the DEP8 failures: - nova: retry fixed it - west-chamber/i386: migration-reference/0 is also failing, so that cleared it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1992454 Title: iptables: segfault when renaming a chain Status in iptables package in Ubuntu: Fix Released Status in iptables source package in Bionic: Fix Committed Status in iptables source package in Focal: Fix Committed Status in iptables source package in Jammy: Fix Committed Status in iptables source package in Kinetic: Fix Committed Bug description: [ Impact ] * An explanation of the effects of the bug on users This is the description for the upstream fix of this bug[1] : This is an odd bug: If the number of chains is right and one renames the last one in the list, libiptc dereferences a NULL pointer. * justification for backporting the fix to the stable release. Without this patch, users may experience segmentation fault when using the following versions of iptables : - Bionic : iptables - Focal : iptables - Jammy : iptables-legacy - Kinetic: iptables-legacy * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. The upstream fix adjust the size of the chain_index if the element is the last chain in the list. [1] http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f [ Test Plan ] * detailed instructions how to reproduce the bug The following code (adapted from the upstream commit to work on Kinetic) may be used to reproduce the issue : 8< #!/bin/bash # # Cover for a bug in libiptc: # - the chain 'node-98-tmp' is the last in the list sorted by name # - there are 81 chains in total, so three chain index buckets # - the last index bucket contains only the 'node-98-tmp' chain # => rename temporarily removes it from the bucket, leaving a NULL bucket # behind which is dereferenced later when inserting the chain again with new # name again ( echo "*filter" for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 node-92 node-93 node-95 node-98-tmp; do echo ":$chain - [0:0]" done echo "COMMIT" ) | $XT_MULTI iptables-legacy-restore $XT_MULTI iptables-legacy -E node-98-tmp node-98 exit $? >8 Alternatively, this test has been added to the DEP8 list of tests, and will be executed automatically once the package is accepted into proposed. The DEP8 logs can be inspected for its run. Look for a test named "0006rename-segfault". [ Where problems could occur ] For Jammy and onward, only users of the -legacy commands may be affected. Since Jammy, iptables uses the new nft libraries which are not affected by the bug. For Bionic and Focal users, the regular iptables command is affected by the change. As stated in the manpage : E, --rename-chain old-chain new-chain Rename the user specified chain to the user supplied name. This is cosmetic, and has no effect on the structure of the table. In case of a problem, only the modification of the name would be affected as this is clearly outlined as a cosmetic only change. [ Other Info ] The patch is also applied to lunar and mantic, but is fixed in upstream's 1.8.9 release which so far is only in debian testing/unstable. This is being uploaded together with test fixes from bug #1992454 (bionic-specific) and bug #2019023 (focal-specific), which were found and fixed while trying out the DEP8 runs for this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1992454/+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 1980239] Proposed package upload rejected
An upload of gst-plugins-ugly1.0 to jammy-proposed has been rejected from the upload queue for the following reason: "Request for test cases on gst-plugins-ugly1.0 has gone unanswered since last July". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980239 Title: Update gstreamer to 1.20.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Jammy: Fix Released Status in gst-plugins-bad1.0 source package in Jammy: Fix Released Status in gst-plugins-good1.0 source package in Jammy: Fix Released Status in gst-plugins-ugly1.0 source package in Jammy: In Progress Status in gst-python1.0 source package in Jammy: Won't Fix Status in gst-rtsp-server1.0 source package in Jammy: In Progress Status in gstreamer-editing-services1.0 source package in Jammy: Incomplete Status in gstreamer-vaapi source package in Jammy: Triaged Status in gstreamer1.0 source package in Jammy: Fix Released Bug description: Impact -- Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two bugfix stable releases. https://gstreamer.freedesktop.org/releases/1.20/#1.20.2 https://gstreamer.freedesktop.org/releases/1.20/#1.20.3 Test Case 1 --- We now run upstream's test suite for most gstreamer components at build time and fail the build for errors on our key desktop architectures, amd64 & arm64. Ensure the builds succeeed. Test Case 2 --- Play a variety of videos in Totem. Play a variety of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. What Could Go Wrong --- If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1980239/+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 1980239] Proposed package upload rejected
An upload of gst-python1.0 to jammy-proposed has been rejected from the upload queue for the following reason: "rejected as discussed on the bug". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1980239 Title: Update gstreamer to 1.20.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Jammy: Fix Released Status in gst-plugins-bad1.0 source package in Jammy: Fix Released Status in gst-plugins-good1.0 source package in Jammy: Fix Released Status in gst-plugins-ugly1.0 source package in Jammy: In Progress Status in gst-python1.0 source package in Jammy: Won't Fix Status in gst-rtsp-server1.0 source package in Jammy: In Progress Status in gstreamer-editing-services1.0 source package in Jammy: Incomplete Status in gstreamer-vaapi source package in Jammy: Triaged Status in gstreamer1.0 source package in Jammy: Fix Released Bug description: Impact -- Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two bugfix stable releases. https://gstreamer.freedesktop.org/releases/1.20/#1.20.2 https://gstreamer.freedesktop.org/releases/1.20/#1.20.3 Test Case 1 --- We now run upstream's test suite for most gstreamer components at build time and fail the build for errors on our key desktop architectures, amd64 & arm64. Ensure the builds succeeed. Test Case 2 --- Play a variety of videos in Totem. Play a variety of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. What Could Go Wrong --- If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1980239/+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 2018538] Re: All PDFs when printed come out mirror image
Affects my Brother QL-800 label printer too, just after the upgrade to 23.04. My Xerox Phaser-3010 printer is fine although connected to the same computer. Setting the printer to mirror-print in settings won't help. -- 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/2018538 Title: All PDFs when printed come out mirror image Status in cups package in Ubuntu: Confirmed Bug description: Since updating to Ubuntu 23.04. Whenever I try to print a PDF (regardless of application the PDF is open in) it will print the PDF in mirror image. If I enable printing mirror image in the settings, every other page become mirror image as instead. (I'm printing double sided/long edge print, so one side is normal and the other side becomes mirror image when I do this). I'm trying to print to a HP Colour LaserJet CP2025dn Note: If I print from my second device when it was running Ubuntu 22.10 it would print normally, but as soon as I updated it to 23.04, it started having the same issue as well. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 4 20:31:48 2023 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-10-22 (194 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2018538/+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 1979258] Re: lxc: lxc-test-parse-config-file failed (failed to set config item)
I've sent a fix related to this issue: https://github.com/lxc/lxc/commit/8575ffeb7fc04b96e1d7bc736afb46670c5f7631 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1979258 Title: lxc: lxc-test-parse-config-file failed (failed to set config item) Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Status in lxc source package in Jammy: New Bug description: With bug 1943441 (expected value and retrieved value do not match) fixed with lxc 1:4.0.12-0ubuntu1 on Jammy (still exist on F / I) Now this test on Jammy with lxc 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1 will fail with: Running '/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file' parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.selinux.context" to "system_u:system_r:lxc_t:s0:c22" parse_config_file.c: 49: set_get_compare_clear_save_load: failed to set config item "lxc.seccomp.profile" to "/some/seccomp/file" parse_config_file.c: 580: main: lxc.seccomp.profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1979258/+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 2018656] Re: login process frozen in between username and password
This seems to be logged after entering username and clicking next: May 16 19:02:28 maunium kernel: WebKitWebProces[560981]: segfault at 563a37787e6d ip 563a37787e6d sp 7ffea85fdc98 error 14 in WebKitWebProcess[563f5260e000+1000] likely on CPU 15 (core 7, socket 0) May 16 19:02:28 maunium kernel: Code: Unable to access opcode bytes at 0x563a37787e43. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2018656 Title: login process frozen in between username and password Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: MY SYSTEM No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 gnome-online-accounts: Installed: 3.48.0-1 Candidate: 3.48.0-1 Version table: *** 3.48.0-1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I have tested this on my desktop running 23.04 on Intel I-9, and the second desktop running the same (23.04) but on Intel I-7, and both of them show the same problem. -PROBLEM--- When I entered my email address in my Google account, I could provide my email address, and after I clicked on the following form to enter my password. The form was able to pick up my email address and moved to the following form for password entry; it just froze in between. Sometimes, the password form could pick up the first keyboard character but never go past 2nd character. Sometimes, it just froze without being able to pick up the first keyboard character. Then a bit later, the whole box of gnome-online-accounts blacks out. Closing with X didn't work, so I had to xkill the app. -TYPICAL BEHAVIOR--- Usually, on 22.04, I never had a problem adding online accounts, particularly for Google accounts. The first form asked for my email address, and quickly moved on to the following form asking for a password. Once the password is accepted, it will move on to the next form requesting my authorization for GNOME to connect to my account on Google before adding it to my Ubuntu system (I'd see the drive folder on the bar on Nautilus). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-online-accounts 3.48.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 6 13:51:07 2023 InstallationDate: Installed on 2023-05-04 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2018656/+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 2011458] Autopkgtest regression report (openssh/1:9.0p1-1ubuntu7.2)
All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu7.2) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.50.2-2 (ppc64el) hg-git/0.10.4-3 (amd64, arm64, armhf, ppc64el, s390x) nova/3:26.1.0-0ubuntu2.1 (armhf) piuparts/1.1.5 (amd64, arm64, ppc64el, s390x) sbuild/0.83.1ubuntu1 (amd64, arm64, ppc64el, s390x) tinyssh/20190101-1ubuntu1 (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#openssh [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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/2011458 Title: ssh fails to rebind when it is killed with -HUP Status in openssh package in Ubuntu: Fix Committed Status in openssh source package in Kinetic: Fix Committed Status in openssh source package in Lunar: Fix Committed Bug description: [Impact] The sshd re-execution logic is generally broken with systemd socket activation, which means that (1) sshd fails when it is told to re-exec via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in debug mode. [Test Case] (1) Test systemctl reload ssh: * On a machine with openssh-server installed, make a connection to localhost to activate ssh.service (the connection does not need to be complete, so you can just say "no" at the host key verification stage): $ ssh localhost [...] * Send SIGHUP to sshd by calling systemctl reload ssh: $ systemctl reload ssh * Check the service state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s ago Duration: 2min 44.132s TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS) Main PID: 1112 (code=exited, status=255/EXCEPTION) CPU: 79ms Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 [preauth] Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell server... Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting. Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell server. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: Address already in use. Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address. Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, code=exited, status=255/EXCEPTION Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'. * On an affected machine, the service will fail as shown above. (2) Test debug mode: * On a machine with openssh-server installed, edit /etc/default/ssh to configure debug mode for sshd: $ cat /etc/default/ssh # Default settings for openssh-server. This file is sourced by /bin/sh from # /etc/init.d/ssh. # Options to pass to sshd SSHD_OPTS=-ddd * Attempt to make a connection to localhost: $ ssh localhost kex_exchange_identification: read: Connection reset by peer Connection reset by 127.0.0.1 port 22 * On an affected machine, the attempt will fail as shown above, and the service will be in a failed state: $ systemctl status ssh × ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.service.d └─00-socket.conf Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 2min 27s ago Duration: 5ms TriggeredBy: ● ssh.socket Docs: man:sshd(8) man:sshd_config(5) Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS) Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255/EXCEPTION) Main PID: 1167 (code=exited, status=255/EXCEPTION) CPU: 40ms Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22. Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is
[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems
** Also affects: util-linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: util-linux (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: New Status in util-linux source package in Jammy: New Status in util-linux source package in Lunar: New Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 1951018] Re: No ability to discern IPv4 vs IPv6 rules through Python
Thank you for reporting a bug in ufw. I've committed a fix for this to add get_rules_ipv4() and get_rules_ipv6(). ** Changed in: ufw Importance: Undecided => Wishlist ** Changed in: ufw Status: New => Fix Committed ** Changed in: ufw Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: ufw (Ubuntu) Status: New => Triaged ** Changed in: ufw (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1951018 Title: No ability to discern IPv4 vs IPv6 rules through Python Status in ufw: Fix Committed Status in ufw package in Ubuntu: Triaged Bug description: Version: ufw 0.36 Ubuntu Version: 20.04.3 LTS There doesn't appear to be a Python method for accessing IPv4 and IPv6 rules in a distinguishable manner. In the source code (root/src/backend.py) there is an object that stores IPv4 and IPv6 rules in separate lists. Those lists are then accessed with the following method: def get_rules(self): '''Return list of all rules''' return self.rules + self.rules6 The issue with this is that the returned list doesn't contain an indication of what IP version each item corresponds to and would display something like the following. 1 allow 22/tcp 2 allow 80 3 allow 443 4 allow 22/tcp 5 allow 80 6 allow 443 I don't currently see a way to distinguish between IPv4 and IPv6 rules other than accessing the lists in the backend object directly (but I don't think this is best practice). E.g.: rules_ipv4 = backend.rules rules_ipv6 = backend.rules6 One possible fix would be to add functions that return only the IPv4 or IPv6 rules. E.g.: def get_rules_ipv4(self): '''Return list of all ipv4 rules''' return self.rules def get_rules_ipv6(self): '''Return list of all ipv6 rules''' return self.rules6 To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1951018/+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 2000798] Re: cannot connect to K380 bluetooth keyboard
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2000798 Title: cannot connect to K380 bluetooth keyboard Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Had trouble connecting my K380 keyboard with the laptop (previously used it without issues), unpaired and now I can no longer pair it. Other bluetooth devices work with this particular laptop (mouse, earbuds), the keyboard works flawlessly with a different laptop (running the same Ubuntu 20.04 OS) and an Android phone. Used bluetoothctl to peek under the hood and got nowhere after turning scan on on the controller and activating the keyboard: [NEW] Device [...mac address of the keyboard...] Keyboard K380 [CHG] Device [...mac address of the keyboard...] Connected: no [DEL] Device [...mac address of the keyboard...] Keyboard K380 After this action, I get: # connect [...mac address of the keyboard...] Device [...mac address of the keyboard...] not available When I activate the keyboard (by pressing any key on it while it's turned on), in the bluetooth settings GUI tool I see the keyboard appear for a fraction of a second in the list of unpaired devices and then it disappears. Help? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Dec 30 19:41:41 2022 InstallationDate: Installed on 2022-11-03 (57 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems LAPKC71E ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: KCTGL357.0037.2021.0712.0948 dmi.board.name: LAPKC71E dmi.board.vendor: Intel Corporation dmi.board.version: M1-402 dmi.chassis.type: 10 dmi.chassis.vendor: Intel(R) Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000: dmi.product.family: KC dmi.product.name: LAPKC71E dmi.product.sku: BKC71EBFB6000 dmi.product.version: M38559-402 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 20:1E:88:3C:4C:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:221779 acl:5063 sco:0 events:6018 errors:0 TX bytes:785416 acl:104 sco:0 commands:4168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes
ad. 1 not sure whether that's the one but I only see google chrome beside -rw-r- 1 mastier whoopsie 11313793 May 15 17:43 _usr_bin_gnome-control-center.1000.crash -rw-r--r-- 1 mastier whoopsie0 May 15 17:43 _usr_bin_gnome-control-center.1000.upload -rw--- 1 whoopsie whoopsie 37 May 15 17:43 _usr_bin_gnome-control-center.1000.uploaded it was sent ubuntu-bug /var/crash/_usr_bin_gnome-control-center.1000.crash ok, I run now from the console and click to authorize new google account mastier@drakkar:~$ gnome-control-center Segmentation fault (core dumped) mastier@drakkar:~$ sudo cat /var/lib/whoopsie/whoopsie-id 9dd61bf1171ac3761d445e300092a9cdcc1c72aef677e03db46fe3494f040a7ad1798ce8986311da05f2e54c89013eb395d3a9942206f177c01b5cae5fc72c95 mastier@drakkar:~$ ls -la /var/crash/ total 28356 drwxrwsrwt 2 root whoopsie8 May 16 13:41 ./ drwxr-xr-x 15 root root 17 Nov 20 15:20 ../ -rw-r- 1 mastier whoopsie 19583853 May 16 01:58 _opt_google_chrome_chrome.1000.crash -rw-r--r-- 1 mastier whoopsie0 May 16 01:58 _opt_google_chrome_chrome.1000.upload -rw--- 1 whoopsie whoopsie5 May 16 01:58 _opt_google_chrome_chrome.1000.uploaded -rw-r- 1 mastier whoopsie 11339816 May 16 13:39 _usr_bin_gnome-control-center.1000.crash -rw-r--r-- 1 mastier whoopsie0 May 16 13:39 _usr_bin_gnome-control-center.1000.upload -rw--- 1 whoopsie whoopsie 37 May 16 13:39 _usr_bin_gnome-control-center.1000.uploaded new file appeared Seems crucial issue, can haz fix asap, plz ? ;-) I was ablwe to send it mastier@drakkar:~$ ubuntu-bug /var/crash/_usr_bin_gnome-control-center.1000.crash mastier@drakkar:~$ echo $? 0 Ok, so it seems the gnome-controler-center crashes https://errors.ubuntu.com/user/9dd61bf1171ac3761d445e300092a9cdcc1c72aef677e03db46fe3494f040a7ad1798ce8986311da05f2e54c89013eb395d3a9942206f177c01b5cae5fc72c95 ** Changed in: gnome-online-accounts (Ubuntu) Status: Incomplete => New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2019739 Title: Cannot reauthorize Google account or authorize again. The app crashes Status in gnome-control-center package in Ubuntu: New Status in gnome-online-accounts package in Ubuntu: New Bug description: As in title I tried to relogin, The window prompt appears and quickly exits and nothing happens. Still cannot not logged in. Have to remove account and sign in again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-online-accounts 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 15 17:45:34 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019739/+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 2019856] [NEW] Add missing ARM-cores to support Grace-based systems
Public bug reported: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2019856 Title: Add missing ARM-cores to support Grace-based systems Status in util-linux package in Ubuntu: New Bug description: [Impact] When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't report a model name: Vendor ID: ARM Model: 0 [Fix] Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. The commit below adds the specific codes missing from Jammy's version. https://github.com/util-linux/util- linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740 [Evidence] When upstream code is compiled, output of lscpu is correctly displayed: Vendor ID: ARM Model name: Neoverse-V2 [What Could Go Wrong] The fix does not apply directly to Jammy's version, as other commits change sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to the list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Confirmed Bug description: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Confirmed Bug description: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 2018656] Re: login process frozen in between username and password
Thank you for your bug report. Could you do $ journalctl -f then trigger the bug and see if any error is printed in the journal log? ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-online-accounts (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2018656 Title: login process frozen in between username and password Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: MY SYSTEM No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 gnome-online-accounts: Installed: 3.48.0-1 Candidate: 3.48.0-1 Version table: *** 3.48.0-1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status I have tested this on my desktop running 23.04 on Intel I-9, and the second desktop running the same (23.04) but on Intel I-7, and both of them show the same problem. -PROBLEM--- When I entered my email address in my Google account, I could provide my email address, and after I clicked on the following form to enter my password. The form was able to pick up my email address and moved to the following form for password entry; it just froze in between. Sometimes, the password form could pick up the first keyboard character but never go past 2nd character. Sometimes, it just froze without being able to pick up the first keyboard character. Then a bit later, the whole box of gnome-online-accounts blacks out. Closing with X didn't work, so I had to xkill the app. -TYPICAL BEHAVIOR--- Usually, on 22.04, I never had a problem adding online accounts, particularly for Google accounts. The first form asked for my email address, and quickly moved on to the following form asking for a password. Once the password is accepted, it will move on to the next form requesting my authorization for GNOME to connect to my account on Google before adding it to my Ubuntu system (I'd see the drive folder on the bar on Nautilus). ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-online-accounts 3.48.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 6 13:51:07 2023 InstallationDate: Installed on 2023-05-04 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2018656/+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 2019746] Re: package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez package pre-removal script subprocess returned error exit status 1
Thank you for your bug report. Could you give some details on your system? The error is > Failed to stop bluetooth.service: Unit bluetooth.service not loaded. it seems bluetooth isn't active. It also look from the report that you have the bluez snap installed? Did you disable the bluetooth deb service yourself? ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2019746 Title: package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez package pre-removal script subprocess returned error exit status 1 Status in bluez package in Ubuntu: Incomplete Bug description: adding import of OBD with these packages as requirements, but are in constrast to each other. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: pulseaudio-module-bluetooth:amd64: Remove gnome-bluetooth:amd64: Remove bluez:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon May 15 13:30:12 2023 DpkgTerminalLog: Removing pulseaudio-module-bluetooth (1:15.99.1+dfsg1-1ubuntu2.1) ... Removing gnome-bluetooth (3.34.5-8) ... Removing bluez (5.64-0ubuntu1) ... Failed to stop bluetooth.service: Unit bluetooth.service not loaded. invoke-rc.d: initscript bluetooth, action "stop" failed. ErrorMessage: installed bluez package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2023-01-23 (112 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) InterestingModules: bluetooth MachineType: Gateway NE56R ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 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.9 Snap.Changes: ID Status Spawn Ready Summary 27 Done2023-05-14T20:11:56-04:00 2023-05-14T20:13:10-04:00 Install "bluez" snap SourcePackage: bluez Title: package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.release: 2.7 dmi.bios.vendor: Gateway dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EG50_HC_HR dmi.board.vendor: Gateway dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: V2.07 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnGateway:bvrV2.07:bd10/15/2012:br2.7:efr0.0:svnGateway:pnNE56R:pvrV2.07:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnGateway:ct10:cvrV2.07:skuNE56R_0649_V2.07: dmi.product.family: Type1Family dmi.product.name: NE56R dmi.product.sku: NE56R_0649_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Gateway hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2019746/+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 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2019739 Title: Cannot reauthorize Google account or authorize again. The app crashes Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: As in title I tried to relogin, The window prompt appears and quickly exits and nothing happens. Still cannot not logged in. Have to remove account and sign in again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-online-accounts 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 15 17:45:34 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2019739/+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 2019424] Re: Heimdal can be synced
@Steve / @Vorlon As outlined above we still can't see the diff in dependencies due to LTO. But I'm sure you have seen it or you wouldn't have said so and we want to spot where in our work the mistake was ... Therefore let me ask - was that a local build that you did or is that somewhere we could have a look at for comparison? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2019424 Title: Heimdal can be synced Status in heimdal package in Ubuntu: Confirmed Bug description: After heimdal merge process, I was trying to figure out if the delta that is still not dropped is required or not. So, to test it, I have created 2 PPAs, one in which lto is disabled, and the second one, where the lto is enabled. I have built them and downloaded the debs for i386 and amd64. Then I have compared amd64 deb from PPA1 with amd64 deb from PPA2. The same story with i386. The binary dependencies were identical. There is no difference between the files. So in that case, the delta can possibly be dropped. The package has already been merged again, with the change: heimdal (7.8.git20221117.28daf24+dfsg-2ubuntu1) mantic; urgency=low * Merge from Debian unstable. Remaining changes: - d/rules: Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different than i386 resulting in different files on amd64 and i386. -- Steve Langasek Tue, 02 May 2023 09:56:10 +0200 heimdal (7.8.git20221117.28daf24+dfsg-1ubuntu1) lunar; urgency=low * Merge from Debian unstable. Remaining changes: - d/rules: Disable lto, to regain dep on roken, otherwise dependencies on amd64 are different than i386 resulting in different files on amd64 and i386. (LP #1934936) -- Steve Langasek Tue, 24 Jan 2023 19:14:54 -0800 Due to this, syncpackage doesn't run. The package can be sync'd next time it comes up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2019424/+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 2019424] Re: Heimdal can be synced
Hmm - odd, Michal has checked the files and the build logs as he outlined above. And in addition to all those checks being done, if we just grep for all final dependencies and compare there is no difference (other than a glibc min version level). I know names are not too helpful: - ~ppa1 = LTO-off - ~ppa2 = LTO-on This compares amd64 vs i386 without LTO enabled $ grep "Depends" buildlog_ubuntu-lunar-amd64.heimdal_7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2_BUILDING.txt > amd64.deps $ grep "Depends" buildlog_ubuntu-lunar-i386.heimdal_7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2_BUILDING.txt > i386.deps $ diff -Naur amd64.deps i386.deps --- amd64.deps 2023-05-16 10:18:49.754334825 +0200 +++ i386.deps 2023-05-16 10:18:51.106344323 +0200 @@ -8,10 +8,10 @@ Depends: debconf (>= 0.5.00) | debconf-2.0, heimdal-clients, krb5-config, lsb-base, openbsd-inetd | inet-superserver, libasn1-8-heimdal (>= 1.4.0+git20110226), libc6 (>= 2.34), libcap-ng0 (>= 0.7.9), libgssapi3-heimdal (>= 1.4.0+git20110226), libhcrypto5-heimdal (>= 1.4.0+git20110226), libhdb9-heimdal (>= 1.6~git20131117), libheimntlm0-heimdal (>= 1.4.0+git20110226), libkadm5srv8-heimdal (>= 7.8.git20221115.a6cf945+dfsg), libkdc2-heimdal (>= 1.4.0+git20110226), libkrb5-26-heimdal (>= 1.7~git20160418), libroken19-heimdal (>= 1.7~git20150920), libsl0-heimdal (>= 1.4.0+git20110226) Depends: comerr-dev, libasn1-8-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libgssapi3-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libhcrypto5-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libhdb9-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libheimbase1-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libhx509-5-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libkadm5clnt7-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libkadm5srv8-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libkafs0-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libkdc2-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libkrb5-26-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libwind0-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libotp0-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libsl0-heimdal (= 7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2), libc6 (>= 2.34), libcom-err2 (>= 1.43.9), libroken19-heimdal (>= 1.4.0+git20110226) Depends: krb5-config, openbsd-inetd | inet-superserver, libc6 (>= 2.34), libkrb5-26-heimdal (>= 1.4.0+git20110226), libroken19-heimdal (>= 1.4.0+git20110226) - Depends: libc6 (>= 2.14), libcom-err2 (>= 1.43.9), libroken19-heimdal (>= 1.4.0+git20110226) + Depends: libc6 (>= 2.8), libcom-err2 (>= 1.43.9), libroken19-heimdal (>= 1.4.0+git20110226) Depends: libasn1-8-heimdal (>= 1.4.0+git20110226), libc6 (>= 2.34), libcom-err2 (>= 1.43.9), libhcrypto5-heimdal (>= 1.4.0+git20110226), libheimntlm0-heimdal (>= 1.4.0+git20110226), libkrb5-26-heimdal (>= 1.6~git20131117), libroken19-heimdal (>= 1.7~git20150920) Depends: libasn1-8-heimdal (>= 1.4.0+git20110226), libc6 (>= 2.36), libheimbase1-heimdal (>= 1.4.0+git20110226), libroken19-heimdal (>= 1.7~git20150920) - Depends: libasn1-8-heimdal (>= 1.6~git20120311g), libc6 (>= 2.14), libcom-err2 (>= 1.43.9), libdb5.3, libkrb5-26-heimdal (>= 1.7~git20161112), libldap2 (>= 2.6.2), libroken19-heimdal (>= 1.7~git20150920), libsqlite3-0 (>= 3.5.9) + Depends: libasn1-8-heimdal (>= 1.6~git20120311g), libc6 (>= 2.8), libcom-err2 (>= 1.43.9), libdb5.3, libkrb5-26-heimdal (>= 1.7~git20161112), libldap2 (>= 2.6.2), libroken19-heimdal (>= 1.7~git20150920), libsqlite3-0 (>= 3.5.9) Depends: libc6 (>= 2.34) Depends: libc6 (>= 2.4), libhcrypto5-heimdal (>= 1.4.0+git20110226), libkrb5-26-heimdal (>= 1.4.0+git20110226), libroken19-heimdal (>= 1.7~git20150920), libwind0-heimdal (>= 1.4.0+git20110226) Depends: libasn1-8-heimdal (>= 1.4.0+git20110226), libc6 (>= 2.34), libcom-err2 (>= 1.43.9), libhcrypto5-heimdal (>= 1.4.0+git20110226), libheimbase1-heimdal (>= 1.6~git20131117), libroken19-heimdal (>= 1.7~git20150920), libwind0-heimdal (>= 1.4.0+git20110226) @@ -23,4 +23,4 @@ Depends: libc6 (>= 2.33), libdb5.3, libhcrypto5-heimdal (>= 1.4.0+git20110226) Depends: libc6 (>= 2.36), libcrypt1 (>= 1:4.1.0) Depends: libc6 (>= 2.11), libedit2 (>= 2.11-20080614-0) - Depends: libc6 (>= 2.14), libcom-err2 (>= 1.43.9) + Depends: libc6 (>= 2.4), libcom-err2 (>= 1.43.9) And checking the PPAs build if LTO was really back on I indeed see "... -ffat-lto-objects ..." used in https://launchpadlibrarian.net/646899573/buildlog_ubuntu-lunar-amd64.heimdal_7.8.git20221117.28daf24+dfsg-1ubuntu1~ppa2_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/2019424 Title: Heimdal can be synced Status in heimdal package in Ubuntu: Confirmed Bug description: After
[Touch-packages] [Bug 2017979] Re: [UBUNTU 20.04] Cannot upgrade Ubuntu 20.04.6 LTS to 22.04. because the package language-pack-en-base cannot be updated
Hi - the majority of engineers where on Sprints in the recent weeks, so we were a bit short on staff - apologize. This bug got already assigned. But to get you unblocked, you may just remove (sudo apt remove ...) the package in question (and the one that has it as dependency), since they are not mandatory: $ apt-cache policy language-pack-en-base language-pack-en language-pack-en-base: Installed: (none) Candidate: 1:20.04+20220818 Version table: 1:20.04+20220818 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main s390x Packages 1:20.04+20200416 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages language-pack-en: Installed: (none) Candidate: 1:20.04+20200416 Version table: 1:20.04+20200416 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages If you remove them, please note if further (reverse) dependencies are removed too, if so record them and re-install again after the upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-en-base in Ubuntu. https://bugs.launchpad.net/bugs/2017979 Title: [UBUNTU 20.04] Cannot upgrade Ubuntu 20.04.6 LTS to 22.04. because the package language-pack-en-base cannot be updated Status in Ubuntu on IBM z Systems: Confirmed Status in language-pack-en-base package in Ubuntu: New Status in language-pack-en-base source package in Focal: Confirmed Bug description: ---Problem Description--- Cannot upgrade Ubuntu 20.04.6 LTS to 22.04. because the package language-pack-en-base cannot be updated do-release-update does not work Contact Information = pp...@de.ibm.com ---uname output--- Linux lnxut06 5.4.0-148-generic #165-Ubuntu SMP Tue Apr 18 08:52:35 UTC 2023 s390x s390x s390x GNU/Linux Machine Type = 3906 758 M03 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- root@lnxz:/etc/apt# do-release-upgrade Checking for a new Ubuntu release Please install all available updates for your release before upgrading. root@lnxz:/etc/apt# apt update Hit:1 http://de.ports.ubuntu.com/ubuntu-ports focal InRelease Get:2 http://de.ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Ign:4 https://pkg.jenkins.io/debian-stable binary/ InRelease Hit:5 https://pkg.jenkins.io/debian-stable binary/ Release Hit:7 http://de.ports.ubuntu.com/ubuntu-ports focal-backports InRelease Fetched 228 kB in 1s (201 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. root@lnxz:/etc/apt# apt list --upgradable Listing... Done language-pack-en-base/focal-updates 1:20.04+20220818 all [upgradable from: 1:20.04+20220211] N: There are 2 additional versions. Please use the '-a' switch to see them. root@lnxz:/etc/apt# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@lnxz:/etc/apt# apt --only-upgrade install language-pack-en-base Reading package lists... Done Building dependency tree 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: language-pack-en-base : Depends: language-pack-en (>= 1:20.04+20220818) but it is not going to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2017979/+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
