Problems with Xorg 1.20.x (Arch32 issue)
DISCLAIMER: This is an issue happening on my netbook using Arch32, so I dont know if I can post this here. I'd like your opinion anyway, so any comment saying that I need to change my hardware, although it's true that I cant avoid it, if possible I'd like to focus on the issue at hand instead(I have several other x64 systems using Arch, so I'll have future posts regarding those for certain XD)
After upgrading my system from xorg-server 1.19.x to 1.20.x, my system (an HP Mini 210-4000 with a Atom n2800 CPU and GMA 3600 iGPU(not supported by intel driver, but some support available with xorg-server itself). After upgrading it, the system no longer started X, when the display manager greeter should appear, instead a black screen appears with only a single blinking dash at the top. I know for a fact that this package is the one causing the issue, because my system works perfectly fine without any other xf86-video-* package, and after downgrading this package back to 1.19.*, it works fine again. My main concern is that some big change occurred upstream in between those two version that removed or changed the code supporting my board. I'd like to know if something similar has happened to you on similar systems, or if you happened to know about any hint regarding any modification or new feature in Xorg upstream that might have caused this breakage.
BTW: This has happened to me on the same machine with a different distro, Void Linux, with the same package xorg-server 1.20.x. So it's perfectly reproducible. (I haven't tried in other distributions yet)
Posted Jun 23, 2018, 4:11 PM UTC
Same issue here on my desktop running a 3570k. X fails to start regardless of whether I'm using integrated graphics or my Nvidia card. Haven't had a chance to debug much yet.
Have you tried with the previous version of xorg-server?
Haven't yet, but I suspect that either mesa or xorg are responsible for the issues.
Update: Turns out GDM was failling to start due to some missing wayland libraries. Installing egl-wayland and re-installing wayland fixed my issues.
You're using wayland then? I see