X apps not opening on frieza

[Allan LeSage]

XChat not opening on frieza rc-proposed r88 .

TEST CASE
1. Tap XChat icon.
EXPECTED
XChat opens.
ACTUAL
Nothing.

Will also tag libertine although I performed a pretty extensive exploratory test upon release of 1.0, wondering if capnproto or unity8 landings might be involved?

############
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 88
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
last update: 2016-04-21 16:24:53
version version: 88
version ubuntu: 20160421
version device: 20160411.0
version custom: 20160330--38-10-vivid
phablet@ubuntu-phablet:~$ apt-cache policy liblibertine1
liblibertine1:
  Installed: 1.0.0+15.04.20160411-0ubuntu1
  Candidate: 1.0.0+15.04.20160411-0ubuntu1
  Version table:
 *** 1.0.0+15.04.20160411-0ubuntu1 0
        100 /var/lib/dpkg/status
phablet@ubuntu-phablet:~$ apt-cache policy unity8
unity8:
  Installed: 8.12+15.04.20160414.1-0ubuntu1
  Candidate: 8.12+15.04.20160414.1-0ubuntu1
  Version table:
 *** 8.12+15.04.20160414.1-0ubuntu1 0
        100 /var/lib/dpkg/status

[Pat McGowan (pat-mcgowan)]

@allan its working for me on 88, although I do not have it configured yet
You have puritine? this is a standard install?

[Allan LeSage (allanlesage)]

This is from a fresh flash via ubuntu-device-flash, apt-cache search puritine turning up empty for me?

[Allan LeSage (allanlesage)]

FWIW davmor2 reproduced this earlier in the day informally.

[Christopher Townsend (townsend)]

Is there ~/.cache/upstart/application-legacy-puritine_xchat-gnome_0.0-.log and if so, could you please provide the output?

Also, Puritine is a click package, so it won't show up in apt-cache. Try 'click list'.

Thanks!

[Allan LeSage (allanlesage)]

@townsend

phablet@ubuntu-phablet:~$ click list | grep puritine
com.ubuntu.puritine 0.7

[Allan LeSage (allanlesage)]

More logs to retrieve? I did have an XMir crash while testing external monitor last go, but that was on a previous flash.

[Christopher Townsend (townsend)]

The image contains an invalid ~/.local/share/libertine/ContainersConfig.json file which doesn't allow the puritine-click Upstart job to link to the correct ContainersConfig.json.

So the short of it is that the image needs to have the 0 byte ~/.local/share/libertine/ContainersConfig.json file removed.

[Jean-Baptiste Lallement (jibel)]

After a fresh flash, it seems that this file is created on first boot after the wizard.

[Christopher Townsend (townsend)]

So, after doing more debugging and thinking about other processes that call into liblibertine, an unintended side effect is that a 0 byte file can be created before the puritine-click upstart job creates the link. So I was wrong on my initial assessment:(

Anyways, I have one fix in the pipe that will take care of this no matter what. I can also fix the upstart job to make the link before the 0 byte file creating, which I will do to.

I will get those fixes in a landing soon.

[Libertine CI Bot (libertine-ci-bot)]

Fix committed into lp:libertine at revision 211, scheduled for release in libertine, milestone Unknown