Bug 746476

Summary:	"Something has gone wrong" after reboot
Product:	[Fedora] Fedora	Reporter:	Jonathan Kamens <jik>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	awilliam, lecotegougdelaforce, rstrode
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-11 08:14:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jonathan Kamens 2011-10-16 12:25:13 UTC

I imagine this must be a duplicate, but I can't find the original...

With everything current in F16, every time I reboot I get the dreaded "Something has gone wrong" screen when gdm tries to log me into my gnome session.

Note that I have auto-login enabled, so I'm not typing my username and password -- it's logging me in immediately upon boot.

Sometimes that "Something has gone wrong" screen goes black before I can click the logout button, and I have to switch to a different VT and restart prefdm.service to be able to log in.

When I do that, it usually starts up just fine.

I suspect that gdm has a dependency that is not yet fully initialized when it tries to start up.

Comment 1 Skippy 2011-11-10 22:15:59 UTC

See also Bug 741075.

Comment 2 Adam Williamson 2011-11-10 23:15:33 UTC

skippy: the error message in question is a very generic one, you can't assume all people who see the error are hitting the same bug. that error message pops up any time a process critical to the GNOME session is restarted twice within a minute.

jon: are you still having issues or has this been fixed by later f16 updates?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Jonathan Kamens 2011-11-11 08:14:41 UTC

With current updates I am not able to reproduce the issue. At least, it didn't happen the one time I tried. I'll reopen the ticket later if I see it again.

Comment 4 Skippy 2011-11-11 10:27:28 UTC

(In reply to comment #2)
> skippy: the error message in question is a very generic one, you can't assume
> all people who see the error are hitting the same bug. that error message pops
> up any time a process critical to the GNOME session is restarted twice within a
> minute.

Well, it might help if the error message was less generic.  I can imagine the answer one would get if (s)he filed a bug report simply saying "hey guys, something has gone wrong in my computer !"…

Anyway at least bringing those reports together seems to have lead to some activity on them all.  ;-)