Ignore me. It helps when you pay attention when you read the documents. It turns out you have to define some type of core mouse pointer since the stylistic pen isn't one because gnome and kde both try and accelerate it when you start. If it isn't there, they bomb.
On Wed, 2002-10-23 at 16:36, Ti Leggett wrote: > I have a very strange problem. I just installed linux a Fujitsu > Stylistic 2300 pen tablet. Everything seemed to just work. I got the pen > working and everything. GDM started up and everything seemed hunky dory > until I tried to login. First I tried loggin into a GNOME session. It'd > get about half way through gnome initialization sequence and X > restarted. So I tried KDE. Same thing. So I tried failsafe. That worked > got an xterm and ran twm. That worked. So I killed twm, and tried > gnome-session. Same thing, X restarts. Upon investigation several things > are happening that I can see. One, gnome and kde don't have permissions > to connect to the DISPLAY. Another thing, an .Xauthority file isn't > being created, so I added my own with proper things like > localhost.localdomain:0 > localhost.localdomain/unix:0 > <hostname>:0 > <hostname/unix:0 > And that didn't help. Here is a sample from the .xsession_errors files > (excuse mistypes as I'm having to retype the errors by hand): > > X connection to :0.0 broken (explicit kill or server shutdown). > X connection to :0.0 broken (explicit kill or server shutdown). > Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server > shutdown). > Gdk-ERROR **: Fatal IO error 104 (Connection reset by peer) on X server > :0.0. > Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server > shutdown). > Gdk-ERROR **: Fatal IO error 104 (Connection reset by peer) on X server > :0.0 > Gdk-ERROR **: Fatal IO error 104 (Connection reset by peer) on X server > :0.0 > > And here's what's reported in /var/log/messages: > > Oct 23 18:01:41 localhost gdm(pam_unix)[5470]: session closed for user > root > Oct 23 18:01:41 localhost gdm[5470]: gdm_slave_xioerror_handler: Fatal X > error - Restarting :0 > > I'm enabling the options that the neomagic man page says need to be > enabled to prevent lockups with this chipset (can't remember them off > the top of my head). > > Any ideas on what's going on here? Please let me know if any more > information is needed. -- Ti Leggett <[EMAIL PROTECTED]> _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
