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
** 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:
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-
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/De
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:
ht
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 not
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/
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
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
B
** 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
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/issu
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-
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:
ar
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 inst
** 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 yo
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 amd
> 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 fin
@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
> Eventually I found I need to unimport&import 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 susp
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 n
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
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 notificatio
** 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 Ub
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
[
** 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:
** 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 r
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-port
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.l
** 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.ubunt
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
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
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/aarch6
** 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 man
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 in
** 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
B
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 sess
** 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
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 n
38 matches
Mail list logo
