[Touch-packages] [Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
I wonder if there is a method or a script which can be run automatically to check printer status and remove the certificate if something is wrong? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss
I agree that the importance should be higher than "Low". This bug is also triggered every time a "netplan apply" is run, since netplan will always re-generate the systemd-networkd config files. VLAN interfaces are also torn down and recreated. This is highly problematic on critical networking hosts, such as firewalls, since any networking configuration change will trigger seconds of downtime, which can lead to VRRP failovers, etc... -- 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/2003250 Title: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: We currently use Ubuntu 22.04.1 LTS including updates for our production cloud (switched from legacy Centos 7). Although we like the distribution we recently hit serious systemd buggy behavior described in [1] bugreport using packages [2]. Unfortunatelly the clouds we are running consist of openstack on top of kubernetes and we need to have complex network configuration including linux bond devices. Our observation is that every time we apply our configuration via CI/CD infrastructure using ansible and netplan (regardless whether there is actual network configuration change) we see approximatelly 8-16 seconds network interruptions and see bond interfaces going DOWN and then UP. We expect bond interfaces stay UP when there is no network configuration change. We went though couple of options how to solve the issue and the first one is to add such existing patch [3] into current systemd-249.11-0ubuntu3.6. Could you comment whether this kind of non-security patch is likely to land in 22.04.1 LTS soon. We are able to help to bring patch into systemd package community way if you suggest the steps. [1] https://github.com/systemd/systemd/issues/25067 [2] Packages root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)' netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 [installed,automatic] systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic] [3] https://github.com/systemd/systemd/pull/25162 [4] # lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+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 2028935] Re: Merge rsyslog 8.2306.0-2
A build of rsyslog - 8.2306.0-2ubuntu1 is available in ppa:xypron/merge- from-debian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2028935 Title: Merge rsyslog 8.2306.0-2 Status in rsyslog package in Ubuntu: New Bug description: Debian has upgraded rsyslog to 8.2306.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2028935/+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 2028879] Re: Lack of default dpkg diverts causes test_get_file_package_diversion to fail
https://github.com/canonical/apport/pull/214 was merged ** Changed in: apport Status: In Progress => Fix Committed -- 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/2028879 Title: Lack of default dpkg diverts causes test_get_file_package_diversion to fail Status in Apport: Fix Committed Status in apport package in Ubuntu: Triaged Bug description: tests/integration/test_packaging_apt_dpkg.py::test_get_file_package_diversion fails if it doesn't detect any dpkg diversions. Apparently something (possibly dash?) stopped diverting something, so now there are no diversions in the autopkgtest environment and therefore this test fails. One option is to add something that does divert something, eg. vim, to the test dependencies. This fixes the issue for now, but isn't really a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2028879/+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 2028935] Re: Merge rsyslog 8.2306.0-2
** Merge proposal linked: https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/447986 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2028935 Title: Merge rsyslog 8.2306.0-2 Status in rsyslog package in Ubuntu: New Bug description: Debian has upgraded rsyslog to 8.2306.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2028935/+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 2028935] Re: Merge rsyslog 8.2306.0-2
Merge request https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/447986 ** Changed in: rsyslog (Ubuntu) Assignee: Heinrich Schuchardt (xypron) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2028935 Title: Merge rsyslog 8.2306.0-2 Status in rsyslog package in Ubuntu: New Bug description: Debian has upgraded rsyslog to 8.2306.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2028935/+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 2025678] Re: Merge rsyslog 8.2306.0-1 from Debian unstable
Merge request https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/447986 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2025678 Title: Merge rsyslog 8.2306.0-1 from Debian unstable Status in rsyslog package in Ubuntu: Fix Released Bug description: Tracking bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2025678/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu Jammy) 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/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Fix Released Status in modemmanager source package in Jammy: Confirmed Status in ubuntu-meta source package in Jammy: Confirmed Bug description: [Impact] Cloud images should not have fwupd, modemmanager, and udisks2 installed as those are not needed and only taking up memory. [Test Case] Build cloud images with livecd-rootfs and confirm that fwupd, modemmanager, and udisks2 are not present and not running. [Regression Potential] Only thing that might happen is for any of the 3 listed packages getting removed from images where they might be used. So possibly double-checking if this will affect preinstalled server images and if they care about this or not. [Original Description] Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: modemmanager (Ubuntu Jammy) 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/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Fix Released Status in modemmanager source package in Jammy: Confirmed Status in ubuntu-meta source package in Jammy: Confirmed Bug description: [Impact] Cloud images should not have fwupd, modemmanager, and udisks2 installed as those are not needed and only taking up memory. [Test Case] Build cloud images with livecd-rootfs and confirm that fwupd, modemmanager, and udisks2 are not present and not running. [Regression Potential] Only thing that might happen is for any of the 3 listed packages getting removed from images where they might be used. So possibly double-checking if this will affect preinstalled server images and if they care about this or not. [Original Description] Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
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/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: Confirmed Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Fix Released Status in modemmanager source package in Jammy: Confirmed Status in ubuntu-meta source package in Jammy: Confirmed Bug description: [Impact] Cloud images should not have fwupd, modemmanager, and udisks2 installed as those are not needed and only taking up memory. [Test Case] Build cloud images with livecd-rootfs and confirm that fwupd, modemmanager, and udisks2 are not present and not running. [Regression Potential] Only thing that might happen is for any of the 3 listed packages getting removed from images where they might be used. So possibly double-checking if this will affect preinstalled server images and if they care about this or not. [Original Description] Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container
Package fwupd-signed is still installed, is it needed? Checked in https://cloud- images.ubuntu.com/releases/22.04/release/ubuntu-22.04-server-cloudimg- amd64.img and https://cloud-images.ubuntu.com/mantic/current/mantic- server-cloudimg-amd64.img. -- 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/1981109 Title: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container Status in fwupd package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Triaged Status in ubuntu-meta package in Ubuntu: New Status in fwupd source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: Fix Released Status in modemmanager source package in Jammy: New Status in ubuntu-meta source package in Jammy: New Bug description: [Impact] Cloud images should not have fwupd, modemmanager, and udisks2 installed as those are not needed and only taking up memory. [Test Case] Build cloud images with livecd-rootfs and confirm that fwupd, modemmanager, and udisks2 are not present and not running. [Regression Potential] Only thing that might happen is for any of the 3 listed packages getting removed from images where they might be used. So possibly double-checking if this will affect preinstalled server images and if they care about this or not. [Original Description] Looking at memory utilization in a pristine Ubuntu lxd container (top -o RES), I see that ModemManager is running, which I was surprised to see is present at all in the stock image. Tracking this I find that fwupd depends on libmm-glib0, which in turn Recommends: modemmanager. Libraries in general should not recommend daemons, so it's possible this should be fixed by libmm-glib0 dropping this Recommends. It certainly doesn't seem to be a deliberate decision by the Server Team to have modemmanager installed and running by default on all systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1981109/+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 2026599] Re: rsyslogd does not have enough permission to do its job
Hello Marco, When I boot the 22.04.2 preinstalled server rsyslog is running as syslog and not as rsyslog./ /var/log is ownded by root:syslog. What makes your rsyslog run as user rsyslog and not as user syslog? Best regards Heinrich ** Changed in: rsyslog (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2026599 Title: rsyslogd does not have enough permission to do its job Status in rsyslog package in Ubuntu: Incomplete Bug description: I have installed a new ubuntu 22.04 server. After installing ufw and a mailer daemon and activate them. Rsyslog starts complaining about permission denied error in the following files: /var/log/ufw.log /var/log/mail.err /var/log/mail.log and the following lines appear in journalctl. Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' resumed (module 'builtin:omfile') [v8.2112.0 try https://www.rsyslog.com/e/2359 ] Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 ] Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' resumed (module 'builtin:omfile') [v8.2112.0 try https://www.rsyslog.com/e/2359 ] Jul 07 17:01:01 x rsyslogd[4622]: action 'action-6-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2112.0 try https://www.rsyslog.com/e/2007 ] Creating the files manually and adding the group rsyslog:rsyslog solves the logs. Expected behaviour: rsyslog has the adequate configuration to create the files in /var/log and update them. What happened instead: the log files have to be created manually, or maybe, the default config of rsyslog modified. Or the permission of the /var/log folder have to be modified. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: rsyslog 8.2112.0-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jul 7 17:07:50 2023 InstallationDate: Installed on 2023-07-07 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230217.1) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2026599/+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 2028881] Re: apport FTBFS
The new pylint complaints are false positives and I reported them upstream: https://github.com/pylint-dev/pylint/issues/8895 ** Bug watch added: github.com/pylint-dev/pylint/issues #8895 https://github.com/pylint-dev/pylint/issues/8895 -- 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/2028881 Title: apport FTBFS Status in apport package in Ubuntu: Triaged Bug description: Rebuilding apport in mantic today FTBFS because of a pylint complaint. We discussed this in #ubuntu-devel today. I don't think that failing the build on a lint failure is appropriate in distribution packaging in a production build since otherwise the build regresses for no good reason. Linting should be done during development but not enabled in production archive builds. This can be fixed by dropping the lint tests from override_dh_auto_test in debian/rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2028881/+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 2028935] [NEW] Merge rsyslog 8.2306.0-2
Public bug reported: Debian has upgraded rsyslog to 8.2306.0-2. ** Affects: rsyslog (Ubuntu) Importance: Undecided Assignee: Heinrich Schuchardt (xypron) Status: New ** Changed in: rsyslog (Ubuntu) Assignee: (unassigned) => Heinrich Schuchardt (xypron) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/2028935 Title: Merge rsyslog 8.2306.0-2 Status in rsyslog package in Ubuntu: New Bug description: Debian has upgraded rsyslog to 8.2306.0-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2028935/+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 2028881] Re: apport FTBFS
Proposed solution: Add --errors-only mode to run-linters to only run pylint in --errors-only mode and mypy: https://github.com/canonical/apport/pull/215 Those two can find relevant errors. The linters like black will be skipped. -- 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/2028881 Title: apport FTBFS Status in apport package in Ubuntu: Triaged Bug description: Rebuilding apport in mantic today FTBFS because of a pylint complaint. We discussed this in #ubuntu-devel today. I don't think that failing the build on a lint failure is appropriate in distribution packaging in a production build since otherwise the build regresses for no good reason. Linting should be done during development but not enabled in production archive builds. This can be fixed by dropping the lint tests from override_dh_auto_test in debian/rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2028881/+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 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
Hello Heinrich, or anyone else affected, Accepted ubuntu-meta into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-meta/1.481.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Jammy: Fix Committed Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The GNOME desktop might fail. [ Other Info ] This change was previously made in time for the Ubuntu 22.10 release. See https://launchpad.net/bugs/1989733 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 2028774] Re: ssh fails to load opensc-pkcs11.so
Upstream says the change is intentional, so I am closing this bug. Thanks! ** Changed in: openssh (Ubuntu) Status: Confirmed => Won't Fix -- 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/2028774 Title: ssh fails to load opensc-pkcs11.so Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Won't Fix Bug description: I have PKCS11Provider opensc-pkcs11.so in my ~/.ssh/config After the last update of openssh-client I now get: $ strace -o slogin.log slogin host lib_contains_symbol: open opensc-pkcs11.so: No such file or directory provider opensc-pkcs11.so is not a PKCS11 library (uwe@host) Password for uwe@host: $ grep -i pkcs11 slogin.log read(3, "PKCS11Provider opensc-pkcs11.so\n"..., 4096) = 1603 openat(AT_FDCWD, "opensc-pkcs11.so", O_RDONLY) = -1 ENOENT (No such file or directory) write(2, "provider opensc-pkcs11.so is not"..., 51) = 51 $ dpkg-query --listfiles opensc-pkcs11 | grep opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/onepin-opensc-pkcs11.so /usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh-client 1:8.9p1-3ubuntu0.3 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 26 15:46:30 2023 InstallationDate: Installed on 2022-08-25 (334 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: ssh-askpass 1:1.2.4.1-13 libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.9p1 Ubuntu-3ubuntu0.3, OpenSSL 3.0.2 15 Mar 2022 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/2028774/+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 2028769] Re: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy
This has been uploaded to the Jammy unapproved queue where it will need to be manually accepted by a member of the SRU team before it will be available as a proposed update. I believe this upload will also need assistance from the Ubuntu Archive team since it adds a NEW binary package (exists on other architectures but new for riscv64) ** Changed in: ubuntu-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Heinrich Schuchardt (xypron) ** Changed in: ubuntu-meta (Ubuntu) Status: In Progress => Fix Released ** Also affects: ubuntu-meta (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu Jammy) Assignee: (unassigned) => Heinrich Schuchardt (xypron) ** Changed in: ubuntu-meta (Ubuntu Jammy) Status: New => In Progress ** Description changed: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. - * The Gnome desktop might fail. + * The GNOME desktop might fail. [ Other Info ] - - n/a + + This change was previously made in time for the Ubuntu 22.10 release. + See https://launchpad.net/bugs/1989733 for more details. -- 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/2028769 Title: [SRU] missing riscv64 packages ubuntu-desktop, ubuntu-desktop-minimal in Jammy Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Jammy: In Progress Bug description: [ Impact ] Without packages ubuntu-desktop, ubuntu-desktop-minimal it is unnecessarily difficult to setup the Ubuntu desktop on systems like the SiFive HiFive Unmatched. All dependent packages are available. We just need to add the riscv64 architecture in debian/control. [ Test Plan ] Reproducing the issue: * Check that the packages ubuntu-desktop, ubuntu-desktop-minimal are not available for riscv64 in the archive. Testing: * Install Ubuntu Jammy using the live installer on the SiFive HiFive Unmatched board. * Install package ubuntu-desktop-minimal. * Install package ubuntu-desktop. * Reboot * Login * Check that you have a function desktop by opening a preinstalled application. [ Where problems could occur ] * The packages might not be installable due to missing dependencies. * The GNOME desktop might fail. [ Other Info ] This change was previously made in time for the Ubuntu 22.10 release. See https://launchpad.net/bugs/1989733 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2028769/+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 2028879] Re: Lack of default dpkg diverts causes autopkgtest failure
The integration test should be skipped in case there is no diversion: https://github.com/canonical/apport/pull/214 For Ubuntu, we should pull in something with diversion to have this test do something useful. ** Also affects: apport Importance: Undecided Status: New ** Changed in: apport Milestone: None => 2.28.0 ** Changed in: apport Status: New => Triaged ** Changed in: apport Importance: Undecided => High ** Changed in: apport Status: Triaged => In Progress ** Summary changed: - Lack of default dpkg diverts causes autopkgtest failure + Lack of default dpkg diverts causes test_get_file_package_diversion to fail -- 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/2028879 Title: Lack of default dpkg diverts causes test_get_file_package_diversion to fail Status in Apport: In Progress Status in apport package in Ubuntu: Triaged Bug description: tests/integration/test_packaging_apt_dpkg.py::test_get_file_package_diversion fails if it doesn't detect any dpkg diversions. Apparently something (possibly dash?) stopped diverting something, so now there are no diversions in the autopkgtest environment and therefore this test fails. One option is to add something that does divert something, eg. vim, to the test dependencies. This fixes the issue for now, but isn't really a permanent solution. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2028879/+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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'
the new upload was for bug 2027636, setting tags back to verified here -- 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/2027575 Title: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory' Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: Fix Committed Status in initramfs-tools source package in Lunar: Fix Committed Bug description: [Impact] In debian/tests/run-image we instantiate an image with 512Mb of ram, but recent jammy/lunar 6.2 kernels need more than that. Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz 'net' test fails with a kernel panic due to out-of-memory. It also relies on an existing and working cloud image. If the cloud image is not available, the test will silently succeed. [Fix] The net autopkgtest was ported to the common test framework in initramfs-tools 0.142ubuntu3. This makes the test more robust by relying on the minimum needed for the integration test. [Test Plan] Check that the autopkgtest succeed or test it manually: 1. Download a lunar image: $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar 2. Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image instantiated by 'run-image'. The testcase should complete successfully without the kernel panic. $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img [Where problems could occur] The usage of a larger image for the tests could fail if the the test system is low on ram size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2027575] Please test proposed package
Hello Roxana, or anyone else affected, Accepted initramfs-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.140ubuntu13.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-needed verification-needed-jammy verification-needed-lunar ** Tags added: verification-done verification-done-jammy verification-done-lunar -- 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/2027575 Title: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory' Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: Fix Committed Status in initramfs-tools source package in Lunar: Fix Committed Bug description: [Impact] In debian/tests/run-image we instantiate an image with 512Mb of ram, but recent jammy/lunar 6.2 kernels need more than that. Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz 'net' test fails with a kernel panic due to out-of-memory. It also relies on an existing and working cloud image. If the cloud image is not available, the test will silently succeed. [Fix] The net autopkgtest was ported to the common test framework in initramfs-tools 0.142ubuntu3. This makes the test more robust by relying on the minimum needed for the integration test. [Test Plan] Check that the autopkgtest succeed or test it manually: 1. Download a lunar image: $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar 2. Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image instantiated by 'run-image'. The testcase should complete successfully without the kernel panic. $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img [Where problems could occur] The usage of a larger image for the tests could fail if the the test system is low on ram size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'
Hello Roxana, or anyone else affected, Accepted initramfs-tools into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.142ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-lunar ** Tags added: verification-needed verification-needed-lunar ** Tags removed: verification-done-jammy ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2027575 Title: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory' Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Jammy: Fix Committed Status in initramfs-tools source package in Lunar: Fix Committed Bug description: [Impact] In debian/tests/run-image we instantiate an image with 512Mb of ram, but recent jammy/lunar 6.2 kernels need more than that. Example of a test failure: https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz 'net' test fails with a kernel panic due to out-of-memory. It also relies on an existing and working cloud image. If the cloud image is not available, the test will silently succeed. [Fix] The net autopkgtest was ported to the common test framework in initramfs-tools 0.142ubuntu3. This makes the test more robust by relying on the minimum needed for the integration test. [Test Plan] Check that the autopkgtest succeed or test it manually: 1. Download a lunar image: $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar 2. Run autotestpkg tests from initramfs-tools package. The "net" test is the one that depends on the image instantiated by 'run-image'. The testcase should complete successfully without the kernel panic. $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img [Where problems could occur] The usage of a larger image for the tests could fail if the the test system is low on ram size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2027636] Please test proposed package
Hello Loïc, or anyone else affected, Accepted initramfs-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.140ubuntu13.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2027636 Title: [SRU] ucsi drivers missing in initramfs Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Jammy: Fix Committed Status in initramfs-tools source package in Lunar: Fix Committed Bug description: [Impact] Some systems rely on a USB type-C UCSI connection; without the corresponding driver in the initramfs, USB storage might not be accessible. This is notably affecting NVIDIA Tegra systems such as Jetson AGX or the IGX and prevents completing USB boot for installation purposes. The initramfs-tools package has a list of relevant USB drivers to include for the default MODULES=most configuration, but didn't list the recently introduced ucsi one. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the ucsi driver. On jammy system, you can verify the current initrd doesn't contain typec_ucsi.ko by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up typec_ucsi.ko: $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew by 93403B from 122298948B to 122392351B, so by less than 0.08%. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 2027636] Please test proposed package
Hello Loïc, or anyone else affected, Accepted initramfs-tools into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.142ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2027636 Title: [SRU] ucsi drivers missing in initramfs Status in initramfs-tools package in Ubuntu: Fix Committed Status in initramfs-tools source package in Jammy: Fix Committed Status in initramfs-tools source package in Lunar: Fix Committed Bug description: [Impact] Some systems rely on a USB type-C UCSI connection; without the corresponding driver in the initramfs, USB storage might not be accessible. This is notably affecting NVIDIA Tegra systems such as Jetson AGX or the IGX and prevents completing USB boot for installation purposes. The initramfs-tools package has a list of relevant USB drivers to include for the default MODULES=most configuration, but didn't list the recently introduced ucsi one. [ Test Plan ] The -generic kernel and probably all kernel flavors contain the ucsi driver. On jammy system, you can verify the current initrd doesn't contain typec_ucsi.ko by decompressing the initramfs and listing its files: $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko After installing the updated initramfs-tools package, your current initramfs should be automatically rebuilt and pick up typec_ucsi.ko: $ lsinitramfs /boot/initrd.img-5.19.0-46-generic | grep typec_ucsi.ko usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko [ Where problems could occur ] This is making the initramfs slightly bigger. In my testing, typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew by 93403B from 122298948B to 122392351B, so by less than 0.08%. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 2028832] Re: NetworkManager : sharing per ethernet needs to switch off and on
** Description changed: Hello, My Lenovo laptop is connected to the Internet trough Wifi and I need to share the Internet (tethering) trough my ethernet port (Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)) to a Rapsberry Pi 3. To achieve this, I setup the ethernet network with NetworkManager (sharing the link with IPV4 and IPV6 is desactivated). This sharing is configured to switch on automatically when NetworkManager is started. But that sharing never goes up automatically. I need to manually switch off and on the ethernet link in NetworkManager and then tethering trough ethernet works fine. There seems to be a bug in NetworkManager considering the automatic setup up of a ethernet sharing link. Can you solve that? + + PS:I made a bug report 6 month ago in r8169 modules for the same trouble + #1995147 ** Description changed: Hello, My Lenovo laptop is connected to the Internet trough Wifi and I need to share the Internet (tethering) trough my ethernet port (Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)) to a Rapsberry Pi 3. To achieve this, I setup the ethernet network with NetworkManager (sharing the link with IPV4 and IPV6 is desactivated). This sharing is configured to switch on automatically when NetworkManager is started. But that sharing never goes up automatically. I need to manually switch off and on the ethernet link in NetworkManager and then tethering trough ethernet works fine. There seems to be a bug in NetworkManager considering the automatic setup up of a ethernet sharing link. Can you solve that? - PS:I made a bug report 6 month ago in r8169 modules for the same trouble + PS:I made a bug report 6 months ago in r8169 module for the same trouble #1995147 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2028832 Title: NetworkManager : sharing per ethernet needs to switch off and on Status in network-manager package in Ubuntu: New Bug description: Hello, My Lenovo laptop is connected to the Internet trough Wifi and I need to share the Internet (tethering) trough my ethernet port (Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)) to a Rapsberry Pi 3. To achieve this, I setup the ethernet network with NetworkManager (sharing the link with IPV4 and IPV6 is desactivated). This sharing is configured to switch on automatically when NetworkManager is started. But that sharing never goes up automatically. I need to manually switch off and on the ethernet link in NetworkManager and then tethering trough ethernet works fine. There seems to be a bug in NetworkManager considering the automatic setup up of a ethernet sharing link. Can you solve that? PS:I made a bug report 6 months ago in r8169 module for the same trouble #1995147 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2028832/+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
