ipfs/ipfs-desktop

Snap installations broken without "confinement: classic"

Open

#2,031 opened on Mar 14, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (5,632 stars) (912 forks)batch import
P3area/linuxhelp wantedkind/bugkind/maintenancestatus/blocked

Description

TLDR: snap confinement should not be applied to tools like ipfs-desktop. This is called "classic" mode.

I filled a request to apply "classic" confinement to ipfs-desktop in https://forum.snapcraft.io/t/ipfs-desktop-classic-review/28517

:point_right: Until this is fixed, please avoid using Snap, and choose .AppImage instead. :point_right: If you really, really want to use Snap, please raise support here.

Contributor guide

Tech stack
javascriptelectron
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Snap packaging basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue is about Snap confinement for ipfs desktop. The fix requires modifying the snapcraft.yaml file to add 'confinement: classic'. There is already a forum request at https://forum.snapcraft.io/t/ipfs desktop classic review/28517. The solution is to update the snap configuration and potentially wait for approval from the Snap store. No code changes are needed, only packaging configuration.
Snap installations broken without "confinement: classic" · ipfs/ipfs-desktop#2031 | Good First Issue