The container has since been restarted (by issuing a 'reboot' inside the
container), which "unstuck" lxc-ls, it's now behaving normally. If it
happens again I'll see what I can see. It's not the first time I've seen
this happen.
LXC has not been upgraded since the container was started, no.
The c
Quoting Serge Hallyn
> Perhaps after a (reasonably long) timeout we should assume
> it is dead, hard-kill the container (in this case the owner of the
> command socket), and continue.
I'm seeing this behaviour happen in Vivid although in my case the
"stuck" container is perfectly responsive and is
Correction, I meant to say "I'm seeing this behaviour happen in Trusty"
not Vivid.
--
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/1377973
Title:
lxc-destroy/lxc-stop gets stuc
Retested with latest firmware - no change.
--
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/1341022
Title:
[Latitude E7240, Realtek ALC292, Mic, Internal] Internal Mic n
(there's no dock attached to the system - I don't even own one!)
--
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/1341022
Title:
[Latitude E7240, Realtek ALC292, Mic, In
Public bug reported:
Sound Settings panel shows "Headset microphone" and "Dock microphone".
Headset when plugged in works fine (the little dialogue pops up etc).
Internal microphone is not visible anywhere within the GUI.
alsamixer "sees" the internal microphone and I can adjust its levels but
th
6 matches
Mail list logo
