It would be helpful to run the Apps scope manually with debug enabled, reproduce the issue and grab the output, i.e.
1) Make sure the scope is not running already (ps aux|grep clickscope)
2) Log in via adb and run it as phablet user:
U1_DEBUG=1 /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner "" /usr/lib/arm-linux-gnueabihf/unity-scopes/clickapps/clickscope.ini > output.log 2>&1
3) Reproduce the problem & stop the scope (CTRL+C), attach output.log.
Alternatively, add "env U1_DEBUG=1" below "author" line in /usr/share/upstart/sessions/scope-registry.conf to enable debug permanently, then reboot the phone - if the problem is reproduced, the debug output should be appended to /home/phablet/.cache/upstart/scope-registry.log.
It would be helpful to run the Apps scope manually with debug enabled, reproduce the issue and grab the output, i.e. arm-linux- gnueabihf/ unity-scopes/ scoperunner "" /usr/lib/ arm-linux- gnueabihf/ unity-scopes/ clickapps/ clickscope. ini > output.log 2>&1
1) Make sure the scope is not running already (ps aux|grep clickscope)
2) Log in via adb and run it as phablet user:
U1_DEBUG=1 /usr/lib/
3) Reproduce the problem & stop the scope (CTRL+C), attach output.log.
Alternatively, add "env U1_DEBUG=1" below "author" line in /usr/share/ upstart/ sessions/ scope-registry. conf to enable debug permanently, then reboot the phone - if the problem is reproduced, the debug output should be appended to /home/phablet/ .cache/ upstart/ scope-registry. log.