Good question... Now another question... Have you tried the current cvs snapshot? Things are getting close to 2.2.3, and there have been numerous improvements since 2.2.2. I'm suspicious that it's been on ongoing thing since 2.2.0. Have you upgraded Distros/Kernels/etc since running 2.2.0? Could it be a bad DIMM? If you have a pair, try removing one, then the other. For me, AS has been very solid, and the current cvs is VERY solid. I don't think I've had a lockup with a stable release of AS. The only issue I had turned-out to be a bad kernel update that wasn't config'd right for my VIA processor. That took a rebuild of the kernel and a later kernel revision to fix. Jeff Krebs * Kyle Liddell (kyle@foobox.homelinux.net) wrote: > Greetings. > > I've been having some issues with Afterstep locking up on start up. In the default config, afterstep will lock up maybe every 5 startup attempts. I've since had my .xinitrc clobber the workspace_state file when I start X, which makes it happen maybe once every 20 times I start afterstep. It still seems to happen pretty often whenever I restart the afterstep session (by doing AfterStep menu->Quit->Restart this session). I've told afterstep send all the output to a logfile, but there's too much in there to just scan the whole thing. > > So, there's my problem...and my question then is, where should I start looking for the cause of this problem? > > Oh, I'm running afterstep 2.2.2, and I know I had the same problems on 2.2.1 and 2.2.0, and quite possibly earlier versions (don't remember what version afterstep was on when I first started using it). > > Thanks, > Kyle Liddell > _______________________________________________ > As-users mailing list > As-users@afterstep.org > http://mail.afterstep.org/mailman/listinfo/as-users _______________________________________________ As-users mailing list As-users@afterstep.org http://mail.afterstep.org/mailman/listinfo/as-users