After 2 hours the system reboots itself

[Charles Hensgens]

I updated the system to karmic koala via the button in the update manager on the release day of Karmic. Now after switching on the computer (a netbook medion Akoya mini E1210 similar to a MSI-wind) after exactly 2 hours the system switches from the X window screen back to the tty screen and reboots. This rebooting occurs without going back to grub. As far as I know I have not changed anything which would provoke this. I have seen this behaviour now on a consistent basis. It happens always after 2 hours of starting the system. Please guide me in providing more information.

lsb_release -rd reveals
Description: Ubuntu 9.10
Release: 9.10

Charles

[Charles Hensgens (charles-hensgens)]

After typing the uptime command I see that the uptime just continues after 2 hours. It looks like a restarting of X and a new gnome session and not an actual reboot.

Charles

[Charles Hensgens (charles-hensgens)]

Here is the auth.log I have the impression this might be indicative for the problem.
ov 12 18:26:59 ubuntu gdm-session-worker[1709]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :0
Nov 12 18:27:04 ubuntu seahorse-daemon[1900]: init gpgme version 1.1.8
Nov 12 18:31:13 ubuntu sudo: root : TTY=unknown ; PWD=/ ; USER=charles ; COMMAND=/usr/bin/gconftool --get /system/http_proxy/use_http_proxy
Nov 12 18:31:13 ubuntu sudo: root : TTY=unknown ; PWD=/ ; USER=charles ; COMMAND=/usr/bin/gconftool --get /system/http_proxy/host
Nov 12 18:31:14 ubuntu sudo: root : TTY=unknown ; PWD=/ ; USER=charles ; COMMAND=/usr/bin/gconftool --get /system/http_proxy/port
Nov 12 19:17:01 ubuntu CRON[2371]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 12 19:17:02 ubuntu CRON[2371]: pam_unix(cron:session): session closed for user root
Nov 12 20:17:01 ubuntu CRON[2404]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 12 20:17:01 ubuntu CRON[2404]: pam_unix(cron:session): session closed for user root
Nov 12 20:26:43 ubuntu seahorse-agent[1876]: GConf error:#012 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://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Connection is closed)
Nov 12 20:26:43 ubuntu seahorse-agent[1876]: GConf error:#012 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://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Connection is closed)
Nov 12 20:28:41 ubuntu gdm-session-worker[2494]: pam_unix(gdm:session): session opened for user charles by (uid=0)
Nov 12 20:28:41 ubuntu gdm-session-worker[2494]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :0
Nov 12 20:28:47 ubuntu seahorse-daemon[2635]: init gpgme version 1.1.8
Nov 12 20:31:31 ubuntu sudo: charles : TTY=unknown ; PWD=/home/charles ; USER=root ; COMMAND=/usr/sbin/synaptic --hide-main-window --non-interactive --parent-window-id 127926312 --update-at-startup

Charles

[Charles Hensgens (charles-hensgens)]

I noticed now that the restarting of the X-server is probably linked to the program AisleRiot the patience card program. The restarting occurs only after 2 hours if AisleRiot is opened an actively played. Do not know yet if opening the program and waiting in the background yields the same error.

Charles

[Charles Hensgens (charles-hensgens)]

I saw that somebody else found the same bug bug 450832. This bug can be closed and merged with that bug. Only addition that I can give is the time it takes for the crash of the X server to occur which is 2 hours see also the log file above

Charles