Bug 1287142

Summary: "Oh no! Something has gone wrong." instead of gdm login screen
Product: [Fedora] Fedora Reporter: Andre Robatino <robatino>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: awilliam, fmuellner, kparal, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 15:17:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1230431    
Attachments:
Description Flags
system journal
none
rpm -qa none

Description Andre Robatino 2015-12-01 15:37:12 UTC 
Description of problem:
Right after graphical mode starts, I get the "Oh no!" screen instead of the gdm login screen. Proposing as Alpha Blocker according to https://fedoraproject.org/wiki/Fedora_24_Alpha_Release_Criteria#Expected_installed_system_boot_behavior : "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility."

Version-Release number of selected component (if applicable):
gnome-shell-3.19.2-1.fc24.x86_64

How reproducible:
always

Additional info:
VirtualBox 5.0.10 VM
Comment 1 Kamil Páral 2015-12-01 15:44:47 UTC 
I see the same thing on a KVM VM with Rawhide and both gnome-shell-3.19.2-1.fc24.x86_64 and gnome-shell-3.19.1-3.20151110.fc24.x86_64. But it doesn't seem to affect bare metal.
Comment 2 Kamil Páral 2015-12-01 15:45:04 UTC 
Created attachment 1100946 [details]
system journal
Comment 3 Kamil Páral 2015-12-01 15:45:24 UTC 
Created attachment 1100947 [details]
rpm -qa
Comment 4 Adam Williamson 2015-12-02 15:17:05 UTC 

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