proot fails in zesty: "proot error: can't write the loader: Bad address"

Bug #1651564 reported by Larry Price
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
proot (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After creating a fakechroot in latest zesty this morning (20 Dec 2016), running `proot -b /usr/lib/locale -S $HOME/.cache/libertine-container/zesty/rootfs ldconfig.REAL` results in the following error:

    proot error: can't write the loader: Bad address
    proot error: execve("/sbin/ldconfig.REAL"): No such file or directory
    proot info: possible causes:
      * the program is a script but its interpreter (eg. /bin/sh) was not found;
      * the program is an ELF but its interpreter (eg. ld-linux.so) was not found;
      * the program is a foreign binary but qemu was not specified;
      * qemu does not work correctly (if specified);
      * the loader was not found or doesn't work.
    fatal error: see `proot --help`.
    proot error: can't chmod '/tmp/proot-14984-arcVpK': No such file or directory

We think this may be related to this commit, which has not been brought into the zesty proot package yet: https://github.com/proot-me/PRoot/commit/f2839cff8e4fd1ee7a3ab6c005f669e24b670f32

ubuntu zesty
proot 5.1.0-1.1
linux-4.9.0-11-generic

Tags: zesty
Ken Sharp (kennybobs)
tags: added: zesty
Revision history for this message
Ken Sharp (kennybobs) wrote :

Can you recreate this on a supported version of Ubuntu?

Changed in proot (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for proot (Ubuntu) because there has been no activity for 60 days.]

Changed in proot (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.