Bug 995131

Summary:	openSUSE 42.2 Cannot login after recent updates - Login account icon not responding to mouse click
Product:	[openSUSE] openSUSE Distribution	Reporter:	Wayne Patton <wayne.patton>
Component:	GNOME	Assignee:	E-mail List <gnome-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	dimstar
Version:	Leap 42.2
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Wayne Patton 2016-08-23 16:37:12 UTC

After the recent (week of 8/15) updates, the login screen will not respond when I click on the login name. Usually I could hit the Enter key to initiate a login but that also does not respond. I can click on the icons in the upper right corner to initiate a reboot so the mouse is working on that screen, just not able to initiate the login. I also reinstalled the OS from build openSUSE-Leap-42.2-DVD-x86_64-Build0150-Media.iso and I get the same results after making sure all updates are applied. In order to login, I have to enable auto-login. 

My system is a Dell 5510 if that matters. 

I would be happy to provide any logs but at this point, I am not sure what to provide.

Comment 1 Wayne Patton 2016-08-23 16:48:15 UTC

When I click on "Not Listed?" I can supply my login name and when I click next, the little spinning icon shows up next to the Next button and it never stops or moves on after that. 

Here is journalctl output from my latest attempt. I used logger to log the first message, and included everything until I rebooted. 
 

Aug 23 11:44:25 yoda.wp.com wayne[3978]: logging out and trying to login
Aug 23 11:44:28 yoda.wp.com terminator.desktop[3919]: <Window object at 0x7f0fe28a69b0 (terminatorlib+window+Window at 0xc9b0f0)> is not in registered window list
Aug 23 11:44:33 yoda.wp.com org.gtk.vfs.Daemon[2139]: A connection to the bus can't be made
Aug 23 11:44:33 yoda.wp.com org.gnome.Shell.CalendarServer[2139]: gnome-shell-calendar-server[2320]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting
Aug 23 11:44:33 yoda.wp.com org.gnome.evolution.dataserver.Calendar7[2139]: (evolution-calendar-factory-subprocess:2558): GLib-GIO-WARNING **: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2430x3: The connection is closed
Aug 23 11:44:33 yoda.wp.com org.gnome.evolution.dataserver.Calendar7[2139]: (evolution-calendar-factory-subprocess:3289): GLib-GIO-WARNING **: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2430x4: The connection is closed
Aug 23 11:44:33 yoda.wp.com org.gnome.evolution.dataserver.Calendar7[2139]: (evolution-calendar-factory-subprocess:3289): GLib-GObject-WARNING **: gsignal.c:2635: instance '0x492a010' has no handler with id '212'
Aug 23 11:44:33 yoda.wp.com org.freedesktop.Tracker1[2139]: Received signal:15->'Terminated'
Aug 23 11:44:33 yoda.wp.com org.freedesktop.Tracker1[2139]: OK
Aug 23 11:44:52 yoda.wp.com systemd[2025]: Stopped target Default.
Aug 23 11:44:52 yoda.wp.com systemd[2025]: Stopped target Basic System.
Aug 23 11:44:52 yoda.wp.com systemd[2025]: Stopped target Paths.
Aug 23 11:44:52 yoda.wp.com systemd[2025]: Reached target Shutdown.
Aug 23 11:44:52 yoda.wp.com systemd[2025]: Starting Exit the Session...
Aug 23 11:44:52 yoda.wp.com systemd[2025]: Stopped target Timers.
Aug 23 11:44:52 yoda.wp.com systemd[2025]: Stopped target Sockets.
Aug 23 11:44:52 yoda.wp.com systemd[2028]: pam_unix(systemd-user:session): session closed for user wayne
Aug 23 11:44:52 yoda.wp.com systemd[2025]: Received SIGRTMIN+24 from PID 4298 (kill).
-- Reboot --

Comment 2 Dominique Leuenberger 2016-08-23 16:49:59 UTC

this is most definitively a DUP of 994876

*** This bug has been marked as a duplicate of bug 994876 ***