[Bug 1929259] Re: Focal arm64: pip3 install h5py==3.1.0 fails with /usr/include/hdf5/openmpi/H5public.h:60:13: fatal error: mpi.h: No such file or directory
** Also affects: arm-ports Importance: Undecided Status: New ** Also affects: pip Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929259 Title: Focal arm64: pip3 install h5py==3.1.0 fails with /usr/include/hdf5/openmpi/H5public.h:60:13: fatal error: mpi.h: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/arm-ports/+bug/1929259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929259] [NEW] Focal arm64: pip3 install h5py==3.1.0 fails with /usr/include/hdf5/openmpi/H5public.h:60:13: fatal error: mpi.h: No such file or directory
Public bug reported: TensorFlow 2.5 requires python3 h5py 3.1.0. On Ubuntu Focal arm64, the following sequence of commands fails (full log is given at the bottom) # apt-get install --install-recommends python3-pip # apt-get build-dep h5py # pip3 install h5py==3.1.0 The same sequence of commands succeeds on Ubuntu Hirsute arm64, Debian Buster arm64 and Debian Bullseye arm64. The main reason of the failure is aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DH5_USE_18_API -DNPY_NO_DEPRECATED_API=0 -I./h5py -I/usr/include/openmpi -I/usr/include/hdf5/openmpi -I/tmp/pip-install-f0eh53x0/h5py/lzf -I/tmp/pip-install-f0eh53x0/h5py/lzf/lzf -I/tmp/pip-build-env-jau4onvg/normal/lib/python3.8/site-packages/numpy/core/include -I/usr/include/python3.8 -c /tmp/pip-install-f0eh53x0/h5py/h5py/defs.c -o build/temp.linux-aarch64-3.8/tmp/pip-install-f0eh53x0/h5py/h5py/defs.o In file included from /usr/include/hdf5/openmpi/hdf5.h:22, from /tmp/pip-install-f0eh53x0/h5py/h5py/api_compat.h:27, from /tmp/pip-install-f0eh53x0/h5py/h5py/defs.c:669: /usr/include/hdf5/openmpi/H5public.h:60:13: fatal error: mpi.h: No such file or directory 60 | # include | ^~~ compilation terminated. warning: h5py/h5pl.pyx:65:14: cpdef variables will not be supported in Cython 3; currently they are no different from cdef variables warning: h5py/h5pl.pyx:66:14: cpdef variables will not be supported in Cython 3; currently they are no different from cdef variables warning: h5py/h5pl.pyx:81:14: cpdef variables will not be supported in Cython 3; currently they are no different from cdef variables error: command 'aarch64-linux-gnu-gcc' failed with exit status 1 The full log is given as attachment: ** Affects: arm-ports Importance: Undecided Status: New ** Affects: python-pip (Ubuntu) Importance: Undecided Status: New ** Tags: arm arm64 focal ** Attachment added: "Full log" https://bugs.launchpad.net/bugs/1929259/+attachment/5499312/+files/h5py-focal-arm64.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929259 Title: Focal arm64: pip3 install h5py==3.1.0 fails with /usr/include/hdf5/openmpi/H5public.h:60:13: fatal error: mpi.h: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/arm-ports/+bug/1929259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903681] Re: 20.04 LTS's OVMF_CODE.ms.fd does not boot
Thanks. I will use OVMF files from Fedora 33. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903681 Title: 20.04 LTS's OVMF_CODE.ms.fd does not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1903681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903681] Re: 20.04 LTS's OVMF_CODE.ms.fd does not boot
Thanks. I was told at the upastream https://bugzilla.tianocore.org/show_bug.cgi?id=3064#c5 that (1) Ubuntu/Debian packaging of ovmf should be built with -a X64 -a IA32, or (2) Ubuntu/Debian packaging of qemu-system-x86_64 should include -global ICH9-LPC.disable_s3=1. In their opinion, Ubuntu/Debian packaging is unsuitable. ** Bug watch added: bugzilla.tianocore.org/ #3064 https://bugzilla.tianocore.org/show_bug.cgi?id=3064 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903681 Title: 20.04 LTS's OVMF_CODE.ms.fd does not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1903681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903681] [NEW] 20.04 LTS's OVMF_CODE.ms.fd does not boot
Public bug reported: This is an upstream issue reported at https://bugzilla.tianocore.org/show_bug.cgi?id=3064 /usr/share/OVMF/OVMF_CODE.ms.fd does not boot by qemu-system-x86_64. To reproduce the symptom, on Ubuntu 20.04 amd64, do the following: cp /usr/share/OVMF/OVMF_VARS.ms.fd . qemu-system-x86_64 -enable-kvm -cpu host -machine q35,smm=on,accel=kvm -global driver=cfi.pflash01,property=secure,value=on -m 1024 -drive if=pflash,unit=0,format=raw,read-only=on,file=/usr/share/OVMF/OVMF_CODE.ms.fd -drive if=pflash,unit=1,format=raw,file=OVMF_VARS.ms.fd On the other hand, if OVMF_CODE.ms.fd in the above command is replaced by OVMF_CODE.fd, the qemu starts fine. Fedora 33 somehow built a working version of OVMF_CODE.ms.fd as OVMF_CODE.secboot.fd. Borrowing those files from Fedora 33 suppress this symptom... I hope working OVMF_CODE.ms.fd will be delivered in a future updates to Ubuntu Focal LTS. ** Affects: edk2 (Ubuntu) Importance: Undecided Status: New ** Affects: edk2 (Debian) Importance: Unknown Status: Unknown ** Tags: focal ** Bug watch added: Debian Bug tracker #973783 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973783 ** Also affects: edk2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973783 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903681 Title: 20.04 LTS's OVMF_CODE.ms.fd does not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1903681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901376] Re: xdmcp stopped working with groovy gdm3 on raspi
** Summary changed: - xdmcp stopped working with groovy gdm3 + xdmcp stopped working with groovy gdm3 on raspi ** Tags added: arm raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901376 Title: xdmcp stopped working with groovy gdm3 on raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901450] [NEW] XDMCP does not work on Raspi Groovy while it works fine on Groovy Ubuntu Mate AMD64
Public bug reported: The following configuration enables XDMCP of LightDM in Ubuntu Mate Groovy. But it fails on Groovy Raspberry Pi 64bit. [LightDM] start-default-seat=false lock-memory=false remote-sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions [XDMCPServer] enabled=true #port=177 listen-address=127.0.0.1 journalctl -e shows the following: Oct 26 07:56:41 raspi-groovy systemd[1]: Started Session 1 of user root. Oct 26 07:57:10 raspi-groovy systemd[1]: /etc/systemd/system/Xtigervnc@.service:9: Special user nobody configured, this is not safe! Oct 26 07:57:10 raspi-groovy systemd[1]: Created slice system-Xtigervnc.slice. Oct 26 07:57:10 raspi-groovy systemd[1]: Starting XVNC Per-Connection Daemon (192.168.1.75:41812)... Oct 26 07:57:10 raspi-groovy systemd[1]: Started XVNC Per-Connection Daemon (192.168.1.75:41812). Oct 26 07:57:11 raspi-groovy lightdm[893]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Oct 26 07:57:11 raspi-groovy lightdm[893]: PAM adding faulty module: pam_kwallet.so Oct 26 07:57:11 raspi-groovy lightdm[893]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Oct 26 07:57:11 raspi-groovy lightdm[893]: PAM adding faulty module: pam_kwallet5.so Oct 26 07:57:11 raspi-groovy lightdm[893]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Oct 26 07:57:11 raspi-groovy systemd[1]: Created slice User Slice of UID 108. Oct 26 07:57:11 raspi-groovy systemd[1]: Starting User Runtime Directory /run/user/108... Oct 26 07:57:11 raspi-groovy systemd-logind[530]: New session c1 of user lightdm. Oct 26 07:57:11 raspi-groovy systemd[1]: Finished User Runtime Directory /run/user/108. Oct 26 07:57:11 raspi-groovy systemd[1]: Starting User Manager for UID 108... Oct 26 07:57:11 raspi-groovy systemd[897]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0) Oct 26 07:57:12 raspi-groovy systemd[902]: gnome-systemd-autostart-condition not found: No such file or directory Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.PrintNotifications-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-gnome\x2dinitial\x2dsetup\x2dcopy\x2dworker-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.MediaKeys-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Smartcard-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dsecrets-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-at\x2dspi\x2ddbus\x2dbus-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Housekeeping-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: gnome-systemd-autostart-condition not found: No such file or directory Oct 26 07:57:12 raspi-groovy systemd[902]: gnome-systemd-autostart-condition not found: No such file or directory Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dssh-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Color-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Wwan-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-xdg\x2duser\x2ddirs-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.Rfkill-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-gnome\x2dkeyring\x2dpkcs11-autostart.service, startup phases are not supported. Oct 26 07:57:12 raspi-groovy systemd[902]: Not generating service for XDG autostart app-org.gnome.SettingsDaemon.A11ySettings-autostart.service, startup phases are
[Bug 1901376] Re: xdmcp stopped working with groovy gdm3
** Description changed: On Ubuntu Focal [xdmcp] Enable=tue ShowLocalGreeter=false in /etc/gdm3/custom.conf enabled XDMCP. But the same config. has no effect in Groovy. + This is observed on Raspberry Pi 64bit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901376 Title: xdmcp stopped working with groovy gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901376] [NEW] xdmcp stopped working with groovy gdm3
Public bug reported: On Ubuntu Focal [xdmcp] Enable=tue ShowLocalGreeter=false in /etc/gdm3/custom.conf enabled XDMCP. But the same config. has no effect in Groovy. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901376 Title: xdmcp stopped working with groovy gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1901376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901369] [NEW] whoopsie ignores https_proxy
Public bug reported: HTTP and HTTPS traffic are blocked in my network. /etc/environment has http_proxy=http://192.168.1.2:3128/ https_proxy=http://192.168.1.2:3128/ But whoopsie ignores them and says whoopsie[872]: [11:37:29] Cannot reach: https://daisy.ubuntu.com It is observed on Ubuntu Groovy RaspberryPi 64-bit Desktop. ** Affects: whoopsie Importance: Undecided Status: New ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: arm groovy ** Also affects: whoopsie (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901369 Title: whoopsie ignores https_proxy To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/1901369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897854] [NEW] groovy qemu-arm-static: /build/qemu-W3R0Rj/qemu-5.0/linux-user/elfload.c:2317: pgb_reserved_va: Assertion `guest_base != 0' failed.
Public bug reported: I do not observe the following error in Ubuntu Focal nor the qemu source downloaded and compiled on 30 September 2020. The error message of the title is reproduced by the following command and mmdebstrap fails. Host is Ubuntu Focal of amd64 architecture. root@ryutaroh-CFSZ6-1L:/var/tmp# dpkg-query -W | grep qemu-user-static qemu-user-static1:5.0-5ubuntu9 root@ryutaroh-CFSZ6-1L:/var/tmp# mmdebstrap --architectures=armhf,arm64 --variant=apt --components="main contrib non-free" --include=linux-image-arm64,udev,kmod,e2fsprogs,btrfs-progs,systemd-sysv,libpam-systemd,libnss-systemd,dbus-user-session,locales,tzdata,openssh-server,bash,apt-utils,whiptail,vim-tiny,less,man-db,wpasupplicant,crda,raspi-firmware,firmware-brcm80211,firmware-linux-free,firmware-misc-nonfree,keyboard-configuration,console-setup bullseye /tmp/test1 I: automatically chosen mode: root I: armhf cannot be executed, falling back to qemu-user I: running apt-get update... done I: downloading packages with apt... done I: extracting archives... done I: installing packages... done qemu-arm-static: /build/qemu-W3R0Rj/qemu-5.0/linux-user/elfload.c:2317: pgb_reserved_va: Assertion `guest_base != 0' failed. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: groovy ** Summary changed: - qemu-arm-static: /build/qemu-W3R0Rj/qemu-5.0/linux-user/elfload.c:2317: pgb_reserved_va: Assertion `guest_base != 0' failed. + groovy qemu-arm-static: /build/qemu-W3R0Rj/qemu-5.0/linux-user/elfload.c:2317: pgb_reserved_va: Assertion `guest_base != 0' failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897854 Title: groovy qemu-arm-static: /build/qemu-W3R0Rj/qemu-5.0/linux- user/elfload.c:2317: pgb_reserved_va: Assertion `guest_base != 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1897854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895420] [NEW] gdm3 with xdmcp does not show login box to a remote X server
Public bug reported: With a fresh installation of Ubuntu 20.04.1, adding the following to /etc/gdm/custom.conf [xdmcp] Enable=tue ShowLocalGreeter=false works fine. But with ShowLocalGreeter=true, gdm3 does not show a login box to a remote X server. journalctl -u gdm shows "GdmDisplay: Session never registered, failling" If the combination of Enable=true and ShowLocalGreeter=true is unsupported, Enable=true should also mean ShowLocalGreeter=false. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: gdm3 (Debian) Importance: Unknown Status: Unknown ** Tags: focal ** Bug watch added: Debian Bug tracker #970212 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970212 ** Also affects: gdm3 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970212 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895420 Title: gdm3 with xdmcp does not show login box to a remote X server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1895420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894356] Re: could not acquire name on session bus by simultaneous login by XDMCP and keyboard
** Bug watch added: Debian Bug tracker #969564 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969564 ** Also affects: lightdm (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969564 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894356 Title: could not acquire name on session bus by simultaneous login by XDMCP and keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1894356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894356] [NEW] could not acquire name on session bus by simultaneous login by XDMCP and keyboard
Public bug reported: This symptom is observed with Ubuntu Mate 20.04. 1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as [XDMCPServer] enabled=true and restart lightdm. 2. Login as a normal user from keyboard. 3. Login as the same user as 2 from XDMCP gives "Could not acquire name on session bus" and I cannot login from XDMCP. Without Step 2, XDMCP login succeeds. The same symptom is reported at https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001 which recommends removal of "dbus-user-session" Ubuntu package. I worked around the above issue by putting "unset DBUS_SESSION_BUS_ADDRESS" in /etc/X11/Xsession.d/ The same issue is also reported at https://bugs.launchpad.net/ubuntu-mate/+bug/1769353 ** Affects: lightdm Importance: Undecided Status: New ** Affects: ubuntu-mate Importance: Undecided Status: New ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: ubuntu ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mate Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894356 Title: could not acquire name on session bus by simultaneous login by XDMCP and keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1894356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893491] Re: groovy arm64 raspi: Unsupported platform. dpkg: error processing package flash-kernel (--configure):
** Summary changed: - groovy arm64: Unsupported platform. dpkg: error processing package flash-kernel (--configure): + groovy arm64 raspi: Unsupported platform. dpkg: error processing package flash-kernel (--configure): -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893491 Title: groovy arm64 raspi: Unsupported platform. dpkg: error processing package flash-kernel (--configure): To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1893491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893491] [NEW] groovy arm64 raspi: Unsupported platform. dpkg: error processing package flash-kernel (--configure):
Public bug reported: On Groovy arm64 running on Raspberry Pi 4B, apt-get install flash-kernel fails with the following message root@ubuntu:~# apt-get install flash-kernel Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: flash-kernel 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/35.1 kB of archives. After this operation, 206 kB of additional disk space will be used. Preconfiguring packages ... Selecting previously unselected package flash-kernel. (Reading database ... 63789 files and directories currently installed.) Preparing to unpack .../flash-kernel_3.100ubuntu2_arm64.deb ... Unpacking flash-kernel (3.100ubuntu2) ... Setting up flash-kernel (3.100ubuntu2) ... Creating config file /etc/default/flash-kernel with new version flash-kernel: deferring update (trigger activated) Processing triggers for man-db (2.9.3-2) ... Processing triggers for flash-kernel (3.100ubuntu2) ... Unsupported platform. dpkg: error processing package flash-kernel (--configure): installed flash-kernel package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: flash-kernel E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: flash-kernel (Ubuntu) Importance: Undecided Status: New ** Tags: arm64 groovy raspi ** Description changed: - On Groovy arm64, apt-get install flash-kernel fails with the following - message + On Groovy arm64 running on Raspberry Pi 4B, + apt-get install flash-kernel fails with the following message root@ubuntu:~# apt-get install flash-kernel Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following NEW packages will be installed: - flash-kernel + flash-kernel 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/35.1 kB of archives. After this operation, 206 kB of additional disk space will be used. Preconfiguring packages ... Selecting previously unselected package flash-kernel. (Reading database ... 63789 files and directories currently installed.) Preparing to unpack .../flash-kernel_3.100ubuntu2_arm64.deb ... Unpacking flash-kernel (3.100ubuntu2) ... Setting up flash-kernel (3.100ubuntu2) ... Creating config file /etc/default/flash-kernel with new version flash-kernel: deferring update (trigger activated) Processing triggers for man-db (2.9.3-2) ... Processing triggers for flash-kernel (3.100ubuntu2) ... Unsupported platform. dpkg: error processing package flash-kernel (--configure): - installed flash-kernel package post-installation script subprocess returned error exit status 1 + installed flash-kernel package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: - flash-kernel + flash-kernel E: Sub-process /usr/bin/dpkg returned an error code (1) ** Tags added: raspi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893491 Title: groovy arm64 raspi: Unsupported platform. dpkg: error processing package flash-kernel (--configure): To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1893491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893483] Re: groovy arm64: ImportError: /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block
** Tags added: arm64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893483 Title: groovy arm64: ImportError: /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1893483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893483] [NEW] groovy arm64: ImportError: /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block
Public bug reported: root@ubuntu:~# python3 Python 3.8.5 (default, Aug 2 2020, 15:09:07) [GCC 10.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import numpy >>> import cv2 Traceback (most recent call last): File "", line 1, in ImportError: /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block The above symptom is observed on Groovy arm64. I did not observe this on neither Focal arm64 nor Debian Unstable arm64. This seems unique to Groovy arm64. Related package versions are root@ubuntu:~# dpkg-query -W | grep gomp libgomp1:arm64 10.2.0-5ubuntu2 root@ubuntu:~# dpkg-query -W | grep ^python3 python3 3.8.2-0ubuntu2 python3-apport 2.20.11-0ubuntu45 python3-apt 2.1.3 python3-attr19.3.0-5 python3-blinker 1.4+dfsg1-0.3ubuntu1 python3-cachetools 4.1.1-1 python3-certifi 2020.4.5.1-1 python3-cffi-backend1.14.1-1 python3-chardet 3.0.4-7 python3-commandnotfound 20.10.1 python3-cryptography3.0-1 python3-cycler 0.10.0-3 python3-dateutil2.8.1-4 python3-dbus1.2.16-3 python3-debconf 1.5.74 python3-debian 0.1.37 python3-decorator 4.4.2-0ubuntu1 python3-dill0.3.2-1 python3-distro 1.5.0-1 python3-distro-info 0.23ubuntu1 python3-distupgrade 1:20.10.10 python3-distutils 3.8.5-1 python3-future 0.18.2-4 python3-gdbm:arm64 3.8.5-1 python3-gi 3.36.0-4 python3-grpcio 1.30.2-2build1 python3-h5py2.10.0-9 python3-h5py-serial 2.10.0-9 python3-httplib20.18.1-1 python3-idna2.10-1 python3-importlib-metadata 1.6.0-2 python3-jeepney 0.4.3-1 python3-jinja2 2.11.2-1 python3-json-pointer2.0-0ubuntu1 python3-jsonpatch 1.25-3 python3-jsonschema 3.2.0-0ubuntu2 python3-jwt 1.7.1-2ubuntu2 python3-keyring 21.3.0-1 python3-kiwisolver 1.2.0-1 python3-launchpadlib1.10.13-1 python3-lazr.restfulclient 0.14.2-2build1 python3-lazr.uri1.0.5-1 python3-lib2to3 3.8.5-1 python3-markdown3.2.2-2 python3-markupsafe 1.1.1-1 python3-matplotlib 3.2.2-1 python3-minimal 3.8.2-0ubuntu2 python3-more-itertools 4.2.0-3 python3-nacl1.4.0-1 python3-newt:arm64 0.52.21-4ubuntu2 python3-numpy 1:1.18.4-1ubuntu1 python3-oauthlib3.1.0-2 python3-opencv 4.2.0+dfsg-6build3 python3-openssl 19.1.0-2 python3-pexpect 4.6.0-3 python3-pil:arm64 7.2.0-1 python3-pip 20.1.1-2 python3-pkg-resources 46.1.3-1 python3-problem-report 2.20.11-0ubuntu45 python3-protobuf3.12.3-2ubuntu2 python3-ptyprocess 0.6.0-1ubuntu1 python3-pyasn1 0.4.8-1 python3-pyasn1-modules 0.2.1-1 python3-pydot 1.4.1-3 python3-pymacaroons 0.13.0-3 python3-pyparsing 2.4.7-1 python3-pyrsistent:arm640.15.5-1build1 python3-requests2.23.0+dfsg-2 python3-requests-oauthlib 1.0.0-1.1build1 python3-requests-unixsocket 0.2.0-2 python3-rsa 4.0-4 python3-scipy 1.4.1-2 python3-secretstorage 3.1.2-1 python3-serial 3.4-5.1 python3-setuptools 46.1.3-1 python3-simplejson 3.17.0-1 python3-six 1.15.0-1 python3-software-properties 0.99.3 python3-systemd 234-3build2 python3-termcolor 1.1.0-3 python3-tqdm4.48.2-1 python3-update-manager 1:20.10.1 python3-urllib3 1.25.9-1 python3-wadllib 1.3.4-1 python3-werkzeug1.0.1+dfsg1-2 python3-wheel 0.34.2-1 python3-wrapt 1.11.2-2build1 python3-yaml5.3.1-2 python3-zipp1.0.0-3 python3.8 3.8.5-2 python3.8-minimal 3.8.5-2 ** Affects: opencv (Ubuntu) Importance: Undecided Status: New ** Tags: groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893483 Title: groovy arm64: ImportError: /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1893483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890881] Re: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container
Thank you very much. qemu-user-static1:5.0-5ubuntu5~ppa2 also works fine for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890881 Title: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890881] Re: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container
> Eventually I found I need to unimport it after exchanging the binary. > Then I get it to use the new version. Yes... I also needed to run "systemctl restart binfmt-format", which looks equivalent. After qemu-user-static package is upgraded, user space emulation sometimes fails, so I suspect that qemu-user(-static) upgrade script also needs to run "systemctl restart binfmt-format" or equivalent. But I am not completely sure and I have filed no bug report to neither Ubuntu nor Debian... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890881 Title: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890881] Re: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container
@paelzer, I got below. This seems to mean that #LP1887606 is fixed in 1:4.2-3ubuntu6.4~ppa1 while #LP1890881 remains. By the way, debian Bullseye 1:5.1+dfsg-0exp1 worked fine as far as I see. Preparing to unpack .../qemu-user-static_1%3a4.2-3ubuntu6.4~ppa1_amd64.deb ... Unpacking qemu-user-static (1:4.2-3ubuntu6.4~ppa1) over (1:4.2-3ubuntu6.3) ... Setting up qemu-user-static (1:4.2-3ubuntu6.4~ppa1) ... Processing triggers for man-db (2.9.1-1) ... root@ryutaroh-CFSZ6-1L:/home/ryutaroh# systemctl restart binfmt-support root@ryutaroh-CFSZ6-1L:/home/ryutaroh# systemd-nspawn -M armhf-focal -b Spawning container armhf-focal on /var/lib/machines/armhf-focal. Press ^] three times within 1s to kill container. systemd 245.4-4ubuntu3 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Detected virtualization systemd-nspawn. Detected architecture arm. Welcome to Ubuntu 20.04 LTS! Set hostname to . Caught , dumped core as pid 3. Exiting PID 1... Container armhf-focal failed with error code 255. root@ryutaroh-CFSZ6-1L:/home/ryutaroh# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890881 Title: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890881] Re: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container
> you could give it a try on focal right? Yes, I can and I will. > I'm still unsure what we should do about this bug 1890881 then without > having an isolated fix, but one step at a time ... I had a similar feeling: After seeing #LP1886811 fixed in upstream QEMU, "systemd-nspawn -b" started fine on some architectures and failed on others with self-compiled QEMU binaries. But failing architectures were not used in my job, I did not file a but report... By the way, QEMU 5.1.0 was released. https://download.qemu.org/qemu-5.1.0.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890881 Title: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890881] Re: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container
Hi @paelzer, what I had done was testing "netlink RTM_SETLINK command" against the latest git source of qemu (around July 2020), and seeing that self-compiled version from the source worked fine. I had never seen a working Ubuntu qemu-user-static package that can start an armhf container on an amd64 host... I just saw "fix released" status, so I assumed someone verified the Ubuntu package... If an urgent fix is not required (I think nobody complains this issue here so very few people seem to use LXC/systemd-nspawn containers of armhf on amd64, which is in my opinion convenient for testing Raspberry Pi SD card images), then we can just wait the official release of qemu 5.1, which should not have this issue... If fix of this issue is important (I am doubting if it is), then https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606 still exists in qemu-user-static 1:4.2-3ubuntu6.3 in focal-updates, armhf container cannot be used on amd64 Focal host, and a fix in Focal is desirable. I cannot see if this issue #LP1890881 exists in Focal or not as #LP1887606 suppress this issue... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890881 Title: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890881] Re: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container
** Bug watch added: Debian Bug tracker #968088 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968088 ** Also affects: qemu (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968088 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890881 Title: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890881] [NEW] qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container
Public bug reported: This is somewhat similar but different from https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606 The following bug does not occur with the upstream version qemu-5.1.0-rc3 built from it source code. How to reproduce (as root) on amd64 host running Ubuntu: apt-get install -t groovy qemu-user-static (the Ubuntu package version is 1:5.0-5ubuntu4) mmdebstrap --components="main restricted universe multiverse" --variant=standard --architectures=armhf focal /var/lib/machines/armhf- focal http://ports.ubuntu.com/ubuntu-ports/ systemd-nspawn -D /var/lib/machines/armhf-focal -b # systemd-nspawn -M armhf-focal -b Spawning container armhf-focal on /var/lib/machines/armhf-focal. Press ^] three times within 1s to kill container. systemd 245.4-4ubuntu3 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Detected virtualization systemd-nspawn. Detected architecture arm. Welcome to Ubuntu 20.04 LTS! Set hostname to . Caught , dumped core as pid 3. Exiting PID 1... Container armhf-focal failed with error code 255. Afain, with qemu-5.1.0-rc3, the container starts fine. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890881 Title: qemu-user-static 1:5.0-5ubuntu4 in groovy does not start armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1890881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887606] Re: armhf focal guest container fails on amd64 host with Failed to enqueue loopback interface start request: Operation not supported
Fix released: https://bugs.launchpad.net/qemu/+bug/1886811/comments/6 ** Changed in: qemu (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887606 Title: armhf focal guest container fails on amd64 host with Failed to enqueue loopback interface start request: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887606] Re: armhf focal guest container fails on amd64 host with Failed to enqueue loopback interface start request: Operation not supported
** Description changed: How to reproduce (as root) on amd64 host running Ubuntu: apt-get install -t groovy qemu-user-static mmdebstrap --components="main restricted universe multiverse" --variant=standard --architectures=armhf focal /var/lib/machines/armhf- focal http://ports.ubuntu.com/ubuntu-ports/ - systemd-nspawn -D /var/lib/machines/armhf-focal + systemd-nspawn -D /var/lib/machines/armhf-focal -b Then I get: Spawning container armhf-focal on /var/lib/machines/armhf-focal. Press ^] three times within 1s to kill container. systemd 245.4-4ubuntu3 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Detected virtualization systemd-nspawn. Detected architecture arm. Welcome to Ubuntu 20.04 LTS! Set hostname to . Failed to enqueue loopback interface start request: Operation not supported Caught , dumped core as pid 3. Exiting PID 1... Container armhf-focal failed with error code 255. This is an upstream issue reported at https://bugs.launchpad.net/qemu/+bug/1886811 Workaround patch is also available at https://bugs.launchpad.net/qemu/+bug/1886811 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887606 Title: armhf focal guest container fails on amd64 host with Failed to enqueue loopback interface start request: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606 ** No longer affects: qemu (Ubuntu) ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886811 Title: systemd complains Failed to enqueue loopback interface start request: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1886811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887606] [NEW] armhf focal guest container fails on amd64 host with Failed to enqueue loopback interface start request: Operation not supported
Public bug reported: How to reproduce (as root) on amd64 host running Ubuntu: apt-get install -t groovy qemu-user-static mmdebstrap --components="main restricted universe multiverse" --variant=standard --architectures=armhf focal /var/lib/machines/armhf- focal http://ports.ubuntu.com/ubuntu-ports/ systemd-nspawn -D /var/lib/machines/armhf-focal Then I get: Spawning container armhf-focal on /var/lib/machines/armhf-focal. Press ^] three times within 1s to kill container. systemd 245.4-4ubuntu3 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) Detected virtualization systemd-nspawn. Detected architecture arm. Welcome to Ubuntu 20.04 LTS! Set hostname to . Failed to enqueue loopback interface start request: Operation not supported Caught , dumped core as pid 3. Exiting PID 1... Container armhf-focal failed with error code 255. This is an upstream issue reported at https://bugs.launchpad.net/qemu/+bug/1886811 Workaround patch is also available at https://bugs.launchpad.net/qemu/+bug/1886811 ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: focal groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887606 Title: armhf focal guest container fails on amd64 host with Failed to enqueue loopback interface start request: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1887606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886811] Re: systemd complains Failed to enqueue loopback interface start request: Operation not supported
** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886811 Title: systemd complains Failed to enqueue loopback interface start request: Operation not supported To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1886811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857542] [NEW] lxc-checkpoint needs the criu package
Public bug reported: lxc-checkpoint needs criu to be installed but the criu package is absent in eoan and focal (criu exists in disco and bionic). ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857542 Title: lxc-checkpoint needs the criu package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
lxc-checkpoint in the latest github master branch does not work under pure cgroup v2 as https://github.com/lxc/lxc/issues/3240 ** Bug watch added: LXC bug tracker #3240 https://github.com/lxc/lxc/issues/3240 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
https://github.com/lxc/lxd/issues/6587 When Ubuntu Eoan is booted with systemd.unified_cgroup_hierarchy, LXD cannot run Ubuntu Eoan in its container, but a small change to lxd/lxd/container_lxc.go enables LXD to operate as usual. ** Bug watch added: LXD bug tracker #6587 https://github.com/lxc/lxd/issues/6587 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
https://github.com/lxc/lxc/issues/3221 Another LXC-container-doesn't -start-at-all type issue also observed on Ubuntu Eoan with systemd.unified_cgroup_hierarchy as well as Fedora 31. ** Bug watch added: LXC bug tracker #3221 https://github.com/lxc/lxc/issues/3221 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
https://github.com/lxc/lxc/issues/3198#issuecomment-562252884 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
This was reported to the upstream https://github.com/lxc/lxc/issues/3198 The purpose of libpam-cgfs is only chowning some CGroup directories to the login user. When Linux is booted with systemd.unified_cgroup_hierarchy, /sys/fs/cgroup/user.slice/user-$UID.slice/session-nnn.scope is not chowned to a login user. So libpam-cgfs completely fails to function under cgroup v2. ** Also affects: lxcfs (Ubuntu) Importance: Undecided Status: New ** Bug watch added: LXC bug tracker #3198 https://github.com/lxc/lxc/issues/3198 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
When Ubuntu Eoan is started with systemd.unified_cgroup_hierarchy, lxc- start (version 3.0.4 packaged by Eoan) cannot be used in its default setting. It is a combination of unsuitable default configuration and an upstream bug in LXC 3.0.4. For detail, please refer to https://github.com/lxc/lxc/issues/3183 ** Project changed: lxc => lxc (Ubuntu) ** Changed in: lxc (Ubuntu) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
** Bug watch added: LXC bug tracker #3183 https://github.com/lxc/lxc/issues/3183 ** Also affects: lxc via https://github.com/lxc/lxc/issues/3183 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1850667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
