Kcontrol is STILL broken after running kbuildsycoca as root and as user. KDE
2.1 hasn't had it right since its inception.
It is not an option to do a total reinstall...and if that is how Mandrake is
supposed to work, it is going to LOSE people instead of gain them. One
should not have to totally reinstall the distro just to upgrade one part of
it that isn't even critical and central to its overall function. That is
what M$ requires of windoze users. It is not something to emmulate here.
In any case, this is the ONLY distro I have ever used that would appear to
require periodic complete reinstalls just to get a damn window manager and
environment working. Not acceptable.
I have many packages on my system upgraded from the raw 7.2 install. The
kernel, my XFree, devel libs, etc. I will not lose all that just to make
kcontrol work. That isn't the way to design a system anyway. It should NOT
be necessary. This problem exists on both my laptop and desktop system
essentially everything working perfectly on both except kcontrol. Kcontrol
broke ONLY upon installing kde2.1. The problem resides in kde 2.1, not on
the system.
Kcontrol SHOULD work off a simple, neverchanging config file. It obviously
doesn't. In any case, deleting all things kde from one's home directory and
then re-logging in, thus "installing" kde for that user from scratch should
work...it does not. It is broken and needs fixing before they (KDE or
Mandrake or anyone else for that matter) tries to release it as a "final".
If it is released without fixing this (simple) problem, then it is releasing
an obviously buggy package - which is what M$ does.
It works for root but not users. This means that what is required to make it
function properly IS on the computer but it isn't being used for ALL users.
What is this "thing/file" that allows root to use kcontrol but remains
invisable and lost to users? Where does this magic item go so that it can be
fixed for users? All I get (only as a user) when trying to run kcontrol is:
WARNING: No K menu group with X-KDE-BaseGroup=settings found ! Defaulting to
Settings/
Obviously, the Settings/ directory is dicked up or it would work. What file,
and where, contains this X-KDE-BaseGroup=settings entry?
On Thursday 01 February 2001 06:34, you wrote:
> Here is an excerpt from another message on the KDE mailing list.
> I too had the empty control center, but did something different
> (just can't remember what) that fixed it.
>
> Brian
>
> I compiled and installed the KDE2.1beta2, and after a restart I
> had the problem of duplicate menu entries, AND an empty control
> center.
>
> I recalled some article on this list saying that the menu
> structure of the kmenu is corrected with kbuildsycoca.
> Well, I ran it as root and as user, and after that suddenly my
> control center was not empty any more
>
> -----Original Message-----
> From: Tom Brinkman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 30, 2001 9:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] kcontrol STILL doesn't function
>
>
> "Blank Control Center" (kcontrol)
> FWIW, (as user) first thing I did after updating to KDE2b2 was to
> make sure everything was working (it was). Then I installed a few apps I
> use and made the menu entries using menudrake. Then as has been my habit
> with the early updates I made a backup copy of the ../.kde/share/applnk/
> directory. Everything is still fine at this point including kcontrol.
>
> Then, as in earlier kde2 updates, I started File Manager as root and
> changed owner of /applnk/ to root. With earlier updates this always
> prevented losing my user changes. This time it broke kcontrol, it was
> blank (no modules), and unusable. All I had to do to fix it was to copy
> my bakup /applnk/ back in, after deleting the 'root' owned /applnk/
>
> KDE2b2 has not lost any of my user changes, but messin with /applnk/
> as root will break kcontrol ..... so don't ;>
--
Against stupidity, the god's themselves contend in vain.
