/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "stijn" /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/stijn:/tmp/.ICE-unix/4628 Gnome-Message: gnome_execute_async_with_env_fds: returning -1 (gnome-panel:4697): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 evolution-alarm-notify-Message: Setting timeout for 2873 1166918400 1166915527 evolution-alarm-notify-Message: Sun Dec 24 01:00:00 2006 evolution-alarm-notify-Message: Sun Dec 24 00:12:07 2006 Window manager warning: last_user_time (2979392509) is greater than comparison timestamp (2979391339). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: 0xc000b7 (Run Applic) appears to be one of the offending windows with a timestamp of 2979392509. Working around... Window manager warning: last_user_time (2979393873) is greater than comparison timestamp (2979392632). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: 0xc00031 (Top Panel) appears to be one of the offending windows with a timestamp of 2979393873. Working around... Window manager warning: last_focus_time (2979408969) is greater than comparison timestamp (2979408192). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: last_user_time (2979409193) is greater than comparison timestamp (2979408192). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: 0x2400022 (Terminal) appears to be one of the offending windows with a timestamp of 2979409193. Working around... Window manager warning: last_focus_time (2979427321) is greater than comparison timestamp (2979425950). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: last_user_time (2979427392) is greater than comparison timestamp (2979425950). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: 0xe00021 (Desktop) appears to be one of the offending windows with a timestamp of 2979427392. Working around... Window manager warning: last_user_time (2979445601) is greater than comparison timestamp (2979443777). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: 0xc01627 (Run Applic) appears to be one of the offending windows with a timestamp of 2979445601. Working around... Window manager warning: last_user_time (2979463222) is greater than comparison timestamp (2979461498). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: 0x240000c (Character ) appears to be one of the offending windows with a timestamp of 2979463222. Working around... Window manager warning: last_focus_time (2979464159) is greater than comparison timestamp (2979463814). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: last_user_time (2979463878) is greater than comparison timestamp (2979463814). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! alarm-notify.c:366 (alarm_notify_new) - Alarm Notify New alarm-notify.c:302 (alarm_channel_setup) - Channel Setup alarm-notify.c:241 (alarm_notify_init) - Initing Alarm Notify alarm-queue.c:1871 (alarm_queue_init) alarm-queue.c:218 (queue_midnight_refresh) - Refresh at Sun Dec 24 01:00:00 2006 alarm-notify.c:272 (alarm_notify_finalize) - Finalize alarm-queue.c:1942 (alarm_queue_done)