I recently returned to the computing arena after some absence and reinstalled suse linux 5.3 and found that randomly x would report that my mouse was busy or in use after a session locked up and I killed it from the console. I dont remember this behavior in the past and I think gpm had some problems releasing with a bad x session running (and taking all kinds of resources). My rodent is on com1, modem is on com2. I used the character based mousie configuration thing and all is fine now. I doubt its sax or the x based setup. Any ideas? BTW, its nice to be back in familiar haunts and happy new year's to all!! Oh... Not one to send too many emails :) I am downloading informix's bundle for suse 5.2 and noticed it reports something like expired on Dec 31, 1998. What exactly does this mean? Does the database drop dead on the new year? -- Michael E. Perry mperry@basin.com ------------------ - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>