Please can you confirm if still an issue on lxd 5.21/stable as this is
the current supported version. Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2057927
Title:
This is fixed now in latest/edge of lxd for unprivileged containers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2046486
Title:
units with credentials fail in LXD conta
I mention it only for the purposes of testing and for keeping this
ticket informed, i was not suggesting you run production on latest/edge
naturally.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://b
As for when it hits stable channels, im assuming the most important ones
are latest/stable and 5.21/stable (which is the current lts series).
Ill need to check with mihalicyn if the fix relies on a thr lxd snap
switching base to core24.
If so we've got some more issues to resolve first, but if no
OK excellent, so as discussed we'll need to vendor the upstream version
of apparmor into the LXD snap (so we don't have to prematurely rush the
core24 switch) along with the cherry-picks you identified in the GH
issue.
I'll work on landing that in latest/edge first and then we can perform
an inter
Oracular unprivileged containers should now be working OK in
latest/candidate channel.
In latest/edge and latest/candidate we have added a vendored version of
the apparmor parser (v4.0.2).
If our tests pass OK then will proceed to deploy latest/candidate to
latest/stable on Monday.
--
You recei
Apparmor fixes for running Oracular unprivileged containers from
`ubuntu-daily:24.10` are being progressively rolled out to the
`latest/stable` channel now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
ht
We are rolling out fixes to 5.21/stable for this now (snap refresh lxd
--channel=5.21/stable --cohort="+" will get it by bypassing progressive
rollout).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
Hi all, what is the latest on this? It appears to not have been fixed in
Ubuntu 24.04.1
https://github.com/canonical/lxd/issues/13389#issuecomment-2319129052
** Bug watch added: github.com/canonical/lxd/issues #13389
https://github.com/canonical/lxd/issues/13389
--
You received this bug noti
I agree with Stéphane, it would be better to get the LXC_DEVEL issue
fixed quickly and then deal with the packaging refresh separately.
--
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/
I'm running latest HWE kernel on 20.04 (5.4.0-65).
If I connect a microphone via USB or the headphone socket then it works
(in chromium too).
But if I disconnect the microphone then Gnome doesn't detect any built-
in microphone.
As I've made some changes to my modules settings, I think I'll wipe
I just tried this now on a freshly installed Ubuntu 20.04 with kernel
5.8.0-41-generic and it works great in both Gnome and in Chromium. Happy
to mark this resolved.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
I've been able to re-create this using fresh install of Ubuntu 18.04
without using LXC or LXD, but just using network namespaces.
Setup 2 namespaces with IPVLAN:
ip netns add ns1
ip link add name ipv1 link enp0s3 type ipvlan mode l3s
ip link set dev ipv1 netns ns1
ip netns exec ns1 ip addr add 10
LXD depends on the nft tool when iptables-legacy rules are not in use
(as the iptables-nft tools do not provide all the functionality it
depends on).
However the nft tool is bundled in the snap package so this should be
fine.
--
You received this bug notification because you are a member of Ubun
Public bug reported:
On Focal Fossa the microphone is recognised but doesn't work.
Chromium shows the microphone as present but off, and if it is renabled
it goes off again after a couple of seconds.
Chromium logs this error:
[ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected,
I've tried audacity and firefox too and no sound can be recorded.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1868330
Title:
Lenovo ThinkPad-X1-Carbon-7th Gen micro
Thanks Hui, for the quick response. I've installed that package, and
indeed, the microphone now works in apps like Audacity. Great.
However it still does not work in Chromium in Google Meet, the
microphone appears as a device to use, but it shows as "disabled" and so
when I unmute in Google Meet i
I tried installing that kernel and rebooting but I get a grub error
"cant find command hwmatch" and cannot boot into that kernel.
linux-headers-5.6.0-050600rc6_5.6.0-050600rc6.202003200818_all.deb
linux-headers-5.6.0-050600rc6-generic_5.6.0-050600rc6.202003200818_amd64.deb
linux-image-unsigned-5.6
Ah yeah that could be the issue, is there a legacy package one can
install to provide the old API perhaps?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1868330
Title:
19 matches
Mail list logo
