[Bug 1649649] Re: Programs ran using proot fail on arm64 xenial chroots

2017-04-12 Thread Christopher Townsend
Don't think this is relevant anymore. Marking 'Won't Fix'. ** Changed in: libertine/devel Status: Triaged => Won't Fix ** Changed in: libertine/devel Assignee: Christopher Townsend (townsend) => (unassigned) ** Changed in: libertine/devel Milestone: 1.8 => None ** Changed in:

[Bug 1649649] Re: Programs ran using proot fail on arm64 xenial chroots

2017-03-10 Thread Christopher Townsend
** Changed in: libertine/devel Milestone: 1.7 => 1.8 ** Changed in: libertine/trunk Milestone: 1.7 => 1.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649649 Title: Programs ran using

[Bug 1649649] Re: Programs ran using proot fail on arm64 xenial chroots

2017-02-15 Thread Christopher Townsend
** Changed in: libertine Milestone: 1.6 => 1.7 ** Changed in: libertine/trunk Milestone: 1.6 => 1.7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649649 Title: Programs ran using proot

[Bug 1649649] Re: Programs ran using proot fail on arm64 xenial chroots

2017-01-12 Thread Christopher Townsend
** Changed in: libertine Milestone: 1.5 => 1.6 ** Changed in: libertine/trunk Milestone: 1.5 => 1.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649649 Title: Programs ran using proot

[Bug 1649649] Re: Programs ran using proot fail on arm64 xenial chroots

2017-01-11 Thread Christopher Townsend
Looks like we have hit a roadblock with this. Looks to be issues both with proot and some kernels such as the one on frieza. We may just have to require kernels on any device to support unprivileged LXC's, ie the 3.13 kernel. ** Changed in: libertine/devel Status: In Progress => Triaged

[Bug 1649649] Re: Programs ran using proot fail on arm64 xenial chroots

2016-12-13 Thread Christopher Townsend
Some more details when running strace on proot (truncated output): ... ptrace(PTRACE_SETREGSET, 11208, NT_PRSTATUS, [{0x2437f168, 272}]) = 0 ptrace(PTRACE_SYSCALL, 11208, NULL, SIG_0) = 0 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_TRAPPED, si_pid=11208, si_uid=32011, si_status=SIGTRAP,