-
Notifications
You must be signed in to change notification settings - Fork 66
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
Fetch Failed Raspberry Pi armv7 #138
Comments
How much RAM and disk space is available on the machine? |
I have 1GB RAM and 400+ GB of disk space remaining. Would it be a RAM issue with running chromium? |
Indeed, I've seen this kind of error before in this situation. The problem is that the error message issued by Chrome is very generic, so it's not easy to know what's causing the problem. You might be able to fix the problem by passing some switches to Chrome. For example Example: FYI, the complete list of switches is available here: https://peter.sh/experiments/chromium-command-line-switches. Some of them are already passed by |
Thanks for that - I've tried passing those args through. The first time it was successful with only the first 2 (low end device mode and scale factor) but I tried again and it would just continue indefinitely while CPU usage is at 100%. Nothing changed when adding the last software rasterizer flag. Is there any way to see verbose logs while running the command? |
I'm not aware of a way to display detailed logs with Chrome. I'd recommend looking for more info about other switches you might use. AI assistants are pretty good for that, see https://chatgpt.com/share/672d4826-48ac-800e-99c5-5ac8d222bde0 for example. |
I have the following error when attempting to use
single-file-cli
on my Raspberry Pi 3B. Seems to be related to #122 but there was no solution from that post. This is running from within a docker container (specifically linkding - see this issue as well).Other OS details:
Raspbian 1:6.6.51-1+rpt3 (2024-10-08) armv7l Linux
Any ideas on how to approach this? Thanks
The text was updated successfully, but these errors were encountered: