Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2019-08-15 Thread Olivier
Hello, I have the same bug as Svetlana... $ sudo modprobe binder_linux# OK $ sudo modprobe ashmem_linux# OK $ sudo service anbox-container-manager start# OK $ ls /var/lib/anbox/ android_amd64.img (That file was downloaded from

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2019-07-04 Thread Alberto Luaces Fernández
What is the status of the user unit? systemctl --user status anbox-session-manager Can you verify both kernel modules are loaded correctly? ls /dev/{binder,ashmem}

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-29 Thread Svetlana Tkachenko
You are right, with wmaker I don't have a desktop icon but the .desktop file gives me the command to run. $ anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity [ 2018-12-29 22:38:20] [launch.cpp:214@operator()] Session manager failed to become ready $

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-29 Thread Shengjing Zhu
Control: severity -1 wishlist On Sat, Dec 29, 2018 at 6:23 PM Svetlana Tkachenko wrote: > now 'anbox session-manager' gives no error but it shows no android screen > either, it would be nice to have usage information included in the > documentation somewhere. > This is expected behaviour. And

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-29 Thread Svetlana Tkachenko
Hello again, Sorry I missed it that the readme says " *Then start the anbox-container-manager.service and the * *anbox-session-manager.service, anbox-session-manager.service is a systemd * *user service.*" so now I did $ sudo service anbox-container-manager start $ sudo service

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-28 Thread Svetlana Tkachenko
Thanks Shengjing, 1) the readme says "In order to run Android system inside container, you need two kernel modules: ashmem_linux and binder_linux. Since Debian kernel 4.17, these two modules are enabled. You can find theme at, /lib/modules/`uname -r`/kernel/drivers/android/binder_linux.ko and

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-28 Thread Shengjing Zhu
Svetlana Tkachenko 于 2018年12月29日周六 09:59写道: > File/directory /use/share/doc/anbox/ does not exist. > Sorry for the typo, sending from my mobile phone. It's /usr/, you should also find it in package's description. >

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-28 Thread Svetlana Tkachenko
File/directory /use/share/doc/anbox/ does not exist.

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-28 Thread Shengjing Zhu
Svetlana Tkachenko 于 2018年12月28日周五 19:05写道: > > Condition: start condition failed at Fri 2018-12-28 15:00:14 AEDT; 7h ago > Please read /use/share/doc/anbox/README.Debian You should download an Android image first.

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-28 Thread Svetlana Tkachenko
~$ systemctl status anbox-container-manager ● anbox-container-manager.service - Anbox Container Manager Loaded: loaded (/lib/systemd/system/anbox-container-manager.service; enabled Active: inactive (dead) Condition: start condition failed at Fri 2018-12-28 15:00:14 AEDT; 7h ago Docs:

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-27 Thread Shengjing Zhu
Svetlana Tkachenko 于 2018年12月28日周五 12:06写道: > Package: anbox > Version: 0.0~git20181210-1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate > *** > > I ran "anbox session-manager" and received this error: > > ~$ anbox

Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency

2018-12-27 Thread Svetlana Tkachenko
Package: anbox Version: 0.0~git20181210-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I ran "anbox session-manager" and received this error: ~$ anbox session-manager [ 2018-12-28 04:03:29]