Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was wondering what ways there are to check to see what is locking my system. It seems that anywhere from 2 minutes to 10 hours into running GNOME everything freezes and nothing, not even the keyboard or mouse, respond to my commands.
I have no idea how to isolate this problem, any help or suggestions would be appreciated.
The locking seems to happen regardless of whether I use GNOME or KDE and it seems to happen regardless of what I'm doing. Sometimes I'm moving a window, sometimes I'm downloading stuff, sometimes I'm in nautilus, ... you get the picture.
I'd like to look in the system log to see if it gives me any idea's but I'm not 100% sure I know where it is. Should be in /var/log/???, right?
/var/log/messages is where you want to look first, but you should look at the other logs in there as well. Type "less dmesg" to browse through your boot-time messages and make sure there's nothing amiss there. Lastly, use the top or ps command to look at your running processes. You might have some unnecessary procs running in the background, in which case they should be disabled.
To get more specific, you'll need to post more information such as you distro (and its version), CPU/hardware stats, network situation, etc.
I checked out the syslog and both times I've had it crash it was doing something with gconfd. But that doesn't explain it crashing the same way in KDE.
I'm running a Pentium II 350MHz machine with 64MB Ram, S3 Virge video, On Board Sound CDMI something, it's a PC Chips M590 Motherboard, Quantum Fireball 15GB hard drive, Sony CD Rom.
I'm running RH 7.2 but I had the exact same problem on Mandrake.
The problem seems entirely too persistent to be anything but a core problem, either XFree86, the kernel, or the hardware, something like that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.