FS#46835 - [gdm] Possible lockup around GDM/wayland + geoclue/networkmanager
Attached to Project:
Arch Linux
Opened by Alex (axfelix) - Thursday, 22 October 2015, 23:46 GMT
Last edited by Jan de Groot (JGC) - Thursday, 11 August 2016, 12:06 GMT
Opened by Alex (axfelix) - Thursday, 22 October 2015, 23:46 GMT
Last edited by Jan de Groot (JGC) - Thursday, 11 August 2016, 12:06 GMT
|
Details
Hi folks,
Reproducing from https://bugzilla.gnome.org/show_bug.cgi?id=756994 because I'm grasping at straws here, curious what you think: I'm running Gnome 3 with GDM. Haven't had to touch any settings until today when I rebooted for the first time in several weeks (after a few pacman updates) and GDM popped up with a double- or possibly even triple-sized cursor, the usual grey background, no login box, and didn't respond to any input at all (e.g., couldn't move the mouse). I chrooted from a live USB and tried reverting a few gdm and wayland and gnome-session packages but nothing seemed to do the trick other than uncommenting WaylandEnable=false in /etc/gdm/custom.conf. On checking Arch sources, it doesn't seem like the Wayland packages themselves have been updated in a long time, so this would seemingly be down to one of the 3.18 changes, but I can't isolate it. Technically this would be considered a HiDPI machine (it's a Dell Venue 11 Pro, 1080p, something like 200 DPI), and I've made some tweaks to default font sizes and scaling factors via the Gnome tweak tool, but I'm not using the integer HiDPI multiplier setting (under "Windows" in the tweak tool) because I found it to be overkill. No idea if gdm reads these settings or not, just mentioning it in case it's helpful. I have my kernel version locked to 3.18 due to https://bugzilla.kernel.org/show_bug.cgi?id=94281 but I doubt that's relevant either. Is there any other information I can provide that would be helpful? Basically, it seems like now that Wayland is *trying* to be DPI-aware, something is breaking. Bizarrely, if I check systemctl, it seems like geoclue (of all things) is reporting as having dumped core prior to all of the hard restarts I had to do after gdm ending up in this state. This is a long shot, but has anything changed in terms of how gdm calls networkmanager or modemmanager when using Wayland rather than Xorg? This machine has both wifi and LTE; the latter comes up under USB and isn't currently used (I don't have a SIM card in here) but Gnome does detect it properly under normal circumstances, and the wifi is probably connecting in the background while the login screen is displayed. |
This task depends upon
FS#46769,FS#46762,FS#46387, orFS#42568For me the problem occurs when I logout of my DE or WM. I then get a black background with a fixed (normal sized) cursor stuck in the middle of screen without mouse and keyboard working. System is then unusable and needs hardware-poweroff or a reboot over ssh. (as described here: https://bbs.archlinux.org/viewtopic.php?pid=1580592#p1580592)
I'm hoping my logout problem is related.
I'm on 4.1.13-1-lts with Intel GPU (+ hybrid Radeon).
Actually, I was experiencing what appeared to be a race condition after going to 4.6 where xorg-backed gdm would fail to start the shell every few boots, so hopefully this has fixed that too.