Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency
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 https://build.anbox.io/android-images/2018/07/19) $ sudo service anbox-session-manager start # NOT OK Failed to start anbox-session-manager.service: Unit anbox-session manager.service not found. I don't know how to diagnose or to understand more. -- Olivier --- $ anbox system-info version: 0.0~git20190124-1-Debian cpu: arch: x86 brand: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz features: - aes os: name: Debian GNU/Linux version: snap-based: false kernel: version: Linux version 4.18.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-30)) #1 SMP Debian 4.18.10-2 (2018-11-02) binder: true ashmem: true graphics: egl: vendor: Mesa Project version: 1.4 (DRI2) extensions: - EGL_ANDROID_native_fence_sync - EGL_CHROMIUM_sync_control - EGL_EXT_create_context_robustness - EGL_EXT_image_dma_buf_import - EGL_EXT_image_dma_buf_import_modifiers - EGL_KHR_config_attribs - EGL_KHR_create_context - EGL_KHR_create_context_no_error - EGL_KHR_fence_sync - EGL_KHR_get_all_proc_addresses - EGL_KHR_gl_colorspace - EGL_KHR_gl_renderbuffer_image - EGL_KHR_gl_texture_2D_image - EGL_KHR_gl_texture_3D_image - EGL_KHR_gl_texture_cubemap_image - EGL_KHR_image - EGL_KHR_image_base - EGL_KHR_image_pixmap - EGL_KHR_no_config_context - EGL_KHR_reusable_sync - EGL_KHR_surfaceless_context - EGL_KHR_wait_sync - EGL_MESA_configless_context - EGL_MESA_drm_image - EGL_MESA_image_dma_buf_export - EGL_NOK_swap_region - EGL_NOK_texture_from_pixmap - EGL_NV_post_sub_buffer - EGL_WL_bind_wayland_display gles2: vendor: Intel Open Source Technology Center vendor: OpenGL ES 3.1 Mesa 18.2.8 extensions: - GL_EXT_blend_minmax - GL_EXT_multi_draw_arrays - GL_EXT_texture_filter_anisotropic - GL_EXT_occlusion_query_boolean - GL_EXT_texture_compression_dxt1 - GL_EXT_texture_format_BGRA - GL_OES_compressed_ETC1_RGB8_texture - GL_OES_depth24 - GL_OES_element_index_uint - GL_OES_fbo_render_mipmap - GL_OES_mapbuffer - GL_OES_rgb8_rgba8 - GL_OES_standard_derivatives - GL_OES_stencil8 - GL_OES_texture_3D - GL_OES_texture_float - GL_OES_texture_float_linear - GL_OES_texture_half_float - GL_OES_texture_half_float_linear - GL_OES_texture_npot - GL_OES_vertex_half_float - GL_EXT_texture_sRGB_decode - GL_OES_EGL_image - GL_OES_depth_texture - GL_OES_packed_depth_stencil - GL_EXT_texture_type_2_10_10_10_REV - GL_OES_get_program_binary - GL_APPLE_texture_max_level - GL_EXT_discard_framebuffer - GL_EXT_read_format_bgra - GL_EXT_frag_depth - GL_NV_fbo_color_attachments - GL_OES_EGL_image_external - GL_OES_EGL_sync - GL_OES_vertex_array_object - GL_OES_viewport_array - GL_ANGLE_texture_compression_dxt3 - GL_ANGLE_texture_compression_dxt5 - GL_EXT_robustness - GL_EXT_texture_rg - GL_EXT_unpack_subimage - GL_NV_draw_buffers - GL_NV_read_buffer - GL_NV_read_depth - GL_NV_read_depth_stencil - GL_NV_read_stencil - GL_EXT_draw_buffers - GL_EXT_map_buffer_range - GL_KHR_debug - GL_KHR_robustness - GL_OES_depth_texture_cube_map - GL_OES_required_internalformat - GL_OES_surfaceless_context - GL_EXT_color_buffer_float - GL_EXT_separate_shader_objects - GL_EXT_shader_integer_mix - GL_EXT_tessellation_point_size - GL_EXT_tessellation_shader - GL_INTEL_performance_query - GL_EXT_base_instance - GL_EXT_compressed_ETC1_RGB8_sub_texture - GL_EXT_copy_image - GL_EXT_draw_buffers_indexed - GL_EXT_draw_elements_base_vertex - GL_EXT_gpu_shader5 - GL_EXT_polygon_offset_clamp - GL_EXT_primitive_bounding_box - GL_EXT_shader_io_blocks - GL_EXT_texture_border_clamp - GL_EXT_texture_buffer - GL_EXT_texture_cube_map_array - GL_EXT_texture_norm16 - GL_KHR_blend_equation_advanced - GL_KHR_context_flush_control - GL_KHR_robust_buffer_access_behavior - GL_NV_image_formats - GL_OES_copy_image - GL_OES_draw_buffers_indexed - GL_OES_draw_elements_base_vertex - GL_OES_gpu_shader5 - GL_OES_primitive_bounding_box - GL_OES_sample_shading - GL_OES_sample_variables - GL_OES_shader_io_blocks -
Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency
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
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 $ journalctl -u anbox-container-manager.service -- Logs begin at Wed 2018-12-26 10:59:10 AEDT, end at Sun 2018-12-30 10:13:28 A дек 29 21:17:55 debians systemd[1]: Starting Anbox Container Manager... дек 29 21:17:57 debians systemd[1]: Started Anbox Container Manager. $ journalctl -u anbox-session-manager.service -- Logs begin at Wed 2018-12-26 10:59:10 AEDT, end at Sun 2018-12-30 10:13:38 A -- No entries -- $
Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency
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 also addressed in README.Debian, "Android application can be started from desktop menu." You shoud launch the GUI application from desktop menu, or you can see what command should be used from desktop file, /usr/share/applications/anbox.desktop -- Shengjing Zhu
Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency
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 anbox-session-manager start Failed to start anbox-session-manager.service: Unit anbox-session-manager.service not found. $ 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. Svetlana
Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency
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 /lib/modules/`uname -r`/kernel/drivers/staging/android/ashmem_linux.ko." but it does not say how to load these mobules; it turned out to be "modprobe binder_linux" and "modprobe ashmem_linux" but this took several guesses (I tried the full path too). Perhaps the readme should be clarified to include this correct command. 2) if configuration is required, perhaps an ncurses wizard similar to that of mysql (where it sets the root password) should be offered, or at least a dialog "this package requires additional configuration, please check the readme here at /usr/share/doc/anbox/ for details" should be shown 3) Continuing usage after following the steps suggested in the readme, /var/lib/anbox$ sudo lsmod | grep linux ashmem_linux 16384 0 binder_linux 135168 0 /var/lib/anbox$ file android.img android.img: Squashfs filesystem, little endian, version 4.0, 325898705 bytes, 2116 inodes, blocksize: 131072 bytes, created: Fri Jul 20 01:19:03 2018 /var/lib/anbox$ anbox session-manager [ 2018-12-29 05:57:18] [daemon.cpp:61@Run] Failed to connect to socket /run/anbox-container.socket: No such file or directory /var/lib/anbox$ -- Svetlana
Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency
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
File/directory /use/share/doc/anbox/ does not exist.
Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency
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
~$ 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: man:anbox(1) ~$ journalctl -u anbox-container-manager.service -- Logs begin at Wed 2018-12-26 10:59:10 AEDT, end at Fri 2018-12-28 22:03:36 A-- No entries -- ~$
Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency
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 session-manager > [ 2018-12-28 04:03:29] [session_manager.cpp:130@operator()] Failed to > start as > either binder or ashmem kernel drivers are not loaded > ~$ > https://sources.debian.org/src/anbox/0.0~git20181210-1/debian/anbox-container-manager.service/ The kernel modules are pulled by this systemd service. Cloud you attach your log of this service? >
Bug#917516: anbox: does not pull binder or ashmem kernel drivers as dependency
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] [session_manager.cpp:130@operator()] Failed to start as either binder or ashmem kernel drivers are not loaded ~$ I expected that after installing 'anbox' package the program does not require any further kernel configurations. *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU:ru (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages anbox depends on: ii iptables1.8.2-2+b1 ii libboost-atomic1.67.0 1.67.0-11 ii libboost-chrono1.67.0 1.67.0-11 ii libboost-date-time1.67.01.67.0-11 ii libboost-filesystem1.67.0 1.67.0-11 ii libboost-iostreams1.67.01.67.0-11 ii libboost-log1.67.0 1.67.0-11 ii libboost-program-options1.67.0 1.67.0-11 ii libboost-regex1.67.01.67.0-11 ii libboost-serialization1.67.01.67.0-11 ii libboost-system1.67.0 1.67.0-11 ii libboost-thread1.67.0 1.67.0-11 ii libc6 2.28-2 ii libegl1 1.1.0-1 ii libgcc1 1:8.2.0-13 ii libgles21.1.0-1 ii liblxc1 1:3.0.3-1 ii libprotobuf-lite17 3.6.1.3-1 ii libsdl2-2.0-0 2.0.8+dfsg1-6 ii libsdl2-image-2.0-0 2.0.3+dfsg1-3 ii libstdc++6 8.2.0-13 ii libsystemd0 238-2 ii lxc 1:3.0.3-1 Versions of packages anbox recommends: ii dbus-user-session 1.12.12-1 anbox suggests no packages. -- no debconf information
