gnome going berzerk... insane amount of widnows opening...

Strange thing happening on one of my machines. Gnome is seriously going berzerk. The panels on the top and bottom of the display try to appear, then fail, then try again, then fail and on and on and on. Thought it might be just my account so I tried to log in as root. Doing that shows many tasks in the bottom pannel spawn. Each space the tasks takes gets smaller and smaller as more are added. In seconds it looks like slivers of perhaps more than a hundred tasks and they just keep going on and on.

Now, the gnome screen you see before you actually log in is just fine. Once you lg in gnome goes berzerk.

I logged in via just a terminal and copied the .xsession-errors file out. Here is a sample of what it says:

line 1 through 126 or so... This goes on for almost 3,000 lines before I shutdown.

GNOME_KEYRING_SOCKET=/tmp/keyring-1bHDL2/socket
SSH_AUTH_SOCK=/tmp/keyring-1bHDL2/socket.ssh
Failed to play sound: File or data not found
abrt-applet: Can't access '/var/spool/abrt/pyhook-2014-02-04-06:33:58-18410': Permission denied
abrt-applet: Can't access '/var/spool/abrt/pyhook-2014-02-04-06:32:40-12773': Permission denied
abrt-applet: Can't access '/var/spool/abrt/pyhook-2014-02-04-06:31:34-7118': Permission denied
abrt-applet: Can't access '/var/spool/abrt/ccpp-2014-02-04-06:34:11-21165': Permission denied
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:44-5437.new/component': No such file or directory
(null): Warning no default label for /home/aalexzan/.gvfs

(polkit-gnome-authentication-agent-1:3055): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:3055): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
** Message: applet now removed from the notification area

** (gnome-screensaver:3023): WARNING **: screensaver already running in this session
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:42-5394/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:41-5345/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:40-5296/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:39-5251/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:38-5200/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:37-5156/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:36-5106/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:35-5057/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:31-4911/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:30-4854/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:29-4803/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:28-4751/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:26-4677/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:25-4624/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:24-4584/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:22-4532/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:21-4480/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:20-4438/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:19-4395/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:17-4279/component': No such file or directory
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:12-4049/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:09-3924/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:08-3876/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:07-3833/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:06-3788/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:05-3738/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:04-3683/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:01-3561/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:28:00-3511/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:27:58-3444/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:27:57-3396/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:27:56-3363/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
abrt-applet: Can't open file '/var/spool/abrt/ccpp-2014-02-04-06:27:54-3314/component': No such file or directory
abrt-applet: Exceeded maximum number of notifications
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
** Message: applet now embedded in the notification area
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
** Message: applet now removed from the notification area
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
** Message: applet now embedded in the notification area
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
** Message: applet now removed from the notification area

** (gnome-panel:3379): CRITICAL **: panel_applet_frame_change_background: assertion `PANEL_IS_WIDGET (GTK_WIDGET (frame)->parent)' failed
** Message: applet now embedded in the notification area
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
** Message: applet now removed from the notification area

** (gnome-panel:3430): CRITICAL **: panel_applet_frame_change_background: assertion `PANEL_IS_WIDGET (GTK_WIDGET (frame)->parent)' failed
** Message: applet now embedded in the notification area

(nm-applet:3037): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
** Message: applet now removed from the notification area

** (gnome-panel:3474): CRITICAL **: panel_applet_frame_change_background: assertion `PANEL_IS_WIDGET (GTK_WIDGET (frame)->parent)' failed

[snipped]

line 2679 and up...

This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14150: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14157: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14166: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14182: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14201: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14208: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14228: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14237: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14242: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14258: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14266: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14272: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14498: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14533: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14540: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14546: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14555: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14560: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14573: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14589: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
process 14666: arguments to dbus_message_unref() were incorrect, assertion "message->generation == _dbus_current_generation" failed in file dbus-message.c line 1396.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0'.
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gnome-panel: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
abrt-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gnome-volume-control-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
rhsm-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gnome-power-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gpk-update-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
bluetooth-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

(gnome-panel:8177): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed

(gnome-panel:8177): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
nautilus: Fatal IO error 0 (Success) on X server :0.

xsession-errors.txt attached for review.
I uploaded part of the /var/log/messages file as messages.log. It's edited down to just this mornings event.
I also tried again just now and using the above log files I looked in /var/spool/abrt for clues. I uploaded a tar.gz of one of the logs in that directory. That file is called, "ccpp-2014-02-04-18:45:31-6597.tar.gz" It generated quite a few of these.

Any ideas??