syscall error on i386 unless socketcall is allowed
Bug #1594675 reported by
Sebastien Bacher
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd (Ubuntu) |
Fix Released
|
High
|
Jamie Strandboge | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Released
|
High
|
Jamie Strandboge |
Bug Description
Using snapd 2.0.9 on xenial on i386, snap commands hit a syscall error on i386 unless "socketcall" is allowed in the profile, that should perhaps be allowed by default as a workaround until the libseccomp issue is resolved?
Changed in snapd (Ubuntu): | |
importance: | Undecided → High |
summary: |
- syscall error on i386 + syscall error on i386 unless socketcall is allowed |
Changed in snapd (Ubuntu): | |
status: | New → In Progress |
To post a comment you must log in.
This is merged and will be in 2.0.10.