Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Component not found; installation not possible on Fedora Atomic #429

Closed
gluckgluckwasserbauch opened this issue Jan 23, 2024 · 2 comments · Fixed by #443
Closed

Component not found; installation not possible on Fedora Atomic #429

gluckgluckwasserbauch opened this issue Jan 23, 2024 · 2 comments · Fixed by #443
Labels
bug Something isn't working

Comments

@gluckgluckwasserbauch
Copy link

gluckgluckwasserbauch commented Jan 23, 2024

On issue #422, I thought I couldn't install because the device isn't supported yet.
As we found out, it isn't because of the missing support, but due to some misbehaviour on my distro.

Error and backgrounds

Error

The error is: '/system/bin/sh: grep: not foun'

System information

OS: Fedora Atomic (the immutable variants of Fedora), to be more precise, the kinoite-main-image from universal-blue.org.
But I think it should be reproducible for every other image-based Fedora flavour too, maybe even for other distros like NixOS, OpenSuse MicroOS or VanillaOS.
Installation method: Flatpak from flathub.org; I didn't try it with Distrobox yet. Would lead to the same problem I guess.

Potential reason

As far as I (no expert) can guess, this is due to some missing symlinks.
Image-distros use a lot of symlinks to get around the permission problems. Just to visualize, here's a screenshot of my file system:
Screenshot_20240123_114545
Every chain symbol on the icon shows that this folder is just a symlink. And there are a lot of them, including the /bin/ folder, where sh should be located for the installer to make use of.

Solution

Add a line of something like "if /bin/sh not found, then use /usr/bin/sh instead".

I would like to offer you that I can try it out myself, but sadly, I have zero coding experience. Even the bug report was a bit challenging for me... 😓

@gluckgluckwasserbauch gluckgluckwasserbauch added the bug Something isn't working label Jan 23, 2024
@anon1892
Copy link
Member

Thank you, we will look at it! (I'm busy these days...)

As we found out, it isn't because of the missing support, but due to some misbehaviour on my distro.

There is a bug with your distro, but your phone is not yet supported too (so we keep open #422)

@tsterbak tsterbak linked a pull request Feb 7, 2024 that will close this issue
tsterbak added a commit that referenced this issue Mar 13, 2024
Resolves #429 

Could you please test this @gluckgluckwasserbauch
@tsterbak
Copy link
Member

Should be resolved with the next release :) Let me know if this error still persists and we can open it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants