Re: Problems with gdmconf
* Simon Hepburn (sth@blueyonder.co.uk) wrote:
> Cam Ellison wrote:
>
> > I removed gdm and all the directories I could find (having neglected to
> > have apt-get do that).
>
> gulp...
>
> > About kicker -- with no intervention from me, it is now working again, for
> > the moment. It has done that intermittent thing before.
>
> Bizarre. IIRC kicker caches a lot of its settings. Maybe your cache has
> become corrupted. Try doing
>
> #kbuildsycoca
>
> to rebuild it.
>
I shall try this in a couple of days (no time now) and see how it is.
> I'm not too sure what the current state of kde is in woody. At one time there
> was a horrible mishmash of 2.1.x/2.2.x which was causing lots of probs. The
> solution then was to upgrade everything kde to sid. It might be worth your
> while going to the packages web page and comparing woody and sid. Or just ask
> on debian-kde. I wonder if the fact that you originally installed from
> libranet has anything to do with this.
>
Maybe. That's a potato distribution (2.2r1), and I've done a complete dist-upgrade. However, the Libranet adminmenu is still in place, and that may have had some effect.
Thanks for the help.
Cam
--
Cam Ellison Ph.D. R.Psych.
From Roberts Creek on B.C.'s incomparable Sunshine Coast
camellison@dccnet.com
cam@fleuryassociates.com
Reply to: