To be clear - the per-container 'command' handler, which is a part of
the lxc-start process, cannot multiplex, so if one command were to be,
say, suspended while having an open connection to the handler, or if
lxc-start itself were to be hung, that could cause lxc-info to hang (as
it was doing for
Could you please try
sudo apt-get install python3-dbg lxc-dbg apport-retrace
sudo apport-retrace -g _usr_bin_lxc-ls.0.crash
(type 'where', show the output)
Or, if that doesn't seem to work,
mkdir yyy
apport-unpack _usr_bin_lxc-ls.0.crash yyy
cd yyy
gdb python3 CoreDump
where
--
You received t
So I followed your suggestions for retracing he apport dump and got
these results (not much I'm afraid): http://paste.ubuntu.com/5645895/
(1st option); http://paste.ubuntu.com/5645890/ (2nd option).
I'll try replicating the same steps I did before from scratch to see if
I can reproduce it later to
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/
