[Touch-packages] [Bug 1929647] Re: debian helper tools for python never updates
not working ** Attachment added: "software updater fails Peek 2021-06-08 09-27.gif" https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+attachment/5503022/+files/software%20updater%20fails%20Peek%202021-06-08%2009-27.gif -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1929647 Title: debian helper tools for python never updates Status in python-debian package in Ubuntu: New Bug description: software updater prompts new updates debian helper tools for python is always one of them but I cannot select the checkbox so debian helper tools for python never updates Here's the screen shot https://i.imgur.com/AjDd5yo.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1929647/+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 1931178] Re: apt-key fails when POSIXLY_CORRECT environmental variable is set
Is this a regression from an older release? We can fix it, but if it's not a regression, I'd just skip it, as running apt-key is the wrong approach anyway. They should just pmrum cp some-repo-key.gpg /etc/apt/trusted.gpg.d. optimally drop the keyring elsewhere and use signed-by in sources.list snippet, but oh well, it does not add much security really. -- 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/1931178 Title: apt-key fails when POSIXLY_CORRECT environmental variable is set Status in apt package in Ubuntu: New Bug description: apt-key fails when the POSIXLY_CORRECT environmental variable is set. This is due to chmod acting differently with POSIXLY_CORRECT set: chmod tries to use `--` as a parameter with this variable. This prevents some third-party utilities, like pmrun, from using apt- key. --- chmod with POSIXLY_CORRECT unset succeeds with the following commands: ``` touch testfile chmod 0644 -- testfile echo $? ``` The final command prints "0". (This is what the apt-key script expects to happen.) --- chmod with POSIXLY_CORRECT set fails with the following commands: ``` export POSIXLY_CORRECT= touch testfile chmod 0644 -- testfile echo $? ``` The final two commands print these two lines, respectively: """ chmod: cannot access '--': No such file or directory 1 """ (This is unexpected for the apt-key script.) --- As such, when a third party utility that sets the POSIXLY_CORRECT environmental variable, like pmrun, tries to run apt-key, it will fail. Example use similar to what the reporting customer tried: `cat some-repo-key.gpg | pmrun apt-key add -` The chmod examples are run on an up-to-date Bionic container, /usr/bin/apt-key has `chmod -- path` commands at line 338 and line 499: GNU coreutils package version 8.28-1ubuntu1 apt package version 1.6.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1931178/+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 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
There is another fix in master that belongs to https://bugzilla.mozilla.org/show_bug.cgi?id=1566124 - I've bumped my PPA build to include both as it is worth a try if this fixes the current ppc64 issues in v3.66. Build of 3.66-1ubuntu1~impishppa2 started, later on I'll let the autopkgtests run. ** Bug watch added: Mozilla Bugzilla #1566124 https://bugzilla.mozilla.org/show_bug.cgi?id=1566124 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1931104 Title: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish- proposed Status in nss package in Ubuntu: New Bug description: The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed. Example: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz Bad: Installing CA into /var/lib/pki/pki-tomcat. Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 995, in spawn cert = deployer.setup_cert(client, tag) File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py", line 355, in setup_cert return client.setupCert(request) File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert response = self.connection.post( File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper return func(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post r = self.session.post( File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in post return self.request('POST', url, data=data, json=json, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) CA spawn failed: Good: nstalling CA into /var/lib/pki/pki-tomcat. Notice: Trust flag u is set automatically if the private key is present. /usr/lib/python3/dist-packages/urllib3/connection.py:455: SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/urllib3/urllib3/issues/497 for details.) warnings.warn( == INSTALLATION SUMMARY == ... The good test above was with: ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security Service libraries ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite - server Worth to know, the good case test still fails later on with: IOException: SocketException cannot write on socket: Failed to write to socket: (-5938) Encountered end of file. ERROR: CalledProcessError: Command '['pki', '-d', '/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U', 'https://i-dogtag:8443', 'securitydomain-join', '--session', '4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag', '--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']' returned non-zero exit status 255. File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 1038, in spawn subsystem.join_security_domain( File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201, in join_security_domain subprocess.check_call(cmd) File "/usr/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f /etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join --session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port 8080 --secure-port 8443 TKS i-dogtag 8443 Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log Well one issue at a time ... the current install issue first. Since it worked with the nss in -release I was
[Touch-packages] [Bug 1931018] Re: Keyboard layout switch freezes
I'm guessing this is related to bug 108, even if you only have one keyboard. It sounds related. ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: i18n -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1931018 Title: Keyboard layout switch freezes Status in mutter package in Ubuntu: New Bug description: Hi! I have problem with slow keyboard layout switching between Russian and English layouts. In ubuntu 16.04-20.04 :) gsettings get org.gnome.desktop.wm.keybindings switch-input-source ['XF86Keyboard'] But in gnome-tweak-tool I set as key for layout switching caps-lock. It is work, but when I switch from en to ru, fast, and when ru to en, I have delay ~1s. And in gnome-tweak-tool I see caps-lock as keyboard key for switching, and in gsettings is XF86Keyboard or some time ago super+space. When I try to set in gsettings some other keys (as super+space), they worked fast, but in gnome-tweak-tool caps-lock work slooow. And all this keys work in one time, this is strange. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.12.0-8.5-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jun 6 15:58:43 2021 DistUpgraded: 2020-12-05 22:39:51,673 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить процесс-потомок «./xorg_fix_proprietary.py» (Нет такого файла или каталога) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18.1-liquorix-amd64, x86_64: installed nvidia, 460.80, 5.12.0-8.5-liquorix-amd64, x86_64: installed nvidia, 460.80, 5.12.0-9.2-liquorix-amd64, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 3rd Gen Core processor Graphics Controller [1558:2701] NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2018-06-28 (1073 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: CLEVO CO. W250ENQ / W270ENQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: audit=0 intel_pstate=disable BOOT_IMAGE=/boot/vmlinuz-5.12.0-8.5-liquorix-amd64 root=UUID=3f1a1990-8bad-49d1-970e-87308d8cd521 ro quiet splash nouveau.runpm=0 zswap.enabled=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-05 (182 days ago) dmi.bios.date: 04/03/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W250ENQ / W270ENQ dmi.board.vendor: CLEVO CO. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/03/2012:br4.6:svnCLEVOCO.:pnW250ENQ/W270ENQ:pvrNotApplicable:rvnCLEVOCO.:rnW250ENQ/W270ENQ:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W250ENQ / W270ENQ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-06-08T10:33:29.519300 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nv
[Touch-packages] [Bug 1930976] Re: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1930976 Title: 5.8.0-55 kernel issue with RTX 3080 on Nvidia drivers Status in linux-hwe-5.8 package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Kernel: 5.8.0-55 The last kernel destroyed my Ubuntu 20.04.02 installation, something went wrong with some kernel packages. It seems like Ubuntu is unable to find my video card correctly and the device drivers from Nvidia don't seem to work anymore. I had to do a clean installation, but even that doesn't solve the problem. I think this is a serious issue that needs to be looked into. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Sat Jun 5 16:50:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation Device [10de:2206] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:403f] InstallationDate: Installed on 2021-06-05 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=4984fe2f-d45f-4734-884c-2426bcf10ca4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33j dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33j:bd04/23/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1930976/+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 1930903] Re: Frequent kernel oops related to nvidia / nv_drm_master_set
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1930903 Title: Frequent kernel oops related to nvidia / nv_drm_master_set Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: After upgrading yesterday from ubuntu 20 to 21.04 my machine now exhibits frequent involuntary restarts, related to a kernel oops of the form Jun 3 10:48:32 zotac kernel: [ 20.464926] RIP: 0010:nv_drm_master_set+0x27/0x30 [nvidia_drm] [...] Jun 3 10:48:32 zotac kernel: [ 20.464958] Call Trace: Jun 3 10:48:32 zotac kernel: [ 20.464964] drm_new_set_master+0x7e/0x100 [drm] Jun 3 10:48:32 zotac kernel: [ 20.464994] drm_master_open+0x6e/0xa0 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465017] drm_open+0xf8/0x250 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465044] drm_stub_open+0xba/0x140 [drm] Jun 3 10:48:32 zotac kernel: [ 20.465070] chrdev_open+0xf7/0x220 Jun 3 10:48:32 zotac kernel: [ 20.465075] ? cdev_device_add+0x90/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465078] do_dentry_open+0x156/0x370 Jun 3 10:48:32 zotac kernel: [ 20.465081] vfs_open+0x2d/0x30 Jun 3 10:48:32 zotac kernel: [ 20.465084] do_open+0x1c3/0x340 Jun 3 10:48:32 zotac kernel: [ 20.465087] path_openat+0x10a/0x1d0 Jun 3 10:48:32 zotac kernel: [ 20.465090] do_filp_open+0x8c/0x130 Jun 3 10:48:32 zotac kernel: [ 20.465093] ? __check_object_size+0x1c/0x20 Jun 3 10:48:32 zotac kernel: [ 20.465096] do_sys_openat2+0x9b/0x150 Jun 3 10:48:32 zotac kernel: [ 20.465099] __x64_sys_openat+0x56/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465102] do_syscall_64+0x38/0x90 Jun 3 10:48:32 zotac kernel: [ 20.465105] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 3 10:48:32 zotac kernel: [ 20.465108] RIP: 0033:0x7fe6ea270954 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jun 4 17:00:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-05-09 (391 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: NA ZBOX-ER51070 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=4e73512b-1846-4fe4-87d1-079bbaae2a1a ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: ZBOX-ER51070 dmi.board.vendor: NA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/25/2019:br5.12:svnNA:pnZBOX-ER51070:pvrDefaultstring:rvnNA:rnZBOX-ER51070:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZBOX-ER51070 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: NA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xor
[Touch-packages] [Bug 1930925] Re: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM
** Summary changed: - Ubuntu 20.04 doesn't work with moidern KVMs + Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: kvm ** Summary changed: - Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM + Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1930925 Title: Ubuntu 20.04 doesn't work with Logitech, Inc. Unifying Receiver over a KVM switch Status in linux package in Ubuntu: New Bug description: I have recently acquired a acquired a desktop running ubuntu 20.04. I have several computers and switch between them using this KVM https://www.amazon.co.uk/gp/product/B077SV9MMQ/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1 The other machines are either running windows or ubuntu 18.04 or earlier. They are all fine, but the with 20.04 machine neither the keyboard nor the mouse works. On the 18.04 machine I can see lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub and it is the Logitech, Inc. Unifying Receiver which appears when the USB from the KVM is connected. On the 20.04 machine only this appears lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have tested installation discs from 19.04 onwards. The failure first appears in 19.10 and is still present in 21.04 I can observe a similar problem with a dual boot laptop running windows 10 and 20.04. With windows 10 I can use it with the KVM for screen and keyboard/mouse, but with ubuntu 20.04 the keyboard and mouse do not work. This issue has also been observed here https://unix.stackexchange.com/questions/646515/using-logitech-mouse- keyboard-on-tesmart-kvm-switch-with-ubuntu-20-04 and I have observed it using a Lindy 2 port HDMI/USB KVM (but I'm unsure of the model). I had to report this originally against xorg as this bug reporting system seems not to allow reporting of bugs against unknown packages. I also had to report it through the ubuntu-bug executable as I've been unable to find a way in launchpad of reporting a bug (as opposed to getting a guided tour about reporting bugs). I am happy to supply more info and test fixes if I am asked but as with this type of bug where something fails to happen rather than something wrong happens I don't know what to look at. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jun 4 20:21:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-05-14 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 13: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 13: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=0c391c11-c570-4e04-a351-4fd128a75369 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2021 dmi.bios.release: 8.20 dmi.bios.vendor: American Megatrends I
[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
I was able to verify that a merge of 3.66 would on Ubuntu trigger the very same bug that Debian has blocking the dogtag-pki test on powerpc64. => https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train- ppa-service-4577/impish/ppc64el/d/dogtag- pki/20210608_031158_a9d4a@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1931104 Title: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish- proposed Status in nss package in Ubuntu: New Bug description: The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed. Example: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz Bad: Installing CA into /var/lib/pki/pki-tomcat. Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 995, in spawn cert = deployer.setup_cert(client, tag) File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py", line 355, in setup_cert return client.setupCert(request) File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert response = self.connection.post( File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper return func(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post r = self.session.post( File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in post return self.request('POST', url, data=data, json=json, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) CA spawn failed: Good: nstalling CA into /var/lib/pki/pki-tomcat. Notice: Trust flag u is set automatically if the private key is present. /usr/lib/python3/dist-packages/urllib3/connection.py:455: SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/urllib3/urllib3/issues/497 for details.) warnings.warn( == INSTALLATION SUMMARY == ... The good test above was with: ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security Service libraries ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite - server Worth to know, the good case test still fails later on with: IOException: SocketException cannot write on socket: Failed to write to socket: (-5938) Encountered end of file. ERROR: CalledProcessError: Command '['pki', '-d', '/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U', 'https://i-dogtag:8443', 'securitydomain-join', '--session', '4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag', '--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']' returned non-zero exit status 255. File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 1038, in spawn subsystem.join_security_domain( File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201, in join_security_domain subprocess.check_call(cmd) File "/usr/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f /etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join --session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port 8080 --secure-port 8443 TKS i-dogtag 8443 Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log Well one issue at a time ... the current install issue first. Since it worked with the nss in -release I was upgrading this to the new nss. ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite -
[Touch-packages] [Bug 1931178] [NEW] apt-key fails when POSIXLY_CORRECT environmental variable is set
Public bug reported: apt-key fails when the POSIXLY_CORRECT environmental variable is set. This is due to chmod acting differently with POSIXLY_CORRECT set: chmod tries to use `--` as a parameter with this variable. This prevents some third-party utilities, like pmrun, from using apt- key. --- chmod with POSIXLY_CORRECT unset succeeds with the following commands: ``` touch testfile chmod 0644 -- testfile echo $? ``` The final command prints "0". (This is what the apt-key script expects to happen.) --- chmod with POSIXLY_CORRECT set fails with the following commands: ``` export POSIXLY_CORRECT= touch testfile chmod 0644 -- testfile echo $? ``` The final two commands print these two lines, respectively: """ chmod: cannot access '--': No such file or directory 1 """ (This is unexpected for the apt-key script.) --- As such, when a third party utility that sets the POSIXLY_CORRECT environmental variable, like pmrun, tries to run apt-key, it will fail. Example use similar to what the reporting customer tried: `cat some-repo-key.gpg | pmrun apt-key add -` The chmod examples are run on an up-to-date Bionic container, /usr/bin/apt-key has `chmod -- path` commands at line 338 and line 499: GNU coreutils package version 8.28-1ubuntu1 apt package version 1.6.13 ** 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/1931178 Title: apt-key fails when POSIXLY_CORRECT environmental variable is set Status in apt package in Ubuntu: New Bug description: apt-key fails when the POSIXLY_CORRECT environmental variable is set. This is due to chmod acting differently with POSIXLY_CORRECT set: chmod tries to use `--` as a parameter with this variable. This prevents some third-party utilities, like pmrun, from using apt- key. --- chmod with POSIXLY_CORRECT unset succeeds with the following commands: ``` touch testfile chmod 0644 -- testfile echo $? ``` The final command prints "0". (This is what the apt-key script expects to happen.) --- chmod with POSIXLY_CORRECT set fails with the following commands: ``` export POSIXLY_CORRECT= touch testfile chmod 0644 -- testfile echo $? ``` The final two commands print these two lines, respectively: """ chmod: cannot access '--': No such file or directory 1 """ (This is unexpected for the apt-key script.) --- As such, when a third party utility that sets the POSIXLY_CORRECT environmental variable, like pmrun, tries to run apt-key, it will fail. Example use similar to what the reporting customer tried: `cat some-repo-key.gpg | pmrun apt-key add -` The chmod examples are run on an up-to-date Bionic container, /usr/bin/apt-key has `chmod -- path` commands at line 338 and line 499: GNU coreutils package version 8.28-1ubuntu1 apt package version 1.6.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1931178/+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 1931077] Re: emergency shell ignores all keyboard input
Ideally, I'd wish it not to stop sshd when /boot/efi becomes unavailable. Or at least bring back the services it stopped when the emergency shell is canceled. More practically, and more on topic to the original reason for this bug report, I'd like it if stopping the emergency shell would print a message on the console, so the instructions to press Enter or Ctrl-D do not appear to still be relevant. -- 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/1931077 Title: emergency shell ignores all keyboard input Status in systemd package in Ubuntu: Incomplete Bug description: An SSD that held my /boot/efi partition failed, took down local-fs.target, which brought up emergency.target. I ended up with no ssh access, and a message on the local console telling me to press Enter to get a root shell, or press Ctrl-D to continue booting normally. The system did not react to either Enter or Ctrl-D. I could switch between virtual consoles (but nothing was running on them, e.g. no getty), toggle Caps Lock, or reboot with Ctrl+Alt+Del. An emergency console that doesn't accept keyboard input is not a useful emergency console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.47 ProcVersionSignature: Ubuntu 4.15.0-144.148-generic 4.15.18 Uname: Linux 4.15.0-144-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Mon Jun 7 11:18:39 2021 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-144-generic root=/dev/mapper/hostname-root ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2019-08-12 (664 days ago) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931077/+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 1930917] Re: Latest isc-dhcp-server rejects proper dhcpd.conf
Thanks for reporting the issue! -- 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/1930917 Title: Latest isc-dhcp-server rejects proper dhcpd.conf Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Hirsute: Fix Released Status in isc-dhcp source package in Impish: Confirmed Bug description: Ubuntu 21.04 on Raspberry Pi. isc-dhcp-server was working just fine with version V4.4.1-2.2-ubuntu6. I got updated to V4.4.1-2.2ubuntu6.1 and now isc-dhcp-server refuses to start with the error "Can't clone pool group". I backed off to the prior version and it's working as before, so something in the V4.4.1-2.2ubuntu6.1 update has broken config file parsing. Here's the subnet section of the failing config. Removing the "pool" declaration from the subnet declaration eliminates the error, but of course, that's not a working configuration. subnet 192.168.92.0 netmask 255.255.255.0 { option domain-search "foo.com", "dyn.foo.com"; option broadcast-address 192.168.92.255; allow duplicates; ddns-updates off; pool { ddns-updates on; allow unknown-clients; option domain-name "dyn.foo.com"; ddns-rev-domainname "dhcp"; default-lease-time 86400; max-lease-time 86400; range 192.168.92.101 192.168.92.127; } } This was also noted at least twice in the Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2462984 and https://ubuntuforums.org/showthread.php?t=2462930 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1930917/+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 1930917] Re: Latest isc-dhcp-server rejects proper dhcpd.conf
Tested and confirmed that 4.4.1-2.2ubuntu6.2 corrects this. Thank you! -- 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/1930917 Title: Latest isc-dhcp-server rejects proper dhcpd.conf Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Hirsute: Fix Released Status in isc-dhcp source package in Impish: Confirmed Bug description: Ubuntu 21.04 on Raspberry Pi. isc-dhcp-server was working just fine with version V4.4.1-2.2-ubuntu6. I got updated to V4.4.1-2.2ubuntu6.1 and now isc-dhcp-server refuses to start with the error "Can't clone pool group". I backed off to the prior version and it's working as before, so something in the V4.4.1-2.2ubuntu6.1 update has broken config file parsing. Here's the subnet section of the failing config. Removing the "pool" declaration from the subnet declaration eliminates the error, but of course, that's not a working configuration. subnet 192.168.92.0 netmask 255.255.255.0 { option domain-search "foo.com", "dyn.foo.com"; option broadcast-address 192.168.92.255; allow duplicates; ddns-updates off; pool { ddns-updates on; allow unknown-clients; option domain-name "dyn.foo.com"; ddns-rev-domainname "dhcp"; default-lease-time 86400; max-lease-time 86400; range 192.168.92.101 192.168.92.127; } } This was also noted at least twice in the Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2462984 and https://ubuntuforums.org/showthread.php?t=2462930 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1930917/+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 1931077] Re: emergency shell ignores all keyboard input
So to summarize: -your drive failed -you ssh'ed into the machine and started a service that required the drive -systemd put the system into emergency target -you switched to the backup partition and systemd exited the emergency target -the emergency shell is now inactive, but of course its output text remains on the screen If that's a correct summary, I'm not sure what you wanted systemd to do differently? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1931077 Title: emergency shell ignores all keyboard input Status in systemd package in Ubuntu: Incomplete Bug description: An SSD that held my /boot/efi partition failed, took down local-fs.target, which brought up emergency.target. I ended up with no ssh access, and a message on the local console telling me to press Enter to get a root shell, or press Ctrl-D to continue booting normally. The system did not react to either Enter or Ctrl-D. I could switch between virtual consoles (but nothing was running on them, e.g. no getty), toggle Caps Lock, or reboot with Ctrl+Alt+Del. An emergency console that doesn't accept keyboard input is not a useful emergency console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.47 ProcVersionSignature: Ubuntu 4.15.0-144.148-generic 4.15.18 Uname: Linux 4.15.0-144-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Mon Jun 7 11:18:39 2021 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-144-generic root=/dev/mapper/hostname-root ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2019-08-12 (664 days ago) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931077/+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 1931064] Re: lxc autotest failure with kernel >= 5.13
I'm currently treating this as an upstream kernel regression reported here https://lore.kernel.org/regressions/20210607142245.eikvyeacqwwu6dn3@wittgenstein We should wait whether a simple revert will be acceptable or whether anything else is needed from LXC specifically. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1931064 Title: lxc autotest failure with kernel >= 5.13 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: The lxc autotest is failing with the following error(s) on the latest kernel linux-unstable 5.13: FAIL: lxc-tests: lxc-test-apparmor (1s) --- failed - opened /sys/kernel/uevent_helper --- PASS: lxc-tests: lxc-test-apparmor-generated (0s) PASS: lxc-tests: lxc-test-apparmor-mount (29s) FAIL: lxc-tests: lxc-test-attach (1s) --- attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for container lxc-attach-test I was able to bisect the problem and found that the offending commit is: bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check /proc/$pid/attr/ writes against file opener") This commit looks like a sane fix, so simply reverting it in the kernel doesn't seem a viable solution. I think we should address and understand the issue in the lxc package. Detailed log of the failure: https://autopkgtest.ubuntu.com/results /autopkgtest-impish-canonical-kernel-team- bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931064/+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 1930286] Re: Defensics' synopsys fuzzer testing tool cause openssh to segfault
** Description changed: [Impact] Here's what has been brought to my attention by a UA customer: * Release: Xenial/16.04LTS * Openssh version: 7.2p2-4ubuntu2.10 * Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) As of today, I have no access to a reproducer. * coredump: $ gdb $(which sshd) .sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_ctrl (ctx=ctx@entry=0x558a7ae19758, type=type@entry=18, arg=arg@entry=-1, ptr=ptr@entry=0x0) at evp_enc.c:619 #4 0x558a7953f54c in cipher_init (cc=cc@entry=0x558a7ae19750, cipher=0x558a797b3ef0 , key=0x0, keylen=32, iv=0x0, ivlen=, do_encrypt=0) at ../cipher.c:336 #5 0x558a7954521a in ssh_set_newkeys (ssh=ssh@entry=0x558a7ae18ef0, mode=mode@entry=0)at ../packet.c:919 #6 0x558a7955ae92 in kex_input_newkeys (type=, seq=, ctxt=0x558a7ae18ef0)at ../kex.c:434 #7 0x558a7954d269 in ssh_dispatch_run (ssh=ssh@entry=0x558a7ae18ef0, mode=0, done=0x558a7ae18278, ctxt=0x558a7ae18ef0) at ../dispatch.c:119 #8 0x558a7954d2b9 in ssh_dispatch_run_fatal (ssh=0x558a7ae18ef0, mode=, done=, ctxt=) at ../dispatch.c:140 #9 0x558a79502770 in do_ssh2_kex () at ../sshd.c:2744 #10 main (ac=, av=) at ../sshd.c:2301 (gdb) [Test plan] ** NOT REPRODUCIBLE ON MY SIDE ** This seems to be a corner case generated by the Defensics fuzzer test suite (proprietary software from synopsys). That's the only way this could have been reproduced so far. + Here's the details I could gather about the fuzzer test scenario: + + -- + Test Suite: SSHv2 Server Test Suite by Synopsys + Test Case Description: + SSHv2.Key-Exchange.DH-GROUP-EXCHANGE-SHA256.message-sequence.duplicate-message: + Insert extra message 'message-2' before message 'client-newkeys' + -- + [Where problem could occur] [Other information] Upstream fix: https://github.com/openssh/openssh-portable/commit/2adbe1e63bc313d03e8e84e652cc623af8ebb163 Only Xenial requires the fix: # git describe --contains 2adbe1e V_7_5_P1~7 # rmadison openssh => openssh | 1:7.2p2-4ubuntu2.10 | xenial-updates | source openssh | 1:7.6p1-4 | bionic | source openssh | 1:7.6p1-4ubuntu0.3 | bionic-security | source openssh | 1:7.6p1-4ubuntu0.3 | bionic-updates | source openssh | 1:7.6p1-4ubuntu0.4 | bionic-proposed | source openssh | 1:8.2p1-4 | focal| source openssh | 1:8.2p1-4ubuntu0.2 | focal-security | source openssh | 1:8.2p1-4ubuntu0.2 | focal-updates| source openssh | 1:8.3p1-1 | groovy | source openssh | 1:8.3p1-1ubuntu0.1 | groovy-security | source openssh | 1:8.3p1-1ubuntu0.1 | groovy-updates | source openssh | 1:8.4p1-5ubuntu1| hirsute | source openssh | 1:8.4p1-5ubuntu1| impish | source -- 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/1930286 Title: Defensics' synopsys fuzzer testing tool cause openssh to segfault Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: In Progress Bug description: [Impact] Here's what has been brought to my attention by a UA customer: * Release: Xenial/16.04LTS * Openssh version: 7.2p2-4ubuntu2.10 * Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) As of today, I have no access to a reproducer. * coredump: $ gdb $(which sshd) .sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64
[Touch-packages] [Bug 1930917] Re: Latest isc-dhcp-server rejects proper dhcpd.conf
This bug was fixed in the package isc-dhcp - 4.4.1-2.2ubuntu6.2 --- isc-dhcp (4.4.1-2.2ubuntu6.2) hirsute-security; urgency=medium * Fix regression caused by rebuild with newer toolchain (LP: #1930917) - debian/rules: build with -fno-strict-aliasing. -- Marc Deslauriers Mon, 07 Jun 2021 08:08:56 -0400 ** Changed in: isc-dhcp (Ubuntu Hirsute) Status: Confirmed => Fix Released -- 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/1930917 Title: Latest isc-dhcp-server rejects proper dhcpd.conf Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Hirsute: Fix Released Status in isc-dhcp source package in Impish: Confirmed Bug description: Ubuntu 21.04 on Raspberry Pi. isc-dhcp-server was working just fine with version V4.4.1-2.2-ubuntu6. I got updated to V4.4.1-2.2ubuntu6.1 and now isc-dhcp-server refuses to start with the error "Can't clone pool group". I backed off to the prior version and it's working as before, so something in the V4.4.1-2.2ubuntu6.1 update has broken config file parsing. Here's the subnet section of the failing config. Removing the "pool" declaration from the subnet declaration eliminates the error, but of course, that's not a working configuration. subnet 192.168.92.0 netmask 255.255.255.0 { option domain-search "foo.com", "dyn.foo.com"; option broadcast-address 192.168.92.255; allow duplicates; ddns-updates off; pool { ddns-updates on; allow unknown-clients; option domain-name "dyn.foo.com"; ddns-rev-domainname "dhcp"; default-lease-time 86400; max-lease-time 86400; range 192.168.92.101 192.168.92.127; } } This was also noted at least twice in the Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2462984 and https://ubuntuforums.org/showthread.php?t=2462930 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1930917/+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 1915502] Re: "systemd --user" fails to start for non-local users
A little more information, after some investigation. The issue affects xdm logins at the console, as well as remote ssh logins. This also means that audio at the console fails to work, as ACLs for the console's user are not added to the audio devices. It seem that it can be solved by putting in /etc/systemd/system/systemd- logind.service.d/override.conf [Service] RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET IPAddressDeny= ProtectHostname=no after which "systemctl daemon-reload" followed by "systemctl daemon- reexec" does nothing useful, but a reboot does cause things to start working. (I don't understand why daemon-reexec differs from rebooting.) Changing the above file is approximately equivalent to "systemctl edit systemd-logind" followed by "systemctl daemon-reload", but, when faced with multiple machines, the file change may be easier to script. Note that the directory probably does not exist. The need for ProtectHostname=no seems new, and note also that if one speaks IPv6 to one's NIS servers, AF_INET6 may be necessary. I do not use nscd, which may also solve the issue. I don't understand Haoke's comment that systemd is not involved. -- 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/1915502 Title: "systemd --user" fails to start for non-local users Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Focal: Incomplete Bug description: systemd-logind fails to start the systemd --user process for non-local users on Ubuntu 20.04. This is a reproducible problem; all our systems are displaying the same symptoms. The systems are using Kerberos (Active Directory) for authentication, and NIS for account meta-data and authorisation (groups) A base installation is performed using the server 20.04 ISO image. No additional packages are selected. Post-install, I run: apt-get install tcsh nis krb5-user libpam-krb5 libnss-systemd I set up the NIS client (supply the default domain name, check ypbind is running and ypcat passwd is working) I then set up /etc/krb5.conf for kerberos authentication to a domain controller, confirm that kinit works and a kerberos ticket is issued. I modify /etc/passwd, /etc/group and /etc/shadow, appending a "+" to the end of each. /etc/nsswitch.conf is modified to support compat mode, as well as systemd: passwd: compat systemd group: compat systemd shadow: compat I can log in remotely via ssh using my NIS account and Kerberos credentials. MY NIS meta-data looks like: amcvey:KRB5:::Andy McVey:/home/amcvey:/bin/tcsh (where UID and GID are replaced with values unique to the organisation) On login, the following occurs: hostname:~> systemctl --user Failed to connect to bus: No such file or directory I put pam-systemd and systemd-logind into debug mode to get more information: Feb 12 09:51:32 myhostname sshd[1210]: Accepted publickey for amcvey from [redact] port 58849 ssh2: RSA SHA256:[redact] Feb 12 09:51:32 myhostname sshd[1210]: pam_unix(sshd:session): session opened for user amcvey by (uid=0) Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_call sender=:1.13 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CreateSession cookie=2 reply_cookie=0 signature=uusussbssa(sv) error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): pam-systemd initializing Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixUser cookie=40 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Asking logind to create session: uid=198083 pid=1210 service=sshd type=tty class=user desktop= seat= vtnr=0 tty= display= remote=yes remote_user= remote_host=10.105.121.110 Feb 12 09:51:32 myhostname systemd-logind[903]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.6 path=n/a interface=n/a member=n/a cookie=13 reply_cookie=40 signature=u error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a Feb 12 09:51:32 myhostname systemd-logind[903]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=41 reply_cookie=0 signature=s error-name=n/a error-message=n/a Feb 12 09:51:32 myhostname sshd[1210]: pam_systemd(sshd:session): Failed to create session: No such process Feb 12 09:51:32 myhostn
[Touch-packages] [Bug 1930286] Re: Defensics' synopsys fuzzer testing tool cause openssh to segfault
debdiff to go over the ESM process by security team. Thanks - Eric ** Patch added: "xenial_lp1930286.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1930286/+attachment/5502934/+files/xenial_lp1930286.debdiff -- 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/1930286 Title: Defensics' synopsys fuzzer testing tool cause openssh to segfault Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: In Progress Bug description: [Impact] Here's what has been brought to my attention by a UA customer: * Release: Xenial/16.04LTS * Openssh version: 7.2p2-4ubuntu2.10 * Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) As of today, I have no access to a reproducer. * coredump: $ gdb $(which sshd) .sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_ctrl (ctx=ctx@entry=0x558a7ae19758, type=type@entry=18, arg=arg@entry=-1, ptr=ptr@entry=0x0) at evp_enc.c:619 #4 0x558a7953f54c in cipher_init (cc=cc@entry=0x558a7ae19750, cipher=0x558a797b3ef0 , key=0x0, keylen=32, iv=0x0, ivlen=, do_encrypt=0) at ../cipher.c:336 #5 0x558a7954521a in ssh_set_newkeys (ssh=ssh@entry=0x558a7ae18ef0, mode=mode@entry=0)at ../packet.c:919 #6 0x558a7955ae92 in kex_input_newkeys (type=, seq=, ctxt=0x558a7ae18ef0)at ../kex.c:434 #7 0x558a7954d269 in ssh_dispatch_run (ssh=ssh@entry=0x558a7ae18ef0, mode=0, done=0x558a7ae18278, ctxt=0x558a7ae18ef0) at ../dispatch.c:119 #8 0x558a7954d2b9 in ssh_dispatch_run_fatal (ssh=0x558a7ae18ef0, mode=, done=, ctxt=) at ../dispatch.c:140 #9 0x558a79502770 in do_ssh2_kex () at ../sshd.c:2744 #10 main (ac=, av=) at ../sshd.c:2301 (gdb) [Test plan] ** NOT REPRODUCIBLE ON MY SIDE ** This seems to be a corner case generated by the Defensics fuzzer test suite (proprietary software from synopsys). That's the only way this could have been reproduced so far. [Where problem could occur] [Other information] Upstream fix: https://github.com/openssh/openssh-portable/commit/2adbe1e63bc313d03e8e84e652cc623af8ebb163 Only Xenial requires the fix: # git describe --contains 2adbe1e V_7_5_P1~7 # rmadison openssh => openssh | 1:7.2p2-4ubuntu2.10 | xenial-updates | source openssh | 1:7.6p1-4 | bionic | source openssh | 1:7.6p1-4ubuntu0.3 | bionic-security | source openssh | 1:7.6p1-4ubuntu0.3 | bionic-updates | source openssh | 1:7.6p1-4ubuntu0.4 | bionic-proposed | source openssh | 1:8.2p1-4 | focal| source openssh | 1:8.2p1-4ubuntu0.2 | focal-security | source openssh | 1:8.2p1-4ubuntu0.2 | focal-updates| source openssh | 1:8.3p1-1 | groovy | source openssh | 1:8.3p1-1ubuntu0.1 | groovy-security | source openssh | 1:8.3p1-1ubuntu0.1 | groovy-updates | source openssh | 1:8.4p1-5ubuntu1| hirsute | source openssh | 1:8.4p1-5ubuntu1| impish | source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1930286/+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 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
While we wait for 3.67 and maybe (Thanks Timo) for [1] I have ensured that we have a 3.66 test build. => https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4577/+packages The check of it's delta also showed that we can drop a bit of it nowadays. => https://code.launchpad.net/~paelzer/ubuntu/+source/nss/+git/nss/+ref/merge-impish-3.66-1 [1]: https://phabricator.services.mozilla.com/D116274 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1931104 Title: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish- proposed Status in nss package in Ubuntu: New Bug description: The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed. Example: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz Bad: Installing CA into /var/lib/pki/pki-tomcat. Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 995, in spawn cert = deployer.setup_cert(client, tag) File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py", line 355, in setup_cert return client.setupCert(request) File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert response = self.connection.post( File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper return func(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post r = self.session.post( File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in post return self.request('POST', url, data=data, json=json, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) CA spawn failed: Good: nstalling CA into /var/lib/pki/pki-tomcat. Notice: Trust flag u is set automatically if the private key is present. /usr/lib/python3/dist-packages/urllib3/connection.py:455: SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/urllib3/urllib3/issues/497 for details.) warnings.warn( == INSTALLATION SUMMARY == ... The good test above was with: ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security Service libraries ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite - server Worth to know, the good case test still fails later on with: IOException: SocketException cannot write on socket: Failed to write to socket: (-5938) Encountered end of file. ERROR: CalledProcessError: Command '['pki', '-d', '/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U', 'https://i-dogtag:8443', 'securitydomain-join', '--session', '4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag', '--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']' returned non-zero exit status 255. File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 1038, in spawn subsystem.join_security_domain( File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201, in join_security_domain subprocess.check_call(cmd) File "/usr/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f /etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join --session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port 8080 --secure-port 8443 TKS i-dogtag 8443 Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log Well one issue at a time ... the current install issue first. Since it worked with the nss in -release I
[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)
For what it's worth, I commented out the `mystatedir statedir ifindex interface` line, and changed the three `return` lines to be `exit 0` and now I no longer get the angry red FAILED line during boot, `systemctl status networking.service` looks okay, and my internet continues to function just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1907878 Title: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found) Status in ifupdown package in Ubuntu: Confirmed Bug description: Syslog error: nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir: not found I think it's because of this line: if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface <- this is interpreted as a 'mystatedir' command and fails interface=$IFACE if [ ! "$interface" ]; then Perhaps the intention was to 'export mystatedir statedir ...' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1907878/+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 1930286] Re: Defensics' synopsys fuzzer testing tool cause openssh to segfault
** Changed in: openssh (Ubuntu Xenial) Status: New => In Progress ** Description changed: + [Impact] Here's what has been brought to my attention by a UA customer: * Release: Xenial/16.04LTS * Openssh version: 7.2p2-4ubuntu2.10 * Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) As of today, I have no access to a reproducer. Still working on getting access to one (if possible) in order to better understand what the failing test scenario is doing. * coredump: $ gdb $(which sshd) core.cic-1.domain.tld.1612566260.sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_ctrl (ctx=ctx@entry=0x558a7ae19758, type=type@entry=18, arg=arg@entry=-1, ptr=ptr@entry=0x0) at evp_enc.c:619 #4 0x558a7953f54c in cipher_init (cc=cc@entry=0x558a7ae19750, cipher=0x558a797b3ef0 , key=0x0, keylen=32, iv=0x0, ivlen=, do_encrypt=0) at ../cipher.c:336 #5 0x558a7954521a in ssh_set_newkeys (ssh=ssh@entry=0x558a7ae18ef0, mode=mode@entry=0)at ../packet.c:919 #6 0x558a7955ae92 in kex_input_newkeys (type=, seq=, ctxt=0x558a7ae18ef0)at ../kex.c:434 #7 0x558a7954d269 in ssh_dispatch_run (ssh=ssh@entry=0x558a7ae18ef0, mode=0, done=0x558a7ae18278, ctxt=0x558a7ae18ef0) at ../dispatch.c:119 #8 0x558a7954d2b9 in ssh_dispatch_run_fatal (ssh=0x558a7ae18ef0, mode=, done=, ctxt=) at ../dispatch.c:140 #9 0x558a79502770 in do_ssh2_kex () at ../sshd.c:2744 #10 main (ac=, av=) at ../sshd.c:2301 (gdb) + + [Test plan] + + ** NOT REPRODUCIBLE ON MY SIDE ** + + This seems to be a corner case generated by the Defensics fuzzer test + suite (proprietary software from synopsys). + + That's the only way this could have been reproduced so far. + + [Where problem could occur] + + [Other information] + + Upstream fix: + https://github.com/openssh/openssh-portable/commit/2adbe1e63bc313d03e8e84e652cc623af8ebb163 + + Only Xenial requires the fix: + + # git describe --contains 2adbe1e + V_7_5_P1~7 + + # rmadison openssh + => openssh | 1:7.2p2-4ubuntu2.10 | xenial-updates | source + openssh | 1:7.6p1-4 | bionic | source + openssh | 1:7.6p1-4ubuntu0.3 | bionic-security | source + openssh | 1:7.6p1-4ubuntu0.3 | bionic-updates | source + openssh | 1:7.6p1-4ubuntu0.4 | bionic-proposed | source + openssh | 1:8.2p1-4 | focal| source + openssh | 1:8.2p1-4ubuntu0.2 | focal-security | source + openssh | 1:8.2p1-4ubuntu0.2 | focal-updates| source + openssh | 1:8.3p1-1 | groovy | source + openssh | 1:8.3p1-1ubuntu0.1 | groovy-security | source + openssh | 1:8.3p1-1ubuntu0.1 | groovy-updates | source + openssh | 1:8.4p1-5ubuntu1| hirsute | source + openssh | 1:8.4p1-5ubuntu1| impish | source ** Changed in: openssh (Ubuntu) Status: New => Fix Released ** Changed in: openssh (Ubuntu Xenial) Importance: Undecided => Medium ** Description changed: - [Impact] + [Impact] Here's what has been brought to my attention by a UA customer: * Release: Xenial/16.04LTS * Openssh version: 7.2p2-4ubuntu2.10 * Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) - As of today, I have no access to a reproducer. Still working on getting - access to one (if possible) in order to better understand what the - failing test scenario is doing. + As of today, I have no access to a reproducer. * coredump: $ gdb $(which sshd) core.cic-1.domain.tld.1612566260.sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_
[Touch-packages] [Bug 1931104] Re: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
FYI by tjaaltonen - there's another crasher in 3.66 on ppc64el.. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410 So 3.66 won't be the "take this and it works" solution. ** Bug watch added: Debian Bug tracker #989410 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989410 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1931104 Title: Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish- proposed Status in nss package in Ubuntu: New Bug description: The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed. Example: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz Bad: Installing CA into /var/lib/pki/pki-tomcat. Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 995, in spawn cert = deployer.setup_cert(client, tag) File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py", line 355, in setup_cert return client.setupCert(request) File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert response = self.connection.post( File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper return func(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post r = self.session.post( File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in post return self.request('POST', url, data=data, json=json, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) CA spawn failed: Good: nstalling CA into /var/lib/pki/pki-tomcat. Notice: Trust flag u is set automatically if the private key is present. /usr/lib/python3/dist-packages/urllib3/connection.py:455: SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/urllib3/urllib3/issues/497 for details.) warnings.warn( == INSTALLATION SUMMARY == ... The good test above was with: ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security Service libraries ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite - server Worth to know, the good case test still fails later on with: IOException: SocketException cannot write on socket: Failed to write to socket: (-5938) Encountered end of file. ERROR: CalledProcessError: Command '['pki', '-d', '/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U', 'https://i-dogtag:8443', 'securitydomain-join', '--session', '4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag', '--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']' returned non-zero exit status 255. File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 1038, in spawn subsystem.join_security_domain( File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201, in join_security_domain subprocess.check_call(cmd) File "/usr/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f /etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join --session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port 8080 --secure-port 8443 TKS i-dogtag 8443 Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log Well one issue at a time ... the current install issue first. Since it worked with the nss in -release I was upgrading this to the new nss. ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite - s
[Touch-packages] [Bug 1930286] Re: Defensics' synopsys fuzzer testing tool cause openssh to segfault
UA customer test pkg outcome: " We ran the Defensics test suite before and after installing the test packages. We could observe two core dumps before the test package installation. But after test package installation, core dumps were not generated. Can you provide this package as the fix? " This concludes that xenial + commit 2adbe1e63bc313d03e8e84e652cc623af8ebb163 fixes their fuzzer segfault situation. - Eric -- 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/1930286 Title: Defensics' synopsys fuzzer testing tool cause openssh to segfault Status in openssh package in Ubuntu: New Status in openssh source package in Xenial: New Bug description: Here's what has been brought to my attention by a UA customer: * Release: Xenial/16.04LTS * Openssh version: 7.2p2-4ubuntu2.10 * Fuzzer tool used: https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html (proprietary software) As of today, I have no access to a reproducer. Still working on getting access to one (if possible) in order to better understand what the failing test scenario is doing. * coredump: $ gdb $(which sshd) core.cic-1.domain.tld.1612566260.sshd.20731 ... Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `sshd: [net] '. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 136 ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S: No such file or directory. (gdb) bt #0 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:136 #1 0x7fec25b241db in memcpy (__len=, __src=0x0, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 aes_gcm_ctrl (c=0x558a7ae19758, type=, arg=, ptr=0x0) at e_aes.c:1189 #3 0x7fec25b20897 in EVP_CIPHER_CTX_ctrl (ctx=ctx@entry=0x558a7ae19758, type=type@entry=18, arg=arg@entry=-1, ptr=ptr@entry=0x0) at evp_enc.c:619 #4 0x558a7953f54c in cipher_init (cc=cc@entry=0x558a7ae19750, cipher=0x558a797b3ef0 , key=0x0, keylen=32, iv=0x0, ivlen=, do_encrypt=0) at ../cipher.c:336 #5 0x558a7954521a in ssh_set_newkeys (ssh=ssh@entry=0x558a7ae18ef0, mode=mode@entry=0)at ../packet.c:919 #6 0x558a7955ae92 in kex_input_newkeys (type=, seq=, ctxt=0x558a7ae18ef0)at ../kex.c:434 #7 0x558a7954d269 in ssh_dispatch_run (ssh=ssh@entry=0x558a7ae18ef0, mode=0, done=0x558a7ae18278, ctxt=0x558a7ae18ef0) at ../dispatch.c:119 #8 0x558a7954d2b9 in ssh_dispatch_run_fatal (ssh=0x558a7ae18ef0, mode=, done=, ctxt=) at ../dispatch.c:140 #9 0x558a79502770 in do_ssh2_kex () at ../sshd.c:2744 #10 main (ac=, av=) at ../sshd.c:2301 (gdb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1930286/+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 1930917] Re: Latest isc-dhcp-server rejects proper dhcpd.conf
I can confirm the update introduced a regression on Hirsute (and Impish I presume). Focal and Groovy work properly. Unfortunately, it's not related to the security patch, but it stems from the package being rebuilt with the newer toolchain in Hirsute, so removing the patch won't fix the issue. I am currently investigating how to fix this. ** Also affects: isc-dhcp (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Changed in: isc-dhcp (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: isc-dhcp (Ubuntu Hirsute) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: isc-dhcp (Ubuntu Impish) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: isc-dhcp (Ubuntu Hirsute) Importance: Undecided => Critical ** Changed in: isc-dhcp (Ubuntu Impish) Importance: Undecided => Critical -- 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/1930917 Title: Latest isc-dhcp-server rejects proper dhcpd.conf Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp source package in Hirsute: Confirmed Status in isc-dhcp source package in Impish: Confirmed Bug description: Ubuntu 21.04 on Raspberry Pi. isc-dhcp-server was working just fine with version V4.4.1-2.2-ubuntu6. I got updated to V4.4.1-2.2ubuntu6.1 and now isc-dhcp-server refuses to start with the error "Can't clone pool group". I backed off to the prior version and it's working as before, so something in the V4.4.1-2.2ubuntu6.1 update has broken config file parsing. Here's the subnet section of the failing config. Removing the "pool" declaration from the subnet declaration eliminates the error, but of course, that's not a working configuration. subnet 192.168.92.0 netmask 255.255.255.0 { option domain-search "foo.com", "dyn.foo.com"; option broadcast-address 192.168.92.255; allow duplicates; ddns-updates off; pool { ddns-updates on; allow unknown-clients; option domain-name "dyn.foo.com"; ddns-rev-domainname "dhcp"; default-lease-time 86400; max-lease-time 86400; range 192.168.92.101 192.168.92.127; } } This was also noted at least twice in the Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2462984 and https://ubuntuforums.org/showthread.php?t=2462930 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1930917/+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 1931104] [NEW] Test of dogtag-pki is failing on s390x vs the nss v3.63 in impish-proposed
Public bug reported: The test of dogtag-pki is failing on the nss 3.63 that is in impish proposed. Example: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/s390x/d/dogtag-pki/20210516_212719_e6522@/log.gz Bad: Installing CA into /var/lib/pki/pki-tomcat. Installation failed: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) ERROR: ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 995, in spawn cert = deployer.setup_cert(client, tag) File "/usr/lib/python3/dist-packages/pki/server/deployment/__init__.py", line 355, in setup_cert return client.setupCert(request) File "/usr/lib/python3/dist-packages/pki/system.py", line 389, in setupCert response = self.connection.post( File "/usr/lib/python3/dist-packages/pki/client.py", line 55, in wrapper return func(self, *args, **kwargs) File "/usr/lib/python3/dist-packages/pki/client.py", line 293, in post r = self.session.post( File "/usr/lib/python3/dist-packages/requests/sessions.py", line 590, in post return self.request('POST', url, data=data, json=json, **kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send r = adapter.send(request, **kwargs) File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send raise ConnectionError(err, request=request) CA spawn failed: Good: nstalling CA into /var/lib/pki/pki-tomcat. Notice: Trust flag u is set automatically if the private key is present. /usr/lib/python3/dist-packages/urllib3/connection.py:455: SubjectAltNameWarning: Certificate for i-dogtag has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/urllib3/urllib3/issues/497 for details.) warnings.warn( == INSTALLATION SUMMARY == ... The good test above was with: ii libnss3:s390x2:3.61-1ubuntu2 s390xNetwork Security Service libraries ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite - server Worth to know, the good case test still fails later on with: IOException: SocketException cannot write on socket: Failed to write to socket: (-5938) Encountered end of file. ERROR: CalledProcessError: Command '['pki', '-d', '/etc/pki/pki-tomcat/alias', '-f', '/etc/pki/pki-tomcat/password.conf', '-U', 'https://i-dogtag:8443', 'securitydomain-join', '--session', '4717921475119312283', '--type', 'TKS', '--hostname', 'i-dogtag', '--unsecure-port', '8080', '--secure-port', '8443', 'TKS i-dogtag 8443']' returned non-zero exit status 255. File "/usr/lib/python3/dist-packages/pki/server/pkispawn.py", line 575, in main scriptlet.spawn(deployer) File "/usr/lib/python3/dist-packages/pki/server/deployment/scriptlets/configuration.py", line 1038, in spawn subsystem.join_security_domain( File "/usr/lib/python3/dist-packages/pki/server/subsystem.py", line 1201, in join_security_domain subprocess.check_call(cmd) File "/usr/lib/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) Installation failed: Command failed: pki -d /etc/pki/pki-tomcat/alias -f /etc/pki/pki-tomcat/password.conf -U https://i-dogtag:8443 securitydomain-join --session 4717921475119312283 --type TKS --hostname i-dogtag --unsecure-port 8080 --secure-port 8443 TKS i-dogtag 8443 Please check pkispawn logs in /var/log/pki/pki-tks-spawn.20210607093926.log Well one issue at a time ... the current install issue first. Since it worked with the nss in -release I was upgrading this to the new nss. ii 389-ds-base1.4.4.11-2 s390x389 Directory Server suite - server ii libnss3:s390x 2:3.63-1ubuntu1 s390xNetwork Security Service libraries With this the install fail is reprodicible. So we can switch in/out bad case by up/downgrading libnss3. Comparing those two cases until they reach the first successful install message I've seen a crash: pki-tomcat[37160]: # pki-tomcat[37160]: # A fatal error has been detected by the Java Runtime Environment: pki-tomcat[37160]: # pki-tomcat[37160]: # SIGSEGV (0xb) at pc=0x03ff9ce9ec02, pid=37160, tid=37246 pki-tomcat[37160]: # pki-tomcat[37160]: # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) pki-tomcat[37160]: # Java VM: OpenJDK 64-Bit Serv
[Touch-packages] [Bug 1539689] Re: package lvm2 2.02.133-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
workaround: sudo apt purge libtss2-esys0 libsrt1-gnutls manpages-de -- 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/1539689 Title: package lvm2 2.02.133-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lvm2 package in Ubuntu: Triaged Bug description: I was trying to upgrade the system to see new updates on the Ubuntu 16.04. But it couldn't be finished because the operation stopped while upgrading lvm2. So I guess it broke the OS because I can't do the "apt-get upgrade" anymore. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu4 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CasperVersion: 1.366 Date: Fri Jan 29 16:32:35 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160128) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: lvm2 Title: package lvm2 2.02.133-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script 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/lvm2/+bug/1539689/+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 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
As I said I tried to recreate this, but it worked. It was fine under Focal/5.4.0-53-generic Host with the Impish-armhf container. Upgrading the host to impish it Impish/5.11.0-16-generic still works fine. It seems it only fails in autopkgtest infrastructure, not sure why yet :-/ -- 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/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1931088/+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 1931064] [NEW] lxc autotest failure with kernel >= 5.13
On Mon, Jun 07, 2021 at 05:14:50AM -, Andrea Righi wrote: > Public bug reported: > > The lxc autotest is failing with the following error(s) on the latest > kernel linux-unstable 5.13: > > FAIL: lxc-tests: lxc-test-apparmor (1s) > --- > failed - opened /sys/kernel/uevent_helper > --- > PASS: lxc-tests: lxc-test-apparmor-generated (0s) > PASS: lxc-tests: lxc-test-apparmor-mount (29s) > FAIL: lxc-tests: lxc-test-attach (1s) > --- > attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for > container lxc-attach-test > > I was able to bisect the problem and found that the offending commit is: > > bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check /proc/$pid/attr/ > writes against file opener") > > This commit looks like a sane fix, so simply reverting it in the kernel > doesn't seem a viable solution. > > I think we should address and understand the issue in the lxc package. So this failure implies that the /sys/kernel/uevent_helper file that we denied access to via AppArmor can now be opened. And then lxc-test-attach reports an LSM label mismatch in the link you posted below too so that seems scary... > > Detailed log of the failure: https://autopkgtest.ubuntu.com/results > /autopkgtest-impish-canonical-kernel-team- > bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz > > ** Affects: lxc (Ubuntu) > Importance: Undecided > Status: New > > ** Description changed: > > The lxc autotest is failing with the following error(s) on the latest > kernel linux-unstable 5.13: > > FAIL: lxc-tests: lxc-test-apparmor (1s) > --- > failed - opened /sys/kernel/uevent_helper > --- > PASS: lxc-tests: lxc-test-apparmor-generated (0s) > PASS: lxc-tests: lxc-test-apparmor-mount (29s) > FAIL: lxc-tests: lxc-test-attach (1s) > --- > attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for > container lxc-attach-test > > I was able to bisect the problem and found that the offending commit is: > > bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check /proc/$pid/attr/ > writes against file opener") > > This commit looks like a sane fix, so simply reverting it in the kernel > doesn't seem a viable solution. > > I think we should address and understand the issue in the lxc package. > + > + Detailed log of the failure: https://autopkgtest.ubuntu.com/results > + /autopkgtest-impish-canonical-kernel-team- > + bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz > > -- > You received this bug notification because you are a member of Ubuntu > containers team, which is subscribed to lxc in Ubuntu. > Matching subscriptions: lxc > https://bugs.launchpad.net/bugs/1931064 > > Title: > lxc autotest failure with kernel >= 5.13 > > Status in lxc package in Ubuntu: > New > > Bug description: > The lxc autotest is failing with the following error(s) on the latest > kernel linux-unstable 5.13: > > FAIL: lxc-tests: lxc-test-apparmor (1s) > --- > failed - opened /sys/kernel/uevent_helper > --- > PASS: lxc-tests: lxc-test-apparmor-generated (0s) > PASS: lxc-tests: lxc-test-apparmor-mount (29s) > FAIL: lxc-tests: lxc-test-attach (1s) > --- > attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for > container lxc-attach-test > > I was able to bisect the problem and found that the offending commit > is: > > bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check > /proc/$pid/attr/ writes against file opener") > > This commit looks like a sane fix, so simply reverting it in the > kernel doesn't seem a viable solution. > > I think we should address and understand the issue in the lxc package. > > Detailed log of the failure: https://autopkgtest.ubuntu.com/results > /autopkgtest-impish-canonical-kernel-team- > bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1931064/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1931064 Title: lxc autotest failure with kernel >= 5.13 Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Bug description: The lxc autotest is failing with the following error(s) on the latest kernel linux-unstable 5.13: FAIL: lxc-tests: lxc-test-apparmor (1s) --- failed - opened /sys/kernel/uevent_helper --- PASS: lxc-tests: lxc-test-apparmor-generated (0s) PASS: lxc-tests: lxc-test-apparmor-mount (29s) FAIL: lxc-tests: lxc-test-attach (1s) --- attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for container lxc-attach-test I was able to bisect the problem and found that the offending commit is: bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check /proc/$pid/attr/ writes against file opener") This commit looks like a
[Touch-packages] [Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default
Please disregard my last comment (#5). The problem I had was not this one but related to using other connector agents in addition to NetworkManager, in my case the openvpn3 command line. (Automatic connection to the VPN is not there, but that is probably safest.) -- 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/1774632 Title: The symbolic link /etc/resolv.conf points to the wrong file by default Status in systemd package in Ubuntu: Confirmed Bug description: When using nslookup for local machine names, the local DNS was being ignored (not queried) and none of the local machines could be found. After much research and digging, it was discovered that the cause was the incorrect symbolic link /etc/resolv.conf file. The default install caused systemd-resolve to configure the link to point to the stub file: /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf Reomving that link and pointing it to the correct file solved the DNS lookup issue. The correct link looks like this: /etc/resolv.conf -> /run/systemd/resolve/resolv.conf Steps used to test the bug before fixing the link is to perform an nslookup on a local (non FQDN) machine that is in your local DNS (my router is my DNS server for this case) Here is an example of the incorrect output: $ nslookup web1 Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find web1: SERVFAIL Switching the symbolic link solves the problem. Here is my solution: $ sudo rm -f /etc/resolv.conf $ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf After switching the symbolic link, the nslookup functions properly. $ nslookup web1 Server: 192.168.1.1 Address:192.168.1.1#53 Name: web1 Address: 192.168.1.107 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 1 05:28:41 2018 InstallationDate: Installed on 2018-01-20 (131 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Dell Inc. Inspiron 5755 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=7fe151d3-4033-4903-b356-341d9f16e124 ro acpi=force SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-04-28 (33 days ago) dmi.bios.date: 08/27/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0VY15F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/27/2015:svnDellInc.:pnInspiron5755:pvrA08:rvnDellInc.:rn0VY15F:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5755 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774632/+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 1931088] [NEW] boot-and-services tests fails in impish on armhf (248.3)
Public bug reported: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: glibc (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Also affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Changed in: dnsmasq (Ubuntu) Status: New => Incomplete ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: glibc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog
[Touch-packages] [Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
I was adding a few of the blocked packages as incomplete tasks to have this bug update-excuse show up in excuses. Right now until we know better I'd consider this a systemd 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/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) Status in dnsmasq package in Ubuntu: Incomplete Status in gdm3 package in Ubuntu: Incomplete Status in glibc package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf before now slipping into a bad mode. Now it seems all tests failed in boot-and-services by hanging until killed by VirtSubproc.Timeout of autokgtest. The last [1] test log has a bit more, it shows a python stack overflow ``` VirtSubproc.Timeout Fatal Python error: Cannot recover from stack overflow. Python runtime state: initialized Current thread 0x7f108e840740 (most recent call first): File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command ``` I have seen a bunch of packages including even gdm3 and glibc being blocked by that so I wanted to at least track down the issue until we can put it on someones task list to resolve. No one replied to my pings yet, but maybe that means someone is already debugging this and had enabled some debugging? By running the same in armhf container on arm64 VM on canonistack I've seen no issues. The test worked fine and had no hang/issues. root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services lxc 1 test_profile (__main__.AppArmorTest) AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352' test_help (__main__.CLITest) --help works and succeeds ... ok test_invalid_option (__main__.CLITest) Calling with invalid option fails ... ok test_version (__main__.CLITest) --version works and succeeds ... ok test_cpushares (__main__.CgroupsTest) service with CPUShares ... ok test_simple (__main__.CgroupsTest) simple service ... ok test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not work in containers' test_log_for_service (__main__.JournalTest) ... ok test_no_options (__main__.JournalTest) ... ok test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most containers' test_failing (__main__.SeccompTest) ... ok test_0_init (__main__.ServicesTest) Verify that init is systemd ... ok test_cron (__main__.ServicesTest) ... ok test_dbus (__main__.ServicesTest) ... ok test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found' test_logind (__main__.ServicesTest) ... ok test_network_manager (__main__.ServicesTest) ... ok test_no_failed (__main__.ServicesTest) No failed units ... ok test_rsyslog (__main__.ServicesTest) ... ok test_tmp_cleanup (__main__.ServicesTest) ... ok test_tmp_mount (__main__.ServicesTest) ... ok test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers' -- Ran 23 tests in 5.589s OK (skipped=6) So I can not reproduce this on canonistack, but it blocks autopkgtests of various packages pretty reproducibly :-/ [1]: https://autopkgtest.ubuntu.com/results/autopkgtest- impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1931088/+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 1931077] Re: emergency shell ignores all keyboard input
Looking at the journal, I think the sequence of events is: - SSD fails last Friday - I log in today over ssh, start messing around - I notice that collectd is not running (since Friday), try to `sudo systemctl start collectd` - systemd tries to bring up collectd's dependency local-fs.target, which need /dev/sda1, which is the failed drive - I figure _that_ out and start editing /etc/fstab to switch the /boot/efi device to the backup on /dev/sdb1 - in the background systemd gives up on local-fs.target and starts emergency.target, which shuts down all the services (including sshd, but not killing my ssh session) and brings up an emergency shell - I finish editing /etc/fstab and do a `sudo mount /boot/efi; sudo systemctl daemon-reload; sudo systemctl start collectd` - systemd notices that local-fs.target is all fine actually and stops the emergency shell - systemd doesn't start all the services that it shut down minutes ago - I exit my ssh session by mistake and now we have the situation where the emergency shell is stopped but its startup message remains, confusing users. (And also no systemd services are running, except for collectd, which is not very useful for getting the system back online.) -- 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/1931077 Title: emergency shell ignores all keyboard input Status in systemd package in Ubuntu: New Bug description: An SSD that held my /boot/efi partition failed, took down local-fs.target, which brought up emergency.target. I ended up with no ssh access, and a message on the local console telling me to press Enter to get a root shell, or press Ctrl-D to continue booting normally. The system did not react to either Enter or Ctrl-D. I could switch between virtual consoles (but nothing was running on them, e.g. no getty), toggle Caps Lock, or reboot with Ctrl+Alt+Del. An emergency console that doesn't accept keyboard input is not a useful emergency console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.47 ProcVersionSignature: Ubuntu 4.15.0-144.148-generic 4.15.18 Uname: Linux 4.15.0-144-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Mon Jun 7 11:18:39 2021 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-144-generic root=/dev/mapper/hostname-root ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2019-08-12 (664 days ago) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931077/+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 1931077] [NEW] emergency shell ignores all keyboard input
Public bug reported: An SSD that held my /boot/efi partition failed, took down local-fs.target, which brought up emergency.target. I ended up with no ssh access, and a message on the local console telling me to press Enter to get a root shell, or press Ctrl-D to continue booting normally. The system did not react to either Enter or Ctrl-D. I could switch between virtual consoles (but nothing was running on them, e.g. no getty), toggle Caps Lock, or reboot with Ctrl+Alt+Del. An emergency console that doesn't accept keyboard input is not a useful emergency console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.47 ProcVersionSignature: Ubuntu 4.15.0-144.148-generic 4.15.18 Uname: Linux 4.15.0-144-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Mon Jun 7 11:18:39 2021 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-144-generic root=/dev/mapper/hostname-root ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2019-08-12 (664 days ago) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1931077 Title: emergency shell ignores all keyboard input Status in systemd package in Ubuntu: New Bug description: An SSD that held my /boot/efi partition failed, took down local-fs.target, which brought up emergency.target. I ended up with no ssh access, and a message on the local console telling me to press Enter to get a root shell, or press Ctrl-D to continue booting normally. The system did not react to either Enter or Ctrl-D. I could switch between virtual consoles (but nothing was running on them, e.g. no getty), toggle Caps Lock, or reboot with Ctrl+Alt+Del. An emergency console that doesn't accept keyboard input is not a useful emergency console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.47 ProcVersionSignature: Ubuntu 4.15.0-144.148-generic 4.15.18 Uname: Linux 4.15.0-144-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 Date: Mon Jun 7 11:18:39 2021 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-144-generic root=/dev/mapper/hostname-root ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2019-08-12 (664 days ago) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931077/+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