Kevin Brosius on Wed, 1 Aug 2001 08:50:05 -0400 |
Arthur Alexion wrote: > ... > > > Out of curiosity, is it any program or one specific program you can't > > start? Can you start another xterm when this happens, or do they fail > > also? If you have an xterm up, then close one, can you start another > > one? > > Once it happens, nothing x will run. Everything running continues > without a problem. I never specifically tried closing an xterm window > and restarting it, but I have tried shutting down j-pilot and xterm in > order to run kppp or rp3 and that did not work, so it is not a simple > free memory issue. Once it happens, no matter what I shut, I still can?t > start anything else. > > Art > That was more of a long shot. I wasn't thinking of memory. I once did an update of a Slackware based system (long time ago) between kernel versions (1.2->2.0 if I recall) and only created four of the VT devices. Not knowing much about the system, everything was fine until I ran X for a while. I could run three or four xterm's, but the next one would not start, failing silently. It took a while to connect the two events. But I also learned that some X apps. use resources other than memory. But this isn't what you are seeing. -- Kevin Brosius ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|