[Touch-packages] [Bug 2037703] Re: dpkg-reconfigure openssh-server doesn't ask questions again
Ok. Thanks for clarification. With that I think we can continue to get https://code.launchpad.net/~toabctl/livecd-rootfs/+git/livecd- rootfs-1/+merge/452352 merged. But I still find this behavior confusing/buggy. I can still use "debconf-show openssh-server" and see the password-authentication entry. And that entry is out-of-sync with the real configuration. That's a bug imo given that the behavior is not documented in README.Debian.gz . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2037703 Title: dpkg-reconfigure openssh-server doesn't ask questions again Status in openssh package in Ubuntu: New Bug description: openssh-server does provide a couple of configuration options: [~]$ sudo debconf-get-selections |grep openssh-server openssh-serveropenssh-server/listenstream-may-failerror openssh-serveropenssh-server/password-authentication boolean true openssh-serveropenssh-server/permit-root-loginboolean true I want to change those options now interactively but nothing I tried worked and showed a dialog: [~]$ sudo dpkg-reconfigure -p low openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. But the documentation (https://manpages.debian.org/testing/debconf- doc/debconf.7.en.html#Reconfiguring_packages) does state that those commands should ask those questions again. p.s. also tried with a lxc debian-sid container and had the same problem there. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.3p1-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 10:35:33 2023 InstallationDate: Installed on 2023-05-10 (142 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2037703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037703] Re: dpkg-reconfigure openssh-server doesn't ask questions again
looks like there's no db_input/db_go call in the openssh-server.config file. Is that by intention? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2037703 Title: dpkg-reconfigure openssh-server doesn't ask questions again Status in openssh package in Ubuntu: New Bug description: openssh-server does provide a couple of configuration options: [~]$ sudo debconf-get-selections |grep openssh-server openssh-serveropenssh-server/listenstream-may-failerror openssh-serveropenssh-server/password-authentication boolean true openssh-serveropenssh-server/permit-root-loginboolean true I want to change those options now interactively but nothing I tried worked and showed a dialog: [~]$ sudo dpkg-reconfigure -p low openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. But the documentation (https://manpages.debian.org/testing/debconf- doc/debconf.7.en.html#Reconfiguring_packages) does state that those commands should ask those questions again. p.s. also tried with a lxc debian-sid container and had the same problem there. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.3p1-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 10:35:33 2023 InstallationDate: Installed on 2023-05-10 (142 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2037703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037703] [NEW] dpkg-reconfigure openssh-server doesn't ask questions again
Public bug reported: openssh-server does provide a couple of configuration options: [~]$ sudo debconf-get-selections |grep openssh-server openssh-server openssh-server/listenstream-may-failerror openssh-server openssh-server/password-authentication boolean true openssh-server openssh-server/permit-root-loginboolean true I want to change those options now interactively but nothing I tried worked and showed a dialog: [~]$ sudo dpkg-reconfigure -p low openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. But the documentation (https://manpages.debian.org/testing/debconf- doc/debconf.7.en.html#Reconfiguring_packages) does state that those commands should ask those questions again. p.s. also tried with a lxc debian-sid container and had the same problem there. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.3p1-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 10:35:33 2023 InstallationDate: Installed on 2023-05-10 (142 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2037703 Title: dpkg-reconfigure openssh-server doesn't ask questions again Status in openssh package in Ubuntu: New Bug description: openssh-server does provide a couple of configuration options: [~]$ sudo debconf-get-selections |grep openssh-server openssh-serveropenssh-server/listenstream-may-failerror openssh-serveropenssh-server/password-authentication boolean true openssh-serveropenssh-server/permit-root-loginboolean true I want to change those options now interactively but nothing I tried worked and showed a dialog: [~]$ sudo dpkg-reconfigure -p low openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. [~]$ sudo dpkg-reconfigure -p low --force --frontend dialog openssh-server Warning: Stopping ssh.service, but it can still be activated by: ssh.socket rescue-ssh.target is a disabled or a static unit not running, not starting it. But the documentation (https://manpages.debian.org/testing/debconf- doc/debconf.7.en.html#Reconfiguring_packages) does state that those commands should ask those questions again. p.s. also tried with a lxc debian-sid container and had the same problem there. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: openssh-server 1:9.3p1-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 10:35:33 2023 InstallationDate: Installed on 2023-05-10 (142 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: openssh UpgradeStatus: Upgraded to mantic on 2023-07-19 (71 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2037703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988523] Re: Cannot install tomcat9 on ubuntu:18.04
This is not a systemd or tomcat bug. As I explained in https://bugs.launchpad.net/cloud-images/+bug/1988498 , a broken systemd package got removed from the archive but the broken version got included into the docker image. We'll release a new docker image soon to fix the problem. Let's track that in https://bugs.launchpad.net/cloud-images/+bug/1988498 and close this bug here. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: tomcat9 (Ubuntu) Status: Confirmed => Invalid -- 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/1988523 Title: Cannot install tomcat9 on ubuntu:18.04 Status in systemd package in Ubuntu: Invalid Status in tomcat9 package in Ubuntu: Invalid Bug description: ### Steps to reproduce 1. `docker pull docker.io/library/ubuntu:18.04` 2. `docker run --pull --rm -it docker.io/library/ubuntu:18.04 bash` 2. Inside the docker container: ```bash apt-get update apt-get install -y tomcat9 ``` ### Expected result * `tomcat9` is installed successfully ### Actual result * Installation fails with unresolvable dependencies: ```bash root@c9849e6844d0:/# apt-get install -y tomcat9 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: tomcat9 : Depends: systemd (>= 215) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` Attempting to install systemd results in the following: ```bash root@c9849e6844d0:/etc/apt# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: systemd : Depends: libsystemd0 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed Recommends: libpam-systemd but it is not going to be installed Recommends: dbus but it is not going to be installed Recommends: networkd-dispatcher but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` ### Workaround * Installing tomcat9 works if you downgrade libsystemd: ```bash apt-get install -y --allow-downgrades tomcat9 libsystemd0=237-3ubuntu10.53 ``` ### Other info * Reproduced using docker image `docker.io/library/ubuntu:18.04`, digest: `sha256:138ddf6a0815d0db123be28790ef1cc5691de06fe7d9951953e2011fd0761685` * Pulled from docker.io/library/ubuntu Fri Sep 2 07:57:03 UTC 2022 I suspect this is caused by an issue in systemd having no version available that matches the latest libsystemd0, so I've included the `apt-cache policy` of systemd and libsystemd0 too. ```bash root@2d05688650c0:/# lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 ``` ``` root@2d05688650c0:/# apt-cache policy tomcat9 tomcat9: Installed: (none) Candidate: 9.0.16-3ubuntu0.18.04.2 Version table: 9.0.16-3ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages root@2d05688650c0:/# apt-cache policy systemd systemd: Installed: (none) Candidate: 237-3ubuntu10.53 Version table: 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@2d05688650c0:/# apt-cache policy libsystemd0 libsystemd0: Installed: 237-3ubuntu10.54 Candidate: 237-3ubuntu10.54 Version table: *** 237-3ubuntu10.54 100 100 /var/lib/dpkg/status 237-3ubuntu10.53 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.50 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 18.04
[Touch-packages] [Bug 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
SRU verification for hirsute: I did a testbuild with repo-stamp enabled against the livecd-rootfs version from proposed (2.719.3). See - https://launchpad.net/~toabctl/+livefs/ubuntu/hirsute/proposed/+build/308173 - https://launchpadlibrarian.net/567803112/buildlog_ubuntu_hirsute_amd64_amd64-tarball_proposed_BUILDING.txt.gz That looks good. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in iptables source package in Bionic: Invalid Status in livecd-rootfs source package in Bionic: Invalid Status in lxd source package in Bionic: Invalid Status in iptables source package in Focal: Invalid Status in livecd-rootfs source package in Focal: Fix Released Status in lxd source package in Focal: Invalid Status in iptables source package in Hirsute: Invalid Status in livecd-rootfs source package in Hirsute: Fix Committed Status in lxd source package in Hirsute: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
I did a testbuild with repo-stamp enabled against the livecd-rootfs version from proposed (2.664.33). See - https://launchpadlibrarian.net/566970666/buildlog_ubuntu_focal_amd64_amd64-tarball_proposed_BUILDING.txt.gz - https://launchpad.net/~toabctl/+livefs/ubuntu/focal/proposed/+build/307101 That looks good. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in iptables source package in Bionic: Invalid Status in livecd-rootfs source package in Bionic: Invalid Status in lxd source package in Bionic: Invalid Status in iptables source package in Focal: Invalid Status in livecd-rootfs source package in Focal: Fix Committed Status in lxd source package in Focal: Invalid Status in iptables source package in Hirsute: Invalid Status in livecd-rootfs source package in Hirsute: New Status in lxd source package in Hirsute: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
Bionic is not affected ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in iptables source package in Bionic: Invalid Status in livecd-rootfs source package in Bionic: Invalid Status in lxd source package in Bionic: Invalid Status in iptables source package in Focal: Invalid Status in livecd-rootfs source package in Focal: Fix Committed Status in lxd source package in Focal: Invalid Status in iptables source package in Hirsute: Invalid Status in livecd-rootfs source package in Hirsute: New Status in lxd source package in Hirsute: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
** Changed in: livecd-rootfs (Ubuntu Hirsute) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Focal) Assignee: (unassigned) => Thomas Bechtold (toabctl) ** Changed in: livecd-rootfs (Ubuntu Bionic) Assignee: (unassigned) => Thomas Bechtold (toabctl) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Status in iptables source package in Bionic: Invalid Status in livecd-rootfs source package in Bionic: New Status in lxd source package in Bionic: Invalid Status in iptables source package in Focal: Invalid Status in livecd-rootfs source package in Focal: New Status in lxd source package in Focal: Invalid Status in iptables source package in Hirsute: Invalid Status in livecd-rootfs source package in Hirsute: New Status in lxd source package in Hirsute: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
** Description changed: - [Why SRU?] + [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. - [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Bug description: [Impact] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1917920] Re: magic-proxy broke with iptables 1.8.7-1ubuntu2
** Description changed: + [Why SRU?] + The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). + + [Test Plan] + - build a livecd-rootfs image with the changes for every series in a PPA + - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature + - Check that the build did not fail or hang + + [Where problems could occur] + The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. + + + [Original description] + when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1917920 Title: magic-proxy broke with iptables 1.8.7-1ubuntu2 Status in launchpad-buildd: Invalid Status in iptables package in Ubuntu: Invalid Status in livecd-rootfs package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Bug description: [Why SRU?] The fixes for this bug (including the fixes for LP:#1944906) need to be backported to hirsute, focal and bionic) to be able to re-enable the "repo-snapshot-stamp" feature for image builds. That feature is important to get consistent image builds (means the same set of packages included in the different images) when doing multiple builds (eg. for AWS, Azure and GCE). [Test Plan] - build a livecd-rootfs image with the changes for every series in a PPA - Do build an image with the livecd-rootfs from the PPA and enable the repo-snapshot-stamp feature - Check that the build did not fail or hang [Where problems could occur] The codepath that will be changed is only executed in livecd-rootfs if the repo-snapshot-stamp feature is enabled. And that feature is currently broken so it shouldn't be enabled anywhere. [Original description] when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic proxy stopped working in livecd-rootfs. It does very simple thing: iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 inside hirsute lxd container, with quite high privileges, in a bionic VM, running 4.15 kernel. With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound connectivity the very first http networking command after the above call would just hang indefinitely. However, if one does this instead: iptables -vv -t nat -S iptables-legacy -vv -t nat -S iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon -j REDIRECT --to 8080 somehow magically everything starts to work fine. weird. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+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 1923542] [NEW] "Failed to restart network-manager.service: Unit network-manager.service not found." during package update
Public bug reported: I updated network-manger on hirsute: network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over (1.30.0-1ubuntu2) During the postinst run, I get: Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ... Failed to restart network-manager.service: Unit network-manager.service not found. invoke-rc.d: initscript network-manager, action "force-reload" failed. The reason seems to be that there is no network-manager.service . it's called NetworkManager.service . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 13 06:15:31 2021 InstallationDate: Installed on 2020-12-08 (125 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: network-manager SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2020-12-09 (124 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1923542 Title: "Failed to restart network-manager.service: Unit network- manager.service not found." during package update Status in network-manager package in Ubuntu: New Bug description: I updated network-manger on hirsute: network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over (1.30.0-1ubuntu2) During the postinst run, I get: Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ... Failed to restart network-manager.service: Unit network-manager.service not found. invoke-rc.d: initscript network-manager, action "force-reload" failed. The reason seems to be that there is no network-manager.service . it's called NetworkManager.service . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 13 06:15:31 2021 InstallationDate: Installed on 2020-12-08 (125 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: network-manager SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2020-12-09 (124 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1923542/+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 1923541] [NEW] /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'
Public bug reported: Currently running 21.04, apport version is 2.20.11-0ubuntu62 . When I try to fill a bug, I see: $ ubuntu-bug network-manager ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1002, in attach_casper_md5check del report['CasperMD5json'] File "/usr/lib/python3.9/collections/__init__.py", line 1064, in __delitem__ del self.data[key] KeyError: 'CasperMD5json' It's not crashing the bug reporting itself, but it looks wrong to have a stacktrace on the command line. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1923541 Title: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json' Status in apport package in Ubuntu: New Bug description: Currently running 21.04, apport version is 2.20.11-0ubuntu62 . When I try to fill a bug, I see: $ ubuntu-bug network-manager ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/ubuntu.py", line 84, in add_info apport.hookutils.attach_casper_md5check(report, File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1002, in attach_casper_md5check del report['CasperMD5json'] File "/usr/lib/python3.9/collections/__init__.py", line 1064, in __delitem__ del self.data[key] KeyError: 'CasperMD5json' It's not crashing the bug reporting itself, but it looks wrong to have a stacktrace on the command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1923541/+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 1915579] Re: lvm2 version 2.03.11-2ubuntu1 breaks initramfs
I also have this problem (with a LUKS & LVM). As a workaround, I did: 1) boot into live CD, start a terminal and do everything as root (sudo -i) 2) open the encrypted LUKS partition: cryptsetup luksOpen /dev/nvme0n1p3 nvme0n1p3_crypt Note that the name (in my case "nvme0n1p3_crypt") must match the name that is in the etc/crypttab . Otherwise the later generated initramfs will not work correctly. 3) vgscan && vgchange -ay vgubuntu 4) mount /dev/vgubuntu/root /mnt 5) mount /dev/nvme0n1p2 /mnt/boot# this is my /boot partition 6) mount --bind /dev /mnt/dev && mount --bind /sys /mnt/sys && mount --bind /proc /mnt/proc 7) chroot /mnt 8) chmod 755 /usr/share/initramfs-tools/hooks/lvm2 9) update-initramfs -u -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1915579 Title: lvm2 version 2.03.11-2ubuntu1 breaks initramfs Status in lvm2 package in Ubuntu: Triaged Bug description: I upgraded lvm2 from 2.03.07-1ubuntu4 to 2.03.11-2ubuntu1 and my initramfs broke. I had to manually rollback to the old version to be able to boot. The error was something like: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/vgubuntu-root does not exist. Dropping to a shell! And there was no neither my lvm lvs, nor lvm binary on initramfs. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lvm2 2.03.07-1ubuntu4 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 13 02:42:08 2021 InstallationDate: Installed on 2019-11-01 (469 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1915579/+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
