FYI, I reported a bug that was just marked a dupe of this one that did not require upstart-app-launch but used aa-exec-click instead. I wonder if it has to do with the environment since aa-exec-click and upstart-app-launch will setup quite a bit of the environment. When launching my blabble app (available in the app store), the following environment is set up by aa-exec-click (I ommitted the env vars that aa-exec-click doesn't set):
To reproduce what I did:
1. grab some click app and install it on the desktop with 'sudo click install --user=$user <click package>
2. adjust /usr/bin/aa-exec-click to do 'set > /tmp/foo' just before the call to aa-exec
3. cd to the app directory (ie, what is in Path= in the ~/.local/share/applications/<app>.desktop
4. run aa-exec-click from this directory. Eg:
aa-exec-click -p com.ubuntu.developer.jdstrand.blabble_blabble_0.2.1 -- qmlscene blabble.qml
If it is indeed something in the environment, I suggest copying /usr/bin/aa-exec-click somewhere and modifying it for debugging/triaging.
FYI, I reported a bug that was just marked a dupe of this one that did not require upstart-app-launch but used aa-exec-click instead. I wonder if it has to do with the environment since aa-exec-click and upstart-app-launch will setup quite a bit of the environment. When launching my blabble app (available in the app store), the following environment is set up by aa-exec-click (I ommitted the env vars that aa-exec-click doesn't set):
APP_ID= 'com.ubuntu. developer. jdstrand. blabble_ blabble_ 0.2.1' PATH='/ opt/click. ubuntu. com/.click/ users/jamie/ com.ubuntu. developer. jdstrand. blabble/ lib/x86_ 64-linux- gnu' opt/click. ubuntu. com/.click/ users/jamie/ com.ubuntu. developer. jdstrand. blabble/ lib/x86_ 64-linux- gnu/bin: /opt/click. ubuntu. com/.click/ users/jamie/ com.ubuntu. developer. jdstrand. blabble: /home/jamie/ bin:/usr/ local/sbin: /usr/local/ bin:/usr/ sbin:/usr/ bin:/sbin: /bin:/usr/ games:/ usr/local/ games:/ sbin:/usr/ sbin:/usr/ local/sbin' PATH='/ opt/click. ubuntu. com/.click/ users/jamie/ com.ubuntu. developer. jdstrand. blabble/ lib/x86_ 64-linux- gnu' '/run/user/ 1000/confined/ com.ubuntu. developer. jdstrand. blabble' APPLICATION_ ISOLATION= '1' HOME=/home/ jamie/. cache DIRS=/etc/ xdg/xdg- ubuntu: /usr/share/ upstart/ xdg:/etc/ xdg HOME=/home/ jamie/. config DIRS='/ opt/click. ubuntu. com/.click/ users/jamie/ com.ubuntu. developer. jdstrand. blabble: /usr/share/ ubuntu: /usr/share/ gnome:/ usr/local/ share/: /usr/share/ ' HOME=/home/ jamie/. local/share DIR=/run/ user/1000 DISK_CACHE_ PATH='/ home/jamie/ .cache/ com.ubuntu. developer. jdstrand. blabble'
LD_LIBRARY_
PATH='/
QML2_IMPORT_
TMPDIR=
UBUNTU_
XDG_CACHE_
XDG_CONFIG_
XDG_CONFIG_
XDG_DATA_
XDG_DATA_
XDG_RUNTIME_
__GL_SHADER_
To reproduce what I did: aa-exec- click to do 'set > /tmp/foo' just before the call to aa-exec share/applicati ons/<app> .desktop developer. jdstrand. blabble_ blabble_ 0.2.1 -- qmlscene blabble.qml
1. grab some click app and install it on the desktop with 'sudo click install --user=$user <click package>
2. adjust /usr/bin/
3. cd to the app directory (ie, what is in Path= in the ~/.local/
4. run aa-exec-click from this directory. Eg:
aa-exec-click -p com.ubuntu.
If it is indeed something in the environment, I suggest copying /usr/bin/ aa-exec- click somewhere and modifying it for debugging/triaging.