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
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

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

Closed by  Jan de Groot (JGC)
Thursday, 11 August 2016, 12:06 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Friday, 23 October 2015, 03:08 GMT
I'm guessing this is a duplicate of  FS#46769 ,  FS#46762 ,  FS#46387 , or  FS#42568 
Comment by Alex (axfelix) - Friday, 23 October 2015, 04:56 GMT
Perhaps. I'm not on Nvidia, and I haven't seen anyone else mention getting the hidpi cursor or the usual grey lockscreen background (immediately before what appears to be a segfault, since the cursor won't respond and I can't switch to tty2). But there's clearly some brittle new stuff kicking around gdm 3.18 vis-a-vis wayland, and I'm not sure how far to read into the geoclue thing.
Comment by Dino Hensen (d.hensen) - Monday, 23 November 2015, 00:22 GMT
I also experience these geoclue coredumps. At login I also see a very huge cursor, but I always have working inputs.
For 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).
Comment by Ethan Schoonover (altercation) - Wednesday, 02 December 2015, 00:12 GMT
I switched from Gnome under X to Gnome Wayland and a moment or two after login I would be dumped back to GDM. Checking journalctl showed the geoclue coredump. I disabled geoclue via systemctl and was able to login to a wayland session from GDM successfully. I'd like to test this further, but wanted to provide this anecdote in case it assists anyone else.
Comment by Jan de Groot (JGC) - Monday, 27 June 2016, 13:08 GMT
Is this still an issue? Note that geoclue has been replaced by geoclue2 in the meantime.
Comment by Alex (axfelix) - Monday, 27 June 2016, 15:36 GMT
I'll check this week -- I expect the issue was never with geoclue but with wayland. It's just a major pain to try to toggle gdm to using wayland on this machine because it doesn't like to boot to tty so I have to have live media on hand to mount the disk in case it doesn't boot.
Comment by Alex (axfelix) - Monday, 27 June 2016, 17:40 GMT
Hey, what do you know, seems fixed now! Wayland/gdm cursor is huge compared to Xorg/gnome-shell so it's clear that they aren't drawing on the same hidpi settings at this point yet (and I've customized gnome's scaling a bit because the flat 2x didn't look good; I have fonts set to larger and UI elements set to 1.25 and so on), but I think this is no longer breaking.

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.

Loading...