[Touch-packages] [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 not
[Touch-packages] [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 Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1901369 Title: whoopsie ignores https_proxy Status in Whoopsie: New Status in whoopsie package in Ubuntu: New Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/1901369/+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 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 Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1894356 Title: could not acquire name on session bus by simultaneous login by XDMCP and keyboard Status in Light Display Manager: New Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: New Status in lightdm package in Debian: Unknown Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1894356/+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 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 Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1894356 Title: could not acquire name on session bus by simultaneous login by XDMCP and keyboard Status in Light Display Manager: New Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1894356/+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 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 Touch seeded packages, which is subscribed to opencv in 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 Status in opencv package in Ubuntu: New Bug description: 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:arm6410.2.0-5ubuntu2 root@ubuntu:~# dpkg-query -W | grep ^python3 python3 3.8.2-0ubuntu2 python3-apport2.20.11-0ubuntu45 python3-apt 2.1.3 python3-attr 19.3.0-5 python3-blinker 1.4+dfsg1-0.3ubuntu1 python3-cachetools4.1.1-1 python3-certifi 2020.4.5.1-1 python3-cffi-backend 1.14.1-1 python3-chardet 3.0.4-7 python3-commandnotfound 20.10.1 python3-cryptography 3.0-1 python3-cycler0.10.0-3 python3-dateutil 2.8.1-4 python3-dbus 1.2.16-3 python3-debconf 1.5.74 python3-debian0.1.37 python3-decorator 4.4.2-0ubuntu1 python3-dill 0.3.2-1 python3-distro1.5.0-1 python3-distro-info 0.23ubuntu1 python3-distupgrade 1:20.10.10 python3-distutils 3.8.5-1 python3-future0.18.2-4 python3-gdbm:arm643.8.5-1 python3-gi3.36.0-4 python3-grpcio1.30.2-2build1 python3-h5py 2.10.0-9 python3-h5py-serial 2.10.0-9 python3-httplib2 0.18.1-1 python3-idna 2.10-1 python3-importlib-metadata1.6.0-2 python3-jeepney 0.4.3-1 python3-jinja22.11.2-1 python3-json-pointer 2.0-0ubuntu1 python3-jsonpatch 1.25-3 python3-jsonschema3.2.0-0ubuntu2 python3-jwt 1.7.1-2ubuntu2 python3-keyring 21.3.0-1 python3-kiwisolver1.2.0-1 python3-launchpadlib 1.10.13-1 python3-lazr.restfulclient0.14.2-2build1 python3-lazr.uri 1.0.5-1 python3-lib2to3 3.8.5-1 python3-markdown 3.2.2-2 python3-markupsafe1.1.1-1 python3-matplotlib3.2.2-1 python3-minimal 3.8.2-0ubuntu2 python3-more-itertools4.2.0-3 python3-nacl 1.4.0-1 python3-newt:arm640.52.21-4ubuntu2 python3-numpy 1:1.18.4-1ubuntu1 python3-oauthlib 3.1.0-2 python3-opencv4.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-report2.20.11-0ubuntu45 python3-protobuf 3.12.3-2ubuntu2 python3-ptyprocess0.6.0-1ubuntu1 python3-pyasn10.4.8-1 python3-pyasn1-modules0.2.1-1 python3-pydot 1.4.1-3 python3-pymacaroons 0.13.0-3 python3-pyparsing 2.4.7-1 python3-pyrsistent:arm64 0.15.5-1build1 python3-requests 2.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-serial3.4-5.1 python3-setuptools46.1.3-1 python3-simplejson3.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-tqdm 4.48.2-1 python3-update-manager1:20.10.1 python3-urllib3 1.25.9-1 python3-wadllib 1.3.4-1 python3-werkzeug 1.0.1+dfsg1-2 python3-wheel 0.34.2-1 python3-wrapt 1.11.2-2build1 python3-yaml 5.3.1-2 python3-zipp 1.0.0-3 python3.8 3.8.5-2 python3.8-minimal 3.8.5-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1893483/+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 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 Touch seeded packages, which is subscribed to opencv in 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 Status in opencv package in Ubuntu: New Bug description: 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:arm6410.2.0-5ubuntu2 root@ubuntu:~# dpkg-query -W | grep ^python3 python3 3.8.2-0ubuntu2 python3-apport2.20.11-0ubuntu45 python3-apt 2.1.3 python3-attr 19.3.0-5 python3-blinker 1.4+dfsg1-0.3ubuntu1 python3-cachetools4.1.1-1 python3-certifi 2020.4.5.1-1 python3-cffi-backend 1.14.1-1 python3-chardet 3.0.4-7 python3-commandnotfound 20.10.1 python3-cryptography 3.0-1 python3-cycler
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1857542 Title: lxc-checkpoint needs the criu package Status in lxc package in Ubuntu: New Bug description: lxc-checkpoint needs criu to be installed but the criu package is absent in eoan and focal (criu exists in disco and bionic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857542/+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 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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxcfs package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+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 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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxcfs package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+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 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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxcfs package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+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 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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxcfs package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+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 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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxcfs package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+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 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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+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
