Ubuntu App Platform

Fail to access the shared content if app starts before connect interface

Bug #1645731 reported by Renato Araujo Oliveira Filho
78
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Confirmed
High
Pat McGowan
Canonical System Image p2 "Ubuntu Personal"
Snappy
Fix Released
High
Zygmunt Krynicki
Ubuntu App Platform
Confirmed
High
Unassigned
snapd
Fix Released
Undecided
Unassigned

Bug Description

Snapd fails to mount the content shared directory if the app starts before connect the interface.

Same happens if you install a new version of the snap package. The directory does not get mounted correct.

HOW TO REPRODUCE:

1- Install ubuntu-app-platform
2- Install any app that uses the 'ubuntu-app-platform'
3- Launch the app (app will complain about the missing connection)
4- Connect the interface to your app
5- Launch the app

Expected:
App launches correct

Current:
The shared directory still empty

See original description
Renato Araujo Oliveira Filho (renatofilho)
description: updated
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

This will require the live namespace mutation tool that we designed but didn't implement. I'll work on getting this fixed in snapd.

Changed in ubuntu-app-platform:
status: New → Confirmed
assignee: nobody → Zygmunt Krynicki (zyga)
Changed in snappy:
status: New → Confirmed
Changed in ubuntu-app-platform:
assignee: Zygmunt Krynicki (zyga) → nobody
Changed in snappy:
importance: Undecided → High
assignee: nobody → Zygmunt Krynicki (zyga)
Tim Peeters (tpeeters)
Changed in ubuntu-app-platform:
importance: Undecided → High
Pat McGowan (pat-mcgowan)
Changed in canonical-devices-system-image:
assignee: nobody → Pat McGowan (pat-mcgowan)
importance: Undecided → High
milestone: none → p2
status: New → Confirmed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

FYI, a less painful workaround to reinstalling the snap is while waiting for the proper fix is:

1. stop your snap
2. do the snap connect command
3. $ sudo /usr/lib/snapd/snap-discard-ns <snapname>
4. start your snap

Revision history for this message
Kyle Fazzari (kyrofa) wrote :

Note that I've had this happen to me between installs as well:

1. Install snap
2. Snap connect
3. Use (works fine)
4. Hack on snap
5. Install again (over the top)
6. Interface is still connected
7. Mount doesn't happen and requires a run of `snap-discard-ns`.

Revision history for this message
Jamie Bennett (jamiebennett) wrote :

Added this as priority to the Snappy Team's roadmap. Will update the bug shortly on when this fix is expected to land.

Revision history for this message
Kyle Fazzari (kyrofa) wrote :

@Jamie, any update here?

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Marking as In Progress since I know Zygmunt has been working on it.

Changed in snappy:
status: Confirmed → In Progress
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

Note lp:1670371 in case its related

Revision history for this message
Jim Hodapp (jhodapp) wrote :

Did anything ever happen on fixing this bug?

Revision history for this message
Lucy Llewellyn (lucyllewy) wrote :

This is especially relevant with the effort to include the gnome-3-24/gnome-platform snap and it's interface in multiple consuming snaps. While there is a quest to get that particular interface auto connected it will be an issue for any other similar projects that are more third-party efforts.

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

This should be fixed now. Can you please try with snapd 2.26.14 (just use stable channel) and report back if it is a problem for you?

Changed in snappy:
status: In Progress → Fix Released
Revision history for this message
Lucy Llewellyn (lucyllewy) wrote :

On my offline install of corebird (an experiment to add gnome-3-24 support via the platform snap) it still fails to connect after the snap has been run:

$ sudo snap install --dangerous corebird_1.5.1_amd64.snap

$ corebird
You need to connect this snap to the gnome platform snap.

$ sudo snap connect corebird:gnome-3-24-platform gnome-3-24:gnome-3-24-platform

$ corebird
You need to connect this snap to the gnome platform snap.

Revision history for this message
Lucy Llewellyn (lucyllewy) wrote :

the message "you need to connect..." is from the desktop-launch script which detects whether the platform snap is mounted in ${SNAP}/gnome-platform. it reports that message when the platform is not mounted.

Sergio Schvezov (sergiusens)
Changed in snappy:
status: Fix Released → Triaged
Revision history for this message
Lucy Llewellyn (lucyllewy) wrote :

Just to ensure everyone is on the same page, there's also discussion of this particular issue affecting the gnome-platform interface on the forums: https://forum.snapcraft.io/t/content-interface-connection-issues/1585

Zygmunt Krynicki (zyga)
Changed in snappy:
status: Triaged → In Progress
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

As indicated on the forum, the actual fix was released with 2.27.2, it landed in master after the long-standing release branch 2.26.x was forked.

Changed in snappy:
status: In Progress → Fix Released
Changed in snapd:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.