[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade
I believe the remaining autopkgtest failures are unrelated. For lunar[1], we have ubuntu-drivers-common failing on ppc64el[2]. We can see the same failure on a different test run without a systemd trigger[3]. For jammy[4], we have linux-nvidia[5] and linux-nvidia-tegra-igx[6], each failing their "rebuild" test. This happens frequently and is unrelated to the systemd change. Finally, there is netplan.io failing its "tunnels" test[7]. This is failing without systemd triggers too[8], and I checked with @danilogondolfo to confirm that this is a separate issue. [1] https://ubuntu-archive-team.ubuntu.com/proposed-migration/lunar/update_excuses.html#systemd [2] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/ppc64el/u/ubuntu-drivers-common/20230925_224541_eee1a@/log.gz [3] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/ppc64el/u/ubuntu-drivers-common/20230815_053853_379e2@/log.gz [4] https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#systemd [5] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-nvidia-6.2/20230926_000856_1a567@/log.gz [6] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/linux-nvidia-tegra-igx/20230926_010738_40534@/log.gz [7] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/netplan.io/20230925_232048_829bd@/log.gz [8] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/netplan.io/20230907_195833_5846d@/log.gz -- 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/2036358 Title: systemd wait-online now times out after jammy and lunar upgrade Status in systemd package in Ubuntu: Invalid Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Lunar: Fix Committed Bug description: [NOTE] If you are running a desktop system and you see this issue, you should run: $ systemctl disable --now systemd-networkd.service This will disable systemd-networkd and associated units, including systemd-networkd-wait-online.service. NetworkManager and systemd- networkd should not be running at the same time. On desktop, NetworkManager is the default network stack. [Impact] When all interfaces are "not required for online", e.g. when they are marked "optional: true" in netplan, systemd-networkd-wait-online will timeout. Or, in other words, systemd-networkd-wait-online will timeout even though all interfaces are ignored, hence none of them will ever be marked as "ready." Depending on what units depend on network- online.target, this can delay boot by 120 seconds (the default timeout for systemd-networkd-wait-online). [Test Plan] 1. Create a new LXD container. These instructions assume jammy is the release, but the same can be done for lunar. $ lxc launch ubuntu-daily:jammy jammy $ lxc exec jammy bash 2. Once in the container, modify the default /etc/netplan/10-lxc.yaml so that eth0 is configured with "optional: true": $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: true dhcp-identifier: mac optional: true 3. Re-generate and apply the netplan configuration. $ netplan generate $ netplan apply 4. Manually run systemd-networkd-wait-online, and observe that all links are ignored, and the command times out: $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10 Found link lo(1) Found link eth0(19) lo: link is ignored eth0: link is ignored Timeout occurred while waiting for network connectivity. [Where problems could occur] This patch partially re-instates a patch remove in bug 1982218. However, instead of exiting if all links are unmanaged, we exit if all links are ignored in manager_configured(). If the patch was wrong, we may re-introduce bug 1982218, so as part of this SRU verification, that bug should be tested too. Any other regressions would also be related to systemd-networkd-wait-online behavior. [Original Description] On Ubuntu 22.04 desktop system using network-manager and upgrading to systemd 249.11-0ubuntu3.10, wait-online now times out which prevents logins (GDM, ssh, console) until it does time out. This seems to be introduced by the change for https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21 also mentioned the problem on Lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"
** Description changed: + === SRU information === + + [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 and results in #2009544 . I have tested this on a raspberry pi 4 with 8GB of memory and obtained speedups at least as high. + + [Where problems could occur] + The change is spread over several patches which touch the internals of openssl. Upstream has code review in place and the patches have first appeared in openssl 3.0.4 iirc and therefore in kinetic which was released a year ago and we have not seen issues crop up. + + === Original description === + This is about SRU'ing to Jammy the patches at https://github.com/openssl/openssl/pull/18151#issuecomment-1118535602 . They're purely performance but their impact is large. They have been released as part of openssl 3.0.4 (they're among the first after 3.0.3) which has been included in Kinetic. -- 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/2033422 Title: openssl: backport to jammy "clear method store / query cache confusion" Status in openssl package in Ubuntu: New Status in openssl source package in Jammy: In Progress Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [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 and results in #2009544 . I have tested this on a raspberry pi 4 with 8GB of memory and obtained speedups at least as high. [Where problems could occur] The change is spread over several patches which touch the internals of openssl. Upstream has code review in place and the patches have first appeared in openssl 3.0.4 iirc and therefore in kinetic which was released a year ago and we have not seen issues crop up. === Original description === This is about SRU'ing to Jammy the patches at https://github.com/openssl/openssl/pull/18151#issuecomment-1118535602 . They're purely performance but their impact is large. They have been released as part of openssl 3.0.4 (they're among the first after 3.0.3) which has been included in Kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2033422/+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 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate
** Description changed: + === SRU information === + + [Impact] + Openssl using an engine dumps core upon certificate creation; other operations are probably affected too. Overall, engines are likely mostly unusable. + + [Test plan] + An engine is needed to test the fix and I don't think we have many in the archive. This complicates reproducing the issue. I have been relying on user reports which have been very detailled and helpful. + The issue has also been reported independently and with another engine (devcrypto). + The issue is fixed in openssl 3.0.8 which landed in lunar. + + [Where problems could occur] + I don't pretend to understand the lifecycle of providers in openssl3 but the patch is simple and has been widely tested by now, including on ubuntu. Thus, I see little chance an unexpected problem would occur with it. + + === Original description === + + openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem + -keyout __key.pem --subj '/CN=US' + ---Problem Description--- OpenSSL with ibmca engine configured dumps core when creating a new certificate. # openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support # openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem -keyout __key.pem --subj '/CN=US' Segmentation fault (core dumped) # journalctl Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b ilc:2 in libc.so.6[3ffae08+1ca000] Jun 07 13:06:08 SYSTEM kernel: Failing address: TEID: 0800 Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user ASCE. Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024 Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded Not tainted 5.15.0-73-generic #80-Ubuntu Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0) Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708 Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:0 PM:0 RI:0 EA:3 Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 02aa3289f9d0 Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 02aa328a4300 Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 02aa03ff Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 03ffae437c22 03ffec2fe000 Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2 lgr%r11,%r2 - 03ffae11c700: 4700bc0,0 - #03ffae11c704: b24f00a0ear%r10,%a0 - >03ffae11c708: 58102018l%r1,24(%r2) - 03ffae11c70c: ebaa002dsllg%r10,%r10,32 - 03ffae11c712: b24f00a1ear%r10,%a1 - 03ffae11c716: 5910a0d0c%r1,208(%r10) - 03ffae11c71a: a7840033brc8,03ffae11c780 + 03ffae11c700: 4700bc0,0 + #03ffae11c704: b24f00a0ear%r10,%a0 + >03ffae11c708: 58102018l%r1,24(%r2) + 03ffae11c70c: ebaa002dsllg%r10,%r10,32 + 03ffae11c712: b24f00a1ear%r10,%a1 + 03ffae11c716: 5910a0d0c%r1,208(%r10) + 03ffae11c71a: a7840033brc8,03ffae11c780 Jun 07 13:06:08 SYSTEM kernel: Last Breaking-Event-Address: Jun 07 13:06:08 SYSTEM kernel: [<03ffae33242c>] 0x3ffae33242c Jun 07 13:06:08 SYSTEM systemd[1]: Started Process Core Dump (PID 2345/UID 0). Jun 07 13:06:08 SYSTEM systemd-coredump[2350]: Process 2344 (openssl) of user 0 dumped core. -Found module linux-vdso64.so.1 with build-id: bcfab8ac8dbd44c758c3c5494e2952db16905d2e -Found module libica.so.4 with build-id: 0cc5ace50644dfba6d0ecf4f783477cd04a55731 -
[Touch-packages] [Bug 2037569] Re: udev issues with mantic beta
Marking invalid in systemd, other than long-standing udev rules being involved I'm not sure this will be fixed in systemd. Exploring if libblockdev with the s390 plugin enabled helps. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Also affects: libblockdev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2028082] Re: Update glib to 2.76.4
** Description changed: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. - Ensure that there aren't autopgktest regressions triggered by this + Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: In Progress Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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 2037569] Re: udev issues with mantic beta
In function udisks_linux_partition_table_update if num_parts > 0, no ID_PART_TABLE_TYPE is present, and bd_part_get_disk_spec fails to get the disk information including part_type, this function will fail. Also, because libblockdev uses libfdisk in a manner that opens the disk RW, that causes another udev event and that will cause udisks_linux_partition_table_update to be called again. -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037205] Re: setuptools: FTBFS in mantic
Discussing the best solution with dh-python maintainers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2037205 Title: setuptools: FTBFS in mantic Status in dh-python package in Ubuntu: New Status in setuptools package in Ubuntu: New Status in dh-python package in Debian: Unknown Status in setuptools package in Debian: New Bug description: As seen in the mantic test rebuild [1], setuptools 68.1.2-1 currently FTBFS: Traceback (most recent call last): File "/<>/setuptools/config/setupcfg.py", line 284, in __setitem__ current_value = getattr(target_obj, option_name) AttributeError: 'MinimalDistribution' object has no attribute 'entry_points' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/setup.py", line 92, in dist = setuptools.setup(**setup_params) File "/<>/setuptools/__init__.py", line 106, in setup _install_setup_requires(attrs) File "/<>/setuptools/__init__.py", line 77, in _install_setup_requires dist.parse_config_files(ignore_option_errors=True) File "/<>/setuptools/dist.py", line 895, in parse_config_files setupcfg.parse_configuration( File "/<>/setuptools/config/setupcfg.py", line 177, in parse_configuration options.parse() File "/<>/setuptools/config/setupcfg.py", line 500, in parse section_parser_method(section_options) File "/<>/setuptools/config/setupcfg.py", line 727, in parse_section_entry_points self['entry_points'] = parsed File "/<>/setuptools/config/setupcfg.py", line 286, in __setitem__ raise KeyError(option_name) KeyError: 'entry_points' E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: python3.11 setup.py clean [1] https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2037205/+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 2023462] Re: chromeos_pstore.service started on non chrome platform hardware.
Are there any plans to fix this in Focal? systemd-analyze blame shows "392ms modprobe@chromeos_pstore.service" -- 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/2023462 Title: chromeos_pstore.service started on non chrome platform hardware. Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] Kernel modules that provide pstore backends are unnecessarily loaded by systemd-pstore.service. While this is pretty benign behavior, it was introduced by an earlier SRU (bug 1978079) and is not consistent with newer releases in which systemd-pstore.service only tries to load efi_pstore. [Test Plan] Check which modules systemd-pstore.service depends on: $ systemctl list-dependencies systemd-pstore.service systemd-pstore.service * |--.mount * |-modprobe@chromeos_pstore.service * |-modprobe@efi_pstore.service * |-modprobe@pstore_blk.service * |-modprobe@pstore_zone.service * |-modprobe@ramoops.service * `-system.slice On an affected machine, we see several pstore providers in addition to efi_pstore. On a patched system, we should only see efi_pstore. [Where problems could occur] If somehow a user was running a configuration where one of the other modules was needed for pstore on their system, and that module was not loaded when systemd-pstore.service ran, they might not get correct output. However, the original bug (bug 1978079) was only about efi_pstore, and that will still be loaded by systemd-pstore.service. On all releases newer than Jammy, only efi_pstore is loaded by systemd-pstore.service, and there have not been bug reports. [Original Description] systemd-analyze blame | grep pstore 110ms modprobe@chromeos_pstore.service 5ms modprobe@efi_pstore.service 5ms modprobe@pstore_blk.service 3ms modprobe@pstore_zone.service /lib/systemd/system/systemd-pstore.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2023462/+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 2037205] Re: setuptools: FTBFS in mantic
** Changed in: dh-python (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2037205 Title: setuptools: FTBFS in mantic Status in dh-python package in Ubuntu: New Status in setuptools package in Ubuntu: New Status in dh-python package in Debian: New Status in setuptools package in Debian: New Bug description: As seen in the mantic test rebuild [1], setuptools 68.1.2-1 currently FTBFS: Traceback (most recent call last): File "/<>/setuptools/config/setupcfg.py", line 284, in __setitem__ current_value = getattr(target_obj, option_name) AttributeError: 'MinimalDistribution' object has no attribute 'entry_points' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/setup.py", line 92, in dist = setuptools.setup(**setup_params) File "/<>/setuptools/__init__.py", line 106, in setup _install_setup_requires(attrs) File "/<>/setuptools/__init__.py", line 77, in _install_setup_requires dist.parse_config_files(ignore_option_errors=True) File "/<>/setuptools/dist.py", line 895, in parse_config_files setupcfg.parse_configuration( File "/<>/setuptools/config/setupcfg.py", line 177, in parse_configuration options.parse() File "/<>/setuptools/config/setupcfg.py", line 500, in parse section_parser_method(section_options) File "/<>/setuptools/config/setupcfg.py", line 727, in parse_section_entry_points self['entry_points'] = parsed File "/<>/setuptools/config/setupcfg.py", line 286, in __setitem__ raise KeyError(option_name) KeyError: 'entry_points' E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: python3.11 setup.py clean [1] https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2037205/+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 2037205] Re: setuptools: FTBFS in mantic
** Bug watch added: Debian Bug tracker #1051837 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051837 ** Also affects: dh-python (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051837 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2037205 Title: setuptools: FTBFS in mantic Status in dh-python package in Ubuntu: New Status in setuptools package in Ubuntu: New Status in dh-python package in Debian: Unknown Status in setuptools package in Debian: New Bug description: As seen in the mantic test rebuild [1], setuptools 68.1.2-1 currently FTBFS: Traceback (most recent call last): File "/<>/setuptools/config/setupcfg.py", line 284, in __setitem__ current_value = getattr(target_obj, option_name) AttributeError: 'MinimalDistribution' object has no attribute 'entry_points' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/setup.py", line 92, in dist = setuptools.setup(**setup_params) File "/<>/setuptools/__init__.py", line 106, in setup _install_setup_requires(attrs) File "/<>/setuptools/__init__.py", line 77, in _install_setup_requires dist.parse_config_files(ignore_option_errors=True) File "/<>/setuptools/dist.py", line 895, in parse_config_files setupcfg.parse_configuration( File "/<>/setuptools/config/setupcfg.py", line 177, in parse_configuration options.parse() File "/<>/setuptools/config/setupcfg.py", line 500, in parse section_parser_method(section_options) File "/<>/setuptools/config/setupcfg.py", line 727, in parse_section_entry_points self['entry_points'] = parsed File "/<>/setuptools/config/setupcfg.py", line 286, in __setitem__ raise KeyError(option_name) KeyError: 'entry_points' E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: python3.11 setup.py clean [1] https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2037205/+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 2037205] Re: setuptools: FTBFS in mantic
Simple workaround: --- a/debian/rules +++ b/debian/rules @@ -26,7 +26,7 @@ override_dh_auto_clean: # # Keep entry_points, we need it to drive setup.py # -mv setuptools.egg-info/entry_points.txt . - dh_auto_clean + rm -rf $(CURDIR)/.pybuild/ # mkdir -p setuptools.egg-info # mv entry_points.txt setuptools.egg-info -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2037205 Title: setuptools: FTBFS in mantic Status in dh-python package in Ubuntu: New Status in setuptools package in Ubuntu: New Status in setuptools package in Debian: New Bug description: As seen in the mantic test rebuild [1], setuptools 68.1.2-1 currently FTBFS: Traceback (most recent call last): File "/<>/setuptools/config/setupcfg.py", line 284, in __setitem__ current_value = getattr(target_obj, option_name) AttributeError: 'MinimalDistribution' object has no attribute 'entry_points' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/setup.py", line 92, in dist = setuptools.setup(**setup_params) File "/<>/setuptools/__init__.py", line 106, in setup _install_setup_requires(attrs) File "/<>/setuptools/__init__.py", line 77, in _install_setup_requires dist.parse_config_files(ignore_option_errors=True) File "/<>/setuptools/dist.py", line 895, in parse_config_files setupcfg.parse_configuration( File "/<>/setuptools/config/setupcfg.py", line 177, in parse_configuration options.parse() File "/<>/setuptools/config/setupcfg.py", line 500, in parse section_parser_method(section_options) File "/<>/setuptools/config/setupcfg.py", line 727, in parse_section_entry_points self['entry_points'] = parsed File "/<>/setuptools/config/setupcfg.py", line 286, in __setitem__ raise KeyError(option_name) KeyError: 'entry_points' E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: python3.11 setup.py clean [1] https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2037205/+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 2037205] Re: setuptools: FTBFS in mantic
"patch" flag removed from the attachment "patch" tag removed ~ubuntu-sponsors unsubscribed ** Tags removed: patch ** Also affects: dh-python (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2037205 Title: setuptools: FTBFS in mantic Status in dh-python package in Ubuntu: New Status in setuptools package in Ubuntu: New Status in setuptools package in Debian: New Bug description: As seen in the mantic test rebuild [1], setuptools 68.1.2-1 currently FTBFS: Traceback (most recent call last): File "/<>/setuptools/config/setupcfg.py", line 284, in __setitem__ current_value = getattr(target_obj, option_name) AttributeError: 'MinimalDistribution' object has no attribute 'entry_points' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/<>/setup.py", line 92, in dist = setuptools.setup(**setup_params) File "/<>/setuptools/__init__.py", line 106, in setup _install_setup_requires(attrs) File "/<>/setuptools/__init__.py", line 77, in _install_setup_requires dist.parse_config_files(ignore_option_errors=True) File "/<>/setuptools/dist.py", line 895, in parse_config_files setupcfg.parse_configuration( File "/<>/setuptools/config/setupcfg.py", line 177, in parse_configuration options.parse() File "/<>/setuptools/config/setupcfg.py", line 500, in parse section_parser_method(section_options) File "/<>/setuptools/config/setupcfg.py", line 727, in parse_section_entry_points self['entry_points'] = parsed File "/<>/setuptools/config/setupcfg.py", line 286, in __setitem__ raise KeyError(option_name) KeyError: 'entry_points' E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: python3.11 setup.py clean [1] https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2037205/+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 2034986] Re: some text became unreadable during a distribution upgrade
I have uploaded the fix. I am adding block-proposed so that I can do another test, i.e. do-release-upgrade -d -p, just because the manual way of testing differs slightly. ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Mantic: In Progress Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
** Description changed: === SRU information === [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] - This issue is not very simple to reproduce because "penssl cms" cannot be used to do so. This has to be done with the openssl API instead. + This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` -- 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/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: Won't Fix Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "openssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 2036124] Re: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Oh, I didn't realize that--thanks for pointing it out. When I was originally prompted to add compression, I think I found a thread recommending zstd instead. I'll try xz. I do have a decdicated nvidia card on this machine. -- 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/2036124 Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: A crash notification popped up when I was not doing anything so I'm not sure what caused it. I hope the automatically-added debug information contains something useful. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Sep 11 00:24:38 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (704 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: initramfs-tools Title: package linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-08-23 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2036124/+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 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
** Description changed:
=== SRU information ===
[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
+ 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
+ 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
+ /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==
+ /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]
- TBD
+ 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, there is
+
[Touch-packages] [Bug 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/452468
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1923363
Title:
Grant access to hardware (UARTs, I2C, etc.) via custom udev rules
Status in cloud-init package in Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
Invalid
Status in ubuntu-settings package in Ubuntu:
Confirmed
Status in user-setup package in Ubuntu:
Invalid
Status in cloud-init source package in Impish:
Won't Fix
Status in ubiquity source package in Impish:
Invalid
Status in ubuntu-settings source package in Impish:
Won't Fix
Status in user-setup source package in Impish:
Invalid
Status in cloud-init source package in Jammy:
Confirmed
Status in ubiquity source package in Jammy:
Invalid
Status in ubuntu-settings source package in Jammy:
Confirmed
Status in user-setup source package in Jammy:
Invalid
Status in cloud-init source package in Kinetic:
Won't Fix
Status in ubiquity source package in Kinetic:
Invalid
Status in ubuntu-settings source package in Kinetic:
Won't Fix
Status in user-setup source package in Kinetic:
Invalid
Status in cloud-init source package in Lunar:
Won't Fix
Status in ubiquity source package in Lunar:
Invalid
Status in ubuntu-settings source package in Lunar:
Won't Fix
Status in user-setup source package in Lunar:
Invalid
Status in cloud-init source package in Mantic:
Fix Released
Status in ubiquity source package in Mantic:
Invalid
Status in ubuntu-settings source package in Mantic:
Confirmed
Status in user-setup source package in Mantic:
Invalid
Bug description:
We're attempting to make the GPIO system on the Raspberry Pi images
work "out of the box" on the new image. By default, GPIO kernel
devices are made available to members of the "dialout" group which the
initial user is added to by default on our server images. However,
we've noticed that this isn't the case on the desktop images.
The regression potential is minimal; the group already exists and
we're simply adding the freshly created user to a new group and not
removing any existing memberships. The group in question ("dialout")
is also rarely used these days except for providing access to serial
consoles, and as mentioned above is already a default membership on
the server images. The change has been tested on the desktop image
successfully.
A test build of the updated image will be made under
https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
attach a debdiff shortly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+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
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/452468 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Triaged 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/+source/libcamera/+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
[Touch-packages] [Bug 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Status: New => Confirmed -- 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
adding the console log from the failed system - Power10 LPAR ** Attachment added: "maas_console_failing_deploy_mantic_power10" https://bugs.launchpad.net/ubuntu-power-systems/+bug/2037417/+attachment/5705394/+files/maas_console_failing_deploy_mantic_p10 -- 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+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 1990216] Re: backport fix for "OpenSSL 3 cannot decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes" to Jammy
** Description changed:
- OpenSSL upstream implemented a fix for their issue #18359 "OpenSSL 3 cannot
decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes"
- https://github.com/openssl/openssl/issues/18359
+ === SRU information ===
+
+ [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]
+ TBD
+
+ === Original description ===
+
+ OpenSSL upstream implemented a fix for their issue #18359 "OpenSSL 3 cannot
decrypt data encrypted with OpenSSL 1.1 with blowfish in OFB or CFB modes"
+ https://github.com/openssl/openssl/issues/18359
as of libssl3 3.0.4 (and thus it is included in recent libssl3 versions in
Kinetic).
Could this fix be backported to libssl3 in Jammy?
--
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 ===
[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
[Touch-packages] [Bug 2037703] Re: dpkg-reconfigure openssh-server doesn't ask questions again
> looks like there's no db_input/db_go call in the openssh-server.config file. Is that by intention? You're right. Sorry, I knew this but had forgotten it. So openssh-server itself does not ever prompt for either of these settings in mantic, which means there's no risk of dpkg-reconfigure causing confusing behavior vs an sshd_config.d setting. (The debconf settings are still used for special config file merge handling on upgrades.) In trusty-focal, we call db_input for openssh-server/permit-root-login but not for the password auth setting that you're changing; so again there's no confusing behavior. Sorry for the distraction. -- 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/2037703 Title: dpkg-reconfigure openssh-server doesn't ask questions again Status in openssh package in Ubuntu: New Bug description: openssh-server does provide a couple of configuration options: [~]$ sudo debconf-get-selections |grep openssh-server openssh-serveropenssh-server/listenstream-may-failerror openssh-serveropenssh-server/password-authentication boolean true openssh-serveropenssh-server/permit-root-loginboolean true I want to change those options now interactively but nothing I tried worked and showed a dialog: [~]$ sudo dpkg-reconfigure -p low openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. But the documentation (https://manpages.debian.org/testing/debconf- doc/debconf.7.en.html#Reconfiguring_packages) does state that those commands should ask those questions again. p.s. also tried with a lxc debian-sid container and had the same problem there. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.3p1-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 10:35:33 2023 InstallationDate: Installed on 2023-05-10 (142 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2037703/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in The Ubuntu-power-systems project: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+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 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
If I understand the process correctly, dhcpcd is already run in a loop. But the loop is over too quickly if the interface takes a few seconds to come up. -- 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/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+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 1895665] Re: PulseAudio automatically switches away from HDMI after display sleep
*** This bug is a duplicate of bug 1888598 *** https://bugs.launchpad.net/bugs/1888598 Likeit is hardcoded...really? Why? https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/blame/master/src/modules/module-switch-on-connect.c#L36 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1895665 Title: PulseAudio automatically switches away from HDMI after display sleep Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 2037569] Re: udev issues with mantic beta
I think it's caused by udisksctl here: https://github.com/storaged-project/udisks/blob/c7027d888c00381851d918f33a13102e7b86e188/tools/udisksctl.c#L2810C1-L2811C75 due to its repeating monitor messages: udisksctl monitor ** (udisksctl monitor:424911): WARNING **: 11:14:33.100: (udisksctl.c:2811):monitor_on_interface_proxy_properties_changed: runtime check failed: (g_strv_length ((gchar **) invalidated_properties) == 0) -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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
This bug was fixed in the package rpi-eeprom - 18.4-1ubuntu1 --- rpi-eeprom (18.4-1ubuntu1) mantic; urgency=medium * New upstream release (LP: #2037642) * Adds Raspberry Pi 5 support -- Dave Jones Thu, 28 Sep 2023 14:51:50 +0100 ** Changed in: rpi-eeprom (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Triaged 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/+source/libcamera/+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
[Touch-packages] [Bug 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
Could the gnome-shell crash be a consequence of how we are booting the Legacy image and starting the desktop environment? I noticed the following in the crash report "gnome-shell --sm-disable --mode=ubiquity". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
Yes I can confirm this is still an issue for me -- 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/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed Status in launchpad-buildd: Incomplete Status in init-system-helpers package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565 New deb-systemd-invoke added functionality for systemd v250 which ubuntu does not have yet. But it also appears to break postinst calls to deb-systemd-invoke, at least as seen during snap builds in lxd containers operated by launchpad-buildd. I wonder if there is a regression in new code, or new systemd, which may warrant a revert. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+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 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
Hi that was a client Laptop and I don't have access to it anymore -- 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/1987792 Title: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers Status in mesa package in Ubuntu: Incomplete Bug description: Sony laptop with AMD RV710 Try to play a DVD with Vaapi mesa drivers installed ALl players crash , example with VLC ( Works great without VAAPI ) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm" [7fd5d8001610] main vout display debug: using vout display module "gl" [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4028010] main video output debug: original format sz 720x576, of (0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0 [7fd5d4029610] main spu text debug: removing module "freetype" [7fd5d4072b40] main spu text debug: looking for text renderer module matching "any": 2 candidates [7fd5d4072b40] freetype spu text debug: Building font databases. [5601ed37aed0] qt interface debug: Logical video size: 768x576 [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds [7fd5d4072b40] main spu text debug: using text renderer module "freetype" [7fd5d409d080] main generic debug: looking for hw decoder module matching "vaapi": 3 candidates [7fd5d409d080] main generic debug: using hw decoder module "vaapi" [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format(). [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel initialisation. [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode. [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18. [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19. [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a. [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b. [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c. [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d. [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e. [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f. [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20. [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21. [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22. [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23. [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24. [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25. [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26. [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27. [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28. [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29. [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a. [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b. [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c. [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d. [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e. [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f. [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30. [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31. [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32. [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33. [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34. [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35. [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36. [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37. [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38. [mpeg2video @ 0x7fd5d4087d80] Slice 16 param buffer (48 bytes) is
[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result
** Description changed: + === SRU information === + + [Impact] + S/MIME signature can fail silently + The commit by upstream propagates the return code of some functions rather than ignore it. + + [Test plan] + This issue is not very simple to reproduce because "penssl cms" cannot be used to do so. This has to be done with the openssl API instead. + At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. + + [Where problems could occur] + At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. + + === Original description === + https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 - Handle SMIME_crlf_copy return code - - Currently the SMIME_crlf_copy result is ignored in all usages. It does - return failure when memory allocation fails. - - This patch handles the SMIME_crlf_copy return code in all occurrences. - - Signed-off-by: Alon Bar-Lev - - Reviewed-by: Tomas Mraz - Reviewed-by: Paul Dale - Reviewed-by: Hugo Landau - (Merged from https://github.com/openssl/openssl/pull/18876) + Handle SMIME_crlf_copy return code + + Currently the SMIME_crlf_copy result is ignored in all usages. It does + return failure when memory allocation fails. + + This patch handles the SMIME_crlf_copy return code in all + occurrences. + + Signed-off-by: Alon Bar-Lev + + Reviewed-by: Tomas Mraz + Reviewed-by: Paul Dale + Reviewed-by: Hugo Landau + (Merged from https://github.com/openssl/openssl/pull/18876) ``` -- 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/1994165 Title: CMS_final: do not ignore CMS_dataFinal result Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Jammy: In Progress Status in openssl source package in Kinetic: Won't Fix Status in openssl source package in Lunar: Fix Released Bug description: === SRU information === [Impact] S/MIME signature can fail silently The commit by upstream propagates the return code of some functions rather than ignore it. [Test plan] This issue is not very simple to reproduce because "penssl cms" cannot be used to do so. This has to be done with the openssl API instead. At least the bug reportere here and the one on openssl's bug tracker have confirmed the patch solves the issue. Additionally, the bug reporter here has tested the PPA that contains the patche and validated it. Finally, I read through the patch attentively. [Where problems could occur] At this point it is unlikely an error would appear. The openssl bug tracker mentions nothing related to this patch which landed more than a year ago. The patch is simple and doesn't change the code logic. === Original description === https://github.com/openssl/openssl/pull/18876 The CMS_dataFinal result is important as signature may fail, however, it is ignored while returning success from CMS_final. Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)" Thanks Upstream commit: ``` commit 67c0460b89cc1b0644a1a59af78284dfd8d720af Author: Alon Bar-Lev Date: Tue Jul 26 15:17:06 2022 +0300 Handle SMIME_crlf_copy return code Currently the SMIME_crlf_copy result is ignored in all usages. It does return failure when memory allocation fails. This patch handles the SMIME_crlf_copy return code in all occurrences. Signed-off-by: Alon Bar-Lev Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Hugo Landau (Merged from https://github.com/openssl/openssl/pull/18876) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1987792 Title: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers Status in mesa package in Ubuntu: Incomplete Bug description: Sony laptop with AMD RV710 Try to play a DVD with Vaapi mesa drivers installed ALl players crash , example with VLC ( Works great without VAAPI ) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm" [7fd5d8001610] main vout display debug: using vout display module "gl" [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4028010] main video output debug: original format sz 720x576, of (0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0 [7fd5d4029610] main spu text debug: removing module "freetype" [7fd5d4072b40] main spu text debug: looking for text renderer module matching "any": 2 candidates [7fd5d4072b40] freetype spu text debug: Building font databases. [5601ed37aed0] qt interface debug: Logical video size: 768x576 [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds [7fd5d4072b40] main spu text debug: using text renderer module "freetype" [7fd5d409d080] main generic debug: looking for hw decoder module matching "vaapi": 3 candidates [7fd5d409d080] main generic debug: using hw decoder module "vaapi" [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format(). [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel initialisation. [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode. [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18. [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19. [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a. [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b. [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c. [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d. [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e. [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f. [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20. [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21. [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22. [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23. [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24. [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25. [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26. [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27. [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28. [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29. [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a. [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b. [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c. [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d. [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e. [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f. [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30. [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31. [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32. [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33. [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34. [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35. [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36. [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37. [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38. [mpeg2video @ 0x7fd5d4087d80] Slice 16 param buffer (48 bytes) is
[Touch-packages] [Bug 2016435] Re: amdgpu driver randomly resets
Random resets are "typically" triggered by mesa or application bugs. Can you still trigger them in the latest mantic (which has a more up to date mesa and kernel)? ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Invalid ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/2016435 Title: amdgpu driver randomly resets Status in mesa package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: amdgpu tends to randomly reset. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xserver-xorg-video-amdgpu 23.0.0-1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sun Apr 16 18:04:34 2023 DistUpgraded: 2023-04-01 18:21:47,742 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 6.2.0-19-generic, x86_64: installed openrazer-driver/3.4.0, 6.2.0-20-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-19-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1849:5212] NVIDIA Corporation GA104 [GeForce RTX 3060 Ti] [10de:2486] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GA104 [GeForce RTX 3060 Ti] [3842:3663] InstallationDate: Installed on 2022-01-14 (457 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to lunar on 2023-04-01 (14 days ago) dmi.bios.date: 10/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F3c dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF3c:bd10/01/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE DistUpgraded: 2023-04-01 18:21:47,742 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroRelease: Ubuntu 23.04 DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 6.2.0-19-generic, x86_64: installed openrazer-driver/3.4.0, 6.2.0-20-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-19-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced
[Touch-packages] [Bug 1094959] Re: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 failed to install/upgrade
> NonfreeKernelModules: fglrx Nothing that will be done in mesa for an issue with fglrx anyway these days. ** Changed in: mesa (Ubuntu) Status: Incomplete => Won't Fix -- 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/1094959 Title: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 failed to install/upgrade Status in mesa package in Ubuntu: Won't Fix Bug description: I was trying to (re)install Steam, and I got this error. One weird thing that happened before is that Steam (and all it's files) wiped themselves out of my system for no reason... ProblemType: PackageDistroRelease: Ubuntu 12.04 Package: libgl1-mesa-dri 8.0.4-0ubuntu0.2 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17 AptOrdering: libgl1-mesa-dri: Install libgl1-mesa-dri: Configure Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Mon Dec 31 16:48:23 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.000, 3.2.0-34-generic, x86_64: installed fglrx-updates, 9.000, 3.2.0-35-generic, x86_64: installed DpkgTerminalLog: Unpacking libgl1-mesa-dri:i386 (from .../libgl1-mesa-dri_8.0.4-0ubuntu0.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libgl1-mesa-dri_8.0.4-0ubuntu0.2_i386.deb (--unpack): './usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' is different from the same file on the system ErrorMessage: './usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' is different from the same file on the system ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices [AMD] nee ATI Device [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:2556] InstallationMedia: This MachineType: HP-Pavilion FQ601AA-A2L m9505f MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-35-generic root=UUID=4fd95ed0-53b7-4da0-9a18-989348244233 ro quiet splashSourcePackage: mesa Title: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: './usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' is different from the same file on the system UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.43 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnFQ601AA-A2Lm9505f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: FQ601AA-A2L m9505f dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1094959/+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 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
In this case the kernel is the "messenger" for the page fault. This is more likely to be a mesa or application issue than a kernel issue. Can you please raise a ticket to the upstream mesa bug tracker? https://gitlab.freedesktop.org/mesa/mesa/ ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: Hi, Switching a video to or from fullscreen freezes the screen for around 10 seconds. This happens with Totem as well as VLC so its not related to a specific app. Additional observations: - The issue seems to be connected to the video's bitrate. With low bitrate videos I cannot trigger the freeze. However, videos with high bandwidth trigger the freeze reliably. Specs: Ubuntu 23.10 up to date as of 28.09.2023 AMD Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic Grub configured with: amdgpu.vm_update_mode=3 Syslog shows: 2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311) 2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+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 2037569] Re: udev issues with mantic beta
Today I did some more tests and investigations. First of all I moved to the new mantic ISO image (20230928) that improved things quite a lot! The installation (on z/VM so far) is again very snappy and quick, incl. the enablement of a DASD device in the zDev activation screen. At the end of the installation, before hitting 'Reboot now' I went to the console and had a look at top to see if udev related processes are active, but I couldn't identify any: top - 10:47:51 up 9 min, 2 users, load average: 0.44, 0.41, 0.20 Tasks: 137 total, 1 running, 136 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3988.9 total,214.3 free, 1957.6 used, 3233.2 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 2031.3 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 15026 root 20 08788 4864 2816 R 0.7 0.1 0:00.28 top 1439 root 20 0 129824 74216 21376 S 0.3 1.8 0:03.76 /snap/subiquity/5183/usr/bin/python3.10 /snap/subiquity/518+ 1441 root 20 0 129788 74312 21376 S 0.3 1.8 0:03.57 /snap/subiquity/5183/usr/bin/python3.10 /snap/subiquity/518+ 2381 root 20 0 12216 5760 4864 S 0.3 0.1 0:00.10 sudo snap run subiquity 2383 root 20 0 206204 77680 21632 S 0.3 1.9 0:04.96 /snap/subiquity/5183/usr/bin/python3.10 -m subiquity 1 root 20 0 103300 13676 8940 S 0.0 0.3 0:03.49 /sbin/init --- 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kthreadd] 3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [rcu_gp] 4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [rcu_par_gp] 5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [slub_flushwq] 6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [netns] 8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [kworker/0:0H-events_highpri] 9 root 20 0 0 0 0 I 0.0 0.0 0:00.00 [kworker/0:1-cgroup_destroy] 10 root 20 0 0 0 0 I 0.0 0.0 0:01.11 [kworker/u128:0-events_unbound] 11 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [mm_percpu_wq] 12 root 20 0 0 0 0 I 0.0 0.0 0:00.00 [rcu_tasks_rude_kthread] 13 root 20 0 0 0 0 I 0.0 0.0 0:00.00 [rcu_tasks_trace_kthread] Then, having the post-install reboot completed, and looking at top, I can observe the udev activities: top - 10:55:26 up 6 min, 1 user, load average: 2.16, 1.75, 0.84 Tasks: 108 total, 5 running, 103 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.1 us, 22.7 sy, 0.0 ni, 48.8 id, 8.1 wa, 0.6 hi, 0.8 si, 0.9 st MiB Mem : 3988.9 total, 3274.2 free,271.4 used,539.0 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 3717.5 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1177 root 20 0 24884 5724 2560 R 33.2 0.1 1:50.24 (udev-worker) 1 root 20 0 168592 12912 8432 R 20.6 0.3 1:07.93 /sbin/init 690 root 20 0 467964 13112 10752 D 15.6 0.3 0:52.91 /usr/libexec/udisks2/udisksd 660 message+ 20 09328 4480 3840 S 14.6 0.1 0:52.68 @dbus-daemon --system --address=systemd: --nofork --nopidfile -+ 16285 ubuntu20 0 18004 9984 8448 S 10.6 0.2 0:33.06 /lib/systemd/systemd --user 385 root 20 0 24764 7492 4676 S 9.3 0.2 0:30.40 /lib/systemd/systemd-udevd 373 root rt 0 288412 26368 8064 S 6.6 0.6 0:21.50 /sbin/multipathd -d -s 686 root 20 0 16096 7424 6528 S 4.0 0.2 0:13.20 /lib/systemd/systemd-logind 681 root 20 0 2066332 34480 21248 S 1.7 0.8
[Touch-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Changed in: rpi-eeprom (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged 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/+source/libcamera/+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
[Touch-packages] [Bug 2037703] Re: dpkg-reconfigure openssh-server doesn't ask questions again
looks like there's no db_input/db_go call in the openssh-server.config file. Is that by intention? -- 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/2037703 Title: dpkg-reconfigure openssh-server doesn't ask questions again Status in openssh package in Ubuntu: New Bug description: openssh-server does provide a couple of configuration options: [~]$ sudo debconf-get-selections |grep openssh-server openssh-serveropenssh-server/listenstream-may-failerror openssh-serveropenssh-server/password-authentication boolean true openssh-serveropenssh-server/permit-root-loginboolean true I want to change those options now interactively but nothing I tried worked and showed a dialog: [~]$ sudo dpkg-reconfigure -p low openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. But the documentation (https://manpages.debian.org/testing/debconf- doc/debconf.7.en.html#Reconfiguring_packages) does state that those commands should ask those questions again. p.s. also tried with a lxc debian-sid container and had the same problem there. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.3p1-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 10:35:33 2023 InstallationDate: Installed on 2023-05-10 (142 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2037703/+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 1967593] Re: kernel modules going missing after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-lowlatency package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1
[Touch-packages] [Bug 1967593] Re: kernel modules going missing after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lowlatency (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-lowlatency package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation
[Touch-packages] [Bug 1967593] Re: kernel modules going missing after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-kvm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-lowlatency package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1
[Touch-packages] [Bug 2037497]
aha, thanks! -- 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/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in Mutter: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497]
(In reply to Adam Williamson from comment #14) > Can reporters please test downgrading packages to figure out what actually > fixes this? I'd suggest this order: > > 1. Downgrade mesa to > https://koji.fedoraproject.org/koji/buildinfo?buildID=2274339 > 2. If that doesn't fix it, downgrade mutter and gnome-shell to > https://koji.fedoraproject.org/koji/buildinfo?buildID=2284675 and > https://koji.fedoraproject.org/koji/buildinfo?buildID=2284676 > > if that doesn't fix it, report back and we'll try something else, I guess. :D > > Instructions for downgrading: `dnf -y install koji`, then make a scratch dir > somewhere (in your home dir or /var/tmp or something), and do `koji > download-build --arch=x86_64 --arch=noarch (buildid)` , where (buildid) is > the build ID from the URL, so 2274339 for mesa. Then do `dnf downgrade > *.rpm`. None of this worked, nor mesa-23.2.0~rc2-1.fc39. I was able to get it working again by downgrading to mesa-23.1.5-1.fc39 (build 2268808). Will try to bisect. -- 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/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in Mutter: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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
Debdiff with squash of https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Briefly tested on Pi 5, 4 and 400. Desktop comes up and glx and vulkan are accelerated. ** Patch added: "mesa_23.2.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2037642/+attachment/5705304/+files/mesa_23.2.1-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged 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/+source/libcamera/+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
[Touch-packages] [Bug 2037703] [NEW] dpkg-reconfigure openssh-server doesn't ask questions again
Public bug reported: openssh-server does provide a couple of configuration options: [~]$ sudo debconf-get-selections |grep openssh-server openssh-server openssh-server/listenstream-may-failerror openssh-server openssh-server/password-authentication boolean true openssh-server openssh-server/permit-root-loginboolean true I want to change those options now interactively but nothing I tried worked and showed a dialog: [~]$ sudo dpkg-reconfigure -p low openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. But the documentation (https://manpages.debian.org/testing/debconf- doc/debconf.7.en.html#Reconfiguring_packages) does state that those commands should ask those questions again. p.s. also tried with a lxc debian-sid container and had the same problem there. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.3p1-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 10:35:33 2023 InstallationDate: Installed on 2023-05-10 (142 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2037703 Title: dpkg-reconfigure openssh-server doesn't ask questions again Status in openssh package in Ubuntu: New Bug description: openssh-server does provide a couple of configuration options: [~]$ sudo debconf-get-selections |grep openssh-server openssh-serveropenssh-server/listenstream-may-failerror openssh-serveropenssh-server/password-authentication boolean true openssh-serveropenssh-server/permit-root-loginboolean true I want to change those options now interactively but nothing I tried worked and showed a dialog: [~]$ sudo dpkg-reconfigure -p low openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. But the documentation (https://manpages.debian.org/testing/debconf- doc/debconf.7.en.html#Reconfiguring_packages) does state that those commands should ask those questions again. p.s. also tried with a lxc debian-sid container and had the same problem there. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.3p1-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 10:35:33 2023 InstallationDate: Installed on 2023-05-10 (142 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2037703/+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 2037399] Re: Processes keep running after "systemctl stop"
This seems to be a related problem: Sep 29 07:00:30 hyades systemd[1]: apt-daily-upgrade.service: Unit process 51088 (exim4) remains running after unit stopped. I would think that apt-daily-upgrade relies on exim4 getting actually restarted after an update. If the process remains running, does that not potentially cause trouble? -- 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/2037399 Title: Processes keep running after "systemctl stop" Status in systemd package in Ubuntu: New Bug description: I have a number of Ubuntu 22.04 installations on various computers. In the last month, I have seen more and more log messages like the following from different systems: ``` systemd[1]: apache2.service: Unit process 70257 (apache2) remains running after unit stopped. systemd[1]: exim4.service: Unit process 61890 (exim4) remains running after unit stopped. ``` I started considering this a problem when subsequently, some php processes continued running after `systemctl stop apache2.service`. This can be a problem when rogue processes interfere with my file- based backup. I had at least one case where a rogue `php` process started misbehaving after both `apache2` and `mysql` where stopped. The `php` processes continued running, possibly inside a rogue `apache2` process, but failed to continue its normal operation due to the absence of `mysql`. Motivation: I have a nightly backup script that stops common services like `exim4`, `apache2` and `mysql`, then performs file-based backup, and subsequently starts services again. I was relying on the fact that processes would end after `systemctl stop`, and do not modify the file system anymore. But this seems not always to be the case? I do not necessarily think that this is a duplicate of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2013543. The way I understand the other bug is that systemd forgets about running processes. Here in my case, systemd seems well aware that not all processes ended, at least this is what the log message indicates. But systemd does not force them to quit. Expected behavior: After `systemctl stop`, I would need all processes to end. This would be required so that I can be sure that it is safe to perform file based backup, without modifications on the file system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037399/+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 2037698] Re: Icon theme changed after recent update
** Package changed: xorg (Ubuntu) => yaru-theme (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2037698 Title: Icon theme changed after recent update Status in yaru-theme package in Ubuntu: New Bug description: Recently the software got updated and all the icons of the pre- installed apps were changed. I tried to change the icon theme using gnome-tweaks. But it is of no use. I need the icons to be like the time of my first installation of ubuntu. I have also tried to copy the theme from my friend's laptop to edit the change, But this was also of no use. Please look into it and help me to find the solution ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 11:58:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:8778] InstallationDate: Installed on 2022-11-01 (331 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14s-er0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=7facb30b-d308-4a9f-876f-f235cfa36a6a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2021 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8778 dmi.board.vendor: HP dmi.board.version: 14.14 dmi.chassis.asset.tag: 5CG0172W2M dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.14 dmi.modalias: dmi:bvnAMI:bvrF.14:bd02/02/2021:br15.14:efr14.14:svnHP:pnHPLaptop14s-er0xxx:pvr:rvnHP:rn8778:rvr14.14:cvnHP:ct10:cvrChassisVersion:sku3C465PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14s-er0xxx dmi.product.sku: 3C465PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2037698/+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 2037698] Re: Icon theme changed after recent update
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2037698 Title: Icon theme changed after recent update Status in yaru-theme package in Ubuntu: New Bug description: Recently the software got updated and all the icons of the pre- installed apps were changed. I tried to change the icon theme using gnome-tweaks. But it is of no use. I need the icons to be like the time of my first installation of ubuntu. I have also tried to copy the theme from my friend's laptop to edit the change, But this was also of no use. Please look into it and help me to find the solution ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 11:58:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:8778] InstallationDate: Installed on 2022-11-01 (331 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14s-er0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=7facb30b-d308-4a9f-876f-f235cfa36a6a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2021 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8778 dmi.board.vendor: HP dmi.board.version: 14.14 dmi.chassis.asset.tag: 5CG0172W2M dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.14 dmi.modalias: dmi:bvnAMI:bvrF.14:bd02/02/2021:br15.14:efr14.14:svnHP:pnHPLaptop14s-er0xxx:pvr:rvnHP:rn8778:rvr14.14:cvnHP:ct10:cvrChassisVersion:sku3C465PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14s-er0xxx dmi.product.sku: 3C465PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2037698/+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 2031919] Re: /usr/share/apport/whoopsie-upload-all:TypeError:/usr/share/apport/whoopsie-upload-all@247:main:collect_info:process_report:add_gdb_info
This bug was fixed in the package apport - 2.27.0-0ubuntu3 --- apport (2.27.0-0ubuntu3) mantic; urgency=medium * fix: raise "gdb not found" as soon as detected (LP: #2031919) * bash-completion: Do not use ls in completion (LP: #1850804) -- Benjamin Drung Fri, 29 Sep 2023 01:03:44 +0200 ** Changed in: apport (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2031919 Title: /usr/share/apport/whoopsie-upload- all:TypeError:/usr/share/apport/whoopsie-upload- all@247:main:collect_info:process_report:add_gdb_info Status in apport package in Ubuntu: Fix Released Bug description: ``` Traceback (most recent call last): File "/usr/share/apport/whoopsie-upload-all", line 247, in main() File "/usr/share/apport/whoopsie-upload-all", line 229, in main stamps = collect_info() ^^ File "/usr/share/apport/whoopsie-upload-all", line 160, in collect_info res = process_report(r) ^ File "/usr/share/apport/whoopsie-upload-all", line 108, in process_report r.add_gdb_info() File "/usr/lib/python3/dist-packages/apport/report.py", line 930, in add_gdb_info environ["HOME"] = "/nonexistent" ~~~ TypeError: 'str' object does not support item assignment ``` The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.26.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/86a1629347349acf400d91c9774296b42c1ab1f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2031919/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
I wonder if this is duplicate of https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202 And if the workaround in https://bugs.launchpad.net/ubuntu/+source/initramfs- tools/+bug/2037202/comments/1 can keep us going -- 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in systemd package in Ubuntu: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+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
** Changed in: libcamera (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-meta-raspi (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: pipewire (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged 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/+source/libcamera/+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
[Touch-packages] [Bug 1850804] Re: Tab completion warnings with ubuntu-bug when using alias for ls
This bug was fixed in the package apport - 2.27.0-0ubuntu3 --- apport (2.27.0-0ubuntu3) mantic; urgency=medium * fix: raise "gdb not found" as soon as detected (LP: #2031919) * bash-completion: Do not use ls in completion (LP: #1850804) -- Benjamin Drung Fri, 29 Sep 2023 01:03:44 +0200 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1850804 Title: Tab completion warnings with ubuntu-bug when using alias for ls Status in Apport: In Progress Status in apport package in Ubuntu: Fix Released Bug description: When running ubuntu-bug on the command line, and tab completing the package name, the following warnings are printed: /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory This happens when following alias is set: alias ls='ls -N --color=yes --time-style=long-iso' ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Oct 31 10:54:43 2019 InstallationDate: Installed on 2017-08-16 (805 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1850804/+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 2037417] Re: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems
I have tested booting with various initrd/kernel/squashfs combinations. * The mantic 6.5.0-5 kernel and modules repacked into a jammy (20230927) or lunar (20230927) initrd and squashfs result in a deployed host. * The mantic initrd and squashfs from 20230908 with the 6.5.0-5 kernel did not deploy. * The original 20230908 mantic maas image (with the 6.3.0-7-generic kernel) does boot. So the 6.5.0-5 kernel works with older images, but not any of the recent mantic images. -- 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/2037417 Title: mantic images after 20230917 are failing to deploy with failure to mount root and kernel filesystems Status in maas-images: New Status in systemd package in Ubuntu: New Bug description: Mantic arm64 deploys started failing on Sept 18th with: [ 41.913552] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Starting [0;1;39msystemd-remount-f鈥t Root and Kernel File Systems... [ 41.940748] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Starting [0;1;39msystemd-udev-trig鈥0m - Coldplug All udev Devices... [ 41.964758] systemd[1]: Started systemd-journald.service - Journal Service. [[0;32m OK [0m] Started [0;1;39msystemd-journald.service[0m - Journal Service. [[0;32m OK [0m] Mounted [0;1;39mdev-hugepages.mount[0m - Huge Pages File System. [[0;32m OK [0m] Mounted [0;1;39mdev-mqueue.mount[鈥�- POSIX Message Queue File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-debug.m鈥t[0m - Kernel Debug File System. [[0;32m OK [0m] Mounted [0;1;39msys-kernel-tracing鈥t[0m - Kernel Trace File System. [[0;32m OK [0m] Finished [0;1;39mkeyboard-setup.se鈥�- Set the console keyboard layout. [[0;32m OK [0m] Finished [0;1;39mkmod-static-nodes鈥eate List of Static Device Nodes. [[0;32m OK [0m] Finished [0;1;39mlvm2-monitor.serv鈥ing dmeventd or progress polling. [[0;32m OK [0m] Finished [0;1;39mmodprobe@configfs鈥0m - Load Kernel Module configfs. [[0;32m OK [0m] Finished [0;1;39mmodprobe@dm_mod.s鈥[0m - Load Kernel Module dm_mod. [[0;32m OK [0m] Finished [0;1;39mmodprobe@drm.service[0m - Load Kernel Module drm. [[0;32m OK [0m] Finished [0;1;39mmodprobe@efi_psto鈥 - Load Kernel Module efi_pstore. [[0;32m OK [0m] Finished [0;1;39mmodprobe@fuse.service[0m - Load Kernel Module fuse. [[0;32m OK [0m] Finished [0;1;39mmodprobe@loop.service[0m - Load Kernel Module loop. [[0;32m OK [0m] Finished [0;1;39msystemd-modules-l鈥ervice[0m - Load Kernel Modules. [[0;1;31mFAILED[0m] Failed to start [0;1;39msystemd-re鈥unt Root and Kernel File Systems. See 'systemctl status systemd-remount-fs.service' for details. After this many other services and cloud-init fails. See the full kopter-0918.log. For comparison, a log from the prior day's test is also attached. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2037417/+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 2037697] [NEW] Xorg freeze when browsing the web
Public bug reported: While using my computer, the screen suddenly goes black with a blinking cursor. It is the 2nd or 3rd time, this time when browsing with Firefox 108.0 (it was at the end of a youtube video), no other apps loaded. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12 19:41:24 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 07:00:09 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094] InstallationDate: Installed on 2023-09-19 (9 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=7a808742-50c6-42f2-9ff3-d1faeb2d8470 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.32 dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze lunar ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2037697 Title: Xorg freeze when browsing the web Status in xorg package in Ubuntu: New Bug description: While using my computer, the screen suddenly goes black with a blinking cursor. It is the 2nd or 3rd time, this time when browsing with Firefox 108.0 (it was at the end of a youtube video), no other apps loaded. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
[Touch-packages] [Bug 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
** Changed in: openssl
Status: Unknown => Fix Released
--
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/1864689
Title:
openssl in 20.04 can't connect to site that was fine in 19.10 and is
fine in Chrome and Firefox
Status in OpenSSL:
Fix Released
Status in openssl package in Ubuntu:
Invalid
Bug description:
openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.
Reproduce with: `curl -v https://www.toodledo.com/'
or: `openssl s_client -connect www.toodledo.com:443`
or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`
or: `wget https://www.toodledo.com/`
These worked in Ubuntu 19.10 and don't work in 20.04.
I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will
be able to figure it out.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1864689/+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 2037698] [NEW] Icon theme changed after recent update
You have been subscribed to a public bug: Recently the software got updated and all the icons of the pre-installed apps were changed. I tried to change the icon theme using gnome-tweaks. But it is of no use. I need the icons to be like the time of my first installation of ubuntu. I have also tried to copy the theme from my friend's laptop to edit the change, But this was also of no use. Please look into it and help me to find the solution ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 11:58:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:8778] InstallationDate: Installed on 2022-11-01 (331 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14s-er0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=7facb30b-d308-4a9f-876f-f235cfa36a6a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2021 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8778 dmi.board.vendor: HP dmi.board.version: 14.14 dmi.chassis.asset.tag: 5CG0172W2M dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.14 dmi.modalias: dmi:bvnAMI:bvrF.14:bd02/02/2021:br15.14:efr14.14:svnHP:pnHPLaptop14s-er0xxx:pvr:rvnHP:rn8778:rvr14.14:cvnHP:ct10:cvrChassisVersion:sku3C465PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14s-er0xxx dmi.product.sku: 3C465PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- Icon theme changed after recent update https://bugs.launchpad.net/bugs/2037698 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade
On 2023-09-26 22:32, Gunnar Hjalmarsson wrote: > But one of the changes in mantic is that no font is safely present > (i.e. the default ones are "Recommends:" only). So later, when people > will upgrade from 23.10 to 24.04, just using "Sans" temporarily may > not be the best option. And changing it to a specific font family is > tricky, since we don't know if the user has uninstalled some of the > default font packages. > > So my thought is: Can this be a reason to let desktop-common depend > on, and not only recommend, some font package after all? And if so, > which package would be suitable for the purpose? To make it easier to keep 'the temporary font' approach in 24.04 — if that is what we want by then — I added a hard dependency on fonts- dejavu-core to desktop-common. No upstream changes to the DejaVu fonts have been made the last 6 years, so it's more or less unmaintained, which in this context is an advantage. ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: ubuntu-meta (Ubuntu Mantic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: In Progress Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
We could create an /etc/apport/report-ignore/ file with the contents '/usr/bin/gnome-shell' so then at least the crash report dialog would not appear. However, after choosing try Ubuntu you presented with a black screen and some console output so its still not a great experience. ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu) Milestone: None => ubuntu-23.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2037210] Re: unable to add PPA by its sources.list line
@Nick Rosbrook (enr0n) Your assumption is correct only in the case when PPA_release = distro_release. But in my case the situation is different: 1. distro version is 23.10, 2. PPA provides packages only for 22.04 LTS. Also please note that there are some obsolete PPAs where their owner is not available of lost the interest for maintaining the packages. So for some packages it is impossible to run `apt-add-repository ppa:user/archive`. So please support old behavior of add-apt-repository. This will make possible to run the below command ``` sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" # note that jammy!=mantic ``` on modern Ubuntu 23.10 without issues. --- Actually it is good that third-party repository support in software- properties-common is not broken, so the following commands work without issues on 23.10: ``` sudo apt-get install software-properties-common sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv A2F683C52980AECF sudo add-apt-repository -y "deb [arch=amd64] https://download.virtualbox.org/virtualbox/debian jammy contrib" sudo apt-get install virtualbox-7.0 ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2037210 Title: unable to add PPA by its sources.list line Status in Software Properties: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 23.10 installed 2. Run ``` sudo apt-key adv --keyserver keyserver.ubuntu.com --recv E756285F30DB2B2BB35012E219BFCAF5168D33A9 sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" ``` Expected results: * key added, two repositories are added to the relevant *.list files at /etc/apt/sources.list.d/ Actual results: * relevant *.list files at /etc/apt/sources.list.d/ are not created, having errors instead ``` $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main Components: ' Description: This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by stupid bug https://pad.lv/1922276 . So user will be able to select all terminal output with full scroll-back in MATE Terminal and other VTE-based terminals as it is expected. This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade VTE packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte Adding repository. E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main Components: ' Description: This PPA provides patched libwnck3 package to fix https://github.com/mate-desktop/mate-panel/issues/1230 and https://pad.lv/1947420 . See details at https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 . This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade WNCK packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck Adding repository. Found existing deb entry in /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo apt-get update E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-common 0.99.39 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback Date: Sun Sep 24 14:02:10 2023 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411 To manage notifications
[Touch-packages] [Bug 2037210] Re: unable to add PPA by its sources.list line
** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2037210 Title: unable to add PPA by its sources.list line Status in Software Properties: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 23.10 installed 2. Run ``` sudo apt-key adv --keyserver keyserver.ubuntu.com --recv E756285F30DB2B2BB35012E219BFCAF5168D33A9 sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" ``` Expected results: * key added, two repositories are added to the relevant *.list files at /etc/apt/sources.list.d/ Actual results: * relevant *.list files at /etc/apt/sources.list.d/ are not created, having errors instead ``` $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/vte/ubuntu jammy main Components: ' Description: This PPA contains VTE library from Ubuntu 20.04 LTS which is not affected by stupid bug https://pad.lv/1922276 . So user will be able to select all terminal output with full scroll-back in MATE Terminal and other VTE-based terminals as it is expected. This PPA is useful for Ubuntu 22.04 LTS, Debian 11 (bullseye) and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade VTE packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/vte`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/vte Adding repository. E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo add-apt-repository -y "deb http://ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main" Repository: 'deb http: //ppa.launchpad.net/nrbrtx/wnck/ubuntu jammy main Components: ' Description: This PPA provides patched libwnck3 package to fix https://github.com/mate-desktop/mate-panel/issues/1230 and https://pad.lv/1947420 . See details at https://github.com/mate-desktop/mate-panel/issues/1230#issuecomment-997422612 . This PPA is useful for Ubuntu 22.04 LTS and Debian 12 (bookworm). As usual one can always remove this PPA and downgrade WNCK packages by using `sudo apt-get install ppa-purge` and `sudo ppa-purge ppa:nrbrtx/wnck`. More info: https://launchpad.net/~nrbrtx/+archive/ubuntu/wnck Adding repository. Found existing deb entry in /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. $ sudo apt-get update E: Malformed entry 1 in sources file /etc/apt/sources.list.d/nrbrtx-ubuntu-vte-mantic.sources (URI) E: The list of sources could not be read. ``` ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: software-properties-common 0.99.39 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback Date: Sun Sep 24 14:02:10 2023 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to mantic on 2023-04-13 (164 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-24T13:25:34.901411 To manage notifications about this bug go to: https://bugs.launchpad.net/software-properties/+bug/2037210/+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 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
Should dhcp really be oneshot? I don't know what dhclient was doing (I guess it was dhclient before) but it sounds difficult to synchronize this properly. I imagine it's also possible to run the dhcp client in oneshot mode in a loop with maybe 3 iterations and "sleep 1" in between. -- 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/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+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 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
** Tags removed: rls-mm-incoming ** Tags added: foundations-todo -- 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/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+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 2037425] Re: ubuntu-server pulls in ZFS userspace
** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+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 2037425] Re: ubuntu-server pulls in ZFS userspace
This bug was fixed in the package ubuntu-meta - 1.522 --- ubuntu-meta (1.522) mantic; urgency=medium * Refreshed dependencies * Removed zfs-initramfs from server [amd64 arm64 ppc64el riscv64 s390x], server-raspi [amd64 arm64 ppc64el riscv64 s390x] (LP: #2037425) * Removed zfsutils-linux from server, server-raspi -- Dan Bungert Thu, 28 Sep 2023 10:32:46 -0600 ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+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 2037527] Re: [Ffe] libwebp
Hello, it is needed for new libavif, as explained in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022001 Having the new version will make easier to build it with finally the sharpyuv functionality. That said, will be anyway autosync next time we open, so there should be plenty of time to fix it properly before 24.04. My idea was to ship in 23.10 to let users broadly test before next LTS. Not a big deal, I'll close this bug and let it sync for NANIMAL ** Bug watch added: Debian Bug tracker #1022001 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022001 ** Changed in: libwebp (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp Status in libwebp package in Ubuntu: Invalid Bug description: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) Changes since mantic version 1.2.4-0.3 == libwebp (1.3.2-0.3) unstable; urgency=medium * Non-maintainer upload. * Fix invalid incremental decoding check. (Closes: #1052447) * Fix next is invalid pointer when WebPSafeMalloc fails * Fix static analyzer warnings. -- Salvatore Bonaccorso Fri, 22 Sep 2023 09:41:18 +0200 libwebp (1.3.2-0.2) unstable; urgency=medium * Non-maintainer upload. * debian/control: Add missing dependency libwebp-dev => libsharpyuv-dev. (Closes: #1052355) -- Boyuan Yang Wed, 20 Sep 2023 15:59:13 -0400 libwebp (1.3.2-0.1) unstable; urgency=medium * Non-maintainer upload. * Upload to unstable. -- Boyuan Yang Wed, 20 Sep 2023 11:03:28 -0400 libwebp (1.3.2-0.1~exp2) experimental; urgency=medium * Non-maintainer upload. [ Gianfranco Costamagna ] * Also install .a files again. * Make sure we have built and installed anim_dump and anim_diff. (Closes: #1023482) -- Boyuan Yang Fri, 15 Sep 2023 14:41:40 -0400 libwebp (1.3.2-0.1~exp1) experimental; urgency=medium * Non-maintainer upload. * New upstream release 1.3.2. + The 1.3.x branch introduces libsharpyuv, which will be introduced as separate Debian binary packages. (Closes: #1040970) + CVE-2023-4863 is handled in this release. (LP: #2035220) * debian/gbp.conf: Use ignore-branch=True to avoid limitation on experimental branch. * debian/control: + Drop unnecessary build-dependency on autotools-related packages. + Add build-dependency on pkg-config. + Migrate buildsystem to cmake. (Closes: #1040972, LP: #2013083) + Apply RPATH-related hotfix before debhelper compat level 14. + Add new binary packages: libsharpyuv-dev, libsharpyuv0, libwebpdecoder3. * debian/libwebp-dev.install: Do not install static library anymore since CMake is not building them by default. * debian/rules: + Enforce --buildsystem=cmake. + Drop explicit option --enable-aligned, this option has been removed by libwebp upstream (see upstream ChangeLog). * debian/docs: Rename to libwebp-dev.docs to avoid confusion. * debian/patches: Drop all old patches, merged upstream. * debian/patches/: + 0001-CMakeLists.txt-Install-CMake-Config-to-arch-dep-loca.patch: Add patch to install CMake Config files to architecture-dependent location instead to retain Multi-Arch property of dev packages. * debian/copyright: Completely rewritten in machine-readable copyright format. -- Boyuan Yang Thu, 14 Sep 2023
[Touch-packages] [Bug 2037425] Re: ubuntu-server pulls in ZFS userspace
seed MP merged, dput of ubuntu-meta done. ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+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 2037531] Re: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1
Ok. Reassigning to apt, which is where we would want to clean the process environment. ** Package changed: perl (Ubuntu) => apt (Ubuntu) ** Changed in: apt (Ubuntu) Importance: High => Low ** Changed in: apt (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/2037531 Title: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 Status in apt package in Ubuntu: Triaged Bug description: Doing a release upgrade from 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam0g:amd64 1.4.0-11ubuntu2.3 ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246 Uname: Linux 5.4.0-163-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Wed Sep 27 11:19:52 2023 DuplicateSignature: package:libpam0g:amd64:1.4.0-11ubuntu2.3 Setting up libpam0g:amd64 (1.4.0-11ubuntu2.3) ... ListUtil.c: loadable library and perl binaries are mismatched (got handshake key 0xcd00080, needed 0xeb00080) dpkg: error processing package libpam0g:amd64 (--configure): installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 ErrorMessage: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-12-14 (1016 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.0.9 SourcePackage: pam Title: package libpam0g:amd64 1.4.0-11ubuntu2.3 failed to install/upgrade: installed libpam0g:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2037531/+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
FFe granted for the remaining packages -- 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 libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged 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/+source/libcamera/+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
[Touch-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Tags added: mantic raspi raspigfx ** Tags removed: raspigfx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged 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/+source/libcamera/+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
[Touch-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
FFe for linux-firmware-raspi in LP: #2037634 FFe for gpiozero in LP: #2037637 ** No longer affects: linux-firmware-raspi (Ubuntu) ** Changed in: libcamera (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux-meta-raspi (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Triaged ** Changed in: mesa (Ubuntu) Status: Confirmed => Triaged ** Changed in: pipewire (Ubuntu) Status: Confirmed => Triaged ** Changed in: rpi-eeprom (Ubuntu) Status: Confirmed => Triaged ** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Triaged -- 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 libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged 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/+source/libcamera/+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
[Touch-packages] [Bug 2037691] [NEW] Audio output stopped working
Public bug reported: Audio output was working fine when i installed ubuntu 1.5 years ago. Approximately a year ago it stopped working, might be because i updated to linux 22.04 then, now i have updated to 23.04 and the issue remains. I tried reinstalling drivers, but nothing helps ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: telemak1863 F wireplumber /dev/snd/controlC0: telemak1863 F wireplumber /dev/snd/seq:telemak1856 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 03:38:05 2023 InstallationDate: Installed on 2022-04-28 (518 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-09-27 (1 days ago) dmi.bios.date: 04/08/2022 dmi.bios.release: 2.10 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: NBM-WXX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1020 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1020 dmi.ec.firmware.release: 2.10 dmi.modalias: dmi:bvnHUAWEI:bvr2.10:bd04/08/2022:br2.10:efr2.10:svnHUAWEI:pnNBM-WXX9:pvrM1020:rvnHUAWEI:rnNBM-WXX9-PCB-B2:rvrM1020:cvnHUAWEI:ct10:cvrM1020:skuC171: dmi.product.family: MateBook D dmi.product.name: NBM-WXX9 dmi.product.sku: C171 dmi.product.version: M1020 dmi.sys.vendor: HUAWEI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2037691 Title: Audio output stopped working Status in pulseaudio package in Ubuntu: New Bug description: Audio output was working fine when i installed ubuntu 1.5 years ago. Approximately a year ago it stopped working, might be because i updated to linux 22.04 then, now i have updated to 23.04 and the issue remains. I tried reinstalling drivers, but nothing helps ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: telemak1863 F wireplumber /dev/snd/controlC0: telemak1863 F wireplumber /dev/snd/seq:telemak1856 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 03:38:05 2023 InstallationDate: Installed on 2022-04-28 (518 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-09-27 (1 days ago) dmi.bios.date: 04/08/2022 dmi.bios.release: 2.10 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: NBM-WXX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1020 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1020 dmi.ec.firmware.release: 2.10 dmi.modalias: dmi:bvnHUAWEI:bvr2.10:bd04/08/2022:br2.10:efr2.10:svnHUAWEI:pnNBM-WXX9:pvrM1020:rvnHUAWEI:rnNBM-WXX9-PCB-B2:rvrM1020:cvnHUAWEI:ct10:cvrM1020:skuC171: dmi.product.family: MateBook D dmi.product.name: NBM-WXX9 dmi.product.sku: C171 dmi.product.version: M1020 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2037691/+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 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies
The DEP8 tests are green now, but we still need verification on this bug. -- 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/1964506 Title: Ping: checks payloads incorrectly, ignores all mismatch replies Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Focal: Fix Committed Bug description: = Impact = the ping statistics are incorrect when dealing with truncated packets = Test case = $ ping -c 1 -s 1200 8.8.8.8 should list truncated replies and received packets = Regression potential = the changes are limited to the ping source any regression would impact that utility, check that responses are correctly handled and statistics reflecting what is expected -- Problematic commit reverted upstream causing incorrect behavior in Ubuntu Focal. Discussion: https://github.com/iputils/iputils/issues/320 Fix: https://github.com/iputils/iputils/pull/321 Release: https://github.com/iputils/iputils/releases/tag/20210722 Could this patch be added for a Focal update please? 1) Ubuntu 20.04.3 LTS 2) 3:20190709-3 3) focal$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. --- 8.8.8.8 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms 4) xenial$ ping -c 1 -s 1200 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated) --- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1964506/+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 1958676] Re: error: too early for operation, device not yet seeded or device model not acknowledged Install failed
Stumbled on this in triage. The bug description writes about "added functionality for systemd v250 which ubuntu does not have yet", which is not the case anymore. The bug report didn't have any significant activity in >1 year. Is this still an issue? ** Changed in: launchpad-buildd Status: New => Incomplete ** Changed in: init-system-helpers (Ubuntu) Status: Confirmed => Incomplete ** Changed in: snapd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: sssd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1958676 Title: error: too early for operation, device not yet seeded or device model not acknowledged Install failed Status in launchpad-buildd: Incomplete Status in init-system-helpers package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: https://launchpad.net/~ubuntu-core-service/+snap/core22/+build/1650565 New deb-systemd-invoke added functionality for systemd v250 which ubuntu does not have yet. But it also appears to break postinst calls to deb-systemd-invoke, at least as seen during snap builds in lxd containers operated by launchpad-buildd. I wonder if there is a regression in new code, or new systemd, which may warrant a revert. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1958676/+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
