Hi Conaz9847,
I'm applying some "lateral thinking" here, and beginning to wonder if your "strange apt-get errors" are a symptom of something else ie. could your SD card be tight on space (and hence apt-get hasn't enough room to work properly)? To test this hypothesis ...
Q1: Are you using an SD card with a pre-installed image?
Q2: If not, when you first booted up the Pi and was presented with the raspi-config menu did you choose the "expand_rootfs" option, exit raspi-config and reboot?
Finally, please boot up your Pi, login and without running "startx" type and run the following:
cd /; sudo du -k | sort -n -r | head
You should see something like this:
Code: Select all
pi@raspigrey ~ $ cd /; sudo du -k | sort -n -r | head
du: cannot access `./proc/2327/task/2327/fd/4': No such file or directory
du: cannot access `./proc/2327/task/2327/fdinfo/4': No such file or directory
du: cannot access `./proc/2327/fd/4': No such file or directory
du: cannot access `./proc/2327/fdinfo/4': No such file or directory
2294596 .
1706884 ./usr
1049828 ./usr/share
511108 ./usr/lib
417152 ./var
365024 ./usr/share/icons
205348 ./var/cache
198848 ./var/cache/apt
187052 ./usr/share/icons/oxygen
185420 ./usr/share/locale
pi@raspigrey / $
The first number is the important one ie. 2294596 in the example above - this means that the file system is using 2294596 kilo-bytes of my 4Gb SD card.
Hope this is not a "red-herring" and proves helpful.
Trev.
Still running Raspbian Jessie or Stretch on some older Pi's (an A, B1, 2xB2, B+, P2B, 3xP0, P0W, 2xP3A+, P3B+, P3B, B+, and a A+) but Buster on the P4B's. See: https://www.cpmspectrepi.uk/raspberry_pi/raspiidx.htm