[PATCH] Error in control center

Frans Englich frans.englich at telia.com
Tue Aug 10 22:52:23 BST 2004

On Tuesday 10 August 2004 21:25, Christian Mueller wrote:
> Am Dienstag, 10. August 2004 21:47 schrieb Frans Englich:
> > I think this is caused by a missconfigured setup. Christian, what KDE
> > version are you running, and is another KDE installation somehow
> > interfering?
> Yes, there's definitely something wrong with my setup.  I noticed some
> other oddities.  For example, I tried to switch the language back to
> English to be able to report the texts accurately but even after a
> restart of KDE my kcontrol is still in German but claims the selected
> language was US English.
> I guess US English should always be available, shouldn't it?

I think this is a known issue, but I'm not on it. It have been discussed here 
on kde-core-devel.

> Then there are *two* modukes in the control center to change the
> password!  One of them didn't start because of the typo.
> With the fixed typo it didn't start in the right part of the
> control center but in a window of its own...
> I (try to) run my own CVS build (KDE_3_3_BRANCH from 2004-08-07)
> alongside the stock debian testing packages (KDE 3.2.3).
> This version conflict probably also explains the crash I've seen:
> http://bugs.kde.org/show_bug.cgi?id=86812
> > KControl doesn't check the NoDisplay directive, and that's why Binner
> > remove the Categories directives from desktop files(passwords among
> > others) in order for KControl to not load them. /If/ Christian's setup is
> > broken, this behavior could be the cause of the bug(a passwords desktop
> > file with Categories laying around).
> > Attached patch makes KControl NoDisplay aware(which people have silently
> > dropped since July), but it shouldn't be necessary in this case. I run
> > clean HEAD and KControl is fine.
> Does it make any sense now to try that patch?  Guess not.

Nope. I just thought it could be a good idea ventilating the (slightly 
related) issue.

> I haven't applied it yet...
> Is there a standard procedure to troubleshoot this kind of version mixup?

Judging from your description you have multiple desktop files for the same 
components. When you rebuild, make sure to have erased your $KDEDIRS(where 
KDE is installed) in order to not have old files laying around. Also ensure 
$KDEDIRS only contains the KDE version you want to use before you start the 
session. An efficient way is of course to erase all other KDE versions...



More information about the kde-core-devel mailing list