question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

RPM installation fails on Fedora Silverblue

See original GitHub issue
  • Etcher version: Latest (v1.5.56)
  • Operating system and architecture: Fedora Silverblue 30

The RPM does not install properly.

Checking out tree c1d33ee... done
Enabled rpm-md repositories: updates fedora-cisco-openh264 fedora etcher-rpm
rpm-md repo 'updates' (cached); generated: 2019-09-09T01:56:55Z
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2019-03-21T15:16:16Z
rpm-md repo 'fedora' (cached); generated: 2019-04-25T23:49:41Z
rpm-md repo 'etcher-rpm' (cached); generated: 2019-07-22T10:35:47Z
Importing rpm-md... done
Resolving dependencies... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
error: Running %post for balena-etcher-electron: Executing bwrap(/bin/sh): Child process killed by signal 1; run `journalctl -t 'rpm-ostree(balena-etcher-electron.post)'` for more information
-- Logs begin at Fri 2019-08-23 07:18:27 CEST, end at Mon 2019-09-09 12:24:43 CEST. --
Sep 06 10:57:00 synergy rpm-ostree(balena-etcher-electron.post)[2404]: ln: failed to create symbolic link '/usr/local/bin/balena-etcher-electron': No such file or directory
-- Reboot --
Sep 09 12:00:55 synergy rpm-ostree(balena-etcher-electron.post)[2445]: ln: failed to create symbolic link '/usr/local/bin/balena-etcher-electron': No such file or directory
Sep 09 12:02:43 synergy rpm-ostree(balena-etcher-electron.post)[2445]: ln: failed to create symbolic link '/usr/local/bin/balena-etcher-electron': No such file or directory

Issue Analytics

  • State:open
  • Created 4 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

2reactions
ssusbauercommented, Jan 19, 2020

Balena Etcher is not available in any other form, so installing it from an RPM is the only way to install it on Silverblue.

The Etcher AppImage works fine on SilverBlue.

2reactions
ccarguelo-ucacommented, Nov 4, 2019
  • Etcher version: Latest (v1.5.56)
  • Operating system and architecture: Fedora Silverblue 30

The RPM does not install properly.

Checking out tree c1d33ee... done
Enabled rpm-md repositories: updates fedora-cisco-openh264 fedora etcher-rpm
rpm-md repo 'updates' (cached); generated: 2019-09-09T01:56:55Z
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2019-03-21T15:16:16Z
rpm-md repo 'fedora' (cached); generated: 2019-04-25T23:49:41Z
rpm-md repo 'etcher-rpm' (cached); generated: 2019-07-22T10:35:47Z
Importing rpm-md... done
Resolving dependencies... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
error: Running %post for balena-etcher-electron: Executing bwrap(/bin/sh): Child process killed by signal 1; run `journalctl -t 'rpm-ostree(balena-etcher-electron.post)'` for more information
-- Logs begin at Fri 2019-08-23 07:18:27 CEST, end at Mon 2019-09-09 12:24:43 CEST. --
Sep 06 10:57:00 synergy rpm-ostree(balena-etcher-electron.post)[2404]: ln: failed to create symbolic link '/usr/local/bin/balena-etcher-electron': No such file or directory
-- Reboot --
Sep 09 12:00:55 synergy rpm-ostree(balena-etcher-electron.post)[2445]: ln: failed to create symbolic link '/usr/local/bin/balena-etcher-electron': No such file or directory
Sep 09 12:02:43 synergy rpm-ostree(balena-etcher-electron.post)[2445]: ln: failed to create symbolic link '/usr/local/bin/balena-etcher-electron': No such file or directory

@zamber Fedora Silverblue is not meant for installing .rpm packages, kindly check Fedora Silverblue documentation for that. Fedora-Silverblue/Getting-Started

Flatpak is the primary way that apps can be installed on Silverblue. (For information, see flatpak.org.) Flatpak works out of the box in Fedora Silverblue, and Fedora provides a small (but growing) collection of apps that can be installed.

The other main source of Flatpak apps is Flathub, which provides a large repository of Flatpak apps that can be installed.

Package layering works by modifying your Silverblue installation. As the name implies, it works by extending the packages from which Silverblue is composed. Most (but not all) RPM packages provided by Fedora can be installed on Silverblue using this method.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting - Fedora Docs
However, if you continue to encounter this problem with a newer compose, you can try to cleanup the metadata with rpm-ostree cleanup -m...
Read more >
Installation of Fedora 32 Silverblue fails with error code 32
Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result...
Read more >
Gnome Software defaults to RPM packages (Fedora ... - GitLab
Gnome Software defaults to RPM packages (Fedora Silverblue 37) · Rebase to Fedora 37 (beta) · Look for any program that is available...
Read more >
Postinst scripts for dpkg fail on Silverblue (rpm-ostree) - fedora ...
Installation of dpkg (or packages which depend on it) fails on dpkg postinst: ... Enabled rpm-md repositories: fedora-cisco-openh264 jkonecny-kakoune ...
Read more >
Fedora 36 Silverblue software update failure - Medium
The update failed. I wasn't bothered at first but then I tried to install something else with rpm-ostree and again, after rebooting the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found