[Bug 290252] Re: Uncontrolable Random Logout in Hardy

2008-11-16 Thread JMO Mandia
Same goes for Intrepid. Will send additional info later. -- Uncontrolable Random Logout in Hardy https://bugs.launchpad.net/bugs/290252 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list

[Bug 290252] Re: Uncontrolable Random Logout in Hardy

2008-11-16 Thread JMO Mandia
Output of command uname -a: Linux jmom-laptop 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux ** Attachment added: dmesg.log http://launchpadlibrarian.net/19703742/dmesg.log -- Uncontrolable Random Logout in Hardy https://bugs.launchpad.net/bugs/290252 You received this

[Bug 290252] Re: Uncontrolable Random Logout in Hardy

2008-11-16 Thread JMO Mandia
** Attachment added: lspci-vvnn.log http://launchpadlibrarian.net/19703752/lspci-vvnn.log -- Uncontrolable Random Logout in Hardy https://bugs.launchpad.net/bugs/290252 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu.

[Bug 290252] Re: Uncontrolable Random Logout in Hardy

2008-11-16 Thread JMO Mandia
Thanks in advance! ** Attachment added: syslog.log http://launchpadlibrarian.net/19703762/syslog.log -- Uncontrolable Random Logout in Hardy https://bugs.launchpad.net/bugs/290252 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm

[Bug 290252] Re: Uncontrolable Random Logout in Hardy

2008-11-16 Thread IanW
Thanks for the information. The syslog shows an X-server crash, so assigning to package 'xorg' Please take a look at the page https://wiki.ubuntu.com/DebuggingXorg If it becomes neccesary, are you able (and willing) to use the described dbg and ssh (from a second system) to assist the debug

[Bug 290252] Re: Uncontrolable Random Logout in Hardy

2008-10-30 Thread IanW
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information. Please include the following additional information: 1. Please include the output of the command uname -a in your next response. It should be one, long line