[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Tags added: bionic sts -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1972939] Re: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes
On Fri, Aug 05, 2022 at 00:35:32 -, Don wrote: > It appears the issue is resolved in libssl3 3.0.4-1ubuntu1 from kinetic > (in addition to enabling the legacy providers) Thanks for that hint. Can you provide any additional details on your Tinc environment and what exactly allowed the connection to start working? For example, did you previously attempt to connect a Tinc node running Kinentic to a Xenial node and have it fail, but then see it start working once you upgraded libssl3 to the 3.0.4-1ubuntu1 release? Nathan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1972939 Title: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes Status in Release Notes for Ubuntu: New Status in openssl package in Ubuntu: New Status in tinc package in Ubuntu: New Bug description: The tinc included in Jammy (1.0.36-2build1 linked with libssl3) cannot connect to tinc nodes running e.g. tinc from Xenial (1.0.26-1). (Tinc from Impish, which is also v1.0.36-2 but is linked to libssl1.1, can connect to these nodes without problems.) The symptom is a log message (on the system running Jammy) during the metadata channel negotiation (with debug level set to 5): Error during initialisation of cipher from tinc_xenial [...] error:0308010C:digital envelope routines::unsupported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1972939/+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 1987523] Re: Pulsaudio crashes once BT microphone is connected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1987523 Title: Pulsaudio crashes once BT microphone is connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I connect my BT headset with microphone and change profile to HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports: Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX (AVRCP) as /devices/virtual/input/input37 Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80% Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data descriptor : 0x1 terminating Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of process 50808 owned by '1000' RT at priority 5. Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes of 1 users. Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: [51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at ../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). Aborting. Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash report... Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie Aug 24 13:44:24 p14s systemd[1]: Started crash report submission. Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: /var/lock/whoopsie/lock Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully. Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk I've identified the upstream fix for this: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e I've built packages with the fix and can confirm that it does solve the problem. Packages are available at: https://launchpad.net/~ivoks/+archive/ubuntu/pulse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1987523/+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 1980123] Re: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- 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/1980123 Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 Status in openssh package in Ubuntu: Expired Bug description: "System Problem Detected" ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.2p1-4ubuntu0.5 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 AptOrdering: curl:amd64: Install libcurl4:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 28 06:18:40 2022 ErrorMessage: installed openssh-server package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-07-08 (354 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: openssh Title: package openssh-server 1:8.2p1-4ubuntu0.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1980123/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
manually scaling node pool/reboot nodes solves this issue. -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988010] Re: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI
Cool, thanks Josh -- 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/1988010 Title: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI Status in systemd package in Ubuntu: New Bug description: Hi there! I'm running ubuntu 22.04.1 LTS installed via the ISO image ubuntu-22.04.1-desktop-amd64.iso. This issue affects both the Live CD and installed operating system. I have configured my modem's DHCP server to push my adguard home DNS server (cloud-hosted) as the DNS for the network. I have an access point that is setup to do the same. With the Live CD and installed operating system, there is a local DNS server installed that runs on 127.0.0.1:53. Somehow this bypasses the DNS servers I've configured for the network and suddenly websites that have been blocked for being malicious or harmful are now accessible. There is no option in the installer or GUI to disable this. Changing the network DNS settings via the GUI of either the live cd or installation do not change the behavior and do not result in the specified DNS server(s) being used. The 127.0.0.1:53 server still overrides anything set in the GUI. The only way I have found to override this behavior is to edit /etc/systemd/resolved.conf: 1) uncomment DNSStubListener=yes 2) change yes to no 3) save file 4) run the following commands in terminal: sudo systemctl daemon-reload sudo systemctl restart systemd-networkd sudo systemctl restart systemd-resolved After doing so, the DNS servers that have been provided by DHCP are properly used. This is considered a security vulnerability due to there being no way for a normal user to change this setting without editing system configuration files and no warning given to the user that the settings they are applying in the GUI have not been applied due to this default configuration. This is considered a hack if this is the intentional configuration as it overrides network configuration options set by the DHCP server. I've resolved it for myself for now by making a custom iso image that removes this configuration by default and instead installs the /etc/systemd/resolved.conf file attached to this bug report. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.4 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 21:18:35 2022 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 2022.08.28 LTS "Custom Jammy Jellyfish" (20220828) MachineType: Micro-Star International Co., Ltd. GS75 Stealth 9SG ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2019 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17G1IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-17G1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17G1IMS.10C:bd03/26/2019:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGS75Stealth9SG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17G1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17G1.1: dmi.product.family: GS dmi.product.name: GS75 Stealth 9SG dmi.product.sku: 17G1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. mtime.conffile..etc.systemd.resolved.conf: 2022-08-28T19:29:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988010/+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 1988010] Re: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI
Hi Seth, I am using the GUI built into the desktop - the one in the top right where I can turn bluetooth on/off and change wifi networks. Toggling the DNS Server section from automatic to off did not result in the DNS server entered being used. Additionally using nslookup didn't result in a response until a request was made by a web browser. https://gyazo.com/1e33fa49040bf14afbbd99252dc37993 https://gyazo.com/75d3cdd0e4412166e807375f784fc305 https://gyazo.com/7617efb2e8d7f89dc0c2f3ceec6c3109 Thanks, Josh -- 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/1988010 Title: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI Status in systemd package in Ubuntu: New Bug description: Hi there! I'm running ubuntu 22.04.1 LTS installed via the ISO image ubuntu-22.04.1-desktop-amd64.iso. This issue affects both the Live CD and installed operating system. I have configured my modem's DHCP server to push my adguard home DNS server (cloud-hosted) as the DNS for the network. I have an access point that is setup to do the same. With the Live CD and installed operating system, there is a local DNS server installed that runs on 127.0.0.1:53. Somehow this bypasses the DNS servers I've configured for the network and suddenly websites that have been blocked for being malicious or harmful are now accessible. There is no option in the installer or GUI to disable this. Changing the network DNS settings via the GUI of either the live cd or installation do not change the behavior and do not result in the specified DNS server(s) being used. The 127.0.0.1:53 server still overrides anything set in the GUI. The only way I have found to override this behavior is to edit /etc/systemd/resolved.conf: 1) uncomment DNSStubListener=yes 2) change yes to no 3) save file 4) run the following commands in terminal: sudo systemctl daemon-reload sudo systemctl restart systemd-networkd sudo systemctl restart systemd-resolved After doing so, the DNS servers that have been provided by DHCP are properly used. This is considered a security vulnerability due to there being no way for a normal user to change this setting without editing system configuration files and no warning given to the user that the settings they are applying in the GUI have not been applied due to this default configuration. This is considered a hack if this is the intentional configuration as it overrides network configuration options set by the DHCP server. I've resolved it for myself for now by making a custom iso image that removes this configuration by default and instead installs the /etc/systemd/resolved.conf file attached to this bug report. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.4 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 21:18:35 2022 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 2022.08.28 LTS "Custom Jammy Jellyfish" (20220828) MachineType: Micro-Star International Co., Ltd. GS75 Stealth 9SG ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2019 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17G1IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-17G1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17G1IMS.10C:bd03/26/2019:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGS75Stealth9SG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17G1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17G1.1: dmi.product.family: GS dmi.product.name: GS75 Stealth 9SG dmi.product.sku: 17G1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. mtime.conffile..etc.systemd.resolved.conf: 2022-08-28T19:29:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1965439] Re: [SRU] kdesu fails to authenticate with sudo from Jammy
Hello Erich, or anyone else affected, Accepted kdesu into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kdesu/5.92.0-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: kdesu (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 sudo in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: [SRU] kdesu fails to authenticate with sudo from Jammy Status in kdesu package in Ubuntu: Fix Released Status in kubuntu-settings package in Ubuntu: Fix Released Status in sudo package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in kdesu source package in Jammy: Fix Committed Status in kubuntu-settings source package in Jammy: In Progress Status in sudo source package in Jammy: Won't Fix Status in ubuntustudio-default-settings source package in Jammy: In Progress Status in kdesu source package in Kinetic: Fix Released Status in kubuntu-settings source package in Kinetic: Fix Released Status in sudo source package in Kinetic: Won't Fix Status in ubuntustudio-default-settings source package in Kinetic: Fix Released Status in kdesu package in Debian: Fix Released Bug description: kdesu fails to authenticate with sudo from Jammy. See upstream bug: KDE bug: https://bugs.kde.org/show_bug.cgi?id=452532 Examples: Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. On entering the correct password authentication is refused, stating that possibly an incorrect password has been entered. It appears that kdesu fails to cope with the sudo config change in this commit: https://salsa.debian.org/sudo- team/sudo/-/commit/59db341d46aa4c26b54c1270e69f2562e7f3d751 kdesu was fixed in Debian with: https://tracker.debian.org/news/1330116/accepted-kdesu-5940-2-source- into-unstable/ and fixed in kinetic with: https://launchpad.net/ubuntu/+source/kdesu/5.94.0-0ubuntu2 The issue can be worked around by adding /etc/sudoers.d/kdesu-sudoers with the contents Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty [Impact] * Users are unable to authenticate to and launch applications via kdesu. * This should be backported to restore functionality that users expect. [Test Plan] * Launch Kubuntu driver manager from system setting, launching ksystemlog from the main menu, or trying to run krusader root mode option via its 'Tools > Start Krusader Root Mode' menu entry. Assuming that the current user is a member of the sudo group. * Confirm that the application authentcate and launch as successfully as in previous releases. [Where problems could occur] * While this update only returns sudo to its default behaviour (used in previous releases and virtually all other distributions) for kdesu, care should be taken to test some other applications that seek root permissions to confirm that no unexpected consequences occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Critical -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988010] Re: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI
Hello Josh, which GUI are you using to change dns or dhcp settings? Thanks ** Information type changed from Private Security to Public Security -- 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/1988010 Title: systemd ignoring DHCP DNS servers and DNS servers set in Network Manager GUI Status in systemd package in Ubuntu: New Bug description: Hi there! I'm running ubuntu 22.04.1 LTS installed via the ISO image ubuntu-22.04.1-desktop-amd64.iso. This issue affects both the Live CD and installed operating system. I have configured my modem's DHCP server to push my adguard home DNS server (cloud-hosted) as the DNS for the network. I have an access point that is setup to do the same. With the Live CD and installed operating system, there is a local DNS server installed that runs on 127.0.0.1:53. Somehow this bypasses the DNS servers I've configured for the network and suddenly websites that have been blocked for being malicious or harmful are now accessible. There is no option in the installer or GUI to disable this. Changing the network DNS settings via the GUI of either the live cd or installation do not change the behavior and do not result in the specified DNS server(s) being used. The 127.0.0.1:53 server still overrides anything set in the GUI. The only way I have found to override this behavior is to edit /etc/systemd/resolved.conf: 1) uncomment DNSStubListener=yes 2) change yes to no 3) save file 4) run the following commands in terminal: sudo systemctl daemon-reload sudo systemctl restart systemd-networkd sudo systemctl restart systemd-resolved After doing so, the DNS servers that have been provided by DHCP are properly used. This is considered a security vulnerability due to there being no way for a normal user to change this setting without editing system configuration files and no warning given to the user that the settings they are applying in the GUI have not been applied due to this default configuration. This is considered a hack if this is the intentional configuration as it overrides network configuration options set by the DHCP server. I've resolved it for myself for now by making a custom iso image that removes this configuration by default and instead installs the /etc/systemd/resolved.conf file attached to this bug report. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.4 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 21:18:35 2022 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu 22.04.1 2022.08.28 LTS "Custom Jammy Jellyfish" (20220828) MachineType: Micro-Star International Co., Ltd. GS75 Stealth 9SG ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2019 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17G1IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-17G1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17G1IMS.10C:bd03/26/2019:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnGS75Stealth9SG:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17G1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17G1.1: dmi.product.family: GS dmi.product.name: GS75 Stealth 9SG dmi.product.sku: 17G1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. mtime.conffile..etc.systemd.resolved.conf: 2022-08-28T19:29:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988010/+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 1988143] Update Released
The verification of the Stable Release Update for linux-restricted- modules-hwe-5.15 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1988143 Title: 20.04.5 (20220829.1 build) has kernel 5.13 packages Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Invalid Bug description: [Impact] * Linux-restricted-modules for the 390 drivers were disabled temporarily back in January, however they were not re-enabled when support for the new kernel was added. * Including the 390 release in the ISO causes the 5.13 packages to be pulled in. [Test Plan] * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver can be installed with its linux-restricted-modules. [Where problems could occur] * The addition of modules for an already existing driver series would not cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 [Other Info] * Other kernel releases support the 390 series. _ Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+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 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages
This bug was fixed in the package linux-restricted-modules-hwe-5.15 - 5.15.0-46.49~20.04.1+1 --- linux-restricted-modules-hwe-5.15 (5.15.0-46.49~20.04.1+1) focal; urgency=medium * Miscellaneous Ubuntu changes (LP: #1988143) - [packaging] revert drop nvidia 390 -- Alberto Milone Tue, 30 Aug 2022 11:40:45 + ** Changed in: linux-restricted-modules-hwe-5.15 (Ubuntu) Status: New => 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/1988143 Title: 20.04.5 (20220829.1 build) has kernel 5.13 packages Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Invalid Bug description: [Impact] * Linux-restricted-modules for the 390 drivers were disabled temporarily back in January, however they were not re-enabled when support for the new kernel was added. * Including the 390 release in the ISO causes the 5.13 packages to be pulled in. [Test Plan] * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver can be installed with its linux-restricted-modules. [Where problems could occur] * The addition of modules for an already existing driver series would not cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 [Other Info] * Other kernel releases support the 390 series. _ Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
You can find here some simple Python script to run a command to the VMSS instances for all subscriptions [or filtered ones]: https://github.com/foreachtoil/execute-command-on-all-vmss I still lack threading, so this might take a little bit. -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988230] [NEW] glib 2.73 breaks modemmanager
Public bug reported: I'm filing this bug in case we want to fix it before letting glib 2.73 in to kinetic. ** Affects: glib Importance: Unknown Status: Unknown ** Affects: glib2.0 (Ubuntu) Importance: High Status: Triaged ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: Triaged ** Affects: glib2.0 (Debian) Importance: Unknown Status: Unknown ** Tags: block-proposed kinetic ** Bug watch added: Debian Bug tracker #1017794 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794 ** Also affects: glib2.0 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017794 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2729 https://gitlab.gnome.org/GNOME/glib/-/issues/2729 ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/-/issues/2729 Importance: Unknown Status: Unknown ** Also affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Changed in: modemmanager (Ubuntu) Status: New => Triaged -- 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/1988230 Title: glib 2.73 breaks modemmanager Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Triaged Status in modemmanager package in Ubuntu: Triaged Status in glib2.0 package in Debian: Unknown Bug description: I'm filing this bug in case we want to fix it before letting glib 2.73 in to kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1988230/+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 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
The fix for kinetic is included in 251.4-1ubuntu1, and the patch is staged in git for the next jammy SRU. ** Changed in: systemd (Ubuntu Kinetic) Status: In Progress => Fix Released ** Changed in: systemd (Ubuntu Jammy) Status: New => Fix Committed -- 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/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] Some NFS setups that have worked on previous versions of Ubuntu are now broken. Specifically, when creating a bind mount, systemd will fail if the directory already exists on NFS. [Test Plan] This test plan requires an NFS server to be in place. The exact setup is not important, but for the purposes of this test plan we will assume the server exports /data, which contains a directory called home. * Make sure nfs-common is installed: $ apt install nfs-common -y * Check the NFS server exports using showmount: $ showmount -e $NFS_SERVER_IP Export list for $NFS_SERVER_IP: /data * * Add the appropriate entries to /etc/fstab. In this example, we will make /home2 a bind mount to /data/home: # /etc/fstab $NFS_SERVER_IP:/data /data nfs defaults,nfsvers=3 0 0 /data/home /home2 none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 * Check systemctl status home2.mount. On an affected system, we should see a permission denied error: $ systemctl status home2.mount x home2.mount - /home2 Loaded: loaded (/etc/fstab; generated) Active: failed (Result: resources) Where: /home2 What: /data/home Docs: man:fstab(5) man:systemd-fstab-generator(8) systemd[1]: home2.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home2.mount: Failed to run 'mount' task: Permission denied systemd[1]: home2.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home2. * On a patched system, we expect /home2 to be mounted successfully. [Where problems could occur] The patch makes it so that systemd will not fail bind mounts immediately if creating the directory fails. Thus, any regressions would be seen during bind mounts with systemd. N.B. that this patch restores previous behavior in systemd. [Original Description] I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu
[Touch-packages] [Bug 1969375] Re: systemd-cryptenroll does not support TPM2 devices
This was covered in the 251.2-2ubuntu1 release in kinetic, but the changelog did not reference the bug number to indicate this. ** Changed in: systemd (Ubuntu Kinetic) Status: In Progress => Fix Released -- 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/1969375 Title: systemd-cryptenroll does not support TPM2 devices Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Released Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] * TPM2/FIDO cannot be used to unlock luks encrpyted block devices * due to missing build-time support in systemd * Error message: "TPM2 not supported on this build." [Test Plan] # 1: check no new binary deps have been introduced to the systemd package, other than "libssl3", which is already installed by default. # Compare to this version of systemd 249.11-0ubuntu3.1: $ apt-cache depends systemd systemd PreDepends: libblkid1 PreDepends: libc6 PreDepends: libcap2 PreDepends: libgcrypt20 PreDepends: liblz4-1 PreDepends: liblzma5 PreDepends: libselinux1 PreDepends: libzstd1 Depends: libacl1 Depends: libapparmor1 Depends: libaudit1 Depends: libcrypt1 Depends: libcryptsetup12 Depends: libgnutls30 Depends: libgpg-error0 Depends: libip4tc2 Depends: libkmod2 Depends: liblz4-1 Depends: libmount1 Depends: libpam0g Depends: libseccomp2 Depends: libsystemd0 Depends: util-linux Depends: mount Depends: adduser Conflicts: Conflicts: Conflicts: Breaks: resolvconf Breaks: udev |Recommends: dbus Recommends: dbus-broker dbus Recommends: networkd-dispatcher |Recommends: systemd-timesyncd Recommends: chrony ntp ntpsec openntpd systemd-timesyncd Suggests: systemd-container Suggests: policykit-1 # 2: check that systemd-cryptenroll doesn't have any undefined symbols that prevent it from running: $ systemd-cryptenroll --help # this should not crash systemd-cryptenroll [OPTIONS...] BLOCK-DEVICE Enroll a security token or authentication credential to a LUKS volume. -h --helpShow this help --version Show package version --passwordEnroll a user-supplied password --recovery-keyEnroll a recovery key --pkcs11-token-uri=URI Specify PKCS#11 security token URI --fido2-device=PATH Enroll a FIDO2-HMAC security token --fido2-with-client-pin=BOOL Whether to require entering a PIN to unlock the volume --fido2-with-user-presence=BOOL Whether to require user presence to unlock the volume --fido2-with-user-verification=BOOL Whether to require user verification to unlock the volume --tpm2-device=PATH Enroll a TPM2 device --tpm2-pcrs=PCR1+PCR2+PCR3+… Specify TPM2 PCRs to seal against --wipe-slot=SLOT1,SLOT2,… Wipe specified slots See the systemd-cryptenroll(1) man page for details. # initial setup $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img - $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img Please enter passphrase for disk volume: s0s3cur3 Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. $ sudo mkfs.ext4 /dev/mapper/volume $ sudo mount /dev/mapper/volume /mnt $ sudo touch /mnt/TPM_TEST $ ls -la /mnt drwxr-xr-x 3 root root 4096 Jun 7 15:06 . drwxr-xr-x 20 root root 4096 Apr 20 11:45 .. drwx-- 2 root root 16384 Jun 7 15:06 lost+found -rw-r--r-- 1 root root 0 Jun 7 15:06 TPM_TEST $ sudo umount /dev/mapper/volume $ sudo cryptsetup luksClose volume $ ls -la /mnt # empty # 3: check non-TPM use cases (--password & --recovery-key) of systemd-cryptenroll have not regressed. # enroll additional password $ systemd-cryptenroll --password encrypted.img Please enter current passphrase for disk /home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cur3 Please enter new passphrase for disk /home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cr3t Please enter new passphrase for disk /home/lukas/canonical/systemd-dbg/encrypted.img (repeat): s0s3cr3t New password enrolled as key slot 1. $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img Please enter passphrase for disk volume: s0s3cr3t Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img. $ sudo cryptsetup luksClose volume $ systemd-cryptenroll --wipe-slot=1 encrypted.img Wiped slot
[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
this worked for us: https://github.com/joaguas/aksdnsfallback#if-the- above-method-fails-because-dhclient-might-stall-another-alternative-is- to-configure-resolved-to-use-a-fallback-dns-server-which-we-can- hardcode-in-its-configuration -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1987642] Re: Chile is delaying the DST by one week for 2022
This bug was fixed in the package tzdata - 2022c-1ubuntu1 --- tzdata (2022c-1ubuntu1) kinetic; urgency=medium * Merge with Debian unstable (LP: #1987642). Remaining changes: - Ship ICU timezone data files which are utilized by php and update them to 2022b as 2022c isn't available tzdata (2022c-1) unstable; urgency=medium * New upstream version, no changes to the timezones. tzdata (2022b-1) unstable; urgency=medium [ Aurelien Jarno ] * New upstream version: - Chile's 2022 DST start is delayed from September 4 to September 11. - Iran plans to stop observing DST permanently, after it falls back on 2022-09-21. * debian/tzdata.config: convert Europe/Kiev into Europe/Kyiv. * debian/tzdata.templates, debian/po/*: update templates and translation following the above change. * Bump Standards-Version to 4.6.1 (no changes). tzdata (2022a-1) unstable; urgency=high [ Aurelien Jarno ] * New upstream version: - Palestine will spring forward on 2022-03-27, not -03-26. * Set urgency to high as the Palestine DST change is in 4 days. * debian/tzdata.config: do not try to get a value from debconf if it hasn't been seen yet. Closes: #999465. * Update English debconf translation. [ Johannes Schauer Marin Rodrigues ] * Add support for support DPKG_ROOT. Closes: #1007756. -- Simon Chopin Mon, 29 Aug 2022 10:14:49 +0200 ** Changed in: tzdata (Ubuntu Kinetic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1987642 Title: Chile is delaying the DST by one week for 2022 Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Xenial: Confirmed Status in tzdata source package in Bionic: Confirmed Status in tzdata source package in Focal: Confirmed Status in tzdata source package in Jammy: Confirmed Status in tzdata source package in Kinetic: Fix Released Bug description: Chile is delaying the start of Daylight Saving Time (DST) by one week this year [1],[2]. DST timezone in Chile will start on midnight of September 11th; and will end on April 1st, 2023. Debian's 2022c-1 and 2022b-1 versions of tzdata contain the fix for this. Upstream commit : https://github.com/eggert/tz/commit/711b46f8fc4e8a3d5caf7d4820562d6cdfe9d769 We need to fix this in all or releases back to Xenial. [1] https://www.interior.gob.cl/noticias/2022/08/09/comunicado-el-proximo-sabado-10-de-septiembre-los-relojes-se-deben-adelantar-una-hora/ [2] https://www.timeanddate.com/news/time/chile-dst-delay-2022.html#:~:text=Chile%20is%20delaying%20the%20start,financial%20district%20in%20Chile%27s%20capital. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1987642/+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 1971932] Re: error in rsync protocol data stream
Since there is known workaround for this I am setting the Importance to Low. ** Changed in: rsync (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1971932 Title: error in rsync protocol data stream Status in rsync package in Ubuntu: Confirmed Bug description: When synchronizing to other systems, rsync exits with "error in rsync protocol data stream (code 12)". The problem occurs since ubuntu 22.04 LTS with two different destination systems not running ubuntu but plain debian. The error did not occur under 20.04 LTS. Synchronisation runs fine for most other files, but always stops at the same (relative large) file. The file itself has also been changed on a test basis to make sure the file is not the problem itself. Log snippet: ... chunk[46131] len=46120 offset=2127561720 sum1=2f48caf4 chunk[46132] len=46120 offset=2127607840 sum1=5dfcb4ee chunk[46133] len=46120 offset=2127653960 sum1=d1037d81 chunk[46134] len=8870 offset=2127700080 sum1=6deedc97 send_files mapped /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX of size 2135722584 calling match_sums /path/backup/subdir/.thunderbird/profile/ImapMail/imap.domain.com/INBOX built hash table hash search b=46120 len=2135722584 sum=1e1722dc k=46120 hash search s->blength=46120 len=2135722584 count=46135 potential match at 0 i=0 sum=1e1722dc match at 0 last_match=0 j=0 len=46120 n=0 potential match at 46120 i=1 sum=c482d6b6 match at 46120 last_match=46120 j=1 len=46120 n=0 potential match at 92240 i=2 sum=b21c7e11 match at 92240 last_match=92240 j=2 len=46120 n=0 potential match at 138360 i=3 sum=d066473a match at 138360 last_match=138360 j=3 len=46120 n=0 potential match at 184480 i=4 sum=a32a2984 match at 184480 last_match=184480 j=4 len=46120 n=0 potential match at 230600 i=5 sum=39cc049f match at 230600 last_match=230600 j=5 len=46120 n=0 potential match at 276720 i=6 sum=ad3de98a match at 276720 last_match=276720 j=6 len=46120 n=0 potential match at 322840 i=7 sum=83e16fa9 match at 322840 last_match=322840 j=7 len=46120 n=0 deflate on token returned 0 (8512 bytes left) rsync error: error in rsync protocol data stream (code 12) at token.c(476) [sender=3.2.3] [sender] _exit_cleanup(code=12, file=token.c, line=476): entered [sender] _exit_cleanup(code=12, file=token.c, line=476): about to call exit(12) Sender system: (rsync 3.2.3-8ubuntu3) - rsync version 3.2.3 protocol version 31 Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others. Web site: https://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, hardlink-specials, symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs, xattrs, optional protect-args, iconv, symtimes, prealloc, stop-at, no crtimes Optimizations: SIMD, no asm, openssl-crypto Checksum list: xxh128 xxh3 xxh64 (xxhash) md5 md4 none Compress list: zstd lz4 zlibx zlib none rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. Recipient systems: (rsync 3.1.3-6) -- rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1971932/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
I've added a few alternatives how to fix the problem, mainly using az cli for vmss, ansible or running a daemonset in this gist : https://gist.github.com/naioja/eb8bac307a711e704b7923400b10bc14 -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Microsoft Support provided fix for AKS, which I also tested successfully
is:
kubectl get no -o json | jq -r '.items[].spec.providerID' | cut -c 9- | az vmss
run-command invoke --ids @- \
--command-id RunShellScript \
--scripts 'grep nameserver /etc/resolv.conf || { dhclient -x; dhclient -i
eth0; sleep 10; pkill dhclient; grep nameserver /etc/resolv.conf; }'
--
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/1988119
Title:
Update to systemd 237-3ubuntu10.54 broke dns
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Two servers today that updated systemd to "systemd 237-3ubuntu10.54"
https://ubuntu.com/security/notices/USN-5583-1
could not resolve dns anymore.
no dns servers, normally set through dhcp.
Ubuntu 18.04
Temp fix.
1. Edit /etc/systemd/resolved.conf
1. Add/Uncomment # FallbackDNS=168.63.129.16
1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service
1. Confirm dns working with systemd-resolve google.com
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1987620] Re: kmod v30 missing new modules.builtin.modinfo file
This bug was fixed in the package initramfs-tools - 0.140ubuntu17 --- initramfs-tools (0.140ubuntu17) kinetic; urgency=medium * Include update from Debian for depmod from kmod 30 (LP: #1987620) + Copy modules.builtin.modinfo into initramfs (Closes: #1014319) -- Graham Inggs Tue, 30 Aug 2022 13:47:27 + ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1987620 Title: kmod v30 missing new modules.builtin.modinfo file Status in initramfs-tools package in Ubuntu: Fix Released Status in kmod package in Ubuntu: Invalid Status in initramfs-tools package in Debian: Unknown Bug description: depmod: WARNING: could not open modules.builtin.modinfo at /tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic: No such file or directory https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/amd64/i/initramfs-tools/20220823_075538_8b7f5@/log.gz We probably need to install the corresponding linux-modules-* package to get that file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1987620/+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 1988196] Re: presage: ftbfs with GCC-11
This bug was fixed in the package presage - 0.9.1-2.2ubuntu3 --- presage (0.9.1-2.2ubuntu3) kinetic; urgency=medium * d/p/c++17.patch: fix the build against GCC-11 by porting the code to C++17 (LP: #1988196) * d/p/format-security.patch: fix insecure format strings in the demo code (FTBFS on Ubuntu due to -Werror=format-security.patch) -- Simon Chopin Tue, 30 Aug 2022 17:56:09 +0200 ** Changed in: presage (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to presage in Ubuntu. https://bugs.launchpad.net/bugs/1988196 Title: presage: ftbfs with GCC-11 Status in presage package in Ubuntu: Fix Released Status in presage package in Debian: New Bug description: Imported from Debian bug http://bugs.debian.org/984297: Package: src:presage Version: 0.9.1-2.2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/presage_0.9.1-2.2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] presage.h:199:33: error: ISO C++17 does not allow dynamic exception specifications 199 | std::string context() const throw (PresageException); | ^ presage.h:206:33: error: ISO C++17 does not allow dynamic exception specifications 206 | bool context_change() const throw (PresageException); | ^ presage.h:212:32: error: ISO C++17 does not allow dynamic exception specifications 212 | std::string prefix() const throw (PresageException); |^ presage.h:221:58: error: ISO C++17 does not allow dynamic exception specifications 221 | std::string config(const std::string variable) const throw (PresageException); | ^ presage.h:230:76: error: ISO C++17 does not allow dynamic exception specifications 230 | void config(const std::string variable, const std::string value) const throw (PresageException); | ^ presage.h:239:30: error: ISO C++17 does not allow dynamic exception specifications 239 | void save_config() const throw (PresageException); | ^ presage.cpp:34:5: error: ISO C++17 does not allow dynamic exception specifications 34 | throw (PresageException) | ^ presage.cpp:45:5: error: ISO C++17 does not allow dynamic exception specifications 45 | throw (PresageException) | ^ presage.cpp:65:5: error: ISO C++17 does not allow dynamic exception specifications 65 | throw (PresageException) | ^ presage.cpp:91:5: error: ISO C++17 does not allow dynamic exception specifications 91 | throw (PresageException) | ^ presage.cpp:140:5: error: ISO C++17 does not allow dynamic exception specifications 140 | throw (PresageException) | ^ presage.cpp:147:5: error: ISO C++17 does not allow dynamic exception specifications 147 | throw (PresageException) | ^ presage.cpp:153:5: error: ISO C++17 does not allow dynamic exception specifications 153 | throw (PresageException) | ^ presage.cpp:201:5: error: ISO C++17 does not allow dynamic exception specifications
[Touch-packages] [Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date
I have filed a separate ticket on this for ubuntu 16.04 and cherry-picked the
linked fix and tested.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901
I didn't see this ticket before I filed my ticket.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1533631
Title:
dhclient killed when DHCPv6 lease is out-of date
Status in NetworkManager:
Fix Released
Status in isc-dhcp package in Ubuntu:
In Progress
Status in network-manager package in Ubuntu:
In Progress
Bug description:
Network Manager summarily kills the IPv6 dhclient process when the
DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
date, leaving the IPv6 interface without a stateful IPv6 address, or,
if the "require IPv6 address on this interface" option is enabled,
causes NM to cycle continuously deactivating and reactivating the
interface (including the IPv4 addresses).
This is effectively a Denial Of Service. It can be trivially induced
if, for example, the dhclient6-$(UUID}.lease file contains a lease
that was issued before the user went away on vacation or the PC wasn't
connected to the same network for a few days (depending on the lease
renew/rebind/expiry times). Calculation on the old lease of
start + preferred_lifetime < NOW
triggers dhclient to 'DEPREFER6' the lease (withdraw the address
record) and ask the DHCPv6 server for a new lease, but Network Manager
will kill the dhclient because it only sees an 'EXPIRE6' state change.
In summary, when the DHCPv6 state transitions from "bound" to
"unknown" then "expire" to "done" Network Manager kills the 'dhclient'
process before it has chance to request and bind a fresh lease, If
'dhclient' is run manually with the same command-line options and
allowed to continue running it correctly gains a new lease.
Network Manager doesn't know how to handle "DEPREF6", which is sent
from isc-dhcp dhclient to the helper script (set by "-sf" option).
So it seems that to correctly solve this issue Network Manager must be
taught how to handle DEPREF6.
/var/log/syslog will show a message from dhclient of the form:
dhclient: PRC: Address 2a02:8011:2007::2 depreferred.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1533631/+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 1969901] Re: network-manager fails to renew ipv6 address
It seems like https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1533631 is the same bug as this one.
--
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/1969901
Title:
network-manager fails to renew ipv6 address
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Incomplete
Bug description:
[Impact]
* This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
used.
* Network manager might kill dhclient(6) and fail to start it again
causing the IPv6 address to be lost on a network that uses mixed
IPv4/IPV6.
The network status will still be seen as online in gnome since ipv4
is still active.
The user then have to manually remove the dhcpv6 lease files and
restart ipv6 connection/restart network manager to regain IPv6
connectivity.
* This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
is based on 1.10.6):
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
* Upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=783391
[Test Plan]
The test requires three computers
* one computer runing isc dhcpd server (with network configured static)
* one computer running patched network manager
* one computer running vanilla ubuntu
The idea is to execute on an isolated network and trigger the error by
changing
ip range handed out by the dhcp-server to force a nack response back to the
clients.
Expected result
* patched network keeps dhclient6 alive
* vanilla network manager will fail to keep dhclient6 alive
in network manager logs dhcp6 will expire and not be restarted
ON THE SERVER
# Disable app-armor, as it has rules restricting dhcpd
aa-teardown
# install isc dhcpserver
isc-dhcp-server
# configure network static
sudo nmcli connection modify "${CONNECTION_NAME}" \
ipv4.method "manual" \
ipv4.addresses "192.168.1.1/24" \
ipv4.gateway "192.168.1.254" \
ipv4.dns "192.168.1.1" \
ipv6.method "manual" \
ipv6.addresses "2001:db8:0:1::1/64" \
ipv6.gateway "2001:db8:0:1::ffbb" \
ipv6.dns "2001:db8:0:1::1/64"
mkdir -p tmp
touch tmp/dhcpd4_a.leases
touch tmp/dhcpd4_b.leases
touch tmp/dhcpd6_a.leases
touch tmp/dhcpd6_b.leases
Then it is time to execute dhcpd
-f - run in foreground
-d - print errors to stderr instead of syslog
# Start in separate terminals
dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6
Press ctrl-C to kill servers, then restart with the b configurations
dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6
Then leases to expire (check for clients that kills dhclient)
Press ctrl-C to kill servers, then restart with the a configurations
ON THE CLIENTS
Setup:
Configure ipv6 network in settings to use dhcp (using the gui)
Test:
check that dhcp clients are still running:
ps aux|grep dhclient
Expected in output
one client for dhcpv4
one client for dhcpv6
Also check network manager status :
journalctl -u NetworkManager.service
journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4
if dhclient is not running:
stop network in gui
remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the
lease for the client not running.
start network in gui
if dhclients are running:
wait additional ten minutes, repeat from beginning of test
[Where problems could occur]
* The change is in the dchp lease expiration handling so verify that
there is no regression in dhcp renewals on different type of
configuration include IPv6
[Other Info]
* We have tested this patch on a couple of clients where we have seen this
this problem. If this patch is feasible to include in Ubuntu 18.04 we
could request more users to test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+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 1969901] Re: network-manager fails to renew ipv6 address
** Description changed:
[Impact]
* This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
used.
* Network manager might kill dhclient(6) and fail to start it again
causing the IPv6 address to be lost on a network that uses mixed
IPv4/IPV6.
The network status will still be seen as online in gnome since ipv4
is still active.
The user then have to manually remove the dhcpv6 lease files and
restart ipv6 connection/restart network manager to regain IPv6
connectivity.
* This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
is based on 1.10.6):
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
* Upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=783391
[Test Plan]
- * The exact conditions for reproducing this bug on mixed IPv4/IPv6
- networks are not known but includes using both IPv4 and IPv6,
- both using dhcp.
+ The test requires three computers
+ * one computer runing isc dhcpd server (with network configured static)
+ * one computer running patched network manager
+ * one computer running vanilla ubuntu
+
+ The idea is to execute on an isolated network and trigger the error by
changing
+ ip range handed out by the dhcp-server to force a nack response back to the
+ clients.
+
+ Expected result
+ * patched network keeps dhclient6 alive
+ * vanilla network manager will fail to keep dhclient6 alive
+ in network manager logs dhcp6 will expire and not be restarted
+
+ ON THE SERVER
+ # Disable app-armor, as it has rules restricting dhcpd
+ aa-teardown
+
+ # install isc dhcpserver
+ isc-dhcp-server
+
+ # configure network static
+ sudo nmcli connection modify "${CONNECTION_NAME}" \
+ ipv4.method "manual" \
+ ipv4.addresses "192.168.1.1/24" \
+ ipv4.gateway "192.168.1.254" \
+ ipv4.dns "192.168.1.1" \
+ ipv6.method "manual" \
+ ipv6.addresses "2001:db8:0:1::1/64" \
+ ipv6.gateway "2001:db8:0:1::ffbb" \
+ ipv6.dns "2001:db8:0:1::1/64"
+
+ mkdir -p tmp
+ touch tmp/dhcpd4_a.leases
+ touch tmp/dhcpd4_b.leases
+ touch tmp/dhcpd6_a.leases
+ touch tmp/dhcpd6_b.leases
+
+ Then it is time to execute dhcpd
+ -f - run in foreground
+ -d - print errors to stderr instead of syslog
+
+ # Start in separate terminals
+ dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
+ dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6
+
+ Press ctrl-C to kill servers, then restart with the b configurations
+
+ dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
+ dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6
+
+ Then leases to expire (check for clients that kills dhclient)
+ Press ctrl-C to kill servers, then restart with the a configurations
+
+ ON THE CLIENTS
+ Setup:
+ Configure ipv6 network in settings to use dhcp (using the gui)
+
+ Test:
+ check that dhcp clients are still running:
+ ps aux|grep dhclient
+
+ Expected in output
+ one client for dhcpv4
+ one client for dhcpv6
+
+ Also check network manager status :
+ journalctl -u NetworkManager.service
+ journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
+ journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4
+
+ if dhclient is not running:
+ stop network in gui
+ remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the
lease for the client not running.
+ start network in gui
+
+ if dhclients are running:
+ wait additional ten minutes, repeat from beginning of test
[Where problems could occur]
* The change is in the dchp lease expiration handling so verify that
there is no regression in dhcp renewals on different type of
configuration include IPv6
[Other Info]
* We have tested this patch on a couple of clients where we have seen this
this problem. If this patch is feasible to include in Ubuntu 18.04 we
could request more users to test.
--
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/1969901
Title:
network-manager fails to renew ipv6 address
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Incomplete
Bug description:
[Impact]
* This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
used.
* Network manager might kill dhclient(6) and fail to start it again
causing the IPv6 address to be lost on a network that uses mixed
IPv4/IPV6.
The network status will still be seen as online in gnome since ipv4
is still active.
The user then have to manually remove the dhcpv6 lease files and
restart ipv6 connection/restart network manager to regain IPv6
connectivity.
* This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
@atykhyy thank you that worked for VMSS! I also had some VMs without scale sets, fixed those with: az vm availability-set list -g --query "[].virtualMachines[].id" --output tsv | az vm run-command invoke --scripts "echo FallbackDNS=168.63.129.16 >> /etc/systemd/resolved.conf; systemctl restart systemd-resolved.service" --command-id RunShellScript --ids @- -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1987620] Re: kmod v30 missing new modules.builtin.modinfo file
Have just upgraded initramfs-tools 0.140ubuntu17 with kinetic 5.19.0-15 kernel, and the previous issue has not been seen. (1987329) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1987620 Title: kmod v30 missing new modules.builtin.modinfo file Status in initramfs-tools package in Ubuntu: Confirmed Status in kmod package in Ubuntu: Invalid Status in initramfs-tools package in Debian: Unknown Bug description: depmod: WARNING: could not open modules.builtin.modinfo at /tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic: No such file or directory https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/amd64/i/initramfs-tools/20220823_075538_8b7f5@/log.gz We probably need to install the corresponding linux-modules-* package to get that file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1987620/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
** Tags added: regression-update -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Is it safe to downgrade from systemd 237-3ubuntu10.54 to the previous 237-3ubuntu10.50? -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
az cli from cmd.exe, something like this for AKS nodes experiencing the issue: az vmss list-instances -g -n vmss --query "[].id" --output tsv | az vmss run-command invoke --scripts "echo FallbackDNS=168.63.129.16 >> /etc/systemd/resolved.conf; systemctl restart systemd-resolved.service" --command-id RunShellScript --ids @- -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards
This issue also exists for "Yeti Stereo Microphone" and "HD Pro Webcam C920". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1002952 Title: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards Status in alsa-lib package in Ubuntu: Confirmed Bug description: === Read me first === = Symptom = If you have a USB headset, or other USB device that does not have any S/PDIF output, but yet sometimes there is an extra device called "Digital Output (S/PDIF)" for that device, you're suffering from this bug. This bug is only for USB devices - if you have an invalid digital output for some other type of device, please file a separate bug instead. = Workaround = If you're affected, please try this workaround: first check the output of "aplay -l" (lowercase L), or "arecord -l" if it's an input device, and grab the first of two name in brackets: Example: card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio] here grab the name "Sennheiser USB Headset". Now edit the file /usr/share/alsa/cards/USB-Audio.conf (requires root permissions) Around line 40, you will find a line saying "Logitech USB Headset" 999 Add a new line after this line, so that there is now a new line called "Sennheiser USB Headset" 999 (including quotes, and replace "Sennheiser USB Headset" with whatever your particular card was named.) Save the file and reboot your computer for the changes to take effect. = Already known devices = These card names are already in 12.04: "Blue Snowball" "Logitech USB Headset" "Logitech Web Camera" These card names are on their way into 12.04: "Logitech Speaker Lapdesk N700" "Logitech Wireless Headset" "Plantronics USB Headset" "Sennheiser USB headset" If you have one of the above four, please help out by testing the proposed repository and report back in bug 987163. If your name is not listed above, please add a comment to this bug, including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo - they will be collected for a SRU later on, or at least make it into the next release of Ubuntu. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04
*** This bug is a duplicate of bug 1842320 *** https://bugs.launchpad.net/bugs/1842320 I am getting this error on a workstation with 128GB of RAM. Compression does nothing to fix, especially with how big the nvidia driver is. -- 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/1970402 Title: Initrd out of memory error after upgrade to 22.04 Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools source package in Jammy: Confirmed Bug description: After upgrading to 22.04 system is unbootable because of "out of memory" error when loading initial ramdisk. I was able to fix it by editing cat /etc/initramfs-tools/initramfs.conf and changing configuration to: MODULES=dep COMPRESS=xz RUNSIZE=15% Not sure which one helped, but I can test it if needed. System information: Description:Ubuntu 22.04 LTS Release:22.04 initramfs-tools: Installed: 0.140ubuntu13 Candidate: 0.140ubuntu13 Version table: *** 0.140ubuntu13 500 500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
To temporary mitigate the ImagePullBackOff I scaled up a new functional node (DNS wise) and used this command to reconcile the AKS cluster: az resource update --resource-group --name --namespace Microsoft.ContainerService --resource-type ManagedClusters This recovered CoreDNS in the kube-system namespace, which fixed the ImagePullBackOff -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988196] [NEW] presage: ftbfs with GCC-11
Public bug reported: Imported from Debian bug http://bugs.debian.org/984297: Package: src:presage Version: 0.9.1-2.2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/presage_0.9.1-2.2_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] presage.h:199:33: error: ISO C++17 does not allow dynamic exception specifications 199 | std::string context() const throw (PresageException); | ^ presage.h:206:33: error: ISO C++17 does not allow dynamic exception specifications 206 | bool context_change() const throw (PresageException); | ^ presage.h:212:32: error: ISO C++17 does not allow dynamic exception specifications 212 | std::string prefix() const throw (PresageException); |^ presage.h:221:58: error: ISO C++17 does not allow dynamic exception specifications 221 | std::string config(const std::string variable) const throw (PresageException); | ^ presage.h:230:76: error: ISO C++17 does not allow dynamic exception specifications 230 | void config(const std::string variable, const std::string value) const throw (PresageException); | ^ presage.h:239:30: error: ISO C++17 does not allow dynamic exception specifications 239 | void save_config() const throw (PresageException); | ^ presage.cpp:34:5: error: ISO C++17 does not allow dynamic exception specifications 34 | throw (PresageException) | ^ presage.cpp:45:5: error: ISO C++17 does not allow dynamic exception specifications 45 | throw (PresageException) | ^ presage.cpp:65:5: error: ISO C++17 does not allow dynamic exception specifications 65 | throw (PresageException) | ^ presage.cpp:91:5: error: ISO C++17 does not allow dynamic exception specifications 91 | throw (PresageException) | ^ presage.cpp:140:5: error: ISO C++17 does not allow dynamic exception specifications 140 | throw (PresageException) | ^ presage.cpp:147:5: error: ISO C++17 does not allow dynamic exception specifications 147 | throw (PresageException) | ^ presage.cpp:153:5: error: ISO C++17 does not allow dynamic exception specifications 153 | throw (PresageException) | ^ presage.cpp:201:5: error: ISO C++17 does not allow dynamic exception specifications 201 | throw (PresageException) | ^ presage.cpp:207:5: error: ISO C++17 does not allow dynamic exception specifications 207 | throw (PresageException) | ^ presage.cpp:213:5: error: ISO C++17 does not allow dynamic exception specifications 213 | throw (PresageException) | ^ presage.cpp:219:5: error: ISO C++17 does not allow dynamic exception specifications 219 | throw (PresageException) | ^ presage.cpp:225:5: error: ISO C++17 does not allow dynamic exception specifications 225 | throw (PresageException) | ^ presage.cpp:231:5: error: ISO C++17 does not allow dynamic exception specifications 231 | throw (PresageException) | ^ make[5]: *** [Makefile:580: libpresage_la-presage.lo] Error 1 make[5]: Leaving directory '/<>/src/lib' make[4]: *** [Makefile:616: all-recursive] Error 1 make[4]: Leaving directory
[Touch-packages] [Bug 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Yes @richardprammer, it appears ImagePullBackOff is one of the symptoms of this issue. -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
> Could this be a related issue, when deployment to aks fails, due to a connection refused when pulling images from azure container registry(ImagePullBackOff). I you look closer at the message accompanying the ImagePullBackOff, you should see something like: dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:36288->[::1]:53: read: connection refused Port 53 is the port a DNS server usually listens on. If this is what you're seeing, then yes: your problems are caused by the issue described in here. -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Could this be a related issue, when deployment to aks fails, due to a connection refused when pulling images from azure container registry(ImagePullBackOff). This problem started this morning out of the blue. Credentials for azure container service are ok and about every 20 image pulls I get one, and the container would start. -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1986984] Re: [FFe] tzdata 2022c update
Please proceed! Approved.
** Changed in: tzdata (Ubuntu Kinetic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Confirmed
Status in tzdata source package in Focal:
Confirmed
Status in tzdata source package in Jammy:
Confirmed
Status in tzdata source package in Kinetic:
Triaged
Bug description:
New timezone data, with the following timezones impacted:
- Chile will spring forward on 2022-09-11, not 2022-09-04 (America/Santiago)
- Iran no longer observes DST (Asia/Tehran)
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v America/Santiago | grep 'Sep.*2022'
-> should indicate Sep 11, not Sep 4
2) zdump -v Asia/Tehran | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
The assertions would crash on 2022a.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
[Original report]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+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 1986984] Re: [FFe] tzdata 2022c update
** Changed in: tzdata (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Focal)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Triaged
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Confirmed
Status in tzdata source package in Focal:
Confirmed
Status in tzdata source package in Jammy:
Confirmed
Status in tzdata source package in Kinetic:
Triaged
Bug description:
New timezone data, with the following timezones impacted:
- Chile will spring forward on 2022-09-11, not 2022-09-04 (America/Santiago)
- Iran no longer observes DST (Asia/Tehran)
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v America/Santiago | grep 'Sep.*2022'
-> should indicate Sep 11, not Sep 4
2) zdump -v Asia/Tehran | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
The assertions would crash on 2022a.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
[Original report]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+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 1699942] Re: network-manager fails to deprecate addresses
The bug is from 2017 without activity until now, from a desktop perspective it isn't a rls issue, tagging a notfixing ** Tags removed: rls-kk-incoming ** Tags added: rls-kk-notfixing -- 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/1699942 Title: network-manager fails to deprecate addresses Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.
It appears dbus is stuck in kinetic-proposed due to failures in dependency resolution on i386; there are two new arch-indep packages in the merged package which the dbus package depends on, but they lack Multi-Arch tags in d/control. I'm attaching (yet another :) debdiff which adds M-A: foreign to these packages which should permit the resolver to use these packages when attempting to install dbus:i386. @slyon could you sponsor this change into -proposed? Hopefully things will migrate this time (and many thanks to @jawn-smith for the recollection of Multi-Arch when dealing with i386 things!) ** Patch added: "3-1959211.debdiff" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+attachment/5612541/+files/3-1959211.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.14.0-2 from Debian unstable. Status in dbus package in Ubuntu: In Progress Bug description: Please merge dbus 1.14.0-2 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
We are testing this in our AKS clusters now, but we were able to manually scale up a node pool which brought up new "working" nodes. Then manually scaled the pool back down to remove the "non-working" nodes. This left only new nodes up and the services are functioning properly now. -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
For people having this is issue on AKS clusters with custom DNS... We have done this on all affected nodepools: $ VMSS=XXX-vmss $ nodeResourceGroup=XXX-worker $ az vmss list-instances -g $nodeResourceGroup -n $VMSS --query "[].id" --output tsv | az vmss run-command invoke --scripts "systemd-resolve --set-dns=your_dns --set-dns=your_dns --set-domain=reddog.microsoft.com --interface=eth0" --command-id RunShellScript --ids @- -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
I just hit it, after system upgrades of the following packages: Start-Date: 2022-08-30 06:13:35 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:i386 (237-3ubuntu10.50, 237-3ubuntu10.54) End-Date: 2022-08-30 06:13:36 Start-Date: 2022-08-30 06:13:42 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:i386 (237-3ubuntu10.50, 237-3ubuntu10.54), libudev1:i386 (237-3ubuntu10.50, 237-3ubuntu10.54) End-Date: 2022-08-30 06:13:48 Start-Date: 2022-08-30 06:13:54 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:i386 (237-3ubuntu10.50, 237-3ubuntu10.54), libpam-systemd:i386 (237-3ubuntu10.50, 237-3ubuntu10.54), systemd:i386 (237-3ubuntu10.50, 237-3ubuntu10.54), libnss-systemd:i386 (237-3ubuntu10.50, 237-3ubuntu10.54) End-Date: 2022-08-30 06:14:03 -- 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/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Invalid Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
For anyone hitting this issue with AKS clusters: I have embedded the workaround above in a daemonset to avoid having to restart all nodes (for now) https://gist.github.com/skinny/96e7feb6b347299ebfacaa76295a82e7 - Please check the image+tag used in the daemonset to whatever is available in your cluster. - Deploy this daemonset to the cluster (default namespace is used) - After all pods are running 1/1 for a bit, you can delete it - Images can be pulled again :) HTH -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988078] Re: Please backport systemd-hwdb patches to support src:systemd-hwe tests
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/429150 -- 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/1988078 Title: Please backport systemd-hwdb patches to support src:systemd-hwe tests Status in systemd package in Ubuntu: New Bug description: [Impact] We plan to SRU src:systemd-hwe to Jammy[1] to provide an easier way to SRU HWE hwdb rules to Ubuntu. The src:systemd-hwe package contains a test script[2] to ensure that no redundant hwdb rules are added to the package, i.e. rules that are already present in src:systemd. This test requires patches to implement --root flag support for the `systemd- hwdb query` command[3]. These patches are already present in kinetic. Without these patches in Jammy, src:systemd-hwe would have to disable these tests, which are important to maintaining HWE hwdb rules in Ubuntu. [1] https://bugs.launchpad.net/ubuntu/+source/systemd-hwe/+bug/1983996 [2] https://git.launchpad.net/~canonical-foundations/+git/systemd-hwe/tree/tests/hwdb-redundancy?h=main [3] https://github.com/systemd/systemd/pull/23518 [Test plan] * Create a new directory for testing hwdb rule queries: $ mkdir -p fakeroot/etc/udev/hdwb.d * Add a new .hwdb file to override an existing rule. For example, I chose to override the last entry from /lib/udev/hdwb.d/60-keyboard.hwdb: $ tail -2 /lib/udev/hwdb.d/60-keyboard.hwdb > fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb $ sed -i 's/chromebook/reserved/g' fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb $ cat fakeroot/etc/udev/hwdb.d/60-keyboard.hwdb evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* XKB_FIXED_MODEL=reserved * Create the hwdb.bin within fakeroot: $ systemd-hwdb update --root fakeroot $ ls fakeroot/etc/udev/hwdb.bin fakeroot/etc/udev/hwdb.bin * Finally, attempt to query this new hwdb.bin using systemd-hwdb query. On an unpatched system, we will see results from the system's hwdb.bin: $ systemd-hwdb query --root fakeroot evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL XKB_FIXED_MODEL=chromebook ...and on a patched system we should see the overridden rule: $ systemd-hwdb query --root fakeroot evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pnPeppy:* | grep XKB_FIXED_MODEL XKB_FIXED_MODEL=reserved [Where problems could occur] The patches add support for the --root flag when calling systemd-hwdb query, thus changing the behavior of this command (previously, query would always load the system's hwdb.bin). It is unlikely that existing scripts try to use the --root flag with `systemd-hwdb query`, but if they did, this is where we would see problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988078/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Hey guys, nothing is working. My application has been out since this early morning. We have already tried to restart the nodes, restart the VM, but nothing has been working and we don't have any update from Microsoft. 4 hours ago they said "More information will be provided within 60 minutes, when we expect to know more about the root cause and mitigation workstreams.". -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1987620] Re: kmod v30 missing new modules.builtin.modinfo file
** Changed in: kmod (Ubuntu) Status: Confirmed => Invalid ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Graham Inggs (ginggs) ** Bug watch added: Debian Bug tracker #1014319 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014319 ** Also affects: initramfs-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014319 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1987620 Title: kmod v30 missing new modules.builtin.modinfo file Status in initramfs-tools package in Ubuntu: Confirmed Status in kmod package in Ubuntu: Invalid Status in initramfs-tools package in Debian: Unknown Bug description: depmod: WARNING: could not open modules.builtin.modinfo at /tmp/autopkgtest.tKMBKb/autopkgtest_tmp/mkinitramfs_uvT4BW/lib/modules/5.15.0-27-generic: No such file or directory https://autopkgtest.ubuntu.com/results/autopkgtest- kinetic/kinetic/amd64/i/initramfs-tools/20220823_075538_8b7f5@/log.gz We probably need to install the corresponding linux-modules-* package to get that file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1987620/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Not sure if this is the best place to help people out understanding if nodes are impacted. We already saw 2 different types of impact on our Azure AKS clusters. - Pod not able to Terminate - New images being pulled from ACR (or any container registry Sometimes it was very clear that we saw the nodes where "Not Ready` in order cases it's very hard to detect. We have found a way to detect if your nodes are affected. kubectl logs When you get the following error you know it's impacted: Error from server (InternalError): Internal error occurred: Authorization error (user=masterclient, verb=get, resource=nodes, subresource=proxy) So restarting the node will help and especially if your cluster is sensitive then you can be more granular about the restart. I hope it helps some visitors from the azure status page -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988145] Re: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key
Thanks for pointing at user _apt. My /tmp is chmod 777 and mounted as tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,inode64) When I create the chroot directory in / which is chmod 755 I can execute the test case. So I guess it is one of the mount options that is incompatible with the test case. We need to update the test case and describe the requirements for successful execution- -- 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/1988145 Title: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Status in apt package in Ubuntu: Invalid Bug description: I tried to run http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results I downloaded http://cdimage.ubuntu.com/ubuntu- base/focal/daily/20220829.1/focal-base-riscv64.tar.gz mkdir base sudo tar -C base -zxf focal-base-riscv64.tar.gz sudo mount --bind /proc base/proc sudo mount --bind /sys base/sys sudo mount --bind /dev base/dev sudo mount --bind /dev/pts base/dev/pts sudo cp /etc/resolv.conf base/etc/ sudo chroot base apt-get update results in: Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key Reading package lists... Done W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. As touch /tmp/apt.conf.fsIutr works without issues there must be a bug in how apt creates temporary files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988145/+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 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages
** Description changed: + [Impact] + + * Linux-restricted-modules for the 390 drivers were disabled + temporarily back in January, however they were not re-enabled when + support for the new kernel was added. + + * Including the 390 release in the ISO causes the 5.13 packages to be + pulled in. + + [Test Plan] + + * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver + can be installed with its linux-restricted-modules. + + [Where problems could occur] + + * The addition of modules for an already existing driver series would not +cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: + https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + _ + Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. ** Description changed: [Impact] - * Linux-restricted-modules for the 390 drivers were disabled + * Linux-restricted-modules for the 390 drivers were disabled temporarily back in January, however they were not re-enabled when support for the new kernel was added. - * Including the 390 release in the ISO causes the 5.13 packages to be + * Including the 390 release in the ISO causes the 5.13 packages to be pulled in. [Test Plan] - * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver + * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver can be installed with its linux-restricted-modules. [Where problems could occur] - * The addition of modules for an already existing driver series would not -cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: + * The addition of modules for an already existing driver series would not + cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + + * Other kernel releases support the 390 series. _ Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated.
[Touch-packages] [Bug 1988062] Re: Tests are failing on builders with proxy set
** Changed in: glib-networking (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1988062 Title: Tests are failing on builders with proxy set Status in glib-networking package in Ubuntu: Fix Released Bug description: Reported upstream https://gitlab.gnome.org/GNOME/glib- networking/-/issues/195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1988062/+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 1979879] Re: Apparmor profile in 22.04 jammy - fails to start when printing enabled
Updated bug description with: Moreover, the dmesg output failed and it has showed that the 'k' flag is required for the *.tdb files within /etc/apparmor.d/abstractions/samba. It is required to close that bug in professional way, because the flag is also affected by samba-bgqd. ** Description changed: See bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1191532 Fix was backported, but the path to samba-bgqd is wrong on 22.04. Currently apparmor profile has it like this: /usr/lib*/samba/samba-bgqd When in fact 22.04 has it on /usr/lib/x86_64-linux-gnu/samba/samba-bgqd Moreover, the dmesg output failed and it has showed that the 'k' flag is - required in the *.tdb files. + required for the *.tdb files within /etc/apparmor.d/abstractions/samba. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1979879 Title: Apparmor profile in 22.04 jammy - fails to start when printing enabled Status in apparmor package in Ubuntu: Invalid Status in samba package in Ubuntu: Fix Released Status in apparmor source package in Jammy: In Progress Status in samba source package in Jammy: Triaged Bug description: See bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1191532 Fix was backported, but the path to samba-bgqd is wrong on 22.04. Currently apparmor profile has it like this: /usr/lib*/samba/samba-bgqd When in fact 22.04 has it on /usr/lib/x86_64-linux-gnu/samba/samba- bgqd Moreover, the dmesg output failed and it has showed that the 'k' flag is required for the *.tdb files within /etc/apparmor.d/abstractions/samba. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1979879/+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 1979879] Re: Apparmor profile in 22.04 jammy - fails to start when printing enabled
** Description changed: See bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1191532 Fix was backported, but the path to samba-bgqd is wrong on 22.04. Currently apparmor profile has it like this: /usr/lib*/samba/samba-bgqd When in fact 22.04 has it on /usr/lib/x86_64-linux-gnu/samba/samba-bgqd + + Moreover, the dmesg output failed and it has showed that the 'k' flag is + required in the *.tdb files. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1979879 Title: Apparmor profile in 22.04 jammy - fails to start when printing enabled Status in apparmor package in Ubuntu: Invalid Status in samba package in Ubuntu: Fix Released Status in apparmor source package in Jammy: In Progress Status in samba source package in Jammy: Triaged Bug description: See bug here: https://bugzilla.opensuse.org/show_bug.cgi?id=1191532 Fix was backported, but the path to samba-bgqd is wrong on 22.04. Currently apparmor profile has it like this: /usr/lib*/samba/samba-bgqd When in fact 22.04 has it on /usr/lib/x86_64-linux-gnu/samba/samba- bgqd Moreover, the dmesg output failed and it has showed that the 'k' flag is required for the *.tdb files within /etc/apparmor.d/abstractions/samba. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1979879/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
** Also affects: systemd Importance: Undecided Status: New ** No longer affects: systemd -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages
...discussed this with the kernel team and it seems to be a bug in the 5.15 hwe lrm kernel packages. Apparently because of an error, the nvidia-390 packages have not been prepared for this kernel. And since we pull in 390 (and should), this causes the build infrastructure to pull in the old 5.13 kernels along with them. The kernel team is working on a lrm-only respin. ** Also affects: linux-restricted-modules-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid -- 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/1988143 Title: 20.04.5 (20220829.1 build) has kernel 5.13 packages Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+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 1959211] Re: Please merge dbus 1.14.0-2 from Debian unstable.
> I'll upload it using git-ubuntu style, too, so it will be easier to do the next merge. I must get Robie to remind me what I need to stuff in the .changes file to make that automatic (I vaguely recall him mentioning there were some extra tags that could/should be placed there). > Using a "ubuntu/bionic" gbp branch, is probably as useless as using a "debian/unstable" branch in Ubuntu's development release. I wonder if we could/should drop that part of the delta on the next occasion. Yes -- during the merge I initially dropped that change, but then reverted it because it made the range-diff a little noisier for no particularly good reason. Still, I do agree it's basically pointless and should be dropped. > This seems to be generally useful. Would you mind sending this patch to Debian, so we can eventually drop it from our delta? Will do. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1959211 Title: Please merge dbus 1.14.0-2 from Debian unstable. Status in dbus package in Ubuntu: In Progress Bug description: Please merge dbus 1.14.0-2 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1959211/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
> This won't help anyone that has already received the broken update - I think the advice there is to restart, or there is a workaround in the OP here - but it should prevent any further occurrences. Do note this is not a solution for those using non-Azure resolvers provided via DHCP through their VNET. These users must reboot or manually set the fallback servers to their custom DNS resolver addresses -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988144] Re: klist not showing tgt after reboot
** Package changed: ubuntu => krb5 (Ubuntu) ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1988144 Title: klist not showing tgt after reboot Status in krb5 package in Ubuntu: New Bug description: Hello, iam not sure if this is a bug, but iam noticed a different behaviour of kinit/klist between Ubuntu 18.04 and 22.04 I already talked to sam hartman who is maintainer of krb5 packages at debian and he told that basically there is no difference between different version of kinit/klist and one should dig in Ubuntu environment. Let me decribe the notice: We use kinit/klist/krb5 keytab as base for sssd and ssh access controlled by AD. In Ubuntu 18.04 LTS i could do: "kinit myprincipal" and created a valid tgt. This tgt was stable and survived a reboot which can be viewed by "klist". I log in as unprivileged user, doing "sudo -i" and see: myhost: # klist Ticket cache: FILE:/tmp/krb5cc_27465975_uqBiyq File /tmp/krb5cc_27465975_uqBiyq is existent and owned by my unprivileged username and group domainusers. Ubuntu 18.04 LTS is using 1.16-2ubuntu0.2 of krb5-user. i have to say, that first login as unprivileged user is done by using ssh-keypair, so no sssd is involved. But by using "sudo -i" sssd is used and worked like expected. Now we switched to Ubuntu 22.04 LTS, Version of krb5-user is 1.19.2-2 Doing kinit myprincipal on 22.04 leads to: myhost: # klist Ticket cache: FILE:/tmp/krb5cc_0 File /tmp/krb5cc_0 is owned by root:root After reboot i can still login successful as unprivileged user make "sudo -i" and klist says: myhost: # klist klist: No credentials cache found (filename: /tmp/krb5cc_0 File /tmp/krb5cc_0 is gone (deleted from unknown), but i see a file /tmp/krb5cc_27465975_nGySkP which is owned by my unprivileged username and group is domainusers. is this expected? It seems that newer klist always wants to use the default name /tmp/krb5cc_0. It creates tgt with this name and tries to read this filename. but after reboot file is recreated with different name and default klist command fails. First login as unprivilged user was done with ssh-keypair without sssd, but "sudo -i" uses sssd agin. Whole thing only works like in 18.04 if you dont use ssh-keypairs and do all logins by hand with manually login, so sssd is forced to use in every step. What do you think? Is this a bug or wrong use? Behaviour of 18.04 was absolutely satisfying. Thanks, Hans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1988144/+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 1988151] Re: Printer not working anymore after update
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 You've provided no details of what Ubuntu product you're using, what release, what package(s) are involved, type of connections, is this a new install (days?, weeks? months?)? old install (days? weeks? months? years?) with changes made etc... You do mention updates, but gave no specifics. Support would likely help you better, and this question can be turned into a Support Question too. I've marked this as 'incomplete', if you believe I'm in error and do wish to report a bug, status can be returned to "New" after you've left a comment provide details so package involved in the bug-filing can be determined, then you'll be requested to provide more details (via `apport-collect`) -- 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/1988151 Title: Printer not working anymore after update Status in cups package in Ubuntu: New Bug description: Multifunction printer (Brother MFC-J6510DW) not working anymore. Since one of the last updates the printer is cancelling the print job it receives. Reinstallation of the driver/printer trying all available connections did not bring success. (dnssd, IPP, LPD, Socket, etc. using cups, with and without dedicated driver .ppd.) Printer scan function is working, though. Printer works under windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1988151/+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 1988151] Re: Printer not working anymore after update
** Package changed: ubuntu => cups (Ubuntu) -- 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/1988151 Title: Printer not working anymore after update Status in cups package in Ubuntu: New Bug description: Multifunction printer (Brother MFC-J6510DW) not working anymore. Since one of the last updates the printer is cancelling the print job it receives. Reinstallation of the driver/printer trying all available connections did not bring success. (dnssd, IPP, LPD, Socket, etc. using cups, with and without dedicated driver .ppd.) Printer scan function is working, though. Printer works under windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1988151/+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 1988151] [NEW] Printer not working anymore after update
You have been subscribed to a public bug: Multifunction printer (Brother MFC-J6510DW) not working anymore. Since one of the last updates the printer is cancelling the print job it receives. Reinstallation of the driver/printer trying all available connections did not bring success. (dnssd, IPP, LPD, Socket, etc. using cups, with and without dedicated driver .ppd.) Printer scan function is working, though. Printer works under windows. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: connectivity printer -- Printer not working anymore after update https://bugs.launchpad.net/bugs/1988151 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups 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 1988144] [NEW] klist not showing tgt after reboot
You have been subscribed to a public bug: Hello, iam not sure if this is a bug, but iam noticed a different behaviour of kinit/klist between Ubuntu 18.04 and 22.04 I already talked to sam hartman who is maintainer of krb5 packages at debian and he told that basically there is no difference between different version of kinit/klist and one should dig in Ubuntu environment. Let me decribe the notice: We use kinit/klist/krb5 keytab as base for sssd and ssh access controlled by AD. In Ubuntu 18.04 LTS i could do: "kinit myprincipal" and created a valid tgt. This tgt was stable and survived a reboot which can be viewed by "klist". I log in as unprivileged user, doing "sudo -i" and see: myhost: # klist Ticket cache: FILE:/tmp/krb5cc_27465975_uqBiyq File /tmp/krb5cc_27465975_uqBiyq is existent and owned by my unprivileged username and group domainusers. Ubuntu 18.04 LTS is using 1.16-2ubuntu0.2 of krb5-user. i have to say, that first login as unprivileged user is done by using ssh-keypair, so no sssd is involved. But by using "sudo -i" sssd is used and worked like expected. Now we switched to Ubuntu 22.04 LTS, Version of krb5-user is 1.19.2-2 Doing kinit myprincipal on 22.04 leads to: myhost: # klist Ticket cache: FILE:/tmp/krb5cc_0 File /tmp/krb5cc_0 is owned by root:root After reboot i can still login successful as unprivileged user make "sudo -i" and klist says: myhost: # klist klist: No credentials cache found (filename: /tmp/krb5cc_0 File /tmp/krb5cc_0 is gone (deleted from unknown), but i see a file /tmp/krb5cc_27465975_nGySkP which is owned by my unprivileged username and group is domainusers. is this expected? It seems that newer klist always wants to use the default name /tmp/krb5cc_0. It creates tgt with this name and tries to read this filename. but after reboot file is recreated with different name and default klist command fails. First login as unprivilged user was done with ssh-keypair without sssd, but "sudo -i" uses sssd agin. Whole thing only works like in 18.04 if you dont use ssh-keypairs and do all logins by hand with manually login, so sssd is forced to use in every step. What do you think? Is this a bug or wrong use? Behaviour of 18.04 was absolutely satisfying. Thanks, Hans ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- klist not showing tgt after reboot https://bugs.launchpad.net/bugs/1988144 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
I've removed the update from bionic-security and bionic-updates, and restored the versions which were previously in there. This won't help anyone that has already received the broken update - I think the advice there is to restart, or there is a workaround in the OP here - but it should prevent any further occurrences. Note that there will be a delay of up to an hour or so for mirrors to receive the deletion. -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1897932] Re: systemd-repart not packaged
After the discussion on the mailing list (ubuntu-devel@) has settled, and @bluca provided an updated MP#427557 to ship systemd-repart as an additional binary package in Jammy (universe, not installed by default), I've moved ahead and staged the changes to provide an upgrade path (removal of systemd-repart in Kinetic++, now provided by the "systemd" binary itself): https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-kinetic=2281670aa8007179170d5cc485bb94e3bbc3b63c I've tested that Jammy's systemd-repart binary is removed/replaced by Kinetic's "systemd" binary on "apt full-upgrade". Also, I've verified that the systemd-repart build-time test is executed when running the build locally (dpkg-buildpackage) and full test logs can be found in "build-deb/meson-logs/testlog.txt". The systemd-repart test is being skipped when ran in sbuild, due to missing the /dev/loop- control device. The new TEST-58-REPART autopkgtest is executed as part of the "upstream-2" test suite. -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. * Attach (local) build-log showing the systemd-repart self-tests passing, as found in build-deb/meson-logs/testlog.txt * Attach autopkgtest logs showing the regression tests passing (especially TEST-58-REPART from "upstream-2" testsuite) * Test upgrade-path Jammy->Kinetic to make sure systemd-repart is properly replaced by Kinetic's "systemd" binary package [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. Runtime behavior of existing components is not affected by the build config change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932/+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 1897932] Re: systemd-repart not packaged
** Description changed: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd-repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. - * Attach (local) build-log showing the systemd-repart self-tests passing - * Attach autopkgtest logs showing the regression tests passing (especially TEST-58-REPART) + * Attach (local) build-log showing the systemd-repart self-tests passing, as found in build-deb/meson-logs/testlog.txt + * Attach autopkgtest logs showing the regression tests passing (especially TEST-58-REPART from "upstream-2" testsuite) * Test upgrade-path Jammy->Kinetic to make sure systemd-repart is properly replaced by Kinetic's "systemd" binary package [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. Runtime behavior of existing components is not affected by the build config change. -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. * Attach (local) build-log showing the systemd-repart self-tests passing, as found in build-deb/meson-logs/testlog.txt * Attach
[Touch-packages] [Bug 1988145] Re: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key
Closing this as invalid. The analysis is flawed, the configuration file is created by user _apt, not root, the call is literally just mkstemp() with the path given in the error message, or rather a template, so there is no bug in apt here. It's more likely to be wrong permissions on /tmp preventing the _apt user from creating files. -- 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/1988145 Title: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Status in apt package in Ubuntu: Invalid Bug description: I tried to run http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results I downloaded http://cdimage.ubuntu.com/ubuntu- base/focal/daily/20220829.1/focal-base-riscv64.tar.gz mkdir base sudo tar -C base -zxf focal-base-riscv64.tar.gz sudo mount --bind /proc base/proc sudo mount --bind /sys base/sys sudo mount --bind /dev base/dev sudo mount --bind /dev/pts base/dev/pts sudo cp /etc/resolv.conf base/etc/ sudo chroot base apt-get update results in: Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key Reading package lists... Done W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. As touch /tmp/apt.conf.fsIutr works without issues there must be a bug in how apt creates temporary files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988145/+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 1988145] Re: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/1988145 ** Tags added: iso-testing -- 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/1988145 Title: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Status in apt package in Ubuntu: Invalid Bug description: I tried to run http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results I downloaded http://cdimage.ubuntu.com/ubuntu- base/focal/daily/20220829.1/focal-base-riscv64.tar.gz mkdir base sudo tar -C base -zxf focal-base-riscv64.tar.gz sudo mount --bind /proc base/proc sudo mount --bind /sys base/sys sudo mount --bind /dev base/dev sudo mount --bind /dev/pts base/dev/pts sudo cp /etc/resolv.conf base/etc/ sudo chroot base apt-get update results in: Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key Reading package lists... Done W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. As touch /tmp/apt.conf.fsIutr works without issues there must be a bug in how apt creates temporary files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988145/+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 1988145] Re: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key
** Changed in: apt (Ubuntu) Status: New => Invalid -- 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/1988145 Title: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Status in apt package in Ubuntu: Invalid Bug description: I tried to run http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results I downloaded http://cdimage.ubuntu.com/ubuntu- base/focal/daily/20220829.1/focal-base-riscv64.tar.gz mkdir base sudo tar -C base -zxf focal-base-riscv64.tar.gz sudo mount --bind /proc base/proc sudo mount --bind /sys base/sys sudo mount --bind /dev base/dev sudo mount --bind /dev/pts base/dev/pts sudo cp /etc/resolv.conf base/etc/ sudo chroot base apt-get update results in: Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key Reading package lists... Done W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. As touch /tmp/apt.conf.fsIutr works without issues there must be a bug in how apt creates temporary files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988145/+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 1988145] Re: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key
Outside the chroot these are my mounts relevant for the test: $ mount | grep /home /dev/mapper/vgubuntu-home on /home type ext4 (rw,relatime) proc on /home/user/temp/base/proc type proc (rw,nosuid,nodev,noexec,relatime) sysfs on /home/user/temp/base/sys type sysfs (rw,nosuid,nodev,noexec,relatime) udev on /home/user/temp/base/dev type devtmpfs (rw,nosuid,relatime,size=7940560k,nr_inodes=1985140,mode=755,inode64) devpts on /home/user/temp/base/dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) ** Description changed: I tried to run http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results - I downloadedhttp://cdimage.ubuntu.com/ubuntu- + I downloaded http://cdimage.ubuntu.com/ubuntu- base/focal/daily/20220829.1/focal-base-riscv64.tar.gz mkdir base sudo tar -C base -zxf focal-base-riscv64.tar.gz sudo mount --bind /proc base/proc sudo mount --bind /sys base/sys sudo mount --bind /dev base/dev sudo mount --bind /dev/pts base/dev/pts sudo cp /etc/resolv.conf base/etc/ sudo chroot base - apt-get update results in: Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease - Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key + Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease - Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key + Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease - Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key + Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease - Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key + Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key Reading package lists... Done W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. - - As touch /tmp/apt.conf.fsIutr works without issues there must be a bug in how apt creates temporary files. + As touch /tmp/apt.conf.fsIutr works without issues there must be a bug + in how apt creates temporary files. -- 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/1988145 Title: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Status in apt package in Ubuntu: New Bug description: I tried to run http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results I downloaded http://cdimage.ubuntu.com/ubuntu- base/focal/daily/20220829.1/focal-base-riscv64.tar.gz mkdir base
[Touch-packages] [Bug 1988145] [NEW] Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key
Public bug reported: I tried to run http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results I downloaded http://cdimage.ubuntu.com/ubuntu- base/focal/daily/20220829.1/focal-base-riscv64.tar.gz mkdir base sudo tar -C base -zxf focal-base-riscv64.tar.gz sudo mount --bind /proc base/proc sudo mount --bind /sys base/sys sudo mount --bind /dev base/dev sudo mount --bind /dev/pts base/dev/pts sudo cp /etc/resolv.conf base/etc/ sudo chroot base apt-get update results in: Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Err:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key Reading package lists... Done W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal InRelease: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease: Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease: Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ports.ubuntu.com/ubuntu-ports focal-security InRelease: Couldn't create temporary file /tmp/apt.conf.L2I28d for passing config to apt-key E: The repository 'http://ports.ubuntu.com/ubuntu-ports focal-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. As touch /tmp/apt.conf.fsIutr works without issues there must be a bug in how apt creates temporary files. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1988145 Title: Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Status in apt package in Ubuntu: New Bug description: I tried to run http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results I downloaded http://cdimage.ubuntu.com/ubuntu- base/focal/daily/20220829.1/focal-base-riscv64.tar.gz mkdir base sudo tar -C base -zxf focal-base-riscv64.tar.gz sudo mount --bind /proc base/proc sudo mount --bind /sys base/sys sudo mount --bind /dev base/dev sudo mount --bind /dev/pts base/dev/pts sudo cp /etc/resolv.conf base/etc/ sudo chroot base apt-get update results in: Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB] Err:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease Couldn't create temporary file /tmp/apt.conf.fsIutr for passing config to apt-key Err:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease Couldn't create temporary file /tmp/apt.conf.x7LQrB for passing config to apt-key Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [108 kB] Err:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease Couldn't create temporary file /tmp/apt.conf.t2upW0 for passing config to apt-key Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [114 kB] Err:4
[Touch-packages] [Bug 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages
** Description changed: Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? + + This impacts all flavours as well that include nvidia stuff in their ISO + - so if the solution is to change the meta file for a revised regexp for + nvidia then all flavours that include nvidia will likewise need their + meta packages updated. -- 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/1988143 Title: 20.04.5 (20220829.1 build) has kernel 5.13 packages Status in ubuntu-meta package in Ubuntu: New Bug description: Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1988143/+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 1986984] Re: [FFe] tzdata 2022c update
This update has been prepared in the following PPA:
https://launchpad.net/~schopin/+archive/ubuntu/tzdata
The kinetic upload has been prepared as a full merge from Debian,
however I kept the other series' diff as small as possible by doing a
plain "upstream update". Notably, I didn't pick up the Debian changes
renaming Kiev to Kyiv in the older releases.
You'll note that the ICU data has only been updated 'til 2022b. That's
because they haven't picked up 2022c yet, and probably won't since that
last release is more of a bugfix release, with no data changes.
** Also affects: tzdata (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Also affects: tzdata (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: tzdata (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: tzdata (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: tzdata (Ubuntu Focal)
Status: New => Confirmed
** Changed in: tzdata (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Confirmed
Status in tzdata source package in Xenial:
Confirmed
Status in tzdata source package in Bionic:
Confirmed
Status in tzdata source package in Focal:
Confirmed
Status in tzdata source package in Jammy:
Confirmed
Status in tzdata source package in Kinetic:
Confirmed
Bug description:
New timezone data, with the following timezones impacted:
- Chile will spring forward on 2022-09-11, not 2022-09-04 (America/Santiago)
- Iran no longer observes DST (Asia/Tehran)
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v America/Santiago | grep 'Sep.*2022'
-> should indicate Sep 11, not Sep 4
2) zdump -v Asia/Tehran | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
The assertions would crash on 2022a.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
[Original report]
tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1986984/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Microsoft has created an incident for this. https://azure.status.microsoft/en-us/status reports: Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors - Investigating Starting at approximately 06:00 UTC on 30 Aug 2022, a number of customers running Ubuntu 18.04 (bionic) VMs recently upgraded to systemd version 237-3ubuntu10.54 reported experiencing DNS errors when trying to access their resources. Reports of this issue are confined to this single Ubuntu version. This bug and a potential fix have been highlighted on the Canonical / Ubuntu site, which we encourage impacted customers to read: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119 An additional potential workaround customers can consider is to reboot impacted VM instances so that they receive a fresh DHCP lease and new DNS resolver(s). Any Azure service, including AKS, that uses Canonical Ubuntu version 18.04 of Linux may have some impact from this issue. We are working on mitigations across Azure services that are impacted. More information will be provided within 60 minutes, when we expect to know more about the root cause and mitigation workstreams. This message was last updated at 09:20 UTC on 30 August 2022 -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
Seems to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938791 - same symptoms. [Workaround] Reboot the node, DNS should return back to normal. -- 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/1988119 Title: Update to systemd 237-3ubuntu10.54 broke dns Status in systemd package in Ubuntu: Confirmed Bug description: Two servers today that updated systemd to "systemd 237-3ubuntu10.54" https://ubuntu.com/security/notices/USN-5583-1 could not resolve dns anymore. no dns servers, normally set through dhcp. Ubuntu 18.04 Temp fix. 1. Edit /etc/systemd/resolved.conf 1. Add/Uncomment # FallbackDNS=168.63.129.16 1. Restart systemd-resolved sudo systemctl restart systemd-resolved.service 1. Confirm dns working with systemd-resolve google.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/+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 1988143] [NEW] 20.04.5 (20220829.1 build) has kernel 5.13 packages
Public bug reported: Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: focal iso-testing ** Tags added: iso-testing ** Description changed: Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. + + http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- + amd64.list + + e.g. + + /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb + /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb + /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb + /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb + /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? -- 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/1988143 Title: 20.04.5 (20220829.1 build) has kernel 5.13 packages Status in ubuntu-meta package in Ubuntu: New Bug description: Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1988143/+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 1938791] Re: [18.04] systemd-resolve does not update DNS servers
*** This bug is a duplicate of bug 1988119 *** https://bugs.launchpad.net/bugs/1988119 ** This bug has been marked a duplicate of bug 1988119 Update to systemd 237-3ubuntu10.54 broke dns -- 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/1938791 Title: [18.04] systemd-resolve does not update DNS servers Status in systemd package in Ubuntu: New Bug description: Hi, A number of my nodes were in a broken state resolving DNS on an unattended-upgrades enabled nodes, running dhclient and checking systemd-resolve --status shows the following: Link 2 (eth0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Compared to a working node: Link 2 (eth0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 145.218.226.65 145.218.238.29 DNS Domain: reddog.microsoft.com [Workaround] Reboot the node, DNS should return back to normal. sos report and additional information: https://private- fileshare.canonical.com/~pjds/dsv/dns-issue/ Thanks, Peter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938791/+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 1986984] Re: [FFe] tzdata 2022c update
** Summary changed:
- Availability of tzdata 2022c for Ubuntu 20.04
+ [FFe] tzdata 2022c update
** Description changed:
- tzdata 2022b and 2022c were just released that includes some timezone
- changes for Chile. According to the tzdata lib listed for Ubuntu 20.04,
- the latest package is 2022a. Any idea when 2022b or 2022c will be
- available? Chile made a change to the start of their daylight savings
- and pushed it from Sept 4th to the 11th, so we really need our servers
- updated before the 4th.
+ New timezone data, with the following timezones impacted:
+ - Chile will spring forward on 2022-09-11, not 2022-09-04 (America/Santiago)
+ - Iran no longer observes DST (Asia/Tehran)
+
+ Verification is done with 'zdump'. The first timezone that gets changed
+ in the updated package is dumped with 'zdump -v
+ $region/$timezone_that_changed' (this needs to be greped for in
+ /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
+ compared to the same output after the updated package got installed. If
+ those are different the verification is considered done.
+
+ [Test Case for all releases]
+ 1) zdump -v America/Santiago | grep 'Sep.*2022'
+ -> should indicate Sep 11, not Sep 4
+ 2) zdump -v Asia/Tehran | tail
+ -> last dates should be in 2022, not in 2499
+
+ [Test Case for releases >= 20.04 LTS]
+
+ For releases with ICU timezone data verification is done using the following
with dates before and after the change:
+ 1) sudo apt-get install python3-icu
+ 2) Run the following python script:
+
+ from datetime import datetime
+ from icu import ICUtzinfo, TimeZone
+ tz = ICUtzinfo(TimeZone.createTimeZone("America/Santiago"))
+ always_before = datetime(2022, 9, 1)
+ now_before = datetime(2022, 9, 8)
+ always_after = datetime(2022, 9, 12)
+ assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
+ assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
+
+ The assertions would crash on 2022a.
+
+ [Test Case for releases <= 20.04 LTS]
+
+ Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
+ diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
+
+ Nothing should be returned by the above command.
+
+ [Original report]
+ tzdata 2022b and 2022c were just released that includes some timezone changes
for Chile. According to the tzdata lib listed for Ubuntu 20.04, the latest
package is 2022a. Any idea when 2022b or 2022c will be available? Chile made a
change to the start of their daylight savings and pushed it from Sept 4th to
the 11th, so we really need our servers updated before the 4th.
Thanks
Jason
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Confirmed
Bug description:
New timezone data, with the following timezones impacted:
- Chile will spring forward on 2022-09-11, not 2022-09-04 (America/Santiago)
- Iran no longer observes DST (Asia/Tehran)
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v America/Santiago | grep 'Sep.*2022'
-> should indicate Sep 11, not Sep 4
2) zdump -v Asia/Tehran | tail
-> last dates should be in 2022, not in 2499
[Test Case for releases >= 20.04 LTS]
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
1) sudo apt-get install python3-icu
2) Run the following python script:
from datetime import datetime
from icu import ICUtzinfo, TimeZone
tz = ICUtzinfo(TimeZone.createTimeZone("America/Santiago"))
always_before = datetime(2022, 9, 1)
now_before = datetime(2022, 9, 8)
always_after = datetime(2022, 9, 12)
assert(tz.utcoffset(always_before) == tz.utcoffset(now_before))
assert(tz.utcoffset(now_before) != tz.utcoffset(always_after))
The assertions would crash on 2022a.
[Test Case for releases <= 20.04 LTS]
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and
earlier releases. Subsequently, these should be checked for using the following:
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
[Original report]
tzdata 2022b and 2022c were
[Touch-packages] [Bug 1987920] Re: indicator-datetime fails to build with default gcc (gcc-12)
It is released now, but we are looking into fixing build with gcc 12. And we are also looking into if we can port to ayatana this cycle. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1987920 Title: indicator-datetime fails to build with default gcc (gcc-12) Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-datetime source package in Kinetic: Confirmed Bug description: indicator-datetime fails to build from source in Kinetic with the default compiler, gcc/g++-12 To allow the package to build so that we can complete the evolution- data-server 3.45 transition, I switched the package to build with gcc/g++-11. I suggest switching to the Ayatana Indicators (ayatana-indicator- datetime) which are maintained and are able to build successfully with the default compiler. See https://launchpad.net/bugs/1983374 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1987920/+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 1988119] Re: Update to systemd 237-3ubuntu10.54 broke dns
We've just had the same problem, on multiple VMs running in Azure. In the dpkg log we can see that systemd was indeed updated (times in UTC): 2022-08-30 06:31:18 status unpacked udev:amd64 237-3ubuntu10.54 2022-08-30 06:31:18 status half-configured udev:amd64 237-3ubuntu10.54 2022-08-30 06:31:19 status installed udev:amd64 237-3ubuntu10.54 2022-08-30 06:31:19 status triggers-pending initramfs-tools:all 0.130ubuntu3.13 2022-08-30 06:31:19 trigproc man-db:amd64 2.8.3-2ubuntu0.1 2022-08-30 06:31:19 status half-configured man-db:amd64 2.8.3-2ubuntu0.1 2022-08-30 06:31:19 status installed man-db:amd64 2.8.3-2ubuntu0.1 2022-08-30 06:31:19 trigproc ureadahead:amd64 0.100.0-21 2022-08-30 06:31:19 status half-configured ureadahead:amd64 0.100.0-21 2022-08-30 06:31:20 status installed ureadahead:amd64 0.100.0-21 2022-08-30 06:31:20 trigproc libc-bin:amd64 2.27-3ubuntu1.5 2022-08-30 06:31:20 status half-configured libc-bin:amd64 2.27-3ubuntu1.5 2022-08-30 06:31:20 status installed libc-bin:amd64 2.27-3ubuntu1.5 2022-08-30 06:31:20 trigproc systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:20 status half-configured systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:20 status installed systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:20 trigproc initramfs-tools:all 0.130ubuntu3.13 2022-08-30 06:31:20 status half-configured initramfs-tools:all 0.130ubuntu3.13 2022-08-30 06:31:34 status installed initramfs-tools:all 0.130ubuntu3.13 2022-08-30 06:31:37 startup archives unpack 2022-08-30 06:31:38 upgrade libnss-systemd:amd64 237-3ubuntu10.53 237-3ubuntu10.54 2022-08-30 06:31:38 status triggers-pending libc-bin:amd64 2.27-3ubuntu1.5 2022-08-30 06:31:38 status half-configured libnss-systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status unpacked libnss-systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status half-installed libnss-systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status triggers-pending man-db:amd64 2.8.3-2ubuntu0.1 2022-08-30 06:31:38 status half-installed libnss-systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status unpacked libnss-systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:38 status unpacked libnss-systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:38 upgrade libpam-systemd:amd64 237-3ubuntu10.53 237-3ubuntu10.54 2022-08-30 06:31:38 status half-configured libpam-systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status unpacked libpam-systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status half-installed libpam-systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status half-installed libpam-systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status unpacked libpam-systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:38 status unpacked libpam-systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:38 upgrade systemd:amd64 237-3ubuntu10.53 237-3ubuntu10.54 2022-08-30 06:31:38 status half-configured systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status unpacked systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:38 status half-installed systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:39 status triggers-pending ureadahead:amd64 0.100.0-21 2022-08-30 06:31:39 status triggers-pending dbus:amd64 1.12.2-1ubuntu1.3 2022-08-30 06:31:39 status triggers-pending dbus:amd64 1.12.2-1ubuntu1.3 2022-08-30 06:31:39 status half-installed systemd:amd64 237-3ubuntu10.53 2022-08-30 06:31:39 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:39 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 upgrade libsystemd0:amd64 237-3ubuntu10.53 237-3ubuntu10.54 2022-08-30 06:31:40 status half-configured libsystemd0:amd64 237-3ubuntu10.53 2022-08-30 06:31:40 status unpacked libsystemd0:amd64 237-3ubuntu10.53 2022-08-30 06:31:40 status half-installed libsystemd0:amd64 237-3ubuntu10.53 2022-08-30 06:31:40 status half-installed libsystemd0:amd64 237-3ubuntu10.53 2022-08-30 06:31:40 status unpacked libsystemd0:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked libsystemd0:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 startup packages configure 2022-08-30 06:31:40 configure libsystemd0:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked libsystemd0:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status half-configured libsystemd0:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status installed libsystemd0:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 startup packages configure 2022-08-30 06:31:40 configure systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked systemd:amd64 237-3ubuntu10.54 2022-08-30 06:31:40 status unpacked systemd:amd64
[Touch-packages] [Bug 1938791] Re: [18.04] systemd-resolve does not update DNS servers
exact the same as described above happened today morning after an unattended update on Ubuntu 18.04 and 20.04 machines. `grep 'configure systemd:amd64 237-3ubuntu10.54' /var/log/dpkg.log` -- 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/1938791 Title: [18.04] systemd-resolve does not update DNS servers Status in systemd package in Ubuntu: New Bug description: Hi, A number of my nodes were in a broken state resolving DNS on an unattended-upgrades enabled nodes, running dhclient and checking systemd-resolve --status shows the following: Link 2 (eth0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Compared to a working node: Link 2 (eth0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 145.218.226.65 145.218.238.29 DNS Domain: reddog.microsoft.com [Workaround] Reboot the node, DNS should return back to normal. sos report and additional information: https://private- fileshare.canonical.com/~pjds/dsv/dns-issue/ Thanks, Peter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938791/+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 1897932] Re: systemd-repart not packaged
** Description changed: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd-repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. - * Attach build-logs showing the systemd-repart self-tests passing - * Attach autopkgtest logs showing the systemd-repart regression test passing + * Attach (local) build-log showing the systemd-repart self-tests passing + * Attach autopkgtest logs showing the regression tests passing (especially TEST-58-REPART) * Test upgrade-path Jammy->Kinetic to make sure systemd-repart is properly replaced by Kinetic's "systemd" binary package [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. Runtime behavior of existing components is not affected by the build config change. -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. * Attach (local) build-log showing the systemd-repart self-tests passing * Attach autopkgtest logs showing the regression tests passing (especially TEST-58-REPART) * Test upgrade-path Jammy->Kinetic to make sure systemd-repart is
[Touch-packages] [Bug 1897932] Re: systemd-repart not packaged
** Description changed: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd-repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. + * Attach build-logs showing the systemd-repart self-tests passing + * Attach autopkgtest logs showing the systemd-repart regression test passing + * Test upgrade-path Jammy->Kinetic to make sure systemd-repart is properly replaced by Kinetic's "systemd" binary package + [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service that runs on boot, it's configured to not do anything if no config files are shipped with the system or provided by the user. As such, the service, if enabled, will effectively be a noop. Aside from the service, there's the CLI tool systemd-repart and the accompanying man pages that will be shipped as part of the systemd package. Given that there's no risk involved with enabling systemd-repart, and given the useful features it provides, the systemd/mkosi developers would like to request that systemd-repart be enabled in Ubuntu and backported to Jammy so that they can start adopting it in mkosi. Runtime behavior of existing components is not affected by the build config change. -- 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/1897932 Title: systemd-repart not packaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Confirmed Status in systemd package in Debian: Fix Released Bug description: [Impact] systemd-repart is not (as of 246.6-1ubuntu1) packaged in the Ubuntu/Debian packages of systemd - probably because it has an extra dependency? The bug reporter would like to use it in their new raspberry pi images where they don't have cloud-init installed. The reporter is already using systemd-growfs, but they are missing the nice partition resizing part (so are using cloud-initramfs-growroot). Furthermore, in the mkosi image builder (https://github.com/systemd/mkosi), the systemd/mkosi developers would like to start using systemd-repart for partitioning. Unfortunately, they're currently blocked on this because 22.04 doesn't ship systemd- repart. The upstream CI uses Github Actions which runs on Ubuntu Jammy and will do so until the next Ubuntu LTS is released. If we have to wait for the next LTS to be released, we'll have to wait for a considerable amount of time before we're able to start using systemd- repart. Being able to use systemd-repart will allow the systemd/mkosi developers to take advantage of its improved interface compared to sfdisk, as well as its builtin protections against race conditions surrounding the use of loop devices. The systemd/mkosi developers expect to be able to get rid of some nasty loop device failure in mkosi by using systemd-repart. [Test Plan] This is a missing extra executable. Once enabled it has self-tests in the build-time unit tests, and also a regression test in the autopkgtest 'upstream' suite. * Attach build-logs showing the systemd-repart self-tests passing * Attach autopkgtest logs showing the systemd-repart regression test passing * Test upgrade-path Jammy->Kinetic to make sure systemd-repart is properly replaced by Kinetic's "systemd" binary package [Where problems could occur] Shipping systemd-repart will come with no additional risk. While there is a systemd-repart.service
