compatibility bug with fedora

Bug #1824158 reported by Zygmunt Krynicki on 2019-04-10
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
snapd
High
Unassigned

Bug Description

From https://forum.snapcraft.io/t/compatibility-issues-running-snaps-under-fedora-29/10402/12

We see:

[pid 4565] access("/usr/lib/snapd/snap-device-helper", X_OK) = 0
[pid 4565] execve("/usr/lib/snapd/snap-device-helper", ["/usr/lib/snapd/snap-device-helpe"..., "add", "snap_notepad-plus-plus_notepad-p"..., "/sys/class/mem/null", "1:3"], 0x7ffd0dce6418 /* 0 vars */) = -1 ENOENT (No such file or directory)
[pid 4565] write(2, "execl failed", 12execl failed) = 12
[pid 4565] write(2, ": No such file or directory\n", 28: No such file or directory

This is a problem of the location of the interpreter of the shell script "snap-device-helper"

Zygmunt Krynicki (zyga) on 2019-04-10
Changed in snapd:
status: New → Confirmed
importance: Undecided → High

On Fedora, the interpreter is #!/usr/bin/sh. The change is introduced automatically when building the RPM.

Markus Neteler (neteler) wrote :

I can confirm that this change helps on Fedora 29:

diff -u /usr/libexec/snapd/snap-device-helper.orig /usr/libexec/snapd/snap-device-helper
--- /usr/libexec/snapd/snap-device-helper.orig 2019-04-23 20:52:07.000000000 +0200
+++ /usr/libexec/snapd/snap-device-helper 2019-05-07 15:15:42.341304463 +0200
@@ -1,4 +1,4 @@
-#!/usr/bin/sh
+#!/bin/bash
 # udev callout to allow a snap to access a device node
 set -e
 # debugging

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers