So far as I know, pacman's cache was left untouched by the script. On Sun, 10 Sep 2017, Guus Snijders via arch-general wrote:
Date: Sun, 10 Sep 2017 06:37:48 From: Guus Snijders via arch-general <arch-general@xxxxxxxxxxxxx> To: General Discusson about Arch Linux <arch-general@xxxxxxxxxxxxx> Cc: Guus Snijders <gsnijders@xxxxxxxxx>, arch-general@xxxxxxxxxxxxxxxxxxx Subject: Re: gnome fix needed Op 10 sep. 2017 11:41 schreef "Jude DaShiell" <jdashiel@xxxxxxxxx>: I discovered this and was able to recover, and think gnome could do with a fix. You do sound a bit mysterious here :). Apparently you discovered something, but don't tell what it is. Kudos for capturing attention, but don't expect a fix for anything soon... I put together a script to completely erase gnome from this system and for the most part that script worked really well. The exception was that it also removed wpa_supplicant [.. ] I put wpa_supplicant back on the system using the install disk Did your script also delete pacman's cache? Otherwise it would have been there in /var/cache/pacman/pkg (from the top of my head). [Sudo, xorg, segfault] Okay, that's a sudden twist. The message starts with the subject of a Gnome problem, continues on a removal script and ends with a question on a sudo/xorg question. With a little work, it could probably become a great forum or blogpost, but for a technical mailinglist it's a bit too puzzling. We usually love to puzzle out a solution for a *specific* problem. In this case, I still don't know where the problem is, other then sudo or xorg crashing. But perhaps it's just me...? Mvg, Guus Snijders
--
