all my projects show this in the sdk bash: /usr/bin/webapp-container: No such file or directory Application finished with exit code 127.
but the command is there ? wayneward@shanghai:~$ /usr/bin/webapp-container The application has been launched with no explicit or system provided app id. An application id can be set by using the --app-id command line parameter and setting it to a unique application specific value or using the APP_ID environment variable. any ideas... Wayne On Tue, 2016-06-21 at 08:16 +0200, Benjamin Zeller wrote: > On 06/21/2016 03:07 AM, Felipe De La Puente wrote: > > Hi Benjamin, > > > > Thanks a lot for your answers and help! > > > > On Mon, Jun 20, 2016 at 3:28 PM, Benjamin Zeller <benjamin.zeller@c > > anonical.com> wrote: > > > On 06/20/2016 06:54 PM, Felipe De La Puente wrote: > > > > Hi Zoltan, > > > > > > > > I gave the new sdk-ide a little try. I created a container for > > > > 16.04-amd64-desktop, when I tried to build my existing > > > > projects, they failed not finding the qmake .pro file. Didn't > > > > have time to dig into the > > > > problem yet... > > > > > > > > Some questions: > > > > 1. Is the change backwards compatible with projects that > > > > started with the old scheme? > > > Yes, your projects should still compile. But you will loose > > > existing project configurations, since your schroot based Kits > > > are gone. > > > So you need to add your new Kits to the project. > > > > 2. Is it mandatory to reset qt-creator settings? > > > No. Normally QtC should remove the old Kits once they are gone > > > and discover the new ones. You can also just reset those files: > > > ~/.config/QtProject/qtcreator/cmaketools.xml > > > ~/.config/QtProject/qtcreator/devices.xml > > > ~/.config/QtProject/qtcreator/profiles.xml > > > ~/.config/QtProject/qtcreator/toolchains.xml > > > > > > This will only reset the toolchains and leave your other settings > > > intact. > > > > > > > > Today when I tried the failing project it compiled successfully, so > > there must have been something that got inconsistent the other > > day... > > > > > > 3. When should we expect the NVIDIA driver issue to be fixed? > > > This is a really tricky issue. We have a possible fix, but it > > > seems to fail in some conditions we > > > did not figure out yet. This is basically the steps to make it > > > work in the chroots (not tested for typos): > > > > > > http://pastebin.ubuntu.com/17429225/ > > > > > > > > I implemented your suggested script and got the app running. It > > rendered the main view for an instant until the SceneGraph creation > > failed. So it seems something GL related is still inconsistent. > > > > The exact debug message was: > > > > "Failed to create OpenGL context for format QSurfaceFormat(version > > 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, > > greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, > > stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1, > > profile 0)" > 1. Do you have the correct nvidia driver mounted? You can use "cat > /sys/module/nvidia/version" to get the version (only use the major > number) > 2. The script is running glxgears to check if the glx drivers work. > Probably mesa-utils was not installed in your container. Could you > please check if glxgears runs for you? > > To get glxgears: > > lxc exec ${CONTAINER_NAME} -- apt install mesa-utils > usdk-target exec ${CONTAINER_NAME} -- bash -c "export DISPLAY=:0.0 && > glxgears" > > If glxgears shows up then there is a different issue. > > Thanks for testing :) > > Cheers, > > Benjamin > > > > > > > But we need to figure out the corner cases. However you can try > > > to use the script to fix your container. > > > I can not give you a estimate when it will be solved, first we > > > need to figure out why it breaks sometimes. > > > > > > Cheers, > > > > > > Benjamin > > > > > > Best Regards, > > Felipe. > > > > > > > > > > On Tue, Jun 14, 2016 at 8:30 AM, Leonardo "LeartS" Donelli <lea > > > > rt...@gmail.com> wrote: > > > > > This sounds really, really great. I have a very very limited > > > > > experience with the SDK/IDE (just trying some things around) > > > > > but > > > > > already encountered basically all the issues described in the > > > > > preface. > > > > > Good job. > > > > > > > > > > On 14 June 2016 at 13:38, Zoltán Balogh <zoltan.balogh@canoni > > > > > cal.com> wrote: > > > > > > And calling for beta testers > > > > > > > > > > > > https://developer.ubuntu.com/en/blog/2016/06/14/calling-tes > > > > > ters-new-ubuntu-sdk-ide-post/ > > > > > > > > > > > > cheers, > > > > > > > > > > > > bzoltan > > > > > > > > > > > > -- > > > > > > Mailing list: https://launchpad.net/~ubuntu-phone > > > > > > Post to : ubuntu-phone@lists.launchpad.net > > > > > > Unsubscribe : https://launchpad.net/~ubuntu-phone > > > > > > More help : https://help.launchpad.net/ListHelp > > > > > > > > > > -- > > > > > Mailing list: https://launchpad.net/~ubuntu-phone > > > > > Post to : ubuntu-phone@lists.launchpad.net > > > > > Unsubscribe : https://launchpad.net/~ubuntu-phone > > > > > More help : https://help.launchpad.net/ListHelp > > > > > > > > > > > > > > > > > > > -- > > > Mailing list: https://launchpad.net/~ubuntu-phone > > > Post to : ubuntu-phone@lists.launchpad.net > > > Unsubscribe : https://launchpad.net/~ubuntu-phone > > > More help : https://help.launchpad.net/ListHelp > > > > > > > > -- > Mailing list: https://launchpad.net/~ubuntu-phone > Post to : ubuntu-phone@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-phone > More help : https://help.launchpad.net/ListHelp -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
