1/21/2024 0 Comments Sudo apt get update for raspbarry![]() ![]() ) from exĭpkg-deb: error: tar subprocess was killed by signal (Segmentation fault)ĭpkg: error processing archive /var/cache/apt/archives/base-files_10.3+rpi1+deb10u4_b (-unpack):ĭpkg-deb -control subprocess returned error exit status 2Įrrors were encountered while processing: Subprocess.CalledProcessError: Command '' returned non-zero exit status 2.ĭuring handling of the above exception, another exception occurred:įile "/usr/bin/apt-listchanges", line 281, in įile "/usr/bin/apt-listchanges", line 96, in mainįile "/usr/share/apt-listchanges/DebianFiles.py", line 215, in _init_įile "/usr/share/apt-listchanges/DebianFiles.py", line 128, in readdeb ![]() Obvious factors are internet and network speed, as well as which server you connect to and how busy it is, and of course, how big of an upgrade it is. There are a lot of factors that affect how long upgrades can take. Output = subprocess.check_output(command)įile "/usr/lib/python3.7/subprocess.py", line 395, in check_outputįile "/usr/lib/python3.7/subprocess.py", line 487, in run Re: Apt-get update running very slow Wed 11:45 pm. Raspberr圜 - Die deutsche Raspberry Pi Community. Roughly at least once on every day before you're installing something new and once in a while followed by 'sudo apt-get upgrade' to install latest patches. I just uploaded the screenshot, thanks for helping me out Now try sudo apt-get clean, and after it's done try sudo apt-get update again, this might clear it up. Re: How often to run 'sudo apt-get update'. Code: Select all dpkg-deb: error: tar subprocess was killed by signal (Segmentation fault)įile "/usr/share/apt-listchanges/DebianFiles.py", line 124, in readdeb Open a terminal and type ping, and update your post with the output of that command.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |