etcher: Error at launch when GRUB_CMDLINE_LINUX="net.ifnames=0"

  • Etcher version: 1.0.0. beta 19 x64
  • Operating system and architecture: Ubuntu Mate - 16.04.2 TLS
  • Do you see any meaningful error information on DevTools? Alert box on launch

When /etc/default/grub contains GRUB_CMDLINE_LINUX=“net.ifnames=0” Etcher shows an error at launch, before displaying:

Command failed: /tmp/.org.chromium.Chromium.KohxiJ
/tmp/.org.chromium.Chromium.KohxiJ: ligne 122: UDEV_net.ifnames=0 : commande introuvable

Error: Command failed: /tmp/.org.chromium.Chromium.KohxiJ
/tmp/.org.chromium.Chromium.KohxiJ: ligne 122: UDEV_net.ifnames=0 : commande introuvable

    at ChildProcess.exithandler (child_process.js:218:12)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Socket.<anonymous> (internal/child_process.js:334:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:493:12)

Same error when launched in the devtool console log. (The very same etcher was working on the same box before the Grub modification) Image selection is then ok, but etcher doesn’t recognize any usb drive. Tried with the https://dl.bintray.com/resin-io/debian stable etcher repo too, idem.

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 28 (20 by maintainers)

Commits related to this issue

Most upvoted comments

Hi guys, Sorry it took so long. Got it and tested, no problem, works fine now: thanks a lot!

Yeah, makes sense. I’ll prepare one and upload it here.

On Ubuntu 14.04, awk, mawk and gawk all behave identically with the awk-code used here.

In the meantime, I rebooted without the net.ifnames=0 : etcher works well. Re-rebooted with the line.

Tested the script, script fails with the same error. Removed 2 of the backslashes, seems to work:

device: /dev/sda
description: "SanDisk SDSSDA24"
size: 240057409536
mountpoints:
  - path: /boot
raw: /dev/sda
protected: False
system: True

Oh, I see. If that’s the case I wonder why I didn’t catch it in my testing 😕

@actuino Could you please paste here the result of

udevadm info --query=property --export --export-prefix=UDEV_ --name="/dev/sda"

Thanks.