Your problem isn't enlightenment (as I'm betting it is not enlightenment itself crashing, but rather your X server). The problem with gkrellm is that gkrellm has a memory leak (I have observed this in the past when leaving it running for several days). The problem with mtv is likely one of linux emulation (since it is a linux app). If you want to fix the problem with gkrellm, I'd suggest turning on debuging in it or something and tracing down what exactly is leaking memory, and/or contacting the author of said program and reporting your results to him and see how he responds. The problem with mtv isn't as easy to solve. It could be a bug in the linuxlator, a bug in one of the linux shared libraries, or a bug in mtv itself. None of these problems is easily solved. The best suggestion with regards to it is, find out exactly what you did to crash X with mtv, and don't do it. Jeremy On Sun, Feb 04, 2001 at 10:45:25AM -0500, Matthew J . Turk wrote: > > What versions of each are you running? I've been running enlightenment > > & gkrellm with X 3.3.6 for ages now without problems. Currently I'm > > using enlightenment 0.16.5 and gkrellm 1.0.5. > > > > I'm running E 0.16.5_5 and gkrellm 1.0.6. I don't think it's neccessarily > gkrellm, because E crashes when I run MTV as well, which I discovered last > night after my first message. > > Is there a way I can diagnose which library it calls when it starts to go, or > what it's doing? > > > > mjt > -- > "Having said that, music is supposed to be > in the world for celebration, ritual, and > healing - that's the point for me." > -- Trey Anastasio > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
