1) Nautilus error - "The destination is read-only".
® Linux Deploy (Post # 18199163)2) Constant CPU usage by the dbus service (Debian / Ubuntu).
® Linux Deploy (Post # 18821886)3) After installing and running GNU / Linux, I cannot switch to root.
One of the reasons may be an error related to the nosuid mount option of the partition on which the application's working environment is located. To solve this problem, you can go two ways. 1. Change user in LD parameters to root (Parameters ->Username) and reconfigure. 2. Change the directory of the working environment to / system / linux (Settings ->Environment directory) and update the environment. Before updating the environment, you need to remount the / system partition for writing with the command mount -o rw, remount / system from any Android terminal under the root. At the same time on the / system partition should be at least 20 MB of free space.
4) Environment update or installation does not start, errors appear in debug mode.
Linux Deploy can also constantly display the message "The container is already mounted" or nothing at all. In debug mode, "Permission denied", "Socket operation on non-socket", or other errors may appear.
Solution: Install Compatible
® BusyBoxIn / system / xbin, add to "Settings ->PATH "(" Settings ->PATH variable ") path / system / xbin, update environment" Settings ->Update environment "(" Settings ->Update ENV "). Before updating the environment, it is desirable to reboot the device. Then in the container parameters select" Parameters ->File system ->Autodetection "(" Properties ->File system ->Auto ") and" Options ->Image Size (MB) ->2000 "(" Propetries ->Image size (MB) ->2000 "), because busybox mke2fs does not support the" -t "parameter to specify the file system type and does not support images larger than 2 GB. After that, you can launch the new installation" Menu - Install "(" Menu ->Install ").
5) Error during image creation.
Making new disk image (4095 MB) ... fail
dd: opening `/storage/emulated/0/linux.img ': No such file or directory
Replace in path 0 with legacy.
6) Error when installing the application through Google Play.
Message: "Unknown error code during installation of application 24".
Decision:
http://lifehacker.ru/2...ozhenij-v-google-play/In short, you need to delete the residual application files from the device (if it has already been installed before). To do this, delete the directory: /data/data/ru.meefik.linuxdeploy
7) LD does not see the memory card, during the installation an error "Read-only file system" appears, creating an image on the memory card ends with an error.
This can happen if the system uses namespace splitting. In this case, the memory card is mounted under some user, and when switching to root, the mounted devices are no longer visible. The SuperSU utility has an option that can help solve this problem. To do this, remove the flag "SuperSU ->Settings ->Create namespace separation ".
® Linux Deploy (Post meefik # 40263455)8) "Couldn't find these debs: 0" error (version 1.x) appears
In Android, you need to set the correct permissions for the pkgdetails file.
Through the terminal it can be done like this:
chmod 755 /data/data/en.meefik.linuxdeploy/linux/deploy/debootstrap/pkgdetails
9) Error launching LXDE "No session for pid"
® Linux Deploy (Post _sudo_ # 43416527)10) Error "PERM_ROOT: setresuid (0, -1, -1): Premission denied"
® Linux Deploy (Post meefik # 55082689)11) Error "chroot: can't execute '/ debootstrap / debootstrap': Permission denied"
® Linux Deploy (Post ottiwell # 71213504)Instead of '/ debootstrap / debootstrap' there may be another command, depending on the distribution.
The problem is related to the lack of rights to execute files on a partition. When installing in a directory, do not use an SD card with the FAT file system. If installation takes place in / data, then the / data section should be mounted with suid, exec, dev rights.
mount -o remount suid, exec, dev / data