Alan L Tyree wrote:
Alan, I'm still very new to linux, so I could be way off track.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.
Look at power management, it sounds very much like power management kicking in , failing and logging you out.
Try
*xset -dpms*
In /etc/X11/XF86Config-4 comment out Option "DPMS"
Its not supported in woody 2.4... this will stop the system trying to suspend to disk.
Also make sure you dont have any ACPI stuff running, woody only supports APM which is now old and they dont work together.
Also turn off any power management in the BIOS.
If things come right, you know its power management that was causing the problem.
I think the best solution is to upgrade the kernel to 2.6, turn off APM and enable ACPI.
Or rebuild your kernel and remove APM.
If you do go the kernel upgrade route then you get kewl stuff like thermal monitoring as well, I kinda like having the processor temp on the desk top. On my laptop I also got battery monitoring working.
The easiest way is to just move to SID on debian. Also get kewl sound system like ALSA, it all seems to work just fine, however if you a KDE fan, dont. I dont like KDE so its not a problem, and it seems in debian SID, KDE is very slow in getting upgraded. It seems the linux guys arent in a hurry to help a proprietry organization like KDE. I dont recommend woody at all, it may be super stable, and good for running a postgres system but other than that its not nice. For example when you move from woody to sarge the interface is going to change. Woody likes MC, sarge onwards uses Nautilus. I suggest SARGE on desktops, and SID on laptops.
You can now see the reason, laptops have to have good power management.
Problem: running X I get logged out after about 20 of inactivity. It happens no matter what window manager I am using.
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?
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.
Cheers, Alan
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
