Thank you. The thing is, however, that I did do anything with menudrake.
Kcontrol was working with (I can't recall precisely) kde 2.1-20010115 but
upon upgrading to kde 2.1-20010118 and then again to 2.1-20010122, kcontrol
didn't work. The only thing changing was the version of kde 2.1.
Then, there is the fact of me deleting my .kderc and .kde/ so that when I
re-logged in, it would be as if for the first time, vis a vis, kde, so it
would install all the default settings as if for the first time.
I wasn't going from 2.0.1 to 2.1, for which I might really expect trouble,
but going from one 2.1 to the next. In truth, there were only two reasons I
was even upgrading: first, to see if any newer version had a functional
kword (still negative thus far), and then to see if kcontrol was going to
work.
Yesterday, with some spare time and as I mentioned previously, I went ahead
and totally removed kde from my system and then reinstalled it. I then
deleted my then current .kderc and .kde/ as well as everything in /tmp. I
then rebooted and kcontrol was working. I went home and that evening did the
same thing on my desktop. It worked initially, I even used kcontrol to
change settings back to what I wanted. I then closed kcontrol and a minute
or so later, reopened it just to check...it didn't work and was blank again.
I didn't even THINK about menudrake and I didn't mess with any directories in
the meantime. It was working one moment, the next, it's blank.
I deleted once again my .kderc, .kde/, and everthing in .tmp/ and /tmp then
rebooted. It was working again, and then I made my changes
again...lookandfeel, fixed the file association for html, mouse acceleration.
That's all. That is all I did the previous time too. Thus far, THIS time
kcontrol still is functioning but now I expect that at any moment without any
input or change on my part, I will open it up and find it blank again. I had
hoped that there was some config file rather than just a menu structure.
With a config file, I could make it immutable so that it never vanishes or
changes.
On Saturday 03 February 2001 03:11, you wrote:
> Maybe I had to explain to you in details what is going on when you
> change your Mandrake menus with
> menudrake (read: application links). X-KDE-BaseGroup is nothing but a
> KDE directory in your application links.
> In Mandrake menu this directory is subdirectory of Configuration
> directory. That's why I told you that you have
> messed up with your application links. If you do not believe go to
> /.kde/share/ and move applnk directory somewhere
> else, then restart your kde session and take a look at Kcontrol. All
> entries are missing ;). Or you can do that using
> menudrake and remove KDE subdirectory from Configuration directory in
> your KDE menu. The result will be the same:
> empty Kcontrol. People are just not aware that using menudrake can be
> very "dangerous" and give you a headache.
>
> I bet that all of you who have empty Kcontrol have used menudrake and
> moved or deleted KDE dir in Configuration
> menu dir. And then installed kde 2.1beta1 or beta2. The whole problem is
> because KDE has its own structure of menus
> and Mandrake has another. And when you install KDE's RPM's installation
> can not find default Mandrake menu structure
> and do not puts KDE dir with links to Configuration menu dir.
>
> Best regards,
--
Against stupidity, the gods themselves contend in vain.
