Fastfetch spits out `bad system call`.
Hi, I had an issue after updating all packages on termux, whenever I use fastfetch it spits out
bad system call fastfetch
23 Replies
Phone info:
Packages CPU architecture:
aarch64
Subscribed repositories:
# sources.list
deb https://mirror.mwt.me/termux/main stable main
# root-repo (sources.list.d/root.list)
deb https://mirror.mwt.me/termux/root root stable
# x11-repo (sources.list.d/x11.list)
deb https://mirror.mwt.me/termux/x11 x11 main
Updatable packages:
All packages up to date
termux-tools version:
1.45.0
Android version:
9
Kernel build information:
Linux localhost 4.9.117+ #2 SMP PREEMPT Mon Apr 15 12:11:48 CST 2024 aarch64 Android
Device manufacturer:
OPPO
Device model:
CPH2083
Supported ABIs:
SUPPORTED_ABIS: arm64-v8a,armeabi-v7a,armeabi
SUPPORTED_32_BIT_ABIS: armeabi-v7a,armeabi
SUPPORTED_64_BIT_ABIS: arm64-v8a
LD Variables:
LD_LIBRARY_PATH=
LD_PRELOAD=/data/data/com.termux/files/usr/lib/libtermux-exec-ld-preload.so
Installed termux plugins:
com.termux.api versionCode:1002
com.termux.x11 versionCode:15@Unix Haswell thanks for reporting, we are not allowed to edit the
fastfetch package because the upstream developer wants to micromanage the termux package (and I approve and enable them maybe i don't really know if I do but I guess I do!)Also more info
Uhh my main phone the realme c21-y, after updating, fastfetch worked without any issues
What that means is basically, rather than jumping to apply any rushed fixed myself, I have forwarded the report upstream with my own reproduction information
GitHub
[BUG] version 2.53.0 has
Bad system call in module disk on Samsun...Read the FAQ first I have checked the FAQ but the issue is not covered Description Hi, I wanted to let you know that unfortunately, after commit 822ddc6, on some devices fastfetch version 2.53.0 is...
It has android 11
Thanks
interesting, do you mean you updated termux and it stopped? or updated something else?
ohh i think i know what you mean
yes
you mean that you noticed on some devices the problem doesn't happen but on other devices it does
good, that's correct
you will notice the problem is related to the Android version used 😺
https://android.googlesource.com/platform/bionic/+/refs/heads/android15-release/libc/include/sys/stat.h#215
upstream has now fixed it. it will be fixed in the next fastfetch release. they fixed it by doing this https://github.com/fastfetch-cli/fastfetch/commit/1bbb21486c9b82c46018666f0797b86c2df64ad4
lol! the commit message
cool thanks
can we at least apply a patch before the next release?
unfortunately, we can't, or at least, I guess my vote is no because, I have been enabling the upstream developer to micromanage the termux package at their request
every time a bug happens or a feature is needed, they insist that they will be "offended" if anyone modifies fastfetch in the downstream, and they make the change desired themselves in the upstream, then allow the auto update system to bump the package in termux, or bump it themselves
however, i have been writing to them in a very flattering way and helping them by reporting issues in the upstream rather than in termux, sort of because that's just how I normally respond to that kind of situation, so that is sort of what has been going on for a while
this practice makes sense for software like fastfetch that has "termux-aware upstream" meaning that the upstream code contains explicit references to dependencies or behaviors that only exist in Termux and not in 100% stock Android or other distros
the reason is because, when an upstream developer becomes "termux-aware" and adds that kind of code into their software in order to support Termux explicitly from the upstream side, if anyone also starts editing the Termux package rather than making PRs upstream, it can make it very difficult for them to calculate what is going on when the package that people are testing and reporting issues for is not behaving the same as their own test builds
Here's some of the kind of code that I am referring to:
GitHub
fastfetch/CMakeLists.txt at 31ae7a642a180fca3c054074445eb064f9438e2...
A maintained, feature-rich and performance oriented, neofetch like system information tool. - fastfetch-cli/fastfetch
upstream
CMakeLists.txt has an elseif(ANDROID) block containing CHECK_LIBRARY_EXISTS(-l:libandroid-wordexp.a...
that's the termux-only package libandroid-wordexp-static. It doesn't exist by default in non-Termux Android apps.
so one can see from that, that upstream fastfetch needs to micromanage at least the build dependencies of the termux-packages package to make sure everything matches up with what they write upstream, and everything else they've been micromanaging kind of follows similar patterns.Y'all it's fixed now thx :3
(Y'all are the best)
I hate my main's camera ðŸ˜ðŸ˜ðŸ˜
Probably you should learn how to make screenshots properly. Press Volume Down + Power keys.
actually it turns out we can apply patches and now we have permission to, but only if the patch is associated with an upstream bug report ("bug fix") and is already merged in the upstream repository (an action known as "cherry-pick" or "backport"). this changes the situation from what I said previously.
we often do cherry-pick from nightly builds, i don't know why won't you wanna do that
it is because there was one time when the fastfetch developer got upset and told us to stop, but recently they clarified that cherry-picking bug fixes is ok
Actually if I did that and sent a screenshot to the discord that's installed in the phone, it would just die, even if the battery is on 100 or in the 90%s so I decided to capture the screen with other camera.
Idk why but I think it's just a Helio p35 moment
no it's a discord android app moment, that happens to me a lot too
(imo the discord android app is not very good so mostly i use discord.com in firefox for android, this one https://f-droid.org/en/packages/org.mozilla.fennec_fdroid/)
Forgot to mention, it does this everytime
Not only on discord, even in TikTok and yt
Suspected this is a battery issue, or I saw this issue before in a vivo y53
Whereas the power ic was shitted and shuts down often while idling
Caused because of the overheating issues of the snapdragon 425
The same can also be said on the p35