The Avila project

[Avila]puritine click v0.5 Firefox fails to launch

Bug #1532856 reported by Victor Tuson Palau on 2016-01-11

This bug report is a duplicate of: Bug #1532858: Some puritine packaged apps don't open on some devices. Edit Remove

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Canonical Pocket Desktop	New	Critical	kevin gunn
Libertine	Fix Committed	Critical	Christopher Townsend
Puritine	Invalid	Critical	Christopher Townsend
The Avila project	In Progress	Critical	Christopher Townsend	The Avila project ww02-2016
libertine (Ubuntu)	Fix Released	Critical	Christopher Townsend

Bug Description

Running firefox from puritine v0.5 and firefox launches but immediately reports : Your firefox profile could not be loaded. it may be missing or inaccessible.
-----------------------
confirmed that there are no issues with firefox launching and usability on N4/N7

See original description

Tags:

Related branches

lp://staging/~townsend/libertine/disable-seccomp

Merged into lp://staging/libertine at revision 156

Libertine CI Bot: Approve (continuous-integration) on 2016-01-14

Stephen M. Webb (community): Approve on 2016-01-14

Victor Tuson Palau (vtuson) on 2016-01-11

Changed in avila:
status:	New → Confirmed
importance:	Undecided → Critical
milestone:	none → alpha

kevin gunn (kgunn72) on 2016-01-11

Changed in canonical-pocket-desktop:
importance:	Undecided → Critical
Changed in puritine:
importance:	Undecided → Critical
assignee:	nobody → Christopher Townsend (townsend)
Changed in canonical-pocket-desktop:
assignee:	nobody → kevin gunn (kgunn72)

Revision history for this message

kevin gunn (kgunn72) wrote on 2016-01-11:

@victor - slightly confused, so FF does launch? does it not allow navigation?

Jason Yen (jasonyen) on 2016-01-12

tags:

added: ue

kevin gunn (kgunn72) on 2016-01-12

description:

updated

Revision history for this message

Christopher Townsend (townsend) wrote on 2016-01-12:

Could you please provide ~/.cache/upstart/application-legacy-puritine_firefox_0.0-.log?

Seems maybe it's not able to write to home directory that is mounted inside the container for some reason.

Revision history for this message

Chunsang Jeong (chunsang) wrote on 2016-01-13:

Please refer below;
https://pastebin.canonical.com/147505/

Jason Yen (jasonyen) on 2016-01-13

Changed in avila:
assignee:	nobody → Christopher Townsend (townsend)

Christopher Townsend (townsend) on 2016-01-13

Changed in puritine:
status:	New → In Progress
Changed in avila:
status:	Confirmed → In Progress

Revision history for this message

John McAleely (john.mcaleely) wrote on 2016-01-14:

Interesting. Sounds similar to some of the issues we had at bring up with (AFAIK Mir/GLES). tvoss & morphis fixed those, if that's a help.

Revision history for this message

John McAleely (john.mcaleely) wrote on 2016-01-14:

Here's the wiki documenting the archietcture on these devices which use a 64bit Android BSP:

https://wiki.ubuntu.com/Touch/ContainerArchitecture
"mixed-containers, 32bit Ubuntu, 64bit Android"

Revision history for this message

Christopher Townsend (townsend) wrote on 2016-01-14:

As a temporary workaround, we need to disable seccomp when running proot. Still need to figure out why this is the case, but making a temporary fix in Libertine will take care of this.

Changed in puritine:
status:	In Progress → Invalid
Changed in libertine:
status:	New → In Progress
importance:	Undecided → Critical
assignee:	nobody → Christopher Townsend (townsend)

Christopher Townsend (townsend) on 2016-01-14

Changed in libertine:
status:	In Progress → Fix Committed

Christopher Townsend (townsend) on 2016-01-14

Changed in libertine (Ubuntu):
status:	New → In Progress
importance:	Undecided → Critical
assignee:	nobody → Christopher Townsend (townsend)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-01-18:

#10

This bug was fixed in the package libertine - 0.99.8+16.04.20160114.1-0ubuntu1

---------------
libertine (0.99.8+16.04.20160114.1-0ubuntu1) xenial; urgency=medium

  [ Chris Townsend ]
  * Various fixes for making LXC containers work.
  * Refactor libertine-launch to have no explicit dependencies on
    either the LXC or chroot backends. Move specific functions to
    their respective backends.
  * Refactor the discovery of the type of container being used, so
    it's taken care inside of the class.
  * Add new libertine-launch tests.
  * Allow LXC containers access to /dev/dri devices since some X apps
    like to talk to them directly.
  * Fix Depends so that the lxc backend will be installed by default
    if the kernel supports it. Otherwise, fall back to the chroot
    backend.
  * As a temporary fix, disable seccomp when running proot. Fixes
    incompatible kernels. (LP: #1532856, #1532858)