On Friday 02 February 2001 01:59 pm, you wrote:
> Thank you.  BUT saying it 100 times wouldn't fix this.  Someone wrote me to
> suggest running kbuildsycoca...as root and as user.  I did.  The result was
> that root AND user no longer had a functioning kcontrol.  Neither had
> kcontrol so I cannot compare /root/.kde/share/applnk or app/ with any user.
> Whatever is lacking is lacking globally after this kbuildsycoca run.  I
> also tried the copy of
> /usr/share/applnk to .kde/share/applnk...etc.  Still no kcontrol.
>
> Perhaps you will be relieved to know that I got fed up with whatever the
> problem was (since no one seems to know SPECIFICALLY what file contains the
> information that kcontrol looks for with regards to X-KDE, etc, AND I had
> time to WASTE).  I downloaded the whole mess AGAIN.  I uninstalled all of
> KDE and then reinstalled ALL of it again.  Now, kcontrol works.  Nice, but
> I still want to know SPECIFICALLY what file provides the information to
> kcontrol so when I run into this (it is assured that upon upgrading to the
> next kde2.1 version that it will break again since it has with every kde
> 2.1 iinstall so far...even though it is upgrading from one kde 2.1 to the
> next) I can fix it without all the ridiculous downloading, uninstalling,
> reintstalling, deleting .kderc, .kde/, and restarting.  It IS ridiculous.
>
> I don't want to simply follow the formula, if it works next time since it
> didn't this time, of deleting my .kde/share/applnk and copying the
> /usr/share/applnk every time kde 2.1 gets a tweaking and I want to use it. 
> I would like to simply be able to leave everything alone and cop ONE file
> from /usr/share/applnk to my home version.
>
> I really do not mean to be an ass but SHIT!  If something isn't broken,
> don't "fix" it by breaking it with EVERY release.  Settle on the format for
> config files (or whatever) and leave it.  You do not get any gain by
> changing the name or organization of the contents of a config file (or
> whatever is involved in this repetitive problem).  I am frustrated by the
> pointless changing for the sake of changing things that don't require
> changing.
>
> On Friday 02 February 2001 13:01, you wrote:
> > On Friday 02 February 2001 19:29, you wrote:
> >
> > I really do not know how many time I have to tell you that your problem
> > is in applnk. If you have Kcontrol as root with all entries listed in
> > kcontrol and do not have the same as user that means that you messed up
> > with application links.
> >
> > 1. Check in /usr/share/applnk if this directory is readable for users
> > (see if permissions are OK).
> >
> > 2. Copy  directory to /.kde/share and restart kde.

I too have had the same frustrations as you have.  I have been off line for 2 
days trying to reinstall to get it working.  Reinstalling kde didn't do 
it(probably didn't remove some files?). I upgraded to beta2 following Chris' 
instructions on a clean 7.2 install.  Kcontrol worked but files weren't 
opening properly.  Trying to fix this by editing 
/usr/share/applnk.kde/.hidden/konqfilemgr.desktop to include inode/directory 
and inode/block device worked to open files which worked.  Url links still 
wouldn't work when I removed quanta.  Basically I have had all the hassles 
you've had.  Kcontrol crashed again and so I did another 7.2 and kde beta2 
install.  Now I try not to mess directly with the config and hidden files 
that run the kde menus and kcontrol etc. but try to find the way to use the 
software built in kde to edit them.  So far I haven't hosed anything yet.  
Just in case you want to know like I did where that X-KDE-BaseGroup=settings 
is I looked in the hidden directories and did :
[root@localhost .menu]# rgrep -r X-KDE-BaseGroup=settings *
kdebasedir:#?package(kdebase): needs="kde" section="Configuration/" 
title="KDE" kde_opt="X-KDE-BaseGroup=settings"
Note that's one line that starts with #?pac ...  and ends with   ...=settings"
Again, I don't want to mess directly with the files any more but if I 
inadvertently screw things up I'd consider adding that line to 
/root/.menu/kdebasedir .  Hope it goes well with your new install. :-)
-- 
Kelley Terry <[EMAIL PROTECTED]


Reply via email to