Google search is a very helpful tool for those types of questions. Paste the error message into a search, and review the suggestions which result.
Mark Waite On Tue, Sep 22, 2015 at 6:03 PM Kirshan Luhana <[email protected]> wrote: > Can you please guide how can I solve this problem, > > *libGL error: failed to load driver: swrast > * > > *libGL error: failed to load driver: swrast > getGLES1ExtensionString: Could not find GLES 1.x config! > Failed to obtain GLES 1.x extensions string!* > > > I using linux mint 17.2, latest Jenkins and andoid plugin and XVNC. > > > > > On Tuesday, 8 September 2015 19:04:19 UTC+2, Mark Waite wrote: > >> I don't think that is related to Xvnc, but it could be. A double free >> message could be from many different places. >> >> Mark Waite >> >> On Tue, Sep 8, 2015 at 8:52 AM Kirshan Luhana <[email protected]> >> wrote: >> > Thank you very very much for this guide, my emulator finally started but >>> now I am getting this error , is this due vnc ? as before when I was tested >>> with different user, it was working fine. >>> >>> **** Error in `/home/jenkins/tools/android-sdk-linux/tools/emulator64-x86': >>> double free or corruption (fasttop): 0x00007f1ecf2a8000 *** >>> * >>> >>> *$ /home/jenkins/tools/android-sdk-linux/platform-tools/adb kill-server >>> Terminating xvnc. >>> $ vncserver -kill :93 >>> Killing Xvnc4 process ID 5807* >>> >>> >>> >>> here is my complete log >>> >>> started by user anonymous <http://localhost:8080/user/null> >>> [EnvInject] - Loading node environment variables. >>> Building in workspace /home/jenkins/workspace/emulatorTest >>> $ pkill Xvnc >>> pkill: killing pid 10536 failed: Operation not permitted >>> pkill: killing pid 10614 failed: Operation not permitted >>> pkill: killing pid 10674 failed: Operation not permitted >>> $ pkill Xrealvnc >>> $ sh -c "rm -f /tmp/.X*-lock /tmp/.X11-unix/X*" >>> rm: cannot remove ‘/tmp/.X11-lock’: Operation not permitted >>> rm: cannot remove ‘/tmp/.X12-lock’: Operation not permitted >>> rm: cannot remove ‘/tmp/.X13-lock’: Operation not permitted >>> rm: cannot remove ‘/tmp/.X11-unix/X0’: Operation not permitted >>> rm: cannot remove ‘/tmp/.X11-unix/X11’: Operation not permitted >>> rm: cannot remove ‘/tmp/.X11-unix/X12’: Operation not permitted >>> rm: cannot remove ‘/tmp/.X11-unix/X13’: Operation not permitted >>> Starting xvnc >>> [emulatorTest] $ vncserver :93 -localhost -nolisten tcp >>> >>> New 'luhana:93 (catroid)' desktop is luhana:93 >>> >>> Starting applications specified in /home/catroid/.vnc/xstartup >>> Log file is /home/catroid/.vnc/luhana:93.log >>> >>> $ /home/jenkins/tools/android-sdk-linux/tools/android list target >>> [android] Using Android SDK: /home/jenkins/tools/android-sdk-linux >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb start-server >>> * daemon not running. starting it now on port 8212 * >>> * daemon started successfully * >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb start-server >>> [android] Starting Android emulator >>> [android] Erasing existing emulator data... >>> $ /home/jenkins/tools/android-sdk-linux/tools/emulator -ports 8210,8211 >>> -prop persist.sys.language=en -prop persist.sys.country=US -avd >>> hudson_en-US_213_HVGA_android-18_x86 -no-snapshot-load -no-snapshot-save >>> -wipe-data -camera-back emulated -camera-front emulated -gpu on -qemu -m >>> 800 -enable-kvm >>> >>> unhandled buffer attach event, attachment type 20 >>> unhandled buffer attach event, attachment type 20 >>> >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb connect >>> localhost:8211 >>> connected to localhost:8211 >>> [android] Waiting for emulator to finish booting... >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb -s >>> localhost:8211 shell getprop init.svc.bootanim >>> error: device offline >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb connect >>> localhost:8211 >>> >>> unhandled buffer attach event, attachment type 26 >>> unhandled buffer attach event, attachment type 28 >>> >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb -s >>> localhost:8211 shell getprop init.svc.bootanim >>> error: device offline >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb connect >>> localhost:8211 >>> >>> unhandled buffer attach event, attachment type 30 >>> >>> unhandled buffer attach event, attachment type 32 >>> >>> unhandled buffer attach event, attachment type 32 >>> >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb -s >>> localhost:8211 shell getprop init.svc.bootanim >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb -s >>> localhost:8211 logcat -v time >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb connect >>> localhost:8211 >>> [android] Emulator is ready for use (took 32 seconds) >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb disconnect >>> localhost:8211 >>> [android] Stopping Android emulator >>> *** Error in `/home/jenkins/tools/android-sdk-linux/tools/emulator64-x86': >>> double free or corruption (fasttop): 0x00007f1ecf2a8000 *** >>> >>> $ /home/jenkins/tools/android-sdk-linux/platform-tools/adb kill-server >>> Terminating xvnc. >>> $ vncserver -kill :93 >>> Killing Xvnc4 process ID 5807 >>> Finished: SUCCESS >>> >>> >>> >>> On Monday, 7 September 2015 17:07:28 UTC+2, Mark Waite wrote: >>> >>>> Refer to https://wiki.jenkins-ci.org/display/JENKINS/Xvnc+Plugin for >>>> plenty of details on Xvnc. >>>> >>>> The simple steps: >>>> >>>> 1. Install vncserver package for your operating systems (sudo >>>> apt-get install tightvncserver on Debian) >>>> 2. Install the Xvnc Jenkins plugin (from Jenkins Update Center) >>>> 3. Configure the Xvnc Jenkins plugin globally (part of "Configure >>>> System" under the "Manage Jenkins" link) >>>> 4. Configure each job that needs Xvnc to start a VNC server when >>>> the job starts (check box in the job definition) >>>> >>>> Thanks, >>>> Mark Waite >>>> >>>> On Mon, Sep 7, 2015 at 8:59 AM Kirshan Luhana <[email protected]> >>>> wrote: >>>> >>> Yes you are right, after restart I lost access to Display :=0. >>>>> Is this anyway to get access after every boot? >>>>> Can you share some more on XVNC ? I just started exploring Jenkins :) >>>>> >>>>> Thank you very ,much. >>>>> >>>>> >>>>> On Monday, 7 September 2015 15:50:07 UTC+2, Mark Waite wrote: >>>>> >>>>>> I don't think you'll like the long term results of setting DISPLAY=:0 >>>>>> for the entire Jenkins process. I think that technique assumes the >>>>>> Jenkins >>>>>> user will always have access to the ":0" X windows display. The next >>>>>> time >>>>>> you logout, Jenkins won't have access to that display. >>>>>> >>>>>> You probably want to install and configure the xvnc plugin and >>>>>> configure the job so that it starts an Xvnc session when the job starts, >>>>>> and closes that Xvnc session when the job ends. I've used the Xvnc >>>>>> plugin >>>>>> on many different jobs with good results. >>>>>> >>>>>> Alternately, you could install and configure the xvfb plugin and >>>>>> configure the job to use it. I haven't used the xvfb plugin, but there >>>>>> are >>>>>> many others who have used it with good results. >>>>>> >>>>>> Mark Waite >>>>>> >>>>>> On Mon, Sep 7, 2015 at 7:33 AM Kirshan Luhana <[email protected]> >>>>>> wrote: >>>>>> >>>>> I got solution >>>>>>> >>>>>>> First I designed on job and run shell commands >>>>>>> whoami >>>>>>> printenv >>>>>>> >>>>>>> Result: >>>>>>> anonymous >>>>>>> printenv result did now show Display =:0 >>>>>>> >>>>>>> Then I export DISPAY =:0 from terminal (master user) >>>>>>> and then restart Jenkins with (master user) >>>>>>> >>>>>>> it worked :) >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Sunday, 6 September 2015 13:29:51 UTC+2, Kirshan Luhana wrote: >>>>>>>> >>>>>>>> Thanks, I already checked. >>>>>>>> Actually I am new to Jenkins, did not understand VNC server stuff >>>>>>>> and I have very fresh linux OS with only jenkins installed (Latest) and >>>>>>>> then I tried to run emulator and it fails. >>>>>>>> >>>>>>>> >>>>>>>> On Sunday, 6 September 2015 13:20:25 UTC+2, Victor Martinez wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> There is already a closed jira ticket about that issue: >>>>>>>>> >>>>>>>>> - https://issues.jenkins-ci.org/browse/JENKINS-6912 >>>>>>>>> >>>>>>>>> It might be related, otherwise can you please raise a ticket and >>>>>>>>> explain your current setup (jenkins version, java version, plugin >>>>>>>>> list and >>>>>>>>> their versions and your job setup?) >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> >>>>>>>>> On Sunday, 6 September 2015 01:06:17 UTC+2, Kirshan Luhana wrote: >>>>>>>>>> >>>>>>>>>> But when I run this on command line it working fine. >>>>>>>>>> >>>>>>>>>> Started by user anonymous <http://localhost:8080/user/null> >>>>>>>>>> Building in workspace /home/jenkins/workspace/emulatorTest >>>>>>>>>> $ /home/jenkins/tools/android-sdk/tools/android list target >>>>>>>>>> [android] Using Android SDK: /home/jenkins/tools/android-sdk >>>>>>>>>> [android] Creating Android AVD: >>>>>>>>>> /home/jenkins/workspace/emulatorTest/.android/avd/hudson_en-US_640_WXGA720_android-23_tdsltest1.avd >>>>>>>>>> [android] /home/jenkins/tools/android-sdk/tools/android create avd >>>>>>>>>> -f -a -s WXGA720 -n hudson_en-US_640_WXGA720_android-23_tdsltest1 -t >>>>>>>>>> android-23 >>>>>>>>>> >>>>>>>>>> $ /home/jenkins/tools/android-sdk/platform-tools/adb start-server >>>>>>>>>> >>>>>>>>>> * daemon not running. starting it now on port 8297 * >>>>>>>>>> * daemon started successfully * >>>>>>>>>> $ /home/jenkins/tools/android-sdk/platform-tools/adb start-server >>>>>>>>>> $ /home/jenkins/tools/android-sdk/tools/emulator -snapshot-list >>>>>>>>>> -no-window -avd hudson_en-US_640_WXGA720_android-23_tdsltest1 >>>>>>>>>> [android] Starting Android emulator and creating initial snapshot >>>>>>>>>> $ /home/jenkins/tools/android-sdk/tools/emulator -ports 8295,8296 >>>>>>>>>> -prop persist.sys.language=en -prop persist.sys.country=US -avd >>>>>>>>>> hudson_en-US_640_WXGA720_android-23_tdsltest1 -no-snapshot-load >>>>>>>>>> -no-snapshot-save -wipe-data >>>>>>>>>> SDL init failure, reason is: No available video device >>>>>>>>>> >>>>>>>>>> [android] Emulator did not appear to start; giving up >>>>>>>>>> $ /home/jenkins/tools/android-sdk/platform-tools/adb disconnect >>>>>>>>>> localhost:8296 >>>>>>>>>> [android] Stopping Android emulator >>>>>>>>>> $ /home/jenkins/tools/android-sdk/platform-tools/adb kill-server >>>>>>>>>> >>>>>>>>>> Finished: NOT_BUILT >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Saturday, 5 September 2015 04:39:42 UTC+2, Kirshan Luhana >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> Please solve this bug >>>>>>>>>>> I installed fresh copy of linux mint , jenkins and Android >>>>>>>>>>> emulator plugin and when trying to run emulator , I am getting >>>>>>>>>>> error >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> *SDL init failure, reason is: No available video device* >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> I alrady googled a lot , and installed sudo apt-get install >>>>>>>>>>> ia32-libs-sdl >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> but no good solution. >>>>>>>>>>> >>>>>>>>>>> I have HP envy Laptop and in bios visualization on. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Jenkins Users" group. >>>>>>> >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>> >>>>>> >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/b8d23f8a-7527-4377-9e45-2a76be30e1a9%40googlegroups.com >>>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/b8d23f8a-7527-4377-9e45-2a76be30e1a9%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> >>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-users/5ea5df0b-f007-41d2-b6b2-88e712329b76%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-users/5ea5df0b-f007-41d2-b6b2-88e712329b76%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/a0f17b78-afde-4f6b-ad0c-c812b0671f20%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/a0f17b78-afde-4f6b-ad0c-c812b0671f20%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/66f3146a-e4f4-4ba3-b724-e2cc90090e84%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/66f3146a-e4f4-4ba3-b724-e2cc90090e84%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEmhJa4ncJYgCMDQsy9F%2BiErkOSuO8o%3DhyVmpfZG82pFQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
