Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1536895

Summary:	Snapd support currently broken , missing links to /usr/lib/snapd
Product:	[Fedora] Fedora	Reporter:	j.keuseman
Component:	snapd	Assignee:	Neal Gompa <ngompa13>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	me, ngompa13
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	snapd-2.30-1.fc27 snapd-2.30-1.fc26	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-28 21:33:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description j.keuseman 2018-01-22 00:11:36 UTC

Description of problem:
Installing basic snap support does not work properly and results in errors upon any snap package installation.

Version-Release number of selected component (if applicable):
2.29.4

How reproducible:
Every time.

Steps to Reproduce:
1.Installed snap support: sudo dnf install snapd
2. Try to install simple hello : snap install hello
3. Errors are returned about missing snap-seccomp

Actual results:
Setup snap "core" (3748) security profiles (cannot setup seccomp for snap "core": fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory)... Setup snap "core" (3748) security profiles (fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory)

Expected results:
Successful installation

Additional info:
Simple fix is:
sudo ln -s /usr/libexec/snapd /usr/lib/

Comment 1 Neal Gompa 2018-01-22 14:35:38 UTC

There's an upstream fix for this already: https://github.com/snapcore/snapd/commit/fbfee0ea2b7c43de58b2091ee231cc988a9ef925

I am working on an update to fix this issue.

Comment 2 j.keuseman 2018-01-22 18:19:46 UTC

(In reply to Neal Gompa from comment #1)
> There's an upstream fix for this already:
> https://github.com/snapcore/snapd/commit/
> fbfee0ea2b7c43de58b2091ee231cc988a9ef925
> 
> I am working on an update to fix this issue.

I confirm this was Korora, the proposed fix looks good.

Comment 3 Fedora Update System 2018-01-25 09:19:10 UTC

snapd-2.30-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-798e0f02ff

Comment 4 Fedora Update System 2018-01-25 09:19:46 UTC

snapd-2.30-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-04bdce8944

Comment 5 Fedora Update System 2018-01-26 19:11:54 UTC

snapd-2.30-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-798e0f02ff

Comment 6 Fedora Update System 2018-01-26 19:49:03 UTC

snapd-2.30-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-04bdce8944

Comment 7 Fedora Update System 2018-01-28 21:33:28 UTC

snapd-2.30-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2018-02-04 21:22:07 UTC

snapd-2.30-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.