[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to uninstall X



Brad wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> On Mon, 6 Sep 1999, Andrei Ivanov wrote:
> 
> > > > Since I'm having so much trouble getting the extended-half of my
> > > > keyboard to work (arrow keys, pg-up/dn, etc), I'm thinking it might be
> > > > good just to purge all X-related files and do a clean install of the X
> > > > Window System.
> > > >
> > > > Preferably someone can tell me how to fix my keys; alternatively, can
> > > > anyone tell me the best way to wipe X and do a clean install?
> > >
> > > Hi!
> > >
> > > To uninstall, deselect all X11 packages (by typing "_" in dselect) and do a
> > > remove in dselect.
> > >
> > > Hope this helps, Stephan Hachinger
> >
> > Well, due to dependancy problems dslect will try to uninstall ALL packages
> > that are X-related, including Netscape and apps like that. I doubt that is
> > desired. The best solution would be to use
> > dpkg --force-depends --purge packagename
> > This will warn you about all the packages that depend on packagename, but
> > will remove the packagename without deinstalling anything else. I did this
> > to replace X in my machine also, works good.
> 
> You can tell dselect to ignore the dependancies. Just use 'Q' (that's
> shift-q) instead of enter to exit the package selection screen, then
> choose Remove from the dselect menu.
> 
> You should of course fix the situation quicky, so as not to leave your
> machine in a broken state.

Thanks for all the help, folks, but I no longer need to reinstall
X Window; (it wouldn't have fixed the problem anyway); turns out
that the reason my keyboard wasn't working properly is that the
FBDev server (which I needed to use in order to get my currently
unsupported Rage128 video card to work) doesn't support the
XKEYBOARD extension. Uncommenting the "XkbDisable" line in
XF86Config allowed me to finally get control of the keyboard (I
then had to make some mods via Xmodmap, but at least things are
working now).

Thanks, again!


Reply to: