Op 10 sep. 2017 11:41 schreef "Jude DaShiell" : 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

On 09/10/2017 04:41 AM, Jude DaShiell wrote:

please run sudo -H Xorg --configure and let me know if that command errors out with a segmentation fault at address 0x50 or any other address

The 'segmentation fault at address 0x50' is a bug -- plain and simple. Given the address referenced is way, way down in the system-reserved memory range, the most likely cause is an unitialized pointer, or an attempt to access a pointer outside the bounds of an allocated block of memory. Neither I, nor anyone else, can tell you where the segfault is being triggered, but a quick look at 'man Xorg' does provide a few hints on 'Xorg -configure' (not --configure): -configure When this option is specified, the Xorg server loads all video driver modules, probes for available hardware, and writes out an initial xorg.conf(5) file based on what was detected. This option currently has some problems on some platforms, but in most cases it is a good way to bootstrap the configuration process. This option is only available when the server is run as root (i.e, with real-uid 0). It would be worth checking whether your platform is one where -configure "currently has some problems." -- David C. Rankin, J.D.,P.E.