[Touch-packages] [Bug 2032851] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1
Hi there, I appreciate the great work to fix this issue. We have some AWS Ubuntu instance waiting for this release on Focal to upgrade from 18.04 to 20.04. Do you think there's an expected date that we can get the new AppArmor from the generic focal pocket instead of Proposed pocket? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2032851 Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1 Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Focal: In Progress Bug description: [ Impact ] * During an apparmor package upgrade, the cache files were deleted, but there could also be directories under /etc/apparmor.d/cache/ which the pre installation scripts did not account for. The upgrade would then fail with the following error message because it would not be able to remove the directories: package:apparmor:2.12-4ubuntu5.3 Preparing to unpack .../16-apparmor_2.13.3-7ubuntu5.2_amd64.deb ... rm: cannot remove '/etc/apparmor.d/cache/bf9d6da9.0': Is a directory dpkg: error processing archive /tmp/apt-dpkg-install-InP0fz/16-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack): new apparmor package pre-installation script subprocess returned error exit status 1 ErrorMessage: new apparmor package pre-installation script subprocess returned error exit status 1 [ Test Plan ] * On a bionic machine, create a directory under /etc/apparmor.d/cache sudo mkdir /etc/apparmor.d/cache/test * To simulate a system upgrade to focal, you can run the following steps 1. Add the focal archive sudo bash -c "cat
[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent
https://packages.ubuntu.com/noble/ntp I now see that Noble has a package for ntp but it is a transitional package to ntpsec instead of the real ntp package. — This is an extremely dangerous situation for the Long Term Support release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2039252 Title: [needs-packaging] The packages ntp and ntpsec are not equivalent Status in NTP: Confirmed Status in ntp package in Ubuntu: Confirmed Status in Juju Charms Collection: New Status in ntp package in Debian: Confirmed Bug description: I recently did an install of Ubuntu 23.04 and then configured ntp as I have been doing so for more than 8 years. With previous versions of Debian and Ubuntu using the real ntp package, the details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall&rev=38 created the desired results. I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with the new location of ntp.conf, after restarting I noticed that the resultant output was missing requisite details. Compare the following and the lack of ".MCST." and ".ACST.": Original ntp on Apollo-Lake-N3150 jonathan@Apollo-Lake-N3450:~$ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 jonathan@Apollo-Lake-N3450:~$ ntpq -p remote refid st t when poll reach delay offset jitter == 0.ubuntu.pool.n .POOL. 16 p- 6400.000 +0.000 0.000 1.ubuntu.pool.n .POOL. 16 p- 6400.000 +0.000 0.000 2.ubuntu.pool.n .POOL. 16 p- 6400.000 +0.000 0.000 3.ubuntu.pool.n .POOL. 16 p- 6400.000 +0.000 0.000 ntp.ubuntu.com .POOL. 16 p- 6400.000 +0.000 0.000 ntp.mcast.net .MCST. 16 M- 6400.000 +0.000 0.000 ff0e::101 .MCST. 16 M- 6400.000 +0.000 0.000 ntp.mcast.net .ACST. 16 a- 6400.000 +0.000 0.000 ff0e::101 .ACST. 16 a- 6400.000 +0.000 0.000 *time.cloudflare 10.242.8.77 3 u 469 1024 367 234.691 -0.929 67.380 +2001-44b8-2100- 42.3.115.79 2 u 581 1024 377 487.209 +55.669 57.154 +2001-44b8-2100- 4.179.66.17 3 u 215 1024 377 489.637 +57.002 35.399 jonathan@Apollo-Lake-N3450:~$ NTPsec on Braswell-N3150 jonathan@Braswell-N3150:~$ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 jonathan@Braswell-N3150:~$ ntpq -p remote refid st t when poll reach delay offset jitter === 0.ubuntu.pool.ntp.org .POOL. 16 p- 2560 0. 0. 0.0002 1.ubuntu.pool.ntp.org .POOL. 16 p- 2560 0. 0. 0.0002 2.ubuntu.pool.ntp.org .POOL. 16 p- 2560 0. 0. 0.0002 3.ubuntu.pool.ntp.org .POOL. 16 p- 640 0. 0. 0.0002 +prod-ntp-5.ntp1.ps5.canonical.com 37.15.221.1892 u 141 1024 367 383.4932 -19.6895 35.0534 *time.tfmcloud.au203.35.83.2422 u 325 1024 367 325.9317 -0.1496 43.0522 +any.time.nl 133.243.238.243 2 u 158 1024 373 300.7941 -20.8962 136.1422 +ntp2.its.waikato.ac.nz .GPS.1 u 363 1024 377 356.5361 -18.2740 140.5984 +2001-44b8-2100-3f00---007b-0004 42.3.115.79 2 u 214 1024 367 490.3898 28.3416 2.7728 +tic.ntp.telstra.net 203.35.83.2422 u 13 1024 367 566.0744 -14.1332 6.0377 +863xqmprtfqv69pv7nwc.ip6.superloop.au 192.168.1.1 2 u 79 1024 367 330.2658 -14.3483 16.2172 +gps-ads.10mrlp.juneks.com.au.PPS.1 u 271 1024 367 443.4812 -71.8020 44.6332 +x.ns.gin.ntt.net129.250.35.222 2 u 57 1024 367 22.4974 41.3055 6.0639 jonathan@Braswell-N3150:~$ This behaviour will affect the following: Ubuntu 22.10, 23.04 and 23.10 Debian 12, 13 and 14 NTPsec have documented their reasoning for lacking support. https://docs.ntpsec.org/latest/discover.html https://docs.ntpsec.org/latest/ntpsec.html https://docs.ntpsec.org/latest/assoc.html#broad https://docs.ntpsec.org/latest/assoc.html#many The issue remains that ntp and ntpsec are not capability equivalent. I foresee two means of rectifying this predicament, if NTPsec is going to be the default implementation of NTP then ntpsec needs to implement all of the c
[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent
** Also affects: charms Importance: Undecided Status: New ** Changed in: ntp Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/2039252 Title: [needs-packaging] The packages ntp and ntpsec are not equivalent Status in NTP: Confirmed Status in ntp package in Ubuntu: Confirmed Status in Juju Charms Collection: New Status in ntp package in Debian: Confirmed Bug description: I recently did an install of Ubuntu 23.04 and then configured ntp as I have been doing so for more than 8 years. With previous versions of Debian and Ubuntu using the real ntp package, the details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall&rev=38 created the desired results. I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with the new location of ntp.conf, after restarting I noticed that the resultant output was missing requisite details. Compare the following and the lack of ".MCST." and ".ACST.": Original ntp on Apollo-Lake-N3150 jonathan@Apollo-Lake-N3450:~$ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 jonathan@Apollo-Lake-N3450:~$ ntpq -p remote refid st t when poll reach delay offset jitter == 0.ubuntu.pool.n .POOL. 16 p- 6400.000 +0.000 0.000 1.ubuntu.pool.n .POOL. 16 p- 6400.000 +0.000 0.000 2.ubuntu.pool.n .POOL. 16 p- 6400.000 +0.000 0.000 3.ubuntu.pool.n .POOL. 16 p- 6400.000 +0.000 0.000 ntp.ubuntu.com .POOL. 16 p- 6400.000 +0.000 0.000 ntp.mcast.net .MCST. 16 M- 6400.000 +0.000 0.000 ff0e::101 .MCST. 16 M- 6400.000 +0.000 0.000 ntp.mcast.net .ACST. 16 a- 6400.000 +0.000 0.000 ff0e::101 .ACST. 16 a- 6400.000 +0.000 0.000 *time.cloudflare 10.242.8.77 3 u 469 1024 367 234.691 -0.929 67.380 +2001-44b8-2100- 42.3.115.79 2 u 581 1024 377 487.209 +55.669 57.154 +2001-44b8-2100- 4.179.66.17 3 u 215 1024 377 489.637 +57.002 35.399 jonathan@Apollo-Lake-N3450:~$ NTPsec on Braswell-N3150 jonathan@Braswell-N3150:~$ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 jonathan@Braswell-N3150:~$ ntpq -p remote refid st t when poll reach delay offset jitter === 0.ubuntu.pool.ntp.org .POOL. 16 p- 2560 0. 0. 0.0002 1.ubuntu.pool.ntp.org .POOL. 16 p- 2560 0. 0. 0.0002 2.ubuntu.pool.ntp.org .POOL. 16 p- 2560 0. 0. 0.0002 3.ubuntu.pool.ntp.org .POOL. 16 p- 640 0. 0. 0.0002 +prod-ntp-5.ntp1.ps5.canonical.com 37.15.221.1892 u 141 1024 367 383.4932 -19.6895 35.0534 *time.tfmcloud.au203.35.83.2422 u 325 1024 367 325.9317 -0.1496 43.0522 +any.time.nl 133.243.238.243 2 u 158 1024 373 300.7941 -20.8962 136.1422 +ntp2.its.waikato.ac.nz .GPS.1 u 363 1024 377 356.5361 -18.2740 140.5984 +2001-44b8-2100-3f00---007b-0004 42.3.115.79 2 u 214 1024 367 490.3898 28.3416 2.7728 +tic.ntp.telstra.net 203.35.83.2422 u 13 1024 367 566.0744 -14.1332 6.0377 +863xqmprtfqv69pv7nwc.ip6.superloop.au 192.168.1.1 2 u 79 1024 367 330.2658 -14.3483 16.2172 +gps-ads.10mrlp.juneks.com.au.PPS.1 u 271 1024 367 443.4812 -71.8020 44.6332 +x.ns.gin.ntt.net129.250.35.222 2 u 57 1024 367 22.4974 41.3055 6.0639 jonathan@Braswell-N3150:~$ This behaviour will affect the following: Ubuntu 22.10, 23.04 and 23.10 Debian 12, 13 and 14 NTPsec have documented their reasoning for lacking support. https://docs.ntpsec.org/latest/discover.html https://docs.ntpsec.org/latest/ntpsec.html https://docs.ntpsec.org/latest/assoc.html#broad https://docs.ntpsec.org/latest/assoc.html#many The issue remains that ntp and ntpsec are not capability equivalent. I foresee two means of rectifying this predicament, if NTPsec is going to be the default implementation of NTP then ntpsec needs to implement all of the capabilities of ntp, or the easier alternative is that the real ntp https://www.ntp.org/downloads/ is packaged as nt
[Touch-packages] [Bug 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
Workaround that worked for me was to let it begin loading infinitely, then right-click inside the window and select "Reload". It then skipped the login, and took me to the 2FA page that was presumably trying to load. -- 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/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2040385] Re: Merge init-system-helpers from Debian unstable for noble
[Foundations appears to handle this package, and no merge is available yet anyway] ** Changed in: init-system-helpers (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/2040385 Title: Merge init-system-helpers from Debian unstable for noble Status in init-system-helpers package in Ubuntu: Invalid Bug description: Scheduled-For: Backlog Upstream: tbd Debian: 1.65.2 Ubuntu: 1.65.2ubuntu1 If it turns out this needs a sync rather than a merge, please change the tag 'needs-merge' to 'needs-sync', and (optionally) update the title as desired. ### New Debian Changes ### init-system-helpers (1.65.2) unstable; urgency=low * Undo yet another hostile and baseless NMU. -- Luca Boccassi Sun, 18 Sep 2022 02:53:19 +0100 init-system-helpers (1.65.1) unstable; urgency=low * Undo hostile NMU. -- Luca Boccassi Sun, 18 Sep 2022 01:53:32 +0100 init-system-helpers (1.65) unstable; urgency=low * Upload to unstable. -- Luca Boccassi Sat, 17 Sep 2022 21:11:07 +0100 init-system-helpers (1.65~exp2) experimental; urgency=medium * fakechroot tests: skip on architectures where it is not available -- Luca Boccassi Thu, 15 Sep 2022 21:14:08 +0100 init-system-helpers (1.65~exp1) experimental; urgency=medium [ Luca Boccassi ] * Drop outdated conflict with file-rc * Add myself to Uploaders * d/rules: use execute_after instead of override * Add a dependency on usrmerge | usr-is-merged to complete the transition. As per ctte decision and discussion at: https://lists.debian.org/debian-ctte/2022/07/msg00019.html https://lists.debian.org/debian-ctte/2022/07/msg00061.html https://lists.debian.org/debian-ctte/2022/08/msg6.html [ Victor Westerhuis ] * Make deb-systemd-helper work on template units with DefaultInstance. DefaultInstance only influences the meaning of WantedBy/RequiredBy. Alias and Also are not impacted. This patch does not enable changing template instantiations, so `deb-systemd-helper enable getty@tty2.service` will still fail. * Fix tests depending on ordering of lines in state file. The previous commit changes the order in which lines are written to the state file. Because correctness does not depend on the order in which the state file is written, ignore the order in the test. -- Luca Boccassi Sat, 10 Sep 2022 13:27:16 +0100 init-system-helpers (1.64) unstable; urgency=medium * Team upload. * d-s-h: break infinite recursion on symlinks. (Closes: #1014119) * Bump Standards-Version to 4.6.1, no changes * Update date ranges in d/copyright -- Luca Boccassi Mon, 04 Jul 2022 11:19:08 +0100 init-system-helpers (1.63) unstable; urgency=medium [ Debian Janitor ] * Remove constraints unnecessary since buster * init-system-helpers: Drop versioned constraint on perl-base in Depends. * init: Drop versioned constraint on init-system-helpers in Depends. [ Johannes Schauer Marin Rodrigues ] * t/helpers.pm: use installed version of deb-systemd-helper if TEST_INSTALLED is set * add DPKG_ROOT support (Closes: #983421) [ Niels Thykier ] * Add additional error checking on write operations. The `close()` call can fail on both read and write - while the read is usually relatively benign, for the write counter part can include 'fun' errors. Most of these would most likely be persistent issues, but it makes sense to detect errors as early possible. [ Ville Skyttä ] * service: use `grep -F` instead of `egrep` `egrep` and `fgrep` have been deprecated in GNU grep since 2007, and in current post 3.7 Git they have been made to emit obsolescence warnings. The occurrence in `service` uses a non-regex argument, so switch to `grep -F` instead of `-E`. -- Michael Biebl Mon, 23 May 2022 22:48:30 +0200 init-system-helpers (1.62) unstable; urgency=medium * Team upload. [ Johannes Schauer Marin Rodrigues ] * use fakechroot instead of unsharing the mount namespace and mounting tmpfs [ Luca Boccassi ] * deb-systemd-invoke: systemctl --machine @ is now available in v249.10. Adjust the version check accordingly * Skip build-time tests if DEB_BUILD_OPTIONS=nocheck is set * Fix typos found by Lintian * Set Rules-Requires-Root: no ### Old Ubuntu Delta ### init-system-helpers (1.65.2ubuntu1) mantic; urgency=medium * Drop dependency on usrmerge; this transition is long completed in Ubuntu. LP: #2027712. -- Steve Langasek Mon, 17 Jul 2023 08:32:00 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2040385/+subscriptions -- M
[Touch-packages] [Bug 2039798] Re: please merge from debian instable 8.4 to address vulnerability
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/curl/+git/curl/+merge/455006 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2039798 Title: please merge from debian instable 8.4 to address vulnerability Status in curl package in Ubuntu: Confirmed Bug description: Actually Mantic has 8.2.1 version A huge security issue is fixed with 8.4 : https://linuxsecurity.com/news/security-vulnerabilities/curl-8-4-released-for-addressing-a-big-security-vulnerability changelog: https://curl.se/changes.html Available on Debian Sid: https://packages.debian.org/sid/curl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2039798/+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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
** Description changed: === SRU information === [ATTENTION] This SRU contains THREE changes which are listed in the section below. [Meta] - This bug is part of a series of four bugs for a single SRU. + This bug is part of a series of three bugs for a single SRU. This ( #2033422 ) is the "central" bug with the global information and debdiff. - This SRU addresses four issues with Jammy's openssl version: + This SRU addresses three issues with Jammy's openssl version: - http://pad.lv/1994165: ignored SMIME signature errors - http://pad.lv/2023545: imbca engine dumps core - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections (this one) - The SRU information has been added to the four bug reports and I am - attaching the debdiff here only for all four. + The SRU information has been added to the fthree bug reports and I am + attaching the debdiff here only for all three. All the patches have been included in subsequent openssl 3.0.x releases which in turn have been included in subsequent Ubuntu releases. There has been no report of issues when updating to these Ubuntu releases. I have rebuilt the openssl versions and used abi-compliance-checker to compare the ABIs of the libraries in jammy and the one for the SRU. Both matched completely (FYI, mantic's matched completely too). I have also pushed the code to git (without any attempt to make it git- ubuntu friendly). https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy- sru I asked Brian Murray about phasing speed and he concurs a slow roll-out is probably better for openssl. There is a small uncertainty because a security update could come before the phasing is over, effectively fast-forwarding the SRU. Still, unless there is already a current pre-advisory, this is probably better than a 10% phasing which is over after only a couple days anyway. NB: at the moment openssl doesn't phase slowly so this needs to be implemented. [Impact] Severely degraded performance for concurrent operations compared to openssl 1.1. The performance is so degraded that some workloads fail due to timeouts or insufficient resources (noone magically has 5 times more machines). As a consequence, a number of people use openssl 1.1 instead and do not get security updates. [Test plan] Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py . To test, follow these steps: - run "time python3 main.py" # using the aforementioned main.py script - apt install -t jammy-proposed libssl3 - run "time python3 main.py" - compare the runtimes for the two main.py runs You can run this on x86_64, Raspberry Pi 4 or any machine, and get a very large speed-up in all cases. The improvements are not architecture- dependant. Using this changeset, I get the following numbers for ten runs on my laptop: 3.0.2: real 2m5.567s user 4m3.948s sys 2m0.233s this SRU: real 0m23.966s user 2m35.687s sys 0m1.920s As can be easily seen, the speed-up is massive: system time is divided by 60 and overall wall clock time is roughly five times lower. In http://pad.lv/2009544 , Rafael also shared his performance numbers and they are relatable to these. He used slightly different versions (upstreams rather than patched with cherry-picks) but at least one of the version used does not include other performance change. He also used different hardware and this performance issue seems to depend on the number of CPUs available but also obtained a performance several times better. Results on a given machine vary also very little across runs (less than 2% variation on runs of size 10). They are also very similar on a Raspberry Pi 4 (8GB). The benchmark uses https://www.google.com/humans.txt which takes around 130ms to download on my machine but I modified the script to download something only 20ms away. Results are so close to the ones using humans.txt that they are within the error margin. This is consistent with the high-concurrency in the benchmark which both saturates CPU, and "hides" latencies that are relatively low. Finally, there are positive reports on github. Unfortunately they are not always completely targeted at these patches only and therefore I will not link directly to them but they have also been encouraging. [Where problems could occur] The change is spread over several patches which touch the internals of openssl. As such, the engine and provider functionality could be broken by these changes. Fortunately, in addition to upstream's code review, these patches are included in openssl 3.0.4 (iirc) and therefore in kinetic. No issue related to these changes was reported on launchpad or upstream. However, it is possible t
[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353
I have verified the fix using systemd-resolved 253.5-1ubuntu6.1 from mantic-proposed: root@mantic:~# apt policy systemd-resolved systemd-resolved: Installed: 253.5-1ubuntu6.1 Candidate: 253.5-1ubuntu6.1 Version table: *** 253.5-1ubuntu6.1 500 500 http://security.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 253.5-1ubuntu6 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages root@mantic:~# ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.19.111.15%eth0:68 0.0.0.0:* udp UNCONN 00 [fe80::216:3eff:feb4:d412]%eth0:546[::]:* tcp LISTEN 04096 127.0.0.54:53 0.0.0.0:* tcp LISTEN 04096 127.0.0.53%lo:53 0.0.0.0:* root@mantic:~# lsof -i -n -P COMMANDPIDUSER FD TYPE DEVICE SIZE/OFF NODE NAME systemd-n 844 systemd-network 17u IPv4 1737561 0t0 UDP 10.19.111.15:68 systemd-n 844 systemd-network 20u IPv6 1738516 0t0 UDP [fe80::216:3eff:feb4:d412]:546 systemd-r 1363 systemd-resolve 13u IPv4 1743909 0t0 UDP 127.0.0.53:53 systemd-r 1363 systemd-resolve 14u IPv4 1743910 0t0 TCP 127.0.0.53:53 (LISTEN) systemd-r 1363 systemd-resolve 15u IPv4 1743911 0t0 UDP 127.0.0.54:53 systemd-r 1363 systemd-resolve 16u IPv4 1743912 0t0 TCP 127.0.0.54:53 (LISTEN) root@mantic:~# resolvectl Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: stub Link 30 (eth0) Current Scopes: DNS Protocols: +DefaultRoute -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Servers: 10.19.111.1 fe80::216:3eff:fe07:85b6 DNS Domain: lxd ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- 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/2038894 Title: Ubuntu 23.10 cloud images unexpected UDP listening port 5353 Status in cloud-images: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Released Bug description: [Impact] In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP listening port 5353. By default and by policy, aside from port 22 there should be no other open ports on Ubuntu cloud images. Listening port 5353 is a regression. [Test Plan] Check that port 5353 is not open, and in particular that systemd- resolved is not listening on 5353. This is what it looks like when systemd-resolved *is* listening on 5353: ``` $ ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* udp UNCONN 00 127.0.0.1:323 0.0.0.0:* udp UNCONN 0
[Touch-packages] [Bug 2038894] Re: Ubuntu 23.10 cloud images unexpected UDP listening port 5353
The autopkgtest failures were resolved with retries. -- 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/2038894 Title: Ubuntu 23.10 cloud images unexpected UDP listening port 5353 Status in cloud-images: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Mantic: Fix Committed Status in systemd source package in Noble: Fix Released Bug description: [Impact] In the latest Ubuntu 23.10 cloud images we are seeing unexpected UDP listening port 5353. By default and by policy, aside from port 22 there should be no other open ports on Ubuntu cloud images. Listening port 5353 is a regression. [Test Plan] Check that port 5353 is not open, and in particular that systemd- resolved is not listening on 5353. This is what it looks like when systemd-resolved *is* listening on 5353: ``` $ ss --listening --no-header --tcp --udp --numeric udp UNCONN 00 127.0.0.54:53 0.0.0.0:* udp UNCONN 00 127.0.0.53%lo:53 0.0.0.0:* udp UNCONN 00 10.154.0.17%ens4:68 0.0.0.0:* udp UNCONN 00 127.0.0.1:323 0.0.0.0:* udp UNCONN 00 0.0.0.0:5353 0.0.0.0:* udp UNCONN 00 [::1]:323 [::]:* udp UNCONN 00 [::]:5353 [::]:* tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* tcp LISTEN 0 4096 *:22 *:* ``` ``` $ sudo lsof -i -n -P COMMANDPIDUSER FD TYPE DEVICE SIZE/OFF NODE NA
[Touch-packages] [Bug 2042483] [NEW] jconfig.h: No such file or directory
Public bug reported: A compiler can't find jconfig.h libjpeg.pc contains only /usr/include includedir, but the jconfig.h is located in /usr/include/x86_64-linux-gnu/ Maybe it's wrong location? libjpeg-turbo from git places all the headers in /usr/include ** Affects: libjpeg-turbo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/2042483 Title: jconfig.h: No such file or directory Status in libjpeg-turbo package in Ubuntu: New Bug description: A compiler can't find jconfig.h libjpeg.pc contains only /usr/include includedir, but the jconfig.h is located in /usr/include/x86_64-linux-gnu/ Maybe it's wrong location? libjpeg-turbo from git places all the headers in /usr/include To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/2042483/+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 2020259] Re: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2020259 Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: No sound whatsoever on freshly imaged Zenbook UM3504DA Sound control panel only occasionally shows activity, cannot consistently get it to provide sound. Attempted many fixes from other users experiencing same issue, many say this issue occurs after booting to windows or that sound only works at either 100% or 0% but this is not the case for myself. Since this is a recently released device, there are no matching fixes provided by the community that work for me. Hopefully this is at all helpfull ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.3.3-060303-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 21 20:20:32 2023 InstallationDate: Installed on 2023-05-21 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2023 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3504DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3504DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3504DA.302:bd03/10/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook 15 UM3504DA_UM3504DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-05-21T20:12:51.201988 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2020259/+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 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
On Wed, Nov 01, 2023 at 02:39:27PM -, Adrien Nader wrote:
> This one is indeed not in the SRU at the moment. The description edit
> itself did not make much sense.
(Okay, that's what I thought. For what it's worth, I noticed afterwards
that the description for LP: #2033422 still has the "four bugs" version
of that sentence.)
> As far as I understand, tinc could fairly easily work around this issue
> by explicitely setting the key size before doing operations. This is the
> safest approach. It might even be faster than waiting for the SRU and
> corresponding phased updates.
Actually this isn't really easy on the Tinc side (at least for
Ubuntu end users).
In particular, the Tinc package actually hasn't changed at all in
several Ubuntu releases, so the big surprise here was that Tinc
1.0.36 on Jammy fails to connect in a network where Tinc 1.0.36
on Focal worked fine (even after making the configuration
adjustments that were expected due to the openssl 1.1 -> 3
transition).
Tinc does not provide any user-level control on these parameters,
and I don't think it even sets the parameters explicitly
internally in the code; rather, it relies on the default settings
for the algorithm, which is what was broken in that brief range
of OpenSSL v3 upstream releases. (Presumably if it already set
the parameters explicitly then it wouldn't have been affected by
this bug.)
In any case, solving this from the Tinc side would involve
(someone) making a Ubuntu-specific customization to the Tinc
source code -- which seems a lot more fraught than simply using a
fixed libssl3 library...
One thought that occurred to me is the idea of a semi-official
PPA build with this Blowfish patch included in it.
"Semi-official" in that you (or someone involved in the OpenSSL
Ubuntu packaging work) would publish it, building on top of the
official Ubuntu package, and thus it would track any other fixes
that were published to the main OpenSSL Jammy package -- but
since it's in a PPA it would be opt-in for those who need it.
This would be certainly be preferable to me over my current
situation using an "orphan" version of the legacy.so library
file, but I don't know how much effort it would be to provide
that on your end...
Nathan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1990216
Title:
backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL
1.1 with blowfish in OFB or CFB modes" to Jammy
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Jammy:
In Progress
Status in openssl source package in Lunar:
Fix Released
Bug description:
=== SRU information ===
[Meta]
This bug was the fourth in a series of bugs for a single SRU.
The "central" bug with the global information and debdiff is
http://pad.lv/2033422
[Impact]
Decryption for Blowfish with OFB and CFB modes fails due to using a key
shorter than expected by default.
Encryption will also use a key shorter than expected.
Exchange of encrypted data from/to Jammy using BF OFB/CFB will therefore lead
to decryption issues.
[Test plan]
On Focal, run the following and copy the output to your clipboard
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do echo "Test with ${cipher}"
| openssl enc -${cipher} -k test -pbkdf2 -out "pouet.${cipher}"; done
tar c pouet.bf-* | xz | base64 -w 60
You can also run this on Lunar or Mantic if you add "-provider legacy
-provider default" to the "openssl enc" invocation.
On Jammy, run the following and paste your clipboard
base64 -d | xz -d | tar x
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do openssl enc -d -provider
legacy -provider default -${cipher} -k test -pbkdf2 -d -in "pouet.${cipher}";
done
Only "Test with bf-cbc" and "Test with bf-ecb" will be properly
decrypted: the other two will result in garbage on screen.
Here is the result of the enc + tar + xz + base64 on Focal (works with
Lunar/Mantic too but you need to added ):
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARBdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc5VcodF6fu0hEp801tvirgSFNMSAHk5HMN/w
hCgU1BIr/nK51g3A3Lkdv7QNbaUw2ux1AmO/MpCLKLffCB9ElFZH4tuOS5AR
m9CJMzi6LQOw9wytGKm2IK3Ph7WpU6JQ/3HJilffQwHbFLnukiWGpLNO5v0O
D/4AJikrU9iemfChT0jXDbIRZ8a8VpVhJqu0u6eYOheVTqmSRiHHpIC/p1VA
ecFb0mACF/TQhjxcMUWGSGO/mtof+VaLiyg0KB87GKlChfwXTEvgbNuP9hmu
GL64VhX568Oy9EakSxlcXiIRk14kJKv0MdHQqY1R22wAACzqSr/nzpwqAAGs
AoBQAACjzq5WscRn+wIABFla
Here is the same but from Jammy if you want to test encryption on
Jammy and decryption on Lunar/Mantic:
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARFdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc1zK4HR2g3CiLJet+R++nZy/gph6RscQ6hI3
HySjdDOFRfjIVttiNK3DvRsZb37r8SXkj/JCYWicZGjWPZxVE3OAZhEed5qe
jrFv871QAbm4jVGD4oI
[Touch-packages] [Bug 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
Hi Nathan,
Sorry, I didn't have enough time to comment here before a few days of
vacation.
This one is indeed not in the SRU at the moment. The description edit
itself did not make much sense.
I first discussed this topic with Simon but then also with Steve
Langasek, with others attending the same meeting. The general agreement
is that bugs when setting up something for the first time are far less
severe than bugs that appear afterwards. One major issue here is
everything that exists but that we don't know of, including custom
software or scripts.
As far as I'm concerned, I evaluate this roughly like you did but I
cannot do something that the SRU team is against (I also trust them and
their experience, even when my feeling is different).
Lastly, 22.04 was released more than 18 months ago and 24.04 is around
the corner; 18 months is a long delay to introduce breaking changes and
by now people probably expect very few changes to 22.04.
As far as I understand, tinc could fairly easily work around this issue
by explicitely setting the key size before doing operations. This is the
safest approach. It might even be faster than waiting for the SRU and
corresponding phased updates.
** Description changed:
=== SRU information ===
[Meta]
- This bug is part of a series of three bugs for a single SRU.
+ This bug was the fourth in a series of bugs for a single SRU.
The "central" bug with the global information and debdiff is
http://pad.lv/2033422
[Impact]
Decryption for Blowfish with OFB and CFB modes fails due to using a key
shorter than expected by default.
Encryption will also use a key shorter than expected.
Exchange of encrypted data from/to Jammy using BF OFB/CFB will therefore lead
to decryption issues.
[Test plan]
On Focal, run the following and copy the output to your clipboard
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do echo "Test with ${cipher}"
| openssl enc -${cipher} -k test -pbkdf2 -out "pouet.${cipher}"; done
tar c pouet.bf-* | xz | base64 -w 60
You can also run this on Lunar or Mantic if you add "-provider legacy
-provider default" to the "openssl enc" invocation.
On Jammy, run the following and paste your clipboard
base64 -d | xz -d | tar x
for cipher in bf-cbc bf-cfb bf-ecb bf-ofb; do openssl enc -d -provider
legacy -provider default -${cipher} -k test -pbkdf2 -d -in "pouet.${cipher}";
done
Only "Test with bf-cbc" and "Test with bf-ecb" will be properly
decrypted: the other two will result in garbage on screen.
Here is the result of the enc + tar + xz + base64 on Focal (works with
Lunar/Mantic too but you need to added ):
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARBdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc5VcodF6fu0hEp801tvirgSFNMSAHk5HMN/w
hCgU1BIr/nK51g3A3Lkdv7QNbaUw2ux1AmO/MpCLKLffCB9ElFZH4tuOS5AR
m9CJMzi6LQOw9wytGKm2IK3Ph7WpU6JQ/3HJilffQwHbFLnukiWGpLNO5v0O
D/4AJikrU9iemfChT0jXDbIRZ8a8VpVhJqu0u6eYOheVTqmSRiHHpIC/p1VA
ecFb0mACF/TQhjxcMUWGSGO/mtof+VaLiyg0KB87GKlChfwXTEvgbNuP9hmu
GL64VhX568Oy9EakSxlcXiIRk14kJKv0MdHQqY1R22wAACzqSr/nzpwqAAGs
AoBQAACjzq5WscRn+wIABFla
Here is the same but from Jammy if you want to test encryption on Jammy
and decryption on Lunar/Mantic:
/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4Cf/ARFdADgbyxDlZ/1Xd7bAmZw7
8pbqQTu5j8StVybo1p1B2ydBc1zK4HR2g3CiLJet+R++nZy/gph6RscQ6hI3
HySjdDOFRfjIVttiNK3DvRsZb37r8SXkj/JCYWicZGjWPZxVE3OAZhEed5qe
jrFv871QAbm4jVGD4oIc4cOb5V/xDN7KWgwEzpWQy6+tcfPm3KLPQvULx56N
2qQf60hP//p5EXS3RpCitUsrGUoYzTynjOUIRy2yCmgZDh62RmchUshyWePa
k0nEYlDbl5/dSHXbWEWESqW+QDj136MZRwQRY+QC4MvLXg2Bo8H+Dl/xvNDF
/5J4layZdFlh76lWOtFRVoIbX6JtpAP34g4zx1422GSNAABRzyqPdCqX
1AABrQKAUAAABh3ynbHEZ/sCAARZWg==
The contents are expected to be different due to the use of randomness.
Don't try to compare the base64 outputs: I'm only using them to ease
testing across containers.
[Where problems could occur]
This patch makes openssl match the documented default (see "man openssl-enc"
and search for "Blowfish" for instance) and fixes decryption from an up-to-date
Jammy to pretty much everything else, but it also create an issue for data
encrypted on Jammy without this patch and Jammy with this patch.
There are two possible cases: encrypted data being streamed across this
boundary or data at rest being transferred or read later.
Streaming is probably not an issue in practice because it's rather the
current situation that has been an issue and it's easy to remedy by
updating everything (which is relatively few machines since that's only
Jammy and not any other OS or distribution).
Data at rest is more annoying since updating Jammy will make it
impossible to read the data again without updates to other pieces of
software. That sounds like a really bad thing and it kind of is but at
the same, the benefits are much larger than the issues. Indeed,
[Touch-packages] [Bug 2042431] Re: Please merge 1.226-1 into noble
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/netcat-openbsd/+git/netcat-openbsd/+merge/454972 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/2042431 Title: Please merge 1.226-1 into noble Status in netcat-openbsd package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2042431/+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 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image
Thanks for pointing the required resource in hook-function in initramfs-tools. These seems helped. However I'm still check more required drivers. + modules="$modules =drivers/nvmem" modules="$modules =drivers/phy" + modules="$modules =drivers/power" modules="$modules =drivers/regulator" modules="$modules =drivers/reset" modules="$modules =drivers/spi" + modules="$modules =drivers/soc" I think this is also required for "spmi-mtk-pmif" +modules="$modules =drivers/spmi" according to this https://bugzilla.suse.com/show_bug.cgi?id=1216767 fix. ** Bug watch added: bugzilla.suse.com/ #1216767 https://bugzilla.suse.com/show_bug.cgi?id=1216767 -- 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/2038512 Title: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image Status in initramfs-tools package in Ubuntu: New Bug description: [Impact] Peripheral probe failure for MediaTek boards 'mt8195-demo' and 'genio-1200-evk'. [Ubuntu Version] Jammy [initramfs-tools] 0.140ubuntu13.4 [Kernel version] 5.15 -> 6.2 (Generate initrd.img-6.2.0 on 5.15 kernel.) [Fix] I've used 'dracut' to examing the driver dependencies for boards 'mt8195-demo' and 'genio-1200-evk'. It is able to buot into console and use USB port3. Hope these drivers could help to run installer with USB disk in next daily build. Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if just simply add driver lists in '/etc/modules', '/etc/modprobe.d/mediatek.conf' or '/etc/modules- load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems this tool will include more common framework drivers into initrd.img. [MediaTek relate drivers] file: mediatek-drivers-for-mt8195-demo-bringup.txt (Not listed in probing sequence) i2c-mt65xx spi-mt65xx reset-ti-syscon mt6397 rtc-mt6397 mtk-pmic-wrap mt6315-regulator spmi-mtk-pmif mtk_scp_ipi mediatek-drm mtk-vcodec-dec mtk-vcodec-enc mtk_jpeg mtk-vcodec-common mtk-jpeg-enc-hw mtk-vpu mtk-jpeg-dec-hw mtk-cmdq-helper mtk-cmdq-helper mtk-cmdq-mailbox mtk-mdp3 phy-mtk-mipi-dsi-drv btmtk leds-mt6360 tcpci_mt6360 mt6360_charger mt6360-regulator mt6360-core mt6359-regulator mt6360-adc snd-soc-mt8195-afe snd-soc-mtk-common snd-soc-dmic dwmac-mediatek stmmac-platform stmmac mtk-rng mtk_scp mtk_rpmsg pwm-mediatek pwm-mtk-disp nvmem_mtk-efuse mtk-sd cqhci phy-mtk-tphy mtu3 xhci-mtk-hcd phy-mtk-pcie pcie-mediatek-gen3 [lsmod log] file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt [Other info] effected kernel (6.2-latest) ubuntu kernel for lunar, and Mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+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 2041845] Re: Notifies about some ancient downgrades on every boot
> Removed `/var/lib/PackageKit/offline-update-competed` Yes, this solved it. I would expect processing this file disabled alongside with offline updates functionality though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2041845 Title: Notifies about some ancient downgrades on every boot Status in packagekit package in Ubuntu: Incomplete Bug description: Preparing for upgrade from 22.04 to 23.04 some packages were downgraded (or just marked as such?) and now update-notifier reminds me about them on every boot, this makes me likely to miss important upgrades available, because I tend now to dismiss it without looking. google-chrome-stable was upgraded many times since then, but I still get notifications about that 113.0... version. Btw, it says about downgrade from the current version! It's update-notifier/lunar,now 3.192.64 amd64 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: update-notifier 3.192.64 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 14:47:30 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2016-11-26 (2529 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: update-notifier UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago) upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 new release available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2041845/+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 2041845] Re: Notifies about some ancient downgrades on every boot
Removed `/var/lib/PackageKit/offline-update-competed` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2041845 Title: Notifies about some ancient downgrades on every boot Status in packagekit package in Ubuntu: Incomplete Bug description: Preparing for upgrade from 22.04 to 23.04 some packages were downgraded (or just marked as such?) and now update-notifier reminds me about them on every boot, this makes me likely to miss important upgrades available, because I tend now to dismiss it without looking. google-chrome-stable was upgraded many times since then, but I still get notifications about that 113.0... version. Btw, it says about downgrade from the current version! It's update-notifier/lunar,now 3.192.64 amd64 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: update-notifier 3.192.64 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 14:47:30 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2016-11-26 (2529 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: update-notifier UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago) upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 new release available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2041845/+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 2042431] [NEW] Please merge 1.226-1 into noble
Public bug reported: tracking bug ** Affects: netcat-openbsd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/2042431 Title: Please merge 1.226-1 into noble Status in netcat-openbsd package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2042431/+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 2041845] Re: Notifies about some ancient downgrades on every boot
> Were you running kinetic during the development cycle? No. But there might be leftovers from Xubuntu desktop which was installed for some time or many older Ubuntu versions (since 16.04). > pkcon offline-get-prepared shows prepared ones. pkcon offline-get-prepared Command failed: No offline updates have been prepared OK, it shouldn't re-occur again, but how can I clear this? Remove gnome- software? `pkcon get-transactions` gives several transactions from 2023-05-12T03:10:50.577373Z to 2023-07-27T12:04:40.566288Z. It looks weird because it reports installing the same package twice in the same transaction. Like this: Transaction: /31116_daddceac System time: 2023-05-22T10:30:46.247833Z Succeeded: True Role: update-packages Duration: 115704 (seconds) Command line: User ID: 0 Username: root Real name: root Affected packages: - preparing google-chrome-stable-113.0.5672.126-1.amd64 - decompressing google-chrome-stable-113.0.5672.126-1.amd64 - installing google-chrome-stable-113.0.5672.126-1.amd64 - preparing mdadm-4.2-0ubuntu2.amd64 - decompressing mdadm-4.2-0ubuntu2.amd64 - installing mdadm-4.2-0ubuntu2.amd64 - preparing google-chrome-stable-113.0.5672.126-1.amd64 - installing google-chrome-stable-113.0.5672.126-1.amd64 - preparing mdadm-4.2-0ubuntu2.amd64 - installing mdadm-4.2-0ubuntu2.amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2041845 Title: Notifies about some ancient downgrades on every boot Status in packagekit package in Ubuntu: Incomplete Bug description: Preparing for upgrade from 22.04 to 23.04 some packages were downgraded (or just marked as such?) and now update-notifier reminds me about them on every boot, this makes me likely to miss important upgrades available, because I tend now to dismiss it without looking. google-chrome-stable was upgraded many times since then, but I still get notifications about that 113.0... version. Btw, it says about downgrade from the current version! It's update-notifier/lunar,now 3.192.64 amd64 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: update-notifier 3.192.64 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 14:47:30 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2016-11-26 (2529 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: update-notifier UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago) upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 new release available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2041845/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
Same issue here. I don't think this is related to the other common problem where the whole window would freeze if you are running X11 and haven't disabled the sandbox. Hence, it took me a while to find this issue. The problem is the same on both X11 and Wayland, regardless of whether the sandbox is enabled or not. It's not the window that freezes, it's just the login page that is stuck. I had my Google account set up before, but I deleted it, because my calendars stopped syncing (I've had that before as well) and now I cannot add it back. -- 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/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2041845] Re: Notifies about some ancient downgrades on every boot
Hmm that shows the result of the last offline update, not anything queued; and pkcon offline-get-prepared shows prepared ones. Were you running kinetic during the development cycle? There was a short period where offline updates where unintentionally enabled in gnome- software, bug 1992498. I don't know how else you would have triggered that. ** No longer affects: gnome-software (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/2041845 Title: Notifies about some ancient downgrades on every boot Status in packagekit package in Ubuntu: Incomplete Bug description: Preparing for upgrade from 22.04 to 23.04 some packages were downgraded (or just marked as such?) and now update-notifier reminds me about them on every boot, this makes me likely to miss important upgrades available, because I tend now to dismiss it without looking. google-chrome-stable was upgraded many times since then, but I still get notifications about that 113.0... version. Btw, it says about downgrade from the current version! It's update-notifier/lunar,now 3.192.64 amd64 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: update-notifier 3.192.64 ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16 Uname: Linux 6.2.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 14:47:30 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2016-11-26 (2529 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: update-notifier UpgradeStatus: Upgraded to lunar on 2023-06-11 (140 days ago) upstart.update-notifier-release.log: вівторок, 14 серпня 2018 21:28:26 +0300 new release available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2041845/+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 2037642] Re: [FFe] Raspberry Pi 5 support
** No longer affects: libcamera (Ubuntu Noble) ** No longer affects: linux-meta-raspi (Ubuntu Noble) ** No longer affects: linux-raspi (Ubuntu Noble) ** No longer affects: mesa (Ubuntu Noble) ** No longer affects: pipewire (Ubuntu Noble) ** No longer affects: rpi-eeprom (Ubuntu Noble) ** No longer affects: ubuntu-settings (Ubuntu Noble) -- 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/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: Fix Released Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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
