===== BEGIN MILESTONES (/usr/bin/sabayon) =====
MainThread 2009/03/24 12:46:33.4248 (admin-tool): Creating profiles dialog
MainThread 2009/03/24 12:46:33.4450 (admin-tool): Starting main loop
MainThread 2009/03/24 12:46:37.4760 (admin-tool): ========== BEGIN SABAYON-SESSION LOG ==========
DISPATCH ERROR! _glapi_add_dispatch failed to add glGenerateMipmap!
DISPATCH ERROR! _glapi_add_dispatch failed to add glRenderbufferStorage!
DISPATCH ERROR! _glapi_add_dispatch failed to add glCheckFramebufferStatus!
DISPATCH ERROR! _glapi_add_dispatch failed to add glFramebufferTexture3D!
DISPATCH ERROR! _glapi_add_dispatch failed to add glFramebufferTexture2D!
DISPATCH ERROR! _glapi_add_dispatch failed to add glFramebufferRenderbuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glFramebufferTexture1D!
DISPATCH ERROR! _glapi_add_dispatch failed to add glBindFramebuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glGenRenderbuffers!
DISPATCH ERROR! _glapi_add_dispatch failed to add glIsFramebuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glGetFramebufferAttachmentParameteriv!
DISPATCH ERROR! _glapi_add_dispatch failed to add glDeleteFramebuffers!
DISPATCH ERROR! _glapi_add_dispatch failed to add glGenFramebuffers!
DISPATCH ERROR! _glapi_add_dispatch failed to add glBindRenderbuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glDeleteRenderbuffers!
DISPATCH ERROR! _glapi_add_dispatch failed to add glGetRenderbufferParameteriv!
DISPATCH ERROR! _glapi_add_dispatch failed to add glIsRenderbuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glBlitFramebuffer!
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
Xlib:  extension "RANDR" missing on display ":1.0".
Xlib:  extension "RANDR" missing on display ":1.0".
Xlib:  extension "RANDR" missing on display ":1.0".
SESSION_MANAGER=local/spagetka:/tmp/.ICE-unix/6446
** Message: another SSH agent is running at: /tmp/ssh-egesWH6446/agent.6446
Xlib:  extension "RANDR" missing on display ":1.0".
1237895196.228245 Session manager: disconnected...
Xlib:  extension "RANDR" missing on display ":1.0".
Xlib:  extension "RANDR" missing on display ":1.0".
===== BEGIN MILESTONES (/usr/libexec/sabayon-session) =====
MainThread 2009/03/24 12:46:35.4241 (sabayon-session): Starting session window for profile_name='xxx', profile_path='/tmp/profile-sabayon-admin-kZ4ZQr.zip', display_number='1'
MainThread 2009/03/24 12:46:35.4674 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'xxx', '--admin-log-config=/root/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmpHXIG7w']
MainThread 2009/03/24 12:46:35.6377 (proto-session): Finished running sabayon-apply with normal exit status
MainThread 2009/03/24 12:46:35.7985 (sabayon-session): Entering main loop.  Wheeee!
MainThread 2009/03/24 12:46:37.3866 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3872 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 117, in handle_profile_change
    self.COLUMN_DESCRIPTION, new_change.get_short_description ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sources/paneldelegate.py", line 113, in get_short_description
    panel_toplevel = self.delegate.PanelToplevel(toplevel_id)
  File "//usr/lib64/python2.5/site-packages/sabayon/sources/paneldelegate.py", line 170, in __init__
    self.orientation = self.client.get_string (PANEL_KEY_BASE + "/toplevels/" + id + "/orientation")
TypeError: cannot concatenate 'str' and 'NoneType' objects

MainThread 2009/03/24 12:46:37.3873 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3874 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 89, in handle_profile_change
    iter = self.find (new_change.get_source (), new_change.get_id ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 129, in find
    if change.get_source () == source and \
AttributeError: 'NoneType' object has no attribute 'get_source'

MainThread 2009/03/24 12:46:37.3874 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3875 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 89, in handle_profile_change
    iter = self.find (new_change.get_source (), new_change.get_id ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 129, in find
    if change.get_source () == source and \
AttributeError: 'NoneType' object has no attribute 'get_source'

MainThread 2009/03/24 12:46:37.3876 (sabayon-session): Terminating
MainThread 2009/03/24 12:46:37.3876 (sabayon-session): Exiting abnormally; dumping log due to a fatal error
===== END MILESTONES (/usr/libexec/sabayon-session) =====
===== BEGIN RING BUFFER (/usr/libexec/sabayon-session) =====
MainThread 2009/03/24 12:46:35.4241 (sabayon-session): Starting session window for profile_name='xxx', profile_path='/tmp/profile-sabayon-admin-kZ4ZQr.zip', display_number='1'
MainThread 2009/03/24 12:46:35.4674 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'xxx', '--admin-log-config=/root/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmpHXIG7w']
MainThread 2009/03/24 12:46:35.6377 (proto-session): Finished running sabayon-apply with normal exit status
MainThread 2009/03/24 12:46:35.7985 (sabayon-session): Entering main loop.  Wheeee!
MainThread 2009/03/24 12:46:37.3866 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3872 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 117, in handle_profile_change
    self.COLUMN_DESCRIPTION, new_change.get_short_description ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sources/paneldelegate.py", line 113, in get_short_description
    panel_toplevel = self.delegate.PanelToplevel(toplevel_id)
  File "//usr/lib64/python2.5/site-packages/sabayon/sources/paneldelegate.py", line 170, in __init__
    self.orientation = self.client.get_string (PANEL_KEY_BASE + "/toplevels/" + id + "/orientation")
TypeError: cannot concatenate 'str' and 'NoneType' objects

MainThread 2009/03/24 12:46:37.3873 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3874 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 89, in handle_profile_change
    iter = self.find (new_change.get_source (), new_change.get_id ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 129, in find
    if change.get_source () == source and \
AttributeError: 'NoneType' object has no attribute 'get_source'

MainThread 2009/03/24 12:46:37.3874 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3875 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 89, in handle_profile_change
    iter = self.find (new_change.get_source (), new_change.get_id ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 129, in find
    if change.get_source () == source and \
AttributeError: 'NoneType' object has no attribute 'get_source'

MainThread 2009/03/24 12:46:37.3876 (sabayon-session): Terminating
MainThread 2009/03/24 12:46:37.3876 (sabayon-session): Exiting abnormally; dumping log due to a fatal error
===== END RING BUFFER (/usr/libexec/sabayon-session) =====


This configuration for the debug log can be re-created
by putting the following in /root/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000
Xlib:  extension "RANDR" missing on display ":1.0".
-c: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
gnome-panel: Fatal IO error 2 (No such file or directory) on X server :1.0.
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection was disconnected before a reply was received)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to read saved session file /tmp/sabayon-temp-home-6o13z3/.config/metacity/sessions/default0.ms: Failed to open file '/tmp/sabayon-temp-home-6o13z3/.config/metacity/sessions/default0.ms': No such file or directory
Window manager warning: Log level 32: could not find XKB extension.
Window manager warning: Fatal IO error 111 (Connection refused) on display ':1.0'.

========== END SABAYON-SESSION LOG ==========
MainThread 2009/03/24 12:46:37.4761 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1)
MainThread 2009/03/24 12:46:37.5094 (admin-tool): Terminating main loop
MainThread 2009/03/24 12:46:37.5095 (admin-tool): Exiting abnormally; dumping log due to a fatal error
===== END MILESTONES (/usr/bin/sabayon) =====
===== BEGIN RING BUFFER (/usr/bin/sabayon) =====
MainThread 2009/03/24 12:46:33.4248 (admin-tool): Creating profiles dialog
MainThread 2009/03/24 12:46:33.4450 (admin-tool): Starting main loop
MainThread 2009/03/24 12:46:35.2685 (USER): Starting to edit profile 'xxx'
MainThread 2009/03/24 12:46:37.4760 (admin-tool): ========== BEGIN SABAYON-SESSION LOG ==========
DISPATCH ERROR! _glapi_add_dispatch failed to add glGenerateMipmap!
DISPATCH ERROR! _glapi_add_dispatch failed to add glRenderbufferStorage!
DISPATCH ERROR! _glapi_add_dispatch failed to add glCheckFramebufferStatus!
DISPATCH ERROR! _glapi_add_dispatch failed to add glFramebufferTexture3D!
DISPATCH ERROR! _glapi_add_dispatch failed to add glFramebufferTexture2D!
DISPATCH ERROR! _glapi_add_dispatch failed to add glFramebufferRenderbuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glFramebufferTexture1D!
DISPATCH ERROR! _glapi_add_dispatch failed to add glBindFramebuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glGenRenderbuffers!
DISPATCH ERROR! _glapi_add_dispatch failed to add glIsFramebuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glGetFramebufferAttachmentParameteriv!
DISPATCH ERROR! _glapi_add_dispatch failed to add glDeleteFramebuffers!
DISPATCH ERROR! _glapi_add_dispatch failed to add glGenFramebuffers!
DISPATCH ERROR! _glapi_add_dispatch failed to add glBindRenderbuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glDeleteRenderbuffers!
DISPATCH ERROR! _glapi_add_dispatch failed to add glGetRenderbufferParameteriv!
DISPATCH ERROR! _glapi_add_dispatch failed to add glIsRenderbuffer!
DISPATCH ERROR! _glapi_add_dispatch failed to add glBlitFramebuffer!
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
Xlib:  extension "RANDR" missing on display ":1.0".
Xlib:  extension "RANDR" missing on display ":1.0".
Xlib:  extension "RANDR" missing on display ":1.0".
SESSION_MANAGER=local/spagetka:/tmp/.ICE-unix/6446
** Message: another SSH agent is running at: /tmp/ssh-egesWH6446/agent.6446
Xlib:  extension "RANDR" missing on display ":1.0".
1237895196.228245 Session manager: disconnected...
Xlib:  extension "RANDR" missing on display ":1.0".
Xlib:  extension "RANDR" missing on display ":1.0".
===== BEGIN MILESTONES (/usr/libexec/sabayon-session) =====
MainThread 2009/03/24 12:46:35.4241 (sabayon-session): Starting session window for profile_name='xxx', profile_path='/tmp/profile-sabayon-admin-kZ4ZQr.zip', display_number='1'
MainThread 2009/03/24 12:46:35.4674 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'xxx', '--admin-log-config=/root/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmpHXIG7w']
MainThread 2009/03/24 12:46:35.6377 (proto-session): Finished running sabayon-apply with normal exit status
MainThread 2009/03/24 12:46:35.7985 (sabayon-session): Entering main loop.  Wheeee!
MainThread 2009/03/24 12:46:37.3866 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3872 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 117, in handle_profile_change
    self.COLUMN_DESCRIPTION, new_change.get_short_description ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sources/paneldelegate.py", line 113, in get_short_description
    panel_toplevel = self.delegate.PanelToplevel(toplevel_id)
  File "//usr/lib64/python2.5/site-packages/sabayon/sources/paneldelegate.py", line 170, in __init__
    self.orientation = self.client.get_string (PANEL_KEY_BASE + "/toplevels/" + id + "/orientation")
TypeError: cannot concatenate 'str' and 'NoneType' objects

MainThread 2009/03/24 12:46:37.3873 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3874 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 89, in handle_profile_change
    iter = self.find (new_change.get_source (), new_change.get_id ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 129, in find
    if change.get_source () == source and \
AttributeError: 'NoneType' object has no attribute 'get_source'

MainThread 2009/03/24 12:46:37.3874 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3875 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 89, in handle_profile_change
    iter = self.find (new_change.get_source (), new_change.get_id ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 129, in find
    if change.get_source () == source and \
AttributeError: 'NoneType' object has no attribute 'get_source'

MainThread 2009/03/24 12:46:37.3876 (sabayon-session): Terminating
MainThread 2009/03/24 12:46:37.3876 (sabayon-session): Exiting abnormally; dumping log due to a fatal error
===== END MILESTONES (/usr/libexec/sabayon-session) =====
===== BEGIN RING BUFFER (/usr/libexec/sabayon-session) =====
MainThread 2009/03/24 12:46:35.4241 (sabayon-session): Starting session window for profile_name='xxx', profile_path='/tmp/profile-sabayon-admin-kZ4ZQr.zip', display_number='1'
MainThread 2009/03/24 12:46:35.4674 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'xxx', '--admin-log-config=/root/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmpHXIG7w']
MainThread 2009/03/24 12:46:35.6377 (proto-session): Finished running sabayon-apply with normal exit status
MainThread 2009/03/24 12:46:35.7985 (sabayon-session): Entering main loop.  Wheeee!
MainThread 2009/03/24 12:46:37.3866 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3872 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 117, in handle_profile_change
    self.COLUMN_DESCRIPTION, new_change.get_short_description ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sources/paneldelegate.py", line 113, in get_short_description
    panel_toplevel = self.delegate.PanelToplevel(toplevel_id)
  File "//usr/lib64/python2.5/site-packages/sabayon/sources/paneldelegate.py", line 170, in __init__
    self.orientation = self.client.get_string (PANEL_KEY_BASE + "/toplevels/" + id + "/orientation")
TypeError: cannot concatenate 'str' and 'NoneType' objects

MainThread 2009/03/24 12:46:37.3873 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3874 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 89, in handle_profile_change
    iter = self.find (new_change.get_source (), new_change.get_id ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 129, in find
    if change.get_source () == source and \
AttributeError: 'NoneType' object has no attribute 'get_source'

MainThread 2009/03/24 12:46:37.3874 (admin-tool): Got fatal error: Fatal exception in callback; exiting main loop
MainThread 2009/03/24 12:46:37.3875 (admin-tool): Traceback (most recent call last):
  File "//usr/lib64/python2.5/site-packages/sabayon/errors.py", line 125, in wrapper
    return func (*args, **kwargs)
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 89, in handle_profile_change
    iter = self.find (new_change.get_source (), new_change.get_id ())
  File "//usr/lib64/python2.5/site-packages/sabayon/sessionwindow.py", line 129, in find
    if change.get_source () == source and \
AttributeError: 'NoneType' object has no attribute 'get_source'

MainThread 2009/03/24 12:46:37.3876 (sabayon-session): Terminating
MainThread 2009/03/24 12:46:37.3876 (sabayon-session): Exiting abnormally; dumping log due to a fatal error
===== END RING BUFFER (/usr/libexec/sabayon-session) =====


This configuration for the debug log can be re-created
by putting the following in /root/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000
Xlib:  extension "RANDR" missing on display ":1.0".
-c: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.0.
gnome-panel: Fatal IO error 2 (No such file or directory) on X server :1.0.
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection was disconnected before a reply was received)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Could not send message to gconf daemon: Connection is closed)
Window manager warning: Failed to read saved session file /tmp/sabayon-temp-home-6o13z3/.config/metacity/sessions/default0.ms: Failed to open file '/tmp/sabayon-temp-home-6o13z3/.config/metacity/sessions/default0.ms': No such file or directory
Window manager warning: Log level 32: could not find XKB extension.
Window manager warning: Fatal IO error 111 (Connection refused) on display ':1.0'.

========== END SABAYON-SESSION LOG ==========
MainThread 2009/03/24 12:46:37.4761 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1)
MainThread 2009/03/24 12:46:37.5092 (USER): Finishing editing profile
MainThread 2009/03/24 12:46:37.5094 (admin-tool): Terminating main loop
MainThread 2009/03/24 12:46:37.5095 (admin-tool): Exiting abnormally; dumping log due to a fatal error
===== END RING BUFFER (/usr/bin/sabayon) =====


This configuration for the debug log can be re-created
by putting the following in /root/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000
