Bug#932582: anbox: ignores mouse input

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#932582: anbox: ignores mouse input

Phil Morrell
Package: anbox
Version: 0.0~git20190124-1
Severity: grave
Justification: renders package unusable

I am able to launch the android apps from the desktop menu, but cannot
interact other than moving the window around and fullscreening.

I thought this was reported upstream as [#780], but the fix was merged
in [bbf05d8f3] on 2019-01-06 and so included in the debian version.

[#780]: https://github.com/anbox/anbox/issues/780
[bbf05d8f3]: https://github.com/anbox/anbox/commit/bbf05d8f3267ef5fb102525c372183aaa83df830
--
Phil Morrell (emorrp1)



-- System Information:
Debian Release: 10.0
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (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  iptables                        1.8.2-4
ii  libboost-atomic1.67.0           1.67.0-13
ii  libboost-chrono1.67.0           1.67.0-13
ii  libboost-date-time1.67.0        1.67.0-13
ii  libboost-filesystem1.67.0       1.67.0-13
ii  libboost-iostreams1.67.0        1.67.0-13
ii  libboost-log1.67.0              1.67.0-13
ii  libboost-program-options1.67.0  1.67.0-13
ii  libboost-regex1.67.0            1.67.0-13
ii  libboost-serialization1.67.0    1.67.0-13
ii  libboost-system1.67.0           1.67.0-13
ii  libboost-thread1.67.0           1.67.0-13
ii  libc6                           2.28-10
ii  libegl1                         1.1.0-1
ii  libgcc1                         1:8.3.0-6
ii  libgles2                        1.1.0-1
ii  liblxc1                         1:3.1.0+really3.0.3-8
ii  libprotobuf-lite17              3.6.1.3-2
ii  libsdl2-2.0-0                   2.0.9+dfsg1-1
ii  libsdl2-image-2.0-0             2.0.4+dfsg1-1
ii  libstdc++6                      8.3.0-6
ii  libsystemd0                     241-5
ii  lxc                             1:3.1.0+really3.0.3-8

Versions of packages anbox recommends:
ii  dbus-user-session  1.12.16-1

anbox suggests no packages.

-- no debconf information
To: Debian Bug Tracking System <[hidden email]>
Subject: anbox: ignores mouse input
X-Debbugs-Cc: [hidden email]

Package: anbox
Version: 0.0~git20190124-1
Severity: grave
Justification: renders package unusable

I am able to launch the android apps from the desktop menu, but cannot
interact other than moving the window around and fullscreening.

I thought this was reported upstream as [#780], but the fix was merged
in [bbf05d8f3] on 2019-01-06 and so included in the debian version.

[#780]: https://github.com/anbox/anbox/issues/780
[bbf05d8f3]: https://github.com/anbox/anbox/commit/bbf05d8f3267ef5fb102525c372183aaa83df830
--
Phil Morrell (emorrp1)



-- System Information:
Debian Release: 10.0
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (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  iptables                        1.8.2-4
ii  libboost-atomic1.67.0           1.67.0-13
ii  libboost-chrono1.67.0           1.67.0-13
ii  libboost-date-time1.67.0        1.67.0-13
ii  libboost-filesystem1.67.0       1.67.0-13
ii  libboost-iostreams1.67.0        1.67.0-13
ii  libboost-log1.67.0              1.67.0-13
ii  libboost-program-options1.67.0  1.67.0-13
ii  libboost-regex1.67.0            1.67.0-13
ii  libboost-serialization1.67.0    1.67.0-13
ii  libboost-system1.67.0           1.67.0-13
ii  libboost-thread1.67.0           1.67.0-13
ii  libc6                           2.28-10
ii  libegl1                         1.1.0-1
ii  libgcc1                         1:8.3.0-6
ii  libgles2                        1.1.0-1
ii  liblxc1                         1:3.1.0+really3.0.3-8
ii  libprotobuf-lite17              3.6.1.3-2
ii  libsdl2-2.0-0                   2.0.9+dfsg1-1
ii  libsdl2-image-2.0-0             2.0.4+dfsg1-1
ii  libstdc++6                      8.3.0-6
ii  libsystemd0                     241-5
ii  lxc                             1:3.1.0+really3.0.3-8

Versions of packages anbox recommends:
ii  dbus-user-session  1.12.16-1

anbox suggests no packages.

-- no debconf information

signature.asc (235 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#932582: anbox: ignores mouse input

Shengjing Zhu-3
On Mon, Jul 22, 2019 at 8:10 AM Phil Morrell <[hidden email]> wrote:
> My main pc is running radeon open source drivers and an xfce4 desktop.
>

For the reference, I'm using KDE and intel graphic. And anbox works fine.

But since you have tried software-rendering, then probably it's not
related to the AMD gpu.
It's seems your journald has something wrong, which doesn't give
correct log for anbox.

Since the snap version doesn't work too, could you open a bug on
upstream? When it gets fixed, I'll update the version in Debian.

--
Shengjing Zhu

Reply | Threaded
Open this post in threaded view
|

Bug#932582: anbox: ignores mouse input

Ivan Vučica-2
In reply to this post by Phil Morrell
Package: anbox
Version: 0.0~git20191115-1
Followup-For: Bug #932582

This still occurs when using Debian buster's kernel plus current unstable's
anbox on Nvidia.

Per update on 2019-07-22, I understand that this is unlikely to be fixable
downstream, but I'd like to provide this additional information for future
reporters.

Unlike Phil, I have not attempted to run the Snap version at this time.

After resizing windows, there is some animation happening (scrollbars
appearing in builtin Settings app), so I think it's genuinely an input
and not a rendering issue.

-- System Information:
Debian Release: 10.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (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  init-system-helpers             1.56+nmu1
ii  iptables                        1.8.2-4
ii  libboost-filesystem1.67.0       1.67.0-13
ii  libboost-iostreams1.67.0        1.67.0-13
ii  libboost-log1.67.0              1.67.0-13
ii  libboost-program-options1.67.0  1.67.0-13
ii  libboost-system1.67.0           1.67.0-13
ii  libboost-thread1.67.0           1.67.0-13
ii  libc6                           2.29-3
ii  libegl1                         1.1.0-1
ii  libgcc1                         1:8.3.0-6
ii  libgles2                        1.1.0-1
ii  liblxc1                         1:3.1.0+really3.0.3-8
ii  libprotobuf-lite17              3.6.1.3-2
ii  libsdl2-2.0-0                   2.0.10+dfsg1-1
ii  libsdl2-image-2.0-0             2.0.4+dfsg1-1+deb10u1
ii  libstdc++6                      8.3.0-6
ii  libsystemd0                     243-8
ii  lxc                             1:3.1.0+really3.0.3-8

Versions of packages anbox recommends:
ii  dbus-user-session  1.12.16-1

anbox suggests no packages.

-- no debconf information

Reply | Threaded
Open this post in threaded view
|

Bug#932582: anbox: ignores mouse input

Alan MacLeod
In reply to this post by Phil Morrell
Hi,

I've tried both the Snap and packaged versions: the Snap version works
fully, but is very slow, and the packaged version appears quicker, but I
cannot interact with the applications - OP's description is exactly what
I am experiencing: everything opens, I can resize the windows and close
them, but I cannot interact with the application with mouse or keyboard.

I'm using:
Debian Testing
kernel 5.4.0.2-amd64
XFCE 4.14
HP 8440p laptop - Intel core i5 540, 8 GB RAM

apt policy anbox
anbox:
   Installed: (none)
   Candidate: 0.0~git20191115-1
   Version table:
      0.0~git20191115-1 990
         990 https://deb.debian.org/debian testing/contrib amd64 Packages
         500 https://deb.debian.org/debian unstable/contrib amd64 Packages
         100 /var/lib/dpkg/status
      0.0~git20190124-1 500
         500 https://deb.debian.org/debian stable/contrib amd64 Packages

snap list anbox
Name   Version    Rev  Tracking  Publisher  Notes
anbox  4-56c25f1  186  beta      morphis    devmode

What other info can I provide? I'm currently running the Snap version.

Thanks

Alan

Reply | Threaded
Open this post in threaded view
|

Bug#932582: anbox: ignores mouse input

Shengjing Zhu-3
On Thu, Jan 16, 2020 at 3:03 AM Alan MacLeod <[hidden email]> wrote:
>
> Hi,
>
> I've tried both the Snap and packaged versions: the Snap version works
> fully, but is very slow, and the packaged version appears quicker, but I

The snap version includes a software render feature. Maybe you're using this?
This could be slow.

> cannot interact with the applications - OP's description is exactly what
> I am experiencing: everything opens, I can resize the windows and close
> them, but I cannot interact with the application with mouse or keyboard.
>
> I'm using:
> Debian Testing
> kernel 5.4.0.2-amd64
> XFCE 4.14
> HP 8440p laptop - Intel core i5 540, 8 GB RAM

The Debian package must use hardware render. Intel ARK doesn't show
much information about your CPU's graphic[1].
Maybe this CPU is too old? (run `anbox system-info` will give your some info)

And I'm not sure if anyone tests anbox with XFCE, the integration with
XFCE may also be a problem.

[1] https://ark.intel.com/content/www/us/en/ark/products/43544/intel-core-i5-540m-processor-3m-cache-2-53-ghz.html

--
Shengjing Zhu

Reply | Threaded
Open this post in threaded view
|

Bug#932582: anbox: ignores mouse input

Alan MacLeod
On 15/01/2020 14.15, Shengjing Zhu wrote:
The snap version includes a software render feature. Maybe you're using this?
This could be slow.
I'm not sure how to verify this, but it makes sense that hardware acceleration is not being used.
The Debian package must use hardware render. Intel ARK doesn't show
much information about your CPU's graphic[1].
Maybe this CPU is too old? (run `anbox system-info` will give your some info)
version: 4
snap-revision: 186
cpu:
  arch:  x86
  brand: Intel(R) Core(TM) i5 CPU       M 540  @ 2.53GHz
  features:
    - aes
os:
  name: Debian GNU/Linux
  version:
  snap-based: true
kernel:
  version: Linux version 5.4.0-2-amd64 ([hidden email]) (gcc version 9.2.1 20200104 (Debian 9.2.1-22)) #1 SMP Debian 5.4.8-1 (2020-01-05)
  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_buffer_age
      - 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_EXT_pixel_format_float
      - EGL_KHR_wait_sync
      - EGL_MESA_configless_context
      - EGL_MESA_drm_image
      - EGL_MESA_image_dma_buf_export
      - EGL_NOK_texture_from_pixmap
      - EGL_WL_bind_wayland_display
  gles2:
    vendor: Intel Open Source Technology Center
    vendor: OpenGL ES 2.0 Mesa 18.0.5
    extensions:
      - GL_ANGLE_texture_compression_dxt3
      - GL_ANGLE_texture_compression_dxt5
      - GL_APPLE_texture_max_level
      - GL_EXT_blend_minmax
      - GL_EXT_compressed_ETC1_RGB8_sub_texture
      - GL_EXT_discard_framebuffer
      - GL_EXT_draw_buffers
      - GL_EXT_draw_elements_base_vertex
      - GL_EXT_frag_depth
      - GL_EXT_map_buffer_range
      - GL_EXT_multi_draw_arrays
      - GL_EXT_occlusion_query_boolean
      - GL_EXT_polygon_offset_clamp
      - GL_EXT_read_format_bgra
      - GL_EXT_robustness
      - GL_EXT_separate_shader_objects
      - GL_EXT_texture_border_clamp
      - GL_EXT_texture_compression_dxt1
      - GL_EXT_texture_filter_anisotropic
      - GL_EXT_texture_format_BGRA8888
      - GL_EXT_texture_rg
      - GL_EXT_texture_type_2_10_10_10_REV
      - GL_EXT_unpack_subimage
      - GL_KHR_blend_equation_advanced
      - GL_KHR_context_flush_control
      - GL_KHR_debug
      - GL_KHR_no_error
      - GL_KHR_robustness
      - GL_NV_draw_buffers
      - GL_NV_fbo_color_attachments
      - GL_NV_read_buffer
      - GL_NV_read_depth
      - GL_NV_read_depth_stencil
      - GL_NV_read_stencil
      - GL_OES_EGL_image
      - GL_OES_EGL_image_external
      - GL_OES_EGL_sync
      - GL_OES_compressed_ETC1_RGB8_texture
      - GL_OES_depth24
      - GL_OES_depth_texture
      - GL_OES_draw_elements_base_vertex
      - GL_OES_element_index_uint
      - GL_OES_fbo_render_mipmap
      - GL_OES_get_program_binary
      - GL_OES_mapbuffer
      - GL_OES_packed_depth_stencil
      - GL_OES_required_internalformat
      - GL_OES_rgb8_rgba8
      - GL_OES_standard_derivatives
      - GL_OES_stencil8
      - GL_OES_surfaceless_context
      - GL_OES_texture_3D
      - GL_OES_texture_border_clamp
      - 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_array_object
      - GL_OES_vertex_half_float


Not sure if that provides any insight to help solve why the mouse/keyboard won't work with packaged version. I'm comfortable that its plausible the CPU is too old, albeit, the PC is circa 2010, so old, but not that old.

And I'm not sure if anyone tests anbox with XFCE, the integration with
XFCE may also be a problem.

[1] https://ark.intel.com/content/www/us/en/ark/products/43544/intel-core-i5-540m-processor-3m-cache-2-53-ghz.html

Reply | Threaded
Open this post in threaded view
|

Bug#932582: anbox: ignores mouse input

Shengjing Zhu-3
On Thu, Jan 16, 2020 at 4:29 AM Alan MacLeod <[hidden email]> wrote:
[...]
> version: 4
> snap-revision: 186
> cpu:
>   arch:  x86
>   brand: Intel(R) Core(TM) i5 CPU       M 540  @ 2.53GHz
>   features:
>     - aes

Hmm, just aes? I thought the snap version should refuse to install...
IIRC, anbox needs sse4 to work...

What does `anbox check-features` say?

--
Shengjing Zhu

Reply | Threaded
Open this post in threaded view
|

Bug#932582: anbox: ignores mouse input

Alan MacLeod
Thanks for continuing to look at this.

anbox check-features
Your computer does meet all requirements to run Anbox


When I check /proc/cpuinfo, the flags are

flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d


Which lists SSE4_1 and _2.

What I do know the integrated GPU is missing is OpenGL 3 - this has prevented me running a few newer apps in WINE, again, I don't know if that is relevant to the issue.

Thanks

Alan

On 17/01/2020 10.06, Shengjing Zhu wrote:
On Thu, Jan 16, 2020 at 4:29 AM Alan MacLeod [hidden email] wrote:
[...]
version: 4
snap-revision: 186
cpu:
  arch:  x86
  brand: Intel(R) Core(TM) i5 CPU       M 540  @ 2.53GHz
  features:
    - aes
Hmm, just aes? I thought the snap version should refuse to install...
IIRC, anbox needs sse4 to work...

What does `anbox check-features` say?