On Sat, 2004-07-31 at 08:49 +1000, Alan L Tyree wrote: > This is still driving me crazy and I would be grateful for any help. > > System: dead standard Debian woody with 2.4.18-bf2.4 + security updates > + Login.app + sylpheed 0.9.12 backport. > > Problem: running X I get logged out after about 20 of inactivity. It > happens no matter what window manager I am using.
Is that 20 seconds, minutes or hours of inactivity?
>
> It does not happen from a text console, so I presume it is not the
> kernel or bash.
>
> I note that there is a process running:
> /usr/bin/ssh-agent x-window-manager
>
> Is it possible that there is something in ssh that is timing me out? If
> so, where would I fix it?
Unlikely. That process is the one that stores RSA keys. I guess if it
died then it might take the window manager with it. Check the logs I
suggest below and see if anything comes out of it.
>
> I have googled all over the place and find some references to similar
> problems, but no solutions.
>
> Any other ideas gratefully received. I understand it is a security
> safeguard, but it isn't one that I want.
I'd be surprised if that were the explanation. It seems analogous to
keeping the computer turned off in the interests of security.
I've come to this thread a little late, so apologies if I'm repeating
ground that's already been covered.
The first port-of-call will be to run
tail -f ~/.xsession-errors
On a console and wait for it to die. If there's an error from a program
running *inside* the xserver, it will report something in that file
about it. This will allow you eliminate problems with xscreensaver,
typing monitors, window managers and probably a bunch of other processes
that don't normally bear consideration.
Next thing to do is to run
tail -f /var/log/XFree86.0.log
as root (I'm assuming that's the file you need to watch -- all my boxes
are Xorg now). If there's a problem in the server itself, you should get
notification in that file.
When tailing files like that I like to bash enter a few times once the
system is in a "stable" state, so that the section of log where it's an
error is clearly visible.
If you can't make sense of these logs, post them to the list and maybe
someone will see something in them.
Finally, do you get logged out if you login from console and do
startx -- :1
If not, then it's a [gkx]dm problem. There's some options in gdm about
timed sessions. I don't recall what they are or what they do. Worth
checking out though.
HTH,
James.
--
James Gregory <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
