Gnome "Something Has Gone Wrong" Error

Issues related to applications and software problems
Post Reply
idunbar
Posts: 2
Joined: 2015/04/07 13:27:18
Location: Chicago, IL

Gnome "Something Has Gone Wrong" Error

Post by idunbar » 2015/04/07 13:50:39

Hello,

I'm running CentOS 7.1.1503 on top of Microsoft Hyper-V. I've just done a clean install off of the 1503 media, no updates yet. When the machine first boots I briefly get the Gnome language selector and then the "Oh No! Something has gone wrong" screen comes up. Thinking there might have been a problem with first-run create user screens I added a user via SSH and rebooted. Still received the "Something has gone wrong" error. Here is the pertinent output of /var/log/messages:

Code: Select all

Apr  7 08:25:15 localhost gnome-session: (gnome-settings-daemon:2588): color-plugin-WARNING **: failed to get edid: unable to get EDID for output
Apr  7 08:25:15 localhost colord: Device added: xrandr-default
Apr  7 08:25:16 localhost gnome-session: (gnome-settings-daemon:2588): color-plugin-WARNING **: unable to get EDID for xrandr-default: unable to get EDID for output
Apr  7 08:25:16 localhost gnome-session: Window manager warning: Log level 16: Attempt to add property Gjs_MonitorConstraint::primary after class was initialised
Apr  7 08:25:16 localhost gnome-session: Window manager warning: Log level 16: Attempt to add property Gjs_MonitorConstraint::index after class was initialised
Apr  7 08:25:16 localhost chronyd[738]: Selected source 66.7.96.1
Apr  7 08:25:17 localhost systemd: Time has been changed
Apr  7 08:25:18 localhost gnome-session: JS LOG: GNOME Shell started at Tue Apr 07 2015 08:25:18 GMT-0500 (CDT)
Apr  7 08:25:18 localhost dbus-daemon: dbus[763]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
Apr  7 08:25:18 localhost dbus[763]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
Apr  7 08:25:18 localhost systemd: Starting Fingerprint Authentication Daemon...
Apr  7 08:25:18 localhost dbus-daemon: dbus[763]: [system] Successfully activated service 'net.reactivated.Fprint'
Apr  7 08:25:18 localhost dbus[763]: [system] Successfully activated service 'net.reactivated.Fprint'
Apr  7 08:25:18 localhost systemd: Started Fingerprint Authentication Daemon.
Apr  7 08:25:18 localhost fprintd: ** (fprintd:2723): WARNING **: fprint init failed with error -99
Apr  7 08:25:18 localhost systemd: fprintd.service: main process exited, code=exited, status=157/n/a
Apr  7 08:25:18 localhost systemd: Unit fprintd.service entered failed state.
Apr  7 08:25:18 localhost gnome-session: LLVM ERROR: Cannot select: intrinsic %llvm.x86.sse41.pblendvb
Apr  7 08:25:19 localhost gnome-session: Window manager warning: Log level 16: Attempt to add property Gjs_MonitorConstraint::primary after class was initialised
Apr  7 08:25:19 localhost gnome-session: Window manager warning: Log level 16: Attempt to add property Gjs_MonitorConstraint::index after class was initialised
Apr  7 08:25:19 localhost gnome-session: JS LOG: GNOME Shell started at Tue Apr 07 2015 08:25:19 GMT-0500 (CDT)
Apr  7 08:25:20 localhost dbus-daemon: dbus[763]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
Apr  7 08:25:20 localhost dbus[763]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
Apr  7 08:25:20 localhost systemd: Starting Fingerprint Authentication Daemon...
Apr  7 08:25:20 localhost dbus-daemon: dbus[763]: [system] Successfully activated service 'net.reactivated.Fprint'
Apr  7 08:25:20 localhost dbus[763]: [system] Successfully activated service 'net.reactivated.Fprint'
Apr  7 08:25:20 localhost systemd: Started Fingerprint Authentication Daemon.
Apr  7 08:25:20 localhost fprintd: ** (fprintd:2746): WARNING **: fprint init failed with error -99
Apr  7 08:25:20 localhost systemd: fprintd.service: main process exited, code=exited, status=157/n/a
Apr  7 08:25:20 localhost systemd: Unit fprintd.service entered failed state.
Apr  7 08:25:20 localhost gnome-session: LLVM ERROR: Cannot select: intrinsic %llvm.x86.sse41.pblendvb
Apr  7 08:25:20 localhost gnome-session: gnome-session[1828]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Apr  7 08:25:20 localhost gnome-session[1828]: WARNING: App 'gnome-shell.desktop' respawning too quickly
Apr  7 08:25:20 localhost gnome-session: Unrecoverable failure in required component gnome-shell.desktop
I will say that the last time I installed CentOS 7 on Hyper-V it was 7.0 and I did not get this error. Is there something wrong with the Hyper-V drivers in 7.1? Does anyone know how to fix this? I suppose I could go back and install CentOS 6.6 if I have to, but I would like to find out how to fix this. We have some VMs running 7 that have yet to be updated, and I'd hate to have to forgo updates in perpetuity. I would appreciate any help that can be given.

idunbar
Posts: 2
Joined: 2015/04/07 13:27:18
Location: Chicago, IL

Re: Gnome "Something Has Gone Wrong" Error

Post by idunbar » 2015/04/10 16:14:37

Looks like it's a Gnome issue. I reinstalled as a minimal install and installed KDE. If I start KDE manually with "startx" it works just fine, but if I run GDM I get the same error as before. Still not sure what the problem is, but since I'm only using the GUI for installing Oracle this will be a reasonable workaround.

Post Reply