Re: X in Sid
Hi, and thank you. I finally have X working. I believe, although I
cannot be sure, that somehow kde was mucked up. Strange.
I know about GPM, but didn't know about making sure that the two were in
sync. That make a lot of sense, it was something like this mouse
conflict that caused me to install from Knoppix on this bitching Sony
Vaio laptop. Doing so was a mistake, since Knoppix uses a lot of
specialized programs, customized init, and such. I still have lots of
legacy obsolete stuff that Knoppix installed.
That's also why I have such a nasty XFree86Config-4 file. Knoppix
generated. But it actually works for 1280x1024, which the standard one
didn't, so I put it back.
Since erasing everything "X" and now putting it back, I have lots of fun
with fonts trying to get something readable. And getting Kmail and GPG
talking again is not looking simple either. Oh well, that's what I get
for living on the bleeding edge, ne?
Curt-
On Monday 23 February 2004 19:22, you wrote:
> Curtis Howland wrote:
> >Hi. Sorry, I'm going to have fun with this one.
> >Lynx is saying that Yahoo's "attach files" option is
> >malformed, so I cannot attach the file. I also don't
> >have copy and paste.
>
> apt-get install gpm
> Then you'll have a console-based mouse that will do cut&paste for you
> (but remember to set it to repeat "raw" and change your mouse setting
> in XF86Config-4 to /dev/gpmdata, or the console mouse and the X mouse
> will fight over the mouse data).
>
> >So I have created a single file web server:
> >http://68.101.3.223:8080/
> >that has one file, and indexing turned on. Let me know
> >if you have any problems getting the file.
> >Curt-
>
> Nothing obvious in your logfile. As someone else posted earlier
> today, it might not be X you're having a problem with, but rather
> whatever wm/de you're using. Try creating a ~/.xinitrc file with the
> single line: icewm
> (or "twm", or any other simple window manager) (and make sure to
> "apt-get install icewm" if necessary")
> and then try starting X. If X starts up then, you know the problem is
> not with X, but with your normal desktop environment/window manager.
Reply to: