Re: Further Information on X problem

2000-04-08 Thread Lang Hurst
>> and I read that you have to put gnome-session last in your .xinitrc >> file. >> Thinking about it now, I guess that I will just try gnome-session& >> then call >> the window manager, and see what happens. That is just weird to me. > > The point is you don't have to start the window manager y

Re: Further Information on X problem

2000-04-08 Thread Michel Dänzer
Lang Hurst wrote: > > Well, I fooled around a little last night. Finally logged in as a user > instead of root, booted X with no problems (well, still the font error, but > > it doesn't seem to effect anything). Tracked the problem down to an & after > > the window manager call in .xinitrc. D

RE: Further Information on X problem

2000-04-07 Thread Lang Hurst
Well, I fooled around a little last night. Finally logged in as a user instead of root, booted X with no problems (well, still the font error, but it doesn't seem to effect anything). Tracked the problem down to an & after the window manager call in .xinitrc. Doesn't make much sense to me, as

Re: Further Information on X problem

2000-04-07 Thread Sam
I had this problem. It's failing to set the default font path because xpmac is a bad egg. What you need to do is pile all of your fonts into one directory, use mkfontdir on that directory, and use startx -- -mach64 -fp /usr/X11R6/lib/X11/fonts/fontpiledir. <- > Ok. > > $> startx -- -mach64 >

Further Information on X problem

2000-04-06 Thread Lang Hurst
Ok. $> startx -- -mach64 Screen blacks, then grey screen shows up for a second (usual X first starting screen), then it aborts and goes back to original screen which says: Running in mode=0, debth=32; req mode=0 depth=0 Using VT number 7 Mapped frame buffer ..(some physical memory addresse