starred/docker-android
1
0
Fork 0
mirror of https://github.com/budtmo/docker-android.git synced 2026-04-25 20:25:57 +03:00
Code Issues 21 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #13] 6.0 arm image fails to start (Mac OS) #9

New issue
Closed
opened 2026-03-01 15:39:12 +03:00 by kerem · 11 comments
kerem commented 2026-03-01 15:39:12 +03:00
Owner
Copy link

Originally created by @serggl on GitHub (Jun 7, 2017).
Original GitHub issue: https://github.com/budtmo/docker-android/issues/13

here's the log:

Sergey-MBP-2:fuse-box sergeyglukhov$ docker run --privileged -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Nexus 4" --rm butomo1989/docker-android-arm-6.0
2017-06-07 09:25:20,335 CRIT Supervisor running as root (no user in config file)
2017-06-07 09:25:20,337 INFO supervisord started with pid 7
2017-06-07 09:25:21,343 INFO spawned: 'docker-appium' with pid 10
2017-06-07 09:25:21,345 INFO spawned: 'novnc' with pid 11
2017-06-07 09:25:21,347 INFO spawned: 'openbox' with pid 12
2017-06-07 09:25:21,349 INFO spawned: 'xvfb' with pid 13
2017-06-07 09:25:21,352 INFO spawned: 'x11vnc' with pid 15
2017-06-07 09:25:21,354 INFO spawned: 'port-forward' with pid 17
2017-06-07 09:25:21,959 INFO exited: docker-appium (exit status 1; not expected)
2017-06-07 09:25:22,396 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-06-07 09:25:22,396 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-06-07 09:25:22,396 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-06-07 09:25:22,396 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-06-07 09:25:22,396 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-06-07 09:25:23,404 INFO spawned: 'docker-appium' with pid 117
2017-06-07 09:25:23,461 INFO exited: docker-appium (exit status 1; not expected)
2017-06-07 09:25:25,468 INFO spawned: 'docker-appium' with pid 119
2017-06-07 09:25:25,524 INFO exited: docker-appium (exit status 1; not expected)
2017-06-07 09:25:28,534 INFO spawned: 'docker-appium' with pid 120
2017-06-07 09:25:28,592 INFO exited: docker-appium (exit status 1; not expected)
2017-06-07 09:25:29,595 INFO gave up: docker-appium entered FATAL state, too many start retries too quickly
Originally created by @serggl on GitHub (Jun 7, 2017). Original GitHub issue: https://github.com/budtmo/docker-android/issues/13 here's the log: ``` Sergey-MBP-2:fuse-box sergeyglukhov$ docker run --privileged -p 6080:6080 -p 5554:5554 -p 5555:5555 -e DEVICE="Nexus 4" --rm butomo1989/docker-android-arm-6.0 2017-06-07 09:25:20,335 CRIT Supervisor running as root (no user in config file) 2017-06-07 09:25:20,337 INFO supervisord started with pid 7 2017-06-07 09:25:21,343 INFO spawned: 'docker-appium' with pid 10 2017-06-07 09:25:21,345 INFO spawned: 'novnc' with pid 11 2017-06-07 09:25:21,347 INFO spawned: 'openbox' with pid 12 2017-06-07 09:25:21,349 INFO spawned: 'xvfb' with pid 13 2017-06-07 09:25:21,352 INFO spawned: 'x11vnc' with pid 15 2017-06-07 09:25:21,354 INFO spawned: 'port-forward' with pid 17 2017-06-07 09:25:21,959 INFO exited: docker-appium (exit status 1; not expected) 2017-06-07 09:25:22,396 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 09:25:22,396 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 09:25:22,396 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 09:25:22,396 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 09:25:22,396 INFO success: port-forward entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2017-06-07 09:25:23,404 INFO spawned: 'docker-appium' with pid 117 2017-06-07 09:25:23,461 INFO exited: docker-appium (exit status 1; not expected) 2017-06-07 09:25:25,468 INFO spawned: 'docker-appium' with pid 119 2017-06-07 09:25:25,524 INFO exited: docker-appium (exit status 1; not expected) 2017-06-07 09:25:28,534 INFO spawned: 'docker-appium' with pid 120 2017-06-07 09:25:28,592 INFO exited: docker-appium (exit status 1; not expected) 2017-06-07 09:25:29,595 INFO gave up: docker-appium entered FATAL state, too many start retries too quickly ```
kerem 2026-03-01 15:39:12 +03:00
  • closed this issue
  • added the
    bug
         label
kerem commented 2026-03-01 15:39:13 +03:00
Author
Owner
Copy link

@serggl commented on GitHub (Jun 7, 2017):

same time 7.1.1 image works smoothly

<!-- gh-comment-id:306742030 --> @serggl commented on GitHub (Jun 7, 2017): same time 7.1.1 image works smoothly
kerem commented 2026-03-01 15:39:14 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Jun 7, 2017):

Thank you @serggl I will check a bit later and keep you updated. How about the x86 image? I think it fail on your ubuntu machine, it might because you need to enable virtualization in bios.

<!-- gh-comment-id:306824910 --> @budtmo commented on GitHub (Jun 7, 2017): Thank you @serggl I will check a bit later and keep you updated. How about the x86 image? I think it fail on your ubuntu machine, it might because you need to enable virtualization in bios.
kerem commented 2026-03-01 15:39:14 +03:00
Author
Owner
Copy link

@serggl commented on GitHub (Jun 7, 2017):

Is it possible on AWS?

ср, 7 июн. 2017 г., 18:09 Budi Utomo notifications@github.com:

Thank you @serggl https://github.com/serggl I will check a bit later
and keep you updated. How about the x86 image? I think it fail on your
ubuntu machine, it might because you need to enable virtualization in bios.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/butomo1989/docker-android/issues/13#issuecomment-306824910,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADQOHEPCYH9N_rA1TuecjJOYzxkUsVlks5sBr0SgaJpZM4NycJa
.

--
Sergey, AnjLab

<!-- gh-comment-id:306845478 --> @serggl commented on GitHub (Jun 7, 2017): Is it possible on AWS? ср, 7 июн. 2017 г., 18:09 Budi Utomo <notifications@github.com>: > Thank you @serggl <https://github.com/serggl> I will check a bit later > and keep you updated. How about the x86 image? I think it fail on your > ubuntu machine, it might because you need to enable virtualization in bios. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/butomo1989/docker-android/issues/13#issuecomment-306824910>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AADQOHEPCYH9N_rA1TuecjJOYzxkUsVlks5sBr0SgaJpZM4NycJa> > . > -- Sergey, AnjLab
kerem commented 2026-03-01 15:39:14 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Jun 7, 2017):

I didn't try it, but it should work on AWS as well as long as virtualization is enabled. @serggl

<!-- gh-comment-id:306852339 --> @budtmo commented on GitHub (Jun 7, 2017): I didn't try it, but it should work on AWS as well as long as virtualization is enabled. @serggl
kerem commented 2026-03-01 15:39:14 +03:00
Author
Owner
Copy link

@serggl commented on GitHub (Jun 7, 2017):

According to this thread, its impossible
https://forums.aws.amazon.com/thread.jspa?threadID=74338

But the issues I posted is not about this :)

ср, 7 июн. 2017 г., 19:37 Budi Utomo notifications@github.com:

I didn't try it, but it should work on AWS as well as long as
virtualization is enabled. @serggl https://github.com/serggl

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/butomo1989/docker-android/issues/13#issuecomment-306852339,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADQOKYVrVme4DTC4ob4Y7MFSRJz86mOks5sBtHGgaJpZM4NycJa
.

--
Sergey, AnjLab

<!-- gh-comment-id:306854997 --> @serggl commented on GitHub (Jun 7, 2017): According to this thread, its impossible https://forums.aws.amazon.com/thread.jspa?threadID=74338 But the issues I posted is not about this :) ср, 7 июн. 2017 г., 19:37 Budi Utomo <notifications@github.com>: > I didn't try it, but it should work on AWS as well as long as > virtualization is enabled. @serggl <https://github.com/serggl> > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/butomo1989/docker-android/issues/13#issuecomment-306852339>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AADQOKYVrVme4DTC4ob4Y7MFSRJz86mOks5sBtHGgaJpZM4NycJa> > . > -- Sergey, AnjLab
kerem commented 2026-03-01 15:39:14 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Jun 7, 2017):

ahhh.. good to know, thank you @serggl

<!-- gh-comment-id:306876214 --> @budtmo commented on GitHub (Jun 7, 2017): ahhh.. good to know, thank you @serggl
kerem commented 2026-03-01 15:39:15 +03:00
Author
Owner
Copy link

@andrcuns commented on GitHub (Jun 7, 2017):

@serggl Are You sure it's not possible to run it on AWS (I know it's unrelated issue, but still)
According to this 3 years old article, it should.
P.S.
On the issue, did You check the output of actual log files (location in readme)? It might shed some light on why docker-appium process exits with code 1.

<!-- gh-comment-id:306880864 --> @andrcuns commented on GitHub (Jun 7, 2017): @serggl Are You sure it's not possible to run it on AWS (I know it's unrelated issue, but still) According to [this](https://www.ravellosystems.com/blog/running-kvm-hypervisors-aws-product-update/) 3 years old article, it should. P.S. On the issue, did You check the output of actual log files (location in readme)? It might shed some light on why docker-appium process exits with code 1.
kerem commented 2026-03-01 15:39:15 +03:00
Author
Owner
Copy link

@serggl commented on GitHub (Jun 8, 2017):

here's a log output

Sergey-MBP-2:fuse-box sergeyglukhov$ docker exec -it 9e25ac8eaff1 tail -f /var/log/supervisor/docker-android.stdout.log
System image: armeabi-v7a 
Image type: android
[10] [ INFO] app - Device: Nexus 4
[10] [ INFO] app - AVD name: nexus_4_6.0
[10] [ INFO] app - Preparing emulator...
[10] [ INFO] app - Skin ressource path: /root/devices/skins
[10] [ INFO] app - Skin destination path: /root/platforms/android-23/skins
[10] [ INFO] app - Device name in bash: Nexus\ 4, Skin name: nexus_4
[10] [ INFO] app - AVD creation command: echo no | android create avd -f -n nexus_4_6.0 -t android-23 -b armeabi-v7a -d Nexus\ 4 -s nexus_4
Valid ABIs: no ABIs.

also

root@9e25ac8eaff1:~# cd /var/log/supervisor/
root@9e25ac8eaff1:/var/log/supervisor# cat x11vnc.stderr.log
08/06/2017 07:13:30 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 14
08/06/2017 07:13:30 XOpenDisplay(":0") failed.
08/06/2017 07:13:30 Trying again with XAUTHLOCALHOSTNAME=localhost ...

08/06/2017 07:13:30 ***************************************
08/06/2017 07:13:30 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.

Some tips and guidelines:

** An X server (the one you wish to view) must be running before x11vnc is
   started: x11vnc does not start the X server.  (however, see the -create
   option if that is what you really want).

** You must use -display <disp>, -OR- set and export your $DISPLAY
   environment variable to refer to the display of the desired X server.
 - Usually the display is simply ":0" (in fact x11vnc uses this if you forget
   to specify it), but in some multi-user situations it could be ":1", ":2",
   or even ":137".  Ask your administrator or a guru if you are having
   difficulty determining what your X DISPLAY is.

** Next, you need to have sufficient permissions (Xauthority) 
   to connect to the X DISPLAY.   Here are some Tips:

 - Often, you just need to run x11vnc as the user logged into the X session.
   So make sure to be that user when you type x11vnc.
 - Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
   file may be accessed.  The cookie file contains the secret key that
   allows x11vnc to connect to the desired X DISPLAY.
 - You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
   by the -auth option, e.g.:
       x11vnc -auth /home/someuser/.Xauthority -display :0
       x11vnc -auth /tmp/.gdmzndVlR -display :0
   you must have read permission for the auth file.
   See also '-auth guess' and '-findauth' discussed below.

** If NO ONE is logged into an X session yet, but there is a greeter login
   program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
   to find and use the raw display manager MIT-MAGIC-COOKIE file.
   Some examples for various display managers:

     gdm:     -auth /var/gdm/:0.Xauth
              -auth /var/lib/gdm/:0.Xauth
     kdm:     -auth /var/lib/kdm/A:0-crWk72
              -auth /var/run/xauth/A:0-crWk72
     xdm:     -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
     dtlogin: -auth /var/dt/A:0-UgaaXa

   Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.

   Starting with x11vnc 0.9.9 you can have it try to guess by using:

              -auth guess

   (see also the x11vnc -findauth option.)

   Only root will have read permission for the file, and so x11vnc must be run
   as root (or copy it).  The random characters in the filenames will of course
   change and the directory the cookie file resides in is system dependent.

See also: http://www.karlrunge.com/x11vnc/faq.html
08/06/2017 07:13:31 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 115
08/06/2017 07:13:31 Using X display :0
08/06/2017 07:13:31 rootwin: 0x1a9 reswin: 0x400001 dpy: 0x131bb70
08/06/2017 07:13:31 
08/06/2017 07:13:31 ------------------ USEFUL INFORMATION ------------------
08/06/2017 07:13:31 X DAMAGE available on display, using it for polling hints.
08/06/2017 07:13:31   To disable this behavior use: '-noxdamage'
08/06/2017 07:13:31 
08/06/2017 07:13:31   Most compositing window managers like 'compiz' or 'beryl'
08/06/2017 07:13:31   cause X DAMAGE to fail, and so you may not see any screen
08/06/2017 07:13:31   updates via VNC.  Either disable 'compiz' (recommended) or
08/06/2017 07:13:31   supply the x11vnc '-noxdamage' command line option.
08/06/2017 07:13:31 
08/06/2017 07:13:31 Wireframing: -wireframe mode is in effect for window moves.
08/06/2017 07:13:31   If this yields undesired behavior (poor response, painting
08/06/2017 07:13:31   errors, etc) it may be disabled:
08/06/2017 07:13:31    - use '-nowf' to disable wireframing completely.
08/06/2017 07:13:31    - use '-nowcr' to disable the Copy Rectangle after the
08/06/2017 07:13:31      moved window is released in the new position.
08/06/2017 07:13:31   Also see the -help entry for tuning parameters.
08/06/2017 07:13:31   You can press 3 Alt_L's (Left "Alt" key) in a row to 
08/06/2017 07:13:31   repaint the screen, also see the -fixscreen option for
08/06/2017 07:13:31   periodic repaints.
08/06/2017 07:13:31 
08/06/2017 07:13:31 XFIXES available on display, resetting cursor mode
08/06/2017 07:13:31   to: '-cursor most'.
08/06/2017 07:13:31   to disable this behavior use: '-cursor arrow'
08/06/2017 07:13:31   or '-noxfixes'.
08/06/2017 07:13:31 using XFIXES for cursor drawing.
08/06/2017 07:13:31 GrabServer control via XTEST.
08/06/2017 07:13:31 
08/06/2017 07:13:31 Scroll Detection: -scrollcopyrect mode is in effect to
08/06/2017 07:13:31   use RECORD extension to try to detect scrolling windows
08/06/2017 07:13:31   (induced by either user keystroke or mouse input).
08/06/2017 07:13:31   If this yields undesired behavior (poor response, painting
08/06/2017 07:13:31   errors, etc) it may be disabled via: '-noscr'
08/06/2017 07:13:31   Also see the -help entry for tuning parameters.
08/06/2017 07:13:31   You can press 3 Alt_L's (Left "Alt" key) in a row to 
08/06/2017 07:13:31   repaint the screen, also see the -fixscreen option for
08/06/2017 07:13:31   periodic repaints.
08/06/2017 07:13:31 
08/06/2017 07:13:31 XKEYBOARD: number of keysyms per keycode 7 is greater
08/06/2017 07:13:31   than 4 and 51 keysyms are mapped above 4.
08/06/2017 07:13:31   Automatically switching to -xkb mode.
08/06/2017 07:13:31   If this makes the key mapping worse you can
08/06/2017 07:13:31   disable it with the "-noxkb" option.
08/06/2017 07:13:31   Also, remember "-remap DEAD" for accenting characters.
08/06/2017 07:13:31 
08/06/2017 07:13:31 X FBPM extension not supported.
08/06/2017 07:13:31 X display is not capable of DPMS.
08/06/2017 07:13:31 --------------------------------------------------------
08/06/2017 07:13:31 
08/06/2017 07:13:31 Default visual ID: 0x21
08/06/2017 07:13:31 Read initial data from X display into framebuffer.
08/06/2017 07:13:31 initialize_screen: fb_depth/fb_bpp/fb_Bpl 16/16/3200
08/06/2017 07:13:31 
08/06/2017 07:13:31 X display :0 is 16bpp depth=16 true color
08/06/2017 07:13:31 
08/06/2017 07:13:31 Autoprobing TCP port 
08/06/2017 07:13:31 Autoprobing selected TCP port 5900
08/06/2017 07:13:31 Autoprobing TCP6 port 
08/06/2017 07:13:31 Autoprobing selected TCP6 port 5900
08/06/2017 07:13:31 listen6: bind: Address already in use
08/06/2017 07:13:31 Not listening on IPv6 interface.
08/06/2017 07:13:31 
08/06/2017 07:13:31 Xinerama is present and active (e.g. multi-head).
08/06/2017 07:13:31 Xinerama: number of sub-screens: 1
08/06/2017 07:13:31 Xinerama: no blackouts needed (only one sub-screen)
08/06/2017 07:13:31 
08/06/2017 07:13:31 fb read rate: 1565 MB/sec
08/06/2017 07:13:31 fast read: reset -wait  ms to: 10
08/06/2017 07:13:31 fast read: reset -defer ms to: 10
08/06/2017 07:13:31 The X server says there are 10 mouse buttons.
08/06/2017 07:13:31 screen setup finished.
08/06/2017 07:13:31 

The VNC desktop is:      9e25ac8eaff1:0

******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval.  It should work with any VNC viewer.  Try it by running:

    x11vnc -ncache 10 ...

One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
<!-- gh-comment-id:307020018 --> @serggl commented on GitHub (Jun 8, 2017): here's a log output ``` Sergey-MBP-2:fuse-box sergeyglukhov$ docker exec -it 9e25ac8eaff1 tail -f /var/log/supervisor/docker-android.stdout.log System image: armeabi-v7a Image type: android [10] [ INFO] app - Device: Nexus 4 [10] [ INFO] app - AVD name: nexus_4_6.0 [10] [ INFO] app - Preparing emulator... [10] [ INFO] app - Skin ressource path: /root/devices/skins [10] [ INFO] app - Skin destination path: /root/platforms/android-23/skins [10] [ INFO] app - Device name in bash: Nexus\ 4, Skin name: nexus_4 [10] [ INFO] app - AVD creation command: echo no | android create avd -f -n nexus_4_6.0 -t android-23 -b armeabi-v7a -d Nexus\ 4 -s nexus_4 Valid ABIs: no ABIs. ``` also ``` root@9e25ac8eaff1:~# cd /var/log/supervisor/ root@9e25ac8eaff1:/var/log/supervisor# cat x11vnc.stderr.log 08/06/2017 07:13:30 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 14 08/06/2017 07:13:30 XOpenDisplay(":0") failed. 08/06/2017 07:13:30 Trying again with XAUTHLOCALHOSTNAME=localhost ... 08/06/2017 07:13:30 *************************************** 08/06/2017 07:13:30 *** XOpenDisplay failed (:0) *** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue. *** There may be "Xlib:" error messages above with details about the failure. Some tips and guidelines: ** An X server (the one you wish to view) must be running before x11vnc is started: x11vnc does not start the X server. (however, see the -create option if that is what you really want). ** You must use -display <disp>, -OR- set and export your $DISPLAY environment variable to refer to the display of the desired X server. - Usually the display is simply ":0" (in fact x11vnc uses this if you forget to specify it), but in some multi-user situations it could be ":1", ":2", or even ":137". Ask your administrator or a guru if you are having difficulty determining what your X DISPLAY is. ** Next, you need to have sufficient permissions (Xauthority) to connect to the X DISPLAY. Here are some Tips: - Often, you just need to run x11vnc as the user logged into the X session. So make sure to be that user when you type x11vnc. - Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE file may be accessed. The cookie file contains the secret key that allows x11vnc to connect to the desired X DISPLAY. - You can explicitly indicate which MIT-MAGIC-COOKIE file should be used by the -auth option, e.g.: x11vnc -auth /home/someuser/.Xauthority -display :0 x11vnc -auth /tmp/.gdmzndVlR -display :0 you must have read permission for the auth file. See also '-auth guess' and '-findauth' discussed below. ** If NO ONE is logged into an X session yet, but there is a greeter login program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need to find and use the raw display manager MIT-MAGIC-COOKIE file. Some examples for various display managers: gdm: -auth /var/gdm/:0.Xauth -auth /var/lib/gdm/:0.Xauth kdm: -auth /var/lib/kdm/A:0-crWk72 -auth /var/run/xauth/A:0-crWk72 xdm: -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk dtlogin: -auth /var/dt/A:0-UgaaXa Sometimes the command "ps wwwwaux | grep auth" can reveal the file location. Starting with x11vnc 0.9.9 you can have it try to guess by using: -auth guess (see also the x11vnc -findauth option.) Only root will have read permission for the file, and so x11vnc must be run as root (or copy it). The random characters in the filenames will of course change and the directory the cookie file resides in is system dependent. See also: http://www.karlrunge.com/x11vnc/faq.html 08/06/2017 07:13:31 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 115 08/06/2017 07:13:31 Using X display :0 08/06/2017 07:13:31 rootwin: 0x1a9 reswin: 0x400001 dpy: 0x131bb70 08/06/2017 07:13:31 08/06/2017 07:13:31 ------------------ USEFUL INFORMATION ------------------ 08/06/2017 07:13:31 X DAMAGE available on display, using it for polling hints. 08/06/2017 07:13:31 To disable this behavior use: '-noxdamage' 08/06/2017 07:13:31 08/06/2017 07:13:31 Most compositing window managers like 'compiz' or 'beryl' 08/06/2017 07:13:31 cause X DAMAGE to fail, and so you may not see any screen 08/06/2017 07:13:31 updates via VNC. Either disable 'compiz' (recommended) or 08/06/2017 07:13:31 supply the x11vnc '-noxdamage' command line option. 08/06/2017 07:13:31 08/06/2017 07:13:31 Wireframing: -wireframe mode is in effect for window moves. 08/06/2017 07:13:31 If this yields undesired behavior (poor response, painting 08/06/2017 07:13:31 errors, etc) it may be disabled: 08/06/2017 07:13:31 - use '-nowf' to disable wireframing completely. 08/06/2017 07:13:31 - use '-nowcr' to disable the Copy Rectangle after the 08/06/2017 07:13:31 moved window is released in the new position. 08/06/2017 07:13:31 Also see the -help entry for tuning parameters. 08/06/2017 07:13:31 You can press 3 Alt_L's (Left "Alt" key) in a row to 08/06/2017 07:13:31 repaint the screen, also see the -fixscreen option for 08/06/2017 07:13:31 periodic repaints. 08/06/2017 07:13:31 08/06/2017 07:13:31 XFIXES available on display, resetting cursor mode 08/06/2017 07:13:31 to: '-cursor most'. 08/06/2017 07:13:31 to disable this behavior use: '-cursor arrow' 08/06/2017 07:13:31 or '-noxfixes'. 08/06/2017 07:13:31 using XFIXES for cursor drawing. 08/06/2017 07:13:31 GrabServer control via XTEST. 08/06/2017 07:13:31 08/06/2017 07:13:31 Scroll Detection: -scrollcopyrect mode is in effect to 08/06/2017 07:13:31 use RECORD extension to try to detect scrolling windows 08/06/2017 07:13:31 (induced by either user keystroke or mouse input). 08/06/2017 07:13:31 If this yields undesired behavior (poor response, painting 08/06/2017 07:13:31 errors, etc) it may be disabled via: '-noscr' 08/06/2017 07:13:31 Also see the -help entry for tuning parameters. 08/06/2017 07:13:31 You can press 3 Alt_L's (Left "Alt" key) in a row to 08/06/2017 07:13:31 repaint the screen, also see the -fixscreen option for 08/06/2017 07:13:31 periodic repaints. 08/06/2017 07:13:31 08/06/2017 07:13:31 XKEYBOARD: number of keysyms per keycode 7 is greater 08/06/2017 07:13:31 than 4 and 51 keysyms are mapped above 4. 08/06/2017 07:13:31 Automatically switching to -xkb mode. 08/06/2017 07:13:31 If this makes the key mapping worse you can 08/06/2017 07:13:31 disable it with the "-noxkb" option. 08/06/2017 07:13:31 Also, remember "-remap DEAD" for accenting characters. 08/06/2017 07:13:31 08/06/2017 07:13:31 X FBPM extension not supported. 08/06/2017 07:13:31 X display is not capable of DPMS. 08/06/2017 07:13:31 -------------------------------------------------------- 08/06/2017 07:13:31 08/06/2017 07:13:31 Default visual ID: 0x21 08/06/2017 07:13:31 Read initial data from X display into framebuffer. 08/06/2017 07:13:31 initialize_screen: fb_depth/fb_bpp/fb_Bpl 16/16/3200 08/06/2017 07:13:31 08/06/2017 07:13:31 X display :0 is 16bpp depth=16 true color 08/06/2017 07:13:31 08/06/2017 07:13:31 Autoprobing TCP port 08/06/2017 07:13:31 Autoprobing selected TCP port 5900 08/06/2017 07:13:31 Autoprobing TCP6 port 08/06/2017 07:13:31 Autoprobing selected TCP6 port 5900 08/06/2017 07:13:31 listen6: bind: Address already in use 08/06/2017 07:13:31 Not listening on IPv6 interface. 08/06/2017 07:13:31 08/06/2017 07:13:31 Xinerama is present and active (e.g. multi-head). 08/06/2017 07:13:31 Xinerama: number of sub-screens: 1 08/06/2017 07:13:31 Xinerama: no blackouts needed (only one sub-screen) 08/06/2017 07:13:31 08/06/2017 07:13:31 fb read rate: 1565 MB/sec 08/06/2017 07:13:31 fast read: reset -wait ms to: 10 08/06/2017 07:13:31 fast read: reset -defer ms to: 10 08/06/2017 07:13:31 The X server says there are 10 mouse buttons. 08/06/2017 07:13:31 screen setup finished. 08/06/2017 07:13:31 The VNC desktop is: 9e25ac8eaff1:0 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching ```
kerem commented 2026-03-01 15:39:15 +03:00
Author
Owner
Copy link

@serggl commented on GitHub (Jun 8, 2017):

let me know if you need any other logs

<!-- gh-comment-id:307020657 --> @serggl commented on GitHub (Jun 8, 2017): let me know if you need any other logs
kerem commented 2026-03-01 15:39:15 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Jun 9, 2017):

@serggl It is fixed in this commit. I will release the new version (0.7) next week by including other things.

<!-- gh-comment-id:307349918 --> @budtmo commented on GitHub (Jun 9, 2017): @serggl It is fixed in [this commit](https://github.com/butomo1989/docker-android/commit/5b694c2c55003f4cadc63b4ea4eb963b5bb43600). I will release the new version (0.7) next week by including other things.
kerem commented 2026-03-01 15:39:15 +03:00
Author
Owner
Copy link

@budtmo commented on GitHub (Jun 14, 2017):

It is fixed on release 0.7

<!-- gh-comment-id:308439818 --> @budtmo commented on GitHub (Jun 14, 2017): It is fixed on release [0.7](https://github.com/butomo1989/docker-android/releases/tag/0.7)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v3.3.0-p0
v3.2.2-p0
v3.2.0-p0
v3.1.1-p0
v3.1.0-p0
v3.0.2-p2
v3.0.2-p1
v3.0.2-p0
v3.0.1-p1
v3.0.1-p0
v2.19.0-p2
v2.19.0-p1
v2.19.0-p0
v2.18.0-p0
v2.16.2-p0
v2.15.0-p1
v2.15.0-p0
v2.11.4-p0
v2.11.2-p0
v2.11.1-p0
v2.5.4-p1
v2.5.4-p0
v2.5.1-p0
v2.5.0-p0
v2.4.1-p0
v2.3.0-p1
v2.3.0-p0
v2.2.2-p0
v2.1.3-p1
v2.1.3-p0
v2.0.1-p1
v2.0.0-p6
v2.0-p5
v2.0-p4
v2.0-p3
v2.0-p2
v2.0-p1
v1.10-p7
v1.10-p6
v1.10-p5
v1.10-p4
v1.10-p3
v1.10-p2
v1.10-p1
v1.9-p8
v1.9-p7
v1.9-p6
v1.9-p5
1.9-p4
1.9-p3
1.9-p2
1.9-p1
1.9-p0
1.8-p16
1.8-p15
1.8-p14
1.8-p13
1.8-p12
1.8-p11
1.8-p10
1.8-p9
1.8-p8
1.8-p7
1.8-p6
1.8-p5
1.8-p4
1.8-p3
1.8-p2
1.8-p1
1.8-p0
1.7-p1
1.7-p0
1.6-p8
1.6-p7
1.6-p6
1.6-p5
1.6-p4
1.6-p3
1.6-p2
1.6-p1
1.6-p0
1.5-p6
1.5-p5
1.5-p4
1.5-p3
1.5-p2
1.5-p1
1.5-p0
1.4-p1
1.4-p0
1.3-p5
1.3-p4
1.3-p3
1.3-p2
1.3-p1
1.3-p0
1.2
1.1-p1
1.1
1.0
0.9-p5
0.9-p4
0.9-p3
0.9-p2
0.9-p1
0.9
0.8
0.7
0.6
0.5
0.4
0.3
0.2
0.1
Labels
Clear labels   
bug

   
depends_on_docker

   
enhancement

   
help wanted

   
nice to have

   
waiting for response
No labels
bug
depends_on_docker
enhancement
help wanted
nice to have
waiting for response
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docker-android#9
No description provided.